-
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
Design Election Cycle Summary pages #3816
Comments
Breakdown of pages we need to account for in this work: Campaign finance statistics: Election cycle page: (Do we still need these? Is it important that we link to press releases still? Perhaps we can find a new home for them? Maybe on the page listed below?) X-Month Candidate or committee page: @AmyKort @dorothyyeager Please advise if there's anything I'm missing. |
I agree with your breakdown @JonellaCulmer - we do need to link these to press releases though (or have a conversation with press about eliminating those). The election cycle page is sort of the table of contents for the election cycle, so it would be the point of entry for someone wanting access to all of the statistics from a cycle. |
Per a discussion on these pages: (cc: @AmyKort @dorothyyeager @patphongs)
|
@AmyKort @dorothyyeager We call these chunks of data different things. I think we need to come to a decision on what to call these moving forward. And hopefully reduce this list down to one.
There's also: Congressional candidates and Campaign summary tables. When we move these pages over I think we need to try to reduce this list down to one or two names. |
Thank you @JonellaCulmer ! |
Thanks @JonellaCulmer, I have one note about these mock ups. I'm wondering what the importance of the "Published date" column is in the filtered table view. We did not give these dates in the HTML view on transition, so I'm wondering if the start and end dates would be more useful for these reports. |
@patphongs Great point. I included them on the preliminary mockup but I'm really hoping to get from the Press Office an idea of what is most important at this stage and hopefully get a list from them of people (or groups of people) whom they think would be appropriate to user test. |
A meeting with the Press Office has been scheduled for Friday. Moving this to blocked while we wait for that discussion and resulting takeaways. |
Other resource to track: https://www.fec.gov/campaign-finance-data/presidential-campaign-finance-summaries/ Need to consider how we can include this information into the presidential page. |
@JonellaCulmer I've set up a prototype for the congressional data summary table on feature. I attempted to put all the data in one page, but it was too much HTML to insert into one page as I got an error. So we'll split them up by Summary table type. |
After incorporating feedback from the Press office. Below are the mock-ups with which we are moving forward. Here is the approved content and other details needs for this project: Main navCampaign finance statistics browse data pageCampaign finance statistics summary pageData table pagesArchived campaign finance statistics page |
Closing in favor of:
|
Summary
What we are after:
The election cycle summaries produced by the Press Office are still on transition and because we want to get off transition, they would like to put them into Wagtail, starting with the home page.
Page to bring over: https://transition.fec.gov/press/campaign_finance_statistics.shtml (main page) and https://transition.fec.gov/press/summaries/2020/ElectionCycle/2020DataTitle.shtml (example for a cycle) but that page links to many other transition pages. We may want to have @JonellaCulmer take a look at the best way to bring these summaries over and then plan for that work in PI13 because the next deadline for these pages is August.
Completion criteria
Tech steps or considerations (optional)
We want to keep it simple and make sure that the Press Office will be able to use the new pages going forward.
Future work
Other future work that may be needed following this issue's completion.
The text was updated successfully, but these errors were encountered: