Documentation for remote and distributed teams
Remote teams pay for undocumented knowledge in timezone latency — a question asked at 6pm is answered at 11am tomorrow. Flocci Library shifts that to written defaults: pages instead of meetings, threaded comments instead of synchronous review, realtime updates across tabs, and search that actually finds the answer.
The habit to build is answering in the wiki, not in chat. A question answered in a message helps one person once; the same answer as a page, @mentioned from the relevant spec, helps everyone who searches later — and the Links panel makes it findable from the context they were already in.
Asynchronous review needs a home. Threaded page comments with mentions keep feedback attached to the sentence that caused it, so a reviewer eight hours away leaves precise notes and the author wakes up to something actionable rather than a meeting invite.
Realtime updates matter more when nobody shares a room: page trees, links and comments update live across open tabs via websockets, so two people working the same area do not discover the collision at commit time. Conflict-protected auto-save handles the rest.
How to set it up
- Set the norm: if the answer is longer than two sentences, it becomes a page.
- Give each team a space and each recurring question a page.
- Use comments for review; reserve calls for disagreement, not status.
- @mention aggressively — backlinks are what make an async question findable.
- Share outward with read-only links for contractors and partners.
Frequently asked questions
Does Flocci Library support live collaborative editing?
Not cursor-level co-editing. Pages, links and comments update in realtime across tabs and teammates, and concurrent saves are protected by a version check that refuses a stale write rather than silently overwriting. CRDT co-editing is on the roadmap, not shipped.
How do people outside the company read our docs?
Publish the specific page or subtree as a read-only share link. No login, no seat, and you can disable it or rotate its token to invalidate the old URL whenever the engagement ends.
Related use cases
Internal wiki software your team will actually use
Internal wiki
Engineering documentation that stays close to the code
Engineering docs
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