3

I noticed that the Steppers Component are now under 'Archived' instead of with the 'Active' guidelines. See https://material.io/archive/guidelines/components/steppers.html (July 2019).

Does anybody know why they are phased out? Poor usability? Or are there rumours that they will they be replaced with a similar component?

Thanks!

1

The Stepper Component is not literally archived, the website your are looking is.

Google introduced a new version of material.io website in May 2018 with less components description but kept online former versions of the specifications as you can see here : https://material.io/archive/guidelines/

You can find more about this May 2018 update in the Google Design Blog Post "Making More with Material"

All current specified components of the new update are now linked to a technical implementation. The stepper component was indeed specified but never technically implemented as part of the MD web components, take a look at this GitHub Issue from October.

Keep in mind that Google Material Design specifications and components are constantly evolving, while it seems MD started as broad guidelines, I have now the feeling that the project is really becoming a component library.

| improve this answer | |
  • Awesome, thanks a lot for the link to the article. It mostly speaks about theming though, not about phasing out components :) – Sijme Mar 30 at 11:33
  • 1
    Hence, I'm still confused as to why it is archived. The material.io Stepper guideline page now even throws a 404, while in reality we still need a wizard-like component in our UX work. material.io/archive/guidelines/components/steppers.html – Sijme Mar 30 at 11:36
  • Also, Frameworks like Angular still support the Stepper: material.angular.io/components/stepper/overview – Sijme Mar 30 at 11:37
  • [QUOTE](...) while it seems MD started as broad guidelines, I have now the feeling that the project is really becoming a component library[/QUOTE] True, but I think this is desirable given the widespread audience. A better approach for them would have been to keep guidelines on UX and Code together, to prevent the two from living their own live (and hence deviating too much). See 'Architecting the Component Page' in this article as to why: medium.com/eightshapes-llc/documenting-components-9fe59b80c015 – Sijme Mar 30 at 11:39
  • Finally: sorry for the bunch of comments. Apparently, I can't add line breaks / text formatting in here :) – Sijme Mar 30 at 11:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.