Engineering documentation that stays close to the code
Engineering documentation rots when it lives away from the work. Flocci Library keeps specs, ADRs and runbooks in a space per team with syntax-highlighted code blocks, inline SVG and iframe embeds for diagrams, and @mention chips linking every spec to the runbooks and decisions that depend on it.
The unit of engineering knowledge is not a document, it is a decision plus its consequences. Library models that directly: an architecture page @mentions the ADRs that shaped it, and each ADR's Links panel shows every page that references it — so the blast radius of a decision is visible without anyone maintaining an index.
Code survives the round trip. Code blocks are syntax-highlighted and inserted from the slash menu; raw HTML and inline SVG blocks render diagrams without a screenshot pipeline; iframe embeds pull in anything hosted elsewhere; and attachments carry the artefacts that will not paste.
Because Library is one of six Flocci Work Apps on a shared backend, a Projects issue can link to the spec page that defines it — a real row in the cross-app link graph, not a URL pasted into a description field that nobody updates.
How to set it up
- One space per service or team; a top-level page per subsystem.
- Write ADRs as child pages under the subsystem they change.
- Paste code into code blocks and diagrams as inline SVG so both stay editable.
- @mention the spec from every runbook that operationalises it.
- Link the Projects issue to its spec page so the work and the words move together.
Frequently asked questions
Does Flocci Library support code blocks and diagrams?
Yes — syntax-highlighted code blocks from the slash menu, plus raw HTML and inline SVG blocks for diagrams, iframe embeds for anything hosted elsewhere, and file attachments. Tables and native bar, line, pie and area charts are built in too.
How do I stop architecture docs going stale?
Reference pages instead of copying them. An @mention chip re-resolves the live title, so renames never break links, and the target page's Links panel lists everything that depends on it — which makes the pages needing an update obvious when a decision changes.
Related use cases
Internal wiki software your team will actually use
Internal wiki
Employee handbook and onboarding wiki software
Handbook & onboarding
Start writing in Flocci Library
Personal spaces are free — the full editor, backlinks, search, share links and free monthly AI credits. Organisations are ₹49 a seat.
Get started free