Your plan seems fine, Geth. Most people like this go away when they get what they want, anyway.
In my own news, I'm planning to replace all of the {{work}}/{{trope}}/etc. templates soon with something that is largely the same is current. The new one is on display at {{work test}}. I have a few reasons to do this:
You can test it by previewing {{work test}} where {{work}} is currently. Let me know if you see any issues before I deploy.
Later on, I think I wan to finally implement my plan to cancel Sparta for being anti-woke remove Laconic sub pages by putting the content into the main text. If you look at Dacha, you can see what happens with the {{SHORTDESC}} magic word, which makes the description show up there. And not just there! You can see it in search (on newest Vector), as well as in ?action=info. Ideally I'd like to do three things with this: display the short description on category pages to improve discoverability, figure out a way to hack vector2022 search bar into vector classic, and bot the text of Laconic pages into Main, so I can delete them.
I'm not sure if we need to change how the text is displayed. (All of that whitespace on Dacha -- that in the usefulnotes template I'm gonna fix soon). Second, it doesn't seem to apply wikilinks (see Aerith and Bob). Not sure how important that is -- we definitely will have laconics in the form of X meets Y. We could always replace it with something more like Bucket which could do the links, but probably not everything else.
In my own news, I'm planning to replace all of the {{work}}/{{trope}}/etc. templates soon with something that is largely the same is current. The new one is on display at {{work test}}. I have a few reasons to do this:
- I'd like every template on the same module, for once. Updates to the modules didn't take effect because people edited the wrong one.
- I rewrote it to look less like spaghetti code, and more like something that someone else could maintain.
- The net performance is something like the module takes 5 ms longer to run, but we spend 10 ms less in PHP parsing, so it's a tiny perf gain
- Configuration of which subpages go in which order is moved to another module, which other people should be able to edit without screwing things up.
- By replacing {{TOPLEVELPAGE}} with mw.title.rootPageTitle it squashes the italics bug -- comparing string lengths when one of the strings used escaped characters meant counts didn't match (thankfully not a unicode normalization bug, but similar idea)
- Removing Variables extension from our code. We didn't use it much, and its future remains in doubt from the near-term rollout of Parsoid. (Also: Parsoid is second system syndrome for the wiki parser. I expect in 5 years it will be just as bad as the old parser, only differently bad.)
You can test it by previewing {{work test}} where {{work}} is currently. Let me know if you see any issues before I deploy.
Later on, I think I wan to finally implement my plan to cancel Sparta for being anti-woke remove Laconic sub pages by putting the content into the main text. If you look at Dacha, you can see what happens with the {{SHORTDESC}} magic word, which makes the description show up there. And not just there! You can see it in search (on newest Vector), as well as in ?action=info. Ideally I'd like to do three things with this: display the short description on category pages to improve discoverability, figure out a way to hack vector2022 search bar into vector classic, and bot the text of Laconic pages into Main, so I can delete them.
I'm not sure if we need to change how the text is displayed. (All of that whitespace on Dacha -- that in the usefulnotes template I'm gonna fix soon). Second, it doesn't seem to apply wikilinks (see Aerith and Bob). Not sure how important that is -- we definitely will have laconics in the form of X meets Y. We could always replace it with something more like Bucket which could do the links, but probably not everything else.
"Kitto daijoubu da yo." - Sakura Kinomoto