Oh goodness, that makes me SO HAPPY. OK, I'll be in touch soon with next steps. Please tell your co-admins that they are rockstars and have earned a pizza party at my house next time they're in San Francisco.
From there on we could probably tackle the location templates (there are way too many of them around, someone made an awful lot of duplicates a while ago and I'm about to propose we merge them back into one location template per game). The location templates are like the NPC templates in structure.
Finally there are the item, books and shouts templates. Those are the more sophisticated ones where we rely on alternative table lay-outs and scripts running inside the tables. I was planning on replacing some of these scripts with Lua versions, but so far I haven't been able to get these working.
How do the new infoboxes interact with embedded scripts? Something like the DragonScript template has become a big dependency for the wiki itself over the past years.
I know this isn't really my discussion and I know my opinion probably won't mean much, but I had a plan before to merge all the Quest infoboxes into just one infobox for all. Obviously, this fell through because I left the wiki due to dissatisfaction, but hopefully it's something to consider.
It appears that any categories that are added inside the infobox-tag aren't processed. E.g. w:c:tes:Gwilandor is not added to w:c:tes:category:Online:_Image_Needed while there is no image present in the infobox itself. There are parser functions inside table cells that check for missing information and add categories based on this missing information. Does this indicate that parser functions are not yet supported?
Would it work when those parser functions are replaced with Lua equivalents?
For now I think a possible workaround would be moving some of the parser functions and category assignments outside the template, but this is no option for some other templates that are on the todo-list for transformation such as w:c:tes:Template:DragonShouts.