Block editor
Headings, lists, checklists, quotes, tables, images, syntax-highlighted code. Drag-and-drop reordering of blocks.
A knowledge base that knows about your data
Struktura documents can reference table records, update automatically, and are co-edited without conflicts.
demo-стенд · Регламент работы с лидами
Демо-стенд скоро поднимется.Здесь будет настоящая публичная ссылка на «Регламент работы с лидами» из продукта.
Problem
A document disconnected from data quickly becomes stale
A regulation is written, the document is saved — and forgotten. Six months later the table fields have changed but the doc still shows the old instructions. Struktura links documents to specific records: change the record and the mention updates.
Features
Block editor with record mentions and Yjs sync
Links to records
Reference a table record right in the text — Struktura pulls in the name, status, and icon. Change the record and the mention updates.
Slash menu
The '/' command opens an insert menu: block, template, mention, image, video, formula, table object.
Mentions
Mention users and groups — they get a notification. Mention other pages — you get a backlink.
CRDT sync
Yjs under the hood. Multiple people editing simultaneously — without conflicts, with presence cursors.
Version history
Per-block history and a page-wide timeline. Roll back to any version with one click.
Page templates
Create a template for 1:1 meetings, PRDs, postmortems. A new page is created in two clicks.
Export and sharing
Markdown export, page sharing by link with 'read only' or 'comments' rights. External users don't need an account.
How it works
From an empty page to a living knowledge base
- 1
Create a root page
The knowledge base lives as a tree. Roots — HR, IT, marketing, regulations.
- 2
Use templates
Templates for meetings, PRDs, postmortems, and onboarding save hours every week.
- 3
Connect to data
Mention table records right in the text — a runbook references a component and an incident.
- 4
Open it to the team
Grant permissions, add upper-level pages to favorites. For external users — sharing by link.
Scenarios
Documents alongside process data
Internal knowledge base
Regulations, guides, and instructions live next to process data. Change a table record and the mention in the document updates automatically.
- Templates by document type: regulation, instruction, FAQ
- Backlinks: see who references this page
- Collaborative editing without file locking
On-call runbook
Each runbook is tied to a component in the services table. An incident is a record that references the runbook and component. Context is assembled instantly.
- Checklists inside the page with completion state
- @on-call mentions with chat notifications
- Versioning: see who and when changed a runbook step
Comparison
How Struktura documents differ from Notion and Confluence
| Возможность | Struktura | Notion | Confluence | Google Docs |
|---|---|---|---|---|
| Block editor | ✓ | ✓ | basic | — |
| Table record mentions | ✓ | basic | — | — |
| CRDT sync | ✓ | ✓ | — | Google Docs only |
| Per-block version history | ✓ | ✓ | — | — |
| Page templates | ✓ | ✓ | basic | — |
| Backlinks | ✓ | ✓ | — | — |
Gather your regulations and runbooks in one place
Migrate 5 pages for a pilot — we'll help with import from Notion and Confluence.