Wiki 24
Advertisement
Forum: The Situation Room > New mobile-friendly infobox


Wanted to get everyone's thoughts on switching over to the new Wikia infobox - much more device friendly and IMO a visual step up from the all-purpose one we currently use. To see it properly you'll need to copy everything on my stylesheet to your own; some of it won't look right otherwise. Examples here --Pyramidhead (talk) 05:57, September 1, 2016 (UTC)

They look good, a lot better and we definitely need to do something about our mobile skin. A couple of questions:
  1. Is it possible to specify the width of the pictures in the infobox?
  2. Do we need to make lots of infoboxes for each different use? Is it possible to keep it as one template?
  3. Not sure on the "previous" and "next" fields on the events infobox - their placement for one, and really if they're appropriate (in what sense are the events "consecutive" to each other, in universe?)
But generally, really good improvement! Great work, I meant to do something about portable infoboxes ages ago--Acer4666 (talk) 09:42, September 1, 2016 (UTC)
Not really possible to set image width, probably the biggest downside. But with theming we can have a few different width/height settings to account for weird situations - check out the Norway example down at the bottom now. I haven't tried combining them all into one template yet but I think it would be a huge hassle - the episode one at least definitely needs to be its own. Should be simple to convert pages by category though with the bot. As for the event template - I was thinking of it as a timeline companion; the major incidents aren't directly consecutive but they do let you navigate through the course of the show in an interesting way. There aren't a whole lot of events at the moment so it should be pretty easy to put together the correct order. Could certainly move them elsewhere in the template though --Pyramidhead (talk) 10:33, September 1, 2016 (UTC)
One of my concerns is how much extra vertical space these will take up. Compare our current Solarz page to the new version. The page is almost twice the height with a load of empty space. Do the fields need to be stacked on top of each rather than "Key": "value" on the same line?--Acer4666 (talk) 14:11, September 1, 2016 (UTC)
Modified it - so we can independently set both stacked fields or not and group subheadings or not based on the situation. Obviously it doesn't make sense to have three different subheadings for someone like Solarz who only has four relevant fields, so the way it is now the infobox defaults to side-by-side and no subheadings except for "Behind the scenes." Actually, it might be good to make "Behind the scenes" collapsed by default - it kinda helps ensure that the whole top part of every article is strictly in-universe, while you can still see all of that up front if you choose to. --Pyramidhead (talk) 23:48, September 1, 2016 (UTC)
That's much better where you can group subheadings. I'd be against hiding the BTS info by default, I think it may not be immediately obvious to some visitors that there's more info that you need to click on something to reveal.
I still think the spacing of the fields is a little inefficient with space. I played around with
.portable-infobox .pi-item-spacing {
    padding: 5px 10px;
}
Altering those numbers to have less padding, and got something a little bit more space efficient in the way that the current sidebars are.--Acer4666 (talk) 10:40, September 2, 2016 (UTC)
If you want you could add the pi- classes to the site CSS - shouldn't affect anything already on the articles. --Pyramidhead (talk) 19:23, September 3, 2016 (UTC)
I'll put it on when we've made a decision on how to do these infoboxes. I set the padding to 2px 8px on my css, and think it makes the sidebars more compact.
I also think we don't need to split them into loads of templates. The episode one can be a separate template as it is with the current sidebars, but having one flexible template for other things is useful. How far will we go to split it up...Objects? Animals? Copmuter programs? Mr. Floppy? These all benefit from have a flexible template that can adapt. How many fields will need to be present in different contexts? The ability to manage what headers appear on a per-use basis means we can have all the fields on the one template--Acer4666 (talk) 23:18, September 3, 2016 (UTC)
I guess I don't see the upside of continuing to use one template for everything - can't tell you how many times I tried to add a field and had to scroll down for ages, or forgot to account for how it would impact other article types, or had to come up with some ridiculous workaround like the "OOU line" situation. It will be great to be able to know exactly what needs to go on each template, and if new ones are called for we'll be able to add them in seconds. As far as spacing honestly I think it works best as it currently is - tried 2 8 like you said but it makes the group bars way too skinny, and on stacked layout the fields seem to run together. --Pyramidhead (talk) 23:33, September 3, 2016 (UTC)
Tried it some more and 2 8 is okay actually, may take some getting used to though --Pyramidhead (talk) 23:44, September 3, 2016 (UTC)
Seems to look best with Npx (2n)px - I like 2 4, 3 6 --Pyramidhead (talk) 23:53, September 3, 2016 (UTC)
OK cool. Yeah the small padding is how the sidebars currently are, so it should look ok. There's surely some way to make the .pi-headers have extra padding by themselves? I don't know the css well enough to work it out.
I still don't see a strong enough case for splitting the sidebar template. You're saying scrolling to the bottom of the template is a huge undertaking, but copying and pasting all the code to a separate template and altering the different fields takes "seconds"? I don't understand the "account for how it would impact other article types" (can you give an example of the problem you're describing?) and the OOU line is the same as this "behind the scenes" header that the new template has.
Having multiple ones also means that when someone creates an article they have to go through all of the different infobox templates to work out which one is appropriate for the article they're making. That's on a per use basis (until that editor is intimately familiar with the different ones), rather than adding extra fields which happens relatively infrequently--Acer4666 (talk) 10:32, September 4, 2016 (UTC)
Advertisement