Question → Layout
Choose the layout that fits the mechanism: tree for hierarchy, matrix for dense ties, flow for process, radial for cycles.
A design-first view of complex diagrams: clear structure, disciplined encodings, and honest labels. Form follows mechanism — not the other way around.
Structure first Readable encodings Label discipline Perceptual honesty
Curation Principles
Encodings that Read
Prefer position/length over angle/area. Use color sparingly and always with text or symbols.
Honest Legends
Legends and labels are part of the design — not an afterthought. Every mark must be explainable.
Complexity with Restraint
Small multiples beat overloaded single charts. Remove decorative ink that doesn’t earn its space.
Reading Playbook
- Start with the question: comparison, change, or mechanism?
- Decode encodings: position, length, color, links, motion.
- Trace structure: hierarchy vs network; hub-and-spoke vs communities.
- Check uncertainty: sampling, smoothing, missing data.
- Try a simpler view: table or small multiples as a control.
Tip: prototype at two scales — phone width and desktop — before final polish.
Library Highlights
Network Maps
Structure over spectacle: matrices for density, edge-bundling for routes, radial for hubs.
Trees & Hierarchies
Pick between vertical, radial, icicle, and treemap by label length, depth, and comparison needs.
Flows & Timelines
Use Sankey sparingly; prefer stepwise flows and layered timelines with clear stages.
Maps & Projections
Normalize where needed; annotate context and uncertainty; never rely on color alone.
FAQ
Do you publish data or code?
When available we include method notes and assumptions. Clarity beats mystery.
Commercial work?
Accepted if it teaches a reusable idea and states constraints and caveats.
Licensing?
Images remain with their authors. We use minimal thumbnails and commentary under fair use or permission.