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

Design strategy and content of About | Reports about the FEC section #677

Closed
2 of 3 tasks
Tracked by #60
jenniferthibault opened this issue Dec 19, 2016 · 13 comments
Closed
2 of 3 tasks
Tracked by #60

Comments

@jenniferthibault
Copy link
Contributor

jenniferthibault commented Dec 19, 2016

From high-level section flow in https://github.com/18F/fec-cms/issues/626#issuecomment-266852399

and conversation in https://github.com/18F/fec-cms/issues/626#issuecomment-267147474

  • Determine a definitive list of document categories , and which documents fall under each
  • Write necessary microcopy for each document category and/or landing page
  • Determine what bridges to build between this content and other parts of the site (cross-linking strategy)
@emileighoutlaw
Copy link
Contributor

Pasting some high-level notes from our earlier issue in here so we continue to track them:

  • Keep budget and strategy documents together
  • Possibly consider including gift reports and treasury reports here
  • Ensure FAIR Act and procurement reports stay are in the procurement and contracting card
  • A note to future Emileigh: I'm increasingly feeling like Plain Language, the Privacy Act Notices, and the FOIA information should be special snowflakes that exist in the footer (and are thus accessible from every page) but don't live elsewhere in the site structure).

@jenniferthibault
Copy link
Contributor Author

jenniferthibault commented Dec 19, 2016

On policy-like required info that may live in the footer, we have this placeholder issue that captures that general need, but isn't fleshed out: Figure out all the required things we need to link to on the home page #484

We could bring this out of the ice box if you think it's near-ready, @emileighoutlaw

@emileighoutlaw
Copy link
Contributor

You're right @jenniferthibault — it's probably near ready, which is why I keep doing the bad thing of making notes about it in other issues. 😞 Although we may need to wait one more sprint to take it out of the icebox, so we can guarantee we have some of Amy's time to help us sort through this.

@noahmanger noahmanger added this to the Sprint 4 milestone Dec 30, 2016
@jenniferthibault
Copy link
Contributor Author

For a quick refresher, here's where we left off with how this section could possibly be structured (thought the text is probably woefully out of date):

screen shot 2017-01-04 at 1 36 54 pm

screen shot 2017-01-04 at 1 37 02 pm

@emileighoutlaw
Copy link
Contributor

More content ready for @AmyKort to review. Document 🔒

Preview 😎
screen shot 2017-01-12 at 8 07 46 pm

@jenniferthibault
Copy link
Contributor Author

Here's what those would look like in the templates: Reports landing page on InVision | Document Category feed template on InVision

Previews
about-reports_v1
about-documentfeed

@noahmanger noahmanger modified the milestones: Sprint 5, Sprint 4 Jan 17, 2017
@noahmanger
Copy link

Just chiming in to say this all looks good to me.

@emileighoutlaw
Copy link
Contributor

Ping to @AmyKort and @amypike 😄 — how are we feeling about the content in this doc 🔒

@AmyKort
Copy link

AmyKort commented Jan 25, 2017

This looks okay to me. Do you think we could go forward with this as it is planned and then have a little bit of time to let the owners of those reports check out the descriptions before we go forward? I think it would be helpful to folks to see the whole section in context. What do you think @amypike ?

@amypike
Copy link

amypike commented Jan 25, 2017

I agree that it would be helpful for owners to see the whole section in context. This sounds like a great plan to me, @AmyKort. @emileighoutlaw One micro-copy change: In the FOIA section, can we change "record" to "records" so it reads "...records requests the FEC receives from the public?" Thank you!

@emileighoutlaw
Copy link
Contributor

Yep! We can definitely give folks time to review.

Amy Pike: Made that change! Sorry to have missed it in the first place. 💟

@emileighoutlaw
Copy link
Contributor

@jenniferthibault Are we ready to mark this issue as done?

@jenniferthibault
Copy link
Contributor Author

Yes!

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

5 participants