Like many people I use site maintenance as an excuse to try out new technologies and ideas, and I keep notes on the process, including information on how this site was created and the philosophy behind its design.

Recent entries for this category

Feedback is now welcome

After much struggle I've finally managed to get my blog to support comments and TrackBacks. (This is what I get for using "roll your own" blogging software). I'll blog some more later about how I did this, for any Blosxom users who happen to be interested; in the meantime please report any problems to me, either as comments on this post (if you're able to) or via email.

UPDATE: I now have a blog post describing the new Blosxom plugin I wrote to support comments and TrackBacks.

To-do list

As many people can attest, sometimes you spend more time (and have more fun) tinkering with the underpinnings of a web site instead of actually writing new content to be posted on it. In that spirit, here is my current list of things I'm planning to add to or change about my web site and blog. ...

Copyright and license

I've done a lot of work related to software licensing as part of the Mozilla relicensing project and when I worked at CollabNet. As a result of enduring endess wrangling about licensing terms I've been put off complex licensing schemes, and prefer to make my own works available under very liberal terms. ...

Syndication feeds

If you'd like to receive full-text articles from this site as they are published, you can subcribe to one or more of the following feeds, in the formats indicated; simply cut and paste the URLs into your feed reader of choice. The Atom feeds are preferred; I maintain the RSS feeds only for older news aggregators that are not yet Atom-enabled. ...

Design philosophy

The basic principles I tried to follow in creating the this site were as follows:

  • The site should be entirely text-based, with minimal or no use of graphics.
  • All web pages on the site should validate as HTML 4.01 Strict.
  • All web pages on the site should be accessible using URIs that hide the details of the particular content type or page generation mechanism associated with the page.
  • The site should be a transparent upgrade from my previous site (created a few years ago), so that all previous URLs should continue to work. ...

Colophon

This site is a mixture of static content and dynamic content served through the Blosxom blogging system. I use various URI rewriting rules and a number of Blosxom plugins (some slightly hacked) in order to implement the site according to my personal design philosophy. ...

URI rewriting and canonical URIs

Here I document the way in which I use URI rewriting (along with redirection and a couple of Blosxom plugins) to help implement my personal design philosophy for my web site. My goal is to create a unified URI space within which static and dynamic content can transparently co-exist, with publicly-visible URIs for human-readable content (i.e., HTML pages) having a canonical form that omits file extensions or other content type specifiers. ...

Accessibility statement for www.hecker.org

I've tried to make this site accessible to as many people as possible; here I describe the accessibility features of this site. (This statement is based on Mark Pilgrim's accessibility statement.) If you have any questions or comments about the accessibility of this site, feel free to email me at hecker@hecker.org. ...