All posts by

Hey, there. There are fundamental issues (with a significant body of research behind them) with the user interface / user experience of tabbed interfaces of any kind, which is why we are not promoting them (or any other tab analogue) as an alternative to TabView.

Themes.css was a convention used by the (then) Community Technical and Vanguard teams to isolate Portable Infobox relevant code. There's not a significant difference, beyond making it somewhat easier to find CSS blocks.

No, you can't put panels inside groups. It's a top level only element.

But I think I understand now what you're meaning. You want the tab labels of the sections to be on multiple lines. (I originally thought you meant you wanted data fields on multiple lines like that.) While it's possible to do that, my caveat is that it is not recommended. The user experience suffers a bit when you do that.

These are the design guidelines we use for making that decision.

•  https://material.io/components/tabs/#behavior
• https://www.nngroup.com/articles/tabs-used-right/

It's possible, but the images will have a loss in quality as a result. I strongly suggest not adjusting the infobox width from the default.

There is. You would want to put those in a smart group.

That's actually surprisingly simple.

<section name="Limited">
            <label>{{{limited-edition-label|Limited}}}</label>
...

The hover color is intended (so that the reader knows there's an interaction there), but you can alter the color itself with CSS.

.pi-section-tab:hover .pi-section-label {
   color: unset;
}

Notices are intended to be invisible on mobile, even those like "featured article".

There's not, and that's largely by design.

The infobox image is expected to be a reduced size and resample from what's originally supplied, and the expected UX action for image thumbnails that are not used for navigation is to expand the image to full fidelity in a lightbox; we'd rather do that than hover zoom. Image links for navigation, on the other hand, are a little trickier to understand in terms of user intent. PIs were, of course, designed to showcase the data / content and using them for strict navigation was not the primary use case.

Text links are, on the other hand, far less ambiguous. When pointing to an article, a link in the caption should give the reader / explorer much more of a signal where they're going before they click. As you alluded to, this would be true for mobile as much as desktop.

There is not a way, under the current system.

My suggestion would be to have an infobox in the lede that shows information common to all of the weapons on that page, which should push the remaining infoboxes to their respective sections. The mobile skin does not understand the atypical case where the first infobox is below the fold.

Good to know. It really shouldn't work. As I said, it's a bad idea to have that, as it looks bad to users and search engines alike.

<default>[[File:Placeholder]]</default> works inside the image tag, though it's not usually a good idea, for the same reason that having a default of "Unknown" is not a particularly good idea.

Where inside the infobox are you trying to use that tag? If it's not in a place where that tag is valid (such as where wikitext is allowed), it will give that error. 

You can't, and I wouldn't.

I've left a draft at w:c:median-xl:Template:Equipment_(Infobox)/Draft. The last step is some CSS in the theme:

.pi-theme-median .pi-data-value:only-child { flex-basis: 100%; }