emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Matthew Lundin <mdl@imapmail.org>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org publish hierarchies and style variable
Date: Wed, 29 Oct 2008 22:00:12 -0500	[thread overview]
Message-ID: <m2d4hin5xf.fsf@fastmail.fm> (raw)
In-Reply-To: <873aifs2nu.fsf@gollum.intra.norang.ca> (Bernt Hansen's message of "Wed\, 29 Oct 2008 13\:59\:33 -0400")


Bernt,

Bernt Hansen <bernt@norang.ca> writes:

> mdl@imapmail.org writes:
...
>> 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.
... 
>
> 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)

Thanks for this very simple solution. 

Best,

Matt

next prev parent reply	other threads:[~2008-10-30  3:00 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
2008-10-30  3:00   ` Matthew Lundin [this message]
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

  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=m2d4hin5xf.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.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

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