Board Thread:New Features/@comment-2240397-20161117114915/@comment-26402117-20161119144948

I've noticed there's a few things that were suggested that can be achieved with CSS, so I may as well collate a set of short CSS and template solutions here:

I can see how its convenient to be able to do more radical infobox layout changes in the infobox builder, but there is big benefits to building a custom solution in the wiki's CSS stylesheets and then applying it to the infobox conveniently with.
 * left-hand side infoboxes (CSS)
 * two images in the infobox (template)
 * header backgrounds:

I think Warframe have implemented wide infoboxes in this way. The new markup only has tabbers in Oasis and the left-right behaviour in Mercury, so I imagine the reverse ( through an container attribute like ) is good feedback for staff.

I can see some serious convenience to doing header backgrounds through the template styling suggested by Shareif, but at that depth of theming it may be more convenient to create a new theme and assign the backgrounds with CSS.

I also reckon the end result of custom article styling is something that shouldn't subsume infobox theming with too many template declarations (noting that superhero and user infobox colors are a more niche infobox theming). You may end up with users uploading custom files just for their user infoboxes.

On image width, I believe its standardised to the infobox theme by design and is discrete from the article. This differs from the previous status quo on Fandom in articles. I would reckon it ensures visual consistency between the articles that are using the same type of infobox, and gets admins to simply implement consistent image widths for infoboxes.

If an article image is added that is smaller than the infobox width, I believe it gets centered (possibly transparent images of superheroes with different widths and the same height). I've seen 300px infoboxes before (which I reckon are the largest nice size that doesn't constrain Oasis), so there's a need there which Fandom is to address.

I think I've gone a bit off-topic to general PI feedback, lol.