Introducing TheOverAnalyzed 3.0

Over the course of the next few days (weeks?), I am going to explain how exactly I left my previous CMS and transitioned to Casey Liss’s static blogging engine, Camel. I am aptly calling this series Leaving Squarespace.

I said “weeks” because it might actually take that long to finish the series. I haven’t even begun to write the posts. Moreover, moving TheOverAnalyzed to Camel has taken up almost all of my free time over the past two weeks. Because of that, I’m sure I have several links saved to my “Blog Content” folder in Instapaper—links I’m sure I’ll want to share in-between these long-winded design pieces. My intent for this series to be part how-to[1] and part web design philosophy in general.[2]In addition to the loads of Tweet-learning passed to me from both Casey Liss and Roger Stringer (more on him later in the series), I was forced to learn a bunch of stuff the hard way. I hope this series can make a prospective Camel-rider’s journey a tad bit easier than my own.

The tentative outline:

Part I: Getting Started With Camel

In order to start fiddling with Camel, I had to learn some command line tools.

Part II: Modifying Files To Play Nice With Camel

Making all my old Markdown files play nice with Camel was easy, but extremely time-consuming.

Part III: Making Camel My Own

Camel came with several nifty Markdown plugins, but I wanted more.

In the meantime, please explore the new site! I’m pretty proud of it. And as always, thanks for reading.

  1. For people who were as green as I was when I started. I didn’t know GitHub from Git.

  2. I could get pretty meta about the how and why of some of the things I have implemented on the site.