Allow customizable CSS stylesheet in S2.
Short, concise description of the idea
Much like S2's Link(s) List, I think there should be a simple interface to allow users to supply CSS stylesheets for their journals.
Full description of the idea
S1 allows a good deal of customizability through overrides. Much of this customizability comes from the ability to include CSS in one's journal, using the
What I'm proposing here is that some of this customizability be brought to S2, by allowing a simple interface for users of S2 to include CSS in their journals.
An ordered list of benefits
This would make it easier for paid/perm/EA-account-holders to apply CSS to their journals, and possible for free users to do so.
This would make this suggestion (mostly) moot.
This might encourage more people to use S2, which IIRC is less resource-intensive than S1.
howto tutorials that currently use CSS in
GLOBAL_HEAD overrides would be somewhat transferrable to S2 (insofar as S2 system styles match their S1 predecessors).
An ordered list of problems/issues involved
This might discourage free users from paying to CSS-ify their journals.
This might allow non-tech-savvy users to mess up their journal views more easily.
If you have any other thoughts, please comment.
An organized list, or a few short paragraphs detailing suggestions for implementation
Interface-wise, I envisage something like this, to be linked-to from the Manage Accounts page. Alternatively, it could perhaps be built into the Customize Journal page somehow.
Backend-wise, I envisage this overwriting the function Page::print_custom_head() that jproulx described here. Anyone who wants more than a custom stylesheet would need a Paid, Permanent, or Early Adopter Account, and to make their own user or theme layer to overwrite this function manually.
Optionally, there might be two separate stylesheets: one for every view except the friends page, and one for only the friends page. (This is because the friends page, unlike all other views, involves HTML beyond the author's control, so it may be desirable to have different or extra CSS for it.) I don't see this as necessary, though, for the suggestion to be useful.