Hello, world
Writing the first blog post on your new blog is like giving birth to a baby. No, that’s a terrible analogy. It’s more akin to… giving a speech after winning the presidential elections. But with a lot less pomp and ceremony. You think ahead of yourself. How will future me look back 10 years at this post? How will I see myself back here, sweating over every word, because every word, every letter, every bit and byte I put out there will be immortalized. Perhaps not on this blog, maybe not even in this medium. But the Internet never forgets. So I should actually write something useful and interesting instead of wasting time, both yours and mine philosophizing about the nature of producing content on the World Wide Web. What follows is some thoughts on the process of building this site.
Boring technical stuff below.
Designing this site
The site is designed with heavy emphasis on geometric shapes and colors. The defining feature are the stripes running down from the upper right corner of the site. These are created using SVG, which I believe has sufficient mainstream browser support to be used in this manner. Since SVG is all text, the CMS can manage the colors of each post individually, and new color schemes can be created to invoke different moods to accompany each post.

The palette creation tab uses Spectrum. In the future it would be a good idea to include some form of automatic palette generation tool into this. Choosing 5 x 4 background and font colors with two hover states each can be very tiring.
Building this site
This site is created from Laravel, a neat PHP framework that bills itself as a PHP framework ‘for web artisans’. Every part of the site, including the CMS in which I’m writing this post now, is built by hand, from scratch. In this day and age of overabundant CMSes, it seems silly to roll your own. Of course there are many alternatives, many of which are far superior than what I could’ve built myself - WordPress comes to mind immediately as a simple and easy to use CMS. But one of the main goals of building this site is to learn Laravel, and what better way to learn a framework than to go through the old ‘build a CMS’ routine?
Laravel is easy to use and makes for highly expressive code, especially for someone who have previously been using CodeIgniter. The included Eloquent ORM is billed as one of the framework’s best features, and indeed when working with CI I often thought of building models in same way that Eloquent does - binding model data to table rows automagically, leaving most of the simple queries to the model itself. I am, unfortunately, not well versed enough to build an ORM like this, so Eloquent seems like an exciting opportunity to experiment.
However, even a framework as well designed as Laravel isn’t free of quirks. In the next post I’ll talk about some of the strangeness faced when building this site.
Blog posts are written in a mix of Markdown and HTML. Some post processing is done on the HTML generated by PHP Markdown Extra. These blog pages are responsive, but other parts of the site are not (yet). I’m not sure if there is much to be gained from creating responsive designs for the less commonly used areas of the site. Creating a unique design for each portfolio post is already a challenge in itself, and though I enjoy creating every one of them, creating a separate 800px and 400px design for each of them is far too much work.
The admin side of the site is build using Backbone.js. It automatically synchronizes changes made to the posts, and gives code more structure. One thing to note is that Backbone is very flexible, and doesn’t have much in the way of telling you how to use Collections, Models and Views idiomatically. This is great if you know what you’re doing, but also makes it easy to write poor code if you, like me, have no idea what you’re doing since you’re just starting with the framework.
Finally
Am I satisfied with my handiwork? Not really, no. There are a lot of places where the code could be better written, and some obvious features are missing. Would it have been done better with WordPress instead of rolling my own CMS? Most likely, in which case I would have substituted experience in working with Laravel with that of working with WordPress, since to build the sort of features I’m looking for it is likely I’ll have to roll my own plugin or even hack into WordPress’ core. There’s still a few features I’d like to roll out, but for now, I’d say this site is ready for the prime time.
Hello, Internet!
PS. If you see anything broken, have any suggestions, critique, etc. please do drop me a line, and I’ll get it fixed. The site is new, after all.