The community member asked if there is a way to make a group of elements reusable as a component with props/inputs. Another community member responded that there is no Components UI yet, but they can use Slots to keep everything in the slot in sync with each implementation, though it's static and doesn't support props. Another community member asked where they can read about Slots, and was provided a link to a blog post about Slots. A community member who is a fellow ex-CMS creator expressed interest in being able to quickly select a group of elements, extract them into a component, and parameterize them with inputs, as this would help with reusability and making the element tree more usable. The community members indicated that this feature is planned to be implemented soon.
I have a quick question. Is there a way to make a certain group of elements reusable and encapsulate it as a component, ideally with some props/inputs or something?
But you can use Slots which lets you keep everything in the slot in sync with each implementation of the slot. But it's static so yeah no props. Especially useful for headers and footers.
Okay, found this https://webstudio.is/blog/slot-component I guess your website is not super SEO-optimised yet, for some reason it didn't show up for "webstudio.is slots"
@Oleg Isonen hey, been following your progress on Twitter for a while and as a fellow ex-CMS creator myself I'm very impressed how far you've gone.
As I understand, your main idea about custom components is to have them implemented with code and not via UI.
While that is certainly needed as well, one use case I'm expecting is to be able to quickly select a group of elements in the tree, extract it into a component and parametrise it with some inputs.
Besides reusability, that would help with making the element tree more usable, right now there's just way too much stuff for a large page.
