Writing entries in Douglas is fairly straightforward. Each entry is a single text file located somewhere in the directory tree of your datadir. The directory that the entry is in is the category the entry is “filed under”.
For example, if my datadir was
/home/joe/myblog/entries and I
stored an entry named
/home/joe/myblog/entries/status then the category for my entry
A warning about category names:
Be careful when you create your categories—be sure to use characters that are appropriate in directory names for the file system you’re using.
Categories are NOT the same thing as tags. An entry can only belong to ONE category. If that’s not what you want, you should write or install a tags plugin.
Don’t worry about making sure you have all the categories you need up front—you can add them as you need them.
The format of an entry¶
Douglas entries consist of three parts: the title, the metadata, and then the body of the entry. The first line is the title of the entry. Then comes zero or more lines of metadata. After the metadata comes the body of the entry.
The title consists of a single line of plain text. You can have whatever characters you like in the title of your entry. The title doesn’t have to be the same as the entry file name.
The metadata section is between the title and the body of the entry.
It consists of a series of lines that start with the hash mark
then a metadata variable name, then a space, then the value of the
Example of metadata lines:
#mood bored #music The Doors - Greatest Hits Vol 1
The metadata variables set in the metadata section of the entry are
available in your story template. So for the above example, the
$(mood) would be filled in with
$*music) would be filled in with
The Doors - Greatest Hits Vol
Metadata is not collected in a multi-dict. If you include two pieces of metadata with the same key, the second one will overwrite the first one.
#mood bored #mood happy
will result in
'happy' in the metadata.
You can provide metadata keys with no value. If you do this, then
the default value is
'1'. This seems a bit weird, but it makes
it easier for plugin developers to use these as flags.
The body of the entry is written in HTML and comprises the rest of the entry file.
Here’s an example first post entry with a title and a body:
This is my first post! <p> This is the body of the first post to my blog. </p>
Here’s a more complex example with a title and a body:
The rain in Spain.... <p> The rain </p> <p align="center"> in Spain </p> <p align="right"> is <font color="ff0000">mainly</font> on the plain. </p>
Here’s an example of a post with title, metadata, and a body:
The rain in Spain.... #mood bored #music The Doors - Greatest Hits Vol 1 <p> The rain </p> <p align="center"> in Spain </p> <p align="right"> is <font color="ff0000">mainly</font> on the plain. </p>
The posting date of the entry file is the modification time (also known as mtime) of the file itself as stored by your file system. Every time you go to edit an entry, it changes the modification time. You can see this in the following example of output:
willg ~/blog/entries/blosxom/site: vi testpost.txt  willg ~/blog/entries/blosxom/site: ls -l total 16 -rw-r--r-- 1 willg willg 764 Jul 20 2003 minoradjustments.txt -rw-r--r-- 1 willg willg 524 Jul 24 2003 moreminoradjustments.txt -rw-r--r-- 1 willg willg 284 Aug 15 2004 nomorecalendar.txt -rw-r--r-- 1 willg willg 59 Mar 21 16:30 testpost.txt  willg ~/blog/entries/blosxom/site: vi testpost.txt  willg ~/blog/entries/blosxom/site: ls -l total 16 -rw-r--r-- 1 willg willg 764 Jul 20 2003 minoradjustments.txt -rw-r--r-- 1 willg willg 524 Jul 24 2003 moreminoradjustments.txt -rw-r--r-- 1 willg willg 284 Aug 15 2004 nomorecalendar.txt -rw-r--r-- 1 willg willg 59 Mar 21 16:34 testpost.txt 
- I create the blog entry
vi(vi is a text editor). The mtime of the file will be the time I last save the file and exit out of vi.
- Note that the mtime on the file is
Mar 21 16:30. That’s when I last saved the blog entry and exited out of vi.
- I discover that I made a spelling mistake in my entry... So I edit it again in vi and fix the mistake. The mtime of the entry has now changed!
- Now the mtime of the file is
Mar 21 16:34. This is the time that will show up in my blog as the posting date.
A warning about mtimes:
There are some issues with this method for storing the posting date.
First, if you ever change the blog entry, the mtime will change as well. That makes updating blog entries very difficult down the line.
Second, if you move files around (backup/restore, changing the category structure, ...), you need to make sure you do so in a way that maintains the file’s mtime.
Douglas supports one format for entry files by default. This format is the same format that blosxom uses and is described in previous sections.
A sample blog entry could look like this:
First post <p> Here's the body of my first post. </p>
Some people don’t like writing in HTML. Other people use their entries in other places, so they need a different markup format. Some folks write a lot of material in a non-HTML markup format and would like to use that same format for blog entries. These are all very valid reasons to want to use other markup formats.
Douglas allows you to install entry parser plugins which are Douglas plugins that implement an entry parser. These entry parser plugins allow you to use other markup formats. Check the Plugin Registry on the website for other available entry parsers. Douglas comes with a restructured text entry parser.
If you don’t see your favorite markup format represented, try looking at the code for other entry parsers and implement it yourself. If you need help, please ask on the douglas-devel mailing list or on IRC. Details for both of these are on the website.
Additionally, you’re not locked into using a single markup across your blog. You can use any markup for an entry that you have an entry parser for.