• Python 36.2%
  • HTML 22.3%
  • TypeScript 18.5%
  • Lua 13.4%
  • Shell 6.4%
  • Other 3.2%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-07-29 14:00:00 +01:00
.ai feat: records publish — no-CI delivery to a pages branch or rsync webroot (recordkit 0.5.0) 2026-07-29 10:16:31 +01:00
.claude feat: add session skills and featured pinning 2026-07-05 03:00:28 +02:00
.forgejo/workflows refactor: extract build logic to bin/build.sh for reuse in CI and CLI 2026-07-28 23:42:56 +01:00
.github/workflows feat: forge-aware repo links + GitHub/GitLab CI shims 2026-07-29 10:23:04 +01:00
.mem feat: add recordkit engine + .mem/ for AI-free records skills 2026-07-21 11:40:22 +01:00
bin feat: explicit baseURL wins over CI derivation; add publish params 2026-07-29 10:09:22 +01:00
docs docs: add developer roadmap and vision planning conversation 2026-07-29 14:00:00 +01:00
records feat: add demoMode param for theme-shipped demo content 2026-07-28 20:59:36 +01:00
static chore: track the fork-owned static/ dir (configured in staticDir, was absent from fresh clones) 2026-07-29 11:03:33 +01:00
tools fix: upgrade GitLab CI Hugo image to 0.164.0 2026-07-29 12:38:54 +01:00
.gitignore refactor: move hugo, others, pandoc into tools/ directory 2026-07-28 21:23:19 +01:00
.gitlab-ci.yml fix: upgrade GitLab CI Hugo image to 0.164.0 2026-07-29 12:38:54 +01:00
CLAUDE.local.md.example.md fix: upgrade GitLab CI Hugo image to 0.164.0 2026-07-29 12:38:54 +01:00
CURRENT chore: werden postkasse-flue — the provider-agnostic release (0.2.1) 2026-07-29 10:27:59 +01:00
LICENSE.md refactor: move hugo, others, pandoc into tools/ directory 2026-07-28 21:23:19 +01:00
README.md docs: add blyant reference link 2026-07-29 11:49:28 +01:00

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 awesomeHugo 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 homelabrecords 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 — 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

blyant