4 ms·
I guess you're right. Never thought about the nested Divs. Anyway but for things like Form elements, Cards, Panels wherr the classes remain same but each Css f
by superasn 9y ago
I guess you're right. Never thought about the nested Divs.
Anyway but for things like Form elements, Cards, Panels wherr the classes remain same but each Css framework has its own set of classes, i was wondering if it makes sense to have a fixed set of tags like <panel>, <card>, <col>, etc and then we can have a transpiler that coverts those tags to Bootstrap panel or a bulma or uikit, etc panel.. Just like we transpile Sass into css.
- HelloNurse 9y agoIf you are going to write simplified markup in some DSL that adapts HTML to the needs of your pages and a translator to turn it into complete markup with all the classes and utility HTML elements needed for CSS styling, there's no reason to avoid the target CSS framework conventions, including classes, in the output, and there's no place for CSS in the input because it is abstract (it should represent document structure only, e.g. a "panel", without bothering with styling, e.g. turning a "panel" into two levels of DIV and IMG elements with certain classes).