Update posts and pages for blog changes

Add Partial migration article

_posts/2014-01-03-migration-to-jekyll.md

@@ -0,0 +1,16 @@
+---
+layout: post
+title: Mirgration to Jekyll
+description: Details of migrating from using the pelican static site generator to using Jekyll + github pages.
+tags: [pelican, jekyll]
+---
+After having used [pelican](http://docs.getpelican.com/en/3.3.0/) initially for my blog and creating a style for it.  I have found the process of updating the blog on github pages to be a bit more clunky than I would like it to be.  I have now gone through the process of converting the blog to use (http://jekyllrb.com/)[Jekyll].  Converting the actual content was fairly easy, a few quirks were encountered when trying to setup the new templates but overall the process was very easy.
+
+## Reasons for Change
+The main reason for moving from pelican to Jekyll was by switching the process of editing and uploading changes to the blog became much more streamlined.  With pelican the blog was built locally and then the built blog was pushed up to the `master` branch on github.  This was alright, but I also wanted to keep the source and configuration backed up so enter the `sources` branch.  The `sources` branch contained the raw posts and pages along with the pelican configuration files.  While this was not that bad it was a bit clunky. 
+
+Additionally to copy static resources, the files had to be listed within the configuration file (this is for things link CNAME, robots.txt etc).  Eventually I started to feel that the configuration file was getting bloated after adding in all the settings and configurations.
+
+## Jekyll
+Github pages natively supports Jekyll integration which made it a good candidate to replace pelican.  Now everything could be done with a simple push to the pages repository.  TODO...
+

_posts/python/2013-08-03-pelican-red.md

@@ -2,11 +2,10 @@
 layout: post
 title: pelican-red
 date: 2013-08-03 21:23
-tags: pelican-red, pelican, python
+tags: [pelican, python]
+comments: true
 ---
 
-## History
-
 After having tried using wordpress to create a blog on a couple occasions and attempting to create a skin, I gave up due to the clunkiness of the process and began to look for easier alternatives.  After some searching I decided that [pelican](http://getpelican.com) combined with github-pages would provided an adequate and easy to manage solution.
 
 ## Desired Features
@@ -56,4 +55,4 @@ Of these the coolest is the image meta tag which allows for the article to have
 pelican-red currently uses some theme "hacks" to achieve the final design, some of which can be converted into pelican plugins.  The modified time, image, and author information will be converted into plugins to modularize the code a bit better in the future.  Additionally the site menu will have support for nested menu-items instead of just a single drop-down. Finally, the print layout will be improved a bit to look less cluttered in some spots. 
 
 ## Additional Information
-The current documentation is in the [README.md](https://github.com/arsenetar/pelican-red/blob/master/README.md) in the github repository. The README covers all the settings and features in more detail. The theme itself is at [github](https://github.com/arsenetar/pelican-red). Pelican-red is licensed under the MIT-License. 
+The current documentation is in the [README.md](https://github.com/arsenetar/pelican-red/blob/master/README.md) in the github repository. The README covers all the settings and features in more detail. The theme itself is at [github](https://github.com/arsenetar/pelican-red). Pelican-red is licensed under the MIT-License. 

about.md

@@ -1,7 +1,8 @@
 ---
-layout: default
+layout: page 
 title: About
 permalink: /about/
+modified: 2014-01-07T00:00:00
 ---
 
 VoltaicIdeas is the personal blog of Andrew Senetar.