FFXIV Wiki:Template styles

< Wiki to-do list

Project description

Use to reorganize template-specific CSS that are currently in global CSS or inline style attributes

Members

Erin Umbreon (talk)

Status

Backlog

Last updated

3 April

Discussion

Talk page, Discord

Things to move out of Mediawiki:Common.css and Mediawiki:Mobile.css

• ☒ Main page styles (#mainpagenavigation, .page-Main_Page, etc)
  • I think this is mostly going to be done through the FFXIV Wiki:Update site CSS, main page, & sidebar project; I'm going to ignore the old main page styles
• ☐ Fancy table styles (.table, which is provided by {{STDT}} I'm pretty sure?)
• ☐ Infoboxes (.infobox)
  • There's not a single "base infobox" template that everything uses right now, but we can pull in a single CSS page from all the infobox templates for now and do more work to unify their structure later
  • ☐ Also .weapon-damage-stats, .armor-defense-stats, .equipment-footer, etc
• ☐ Navboxes/notices (.nav, shares a lot of styles with infoboxes that will need to be separated, will similarly need to be pulled in by multiple separate templates)
  • This will be somewhat easier now that {{noticebox}} exists, though we have a *lot* of pages that need to be updated to use it
• ☐ Inline icon styles (.inline-icon and .text-icon, not sure how to handle this exactly, it probably doesn't need its own template, this one might stay in common.css for now)
• ☐ Recipe boxes (.recipe-box, .ingredients, etc)
• ☐ Dialogue (wait, we have classes for this? figure out what the fuck uses .dialogue i guess)
  • Note: the new dialogue format is already fine, this is specifically for an old class that I have no idea where it's even used
• ☒ {{STFI}} (.standard-frame-icon etc)
  • This and other icon templates actually can't use template styles at all. We have SMW properties like Property:Is obtained by (used via {{Obtainable parameter}}) which can contain icon templates in their values; and gets converted into strip markers which don't survive a round-trip through being stored as an SMW property value. This breaks display of these properties entirely, so it's a no-go.
• ☒ {{colorize}} (.colorized-description)
  • same as above, this needs to stay in Common.css forever because colorized descriptions are used in SMW properties for items/etc
• ☐ Item rarities (.rarity; honestly these should just be handled as CSS variables I think)
• ☐ Relic quest stuff (.relic-quest - i don't think any of this uses templates yet? it *really* should)
• 🗹 Special chat characters font handling
  • Done by User:Tempest Dawn with the addition of {{Special chat character}}

Things to move out of inline style= attributes

I mean, basically everything that uses inline style attributes should stop doing that outside extremely niche one-off things in the main article namespace. Any styles used by a template should either use or have their CSS in Common.css and Mobile.css. TODO: make a list of some of the templates where this is most relevant