Forums: Index > The Wizengamot > Character infoboxes

Hello. I'm sure some of you have noticed by now that we are currently using 30+ infoboxes for use on character pages. The only difference in the templates being the theme that the template is using.

Not only does this lead to confusion for new users as to which infobox to use on which character, but it also may result in extra maintenance work for the users here.

Say we were to add a new section to character infoboxes, "Favourite sweet" for example. This would mean that a user would have to go through and add the new section. If it took 10 seconds for a user to load the template, add the new section and save the page it would currently take them around 5 minutes to make the change on all of the templates. Why should we take this much time to make such a small change to the infoboxes?

Luckily we don't have to. If you take a look at my portable infoboxes testing wiki you can see that I've set up one template (Template:Individual infobox) to use on all character pages (Minerva McGonagall and Albus Dumbledore).

This template determines which theme to display by searching the |theme= parameter. Entering a value, hogwarts-staff or phoenix for example, will cause the appropriate theme to be displayed.

This will heavily cut down on maintenance work. Instead of pushing all changes to each separate infobox we will be able to make the change in one place.

Migrating to this new convention, however, will require that we edit our character pages (by use of bot) to use the new infobox.

What are your opinions? Any questions?

-- Cörey (talk) 21:08, October 24, 2016 (UTC)

Well I for one think this is a good idea. It will be simple for my bot to replace the infoboxes (such as "Slytherin individual infobox" to "Individual infobox |theme=slytherin") and it lays the groundwork for updating the individual infobox with changes such as separating out family members that were previously discussed. Support! --Ironyak1 (talk) 19:01, October 27, 2016 (UTC)
This proposal looks good. I concur with Ironyak that this will make it easier to overhaul the family field as has been proposed previously. Starstuff (Owl me!) 07:54, November 1, 2016 (UTC)
Seems to make things easier overall. If the required changes can be automatically made via bot, I can't think of a reason why not to do this. --  Seth Cooper  owl post! 14:20, November 1, 2016 (UTC)

Well it seems to me that the decision is unanimous. Having been open for two weeks, the community has, in my opinion, had more than enough time to come forward and express any concerns. Could an administrator please go ahead and unlock Template:Individual infobox so that I can push the necessary changes? Thanks! -- Cörey (talk) 03:45, November 7, 2016 (UTC)

Go ahead, I just unlocked the template page. Thanks. --  Seth Cooper  owl post! 00:14, November 16, 2016 (UTC)
There's a problem with the template colour not rendering in the character name field (which is located at the very top of the infobox, or below the image if there is one). Starstuff (Owl me!) 08:45, November 20, 2016 (UTC)
There's also a problem of certain fields not rendering inputted data at all. For example, see Theseus Scamander, where someone has inputted "Hufflepuff (possible)" into the house field, but this is failing to render. Starstuff (Owl me!) 11:42, November 21, 2016 (UTC)

Fixed it myself...mostly. The non-rendering of certain inputted data in specific fields was limited to "blood status," "gender," and "houses," and was because code for auto-categorization in these fields had been added. Basically, any input other than those coded for would break the template, causing the data not to display. This is hugely problematic, obviously, because it limits the range and flexibility of data that can be inputted. When "male" and "female" are the only gender options code for, you can't go inputting gender statuses like "asexual," "intersex," "transgender female," etc. (not that these have come up in canon as yet). And coding for only "pure-blood" and "half-blood" excludes "Muggle," "Squib," "Muggle-born," as well as qualified inputs like "Squib (possible)" etc. It also makes it impossible to include references in data fields because inputting anything other than the exact words that have been coded for breaks the template. Basically, unless you're going to code for every single possible input, this creates a lot more problems than it solves. Not to mention that auto-categorization breaks the alphabetical ordering of categories, which I and others have painstakingly tried to implement across the wiki.

Also partially solved the issue with the template colour not rendering in the character name field by moving some code. It's still not rendering for certain themes (leaving it blank, for example), but this seems to be because those themes don't exist yet. And I don't know what to edit to add themes. Starstuff (Owl me!) 14:45, November 21, 2016 (UTC)

From the Portable Infoboxes article, I thought the themes were supposed to be in MediaWiki:Wikia.css coded as .portable-infobox.pi-theme-themename , but I don't see them in there. Are they being pulled from MediaWiki:InfoboxColours.css perhaps? --Ironyak1 (talk) 18:16, November 27, 2016 (UTC)
All articles using the different individual infoboxes (Muggle, Wizard, House-elf, etc...) have been updated toTemplate:Individual infobox with the new theme tag. For the record, new themes (such as one for MACUSA individuals) should be added to MediaWiki:InfoboxColours.css.
Going forward, the "Individual infobox" should be the only one used. However, the bot is set up to check for and convert any uses of the old infoboxes so any new articles using the old infoboxes should be brought up to date automatically. Cheers --Ironyak1 (talk) 02:14, December 12, 2016 (UTC)
*Disclosure: Some of the links above are affiliate links, meaning, at no additional cost to you, Fandom will earn a commission if you click through and make a purchase. Community content is available under CC-BY-SA unless otherwise noted.

Fandom may earn an affiliate commission on sales made from links on this page.

Stream the best stories.

Fandom may earn an affiliate commission on sales made from links on this page.

Get Disney+