Pith
Pith is a static website generator, written in Ruby.Using Pith, you can:
- Lay-out your page designs in Haml, ERb, or Liquid.
- Style things up using Sass.
- Succintly add content using Markdown or Textile.
- Encapsulate common markup in "layout" and "partial" templates.
- Easily link pages (and resources) using relative links.
- Test changes quickly using the built-in web-server.
Install it
Pith is packaged as a Ruby gem. Assuming you have Ruby, install it thusly:gem install pith
Quickstart
Create an input directory for your site (wherever you want), and pop some files into it:SITE/
_pith/
images/
logo.png
index.html.haml
_pith". Pith checks that it's present, to prevent you accidently treating your entire home directory as website input.Next, use the
pith build command to convert your inputs into a functioning website.$ pith -i SITE build
Generating to "SITE/_out"
--(copy)--> images/logo.png
--(haml)--> index.html
_out", inside the input directory ... but the default can be easily overridden, e.g.$ pith -i SITE -o OUTPUT build
Templates
Files in the input directory are considered to be "templates" if the file name ends with a template format extension recognised as such by Tilt, e.g. ".haml", or ".textile". These will be evaluated dynamically. Pith strips the format extension off the file name when generating output.Tilt supports a wide variety of formats, including:
At one end of the spectrum are the "template engines", like ERB/Erubis and Liquid, which allow insertion of dynamic content into a template. These aren't really HTML-specific; they can be used to generate any output format ... really, they're just string interpolation on steroids.
At the other end of the spectrum are "markup formats" like Markdown, Textile, Creole, which are targeted specifically at HTML output ... but don't support insertion of dynamic content.
In the middle are hybrids like Haml, and Markaby, which are both HTML-focused, but support dynamic content.
Pipelining
If you want both dynamic content, and simplified markup, in the same template, one option is to use Haml.The alternative to Haml, if you want both dynamic content, and less angle-bracket, is to combine a template format with a markup format. For example, you can create a "page.md.liquid" template, which would undergo first Liquid template expansion (for dynamic content), and then Markdown processing (for generation of HTML).
Resources
Any non-template input files (we call them "resources") are just copied verbatim into the output directory.Ignored files
Files or directories beginning with an underscore are ignored; that is, we don't generate corresponding output files. They can still be used as "layout" or "partial" templates though; see below.Page metadata
A YAML header can be provided at the top of any template, defining page metadata. The header is introduced by a first line containing three dashes, and terminated by a line containing three dots.---
title: "Fish"
subtitle: "All about fish"
...
page.meta" Hash:%html
%head
%title= page.meta["title"]
%body
%h1= page.meta["title"]
%h2= page.meta["subtitle"]
Since the page title is such a common thing to want to specify in the header, it's also available as "
page.title", as a shortcut (if no explicit title was provided, Pith will guess one from the input file name).Partials and Layouts
Templates can include other templates, e.g. = include "_header.haml"
= include "_list.haml", :items => [1,2,3]
%ul
- items.each do |i|
%li= i
= include "_mylayout.haml" do
%p Some content
yield":!!!
%html
%body
.header
... blah blah ...
.main
= yield
Layouts can also be applied by using a "
layout" entry in the page header, e.g.---
layout: "/_mylayout.haml"
...
Some content
Relative links
It's sensible to use relative URIs when linking to other pages (and resources) in your static site, making the site easier to relocate. But generating relative-links from partials and layouts is tricky. Pith makes it easy with the "href" function:%a{:href => href("other.html")} Other page
%img{:src => href("/images/logo.png")}
href" always returns a relative link.There's also a "
link" function, for even easier hyper-linking:link("other.html", "Other page")
Configuring Pith
The behaviour of Pith can be customised somewhat, by dropping a "config.rb" file into the "_pith" directory.There are a couple of flags that can be set to modify generation of links using "
href" and "link":project.assume_content_negotiation = true
project.assume_directory_index = true
assume_content_negotiation is enabled, Pith omits the ".html" suffix from links. When assume_directory_index
is enabled, Pith abbreviates links to "index.html" files. Both of
these assumptions work nicely when the generated files are served using a
web-server such as Apache httpd, but aren't appropriate if you wish to
navigate them as static files on the filesystem.It's also possible to mix behaviour into Pith, using the config file, e.g.
project.helpers do
def handy_method
# ...
end
end
project.helpers block are available for use in templates.For a more extensive example of a config file, look over here.
Incremental rebuild
For quick prototyping, use the "watch" command, rather than "build".
After building your site, Pith will stay running, and regenerate
output files (as necessary) as you edit the inputs. We keep track of
which input files are involved in the production of each output, so only
the affected outputs are re-generated.$ pith -i SITE watch
Generating to "SITE/_out"
--> images/logo.png
--> index.html
# ... edit "index.html.haml" ...
--> index.html
Built-in web-server
For even quicker prototyping, Pith includes a simple HTTP server. Start it by using the "serve" command, rather than "build"$ pith -i SITE serve
Generating to "SITE/_out"
--> images/logo.png
--> index.html
Taking the Pith at "http://localhost:4321"
>> Thin web server (v1.2.7 codename No Hup)
>> Maximum connections set to 1024
>> Listening on 0.0.0.0:4321, CTRL+C to stop
from https://github.com/mdub/pith
related post: http://briteming.blogspot.co.uk/2012/04/blog-post_6959.html