Re: proposal to simplify the website

Jekyll [1] (as made famous by github pages [2]) has to be one of the more
widely used at this point. Content in html or e.g. markdown, with page
templating etc. Not very hard to set up, plus a bunch of people know it now
due to github pages integration.

We could easily set up a post-commit hook or cron job to pull the site down
and run jekyll.

Cheers

Tom

[1] https://github.com/mojombo/jekyll
[2] http://pages.github.com/

On 26 April 2013 05:06, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:

> Kris,
>
> How many changes go everywhere ?
>
> Any suggestions on a simple templating system ?
>
>
>
> Dave Cramer
>
> dave.cramer(at)credativ(dot)ca
> http://www.credativ.ca
>
>
> On Thu, Apr 25, 2013 at 1:48 PM, Kris Jurka <books(at)ejurka(dot)com> wrote:
>
>>
>>
>> On Thu, 25 Apr 2013, Dave Cramer wrote:
>>
>> > The machines that host the sites are not setup with CMS. There isn't
>> that
>> > much content and every CMS I've ever seen has a learning curve. This is
>> > simple, store the html in git, pull it to the machine
>> > The biggest part of the site is the API docs, which is generated with
>> > javadoc.
>> >
>>
>> My concern is that without any templating system at all, some simple
>> changes are going to require a copy and paste into every single page.
>> Don't we need something beyond plain static pages that are directly
>> edited?
>>
>> Forrest is kind of a dead project at this point, but there are a ton of
>> other templating systems that generate static pages that are much more
>> lightweight than Forrest. Shouldn't we consider one of them?
>>
>> Kris Jurka
>>
>
>