From: Bernt Hansen <bernt@norang.ca>
To: mdl@imapmail.org
Cc: emacs-orgmode@gnu.org
Subject: Re: Org publish hierarchies and style variable
Date: Wed, 29 Oct 2008 13:59:33 -0400 [thread overview]
Message-ID: <873aifs2nu.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <87d4hj9zvm.fsf@fastmail.fm> (mdl@imapmail.org's message of "Wed\, 29 Oct 2008 10\:37\:01 -0500")
mdl@imapmail.org writes:
> A question: The org-publish tutorial recommends the use of template
> files for setting the relative link to the stylesheet for nested
> directories to be published to html.
>
> - http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.php
>
> E.g.,
>
> For first level directories such as
>
> ~/org/
> |- css/
> | |- stylesheet.css
> |- index.org
> |- Emacs
> | |- index.org
>
> ~/org/Emacs/index.org would contain the following:
>
> #+SETUPFILE: ~/.emacs.d/level-1.org
>
> which points to a setupfile with the option:
>
> #+STYLE: <link rel="stylesheet" type="text/css"\
> href="../stylesheet.css" />
>
> My question: Instead of this method, which I find a little tedious,
> I've created a hardlink to the master css directory in each
> subdirectory of my project. As a result the, css files get copied to
> each subdirectory in my public web directory and I only need to
> specify a single style option in my org-publish-alist.
>
> Apart from taking up extra disk space on the server (and thus being
> less economical), are there any other potential problems with this
> approach? I'm using org as a wiki and have a lot of org files in each
> subdirectory. This approach seems easier than having to add and tweak
> the SETUPFILE option for each new org file.
I have lots of org files generating documents (some public, most not) at
http://doc.norang.ca/
,----
| Most of the public documents in doc.norang.ca have outdated
| information but the 'How to use git' document might be of interest to
| people on this mailing list.
`----
I wrote a simple Python CGI script that picks up any HTML file in that
directory and displays it on the index page. Each page uses the same
CSS file.
I have one entry for CSS which I share between all of my pages:
,----[ part of my org-publish-project-alist ]
| ("doc-org" :base-directory "~/git/doc.norang.ca/" :publishing-directory "/ssh:www-data@www:~/doc.norang.ca/htdocs" :recursive t :section_numbers nil :table-of-contents nil :base-extension "org" :publishing-function org-publish-org-to-html :style "<link rel=\"stylesheet\"\n href=\"/org.css\"\n type=\"text/css\">" :author-info nil :creator-info nil)
| ("doc-css" :base-directory "~/git/doc.norang.ca/" :publishing-directory "/ssh:www-data@www:~/doc.norang.ca/htdocs" :base-extension "css" :publishing-function org-publish-attachment :recursive t :author nil)
| ("doc" :components
| ("doc-org" "doc-css"))
`----
I create docs in subdirectories under http://doc.norang.ca/ and each
document uses the css file in the root directory. All the documents use
the same CSS file and therefore look the same. You could of course
specify a fixed address for the stylesheet - there's no requirement to
use relative addressing for your stylesheets at all (i.e. I could have
replaced "/org.css" with "http://doc.norang.ca/org.css" and I'm free to
use that stylesheet for any page (even stuff not in the doc.norang.ca
domain)
Feel free to steal it if you like it :)
Maybe some of that is useful...
-Bernt
next prev parent reply other threads:[~2008-10-29 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 15:37 Org publish hierarchies and style variable mdl
2008-10-29 17:59 ` Bernt Hansen [this message]
2008-10-30 3:00 ` Matthew Lundin
2008-10-30 10:38 ` Richard Riley
2008-10-30 15:19 ` Sebastian Rose
2008-10-30 15:06 ` Richard Riley
2008-10-30 17:32 ` Sebastian Rose
2008-10-30 17:04 ` Richard Riley
2008-10-29 18:40 ` Sebastian Rose
2008-10-29 18:59 ` Sebastian Rose
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873aifs2nu.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.