Split default.css.

[textpattern]

Split default.css.

[philwareham]

Whilst on a production site I would not personally store CSS in the database (and I make that quite clear in the comments and readme), this is the default shipping theme for textpattern 4.5 and we will not polute the root directory with static files.

I also disagree with splitting the CSS into multiple files for media types, that is outdated methodology (files should be concatenated wherever possible to lessen http requests).

Thanks for the suggestions but I won't do either of these changes, sorry.

[6aKa]

By default TXP store css in database(txp_css table). For example, when you using "<txp:css format="link" media="" />" in html code you see "". Script css.php get compressed style from database and gives it to output. This output not cached by browser(good for theme developing).
In production useings direct link to css style such as "".
I propose make buildin css edition system more flexible only for developing by spliting, thats all.
As i mean users which not optimizing txp instalation don't care how many css style parts including.
And users who care optimization split css for parts to develope theme for diferent media types and collect for one static file.
I can't find any txp official recomendation or documents about organization css styles.

[philwareham]

End users can split the CSS file into pieces if they wish to (or better still, can use the sass files from this GitHub repo), and the code is clearly commented to make that very easy. It won't be split for the default shipping theme though, we are keeping the database entries to an absolute minimum. Cheers.