Project Setup

An AkashaRender project directory has these attributes:

  • package.json This file lists dependencies on Node.js packages used to build the project, and a scripts section containing commands to drive the rendering and deployment process.
  • Several input directories to hold project assets, content files, layout templates, and partials (smaller templates).
  • One or more AkashaRender configuration files, e.g. config.js, describing the rendering process. Typically there will be one configuration file, but sometimes you'll need more than one to reuse the same content for multiple destinations.
  • (Optionally) Another Node.js script containing DOM processing functions for use with the Mahabhuta engine.

AkashaCMS is written for the Node.js platform, and therefore requires that you install Node.js first. If you don't have Node.js installed the npm commands above will have failed.

The first stop is the ( Node.js download page where you'll see all the download options. You may prefer to install via a package manager for your system, which is also documented on

A quick test is to run these commands

$ node --help
$ npm help

Simple project initialization

We made the ( repository available to use as a starting point for your website. You can simply clone that website and start hacking away. Or, read on to see how to set up an AkashaCMS project from scratch.

Start by making a project directory:

$ mkdir myproject
$ cd myproject
$ npm init
... answer all the questions asked by npm init

Is this ok? (yes) yes

Then install AkashaRender, Mahabhuta and globfs.

$ npm install globfs akasharender mahabhuta --save

If this project is to generate an EPUB3, then you must also install epubtools:

$ npm install epubtools --save

Next, make some directories:

$ mkdir assets documents layouts partials

Make an empty CSS file (or fill it with CSS of your desire)

$ mkdir assets/style
$ touch assets/style/main.css

It's also easy to use LESS that is autocompiled to CSS. Do this instead:

$ mkdir documents/style
$ touch documents/style/main.css.less

We'll go over this later, but AkashaRender automatically compiles LESS code to CSS when the file is named with this double extension.

A simple template file

Create a simple layout template as layouts/page.html.ejs containing

<!doctype html>
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
<title><%= title %></title>
<link rel="stylesheet" href="/style/main.css"
      type="text/css" media="screen"/>
<%- content %>

The double file extension is a convention in AkashaRender meant to indicate

  • filename.css.less: The file is first compiled from LESS, and is output as CSS to: filename.css
  • filename.html.ejs: The file is rendered with EJS, and is output as HTML to: filename.html
  • The file is rendered with Markdown, and is output as HTML to: filename.html

The template file demonstrates two types of content inclusion, using EJS. With <%= title %> we are inserting a metadata value with interpolation such that any HTML tags get encoded. However with <%- content %> the metadata value is not encoded, so that any HTML tags are copied verbatim.

The content variable is special in that it's the result of the previous rendering. All other values we might include come from the frontmatter.

A simple content file

Now let's create a simple content document, as documents/

layout: page.html.ejs
title: Four Score and Seven Years Ago

Four score and seven years ago our fathers brought forth on this continent a new nation conceived in liberty and dedicated to the proposition that all men are created equal.

The frontmatter appears between the --- lines. It is formatted with YAML, a fairly simple markup system to represent data objects as simple text. The best documentation I know of for YAML is on the Wikipedia: (

The way to interpret the file name is to think of multiple extensions that describe the conversion process and the final output format. In this case the file is written in Markdown, and produces HTML.

A simple configuration file

An AkashaRender configuration file is actually a Node.js script. It contains Configuration commands describing how to render this content for a specific destination.

A typical name for this file is config.js.

'use strict';

const akasha  = require('akasharender');

const config = new akasha.Configuration();



    recognizeSelfClosing: true,
    recognizeCDATA: true


module.exports = config;

The akasha.Configuration object contains all the data describing the rendering of input files to produce an output - such as an eBook or website.

The first section we show tells AkashaRender the input directories to use, and their purpose. These commands aren't entirely necessary, because of the baked-in default directory names. But, if you need to change the names you can use these functions.

The .setMahabhutaConfig method is necessary for the Mahabhuta DOM processing engine. Mahabhuta supports a jQuery-like API for processing HTML during the rendering process. Because it uses Cheerio under-the-covers, the values specified in this object actually from the Cheerio project.

The .prepare method adds the baked-in default configuration values so that AkashaRender will be able to function even if you forgot to declare something.

The last line is required for AkashaRender to access the configuration data.

A simple build process

The last thing is to set up the scripts section of the package.json with tasks used in building the project:

"scripts": {
  "clean": "rm -rf out",
  "prebuild": "akasharender copy-assets config.js",
  "build": "akasharender render config.js"

This defines two commands, which you can run as so:

$ npm run clean
$ npm run build

And the project is built for you.

The akasharender command takes several commands, two of which we see here. With copy-assets it copies files from the assets directory to the renderDestination directory. The assets files are ones which AkashaRender does not manipulate, instead they're copied verbatim. The second command, render, is where AkashaRender does manipulate files. These files are located in the documents directory, and are rendered into the renderDestination directory.

The configuration file is named on the command line so that you can use different configuration files for different purposes. For example it's possible to take the content of an eBook and render it into an EPUB file or as a website, simply with different configuration files.

Project Setup

( comments powered by Disqus