User blog comment:CzechOut/How Portable Infoboxes Can Change Your Style/@comment-1142365-20160708232030/@comment-26402117-20160711231438

In defence of staff, customisations can be replicated using CSS - and I try to code my own stuff because I think other people guiding me makes me feel like a toddler. That is not to say that its easy to convert such a massive number of templates to their PI counterparts on CoD Wiki - it is. Perhaps shedding some weight may not be a bad idea. Perhaps there's a few gimmicks. a few weird themes that are useless and should be merged or removed.

That's all I can say in defence however. It's clear that unless you want anons to ask "Where's ?" "Why's this field not formatted?", you have to make a smoother transition by installing a significant and nonzero number of themes. Maybe not 2K lines but yes, a significant amount, at least 100 lines for sure. But affecting locally important things like legibility or things like romaji italicisation, caption customisation, etc is a bad idea and shouldn't be borne. Staff leaving mobile skin with default accent colors and other testing modules across Wikia bleaches the local wiki's presence and makes it all about Wikia, but I've said that in this blogspace before.

Heck, it would be much easier if I could use more browser compliant forms of "matches:" to apply the same rule to different themes with the same individual feature. SASS would decrease the length of each theme specific rule's selectors by about 40%. Maybe a change like that would massively improve things for users and allow them to customise without so many lines. It would make PI customisation easier and more efficient, as constraining as it can be in its current form.