Template talk:Infobox

Does it serve its purpose?
I think the general idea of this is very good but I don't think, in its current form, that it serves its purpose at all.

The main reason we would want a core Infobox template is because it would make editing all infoboxes a breeze. But if we wanted to change the styles of infoboxes, as it is, we would have to edit all infoboxes that use Template:Infobox. If anything, it's a ton harder to edit now because we have three "layers": the templates, Template:Config and Template:Infobox.

I think the ONLY things that this infobox should receive as valid inputs are: These are the only 2 things that we should be allowed to control. All else should be done on this template. -- Sixorish (talk) 21:25, December 13, 2012 (UTC)
 * 1) Content. No HTML formatting (exceptions for span and divs, but preferably only content). We currently have a table structure. What if we move away from that? We would have to edit every single template... which defeats the whole purpose of having a core infobox template. The tr elements in the body parameter on Template:Infobox Item for example will not format properly if we decided to opt out of the table structure, because it's not valid HTML to have tr inside anything but a table (or thead/tbody/tfooter but that is done by the parser):   Yay formatting is broken!
 * 2) Specific style settings and/or CSS classes to control the individual needs of that template. For example the hunting place template is different.