This is a good idea.
> On Jun 25, 2015, at 12:35, Filipe Pires Alvarenga Fernandes > <[email protected]> wrote: > > Hello all, > > Based on John's comments I would like to raise an alternative. If committing > the HTML is the main reason to return to Jekyll, why not we keep the current > work-flow for a while, but make the HTML creation automatic via Travis-CI? > > I have a similar setup for some of my pages: > > https://github.com/pyoceans/seapy/blob/master/.travis.yml > > It would be a matter of creating a `.travis.yml` that executes all the > current build+publish steps. The beauty of this is that we isolate the > Markdown files from any messy HTML creating process we choose. One good side > effect is that, if we do it right, we can change to Jekyll (or any other HTML > generation process) without big changes in the original Markdown files. > > > ********************************************************** > Filipe P. A. Fernandes > Physical Oceanographer > > Email: [email protected] > > http://ocefpaf.github.io/ > ********************************************************** > >> On Thu, Jun 25, 2015 at 1:23 PM, John Blischak <[email protected]> >> wrote: >> I have no preference for jekyll v. pandoc, but I do wish we would stop >> changing our build process so often. We make it very difficult for >> instructors that only contribute a few times a year when they teach >> workshops. >> >> On Wed, Jun 24, 2015 at 2:22 PM, Greg Wilson >> <[email protected]> wrote: >> > 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. >> >> Aren't only the maintainers supposed to commit the generated HTML? >> Generating the html to view locally is similar whether we use jekyll >> or pandoc. >> >> https://github.com/swcarpentry/lesson-template/blob/c19c252bc25885eb7df3e086699a07eedbbd006f/CONTRIBUTING.md >> >> > 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. >> >> As we now make the transition to using jekyll, I'd like us to >> recognize that we have come full circle. We were originally using >> jekyll before we made the switch to pandoc. When making the decision >> to switch from pandoc to jekyll, shouldn't we at least consider the >> reasons we switched from jekyll to pandoc in the first place? What has >> changed since this blog post was written that has made us decide to >> switch back? >> >> http://software-carpentry.org/blog/2014/10/pandoc-and-gh-pages.html >> >> I understand that we want our build process to be as ideal as >> possible, but what if we focused our energy more on improving and/or >> creating lesson content? >> >> John >> >> _______________________________________________ >> 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
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
