First 'Internal Friday'
100 Days in a Row
Third Lunation
Second Successful Lunation
First Successful Lunation
Made the journal public

Design System Starter Kit

Build a library of flexible and un-styled components to start or supplement design system projects. Anyone can jump in the file below
229 entries
Started Apr 30, 2020

I’m still slowly turning components into variants…

I need to speed things up a bit. I’m presenting at a side project showcase zoom call and, although my presentation’s more about the process (work on it every day for ~30 days; post to FL), it would be good to have something ‘complete’ and shareable

More importantly, the sooner I can get his in front of people that can test it and give me feed back the better

Next steps

- Wrap up the transition to variants
- Make v1 of the color system and styles
- Add auto layout v3 features wherever it makes sense. (Auto layout v3 should be launching this month)
- Writ a ToC and readme
- Throw together a website, which will probably just be loose port of the ToC and readme
- Publish the file to the Community

More work on tables
- Headers for sortable columns need 3 states: Ascending, descending, and a default state that indicates they can be sorted.
- The page, frame, and any 'slash naming' determine what the assets panel looks like. Gotta keep things sane.

So here’s an instance where some things don’t slot perfectly into variants.

I have 2 properties: Day and Selected. Toggling Selected on, changes the Day property to Selected Day. Changing the Day property to anything other than Selected Day toggles the Selected property off

Nothing’s broken, but this doesn’t feel quite right.


I need to avoid making a ton of variants.

Here, instead of making "Label" and "Label + helper text" variants of text fields, textareas, and dropdowns, you can just instance swap what’s inside the "Label" and "Label + helper text" components.

We’ll see if this ends up being the best approach

norton Design System Starter Kit