A slightly bigger problem is that since entries are generated when they are initially input, any change to the entry format later doesn't get reflected in what appears on the web. Only sometimes it does. I wasn't able to find a command that just did "refresh entries" though adding a new entry sometimes accomplished that for older entries (as well as also introducing duplicates and other strange problems).
I was also a little bothered by not being able to preview the site locally (nb hardcodes the site's url, so links all go to the real site rather than the local copy, and css files work inconsistently -- they work on some pages but not others) but OTOH blosxom, being a cgi, obviously can only work through a web server and not as local files, so they both have that problem as far as maintenance on a disconnected laptop (and in both cases it can be worked around).
The default nb look (when it does use the css, which it doesn't always) is much nicer than the default blosxom look. For blosxom I'll have to write css and collect a bunch of plugins to get things that nb offers automatically, like a sidebar with topics and a calendar of past entries. That's an appealing side to nb. I'd be really tempted if those duplicate entries weren't such a problem. Hmm.
[ 09:48 Jul 23, 2004 More blogging | permalink to this entry ]