Week of April 5, 2026 https://designsystems.news/#week-2026-4-5

💜💜💜

sugarcube Design tokens, generated CSS, and optional components. Build front ends on strong, reusable foundations.

As always, DMs or GitHub issues/discussions open.

Don't forget to check out the docs, too, if you need them.

sugarcube.sh

Release @sugarcube-sh/core@0.2.0 · sugarcube-sh/sugarcube Minor Changes c4fec95: ### Permutations API Thanks @aarongeorge for the feature request! A new DTCG-aligned permutations API for multi-brand and multi-theme CSS builds. Each permutation declares ...

No Easter eggs but plenty of sweetness in the latest sugarcube release!

- Full DTCG compliance (including fancy `$extends`)
- Permutations API for for multi-brand builds and extra control over output in general
- Cleaner config schema

Migration guide for the config in the release notes ⬇️

Agreed. They are two separate features. Safelist support as a general concept, and a WP plugin specifically.

Absolutely. Plugins are something I've been considering and a wp one would be a great idea.

Sugarcube utility config showing two prefixes for the same CSS property - 'bg' for normal usage and 'wp-preset-background-color' with safelist enabled for WordPress integration

Yep yep yep. We could do:

Screenshot of IDE with proposed sugarcube utility config, in particular, showing the addition of a safelist property as a solution to the question of generating some utility classes regardless of whether they are used in markup or not.

👀 It is not currently possible but something I'd definitely be open to exploring.

Maybe something like this?

Tell me more about your use case. Would you need non-token-based utility classes on the safelist as well?

Example sugarcube utilities config Example sugarcube utilities config . GitHub Gist: instantly share code, notes, and snippets.

In case it helps, here's the typical utils config I rock with in most of my projects: gist.github.com/mark-tomlins...

Good question!

All of them need to be defined in the config because sugarcube can't know in advance which CSS property you want.

If you want utils that are not token-based (e.g. `.absolute`), you can extend sugarcube with a unocss preset like this:

sugarcube.sh/docs/utiliti...

You're not the first person to have run into that! And even I've been like 'hey where's my utils' a couple of times 🤣.

That is certainly high praise - thank you. And thanks for using it.

😂 Let's help you the old fashioned way!

1. `npx @sugarcube-sh/cli init` to get you setup
2. `npx sugarcube generate` to generate your styles
3. Import the generated CSS files wherever you import the rest of your styles.

Let me know if that gets you sorted!

Appreciate it, Jesse. When I was designing this, CSS-first was one of about four non-negotiables. No proprietary syntax, no CSS-in-JS, none of it. Just CSS.

Your Personal Design Systems idea sounds great and not very far from what I'm trying to do here. Hope to see it.

A design system, titled "Set.studio: Pattern Library" with a sidebar of navigation, broken into design tokens, CSS, components and regions. The open pattern is the "BrandSlide", which shows a red slide, titled "Ready, set, go!". In the footer of the slide, it says "Design and development partnership proposal, February 2026", followed by next and previous slide links.

POV you've got a new major version of your internal design system software and @sugarcube.sh to test and a proposal to make.

CSS is the best design tool innit.

Thank you and right back at you: builtbyfield.com is so clean.

sugarcube Design tokens, generated CSS, and optional components. Build front ends on strong, reusable foundations.

Hello, world.

Sugarcube is now available for use.

sugarcube.sh

Check it out on GitHub

github.com/sugarcube-sh...

Or on @npmx.dev

npmx.dev/org/sugarcub...

Thanks for following along :)