- Python 36.2%
- HTML 22.3%
- TypeScript 18.5%
- Lua 13.4%
- Shell 6.4%
- Other 3.2%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
| .ai | ||
| .claude | ||
| .forgejo/workflows | ||
| .github/workflows | ||
| .mem | ||
| bin | ||
| docs | ||
| records | ||
| static | ||
| tools | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| CLAUDE.local.md.example.md | ||
| CURRENT | ||
| LICENSE.md | ||
| README.md | ||
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 publishdelivers to apagesbranch 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 — anywhere, under any name — and the
recording skills follow: invoked from the project workspace, they find the
clone and file transcripts there. /cpd commits and pushes the clone
itself, and the push publishes.
git clone https://codeberg.org/<you>/records.git
echo records/ >> .gitignore # or track it as a submodule
Nothing to configure: contentDir in the clone's tools/hugo/hugo.yaml is the
one source of truth, shared by Hugo and the skills.
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.1 postkasse-flue