Given Bulma and Bootstrap are opposites on the spectrum in terms of naming conventions, why not make fortune have a longhand and shorthand counterpart, one being semantically optimized for prototyping (shorthand) and one being semantically optimized for maintainability (longhand). I can't say I'm a fan of m- and p- classes for margin and padding but I can see the benefit.
E.g. bkg and background available in fortune.shorthand.css and fortune.longhand.css
i think we should try to minimize the public api as much as possible (at least there is a robust contribution team and demand for it). sounds like extra maintenance burden with minimal return
Given Bulma and Bootstrap are opposites on the spectrum in terms of naming conventions, why not make fortune have a longhand and shorthand counterpart, one being semantically optimized for prototyping (shorthand) and one being semantically optimized for maintainability (longhand). I can't say I'm a fan of
m-
andp-
classes for margin and padding but I can see the benefit.E.g.
bkg
andbackground
available infortune.shorthand.css
andfortune.longhand.css