gitrep¶
A system that projects the md in a dir made for publishing onto a blog. It's used to generate this site (6umi Docs).
I came up with it as a way to publish information without changing how I manage things now: git and md based, with AI agents in the loop. Turning it into a blog is left to automatic generation as much as possible. Further down the line, I expect it to also serve as RAG in the broad sense (material for AI to reference).
flowchart LR
src["公開用の dir<br/>(gitrep.toml で opt-in)"] -->|射影| engine["gitrep<br/>(engine)"]
engine -->|md| dest["dest repo<br/>(Zensical)"]
dest -->|build / deploy| web["doc.6umi.net"]
- Input is per dir. A dir is read only when it has a
gitrep.tomland is also on the allowlist. A whole repo is never taken as input - The engine (which decides what to output) and dest (which turns it into html and serves it) are separate repos
Zensical¶
The html part is left to Zensical. It's a static site generator that builds a full site from a folder of md and a single config file. It's the successor made by the Material for MkDocs team, and has blog and RSS built in.
- The first version in 2026-08 was built with Material for MkDocs. It went into maintenance mode, so on 2026-10-05 I moved to Zensical
- Zensical's roadmap includes "combining multiple independent projects into one site." That's the same direction as gitrep, which gathers multiple dirs into one site
- It's still 0.0.x and not battle-tested. The blog feature only landed in 2026-09. I adopted it betting on its momentum and on its being the official successor
- The template is the stock one. Only the colors were changed with CSS to match krkn (the board on 6umi)
Images¶
Images are uploaded to Cloudflare R2 and referenced from articles by a.6umi.net URLs. Since I ended up using R2, I also moved the storage for 6umi's uploader to R2.
Created 2026-10-05 by lamutara · Updated 2026-10-09 by lamutara · 8 revisions · Machine-translated from the Japanese original.