blyant records

Your records, published. Drop Markdown into records/, get a website — blyant records is your own publishing datamaskineri.

Fork, enable Actions, push — your words appear at https://<you>.codeberg.page/records/ (or your own domain name). A fresh fork starts as a working demo site; your first record replaces the demo automatically.

The front page explains the rest: https://blyant.codeberg.page/records/.

Make it yours

It ships with Fuglekasse, a small default theme you restyle from tools/hugo/hugo.yaml or replace. Some like it simple, some like it awesome — Hugo has it all.

Publish anywhere

• Codeberg — fork, enable Actions, push. Zero edits.
• GitHub — enable Pages once (Source: GitHub Actions), push.
• GitLab — push.
• Your own machine, VPS or homelab — records publish delivers to a pages branch or any webroot over rsync; no CI at all.

One build path behind all of them — details in publish anywhere.

Record from your projects

Clone your fork inside any project — the recording skills follow, transcripts land in the clone, and /cpd pushes it home. Nothing to configure — home is where the clone is.

Record together

Teams, friends and lovers can share one blyant records instance. Add them as collaborators on your fork, and they clone, they write, they commit — commit to it. Every push publishes to the same site.

Who is who? It's all in git. Each record carries its author in the history — git log records/ never forgets. One site, many voices, and git is init together.

Record on your own

The skills also run without big-tech AI: a small engine drives the mechanical ones from a VSCode chat sidebar, a Neovim split, or plain shell — no model needed. Add Ollama and /record talks back: your own local model, your records, your machine.

---

Fase — 0.2.2 postkasse-beetle

blyant