Replies: 2 comments
-
Ow ... and the template styles should have the new classes thing etc. bells and whistles. |
Beta Was this translation helpful? Give feedback.
-
Hi @lllopo, we discussed this during the v3.29.0-beta, but I want to include my answer here as well.
Thank you for sharing this idea! 💡 🤗 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Prerequisites
What problem is your feature request going to solve? Please describe..
When a template is created (a header template for example), this still introduces a wrapper HTML node that has a style section in its settings, but only with padding, margin and background, thus no real layouting or styling control what so ever. So, if one wants to have a real control over style and layout - an internal layouting element like a flexbox should be added. This is fully redundant imo.
Describe the solution you'd like.
The solution to this is, to make the style section of any template settings a full fledged DIV styling section. This way the template container itself can be turned into plain block div, flexbox or grid (I don't see grid controls in the layout section anywhere btw, but that is another story) and no internal containers would be needed (unless desired by the end user). End result - one nested HTML node less per template.
As a side note - the template widget (when it comes to V4) should also NOT add it's own wrapping element either as it is not just creating overhead, but also introduces all kind of layouting issues. I have an issue for v3 for this that is not moving forward for a long time now. Hope it'll be noticed here.
Describe alternatives you've considered.
No response
Additional context
No response
Agreement
Beta Was this translation helpful? Give feedback.
All reactions