emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ian Barton <lists@wilkesley.net>
To: emacs-orgmode@gnu.org
Subject: Re: Org as a static site generator
Date: Mon, 01 Apr 2013 20:09:19 +0100	[thread overview]
Message-ID: <5159DB5F.2050307@wilkesley.net> (raw)
In-Reply-To: <B40039897778456F8002DC0E7930F303@gmail.com>

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.

  reply	other threads:[~2013-04-01 19:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01 11:12 Org as a static site generator David Engster
2013-04-01 11:29 ` Vincent Beffara
2013-04-01 11:54   ` David Engster
2013-04-01 12:08     ` Vincent Beffara
2013-04-01 19:09       ` Ian Barton [this message]
2013-04-05 16:02         ` Christopher Allan Webber
2013-04-06  8:01           ` Ian Barton
2013-04-06 15:15             ` Christopher Allan Webber
2013-04-06 16:13               ` Ian Barton
2013-04-10  9:17 ` 'Mash (Thomas Herbert)
2013-04-10 16:59   ` Bastien
2013-05-27 23:48     ` François Pinard
2013-05-29 13:16       ` Eric Schulte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5159DB5F.2050307@wilkesley.net \
    --to=lists@wilkesley.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=ian@manor-farm.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).