<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
 
 <title>tsphethean.co.uk</title>
 <link href="http://tsphethean.co.uk/atom.xml" rel="self"/>
 <link href="http://tsphethean.co.uk"/>
 <updated>2012-12-26T20:05:23+00:00</updated>
 <id>http://tsphethean.co.uk</id>
 <author>
   <name>Tom Phethean</name>
   <email>tsphethean@gmail.com</email>
 </author>

 
 <entry>
   <title>Jekyll and Hyde</title>
   <link href="http://tsphethean.co.uk/blog/2012/12/26/jekyll-and-hyde"/>
   <updated>2012-12-26T00:00:00+00:00</updated>
   <id>http://tsphethean.co.uk/blog/2012/12/26/jekyll-and-hyde</id>
   <content type="html">&lt;h2 id='how_did_i_get_here'&gt;How did I get here?&lt;/h2&gt;

&lt;p&gt;Over the years I&amp;#8217;ve moved through a series of personal websites.&lt;/p&gt;

&lt;p&gt;There was my very first site, built in the good old days of Frontpage Extensions and animated gifs, over a 56k modem I remember being so excited at watching an animated spider bungee down the page&amp;#8230; they were simpler times.&lt;/p&gt;

&lt;p&gt;Next up, was an XML/XSL-T site built for a university module on XML, trying to demonstrate that content style and separation could be achieved with XML, XSL-T and CSS. We&amp;#8217;re still not really there but thankfully we have moved on (largely) from the fun of XSL-T. The grounding in standards, semantics and schema though were useful pieces of learning which still apply today.&lt;/p&gt;

&lt;p&gt;Shortly after, the turning point for me was an ASP.NET 1.0 site which was my first experience of server side programming, dynamic web-page generation and databases to build websites. It was effectively my own CMS, complete with discussion forum, and I shudder to imagine the code I wrote back then. As a first &amp;#8220;proper&amp;#8221; website though, it sparked me on the path of where I am today, and I probably wouldn&amp;#8217;t have ended up in a career in web development if a friend hadn&amp;#8217;t patiently explained concepts to me that set me on my way.&lt;/p&gt;

&lt;p&gt;After a few aborted attempts at building handcrafted sites again, and a few years of abandonment of my site, I setup a Wordpress site, which a few incarnations later is the site I&amp;#8217;m replacing today. Interestingly, although I&amp;#8217;ve played with it a few times, I&amp;#8217;ve never run my own site on Drupal, which given my current occupation might seem strange. However whilst the power of Drupal is compelling, it&amp;#8217;s always felt overkill for the tiny amounts of content, functionality and traffic my site is likely to attract. Added to that, coming home and doing more Drupal after a day in the office isn&amp;#8217;t one that really appeals right now (unless it was fun stuff that would never appear on my site anyway :) ).&lt;/p&gt;

&lt;h2 id='why_jekyll'&gt;Why Jekyll?&lt;/h2&gt;

&lt;p&gt;After deciding I wanted to move away from Wordpress, it wasn&amp;#8217;t too long before I&amp;#8217;d settled on Jekyll. I&amp;#8217;d heard a few people talking and blogging about it, and was interested in learning more about an alternative approach to building simple websites. In a lot of ways, it takes me back to my roots of handcrafting sites, and after only a day of playing with it feels very simple and natural.&lt;/p&gt;

&lt;p&gt;A big benefit I see is being able to draft posts offline more easily than with Wordpress or another hosted CMS. Publishing static HTML appeals as well, as although traffic isn&amp;#8217;t likely to be a problem for me there are simply fewer things to go wrong - as long as my web host keeps Apache up and running then I&amp;#8217;ll have a site, and if they can&amp;#8217;t do that then it&amp;#8217;s probably not a good sign.&lt;/p&gt;

&lt;p&gt;Most importantly though, it&amp;#8217;s something to learn, an approach to play with, and incorporates some tools and technologies I&amp;#8217;ve not played with yet. Isn&amp;#8217;t that what all geeks want for Christmas?&lt;/p&gt;</content>
 </entry>
 
 
</feed>