This little blog is created/compiled with Chronicle, coded by Steve Kemp, and one of the cool
features is that you can specify a command run before/after your blog gets
compiled from the input files. This presents us with one problem and a lot of
opportunities.
First to the problem: the singular "a command" (from the manual
page) might not be enough. Maybe you want to run more than one command. This can
be achieved by creating a directory for the commands you want to run before the
compilation and one for the commands you want to run after the chronicle run.
[UPDATE]Then just add run-parts /path/to/{before,post}.d
to your .chroniclerc for the {pre,post}-build configuration
entries.[/UPDATE] (Thanks to Steve for pointing the obvious out
to me, don't know why I didn't think of run-parts myself.)
Now to one of the oppurtunities this offers: you can now, for example, create
static pages, which share the general visual appearance with your blog entries
but don't show up in the tags or archive system. I'm using this to generate an
imprint for this blog. The script to generate the imprint looks like:
#!/bin/sh
set -e
OUTPUT_PATH=`grep output ${HOME}/.chroniclerc | cut -d= -f2 | tr -d [:blank:]`
sed -nre'/<\?xml version/,/blosxomFirstDayDiv/ {/blosxomFirstDayDiv/b;p}' \
${OUTPUT_PATH}/index.html > ${HOME}/tmp/imprint.html
cat `dirname ${0}`/imprint.data >> ${HOME}/tmp/imprint.html
echo -e "\n" >> ${HOME}/tmp/imprint.html
sed -ne'/imprint_match/,$p' ${OUTPUT_PATH}/index.html >> ${HOME}/tmp/imprint.html
mv ${HOME}/tmp/imprint.html ${OUTPUT_PATH}/imprint.html
There are again some assumptions made here, which you'd need to adopt to your
setup:
- I'm using a modified version of the "Copyrighteous" theme (one
of the modifications was detailed yesterday).
- The script expects the output setting in your
.chroniclerc.
- The content/body of the imprint is stored in a file imprint.data
in the same directory as the script which generates the imprint.
- There is a tmp directory below ${HOME} (this is there
to cope with a chroot environment).
Now you have a very powerful system to modify/extend your chronicle-generated
blog. I hope you enjoy it as much as I do!
A little P.S.: you might want to use version 4.5, as 4.4 had a nasty
encoding bug.
