From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Lundin Subject: Re: Re: Fully featured Web publishing Date: Thu, 19 Mar 2009 11:12:31 -0500 Message-ID: <87iqm58pao.fsf@fastmail.fm> References: <871vsuakc4.fsf@mundaneum.com> <87ljr2ahvx.fsf@kassiopeya.MSHEIMNETZ> <87hc1qsf2m.fsf@mundaneum.com> <878wn2a23d.fsf@kassiopeya.MSHEIMNETZ> <82eiwusamx.fsf@gmail.com> <49c1818c.16125e0a.15dc.fffffaa4@mx.google.com> <878wn1ajdn.fsf@kassiopeya.MSHEIMNETZ> <49c24adb.0637560a.24c6.7e0d@mx.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LkKr3-0007gb-FD for emacs-orgmode@gnu.org; Thu, 19 Mar 2009 12:12:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LkKqy-0007di-Pa for emacs-orgmode@gnu.org; Thu, 19 Mar 2009 12:12:24 -0400 Received: from [199.232.76.173] (port=34629 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LkKqy-0007dU-At for emacs-orgmode@gnu.org; Thu, 19 Mar 2009 12:12:20 -0400 Received: from out2.smtp.messagingengine.com ([66.111.4.26]:51495) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LkKqy-0006tY-30 for emacs-orgmode@gnu.org; Thu, 19 Mar 2009 12:12:20 -0400 In-Reply-To: <49c24adb.0637560a.24c6.7e0d@mx.google.com> (Richard Riley's message of "Thu, 19 Mar 2009 14:38:34 +0100") 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: Richard Riley Cc: emacs-orgmode@gnu.org, Rasmus Pank Roulund Richard Riley writes: >>> Why not us preamble? >>> >>> I'm not sure if its an approved way or not but has done for me for a site >>> wide addition for a while now but I must admit to not being up to date >>> with all latest and greatest innovations. >>> >>> http://richardriley.net/projects/emacs/dotorg.html > It seemed the best way to do it at the time. What is the better way? > At the time I asked about a header and footer which is fairly common > and decided to use preamble and postamble to effectively act as common > header and footer components. Prior to the "id=content" modifications > (container) I also used to introduce the "content"container using > preamble and postamble too (e.preamble opening the div and postamble > closing it). To chime in here, this is precisely how I create the menu on my website: http://faculty.valpo.edu/mlundin/ In my org-publish-project-alist I have the following: ,---- | [snip] | :preamble " | |

" | :postamble "

" | [snip] `---- The preamble is placed directly beneath the tag. I use to add a couple of extra wrapper divs, but with the new default content div, I only add one. Obviously, one could get a lot more elaborate with this. Best, Matt