In Webstudio, slot contents are identical between instances.
Any instance-unique contents within a slot need to come from a Resource or other variable.
This is very powerful, but for me there's at least one drawback. I'd love to have reusable page/component structures (Slots) that have portions of content (within the slot) that are:
- unique to the Slot instance
- and can be designed visually in Webstudio
- and may include native Webstudio components
Populating content within a slot via a Variable or Resource accomplishes #1.
Rich text, via Markdown and Content Embed, accomplishes #2. But editing is done via CMS or within the variable editor in Webstudio, not on-canvas as with ordinary components.
And unless I'm misunderstanding, #3 isn't possible within a slot.
So I'm wondering if there could be a component (an Anti-Slot? a Wormhole?) that serves as an exception to the repeatable contents of an ordinary Slot. Any contents inside this anti-slot could be composable
within the Webstudio visual UI as any normal hierarcy of components, and would be
unique to that particular Slot instance.
I made a little mockup of the idea in the screenshot. "Anti-slots" and content are green, within the purple slot content.
This would allow reusable structures defined by Slots, with optional unique elements inside them, but unlike doing so with Variables/CMS, everything could be visually designed with Webstudio.
I have no idea how crazy and/or difficult this idea would be to implement, but I imagine it might be really useful for:
- people who need easily reusable layouts but don't necessarily need/want a full CMS
- people who are using a CMS, but may not need/want every piece of content mapped to a content model in the CMS
