This site is now Django powered. What does that mean? Well, to me it means I have another excuse to learn more about web development in general and the fascinating internals of the Django project specifically. To you, it might not mean too much except some parts of this site won't work for a while. So please excuse my mess if you come across something that doesn't look quite right or is just plain broken.

Rolling my own blog software (with the help of lots of examples out there on the web) has actually been pretty easy. I'm still pretty far from finished with the design and feature set, but it's coming along nicely.

Here's a list of some of the components I've been able to tie together with this site:

• Markdown - a plain text publishing format that takes some of the pain out of publishing text on the web
• Yahoo reset and grids - makes it easier to design web pages that maintain a consistent visual style across the main browsers (reset) and helps laying columns within a page (grids)
• Django-tagging - a beautifully simple tagging implementation for Django apps
• Jellyroll - a tumblelog-style application for Django (written by one of the Django co-authors, Jacob Kaplan-Moss)

Still to do:

• Import the rest of my 160 or so posts (and pages) from the Wordpress database that previously ran the site and figure out how to keep the same URLs (maybe with mod_rewrite directives, but I might be able to match the previous URL exactly)
• Turn syndication feeds back on (should be low hanging fruit, but I need to figure out how to integrate the Jellyroll as well as blog entries)
• Automate the provider interaction in Jellyroll (run a cron job that automatically pulls in my bookmarks, public photos, last.fm tracks, etc)
• Enable a sitemap (built into Django; should only take a few minutes once I take the time to do it)
• Figure out how to integrate the Jellyroll and blog posts onto the root of this domain

That's plenty to keep me busy for a while. I also plan to move my shopping manager application and maps mashup to this site and need to figure out what to do with codefuture.