Tomes

Longer reading on how grim is put together and why. A tome has no steps and nothing to copy. Read one when a spell did what it says and you want to know why it works that way, or before a decision the recipes take for granted.

4 tomes 4 inked grim 1.0.0 GitHub

The tomes

4 of 4 inked

How grim is assembled

grim-core, modules, themes, a project, the CLI and the registry. Who writes each of them, where it lives, and which of them is only an artefact of another.

≈8 min

Release trains

Core, every module and every theme share one version line. What a train is, what moves it, and what a constraint in grim.json really allows.

≈10 min

Project and package manifests

grim.json, grim.lock, core.json, module.json, theme.json and the two generated module lists, each with its writer, its readers, a minimal example and its fields.

≈12 min

What grim owns in your project

Which files in a project are yours, which grim rewrites, which command rewrites them, and why the repository of a project holds almost nothing.

≈10 min