emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: emacs-orgmode@gnu.org
Cc: suleika@gmail.com
Subject: Re: Publish project alist in org-mode 8 - confusing documentation
Date: Thu, 06 Mar 2014 12:56:10 -0800	[thread overview]
Message-ID: <87k3c7vyfp.fsf@berkeley.edu> (raw)
In-Reply-To: CAPQe_Uo0yQozKBFa89ULs6Jx25AcdMBiPUKHcQhCuw+iBbPC-Q@mail.gmail.com

Hi Gez,

Gez <suleika@gmail.com> writes:

> but I don't know where to begin adapting it to the new export framework.
>
> For example, I'd be very grateful if someone could "translate" the
> following (or something more simple) into org-mode 8 version, so I can
> start evaluating and playing with it.
>
> (require 'org-publish)
> (setq org-publish-project-alist
>       '(
> ("org-notes"
>  :base-directory "~/org/"
>  :base-extension "org"
>  :publishing-directory "~/public_html/"
>  :recursive t
>  :publishing-function org-publish-org-to-html

It's been a while since I converted my publishing setup to the new
exporter, but I *think* the only change you need to make here is to the
:publishing-function option.  

The function you want here is now called org-html-publish-to-html.
There are other similar functions in the other export backends -- e.g.,
the function to publish to PDF is org-latex-publish-to-pdf.

Thus, if you need to find an appropriate publishing function, start by
looking for a function named like: org-BACKEND-publish-to-FORMAT.  I
don't remember how I figured this out, but hopefully it is documented in
the manual...

(I am not sure about the :recursive or :auto-preamble options, which
don't appear in the variable documentation for
org-publish-project-alist; if changing :publishing-function on its own
does not get this setup working, try removing those options.)

>  :headline-levels 7
>  :auto-preamble t
>  )
> ("org-static"
>  :base-directory "~/org/"
>  :base-extension "css\\|js\\|png\\|jpg\\|gif\\|pdf\\|mp3\\|ogg\\|swf"
>  :publishing-directory "~/public_html/"
>  :recursive t
>  :publishing-function org-publish-attachment
>  )
> ("org" :components ("org-notes" "org-static"))
>       ))

Again, I think this should work as-is, with the possible exception of
the :recursive option.  org-publish-attachment is still around.

Hope that helps!

Best,
Richard

  reply	other threads:[~2014-03-06 20:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 19:00 Publish project alist in org-mode 8 - confusing documentation Gez
2014-03-06 20:56 ` Richard Lawrence [this message]
2014-03-07 18:21   ` Gez

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=87k3c7vyfp.fsf@berkeley.edu \
    --to=richard.lawrence@berkeley.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=suleika@gmail.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).