The Radiant Conversion
Fixing Issues
Hopefully this conversion will fix some of the problems that were cropping up before– especially the issue with invalid RSS feeds that news readers like NetNewsWire simply wouldn’t tolerate. I’ve done my best to preserve things like RSS URLs (and article URLs too, to some degree), but I recommend you update any feed subscriptions you have with the new locations– using autodiscovery or by looking in the sidebar.
In terms of running the site, I’m finding Mongrel with Apache forwarding to be a lot more reliable than fcgi, so performance should be a better– especially on heavy Rails Weblog and project.ioni.st traffic days.
If you do notice any problems, please drop me an email . I’ve copied over all of the old comments (as of yesterday), but commenting will be down for a few days.
Why Radiant?
I’ve known for a while that I needed to move to a full CMS; the plain blog structure is nice and simple– and don’t get me wrong, that’s a Good Thing– but I’ve been aching for a bit more control over the format of the site. After a bit of searching, I decided Radiant was the best choice; it’s written on top of Rails, has an interesting premise– and is proving to be exceedingly fun to play with.
John W. Long and the rest of the Radiant developers have really put together a compelling system that deserves some attention. Radiant hasn’t been technically released, so there’s still some things missing that you might be looking for; but if you’re an early adopter and like to look at cool new things, I sincerely recommend it.
If you’ve been here before, you may notice things have changed a bit.
Besides the obvious design changes, there’s a lot that’s different under the covers. I’ve switched from Typo on fcgi to Radiant CMS on Mongrel.
