I was extremly excited about components (and still are ;). I’m working in a large company with a dedicated marketing team and multiple companies/websites in the group. What I am trying to achieve is to have components the content managers simply can drag & drop together in a hierarchy but with a very limited way of “destroying” things design wise . But I still need the possibilities on the development side to create them in a pixel perfect and individual way. Fortunately I found Cwicly to achieve that. Thank you so much for all the hard work and passion going into it!
Now, back to the request. In the context I just described componants are currently of limited use. Maybe I oversaw something. But basically right now they “just” encapsulate the HTML Structure and the Styling (which is great!) but don’t have a possibility for adding components as children in the hierarchy. This gives me a lot of headaches with many components I want to build for the Content Managers.
A simple example is a cards container that allows to add 1 or more cards with the posibilites to adjust the styling. Most of it is perfectly doable right now with components. But adding 1…n cards into the cards container is not. The workaround is to insert like 4 maximum cards in the component and use the visibility to activate 1…4. But than also the complete component properties of the possible cards need to be linked up into the cards container because they are not accessible in customize mode. So I could go into modify mode of the card container, but than I modify all instances of that conatiner which doesn’t make sense in this case.
Okay, with cards it would be managable somehow. You will have more than 3 or 4 cards in a row rarely.
But I have other similar cases. One more complex example would be this element:
I built this as a cwicly component (At least I tried to built it as a component). Each flag is a component with properties like Text but also Orientation and Position. Currently it is not possible to add them as descendants in the Container with the image. But this is important because position and size need to be relative to the image in the background.
Is there anything on the road map for adding decendant components this?
I would propose a special cwicly block called “component content” or “content placeholder” similiar to the cwicly “post content” block, which can be added inside the html hierarchy in the component (1 or more times) and will be visible in the hierarchy on the outside of the component in customise mode so that blocks or other components can be added in there:
Thanks for your time looking into it!