Caltech Library logo

Project Status: Active – The project has reached a stable, usable state and is being actively developed.

MkPage Project

MkPage Project is a collection of tools for rendering static websites. Featured is the mkpage command, a front end to Pandoc (>= v2.9.x). Pandoc supports converting from many lightweight markup languages. mkpage supports metadata encoded as front matter1 using YAML, TOML and JSON as well as additional data sources expressed on the command line in a simple command language. Content is rendered using Pandoc’s template language.

MkPage Project was inspired by deconstructing more complex content management systems and distilling the rendering functions down to a core set of simple command line tools. It is well suited for building sites hosted on services like GitHub Pages or Amazon’s S3. It uses the widely adopted Pandoc as its markup conversion engine and template engine. As such you can create your website using a variety of light weight markup languages such as Markdown, Textile, ReStructureText and Jira’s wiki markup.

The MkPage Project’s tools can run on machines as small as a Raspberry Pi. Their small foot print and minimal dependencies (only Pandoc) means installation usually boils down to copying the precompiled binaries to a bin directory in your path after a installing Pandoc. Precompiled binaries of MkPage Project are available for Linux, Windows 10 and macOS running on Intel as well as for the ARM7 versions of Raspbian running on Raspberry Pi.

MkPage Project’s minimalism is an advantage. It plays nice with the standard suite of text processing tools available with most Unix/POSIX compatible operating systems2. This makes scripting a MkPage Project using languages like Python, Julia, Lua, Make or Bash straight forward. Each mkpage utility is independent. You can use as few or as many or as few as you like. You determine the workflow and build process that best fits your needs.

A quick tour mkpage command

The mkpage command accepts key/value pairs as command line parameters. The pairs can be explicit data types, files on disc or resources from the web. Additionally mkpage will merge in any front matter found in your light weight markup such as Markdown documents. mkpage assembles the all metadata into a JSON structure which will be processed by Pandoc when rendering a Pandoc template. Additionally mkpage understands the Fountain markup language will will handle conversion before passing to onto Pandoc.

mkpage’s command language

The “key” in our key/value pairs is used to map into the Pandoc templates you want rendered. If a key was called “content” the template element would be like content < /code > .Thevalueof“ content” wouldreplace < code>{content} in the Pandoc template. Pandoc templates can combine logic and iteration to make more complex pages. See the Pandoc User Guide for more details.

On the “value” side of the key/value pair you have strings of one of several formats - plain text, markdown, fountain, ReStructureText, Jira text and JSON. The values can be from explicit strings associated with a data type, data from a file where the file extension identifies the content type, or content retrieved via a URL based on the mime-type sent from the web service. Here’s a basic demonstration of sampling of capabilities and integrating data from the NOAA weather website.

Next is an example of a basic Pandoc template followed by an example command line for invoking mkpage.

A basic template

    Date: ${now}
    Hello ${name},
    The weather forecast is
      ${[; ]}
    Thank you

To render the template above (i.e. weather.tmpl) is expecting values from various data sources broken down as follows.

typing the mkpage command

Here is how we would express the key/value pairs on the command line.

    mkpage "now=text:$(date)" \
        'name=text:Little Frieda' \
        'weather=' \
        'signature=examples/signature.txt' \

Notice the two explicit strings are prefixed with “text:” (other formats include “markdown:” and “json:”). Values without a prefix are assumed to be local file paths. We see that in testdata/signature.txt is one. Likewise the weather data is coming from a URL identified by the “http:” protocol reference . mkpage uses the “protocol” prefix to distinguish between literals, file paths and URL based based content. “http:” and “https:” returns an HTTP header the header is used to identify the content type for processing by mkpage before handing off to Pandoc. E.g. “Content-Type: text/markdown” tells us to use Pandoc to translate from Markdown to HTML. For data contained in files we rely on the file extension to identify content type, e.g. “.md” is markdown, “.rst” is ReStructureText, “.json” is a JSON document. If no content type is discernible then we assume the content is plain text.

MkPage Project Tools


mkpage is a page renderer and front end to Pandoc. It is used to aggregate metadata and templates into a complete website page. It serves as a pre-processor for Markdown, Fountain, ReStructureText, Textile, Jira markup, JSON using Pandoc as conversion and template engine.


blogit performs two tasks, first if given a filename and date (in YYYY-MM-DD format) blogit will copy the file into an appropriate blog path based on the date provided. The second task it performs is to maintain a blog.json file describing the content of the blog. This is placed in the same folder as the where the year folders for the blog are create.


mkrss is an RSS feed generator for content authored in Markdown. It can read a blog.json file created with the blogit and produce an RSS feed from it or scan the directory tree for Markdown files with corresponding HTML files and generate an RSS feed.


frontmatter will extract a light weight markup files’ (e.g. Markdown) front matter so you can process it with another tool. It can optional convert the front matter into JSON even if the front matter was defined in YAML or TOML.


byline inside a Markdown file’s front matter for a “byline” field and return it before scanning the file using a regular expression for the byline. If nothing is found in either the front matter or the regular expression then it’ll return an empty string.


titleline will look inside a markdown file’s front matter for a “title” field it if not present in the front matter it’ll look for the h1 demlimiter (Markdown ‘#’) and return it’s content. It will return an empty string if it finds none.


reldocpath is intended to simplify the calculation of relative asset paths (e.g. common CSS files, images, RSS files) when working from a common project directory.

Example reldocpath

You know the path from the source document to target document from the project root folder.

In Bash this would look like–

    # We know the paths relative to the project directory
    echo $(reldocpath $DOC_PATH $CSS_PATH)

the output would look like



sitemapper a simplistic XML Sitemap generator. Sitemaps are used by web crawls to find content in your website and can help your website be more search-able by modern full text search engines.


ws is a simple static file web server. It is suitable for viewing your local copy of your static website on your machine. It runs with minimal resources and by default will serve content out to the URL http://localhost:8000. It is a fast, small, web server for site development and copyedit work.

    ws Sites/

This would start the web server up listen for browser requests on http://localhost:8000. The content viewable by your web browser would be the files inside the Sites/ directory.

    ws -url Sites/

Assume the machine where you are running ws has the name then your could point your web browser at and see the web content you have in Site/ directory.

Problem Reporting and lending a hand

MkPage project is hosted at GitHub and bugs can be reported via the Issue Tracker. As an open source project pull requests as well as bug reports are appreciated.

Getting your copy of MkPage Project

You can find releases of MkPage Project at


MkPage Project is released under an open source license.

  1. Front matter in light weight markup languages like Markdown start at the top of the file and begin and end with a simple set of delimiters. (three dashes) is used for YAML, +++ (three plus signs) for TOML, open and close curly braces are used by JSON.↩︎

  2. Common POSIX compatible systems include macOS, Linux, and recent versions of Windows 10↩︎