Also +1, big fan of Jekyll.
On Wed, Jun 24, 2015 at 10:42 PM, David Pugh drobert.p...@gmail.com wrote:
+1
On Thu, Jun 25, 2015 at 12:11 AM, Joshua Ryan Smith Ph.D.
joshua.r.sm...@gmail.com wrote:
[image: ]
On Jun 24, 2015, at 19:00, Ethan White et...@weecology.org wrote:
+1
On
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
On Thu, Jun 25, 2015 at 10:14 AM Raniere Silva rani...@ime.unicamp.br
wrote:
...
6. The workflow for creating and publishing lessons
should be authentic, i.e., the way people write and
publish lessons should be a way they might use to
write and publish research
On 2015-06-25 12:39 PM, Matt Davis wrote:
I think moving to GitHub's automatic rendering would be a workflow
improvement, but I would like to hear about what's now changed that
would allow us to move back to Jekyll.
The primary change is the volume of complaint:
1. Committing HTML is
At http://software-carpentry.org/blog/2014/10/pandoc-and-gh-pages.html
Greg wrote:
Here's a summary of the forces we need to balance:
1. People should be able to write lessons in Markdown. We choose Markdown
rather than LaTeX or HTML because it's easier to read, diff, and merge;
As part of the move, I'd like to move the validator to use a parser that
better understands Jekyll/Kramdown internally. If anyone has experience
manipulating kramdown-style markdown in python, I'd be curious to hear
recommendations.
(In particular, for the special markdown extensions that aren't
-1 on the change, and thank you to John Blischak for writing a more
eloquent version of the response that I was struggling to write.
On Thu, Jun 25, 2015 at 9:24 AM John Blischak jdblisc...@uchicago.edu
wrote:
I have no preference for jekyll v. pandoc, but I do wish we would stop
changing our
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
gvwil...@software-carpentry.org
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:
Hi everyone,
This thread looks set to run for a while, so let's move discussion to
https://github.com/swcarpentry/lesson-template/issues/279 - please add
further comments there rather than sending to 'discuss'. I'll archive
discussion to date in that issue this evening or first thing tomorrow
Not advocating for or against moving to Jekyll here, but I think Greg's
comment about trailing styles highlights another issue. tl;dr use redcarpet
instead of kramdown.
If we tell people they can use markdown they probably think
Github-flavored markdown, e.g. that they write fenced code blocks
11 matches
Mail list logo
