I don't know if this is related, but I'm gonna mention it here anyway because the timing sort of lines up: the display of images over on Wikisource for PDFs in preview mode also got dramatically worse ~2 days or so ago. The scaling went crazy and it started taking portrait-style PDF page images and displaying them in boxes. e.g. a 724x1124 or so image (correct) became ~1000x1000 (bananas).

@Tgr : I can't speak to if this ticket was correctly categorized for Resource-Loader or Platform. But to be clear, of course there needs to be a way to refer to a skin, and somehow removing that idea was never the point of this ticket. Nor was having to update every string that points at Vector or Vector 2022. I think the original ticket was pretty clear: it's a very common pattern to have an internal identifier and a localized string. For existing skins, they'd be grandfathered as having the exact same name. But if there was some sort of internal name to external name mapping, then it'd be trivial to call the newest skin Delta or Phi or whatever internally, and then change the string it's mapped to at the press of a button while all the internal code points out skin Delta. The mapping would be stored in a config file or a DB table somewhere. If that's not a priority, fine, but I just want to be clear what is being asked for.

Just noting that it's been over a month, and it still appears to be down. Any updates from Mohr Siebeck?

At risk of scope creep... while we're here, it'd be nice to also re-examine gallery sizes. See this conversation on Wikitech-l :

• https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/R3ZN5DMGW55AHOQXXCZVQC5CULGQFG67/

• Why use a description list for a poem?

Well, truth be told, I actually started with the poem tag ( example diff ) and switched over to colons for indentation because I found several other pages on Wikisource that used colon indentation for poetry. I didn't find an actual style guide on how to handle poetry from some quick searching, so modified what I was doing for consistency with those other pages. Colons are pretty simple & easy, so I don't think it's necessarily a problem. And the dl / dd tags have been horribly misused for indentation on talk pages for ages, so I figured it wouldn't be a novel misuse at least.

Just to be clear on the loose outlines of what's being proposed, since this brings up the potential confusion between a skin name / skin key disconnect, I think that taking on and accepting that confusion directly is what's being proposed. Which might well still be too much to ask! Ideally, there'd be an internal codename key that is static, known mostly to developers, and used to refer to the skin, and then a display name which could be anything and changed on a dime. (And probably best to intentionally make the internal codenames different from the start so as not to surprise developers... they'd know the 2026 skin as Aardvark or whatever which it'd stay forever internally, the 2031 skin as Bittern, the 2036 skin as Crane, etc.
The old skins can be grandfathered in with names = keys, of course.)