Slots feel like finally admitting real product work is messy. We need space to improvise. Code’s been composable forever. Design tools are just now catching up.
But freedom needs discipline. Clear purpose. Depth rules. Examples. Otherwise it’s just chaos in a prettier frame.
I'm excited about the native slots. The first thing I did when learning Figma was create a header component, a footer component, put those into a page component... and then went to put in the page-specific sections - but I couldn't! Maybe it's that I started out as a developer, but it was a big shocking. There are plenty of work-arounds but I'll be interested to see if this streamlines some things that I currently just avoid. You bring up some really important questions though. What will the 3rd party designers end up putting in those slots! Much like a CMS where you have to guard and ensure only the right things get tinkered with.
Excellent article Nathan, thanks for your clear overview!
This hit, Nathan.
Slots feel like finally admitting real product work is messy. We need space to improvise. Code’s been composable forever. Design tools are just now catching up.
But freedom needs discipline. Clear purpose. Depth rules. Examples. Otherwise it’s just chaos in a prettier frame.
Waiting for the design-to-code singularity within visual editors.
I'm excited about the native slots. The first thing I did when learning Figma was create a header component, a footer component, put those into a page component... and then went to put in the page-specific sections - but I couldn't! Maybe it's that I started out as a developer, but it was a big shocking. There are plenty of work-arounds but I'll be interested to see if this streamlines some things that I currently just avoid. You bring up some really important questions though. What will the 3rd party designers end up putting in those slots! Much like a CMS where you have to guard and ensure only the right things get tinkered with.