-
Notifications
You must be signed in to change notification settings - Fork 40
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
QA press release and weekly digest content #488
Comments
If this becomes an all hands on deck situation (depending on how much we need to review and the turnaround time), I can shift content focus and devote most of my time to review. |
Ok, as I'm beginning to do this work, I'm finding some style things we should decide.
https://beta.fec.gov/updates/week-of-september-5-september-9-2016/ Here's an example of a page that I cleaned up: https://beta.fec.gov/updates/week-of-september-5-september-9-2016/ And here's the default imported style: https://beta.fec.gov/updates/week-of-august-29-september-2-2016/ |
Definitely I agree that headings should be sentence case. Bolding terms can be useful to users when it underscores important words and phrases. In this case, it doesn't feel very useful to have very similar dates as the only thing in bold. Mostly, the bold feels like a way of highlighting where one event ends and another begins. In which case I do think a list would do that equally well.
versus
As to whether a list or bold is the right visual styling, I'll defer to @jenniferthibault and say that my preference is for list. |
That makes sense to me. I think I prefer bullets in those instances. What about with stuff like this, though (page) A lot of content in the digests is essentially lists. Should they all be bulleted? |
I'm totally ok with bullets being the default format for lists. I'm seeing a distinction though that may be helpful. Advisory opinions and Audits seem to have a document title with a full explanatory paragraph beneath. In these cases, I think setting each off with the title as an That means the list/paragraph choice is determined by category: Commission meetings:
Advisory opinions: Enforcement:
Alternative dispute resolution
Audits: Litigation:
Outreach:
Educational programs:
Press releases:
Campaign finance reports:
Upcoming commission meetings and hearings:
Upcoming educational programs:
Upcoming reporting due dates:
Disclosure initiatives:
Additional research materials: While I did this, I noticed something weird. There seem to be duplicate/redundant categories:
Is this something we want to get into now? |
I never responded, but I really like these suggestions. My only issue is that sometimes the category content varies from week to week. Sometimes a category that you identified as a bullet style either only has one item or it has several rather lengthy items. Do we want to bullets in this case? I finished all of the 2016 press releases and have done several weekly digests. The digests are definitely more time consuming. They take about 5 minutes each (compared to just 2 for the press releases), and there's about 45 left, which means 3.5-4 hours of work to get through 2016. Before we invest all that time, I'd like to run our suggested formatting by the press office to make sure they agree with our choice of bullets, headings, etc., and with our partners to make sure they want us to spend that time cleaning up prior digests. |
I finished making the 2016 Weekly Digests consistent. For a next step, I created an issue to make a formatting guide for these documents so that it's easy to keep them consistent (and in some cases improve existing formatting decisions) in the future. 18F/fec-style#544 |
All 2016 press releases done too! |
Thank you! Closing. |
In order for all imported content to look as good as possible, do a QA process of all imported press release and weekly digest content and publish.
Tasks:
The text was updated successfully, but these errors were encountered: