The custom stylesheet is based on the standard DocBook XSL XHTML stylesheet. However, instead of inserting an HTML header, it inserts PHP calls to include the WordPress headers and footers. The only tricky part of this is to tell WordPress what the title of the resulting page should be. I hacked this in by creating a class with the bare minimum fields required by wp_title() (which is used by WordPress to print the title of the document). The resulting template looks like this:

<?php
  require('../wordpress/wp-blog-header.php');
  class MyPost { var $post_title = "My Title"; }
  $wp_query->is_home = false;
  $wp_query->is_single = true;
  $wp_query->queried_object = new MyPost();
  get_header();
?>
<div id="content" class="narrowcolumn" role="main">
  ...
</div>
<?php
  get_sidebar();
  get_footer();
?>

The DocBook kit is available from my Git repository (or on GitHub, or as a ZIP file). More information about the kit can be found here.

Up until recently, I’ve been using TipiWiki as my notebook, which is very light, simple, and easy to deploy. However, recently started running into its limitations, including limited markup possibilities (e.g. no multi-level lists), the lack of decent history (seeing who changed what, when), … I liked the idea of git-wiki, which used Git as its backend, giving it good history support, and the fact that all documents are in a real repository. However, git-wiki uses Sinatra, which requires way too much valuable resources than I want to spend on a simple wiki.

So, I took the idea of using Git as a backend, threw in the Textile PHP class for marking up text, and wrote WiGit: a simple, themable wiki in PHP (which is less cool, but also less heavy than Ruby/Sinatra), built upon Git, with history support, basic user support (from HTTP authentication), and pretty URLs. The default theme is still rough, and there are still a bunch of features coming up, but it should function properly already as a simple wiki for your everyday needs.