Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requests pack pre-soft launch #15

Open
7 of 14 tasks
giacecco opened this issue Dec 12, 2014 · 5 comments
Open
7 of 14 tasks

Requests pack pre-soft launch #15

giacecco opened this issue Dec 12, 2014 · 5 comments
Assignees

Comments

@giacecco
Copy link
Contributor

Originally in an email by @peterkwells:

  • add CC-BY 4.0 licence in to footer (removes need to state in text), reduce font size on footer
  • change "civic hackers" to "civic technologists" on front page
  • Change "Download" to "Get the data"? Or similar? There will be three ways to get it - download, URI/search and API elsewhere on page, state that this is an Alpha release and that we want feedback
  • link to forums for feedback,
  • say that APIs are "coming soon",
  • smooth out some of the tech language ,
  • add in a link to http://alpha.openaddressesuk.org/ near the top
  • Add an extra level to the Documentation page and include the other docs, simply linking to their Google docs versions. Reiterate that we want people's feedback on what would be useful for them, remove the LR PP data stuff from the tech docs
  • Add forums and public sector datasets to the Get Involved page
  • Move the SM1 (public sector datasets) text to the forums
  • Stick a quick blog up, link to the ODI press release for Open Addresses
  • Team - put para breaks in the team page (is this the same as OA: About/Team page needs restyling theodi/shared#422 @pezholio ?)
  • Vision/FAQ review - FAQ certainly needs the forums adding in
  • Find out where the "add an address" page has gone and get it back in

Peter says: I can do all of the above (apart maybe from adding the extra level to the documentation page) without tech support but is there any chance of getting alpha.openaddressesuk.org hooked into the main site (discussed at theodi/shared#439 ) It's a "dead-end" as it stands with no way to get back.

@giacecco
Copy link
Contributor Author

A few questions for @peterkwells

  • what are the "other docs" you're referring to?
  • when you say that the API are coming soon, it is just because we don't have documentation for those yet? the APIs are working (they're very slow though)
  • I don't understand the "Move the SM1 (public sector datasets) text to the forums" but if you can do it, it is not a problem

@peterkwells
Copy link

Hi All - I'm doing this now, please don't laugh at my markdown mistakes ;-) Can we keep "hands off" the website, apart from #439, whilst I do my thang.

@giacecco -

  1. these docs have been published

Now that we are soft launching the dataset and website we simply integrate them over and continue asking for feedback
2) if the APIs are there that's great, I'll point it over at the documentation
3) I used the SM (social machine)nomenclature in the draft board slides: https://docs.google.com/a/openaddress.es/presentation/d/1IKJW3NhBn1SGsKOKY1K-aLYt599zvKr1gMCWT8mpEpA/edit#slide=id.g44472b6c7_06

@giacecco
Copy link
Contributor Author

About the docs: I would strictly separate the pre-OA docs and the OA docs. The option to have a dedicated documentation section is suitable, as you were suggesting, but because they will become obsolete very very soon I will give them less privileged space. Perhaps they could be not more than a post in the forum.

About the social machines: I would suggest you stay away from the term, even academics don't use it! Too easy to misinterpret or to use inappropriately. I should have told you earlier. I'll suggest you something different when I review that slide.

I won't touch the website until you tell me you're done. Will tell the rest of the team in IRC.

@peterkwells
Copy link

@Floppy lots of stuff done, a couple of bits left to do/discuss and I think the changes to navigation.yml have broken stuff. Let me know when good to run through so you can start moving to the new Rails site.

@giacecco
Copy link
Contributor Author

Hi @peterkwells I shared my more detailed feedback to the "other docs" in private as you requested. This note is just not to forget, as part of this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants