emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matthew Lundin <mdl@imapmail.org>
To: Richard Riley <rileyrgdev@googlemail.com>
Cc: emacs-orgmode@gnu.org, Rasmus Pank Roulund <rasmus.pank@gmail.com>
Subject: Re: Re: Fully featured Web publishing
Date: Thu, 19 Mar 2009 11:12:31 -0500	[thread overview]
Message-ID: <87iqm58pao.fsf@fastmail.fm> (raw)
In-Reply-To: <49c24adb.0637560a.24c6.7e0d@mx.google.com> (Richard Riley's message of "Thu, 19 Mar 2009 14:38:34 +0100")

Richard Riley <rileyrgdev@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> &#124;
| <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

  parent reply	other threads:[~2009-03-19 16:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 16:04 Fully featured Web publishing Sébastien Vauban
2009-03-18 16:57 ` Sebastian Rose
2009-03-18 21:20   ` Sébastien Vauban
2009-03-18 22:38     ` Sebastian Rose
2009-03-18 22:56       ` Rasmus Pank Roulund
2009-03-18 23:19         ` Richard Riley
2009-03-19  7:46           ` Rasmus Pank Roulund
2009-03-19  8:28             ` Richard Riley
2009-03-19  9:43             ` Sébastien Vauban
2009-03-23 11:36               ` Sébastien Vauban
2009-03-23 13:50                 ` Taru Karttunen
2009-03-19 10:37           ` Sebastian Rose
2009-03-19 13:38             ` Richard Riley
2009-03-19 15:03               ` Sebastian Rose
2009-03-19 16:12               ` Matthew Lundin [this message]
2009-04-18  9:23 Tomas Hlavaty
2009-04-18 11:04 ` Carsten Dominik

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=87iqm58pao.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus.pank@gmail.com \
    --cc=rileyrgdev@googlemail.com \
    /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).