Board Thread:News and Information/@comment-26143371-20170304235143/@comment-10228869-20170428055734

For easy discoverability all pages that still use the generic infobox are put into a maintenance category automatically. Thanks. You do an amazing job of adding new content quickly, and I'd certainly never ask you to stop or slow down, but others wishing to contribute would probably appreciate automatic maintenance categories giving them a ready-made list of tasks to chip away at when they have the time.

My version would use the high-traffic pages as test-pages, which in general would seem like a bad idea. However if a problem comes up, it will probably be along the lines of "This specific thing can't be expressed with the new infobox", which means it will be noticed when creating/editing the page as opposed to when viewing it. I get that, but I was figuring you'd rather get a pile of complaints about each template while it's still fresh and you can solve them all with a more general solution, rather than have them come trickling in as pages are gradually updated and doing a series of small hacks.

In working through various issues here over time, I've found a lot of oddities that only affect one or two pages in a given category, so I worry that you'll find major design issues months (or years) in the future that you'll wish you knew about now. Or maybe I'm just too jaded from working too long in the software industry.

The [auto category] code will most likely just end up in a Lua-module where I can do proper logic, which would keep changes to the infobox-templates minimal. I don't know Lua, but if you can at least code a few different examples, I should be able to modify them easily enough to cover any other cases that we can think of. Code is code.