From mboxrd@z Thu Jan 1 00:00:00 1970 From: john@ankarstrom.se (John =?utf-8?Q?Ankarstr=C3=B6m?=) Subject: Re: org to static site? Date: Wed, 31 May 2017 21:51:21 +0200 Message-ID: <877f0wvm86.fsf@ankarstrom.se> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41723) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dG9eT-0007do-9E for emacs-orgmode@gnu.org; Wed, 31 May 2017 15:51:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dG9eP-0002Z0-Vo for emacs-orgmode@gnu.org; Wed, 31 May 2017 15:51:29 -0400 Received: from pusjkin.ankarstrom.se ([172.104.152.215]:49866) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dG9eP-0002YN-Lx for emacs-orgmode@gnu.org; Wed, 31 May 2017 15:51:25 -0400 Received: from vm-linux (c83-252-75-131.bredband.comhem.se [83.252.75.131]) by pusjkin.ankarstrom.se (Postfix) with ESMTPSA id 9A3CE3EC8E for ; Wed, 31 May 2017 21:51:22 +0200 (CEST) In-Reply-To: (Chunyang Xu's message of "Thu, 01 Jun 2017 01:05:04 +0800") 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" To: emacs-orgmode@gnu.org Chunyang Xu writes: > It is said that Nanoc is flexible. You can convert org mode to > HTML with Pandoc or Emacs. Nanoc supports Pandoc out of box. To > use Emacs, you need to write your own "filter" (Nanoc's > terminology, i.e., convert one format into another), for > example, > [...] > I just created my own site with it > last week. Looks fantastic! I've been searching for a good way to write blog posts in Org, and this looks very promising. Thanks for the examples, too. > The syntax highlighting on code block is provided by > htmlize.el. I noticed `org-html-export-to-html' produces > different HTML every time even the org file is unchanged at > all. It is very annoying to me. I found a work-around to avoid > it, I've always been annoyed by Org's default heading id's. The way I usually solve it is by setting a CUSTOM_ID property for every heading, but it's rather inflexible ... Does anybody know of a way to have Org produce sensible, readable id's for headings? Like #this-is-a-heading instead of #orgdcbac14. - John