Package · MIT
bip-kit
Blog, roadmap and changelog from repo-authored markdown. Typed blocks, your design tokens on top.
Why it exists
Writing that lives in a CMS drifts from the product. Writing that is a pile of regexes drifts from itself. The studio writes in the repository, reviewed like code, and needed one dialect.
How it works
Markdown in, typed blocks out: headings, figures, a table of contents, reading time. A reference React renderer is optional. Bring your own tokens; the kit does not own your look. A chart fence that is malformed fails at build time rather than on the reader's screen.
Where it fits
It is how the studio builds in public. OrangeCat's articles, Evig, Botsmann, DataCat and the others render through it, so a claim on a page and a claim in a commit are the same text.