Pretty excited to read through this source code, I've been quite curious about how RSC works underneath the covers.

I feel like the missing piece of DX is making intellisense aware of the custom properties in a project automagically🪄

I'm ready for CSS Modules to make a comeback.

As apps grow, the permutations of styles are effectively infinite. Compiling to atomic classes means CSS output grows logarithmically rather than linearly.

Atomic/Utility/Functional CSS is basically assembly for presentation so it's always cool to see libraries treat it as a compile target. https://t.co/Nq2OxpuuCs

I'm that broken record at work that always says "this should be a state machine", so always delighted to see xstate iterate.

I'm back, did I miss anything?

Get ready for a whole new type of design workflow. Just released folders and component hot swapping for Studio Pro users. Write your content once and then quickly cycle through any component in the current folder to rapidly explore design options🤤

📈 A collection of components growing by the day!

My favorite part about these themes/templates is you'll be able to customize the HTML+CSS without writing any code.

Contrast threshold is now used as a constraint. Choose a color or background color and quickly cycle through accessible options from your theme.

✍️ Working on text editing directly in the @components_ai canvas. The first pass is rolling with some vanilla contenteditable=true magic. In the future we'll likely iterate and add full-fledged rich text editing (via Slate).

This'll be particularly useful for applying styles to MD(X) documents and user-provided content.

Currently working on targeting nested elements in CSS GUI so you can have a Content/Prose component to apply child styles. Here I'm styling nested links (some UX improvements to make still):

And a big thanks to @hturan for doing a lot of heavy lifting with the HTML imports! Our next step will be connecting HTML DOM nodes with any embedded styles, but that's a really hard problem. So this is our first baby step : )

Meanwhile, the HTML/hyperscript AST representation lets us serialize (somewhat) simply to a lot of web-based frameworks since they're fundamentally HTML/JSX with JS sprinkled in with their own syntactic sugar for props and interactive bindings.

The data structure we have for CSS lets us serialize the styles in different ways. Whether that's compiling it using a CSS-in-JS runtime, serializing it to a CSS prop with theme bindings, or eventually serializing to utility/functional CSS. A styles serialization "demux".

Interestingly, we have what's effectively an embedded AST for styles/CSS inside an HTML-like AST. Similarly to how MDX is a Markdown AST with JSX in it.

Kinda wild, but not surprising, how much compiler stuff has been involved with this project. Parsing, transforming, transforming again, serializing to any number of formats. Fun stuff!

Implemented HTML+Markdown imports for CSS GUI. Added a sneaky nicety where if you have Markdown in the input and switch the format to HTML - it'll convert it. HTML => MD => HTML ➿