User:Mudscape

Mudscape talk I also edit on the OldSchool RuneScape Wiki. Mudscape on discord

Wiki's are for users first, editors second.

Projects

Better denote subsections in mobile navboxes
Fix external link color when swapping to dark mode (see main page)
Update css to use variables and combine leftover gadget styles
Minecraft Wiki:Projects/DIG:Design to Implement Granularity - I wrote the first draft of the project page and have participated in splitting multiple pages.
Updating {{Crafting}} and {{Crafting usage}} to use SMW instead of DPL.

Trading table formatting - A similar idea to the mob loot, although villager trades are already consistently in tables. Using a module instead of raw wikitext enables us to change the style/formatting of the information and also store information in SMW, which can then be automatically pulled onto item pages.
Advancements porting from DPL to SMW - resulted in 50% speedup of querying advancements
History section porting from template to module - the vast majority of the actual module code was written by User:Chixvv, I simply updated it with some new history features and replaced the original serialization with JSON serialization. The module performance is 67% faster than the template, while keeping the syntax almost exactly the same. I also ran the bot to update pages to use the new module.
Mob loot formatting - creates a consistently styled table on each mob page with their loot, and saves that loot data using SMW. Template:Drop sources then reads that data on item pages and constructs a similar style table representing all mob sources for that item. This basic system can be expanded for use in breaking blocks, structure generation, loot tables, villager trades, and more.

DPL is really slow. Rewrite dpl templates using Bucket and lua which is much faster.
- Template:Load achievements and Template:Load advancements are both using dpl
Mob is slow, partly because it transcludes Damage/Mobs which calls Template:Health 265 times and that template is a mix of lua and template script logic which means its slower than just going straight into lua.

Self notes:

Think about some sort of Tempalte:BlockBreakingInfo that covers hardness/time to mine/mined drops/silk touch. Can use a synced switch for stuff like crop states and pages covering more than one block
Make the sprite(link) stuff faster by not using lua. Tons of small calls are what lua is worst at.
This is cool [1] - shows module dependencies
Fix dark mode bugs, make (finish?) dark mode for mobile
- Special:Ask really breaks when switching to dark mode.
Write some JS to make "This is a minor edit" "sticky" - can probably copy the "use last summary" thing
Drops do we really need all this duplicated information? Its just another place that doesn't get updated.
POE wiki has some cool solutions to problems that we also experience.
- Their Template:Collapse has extra css to be more noticeable and have the entire displayed bar be a click area for the hide/show toggle.
- They have a nice Gadget-responsive-tables.css and Gadget-responsive-tables.js that is used for their history, it caps the height of history but also lets users uncap the height.
- Module:No globals throws an error when you read from a nil global, or write to any global. This helps catch typos, since lua global variables do not have any specific keyword for declaration, a typo in a local variable name will silently create/reference the global variable.