As with all static site generators, nanoc lets you write your source files in
a simple markup language. Out of the box, nanoc offers you the choice of using
Markdown, Textile, reStructuredText or plain HTML (with or without embedded
Ruby). In fact, nanoc is nothing more than a generator honoring a
that tells it how to compile, layout and route the site’s items.
Compiling items ¶
compile '/static/css/*/' do # compress CSS :) filter :less filter :rainpress end
.less-files into compressed CSS:
Routing items ¶
After compiling (i.e. transforming content through filters) comes the routing
of the items. This is a means of assigning file names to compiled content.
nanoc calculates default files names from the input, but you can use this to
influence the default naming. A special case is where you set the route to
Nil which doesn’t write the file at all. I use this to test draft posts
locally, like this (oh, did I mention the
Rules file is 100% Ruby?):
route '/posts/*/' do if $include_drafts or @item[:published] then '/posts/' + @item.slug + '/index.html' end end
Laying out items ¶
Finally, layouts are applied. Layouts are kind of templates that can be used to “frame” the item’s contents. This is typically used for HTML files only, but isn’t limited to it. For example, the blog posts are compiled into (partial) HTML, and the layout rules put the site’s container HTML around it, adding CSS styling, jQuery scripts, the header, sidebars and footer and Google Analytics tracking (these go for each page). There’s a special extra layout rule for blog post pages, which additionally adds Disqus comments.
Each build of this blog also automatically:
- Converts Textile content to HTML
- Highlights syntax using pygments
- Converts less to CSS
- Minifies CSS
- Downsizes source images
- Generates redirect pages for alternative (old-style) URL’s (for user that have existing bookmarks to old WordPress URL’s)
- Generates a new blog post RSS feed
In short, now nanoc is fully configured to my wishes, I can simply focus on writing blog content, without preparing image content (it is done automatically), and without having to choose between either a “WYSIWYG” editor or writing HTML manually. And I can do it in an offline fashion, too, which was one my main complaints about WordPress.
So I’m happy.
Oh, and since I have been converting my blog anyway, I also created a new look and feel for it. I hope you like it. Feel free to comment.