Changing fonts in Ode is as easy as changing the .css file in the theme(s) you are using.

I've been having some trouble in Fedora with the Arial font, which looks like hell. The Wine non-emulator that runs Windows software in Linux brought an Arial font into my system, and it's just plain ugly.

I started looking at Arial and Helvetica not just in Linux but in Windows, too, and I decided that I don't like either one very much.

So I went into my CSS and killed out Helvetica Neue and Arial. Now Verdana and sans-serif, in that order, are the default fonts.

Looks better, I think.

There is a new Ode-running site out in the wild. Announced on the existing Surface Markup blog is the Surface Markup development blog, which has one of the nicest themes I've ever seen on an Ode site. It's minimal, beautiful and responsive.

Designer/writer Hans Fast helped me make this site responsive, and I continue to thank him.

In my Ode system running on an Apache web server, I'm "exposing" the existence of the /documents directory by stashing HTML there for my site archive.

Normally only text files and images live in that directory, and Ode uses them to produce the HTML pages it serves out of another directory.

I'm not crazy about exposing the contents of directories that don't, for the most part, serve HTML. So I decided to disallow directory listings on my Ode site with this line in .htaccess:

Options -Indexes

Now my readers can see http://stevenrosenberg.net/documents/archive.html but not http://stevenrosenberg.net/documents and the entire structure under that.

Even if I do decide to move my archive file to another directory (and I am seriously thinking about doing that), it still seems like a good idea to block access to the "raw" directories in Apache.

I've been messing around with scripting, and I created a static Ode archive page that lists every entry on this site.

I hacked it quickly. It needs some work. I think this would work better as a full-on Ode extension. For that I'd have to write it in Perl and figure out how Ode add-ins work. It could also be an extension of the Indexette add-in.

I'll be thinking about how to do this.

I decided to script my blog updates via a Bash script for Unix/Linux that runs both my Unison sync and the Indexette reindexing necessary to to make those entries live.

You're probably not running Unison like I am (and I still need to write up my Unison tutorial), but the reindexing line is worth sharing because I find it very useful to reindex the blog without using the web browser.

First of all, you need to install wget on your Unix/Linux system. It's available in just about every distribution. Use your favorite package manager to install it.

Read the rest of this post

That title sounds like a bad master's thesis, right?

What I'm trying to do here is see how Ode posts that get their Indexette tagging locally play with my Unison sync setup.

If Ode doesn't "touch" the pre-tagged files on the server, I think we're all good.

Minutes later: That works. Now to code up a way to drop in the Indexette tag with system-generated current date and time.

Weeks later: I did write the code in the form of a short Perl script, and I incorporated it into the Gedit text editor via the Snippets plugin. I will detail this in a future post.