I require some structure

I happened to post about redoing my personal site the same day a coworker pointed me to Sitesprint. The idea behind it is to stop procrastinating and launch or re-launch your personal site by December 15th. The rules are simple:

1. launch by 12/15
2. document your process
3. on launch, share what you did and how you did it

If you followed the progress of my django site-seach module, you'll know I'm the procrastinating type. Definitely. So I signed up and I'm hoping this will give me the kick in the pants I need to knock this thing out. Forthwith a few personal rules:

• 5 signifigant contribs to the svn repo for my new site CMS per week.
• One blog post about the prcess per week
• Feature-complete by 11/25
• Design (such as it is) done by 12/1
• Design coded by 12/5
• Soft launch 12/10

So, we'll see how it goes. The coding part I'm not worried about, to be honest. But design...ugh. I've tried to redesign this site about 5 times since I launched, and I wasn't happy with anything I came up with, which is why the site still looks like it does.

This blog is written in Django, as mentioned in other posts. Other than a few minor improvements, it's basically the same code I wrote over year ago. I've decided it's time for a rewrite for two reasons. Firstly, I know a lot more about Django now than I did then and there are some things I'd like to improve and some functionality I'd like to add. Secondly, this format doesn't really fit my life. I like doing longer-form entries but rarely have the time, and as a result, there's not a whole lot going on here. My new blog will have a more-frequently-updated tumbleog feed right alonside the normal blog feed (Simon Willison's blog inspired this idea.) There will be RSS feeds for both, separately and together. You can follow my progress or grab the code for your own use.

I'm also planning to move hosting. I'm using Dreamhost now, which is fine as commodity hosts go, but they really don't handle Django well. They force you to use fast-cgi which is bad for a number of reasons and they also like to kill fast-cgi processes, which causes the occasional 500 error to show up around here (just refresh and you should get the page you want). I understand why they want to do this, but the end result is that this just isn't a good place for Django. I'm looking into webfaction, as I've deployed Django apps there before and liked it, but other suggestions are appreciated.

Finally, I'd like to redesign this. Frankly, though, I'm not a good designer—or a designer at all, really—so it probably won't look much better.

Update: Same day I post this, I see Sitesprint. So I went ahead and signed this site up for it.