iiinova — where your digital self keeps evolving

sugarcube.sh @sugarcube.sh · 11/09/2026

👀 Show us when you're done?!?

102

sugarcube.sh @sugarcube.sh · 02/09/2026

I know of at least one mid-sized company, though their DS isn't public. Trying to do some convincing? 😅

120

sugarcube.sh @sugarcube.sh · 20/08/2026

sc also has the concept of 'recipes' now, which negates some of the annoyance of manually writing out each individual token: sugarcube.sh/docs/fluid-s... Not that that solves all of the specific problems Scott is talking about or anything. But a lot more is coming in future releases.

170

Reposted by @sugarcube.sh

Mark Tomlinson @marktomlinson.dev · 12/08/2026

Added a blog to @sugarcube.sh so I can write about things like releases without just linking you out to the boring docs. First post up: O̶n̶e̶ ̶H̶u̶n̶d̶r̶e̶d̶ ̶Y̶e̶a̶r̶s̶ ̶o̶f̶ ̶S̶o̶l̶i̶t̶u̶d̶e̶ Two Years of Sugarcube

sugarcube.sh

Two Years of Sugarcube

Looking back on the past two years of sugarcube, the people who have helped shape it, and what’s next.

1113

Reposted by @sugarcube.sh

Mark Tomlinson @marktomlinson.dev · 21/07/2026

Using @sugarcube.sh to lint @sugarcube.sh 🫣

101

Reposted by @sugarcube.sh

Mark Tomlinson @marktomlinson.dev · 26/06/2026

Ever wanted @sugarcube.sh to NOT generate custom properties for certain tokens - e.g.primitives that have no business in your actual code? Well, now you can control that! Read all about private sets below. And thanks to @alex.unapologetic.io for requesting this feature.

sugarcube.sh

Resolver Document

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

1132

sugarcube.sh @sugarcube.sh · 22/06/2026

"I think we’ll be seeing more and more thinking about how design system information is structured, categorized, and linked in the years ahead." Absolutely.

010

Reposted by @sugarcube.sh

Mark Tomlinson @marktomlinson.dev · 15/06/2026

Can't wait til I finish some of these new features. They've been a while in the works. Especially excited about commands like this one that will help you understand your token graph better. And (eventually) make changes to consumers directly.

041

Reposted by @sugarcube.sh

Markus Finell @finell.dev · 11/06/2026

Current personal project: WordPress starter theme using @sugarcube.sh, combined with a custom block plugin "Every Layout Blocks". Could be a solid setup for building pages! #everylayout #wordpress #webdev

231

sugarcube.sh @sugarcube.sh · 12/06/2026

Yes, yes, yes! I haven't forgotten about the plugin convo we had either. Let me know if sugarcube can be helping more on that side of things.

210

Reposted by @sugarcube.sh

Mike Jeffery @mikejeff.com · 09/06/2026

I'm growing ever more slack-jawed with amazement and wonder as I read through these docs. The fluid typography scale recipes? WOWZA! Really well done, @marktomlinson.dev sugarcube.sh/docs/fluid-s...

sugarcube.sh

Fluid Space & Type

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

171

Reposted by @sugarcube.sh

Andy Bell @bell.bz · 25/05/2026

From the archives: We’ve started a new project which requires heavy, creative theming, so I made a prototype to test some ideas out. piccalil.li/blog/how-wer...

piccalil.li

How we’re approaching theming with modern CSS

We’ve started a new project which requires heavy, creative theming, so I made a prototype to test some ideas out.

0131

Reposted by @sugarcube.sh

Mark Tomlinson @marktomlinson.dev · 22/05/2026

Forgot to mention: this shipped in @sugarcube.sh last week! No more back-and-forth between sugarcube and utopia.fyi. Thanks to @arpit.codes for helping push me to actually implement this. Check out the fluid space & type docs for more:

sugarcube.sh

Fluid Space & Type

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

4227

Reposted by @sugarcube.sh

Scott Riley @scott.is · 21/05/2026

framework-specific component libraries are wild. web components are fucking fab. in this post i walk through creating a framework-agnostic, docs-first design system setup using web standards (and @arielsalminen.com’s wonderful elena). piccalil.li/blog/framewo...

piccalil.li

Framework-agnostic design systems: a practical approach to web components

Baking framework lock-in into your design system from day one is a recipe for obsolescence. Component documentation is often tedious and out-of-sync with development. Let’s build a documentation-first...

56411

Reposted by @sugarcube.sh

earthwhile @earthwhile.xyz · 28/04/2026

We’re trying out @sugarcube.sh for a new project and loving it so far. It’s also making us realise just how dependent we’d become on @tailwindcss.com.

151

Reposted by @sugarcube.sh

Mark Tomlinson @marktomlinson.dev · 24/04/2026

I know it's totally unimpressive and all bots or whatever but that 1k still means a lot to me. Thanks to everyone who has shown interest in, or tried out, @sugarcube.sh so far. I'm working on some demos/educational material as well as a roadmap and some exciting new features at the moment.

Screenshot showing @sugarcube-sh/core package having reached 1k downloads.

1304

sugarcube.sh @sugarcube.sh · 02/04/2026

As always, DMs or GitHub issues/discussions open. Don't forget to check out the docs, too, if you need them. sugarcube.sh

sugarcube.sh

sugarcube

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

010

sugarcube.sh @sugarcube.sh · 02/04/2026

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 ⬇️

github.com

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 ...

232

sugarcube.sh @sugarcube.sh · 10/03/2026

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

010

sugarcube.sh @sugarcube.sh · 10/03/2026

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

010

sugarcube.sh @sugarcube.sh · 10/03/2026

Yep yep yep. We could do:

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

100

sugarcube.sh @sugarcube.sh · 10/03/2026

👀 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?

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.

200

sugarcube.sh @sugarcube.sh · 06/03/2026

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...

sugarcube.sh

CSS Utilities

120

sugarcube.sh @sugarcube.sh · 06/03/2026

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.

110

sugarcube.sh @sugarcube.sh · 06/03/2026

😂 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!

110

sugarcube.sh @sugarcube.sh · 27/02/2026

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.

010

Reposted by @sugarcube.sh

Andy Bell @bell.bz · 26/02/2026

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.

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.

2541

sugarcube.sh @sugarcube.sh · 25/02/2026

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

010

sugarcube.sh @sugarcube.sh · 24/02/2026

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 :)

sugarcube.sh

sugarcube

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

2395