On Tue, Nov 10, 2015 at 2:39 PM, Isarra Yos <zhorishna(a)gmail.com> replied: D'oh, I'm sorry, I meant the on-wiki three-part skinning thing that's been around for a while and introduces in a nutshell as "This page is part 1 of a three-part tutorial". Re: https://www.mediawiki.org/wiki/User:Isarra/How_to_make_a_motherfucking_skin I have a dream where both extensions/BoilerPlate and skins/Example are a script that prompts for your extension or skin name, clones it into YourProject, sets up the example as a non-master remote (so you can track updates to the skeleton), and does the mindless file renames and search and replace to YourProjectName. [1] 'grunt' or whatever in the filenames. Not really sure why those are in the example skin. That's a bit confusing. Nope, they're gold. It means you can run npm test and composer test and automatically have a growing set of basic tests and coding checkers run for you. See BoilerPlate's README.md [1] , maybe the same instructions should be copied to skins/Example. The good advice in your Step 4 and Testing could fit well into Skinning Part 3. [1] Legoktm built such a thing for Wikimedia libraries, https://github.com/wikimedia/generator-wikimedia-php-library#readme [2] https://github.com/wikimedia/mediawiki-extensions-BoilerPlate#readme -- =S Page WMF Tech writer

On Tue, Nov 10, 2015 at 6:31 PM, Isarra Yos &lt;zhorishna(a)gmail.com&gt; wrote: We have a Yeoman generator for libraries ( wikimedia/generator-wikimedia-php-library <https://github.com/wikimedia/generator-wikimedia-php-library>), would be nice to have one for skins as well.

On 12/11/15 03:39, S Page wrote: Yeah, sorry. What I mean to say in particular is the layout as is needs to go - what I'm thinking at this point is ideally we'd have a barebones just-some-steps thing on top, with subpages of specific details and stuff clearly linked from there. A major problem I see with Manual:Skinning right now is it is incredibly overwhelming, with no indication which parts are actually important (in part because which parts are actually important has also changed so much recently). Someone thinking to make a skin can easily look at it and just balk right there, when really the steps they need to follow are much more straight forward, and they only need to worry about some of this anyway. https://www.mediawiki.org/wiki/User:Isarra/How_to_make_a_skin is based much more on a visual approach, where ideally folks will be looking at the page and then just styling whatever they see - including all these things, which appear there on the page. Why list all the things when they're right there on the page (though some is probably a good idea just as an example, with the link to the full list), when a lot of them don't even need any styling, when they're all actually built-in now? Because yes, people should definitely be starting from the example skin. That's what it's for. Ideally with the whole autogenerated alreadynamed skin downloads. But of course just looking at the actual tutorial, people can't actually see the skin, so it really would also need illustrations to really pull that off anyway. Eh.