Idea / Wish for future versions of Cobalt/Emerald
Please, split appearance and code as much as possible. Since Cobalt has already a strong and versatile template approach, it is a logical step to follow that concept in all areas of the extension.
I know, it is hard to find the perfect balance between easy configuration and feature richness. Not to mention the current "Bootstrap" dilemma.
I am aware of the bootstrap pre-build classes and that they are made to include them in the markup... but it should not be hardcoded in deeper files/elements that are not accessible for templating or overriding. We have to think twice, before relying on layout grid classes, buttons and also icons in parameters etc.
If Bootstrap classes and icons are used in templates, it is possible to customize a copy... but also this duplicating could be improved:
i.e. template parameters for layout classes, that allow to change and extend the defaults. This way we could make default templates compatible with other frameworks and grids, without creating any copies.
Thanks for listening.
I am sure, we can do better! ;)
Idea
Announcement
Conversation
Praise
Problem
Question
Accepted
Open
Idea / Wish for future versions of Cobalt/Emerald
Please, split appearance and code as much as possible. Since Cobalt has already a strong and versatile template approach, it is a logical step to follow that concept in all areas of the extension.
I know, it is hard to find the perfect balance between easy configuration and feature richness. Not to mention the current "Bootstrap" dilemma.
I am aware of the bootstrap pre-build classes and that they are made to include them in the markup... but it should not be hardcoded in deeper files/elements that are not accessible for templating or overriding. We have to think twice, before relying on layout grid classes, buttons and also icons in parameters etc.
If Bootstrap classes and icons are used in templates, it is possible to customize a copy... but also this duplicating could be improved:
i.e. template parameters for layout classes, that allow to change and extend the defaults. This way we could make default templates compatible with other frameworks and grids, without creating any copies.
Thanks for listening.
Results in a workaround by using PHP code to change the appearance! :(
I am sure, we can do better! ;)