Hello, I’ve been learning weweb over the last couple of days and am working to create some elements/components that I’d like to eventually share on the marketplace.
From my understanding, to share a custom coded element (named custom component in the main dashboard, which I find confusing), I have to first include that element in a project, and then convert it into a component. A problem here is that all specific props for the element need to be remade and binded to the internal props of the element (unless I am mistaken, but this is what I picked up from https://www.youtube.com/watch?v=t309eaEXgJk). For a heavily modifiable element this could quickly turn into some pretty big overhead.
What’s the reason behind including only components, but not elements, in a library? As a quick example, the “Card” component included in the Starter Kit only exposes two toggles to turn off the header and footer - it seems pretty difficult to turn this into a usable component that we can bring into a project.
Or put another way, is there a way to share “coded components” directly without recreating all the custom props in a component?
I come from a more traditional dev background and in many ways I am impressed with the power of your platform and appreciate the challenges to put it all together! I look forward to continued development, especially tools for feature branching.
Thanks!
