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

Multi-step nav #109

Closed
jrubenoff opened this issue Jul 4, 2015 · 3 comments
Closed

Multi-step nav #109

jrubenoff opened this issue Jul 4, 2015 · 3 comments

Comments

@jrubenoff
Copy link
Contributor

We have a few different components for multi-step navigation. Screendoor's wizard checklist lets you navigate to any step:

screen shot 2015-07-06 at 10 46 47 am

I dislike this component because it takes up a lot of horizontal space. Also, the "checked" status is meaningless. Just because you visited a page, filled something out on that page, or even filled out everything doesn't mean you're done with it.

(For example, you could have a rough draft of a Screendoor project description, and the checklist would still mark it as "done".)

Screendoor's bottom status bar lets you navigate to the previous / next page:

screen shot 2015-07-03 at 7 35 21 pm

The tabs currently in the style guide are great if you don't have to go through each step in order:

screen shot 2015-07-03 at 7 37 28 pm

And for some flows, like when sending a message or importing responses in Screendoor, we have no components.

We probably need to come up with a few different patterns. I was thinking about switching to respondent view-style pagination for the wizard. Something like:

screen shot 2015-07-03 at 7 42 30 pm

But this wouldn't work for a linear flow like importing responses, where it doesn't make sense to jump around between steps.

@ajb
Copy link
Contributor

ajb commented Jul 5, 2015

(I think your first screenshot is not the right one.)

Also, the "checked" status is meaningless. Just because you visited a page, filled something out on that page, or even filled out everything doesn't mean you're done with it.

I agree. A contract designer added it in ~2 years ago, and it's never made any sense to me.

I was thinking about switching to respondent view-style pagination for the wizard.

I'm not so sure this is a good idea. By hiding the nav items under a dropdown, we're expecting the user to know what those items are. (As well as increasing the number of clicks required to navigate to one of those items.)

Imagine a user who's not very familiar with Screendoor knows that they need to add a new form field to their project. I think having all of the wizard steps visible makes this a lot easier than if they're hidden in a dropdown.

Anyway, I'm definitely in favor of adding a new component; in fact, this is what I had in mind when I opened #55. I'll go ahead and close it now since I never really added a good enough description.

@jrubenoff
Copy link
Contributor Author

Fixed the screenshot above. And yeah, not pushing for a specific solution, just jotting my thoughts down for reference.

In response to your concerns (again, not pushing for this, just writing down my thoughts), the dropdown makes the most sense if people are progressing through the wizard in a linear fashion, which they'll probably do the first time around, at least.

@jrubenoff
Copy link
Contributor Author

Closing in favor of #242

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

2 participants