The community members are discussing the desire for a component-oriented layout that would allow them to work on libraries in isolation, similar to how Figma users work. They also express interest in the ability to implement a library like Tailwind natively, with the potential benefit of being managed by owners rather than the community. The comments further clarify the concept of a "component-oriented layout", suggesting a setup where components can be easily reused and edited in one place, solving the issue of manually updating multiple instances of the same component. The community members indicate that this is something they are aware of and are working to address.
I would die for a component oriented layout so we can work on libraries in isolation. Figma users works this ways and i would die for something similar. Also it could be awesome to be able to implement a library like tailwind natively. Such framework might get benefit by being managed by owners instead of community (webflow...) i guess in term of maintanability.
As you know I'm also a tailwind fan. But it becomes cumbersome when you need to manually update a class (or token) on 182 instances of a card that was reused on every page. Each card design is the same but holds different content (text/image).
Being able to edit the "master component" in one place solves this.
yes, tailwind or any functional tokens structure means there are many tokens on each element and now you need a bigger something that allows you to reuse them together - components
I am not sure if thats what @Ludovic meant but if thats it then we are absolutely aware and user components / visual components is the thing that is going to solve this.
Yup, this is partly what i meant. By "component oriented layout" i mean, a space where you could scroll trough library or custom components. I often see two way of creating components : Either like webflow today, where a custom component is made by the user trough his page by transforming a whole Div into a component for example. Or more like Codux, where a component is made in isolation. This is quite friendly for those working with storybook too which is a good practice for scaling up a project.
