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

Prototype: State profile pages #1347

Closed
meiqimichelle opened this issue Mar 28, 2016 · 8 comments
Closed

Prototype: State profile pages #1347

meiqimichelle opened this issue Mar 28, 2016 · 8 comments

Comments

@meiqimichelle
Copy link
Contributor

meiqimichelle commented Mar 28, 2016

This will come from #1334.

@shawnbot
Copy link
Contributor

shawnbot commented Apr 4, 2016

The next step is to generate pages for each state that list out data for the following metrics:

  • Federal revenue
  • Federal production
  • All lands production
  • Jobs (economic impact)

This should provide us with some useful input for the wireframing process, since it will show us, for instance, how many products we will need to show under each section for a particular state or offshore area.

@meiqimichelle
Copy link
Contributor Author

Notes doc

@meiqimichelle
Copy link
Contributor Author

Newer, better start of wires here (that's a google drive doc, limited access), based on Shawn's prototypes (example with Utah data here ).

@shawnbot
Copy link
Contributor

shawnbot commented May 9, 2016

@meiqimichelle in the spirit of the chat we had at the IRL about when wireframing is appropriate, I'm considering renaming this to a prototyping exercise. What say you?

@shawnbot shawnbot changed the title Wireframes: State profile pages Prototype: State profile pages May 12, 2016
@coreycaitlin
Copy link
Contributor

coreycaitlin commented May 12, 2016

@shawnbot: running list of content issues to refine/revisit —

  • "Geothermal" probably needs to be "Geothermal energy" to make sentences work
  • "Hardrock" should be "hardrock minerals" to make sense
  • NGL should be "natural gas liquids"
  • Oil and Gas (Non-royalty): "produce" is the wrong verb here. If possible, could we specify that this revenue is to "secure rights or explore for" oil and gas?
  • "co2" should be "carbon dioxide," and we should figure out what that means

@coreycaitlin
Copy link
Contributor

^^ this fix starts fixing these! It'll take another pass through the page to make sure they're all making sense, but they're way better now, thanks to @shawnbot.

@meiqimichelle
Copy link
Contributor Author

@coreycaitlin should this issue be closed?

@coreycaitlin
Copy link
Contributor

👍 sounds good to me!

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

3 participants