Skip to content
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.

Create final wireframe/design from this image #38

Open
ngrad opened this issue Sep 17, 2015 · 2 comments
Open

Create final wireframe/design from this image #38

ngrad opened this issue Sep 17, 2015 · 2 comments

Comments

@ngrad
Copy link
Contributor

ngrad commented Sep 17, 2015

wirestorm-combined

Header menu

  • Index - a button that brings the user to a page that has a list of all the data sets collected, truly an index page, @crdunwel had this idea.
  • About - this page will create context for the project, tell the story of what we're doing here at Sunlight and most importantly house all Policy Briefs and Blog posts associated with the grant. We do not want to send users back to sf.com to read these briefs and it is grant required that they live with the tool. They should be downloadable by PDF to stay concise and easy to read without taking up a ton of space

Section 1

  • The marquee section of the homepage page exists here. This should be one line that is both actionable and explanatory in one sentence (work with Jenn T. on this copy). Essentially the text should say something about criminal justice data sets live here and you can search for ________ anything. This line is similar to what slack has done on their homepage, where it encourages the user to fill in the blank. Kind of like Mad Libs. With type treatment, it should be clear they can type in this area and they'll see key words or states rotate, simultaneously showing them what they can search for. This should not be a search both, rather a blank line to fill in.

Section 2

  • This section has 4 areas that are illustrated offering other types of data sets the user can search for and simultaneously telling the entire story of the CJ system.
  • The four areas featured are: Arrest, Courts, Corrections and Re-entry.
  • Below these will be 2-3 links offering the most popular topics within those areas.
  • This section operates as quick links to learn the type of data they can search for and help appeal to all audiences

Section 3

  • One or two sentences describing the importance of transparency in CJ data
  • We also talked about a quote from a reputable source

Section 4

  • This is an interactive map of the United States of America
  • the user should be able to scroll and click points on the map to bring them to a search results page of the state they click on
  • this area also simultaneously serves as a description of the data sets and that you can search by state and engages the user

Section 5

  • This is where you can learn more about the policy briefs and blog posts
  • a designer needs to solve how this section should work, should there be a list of posts that bring you to the About page where you can read more? Should you be able to download a few briefs from this area? What is the most effective use of this area?
@beccasjames
Copy link
Contributor

Nikki,

Just saw this! This is what I was thinking about regarding adding more explanatory documentation. My bad.

-Becca

On Sep 17, 2015, at 1:24 PM, Nikki Grad [email protected] wrote:

https://cloud.githubusercontent.com/assets/10213169/9940328/22f4374e-5d3d-11e5-9eb6-6f306c22b349.jpg
Header menu

Index - a button that brings the user to a page that has a list of all the data sets collected, truly an index page, @crdunwel https://github.com/crdunwel had this idea.
About - this page will create context for the project, tell the story of what we're doing here at Sunlight and most importantly house all Policy Briefs and Blog posts associated with the grant. We do not want to send users back to sf.com to read these briefs and it is grant required that they live with the tool. They should be downloadable by PDF to stay concise and easy to read without taking up a ton of space
Section 1

The marquee section of the homepage page exists here. This should be one line that is both actionable and explanatory in one sentence (work with Jenn T. on this copy). Essentially the text should say something about criminal justice data sets live here and you can search for ________ anything. This line is similar to what slack has done on their homepage, where it encourages the user to fill in the blank. Kind of like Mad Libs. With type treatment, it should be clear they can type in this area and they'll see key words or states rotate, simultaneously showing them what they can search for. This should not be a search both, rather a blank line to fill in.
Section 2

This section has 4 areas that are illustrated offering other types of data sets the user can search for and simultaneously telling the entire story of the CJ system.
The four areas featured are: Arrest, Courts, Corrections and Re-entry.
Below these will be 2-3 links offering the most popular topics within those areas.
This section operates as quick links to learn the type of data they can search for and help appeal to all audiences
Section 3

One or two sentences describing the importance of transparency in CJ data
We also talked about a quote from a reputable source
Section 4

This is an interactive map of the United States of America
the user should be able to scroll and click points on the map to bring them to a search results page of the state they click on
this area also simultaneously serves as a description of the data sets and that you can search by state and engages the user
Section 5

This is where you can learn more about the policy briefs and blog posts
a designer needs to solve how this section should work, should there be a list of posts that bring you to the About page where you can read more? Should you be able to download a few briefs from this area? What is the most effective use of this area?

Reply to this email directly or view it on GitHub #38.

@ngrad
Copy link
Contributor Author

ngrad commented Sep 17, 2015

@beccasjames no worries :) It was good you said something, I have more notes to share than this. Getting them in issues right now.

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

No branches or pull requests

2 participants