Minecraft Wiki:Pending tasks/Templates - minecraft.fandom.com
Templates[]
Fix all templates to use <includeonly> (correctly) [bulk-page, correction]
- I'm not sure if I agree with this task; on some templates like Template:Mojangsta notice it would be useful to display the template so users can see what it looks like before using it. Though if we consistently showed the template output in the documentation, it might be fine. –Sonicwave talk 02:26, 23 April 2020 (UTC)
These guides are made by Jjlrjjlr. They summarize all additions and changes of all minor releases of a major update in a simplified, visual way. They would do very well with a nav box similar to {{version nav}}, such as "Template:Guide nav", so you can navigate between them while you're on one. I'm thinking it should for instance contain:
- The name/link of the game edition the guide is for (so far there's only Java Edition guides)
- The official name/link to the parent update page (such as Update Aquatic)
- A list of links to all the relevant releases that the guide covers, similar to the "Development versions" heading of the version nav, but only list full releases (for example for the Update Aquatic guide, this would be 1.13, 1.13.1 and 1.13.2) preferrably automated if possible
- An arrow link to the previous guide, and one for the next guide, if they exist (just like the "prev" and "next" parameters of the version nav)
- Done:
{{Guide nav}}. – Nixinova
06:34, 2 June 2019 (UTC)
- Could you or someone also please add documentation for it? I'd like the doc to specify that only releases may be added to the nav box that have been processed into the guide. This makes those links also double for "what version was this last updated for". Maybe rename the caption also to "Affected" or "Related" releases/versions instead. – Jack McKalling [
] 20:52, 3 June 2019 (UTC)
- Could you or someone also please add documentation for it? I'd like the doc to specify that only releases may be added to the nav box that have been processed into the guide. This makes those links also double for "what version was this last updated for". Maybe rename the caption also to "Affected" or "Related" releases/versions instead. – Jack McKalling [
Add documentation to ALL templates. [wanted page]
Modify the sprite system to generate documentation at runtime, client-side (with JS) [templates]
The documentation for InvSprites (and potentially, large mod sprites on non-English wikis) otherwise exceeds performance limits and stops working, even though the template itself is functional (i. e. sprites can still be used in pages).
Thoughts on implementation: a module calling loadData on the sprite data module, encoding the data to JSON. A JS function that makes an API request to action=parse with an #invoke of this module and scrapes the returned HTML for the JSON. (May need to have the module place the JSON text in pre tags and escape all less-than signs with \u003c - for JSON, they are only valid when within strings.)
- Assigned dark, he seems to be preparing tests on the nl wiki in their namespace. Dhranios (talk) 18:33, 15 January 2020 (UTC)
- All done. See #wiki of the Minecraft Wiki and this GitHub repository for the code that it uses. On the topic of implementation - the module indeed passes JSON to the JS upon receiving an API call with a function specifically made for the job. Instead of putting the data on the page itself, it is stored inside the script itself, whereafter the script generates the documentation out of it. Classes, headings and the like behave like usual, it's just the back-end which is different. A compromise I did have to make, however, is that it is now no longer possible to disable the sprite editor without disabling the script which creates the documentation as well. The rationale I used for that is that you don't have to use it even if it's loaded. —DarkShadowTNT (t ♦ c) 02:34, 21 January 2020 (UTC)
Update the documentation of many infobox templates, as several are extremely outdated.
This task is unassigned
Categorize templates and modules [Templates]
Many templates (such as {{Sound table}} as of the time of writing) and modules are not categorized, making it hard to find them. This is not limited to templates shown on Special:UncategorizedTemplates, since some templates are automatically put into giant categories such as this, but no others.
Add "Work in Progress from Split" template[templates]
A template where it is used on pages that are in the progress of splitting. This will make people copy from the other page.
This may not be necessary but I think it's a little better than putting regular "Work in progress" template. This can also be a parameter for the existing one.