C4 context and components
Levels 1 and 3, building on the existing container diagram.
ProposedThe diagram library
Start with a question.
Find the form that makes the answer visible. Every preview comes from a real example in the repository.
11 of 11 types
Architecture01
AWS architecture poster
Which services exist, and how does a request move through them?
Official icons, account and zone frames, and numbered arrows show the flow in order.
Process02
Numbered-step flow
In what order do things happen between systems?
Each arrow has a number and an adjacent label, so the story can be read without a separate legend.
Architecture03
C4 container diagram
Who uses the system, how is it divided, and what does it depend on?
C4 level 2 notation with a fixed legend and numbered relations labeled with their technology.
Process04
Sequence diagram
Who calls whom, in what order, and what comes back?
Activation bars, alt frames and loops are calculated by coordinates, without automatic layout.
Process05
Process06
BPMN 2.0
What is the formal process, and can it be edited later?
Produces a .bpmn file that opens in Camunda and bpmn.io, alongside the PNG.
Process07
State machine
Which states can an entity enter, and what triggers each change?
The graph gate rejects unreachable states, non-final states without an exit, and transitions out of a final state.
Data08
ER diagram per schema
Which tables exist, and how are they related?
Starts from DDL, with crow's-foot notation, one schema per diagram, table roles in color and a fixed legend.
Data09
Schema dependency matrix
Which schema depends on which?
Shows coupling between schemas without drawing hundreds of arrows.
Comparison10
Comparison table
Which option should we choose, and why?
One criterion per row, one option per column, with the recommendation marked.
Comparison11
Cards catalog
What is in the inventory, and who owns it?
The same structure across every card works for APIs, events, teams and products.
Next on the drawing boardComing soon
Eight proposed types. None started yet.
Network and VPC
Subnets, routes, endpoints and connections, without the business flow of an AWS poster.
ProposedTimeline and roadmap
Milestones, phases and dependencies for presentation.
ProposedDDD context map
Bounded contexts and the relationships between them.
ProposedData flow diagram
Where data comes from, where it is stored and where it goes, with its classification.
ProposedUser journey
Stages, channels and friction points arranged in bands.
ProposedDecision tree
Questions, answers and outcomes for business rules and triage.
ProposedOrganization chart and RACI
Responsibility shown as a tree or a matrix.
Proposed