diff options
Diffstat (limited to '_posts/2014-05-01-migrating-to-github-pages-and-jekyll.markdown')
| -rw-r--r-- | _posts/2014-05-01-migrating-to-github-pages-and-jekyll.markdown | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/_posts/2014-05-01-migrating-to-github-pages-and-jekyll.markdown b/_posts/2014-05-01-migrating-to-github-pages-and-jekyll.markdown index 5271a57..b1bf2e6 100644 --- a/_posts/2014-05-01-migrating-to-github-pages-and-jekyll.markdown +++ b/_posts/2014-05-01-migrating-to-github-pages-and-jekyll.markdown @@ -7,10 +7,10 @@ date: 2014-05-01 00:00:00 redirect_from: "/writing/migrating-to-github-pages-and-jekyll/" --- -## Background - I’ve always been a fan of using [Markdown](http://daringfireball.net/projects/markdown/) to create web content. Several years ago, I created [MDEngine](/projects/mdengine/), a small PHP script to render Markdown files in HTML dynamically. For a while, it was responsible for much of the content on my website. In October 2013, I began work on a fresh design. I decided to use a custom Node.js app deployed on Heroku for processing the Markdown. While this worked effectively, I always had some reservations. +<!--more--> + While my site was decently fast, there was no real reason that it needed to be dynamically generated. I was particularly concerned with the performance of the two list pages, whose backend logic consisted of parsing an entire directory of Markdown files each time it was loaded. Though there was no noticeable performance impact, it was not inconceivable that the page generation time would increase substantially as content grew. In late April 2014, I made some design updates to the site running on Heroku. I decided to take the opportunity to address my performance concerns as well. While my original intent was to simply clean up the server logic I had written, I realized that it would be more sustainable in the long term to migrate to a true static site using [Jekyll](http://jekyllrb.com). |