Goal: network topology
Reader: Network engineers mapping devices, links, packets and traffic. Meta cluster: C — infrastructure & governance Scenarios: 4 · Examples: 4
Scenarios
| Scenario | Tier | Engines | Example files |
|---|---|---|---|
| route flows | T2 | echarts | lines-route-flows.md |
| packet layout | T2 | plantuml | packet-layout-tcp-header.md |
| enterprise network | T2 | plantuml | network-topology-enterprise.md |
| radial network | T2 | plantuml | radial-hub-network.md |
Reading order
Physical or logical topology with vendor stencils, packet layouts for protocol detail, route flows for traffic.
Engines in this goal
echarts— report-grade charts and dashboardsplantuml— diagrams with icon families and UML/ArchiMate/BPMN semantics
Details, limits and anti-patterns: ../engines/echarts.md · ../engines/plantuml.md.
Palette
Every figure takes its colours from a theme. Pick one in
../styles/palette.md — the token contract, the theme index and the
per-engine blocks all start there.
Most figures in this set want Default. Depart from it for the medium, not the topic: Print when it may be photocopied, Contrast for low vision or large-print handouts, Vivid when it will be projected, Accessible when colour must not be the only cue, Editorial for long-form reading, Slate for technical reference, Pastel when the figure sits inside gentle prose, Nord for a cool Nordic register. Every theme is designed for a light ground — the set has no dark page.
Don't
- Topology diagrams without a legend for link type or speed
- Using a force layout for a deliberately layered network