From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Lundin Subject: Re: [Patch] HTML export -- Allow to change the name of the global DIV Date: Mon, 14 Mar 2011 09:11:06 -0400 Message-ID: <87y64hludx.fsf@fastmail.fm> References: <80y64nxgxr.fsf@somewhere.org> <874o7aoxxr.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=36371 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pz7YE-0006t9-Fb for emacs-orgmode@gnu.org; Mon, 14 Mar 2011 09:11:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pz7YC-0004BL-Vy for emacs-orgmode@gnu.org; Mon, 14 Mar 2011 09:11:10 -0400 Received: from out5.smtp.messagingengine.com ([66.111.4.29]:48378) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pz7YC-0004BC-Oc for emacs-orgmode@gnu.org; Mon, 14 Mar 2011 09:11:08 -0400 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: =?utf-8?Q?S=C3=A9bastien?= Vauban , emacs-orgmode@gnu.org Bastien writes: > Are there other hardcoded HTML classes/ids that the user might want to > customize? If so, can we think about a simple way to define all of them > at once? The id/class values are hardcoded in several different places and generated in different ways in org-html.el, so I think the only practical solution, for now, would be to create variables for each one (or perhaps an alist that encompasses all of them). [Slightly OT dreaming] Over the long-term, it would be nice to give the user a simple way to control not only classes and ids, but also the placement of structural divs and other tags. Perhaps we could develop some sort of templating system, allowing the user to create an custom html skeleton which is then fleshed out with data from the org file. The user might then customize which tags, if any, should enclose, say, a level one outline tree. Properties and tags in an org file might be used to specify the use of alternate templates within particular sections of the document. This would have several benefits: 1. It would allow users to export html to an arbitrary tag structure. One might, for instance, create static pages that conform to the structure/styling of an existing web site. Or one might have different types of pages within a single, org-generated website. 2. It would allow simple, clean html when exporting small snippets. Currently, when calling C-u M-x org-export-region-as-html, the output contains a number of hard-coded divs, classes, and ids. This makes it difficult to integrate such snippets into another html file.

A section

Some text.

3. It would allow users to try out the new html5 tags (
,
,