GitHub Pages now runs Jekyll 2.2.0

https://github.com/blog/1867-github-pages-now-runs-jekyll-2-2-0

by xkarga00 • 12 years ago

91 17 12 years ago

stevekinney3• 12 years ago

I asked Github and Sass and CoffeeScript support will apparently also work for regular (non-Jekyll) pages on the `gh-pages` branch if you put dashes at the top of the file you want to be processed.

Source: https://twitter.com/benbalter/status/494533173699543041

Documentation: http://jekyllrb.com/docs/assets/

benbalter2• 12 years ago

To be specific, all sites are processed through Jekyll, unless you add a `.nojekyll` file. Non-Jekyll files (like HTML or CSS) are passed transparently through Jekyll untouched. Adding the dashes to the file header simply tells Jekyll to work its magic.

stevekinney3• 12 years ago

Oh awesome, I didn't realize that everything was going through Jekyll under the hood. Is this new or has it always been like that?

benbalter2• 12 years ago

Yep. The `.nojekyll` option has been around since 2009: https://github.com/blog/572-bypassing-jekyll-on-github-pages

maximumoverload• 12 years ago

Sorry if it's a dumb question. But how does this workflow work?

Are the html/js/css generated on my local pc, or on the github server? I don't get it.

(I have no experience with Jekyll. I have some static pages on github pages.)

stevekinney3• 12 years ago

I believe the files are generated on Github's servers. You can install Jekyll locally to get the same workflow locally.

swanson• 12 years ago

When you run Jekyll, it spits out an `_site` folder - which is the generated HTML/CSS/JS of your site. Locally, when you run the Jekyll server it generates the site and then serves from that folder for you to preview.

With GitHub pages, you push a repository containing the Markdown files, but not the full generated site. On GitHub's server it generates the site and then serves it. You will want to add the `_site` folder to your `.gitignore`.

ionforce• 12 years ago

I was planning to write a guide on this... you know, some day...

From what I understand, Jekyll (the web site builder) automatically runs on their end. And, as the other poster mentioned, you can simulate the result of this by running a local copy of Jekyll on your local checkout.

But in the end, only the Jekyll input configuration/source data is required. The rest is optional.

omarrr• 12 years ago

Pages are generated on Github servers. As somebody mentioned you can run Jekyll locally to preview the rendered pages or simply push to github and review online.

baddox• 12 years ago

It looks like you just commit plaintext files (or markdown, or any of several other formats) into your repo and they get built into HTML by jekyll and hosted as articles on your site.

http://jekyllrb.com/docs/structure/

archagon• 12 years ago

As an aside, if your Jekyll workflow requires custom plugins (which Github doesn't support), you can always generate the site locally and push the contents of the _site folder to Github.

linuxydave• 12 years ago

While I don't host my Jekyll blog on Github I do something similar with my Jenkins server. Webhooks + Jenkins = CI/CD for my blog :)

kehers• 12 years ago

As said, they are generated on Github. There are online content editors like http://prose.io and http://tinypress.co (for Github page blogging) though.

joshschreuder• 12 years ago

Thanks for the links, I've been looking for something a bit more editor GUI like rather than editing files.

tdicola• 12 years ago

Awesome! Been looking forward to this to play with some of the new stuff like collections.

bachmeier• 12 years ago

I was just yesterday wondering why Kramdown wasn't the default. Among other things, it supports Mathjax. Then I came across this in the announcement:

"Kramdown as the default Markdown engine - In addition to better error handling, Kramdown supports MathJax, fenced code blocks, nested lists, tables, and much more."

GitHub Pages now runs Jekyll 2.2.0

Related Stories