Diagram Families
OpenFlowKit supports multiple diagram families because not every problem should be forced into the same node and edge model.
Families in the current editor
Section titled “Families in the current editor”| Family | Best for |
|---|---|
flowchart | General process and system flows |
architecture | Cloud, service, and platform diagrams |
mindmap | Branching ideation and hierarchical thinking |
journey | User journey or multi-stage experience mapping |
stateDiagram | State transitions and event-driven logic |
classDiagram | Object modeling and relationships |
erDiagram | Tables, entities, and relational structure |
gitGraph | Git history and branching flows |
How to choose
Section titled “How to choose”Use the family that matches the semantics of the diagram, not just the visual look.
- Choose
flowchartwhen the problem is procedural. - Choose
architecturewhen services, infrastructure, or trust boundaries matter. - Choose
mindmapwhen branching and hierarchy matter more than exact routing. - Choose
journeywhen stages, actors, and sentiment or score matter. - Choose
classDiagramorerDiagramwhen the relationships themselves carry meaning.
Why it matters
Section titled “Why it matters”Different families unlock different node behavior, import paths, layout assumptions, and inspector controls. Picking the right family early usually means less cleanup later.