Professor.Oak said:
Thank you for your suggestions; I will look to apply it effectively. I would agree that it does look spacious with the list enfolded into the collapsible section; without it, much of the informational contents of the page - the list of move-compatible Pokemon, contextually speaking - will be readily viewable, without looking cluttered (there isn't a myriad of information on the page to begin with).
I would've considered keeping them collapsed if the template itemized other move pools - the list of Pokemon that learn it via TM, move tutor, and so forth - but at this present time, I don't plan to incorporate those lists into the already-existing template. For now, I feel as if it will suffice by linking those subsets of learnable moves via the Availability section in the template, but I may change and rescheme this in the future, depending on future feedback. As long as it only documents the level-up learnset of move, it should be manageable to keep it uncollapsed.
While yes, all of the move-compatible Pokemon are manually entered into the template, I've constructed the template's modularity to require as little of input as needed to output the information that it does -- the only arguments that must be entered are the Pokemon's name, and (if it has a designated level) the level wherein the move is learned naturally. The template generates all of the data needed using primarily the Pokemon's name, calling the said data from
MovesRawList and
PokemonRawList.
For the template to automate any other data, the template-called data would need to be compiled in a raw-text, comma-separated format, as exemplified in the raw-data lists that I've linked. While we won't be able to fetch this data from the "What Links Here" page directly, a script/macro can be used to parse data from the list; just remember to also include the level of the Pokemon was designated to learn it in, in Black/White, since the pages that you've shown won't display it on their index.
