Are token updates outside of the scope of maintenance mode?

[HarmfulBreeze]

Hi!

As a M3 fan and user of material-web, I was wondering if token updates are on the table?
I use material-web's token set in one of my projects and I've noticed that v0.192 is a pretty old version and many improvements to the design system were done since then.

Many thanks :)
Léane

[asyncliz]

Generating new token versions may be possible! Upgrading the components to use the new tokens might be trickier depending on the migrations needed.

I'll take a look :)

[asyncliz]

(it's more complicated now, but I'm still investigating in my free time 🥲)

[HarmfulBreeze]

Thank you very much for checking :)

[HarmfulBreeze]

@asyncliz friendly bump!

[asyncliz]

Thank you for the bump! <3

It was indeed very difficult to try and update tokens to even v1.0, let alone any of the later versions. One of the challenges I'm considering is determining what version to generate. Is it useful to generate the latest version of tokens if there's a significant change to many token set schemas and values?

To help give me context, could you describe how you're using tokens today? Are you integrating them into your own components and styles, or primarily using them as-consumed by the <md-*> elements? How useful would new versions of tokens be without updating MWC's elements to use them?

---

There are some meta questions that token updates would raise for this project as well. Is it valuable to have @material/web/tokens infra an offering independent of the components? What sort of expectation of maintenance and future updates would that put on the team?

[HarmfulBreeze]

Thanks for looking into it.

I work on my free time on a theme [1] for Obsidian, a note-taking app. I don't want to use Material Web components as I want this to remain CSS-only as long as possible, but I do make use of SCSS, @material/web/tokens, and @material/web/color (just for the theme mixin, I could probably do without color).

I also have to directly access some token values for components that haven't been implemented so far, such as search bars and bottom sheets, through @use 'pkg:@material/web/tokens/v0_192/md-comp-X' declarations. Access to all tokens, and not just for components that have been implemented in material-web, is invaluable to my project.

Considering I would like to keep my theme as faithful to the latest guidelines as possible, I would definitely leverage the latest tokens, especially if they are as easily available.

Hope this clarifies :)

---

[1] https://github.com/HarmfulBreeze/obsidian-material-3-theme