Open elf-pavlik opened 10 years ago
Oh, that's cute. I like it, especially if it improves the workflow of dealing with template files / folders.
that looks nice and usefull
the only potential issue i see is a particular workshopper version being out of sync with the current workbook master. there's probably a few ways to resolve this, but we already see people who install a workshopper months before completing it and we end up having them update to take fixes that have been pushed.
I originally imagined that learnyounode and other workshoppers would be in constant flux with exercises being added, removed, adjusted, swapped around amongst different wormshoppers. In practice however, the content of the ones that I've been involved in has been almost completely stable from a user perspective with only minor adjustments along the way. So I'm not sure the sync problem is a huge one.
@rvagg good point, updates happen fairly regularly but it's usually instructional tweaks and bug fixes. rarely are new exercises added or the ordering changed. although, i really do think that "make it modular" should get broken up at some point.
yes, I think everyone agrees that "make it modular" needs to be split, or at least have one added before it
thanks for :+1: @yoshuawuyts @greelgorke and for your feedback :warning: @mikeal & @rvagg
if other people mentoring during next workshop in Berlin (on Sep, 15th) agree with it, I will suggest to participants using workbooks for Core workshoppers which we plan to work with on that day!
we could also consider adding workbook generators to workshoppers :exclamation: people would still need to create github repositories themselves to publish it and we couldn't track forks of workbooks but at least it would stay in sync...
How did this go? Curious about doing it ourselves.
What do you think about creating a workbook for each workshopper? Just with empty files which have names with a number and rest matching exercise name, eg. https://github.com/elf-pavlik/learnyounode-workbook
IMO it could minimize chances for possible confusion with creating files and naming them somehow to run verify on them. People could also later easily push their solutions to github which we could use as proof of work once we start issuing OpenBadges
workflow: