Balzac

an experiment in building a static site generator using rust

Usage

• Install balzac
• Create a balzac.toml configuration file

Directory Structure

Balzac supports different directories that you are free to create or skip:

• pages_directory (required): directory that stores all the handlebars templates that will be used to create pages
• partials_directory (optional): houses all handlebars partials
• layouts_directory (optional): houses all handlebars layouts

Config Reference

• output_directory : the directory where the generated website will be sent to
• pages_directory (optional): the directory where static pages will reside (like your index)
• partials_directory (optional): directory where partial templates will reside
• layouts_directory (optional): directory where layout templates will reside
• assets_directory (optional): directory where static assets will reside
• content_directory (optional): directory where content (markdown) will reside
• global: fill this array if you want to have global data available in all the templates and files

Hooks

Balzac supports hooks that allow you to run shell commands at various phases of the build process. All hooks are optional and configured in the [hooks] section of your balzac.toml file.

Available Hooks

Hooks are executed in the following order during a build:

1. render_init_before: Runs before the renderer is initialized
2. render_init_after: Runs after the renderer is initialized
3. build_before: Runs before the dist folder is created
4. render_before: Runs before rendering static pages and collections
5. render_after: Runs after rendering is complete, before assets are copied
6. build_after: Runs after all build steps are complete

Hook Configuration

Example balzac.toml configuration:

[hooks]
render_init_before = "echo 'Preparing renderer'"
render_init_after = "echo 'Renderer ready'"
build_before = "pnpm build"
render_before = "echo 'Starting page generation'"
render_after = "echo 'Pages generated'"
build_after = "rsync -av dist/ production/"

Notes

• Hooks are executed in the project root directory
• If a hook fails (exits with non-zero status), the entire build process will terminate
• Hook execution time is logged for each hook
• All hooks support full shell command syntax with arguments

Collections

To use a collection, create a subfolder in the content_directory folder with the name of your collection (i.e. posts) and put your markdown files in there.

The next step is to create a file in the pages_directory called <name_of_your_collection>/details.hbs (i.e. posts/details.hbs).

Frontmatter

All frontmatter present in the collection documents will be available in the template under the fm namespace.

---
title: "Test"
---

will be available under fm.title

Development

All required tooling can be installed using mise with mise install