Topic on Talk:Requests for comment/Scoping site CSS

I think it is a nice and useful thing to split UI and Content styles separately, than have them in same CSS file. If the RFC can be modified to say that (content-scope some site-wide CSS, do not content-scope others), I think it will have a lot more support. It'll also solve the problem of displaying content appropriately styled in various places while also not removing any existing functionality. Thoughts?

Creating an entirely new (and equally powerful) way of letting users customize the site is a *huge* task, so removing that monkey off this RFC's back would make things a lot better :)

That sounds like a good idea and good first step. Separating ui styling changes from article styling into MediaWiki:Ui.css would be a useful distinction and would allow the scoping of Common.css

To help with adoption we could imagine making this an opt in thing to allow time to move relevant styles from MediaWiki:Common.css

ps. something funny about 'descoping a proposal about scoping css' :)

Intentional :D

So ideally, this should be split into multiple RFCs. The ones I can think of, so far:

1. LESS support for RL.
2. Separate CSS(LESS?) that applies just to content, and is scoped as such.
3. An easier way to custom-style your wiki that does not require you to edit CSS, and also can be as flexible as the current one.
4. Remove customizability via Site / User CSS.

1 and 2 should mostly get general support, and *should* get what we want (content styles that we can load by themselves without conflicting the UI). 3 is awesome, but also very hard - and does not have a clear use case. 4 is akin to taking away internet from a hackerspace (or wikitext from wikimedians :P) and is a lot, lot harder - and of limited benefit.

So... split this? :)

Compass is better than LESS. Don't prejudice the solution by the choice of RFC titles.

This post was posted by SPage (WMF), but signed as S Page (WMF).

[citation needed] (but yes the RFC shouldn't prejudice the solution - it should be a hard fought battle to the death between the two..

I also like the idea of splitting Common.css into Content.css and Ui.css (or UiCommon.css). Content.css would be scoped to the content, and Ui.css would be general CSS intended for the UI. Common.css could then be deprecated.

I still like the idea of Requests for comment/Allow styling in templates as a longer-term modular approach to content/templates.

This post was posted by Mattflaschen, but signed as Superm401.