emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <zthjwsqqafhv-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Fully featured Web publishing
Date: Wed, 18 Mar 2009 17:04:27 +0100	[thread overview]
Message-ID: <871vsuakc4.fsf@mundaneum.com> (raw)


I'd like to use Org exclusively for composing and then publishing my Web site.
I've done it so far with Emacs Muse, but I have a strong deepish attraction to
go the Org way, for many different reasons you must be aware of -- more than I

The features I need are:

- Conditional CSS [if IE]
- Favicon
- JavaScript for Google Analytics
- Date in the copyright
- Contextual navigation menu

I'll come back into more details to these.

All of these were coded in the header or footer of each page with Muse. What
was good, is that I could write:

--8<---------------cut here---------------start------------->8---
(setq muse-project-alist
         ("~/Public/Websites/Muse/source/" :default "index")
         (:base "xhtml"
                :path   "~/Public/Websites/Muse/publish/"
                :header "~/Public/Websites/Muse/source/header.html"
                :footer "~/Public/Websites/Muse/source/footer.html"))))
--8<---------------cut here---------------end--------------->8---

Hence, specifying file names instead of file contents for both the header and
footer. This is good, as I don't have to change my .emacs file every time I
wanna change the way my pages have to look like. Such a feature would be nice
for Org as well. Is it scheduled?  Can we achieve the same result otherwise?

Regarding the above features:

- Conditional CSS [if IE]

  Can be coded in the common header string. OK.

- Favicon

  Can be coded in the common header string -- if it's a common one for all my
  Web site. How can we specify on a per page basis?  This more or less comes
  down to the recent addition of the `keywords' and `description' meta tags
  (thanks Carsten).

- JavaScript for Google Analytics

  Can be coded in the common header string. OK.

- Date in the copyright

  Can be coded in the common footer string. Well, it would be nice if it could
  be computed somehow, and be for example (depending of user prefs) the date
  when the file (or page) has been changed.

  Hence, it's not specifically a data that's common to every page of my Web
  site. How can we do this?

  This is what I did with Emacs Muse, embedding Emacs Lisp in the footer:

--8<---------------cut here---------------start------------->8---
  Last Updated:
          (format-time-string muse-footer-date-format
                              (nth 5 (file-attributes (muse-current-file))))
--8<---------------cut here---------------end--------------->8---

  but I think this is not currently possible with Org, right?  Is there some
  other solution?

- Contextual navigation menu

  Finally, the only real problem that I see (the above being nice-to-have's)
  is the following: I want to have a common navigation menu, but whose current
  page is highlighted. To do so, I just have to add the class `current' to
  the current entry, but this means the navigation menu is not constant
  between pages!

  I did that with Muse doing so:

--8<---------------cut here---------------start------------->8---
  (setq nav-menu '((\"Home\" .            \"index.html\")
                   (\"About Me\" .        ( (\"CV\"             . \"curriculum-vitae.html\")
                                          (\"PGP Public Key\" . \"pgp-public-key.html\")
                                          (\"Contact Me\"     . \"contact-me.html\")))
                   (\"Resources\" .       ( (\"Ubuntu\"         . \"ubuntu.html\")
                                          (\"Emacs\"          . \"dot-emacs.html\")))))
--8<---------------cut here---------------end--------------->8---

  and in the footer file:

--8<---------------cut here---------------start------------->8---
            <div id=\"navigation\">
--8<---------------cut here---------------end--------------->8---

  with the following (ugly -- caus' it should be written in a recursive way!)
  definition for `my-muse-generate-nav-menu':

--8<---------------cut here---------------start------------->8---
        (defun my-muse-generate-nav-menu ()
          (let* ((html-menu "")
                 (cur-path-muse (muse-current-file))
                  (replace-regexp-in-string "\\.muse" ".html" cur-path-muse)))
            (setq html-menu "<ul>\n")
            (while nav-menu
                (if (not (listp (cdr (car nav-menu))))
                    (setq html-menu
                          (concat html-menu
                                  "<li><a href=\"" (cdr (car nav-menu))
                                  "\" title=\"" (caar nav-menu) "\""
                                  (if (string-match
                                       (concat ".*" (cdr (car nav-menu)) "$")
                                      " class=\"current\""
                                  ">" (caar nav-menu) "</a></li>\n"))
                    (setq html-menu
                          (concat html-menu
                                  "<li>" (caar nav-menu) "\n" "<ul>\n"))

                    (setq nav-submenu (cdr (car nav-menu)))
                    (while nav-submenu
                      (setq html-menu
                            (concat html-menu
                                    "<li><a href=\"" (cdr (car nav-submenu))
                                    "\" title=\"" (caar nav-submenu) "\""
                                    (if (string-match
                                         (concat ".*" (cdr (car nav-submenu)) "$")
                                        " class=\"current\""
                                    ">" (caar nav-submenu) "</a></li>\n"))
                      (setq nav-submenu (cdr nav-submenu)))

                    (setq html-menu (concat html-menu "</ul>\n</li>\n"))))
                (setq nav-menu (cdr nav-menu))))
            (setq html-menu (concat html-menu "</ul>"))
--8<---------------cut here---------------end--------------->8---

  How can I do such a thing in Org?

THANK YOU VERY MUCH for all the hints or help you can provide me with!

I really want to go the Org way for all my composed stuff...

Best regards,

Sébastien Vauban

Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

             reply	other threads:[~2009-03-18 16:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 16:04 Sébastien Vauban [this message]
2009-03-18 16:57 ` Fully featured Web publishing 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

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:

  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=871vsuakc4.fsf@mundaneum.com \
    --to=zthjwsqqafhv-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \


* 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


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).