User:Tiddlywinks/PokemonDivbox/form/doc
This template creates the bottom part of a Pokémon infobox, containing most if its data aside from its names and National Pokédex number. If there is more than one form, this data can be switched between with the selector in User:Tiddlywinks/PokemonDivbox/h.
The first call to this template should be proceeded by User:Tiddlywinks/PokemonDivbox/h and the last call should be followed by User:Tiddlywinks/PokemonDivbox/f.
Parameters
Some should change/disappear, like forme...
- name? (just for the target? which is only even necessary if there are multiple infoboxes on the page, which is mostly for examples here...)
- ndex (for type categorization sorting)
- form: the form # (to match what's selected in the header)
- type1
- type2
- category
- ability1
- ability2
- abilityh (changed from abilityd)
- malerate (unknown, 0, 12.5, 25, 50, 75, 87.5, 100)
- note: changed from gendercode, 0 => 100, 31 => 87.5, 63 => 75, 127 => 50, 191 => 25, 223 => 12.5, 254 => 0, 255 => unknown
- egggroup1
- egggroup2
- height-ftin
- height-m
- weight-lbs
- weight-kg
Also, note to self: I can mostly copy Template:Pokémon Infobox/doc. Don't need to reinvent the wheel. (But for now I think I will keep track of what's in this template.)
Several parameters have now been removed. We'll want to clear out all unnecessary parameters when updating the infobox style.
Examples
We could omit the romanization if it's the same as the trademarked name. And the trademarked name if it's the same as the English. But having them all there if they exist might also be good just for consistency. (I could see people complaining that we don't have the romanization or whatever even if it's the same.)
Notes
Derived from User:SnorlaxMonster/Pokémon Infobox
TBD
- Add a link or something from "different in old game" notes, to some section in game data?
- Categories actually become a little complicated if data was different in a past game. Should categories be offloaded to the linked section? (Is it easy enough to only make categories for the old data?) What if a Pokémon's data has never changed? (Or this or that piece of data.)
- How should introductory generation be handled? Species only, or all forms? (E.g., Category:Generation I Pokémon. Currently it says 001 to 151, but is that still strictly what we want?)
- Double-check all current/old parameters... Are there any old parameters that still need to be included? Should any other parameters be changed?
- Should we still include Smogon links? (Would just having them at the bottom of the page be fine?)
- Is there a good way to add some link to quick jump to form data or something?
- Maybe have some link if there are elided forms (like Vivillon)
- Proper documentation
Category:Pokémon with Mega Evolutions was skipped; it will need to be manually added to appropriate pages.
Data cells
Just in case... All "captioned cells" have the following form.
<div class="roundy" style="background-color: #{{{{{type1|???}}} color light}}; display: flex; flex-direction: column; grid-column-end: span __1or2__;"><!-- captioned cell: __name__ OPEN -->
<div class="blacklinks">'''__link__'''</div><!-- cell caption -->
<div class="roundy" style="background-color: #FFF; padding: 3px; flex: 1; display: flex; flex-direction: column; justify-content: center; align-items: center;"><!-- data space: __name__ OPEN -->
<div style="width: 100%;">__data__</div><!-- __name__ -->
{{#if: {{{__param__-note|}}}|<div style="font-size: smaller;">*Gen. {{{__param__-note|I}}}+</div>}}<!-- note -->
</div><!-- data space: __name__ CLOSE -->
</div><!-- captioned cell: __name__ CLOSE -->
The first div is a container that fits in 1 or 2 columns of the parent grid (__1or2__, if this is 1, the whole grid-column-end property can be erased). The container's children stack vertically, with the first child being the "header"/caption, while the second is a space for data. The data space contains its own children (again vertically stacked): a container for the actual data and a triggerable note to mark if this data was different in a past game.
The data can contain more or less anything necessary (__data__). It may be necessary to add some additional styling to the data container.
All words starting with "__" in the code above should be replaced.
