The Django Option—

Some of the more geek readers of this site will be aware that it is mostly powered by Wordpress. Supporting the WP install is a large collection of PHP functions and a template that are used across the whole site. In general I have been more than happy with how it has turned out.

However, I want this site to be more than a blog, and less focused on the blog as the center of the site. Specifically the Code section of the site wants more fu added to it. Much of this is outside the scope of what WP is designed to a chieve. A second factor is that I don't use a large chuck of what WP provides me.

So what's this about jazz guitar then?

Recently, a new Python, full stack, MVC, web development framework was shown to the world (Sorry about the buzzwords.) It's called Django and its similar the much praised Ruby on Rails.

Why not just use Rails then? A few reasons. I don't know Ruby, I don't want to get stuck on MySQL again, Django makes admin creation really, insanely easy, and – quite significantly – if I am going to have to learn a new technology (especially a large one) I would rather not have to learn a new language at the same time.

Why not PHP? Because I hate it :P It has crap data modeling, crap modules, string processing is at the C level only without the pointer, no namespaces and it makes one hell of a mess even when used well

Things that need to be taken care of

Currently I have a basic blog system taking shape on my Django install. Significantly light weight compared to WP; just Posts, Categories, and Comments. Currently I don't plan to support trackbacks, I was kinda iffy about them but a DrunkenBlog post has tipped me over the edge. Other features from WP will be their own ‘apps’ on the Django system (links and link groups for example, and pages.)

The code section might finally get built. Its a nightmare to do in PHP, and mostly the admin side of things. Thats a breeze in django. Planned features include bug tracking and version information, automated packaging from the SVN, and maybe tie-ins to the blog.

Other bits and peices: My Timetable, I would like to not have to edit the PHP source every time I need to update it. Links, my Bookmarks (currently done using del.icio.us), and a unified home page that is more than a crapped out version of the blog.

The rest

Of course, this assumes Textdrive will be able to run Django, that I am happy with the finished system, or that i even finish the system. As much as anything its a target to aim for in learning Django and evaluating MVC web frameworks as a tool.

Should I really be considering ripping apart a perfectly servicable site? Probably not, but it is fun.