You know you have a good idea when there are half a dozen implementations of it. All essentially the same but filled with subtle nuance. The latest idea I have stumbled across is the “semi-static” website generator. The idea is so painfully obvious I cannot believe that it has taken us until 2009 to do it properly.
What is a semi-static website? Well it’s actually something like this blog. I spend ages writing and editing the articles but once I publish something I don’t generally change it unless it has factual errors. I need something that allows me to make changes but my content easily but my content doesn’t really benefit in anyway from being stored in a database or being generated dynamically on the fly because it is going to spend most of its life not being changed.
If you look at a lot of CMS systems the same is true. People want to be able to edit and reorganise material easily but they are rarely changing it more than once a week. The majority of the time the pages are static.
If you look at a number of CMS or Wiki systems they are actually quite complicated. Before you can get going and generate your content (which remember is the core of what you want to do) you might have to setup a database and get the application deployed to a webserver.
When you combine it with a bit of DVCS magic deployment is even easier. You just checkin your new pages and then update the webserver copy of the content.
So if you want to get into this kind of content management what options do you have? Well you have a lot of choice indeed. Almost all of them are Ruby projects and they have a certain similarity to the Rails concept of code generation. You will be issuing commands like “create page”, “build site” and so on. You operate at one remove from it.
There are many, many, many choices but for myself I chose three to look at Nanoc, Webby and Jekyll. Nanoc I came across via Proggit and was struck by the simplicity and clarity of the documentation.
Installation of all three is via gems but there are some differences here. Nanoc is a very simple Gem and works with HTML and Erb by default, if you want to use a markup language or different templating language you will have to install the gem yourself. This means it also installs easily under JRuby too.
Webby by comparison is a very noisy install, I think it may have its dependencies slightly wrong as it installs a version of rake, flexmock and rspec which are surely development dependencies rather than anything I as a user would need to use for the framework. It also uses hpricot which means you can’t install it under JRuby.
Jekyll has a similarly demanding set of requirements but will install under JRuby. Jekyll did feel a lot like a personal solution as I was installing it. Textile is great but if I am going to be using Markdown why do I need to install RedCloth?
Overall I liked the nanoc install experience most.
Moving on to using them. Nanoc and Webby are very similar in that they use generators to create new elements in the site. Jekyll seems to use convention instead. At this point it is worth mentioning that there are some big differences between the three products in their intentions. Nanoc is a general website creator but it does have a certain amount of opinion as to how to do that. For example it generates very nice clean website urls by putting each page in a directory by itself and then creating the page as an index.html page within that directory. Make sure you have your webserver configured appropriately.
Webby is pretty flexible but comes with some built-in templates that will be build you a basic page, a tumblog style site, a normal blog and a presentation. That was a pretty neat feature and one the other frameworks didn’t have.
However the negative side to this is that the templating is based on Blueprint; which is both excellent as Blueprint is a great way of designing pages and a pain as Blueprint is actually pretty involved in terms of understanding the grid concept and what the various span-x css classes translate to. I felt that Webby did a great job of offering cross-browser styling that looked good but that in doing so it didn’t make the simple stuff simple. With my trial site my sidebar came out on the bottom of the page and I didn’t really know how to get on the right-hand side of the page. In nanoc I could just float: right it, in Webby I felt I had to understand the grid that had been created for me. I’m not sure it really allowed you to use any CSS knowledge someone might already have but the benefit is you know your site is going to look good across browsers and in print and so on. For more professional site development this might actually sway you to select Webby.
Jekyll is primarily a tool for publishing a blog style site so it has a lot of built-in support for special information relating to posts but in terms of layouts it uses general HTML templating like Nanoc does. It allows for the creation of little chunks of reusable content across pages via includes but lacks some of the flexibility of Nanoc’s tag helpers. While focussing on blog publishing Jekyll actually encompasses a powerful set of processing tools for content that effectively allows you to use it as CMS. Jekyll is used to process GitPages on GitHub, a real demonstration of its power beyond just blogging.
For what I wanted to do I initially felt that Nanoc was the best choice, it’s flexible, powerful and generates nice sites. Webby is powerful but didn’t expose that power to me in a way that made me feel in-control. However when I started to get to grips with Jekyll I was really amazed at how powerful the use of a few conventions were. Jekyll processes your site’s pages effectively in-place. It can choose to process your files if they match a naming convention (such as having a content extension like textile or markdown) and it uses an embedded YAML section in the file to do things like provide the title of the page or select the layout that the content should be displayed within. While Nanoc produces fancy URLs Jekyll made it easy to build more conventional websites consisting of clusters of pages.
Jekyll uses a small number of special directories (indicated by a leading underscore) to hold things like layouts, cross-page snippets and posts (if you are using the dated posting functionality). However for a simple site the number of directories and configuration files was significantly less than Nanoc. In fact you could get by with just a master page layout, which would require just one special directory and page within it. Everything that should have been simple was with Jekyll and the result was very close to a conventional website you might have coded by hand but extremely fast to create. It also uses just one command to press the pages and fire up a local server to view the pages. Both Webby and Nanoc seemed to make pressing and previewing slightly harder than it needed to be and at least once I forget to execute the Nanoc commands in the right order.
So, conclusions… Going forward I will be using both Nanoc and Jekyll. Webby I would be willing to consider but I don’t really have a task for it that would reward the additional effort I have to invest in its capabilities. If I just want to bang out pages for a website but minimise my effort and make it easy to abstract common content then I will definitely be using Jekyll. It is a joy to use. For sites that are maybe more based around articles or grouped content then I think I will be using Nanoc. The default URL construction is nice for hierarchical data (as long as you can stand the many directories) and there’s a sense that the configuration files make it easy to make changes that affect the site as a whole. However it does use a lot of scaffolding to achieve the effect and there are a lot of exposed options that could have been reduced by adopting some conventions Jekyll style.
9 thoughts on “Semi-static CMSs”
Thanks for the information, I too consider running a static website but I don’t have the time to compare them all (…). I too was surprised to see that webby has so many dependencies, and then I was again surprised to see that nanoc doesn’t have any dependencies at all!
So, here’s my 3 reasons for running a static web site generated by a web site generator.
1. Security; A static web page is also much more secure than a dynamic one.
2. You can outsource dynamic features to services like Google Friends Connect.
3. Versioning; The source files for a static site are stored as flat text files, this means that you can easily store the site in a versioned repository (Subversion, Mercurial, git, darcs, Bazaar, etc.).
Nice, thanks for posting. I really like the simplicity on edit my content using my favorite tools/editors but also like plugins and integration features used in dynamic CMS like WordPress, Zine and others.
I’m trying to find a Python static site generator. I’ve started to write my own but I don’t want to spend much time reinventing the wheel.
Have you had a look at webgen (http://webgen.rubyforge.org)? It is very similar to Webby and nanoc and easy to use for creating a normal static site – blog support is not really there but in the works.
I hadn’t seen it at the time but I have seen it since. I’m willing to give it a go.
I’ve been using Webgen for a few sites now, it’s pretty good although it does need some more work on the blogging side. I have a list of static site generation tools at http://yakisoft.tumblr.com/post/1086216579/static-web-site-generation
I’ve been honing my own solution to this problem, and I’ve called it Woodcut. It uses Mako templates and is written in Python. I’d love some feedback on the project!
Interesting. I was thinking of looking of the Python alternatives in an update to the post so I’ll be sure to give Woodcut a go.
I bumped into this post while researching about static site generators. Although this post is from year 2009, my conclusion from it is to give nanoc and Jekyll a look (excluding Webby from the list for now).
I do have one question though. I haven’t read all your posts, but when I looked at the source of this page I found that this blog is hosted on wordpress.com and you use WordPress to generate it. Would you care to elaborate why you didn’t (or wouldn’t) pursue using a static site generator and why you chose WordPress despite the fact that your blog’s design *does not* use any fancy WordPress templates (not sure if you’re using any plugins either)? I’m just curious.
I think Jekyll (and derivatives such as Octopress) is much more significant then when I wrote this post originally. Jekyll is probably the first site generator to try now due to the ubiquity of GitHub.
As for the comparison with WordPress, well I do also have generate static sites but for me the differentiators are the features that you would have add in yourself:
1. WordPress is hosted so there’s no admin worries
2. It’s free if you carry advertising
3. You get great analytics
4. Commenting is built-in
5. WordPress provides social promotion of content
6. It has a non-technical interface
This blog is more of an evolving changing thing (like you commenting here on this old post), the static sites I’ve created are generally for creating archives of finite material.