Guides

What the notation actually means, explained without assuming you have picked a tool yet. Useful even if you end up drawing it somewhere else.

A guide here explains one kind of diagram: what its boxes and lines mean, which conventions are the standard and which are just one tool’s habit, and how to read a diagram someone else drew. They are written to be useful even if you never open this editor. The notation is the standard, not the software, and what you learn here works in whatever tool your team already uses.

They spend their words on the parts people actually get wrong. The ER diagram guide, for example, is mostly about optionality, the circle on a crow’s-foot line that says whether a relationship may be empty, and about the extra table hiding inside every many-to-many line.

If you already know the notation and want a particular diagram made, the tutorials are the other half: the same subjects, with the clicks, the import formats and the limits of this editor spelled out. If you would rather edit something finished than start from nothing, the templates open a ready-made ER diagram, swimlane flowchart, UML class diagram or mind map straight on the canvas.

The list is short on purpose. A guide gets written when there is a notation worth explaining properly, not one page per search phrase. What the editor will learn to draw next, and so what is likely to get a guide, is on the roadmap.