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

Progress Indicator #2

Closed
rowanmanning opened this issue Aug 31, 2018 · 3 comments
Closed

Progress Indicator #2

rowanmanning opened this issue Aug 31, 2018 · 3 comments
Assignees

Comments

@rowanmanning
Copy link
Member

rowanmanning commented Aug 31, 2018

What

A progress indicator is used to display a user's progress through a multi-step process. This could be a multi-page form, a contract renewal process, or similar. This is distinct from the deprecated o-progress component in that it has a fixed number of steps and each step can have different state.

Naming: this could also be called a "progress tracker", or "stepped progress".

Why

This component has been designed separately (but very similarly) by two different teams on FT.com and Internal Products. After speaking with the designers it's clear that the use-cases are similar enough for it to be one component.

This is also a component that's present across the web, and so should be familiar to users. There are lots of good examples in this article.

Supporting Examples

I've attached examples of designs. These may change slightly, but there are a lot of similarities.

Designs for FT.com:

screen shot 2018-08-31 at 15 35 51

Designs for Internal Products:

screen shot 2018-08-31 at 15 14 31

screen shot 2018-08-31 at 15 14 59

screen shot 2018-08-31 at 15 15 15

Thinking So Far

  • We need to support both Master and Internal brands
  • Steps are always evenly distributed. Might this ever not be the case?
  • Steps have the states: Completed, In Progress, Next, Error, Green tick (?)
  • Steps are optionally clickable
  • Step Labels can have text and links
  • Between-Step Lines have the states: Completed, Next
  • Current progress can be between steps (in which case a non-dismissible tooltip is required)
@JakeChampion
Copy link
Contributor

There are less states than those listed in the original post.

Steps have the states: Completed, In Progress, Next, Error, Green tick (?)

Green tick (?) looks to be equivalent to In Progress, I'm not sure if that is the case though.


If we use this picture as the example:
image
What happens if the user goes back to the previous step labelled Details? Does the partially filled out step Preferences get a different design or is it the same as In Progress?


Current progress can be between steps (in which case a non-dismissible tooltip is required)

Are the positions between the steps going to be configurable? The designs show the non-dismissible tooltip to be in one of two locations, could it be in more than that?

@rowanmanning
Copy link
Member Author

Green tick (?) looks to be equivalent to In Progress, I'm not sure if that is the case though.

I spoke with Olga about the error and green tick, and it's a shorter term state to highlight that a thing was completed recently. The green would go away after a short amount of time. So it's kind of a "recently completed" state.


What happens if the user goes back to the previous step labelled Details? Does the partially filled out step Preferences get a different design or is it the same as In Progress?

I think that's a good question for design. I'll get them involved.


Are the positions between the steps going to be configurable? The designs show the non-dismissible tooltip to be in one of two locations, could it be in more than that?

In Olga's case, the "You are here" tooltip indicates how far along the timeline you are between the two points, so you can see how close to renewal you are. So the tooltip can be at any point between two steps, ideally configured as a percentage.

@draysonandstock
Copy link

draysonandstock commented Sep 24, 2018

Having had a brief look at this along with a slide component that Internal are after here is what I was looking at:

https://drive.google.com/open?id=1beM5bIEchNPSx6t3mv1yUDA_D78ccbkO

It was mainly basing the sizing off our existing radio buttons but changing the look slightly to better suggest they are interactive beyond just a selected/filled or not state.

slider and pagination

notlee pushed a commit that referenced this issue Mar 6, 2020
We now test each page with Pa11y before a build will pass.
notlee added a commit that referenced this issue Mar 6, 2020
chee pushed a commit that referenced this issue Sep 15, 2021
JakeChampion pushed a commit that referenced this issue Sep 17, 2021
Add micro explanatory message to the weird placeholder
chee pushed a commit that referenced this issue Sep 23, 2021
use origami-service-makefile and whitesource
chee pushed a commit that referenced this issue Sep 23, 2021
…-declarations

Allow `@include oGridRespondTo` after declarations.
notlee added a commit that referenced this issue Oct 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants