Closed JenMysoc closed 10 years ago
Should also include templates for documentation pages within this site.
Also add #1322
We've got templates for the documentation pages - they're at e.g. http://code.alaveteli.org/installing/script/. I think what we need is just a home page like http://fixmystreet.org/
Here's a first-cut of a wireframe for the homepage.
This is based off what we did for FMS.org, combined with content that's available on alaveteli.org currently.
I like this, it's already a big improvement. I think 'Get started' is probably the main call to action, but I wonder what the others for this page should be - I'm thinking perhaps the alaveteli dev list or the Turbo Transparency paper? Maybe not 'help us translate'.
@wrightmartin might be worth looking at http://stefanw.github.io/froide/ too.
Am I coming from too nerdy a perspective when I think that we ought to say something about publishing the responses online? That is the 'gimmick' of the site.
More content to add:
We could 'show not tell' the responsive design? Maybe 'learn more' should link to a brief description of the site, and the Turbo paper.
Do you have thoughts on showing existing installs on this page?
We could 'show not tell' the responsive design?
Like a screenshot of it running on multiple devices? I thought about it, but had a reservation as we're selling a platform, it's a trope of app websites and the visitor might interpret it as an app? I might be wrong though...
Maybe 'learn more' should link to a brief description of the site, and the Turbo paper.
I wonder if the github link in the main hero area is too prominent and we could replace it with 'learn more'?
Do you have thoughts on showing existing installs on this page?
The box-out on the right about the worldwide reach is sort of that - I thought it was more useful than showing specific installs, like we did on FMS, as well as showing a good reach, it also demonstrates how it can adapt to legislative differences
The box-out on the right about the worldwide reach is sort of that - I thought it was more useful than showing specific installs, like we did on FMS, as well as showing a good reach, it also demonstrates how it can adapt to legislative differences
+1 – I like this.
Am I coming from too nerdy a perspective when I think that we ought to say something about publishing the responses online? That is the 'gimmick' of the site.
I think there's something to be said here. It's a key feature.
I think we should put some thought in to what the "features" are. The current ones are more like tech specs, except for "Simple", which IMO is more the type of things we should be highlighting as features. How is it going to help / solve problems, etc.
Like a screenshot of it running on multiple devices? I thought about it, but had a reservation as we're selling a platform, it's a trope of app websites and the view might interpret it as an app? I might be wrong though...
I see what you're saying. I think I'm trying to avoid us using the word 'responsive' here as I don't think people outside the web development world understand what that is. I think we're actually trying to speak to two kinds of people with this frontpage - FOI activists with varying levels of technical knowledge, and techies with varying levels of FOI knowledge. I want the former to 'get' that this will work on smartphones.
Maybe 'learn more' should link to a brief description of the site, and the Turbo paper.
I wonder if the github link in the main hero area is too prominent and we could replace it with 'learn more'?
Yeah, and maybe have a less prominent direct link to github later in the page.
The box-out on the right about the worldwide reach is sort of that - I
thought it was more useful than showing specific installs, like we did on FMS, as well as showing a good reach, it also demonstrates how it can adapt to legislative differences
OK.
v2
This is really good. My only suggestion is maybe adding another element like 'Get the code' that says 'Talk to us' or 'Get in touch' - saying something like 'Not sure if this is the right thing for you?"
+1 on "Messaging, notifications and follow ups" – totally the right kind of things that the platform is solving. I wonder if there's a nice way we can snapshot the public aspect of the requests, and why that's important.
:horse_racing:
:+1:
On Fri, Jun 6, 2014 at 3:27 PM, Martin Wright notifications@github.com wrote:
[image: alaveteli-org] https://cloud.githubusercontent.com/assets/2292925/3201333/b5dccf3a-ed86-11e3-978a-ae7322d51352.png
— Reply to this email directly or view it on GitHub https://github.com/mysociety/alaveteli/issues/1350#issuecomment-45342447 .
Closing as this design has been rolled out and looks great. For disucssion on the addition of screenshot(s) of the site in action as per #1322 , see #1622