From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Barton Subject: Re: Org as a static site generator Date: Mon, 01 Apr 2013 20:09:19 +0100 Message-ID: <5159DB5F.2050307@wilkesley.net> References: <87y5d2cxmz.fsf@engster.org> <3673494705AD49FDB17566C5302436B0@gmail.com> <87ppyecvpb.fsf@engster.org> Reply-To: ian@manor-farm.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:52785) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UMk6e-0007AH-8J for emacs-orgmode@gnu.org; Mon, 01 Apr 2013 15:09:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UMk6c-0003OL-7Q for emacs-orgmode@gnu.org; Mon, 01 Apr 2013 15:09:24 -0400 Received: from mail2.wilkesley.net ([109.74.196.44]:57310 helo=li40-130.members.linode.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UMk6c-0003O1-2T for emacs-orgmode@gnu.org; Mon, 01 Apr 2013 15:09:22 -0400 Received: from [192.168.0.207] (unknown [46.33.134.31]) (Authenticated sender: lists@wilkesley.net) by li40-130.members.linode.com (Postfix) with ESMTPSA id 26C306B5D04 for ; Mon, 1 Apr 2013 20:09:20 +0100 (BST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org On 01/04/13 13:08, Vincent Beffara wrote: > Yes, I mean, I know which html you need for that, simply within o-blog you need to manage between relative paths, absolute paths, canonical paths and so on in the template, to match the right section, - mainly it should be a matter of let-ing the right variable to the right value at the right point in the template and catching it when generating the toc, but I never took the time to get it right ... >> I've also just found this, which uses Org only as a markup tool and >> Jekyll to generate the site: >> >> http://orgmode.org/worg/org-tutorials/org-jekyll.html > I had a look at the too, but it felt just a little bit too convoluted compared to managing everything from Org. Besides, it seems to lose fontification of code snippets and the like? > > /v > As the original author of that page, I agree that using Jekyll is convoluted, but it gives you much more control. However I now use Pelican: https://pelican.readthedocs.org/en/3.1.1/ There are a few reasons for this. Pelican is written in Python, which I find easier to hack on. It is more flexible than Jekyll, which I found hard to get to work the way I wanted with categories and tags. I wrote a yaml importer for Pelican so I could use my old jekyll posts. However, Pelican understands Markdown, which I think the new exporter supports. So my work flow now is Emacs-> export as html -> run Jekyll Ian.