Hi Gez, Gez <sule...@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