On Tue, Nov 10, 2015 at 2:39 PM, Isarra Yos <[email protected]> replied:
> On 10/11/15 21:59, S Page wrote: > >> The tutorial is pretty good IMO, the problem is it forced repetition > > > This may just be because I did it at three in the morning; it probably > doesn't need that much. I'll see if I can clean that up a bit. >.> 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] > Also you can probably delete any random things that say 'composer' or '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 _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
