[jordanlev]

If you're interesting in this, you should also check out Octopress, which sits on top of Jekyll and provides a nice default theme, handy addons (for google site search, disqus comments, twitter/facebook sharing, etc.), and deployment scripts.

http://octopress.org/

[rcfox]

Does GitHub support Jekyll plugins? I doubt they'd be willing to run arbitrary code for everyone...

[jordanlev]

Well, they're not really Jekyll plugins -- just Javascript plugins on the front-end (hence disqus comments instead of your own database of comments, google custom search instead of your own internal search engine, etc.)

[rcfox]

Sorry, I was referring to these plugins: http://octopress.org/docs/plugins/

[jordanlev]

Oh, I get it. Those plugins are "compile-time" -- so they happen during the HTML generation process, before going up to github -- all github ever sees is static HTML and CSS files.

[rcfox]

I played with Jekyll on GitHub several months ago, but as I recall, you commit your source files to the repo, and the GitHub would run Jekyll to compile them to HTML. (And send you an annoying message every time that it was successful...)

[calloc]

But github does that part for you. You push up the raw files AND Github runs Jekyll and generates the HTML files.

[mkopinsky]

Could you have this as a two stage process? Make changes to files, push to my repo, repo hook runs jeckyll, commits new static assets, and pushes to github? This does require using a central server other than github I guess, though...

[josegonzalez]

No, it doesn't if you're using GitHub Pages. Only if you're using your own repository.