Topic on Manual talk:Skin autodiscovery

It has been suggested to provide an example of how the migration was done for core skins – unfortunately it looks like it's not really possible or practical to do this:

• No one listened to me, and Modern and CologneBlue have been immediately moved to separate repositories while being converted (change in core is , new repositories are and ). This makes comparing differences hard to impossible.
• MonoBook and Vector are, most of all, not done yet; when they will be done, the diff will be full of core changes where the skins were hard-coded or just intertwined with core code, which is obviously not relevant for normal skins.
• The only non-core skin that has even been deployed on Wikimedia wikis so far, Nostalgia (which is only used by nostalgia.wikipedia.org), has always used the new way since it was recovered from the great skin purge over a year ago.

If you think this can be put in an useful form, do suggest a way or just improve the page, but I don't think it can be made useful.

Hi there!

I was the one who added the idea to show people how the Core skins got separated from the Core. The reason I find this info useful is simply that there are a number of skins, which are basically Vector clones. They look different and so, but technically they are forks of Vector. I am even maintaining some of them in a Git repo where I have the upstream Vector updates merged into the custom skins. While I think that many custom skins are based on Vector, I doubt that all maintainers use Git to get the updates easily. They are who this information is useful for.

---

Text of my draft.

(A link to an example commit has been added some time ago. I'm still not convinced it's helpful, but alright.)

It's the most helpful thing on the whole page.