This is excellent! I've used Jekyll before and love its simplicity, and I really detest pandoc, and it never felt correct to commit the generated html in addition to the markdown.
This will make contributing a lot more simple, convenient and natural. ~ Tim On Wed, Jun 24, 2015 at 03:22:56PM -0400, Greg Wilson wrote: > Hi everyone, > > The most common complaint about our current lesson template is that > it requires people to commit generated HTML as well as Markdown > source to the repository's gh-pages branch. After a bit of > tinkering, we have put together a variation on the template that > uses Jekyll (the same tool that GitHub uses), so that people will > only need to commit the Markdown [1]. We've blogged about this at > http://software-carpentry.org/blog/2015/06/using-jekyll-for-lessons.html > - we'd be grateful if you could tell us whether it's worth making > the change. > > Thanks, > Greg > > [1] People using R Markdown or Jupyter Notebooks will still need to > convert from those formats to plain old Markdown [2], then commit > that Markdown to the repo, but they have to do that now as well. > > [2] We haven't built this bit yet - we want to see if the switch to > Jekyll is worthwhile first. > > -- > Dr. Greg Wilson | [email protected] > Software Carpentry | http://software-carpentry.org > > > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
