Feature #79287
closed
npm and bower package for css_styled_content fluid_styled_content styles
0%
Description
For a site package it would be awesome to have a npm and bower package with all the css_styled_content and fluid_styled_content styles.
This package could be used from the core and from integrators and would be manages central.
The package should contain sass (and less) and css.
Therefore the core must have a "read from file" functionality for TypoScript _CSS_DEFAULT_STYLE to include that styles w/o braking change.
Updated by Benni Mack about 7 years ago
- Assignee set to Benjamin Kott
Good idea, but probably only for FSC. Maybe @Benjamin Kott could check that?
Updated by Riccardo De Contardi almost 7 years ago
I write here my 2 cents/considerations:
- the technology about frontend developing goes insanely fast, and when you decide to adopt one solution, it could become obsolete very soon ;)
- the _CSS_DEFAULT_STYLE contains some values from TypoScript constants (like $styles.content.textmedia.textMargin )... how to deal with them?
Maybe one solution could be to use css4 variables (var(--something)) so you could split the css in two:
The _CSS_DEFAULT_STYLE could just provide all the variable values,like:
:root {
--styles-content-textmedia-textmargin: {$styles.content.textmedia.textMargin};
/*and so forth*/
}
and so the remaining part of the css could be separated from _CSS_DEFAULT_STYLE and be put on a file (css, scss, etc)
- Cons: Browser support https://caniuse.com/#feat=css-variables :)
Updated by Georg Ringer over 4 years ago
- Status changed from New to Rejected
I am closing this issue because the default CSS is pretty useless nowadays. Nobody wants to have a content element with n variants of images. If still needed it doesn't work out with responsive or any other well known CSS frameworks.
It might change if once the core ships content elements which are up2date.