Information accessibility for x12i products
Docify — one content library, two surfaces
Authors declare documentation truth once. Docify validates, indexes, renders a human site, and packs open Markdown plus an SDK for agents.
$ npm i -D @x12i/docify
Knowledge dogfood: npm i -D @x12i/docify-docs
Products change naming and content only — one design system for all.
Static web with journeys, search, and a non-iframe reader.
INDEX.md, SEARCH.json, packs, and createDocifySdk.
Cloudflare Pages for docs and optional product mini-sites.
The positioning
Authors declare truth. Docify does not invent it.
Docify does not discover product truth by scanning application source repositories. Authors write concepts, guides, scenarios, and diagrams; Docify packages and presents them.
Why it exists
# x12i-docify Platform Overview — Developers
What is different
**Audience:** Engineers wiring `@x12i/docify-*` into a monorepo or publishing a product knowledge SDK. **Twin:** [Builders version](../builders/BOOK.md) **Site:** this library’s web app · platform README at `x12i-docify/README.md`
What you get
## Install (start here)
Docify only builds knowledge that authors declare — it never discovers product truth from source.
Learn more →Every knowledge item ships as readable Markdown plus indexes — the SDK is optional.
Learn more →Marketing copy is a projection of existing docs truth — never invented — and only approved copy is publishable.
Learn more →$ docify build .