Richard Riley <rileyrg...@googlemail.com> 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 " | <div id=\"menu\"> | <div id=\"sidemenu\"> | <a href=\"index.html\">Home</a> | | <a href=\"sitemap.html\">Site Map</a> | </div> | <div id=\"sidetitle\"> | Matthew Lundin | </div> | </div> | <div id=\"wrapper\">" | :postamble "</div>" | [snip] `---- The preamble is placed directly beneath the <body> 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 _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
