- Issue created by @heyyo
- ๐ง๐ชBelgium wim leers Ghent ๐ง๐ช๐ช๐บ
I donโt think this fits with @lauriiiโs product vision. This functionality is what he intends to cover with โElementsโ.
Designs that convey this clearly unfortunately donโt exist to my knowledge.
- ๐ซ๐ทFrance nod_ Lille
Can you point to documentation about "Elements" ? Curious about the requierments
- ๐ง๐ชBelgium wim leers Ghent ๐ง๐ช๐ช๐บ
#4 I was going to! :D
Product requirement
1.1 Elements
in the original product requirements, which states:As a creator, I want to add elements to pages using an intuitive interface, so that I can start creating content before having a defined design system. These elements may be later used to create new components.
No concrete issue exists for implementing these elements or which they should be. We only have tangentially related issues:
- relatively recently, ๐ [Needs design] Library confusingly lists SDC-sourced and Block-sourced Components together Active introduced the logic that determines which components belong in the "UI library"
- and ๐ Component should be allowed to use the reserved "Elements" category Active is where we need to clean up the original "implementation to reserve this for XB in the future": XB supported only SDCs back then, and we didn't want any SDC to declare itself to be an "Element", because that would clash with the future implementation of 1.1
- ๐ฎ๐ฑIsrael heyyo Jerusalem
Thank you for pointing me to this Elements future functionality.
But I don't understand how it's related to my issue ๐ค๐ ?
If I understood correctly, Elements will be the base of bigger components, like image, button, heading, vidรฉo...
But how the organization of the props in the generated form of my SDC ( here a slider) is related to those special components.
I'm trying to follow you but I'm lost ๐ - ๐บ๐ธUnited States Kristen Pol Santa Cruz, CA, USA
This may be of interest in this discussion as well:
โจ Allow component properties to be categorized Active