Skip to content
This repository has been archived by the owner on Dec 23, 2017. It is now read-only.

Wireframe new cycle behavior #801

Closed
noahmanger opened this issue Oct 2, 2015 · 7 comments
Closed

Wireframe new cycle behavior #801

noahmanger opened this issue Oct 2, 2015 · 7 comments
Assignees

Comments

@noahmanger
Copy link
Contributor

Wireframe a solution to allow users to easily view Presidential and Senate financial summaries for the full 4 or 6 year cycle, respectively, while also allowing them to view the traditional 2-year periods.

Decisions to make / questions to address:

  • Does this advanced select only live on candidate pages? Or also their committee principal committee pages?
  • How does this work with adjusting years on election pages?
  • How does it balance the two methods we have for traversing time: choosing an election year and adjusting the date range for data viewed?
@noahmanger
Copy link
Contributor Author

I've got wireframes for different approaches to this new time period select on InVision, as well as how it would work on candidate and election pages: https://invis.io/RE4GG62GB

After discussing with the team today, we're leaning towards going with Option A of a <select> with <optgroup>s to group two-year periods for each election year.

But the plan is to test that against one or two of the other options as static prototypes this week. If this approach works, it's definitely simpler to implement. But I'm a little concerned it may be confusing, so it will be good to test.

Happy to walk through these more over video call on Wednesday if it's helpful.

@PaulClark2
Copy link

For the beta release we'll need to modify Option A so that for a Senate candidate the drop down menu would look like the one below. This should be the first option users are presented. The default would be to the current full cycle. We should include as many other options as the teams decide is useful to present to users.

    **Full Cycle 2012**
    2011-2012
    2009-2010
    2007-2008
    **Full Cycle 2006**
    2005-2006
    2003-2004
    2001-2002

@wluoFEC @AmyKort @jwchumley @amypike

#821

@noahmanger
Copy link
Contributor Author

Just to clarify: are you saying for the release we need to implement this or simply update the wireframes to reflect this?

Second, are you saying that we don't include an option for "All: 2011 - 2016" and you want to use "Full Cycle 2016" to choose that time period?

@AmyKort
Copy link

AmyKort commented Oct 10, 2015

Just update the wireframe to reflect this. And, yes, please go with the "Full Cycle 2016" language instead of the All: 2011 - 2016 language. The Full Cycle option is the 2011 - 2016 range. @PaulClark2 = cc

@AmyKort
Copy link

AmyKort commented Oct 10, 2015

Also, Thank You!

@PaulClark2
Copy link

You're welcome Amy. Again sorry I wasn't clear @noahmanger . Like @AmyKort said we don't need to implement this we just need something folks can comment on.

@noahmanger
Copy link
Contributor Author

This is resolved.

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

4 participants