Board Thread:Watercooler/@comment-3032314-20181119015150/@comment-26402117-20181119115451

Since T is now a global Lua module, we can't just dump the styles into MediaWiki:Wikia.css—they have to go in their own stylesheet. I'm on the fence with the idea of a separate stylesheet for T. The main reason for this is that Mercury recently began respecting inline styles inside Portable Infoboxes (though undocumented). Users on Dev Wiki [#Installation see inline styling] (btw opacity should be 0.75 :p).

There's two sides to this really:    
 * 1) Is it okay to make T Lua code more simple by adding new dependencies? Assuming CSS is kinda more cumbersome to install than JS and Lua here.
 * I personally think HTML5 can allow semantic presentation for this situation :D
 * The,   and   tags are much better to use than default styling.
 * 1) Wouldn't styling and data attributes make it very cumbersome to customise on wikis? How could we ensure that T output isn't overqualified as it is currently? :/
 * I absolutely agree that inline styling should go. Classes would be nicer than data attributes. Not sure whether they trip the portability parser on inline elements tho.
 * However, the prefix and suffix for parameter descriptions could be configured from the T invocation, so that users won't need to install CSS in order to make T work :)

T is used throughout the wiki, so abrubtly yanking out the inline styles will cause breakage until/unless the new stylesheet is @imported. In the past, staff copied code to Wikia.css, but I should confirm that with them. The T module is the best thing since sliced bread ;) but such a change will inconvenience other wikis.

I'm not sure what the proper title is for this new stylesheet. Only two other modules depend on CSS (Global Lua Modules/NavboxBuilder and Global Lua Modules/Mbox), and both use, but I'm nut sure if that's correct. Sounds right (not sure if true in all cases). Should that be noted in DEV:CC for newcomers?