To all who will someday dig through the archives of this blog and find this post (since I know no one is currently reading my previous sham of a blog): Welcome!

I’m (once again) relaunching my personal website/blog in the hopes that I can maintain it and keep it up-to-date, unlike my previous attempts. The difference this time Radiant CMS, which is a fairly open-ended CMS with plenty of extensions to add this or that feature (i.e., a typical blog requires enabling or installing the Archive, Blog, Comments, Paperclipped, and Tags extensions), most of which work seamlessly together. It’s also fairly easy to add custom Ruby/Rails code without having to “hack the source”, as I’ve had to do with every CMS I’ve used in the past. Overall, I’m liking it.

For the record, here’s a rundown of the major revisions of my personal website(s), what I used for each, and what worked and didn’t work:

6bitt.com personal blog | 2003-2005

• For the most part, short articles linking to interesting stuff I found on the Internet (afterall, it was pre-Delicious, Facebook, Twitter,…).
• engine: PMachine blogging engine
• pro: Got me up and running in 2003.
• con: Had to hack the source. Pretty primitive by today’s standards.

slippyd.com 1.0 website/resume | 2007

• An intro page and my resume. Built to get a job after college.
• engine: hand-built PHP pages
• con: Spent way too long on coding HTML & CSS for flexible-width cross-browser layout awesomeness.
• pro: I’ve used variations of that HTML & CSS for everthing since.

slippyd.com 2.0 website/resume | 2007-2008

• Added additional content for my various projects and aggregations of social network sites.
• engine: PHP front-end fed by Drupal back-end
• pro: Coded some awesome time-of-day color-shifting AJAX.
• con: Have now deprecated that code with the latest version, due to unnecessary complexity. Had to write Drupal “plug-ins” (hacks) to get it all to work.

slippyd.com 3.0 website/resume/blog | 2008-2009

• An attempt to create my own CMS in Rails and finally start a new blog.
• engine: hand-built Rails app
• pro: Took a remarkably short time to get mostly everything ported over and the basis of the CMS up and running. Much faster than Drupal.
• con: Still took longer than what I wanted to take. Didn’t get to writing much content.

slippyd.com 4.0 website/resume/blog | 2009-now

• A second attempt to start an interesting blog and get stuff I’ve worked on or am working on up on the web.
• engine: Radiant CMS (on Rails), with bits and pieces of custom Ruby code
• pro: Up & running, faster than ever, with modern blogging/CMS features.
• con: Finding time to write up meaningful content isn’t easy.

So there it was and here we are; thanks for reading and hopefully there will be many more wonderful posts ahead. Arevaderche!