Diagrams are the part of documentation people skip. Not because they do not help — a diagram of an auth handshake explains it faster than four paragraphs ever will — but because making one means leaving your editor, opening another tool, exporting an image, uploading it, and then doing the whole dance again when the flow changes.
So the diagram either never gets made, or it quietly goes out of date and starts lying to readers.
Describe it instead
In FinalDoc you describe the thing in plain English and pick a shape. Ved AI asks a few clarifying questions — how much detail, who the audience is — then generates the diagram into your article as a real, editable diagram rather than a flattened image you would have to recreate from scratch next quarter.
Five diagram types are available:
- Architecture — the system parts that participate, and the data flowing between them
- Flowchart — a process step by step, with decision branches
- Sequence — participants and the messages passing between them, in time order
- Entity relationship — your data model as entities and the relationships joining them
- State — lifecycles and the transitions between them
Worth setting expectations on two of those. Sequence and ER diagrams are drawn as labelled node-and-edge graphs — a sequence diagram shows participants and their messages in order, but not the vertical lifelines of a classical UML diagram, and an ER diagram shows entities and how they relate, but not column-by-column table listings. They communicate the same thing; they do not look like a UML textbook.
Alongside diagrams, the same wizard produces charts — bar, line, pie, and side-by-side comparison — and can generate an illustration instead, if what you want is a picture rather than a graph.
Editable, not baked
Because the diagram is stored as structured data rather than a picture, changing it is an edit rather than a redraw. Hover it in the editor and click Edit: drag nodes, rename things, reconnect edges, or drop into a code view and change the definition as text. Add a step, rename a service, reorder two calls.
Your version history covers diagrams the same as any other content, so you can see what changed and when.
It renders where readers actually are
A diagram that only renders in the editor is a draft. Diagrams in FinalDoc render on your published knowledge base as an interactive canvas readers can pan and zoom — and, the part most tools quietly drop, inside exported PDFs too.
That second one took real work. Exports reuse the image baked when you saved the diagram; when there is none, the exporter renders the real published page and captures the diagram as it actually appears. The PDF renderer also ships its diagram library locally instead of fetching it at export time, so exports work identically in locked-down environments with no outbound internet access.
Rendered safely
Diagram content that becomes markup is a security question, so both diagram paths are closed off. Generated diagrams render through the canvas as ordinary text labels — never as raw HTML injected into the page. Hand-written Mermaid blocks, which you can also drop into an article, render in the library’s strict mode with their output sanitised before it reaches the page, and show an explicit error card rather than failing silently when the syntax is wrong.
Where to start
Open any article, type / for the slash menu, and pick AI Diagram. Architecture and flowchart tend to earn their keep fastest, because they are exactly the explanations that turn into walls of text when nobody draws them. If you would rather draw it yourself, the same menu offers a blank canvas and a Mermaid block.