User:Seb26/Item infobox

Ideas

• Item infobox only. Class, maps, websites should be separate.
• Sole important parameter: type
  • Determines type (weapon, hat, misc, taunt, tool, action)
  • Switches visible fields based on its value
• Scattered ideas:
  • Translations should be defined directly inside the infobox
    • No | weapon-slot = Primärwaffen
    • Instead: | slot = primary which on German pages generates Primärwaffen
  • Attributes:
    • Should be plainly named
      • trade over tradable
    • Simple yes/no (Issue)
      • Sometimes this isn't possible, need way to handle these
        • Possibly "if value != yes/no, display value" (may create issues with translators who translate "yes" and "no")
  • Param names should not be long & hard to remember:
    • name instead of hat-name-override

Core ideas

• Efficient & translator friendly
• Well-documented – both on template page & on Help:Language translation

Implementation

• Research
  • Definite numbers on how many pages to update
  • Generate lists and distribute workload
• AWB find & replace in-template call

Plan 1

• Deploy to {{Item infobox}}. All other infoboxes remain as they are.
• Parse through all pages using older infoboxes, change template to {{Item infobox}} and replace code & old parameters.