Configuration updates #21
Conversation
This change allows Jekyll to build presentation content outside the GitHub Pages environment, for example on Netlify. Per https://www.netlify.com/blog/2017/05/11/migrating-your-jekyll-site-to-netlify > If you have generated your Jekyll site using GitHub pages or forked a template there is a good chance you do not have a Gemfile. This is because GitHub pages will infer dependencies for you. If you would like to build your project outside of GitHub a Gemfile is needed and simple to create.
> Starting May 1st, 2016, GitHub Pages will only support kramdown, Jekyll’s default Markdown engine – https://github.blog/2016-02-01-github-pages-now-faster-and-simpler-with-jekyll-3-0 GitHub Pages currently runs on Jekyll 3.7.4: https://pages.github.com/versions
|
Thanks for this. 🎁 About the Markdown engine switch: Does that impose any breaking changes? If so, I would release it as a major version. |
|
I was about to create a PR to add a docker-compose file to make running locally easier. Does that impact this at all? |
|
The kramdown parser bills itself as supporting a superset of Markdown constructs handled by other engines, so if anything, is should handle more things gracefully, not less. I don't think it's necessarily a breaking change, so I'm not sure this alone would warrant a major version bump, but if you include #22, you might want to do that anyway. |
Guess it depends whether people are more likely to already have Docker available locally, or a local Jekyll install. In the latter case, running this is as simple as cloning & But adding a Docker file wouldn't hurt and might be handy for those that know what to do with it. |
|
Great, I'm merging this and #22 and will release it as a major. Thanks, guys. |
This PR tweaks a few settings in the configuration:
Gemfileto permit builds on hosts that do not infer dependencies (like Netlify)_sitefolder clean