Recently I created a new Theme for the wiki, see RS:THEME#Heroes_.28Monaco.29. I'll be using that one myself. Though there's one problem: a lot of templates are incompatible with it. What I'd like to suggest is to add classes to these templates, so that theme editors can change them. This won't change anything to the default layout, it will only change if the class is edited at Monaco.css. See User:Tedjuh10/test for an example. (I'm not sure if this was already suggested?)
Go ahead - If it improves compatibility on other themes, then I think you should use common sense and do it. What'd also be awesome is if you could compile a list of all the classes hanging around (on a subpage of RS:THEME maybe?). 15:09, July 8, 2010 (UTC)
- Ah, a large list of templates that have these classes added to them. A subpage would be great, and have templates in alphabetical order perhaps, to make finding the one easier. ~MuzTalk 15:14, July 8, 2010 (UTC)
What Gaz said - + Be Bold. If it doesn't affect anything with default theme you don't need consensus. But it is nice to know so people aren't wondering what's going on. HaloTalk 15:20, July 8, 2010 (UTC)
Comment - Allright. I'll just go ahead then :). I'll keep a list of classes on my userpage. Haven't got much time right now, so I'll probably get started doing it tomorrow. Mark (talk) 15:31, July 8, 2010 (UTC)
Comment - Most of the main templates have their classes now. Some of them already had ids/classes, so that spared me some time. You can find a current list of template classes here. Not all of them are done, though when I run into a new template I'll add a class (if it already doesn't have one), and add it to the list. Mark (talk) 12:28, July 9, 2010 (UTC)
- Excellent. I suggest we move that list into the project namespace, akin to Wikipedia's Catalogue of CSS classes. This will be a great resource for anyone using CSS customization.
- Also, I suggest that we don't use ID's for templates which may be embedded multiple times per page. For example,