FFXIV Wiki:Template styles
Jump to navigation
Jump to search
- Project description
- Use
<templatestyles>to reorganize template-specific CSS that are currently in global CSS or inlinestyleattributes - Status
- Backlog
- Members
- Erin Umbreon (talk)
- Discussion
- Talk page, Discord
Things to move out of Mediawiki:Common.css and Mediawiki:Mobile.css
- Main page styles (
#mainpagenavigation,.page-Main_Page, etc) - 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 (
.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) - Inline icon styles (
.inline-iconand.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
.dialoguei guess) - {{colorize}} (
.colorized-description) {{STFI}} (.standard-frame-iconetc)- 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
<templatestyles>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.
- 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
- 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)
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 <templatestyles> or have their CSS in Common.css and Mobile.css.
TODO: make a list of some of the templates where this is most relevant