Everything Kaze builds comes from files in content/. The generator never talks to a database or an API.

Editing files directly

Open the JSON files in any editor, change them, and run the build:

python3 build.py

While working locally, python3 dev.py rebuilds on every change and serves the site at http://localhost:8000. Refresh the browser to see changes.

Article bodies are a Markdown string inside the JSON file. Use \n for line breaks inside the JSON string.

Using Sveltia CMS (optional)

The admin/ folder contains a Sveltia CMS setup. Sveltia is an open-source, Git-based editor that runs in the browser and commits changes to your repository. It reads admin/config.yml, which follows the Decap CMS configuration format.

It does not work out of the box. You need to:

  1. Set repo in admin/config.yml to your GitHub repository.
  2. Provide GitHub authentication. GitHub OAuth needs a small server-side step, usually a Cloudflare Worker such as the Sveltia CMS Authenticator, set as base_url in the config.
  3. Deploy the site so /admin/ is reachable.

If you do not need a browser editor, delete the admin/ folder. The build does not depend on it.

Why files

Your content stays in Git, with full history, and you can move it to another generator later. The JSON fields are documented by example in the files in content/.