nera

Nera - a lightweight static site generator

Nera is a really simple static site generator. It creates static html files out of
Markdown files.

Please be aware of that this software is still under development. It might be that there will be changes which are not compatible with former versions.

Get started

Make sure you run at least Node version 10.2 on your system

git clone [email protected]:seebaermichi/nera.git

# Install dependencies
npm install

# Run local server (browser-sync)
npm run serve

# Render the static files
npm run render

# Local development
npm start

Directory and file structure

|-- assets/
|-- config/
    |-- app.yaml
|-- pages/
|-- src/
    |-- plugins/
        |-- plugin-helper.js
    |-- core.js
    |-- index.js
    |-- render.js
    |-- setup-plugins.js
|-- views/
|-- index.js

Assets

Are all CSS, JavaScript, font and image files which are used on your website. During the render process all assets are copied to the public directory.

Config

Here you can define global settings for your website. All the global settings should got to the config/app.yaml. Like lang, name, etc. They will be available in the data.app object within source or plugin files or as app object within the view files.

Pages

Within the pages directory you add the Markdown files which actually include meta information or settings and the content of your page. Find more information about the Markdown files below.

Src

The src directory includes the app itself. Here you find the core.js, index.js, render.js and setup-plugins.js files which include all the functionality to read the markdown files, get the settings, load plugins, copy assets and render the Html files into the puplic folder.

Plugins

The src folder also includes the plugins folder. In it you would place additional functionality.
Have a look at the current collection of available plugins.

Views

In the views directory you put all the layout files. We use pug as a templating framework.
In addition to the content of the markdown file there is also more data available. There is one app object, which includes all the properties from the config/app.yaml file. The other object is the meta object. Where app includes data relevant or usable on every page the meta object only includes data for the page itself. Therefore it includes by default all the properties and values you define in the meta section of the markdown file. In addition it includes

createdAt
is datetime when the markdown file was created

href
is the path to the current html file

dirname
is the dirname of the current html file

The meta object could of course also include more data depending on what your plugins add to id.

Page Markdown files

Each Markdown file which includes the content of a dedicated webpage needs to have some settings in the head. See an example below:

---
layout: pages/default.pug
title: Homepage
---
# Content
Content goes here...

Of course you can add many more so called meta data. It will be available in the view files as meta object.
In addition the basic config values are available within the app object.

Translations

If you want to use Nera for your multi-language website, you can do this easily by adding translations to the app config file and use the t function in your pug templates.
config/app.yaml

...
translations:
  en:
    app_description: Nera is an easy to use and light weight static site generator
  es:
    app_description: Nera es un generador de sitios estáticos liviano y fácil de usar

views/layouts/layout.pug

...
head
    ...
    meta(name="description", content=`${ meta.description || t('app_description') }`)
    ...

The t function will search for the key in the translations of the app config file and will return the translation for this key. If it can not find the translations property or if there isn't the given key within the translations the function will just return the key.

Links

• Read about how Nera is used to create the Nera website