[nilved]

Quite disappointed the developers have decided to stick with Liquid templates. With such a handicapped and useless template language, jekyll is a non-starter for any website more complex than something you could trivially write yourself.

[parkr]

For security reasons, we have no choice. It's specifically designed not to allow execution of arbitrary Ruby code. GitHub wouldn't run Pages if Jekyll didn't have this guarantee.

[wasd]

I don't use jekyll and have a fairly limited knowledge of pages but doesn't jekyll output static html? Even if you used a dynamic language to create the project, wouldn't it not matter because the end result will be static?

[nilved]

You'd be able to run arbitrary Ruby code during the compilation of your site. GitHub uses Liquid templates as a pseudo-sandbox: it's deliberately a weak system to prevent abuse. But it's lazy, because there are many other solutions that don't take away from user experience.

[benatkin]

They could probably use Docker and not allow network access and limit the resources (including time) to do a build. I don't know if their business model would support it but it's technically possible.

[benatkin]

With Jekyll and GitHub pages people don't have to run any code on their own computer systems. Combined with GitHub for mac and windows, this counts for something in my book.