explaining my publish alist

Most of the configuring for org-publish happens in org-publish-project-alist, with each element being a publishing project. Today I worked on refining and fixing this alist. And here I will explain the reasoning behind my tinkering project by project.

index

The "index" project includes just one file, the index file. The reason it is in a separate project is partly because unlike every other page on my website I do not want org-publish it to give it a default title (I want the title, my name, to be a link to the about page) and partly because

("index"
 :base-directory "org"
 :base-extension "org"
 :exclude ".*"
 :include ("index.org")
 :recursive nil
 :publishing-directory "html"
 :publishing-function org-html-publish-to-html
 :with-title nil
 ,@oo-publish-defaults)

the index file includes the sitemap file generated by the "posts" project (below is code that includes it) meaning that the "posts" project needs to be published beforehand.

#+begin_blog-entries
#+INCLUDE: "posts/sitemap.org" :lines "3-"
#+end_blog-entries

Specifically, I publish the "posts" project first so that the sitemap file is created before the index project is published. And that is why I use the more fine-grained org-publish instead of the more generic org-publish-all.

(org-publish "posts" :force)
(org-publish "pages" :force)
(org-publish "static" :force)
(org-publish "index" :force)

pages

The "pages" project is for publishing non-post files of the website; things like my about page and my index page.

("pages"
 :base-directory "org"
 :base-extension "org"
 :publishing-directory "html"
 :recursive nil
 :exclude "index\\.org$"
 :publishing-function org-html-publish-to-html
 ,@oo-publish-defaults)

posts

The "posts" project is, as its name suggests, for blog posts. I ignore any posts prepended with drafts so I can have control over which posts are published at any given time. Initially, I had the pages and the posts together as one project but since posts have their own CSS stylesheet and I only want the sitemap for blog posts it seemed logical to put them as separate projects. Right now the stylesheet for the blog posts is in the previous directory (the one that corresponds to the "pages" project). It might be more logical to also add it to the post directory but I have not decided yet.

("posts"
 :base-directory "org/posts"
 :base-extension "org"
 :publishing-directory "html/posts"
 :recursive nil
 :exclude "sitemap\\.org$\\|draft_.+\\.org$"
 :publishing-function org-html-publish-to-html
 :auto-sitemap t
 :sitemap-filename "sitemap.org"
 :html-head "<link rel=\"stylesheet\" href=\"../style.css\" type=\"text/css\"/>"
 :sitemap-sort-files anti-chronologically
 ,@oo-publish-defaults)

static

The "static" project, also aptly named, contains are files that are "static", meaning that they do not change and will be published as is. This is for virtually anything that is not an .org file.

("static"
 :base-directory "org"
 :base-extension "css\\|js\\|png\\|jpg\\|gif\\|pdf\\|mp3\\|ogg\\|swf\\|php\\|mov\\|html\\|txt\\|"
 :publishing-directory "html/"
 :publishing-function org-publish-attachment
 :recursive t)