Design · 9 nodes
Design for clarity
A short route from finding an article to reading it comfortably, using clear hierarchy, spacing and familiar interaction patterns.
Browse the reading orderIs this path right for me?
Nothing is tracked and nothing is locked — the map exists so you can see where an article sits.
-
Make an article index scannable
Give readers a clear path through an article index by making the topic and title prominent, then placing summaries and metadata in supporting roles.
- Hierarchy
- Scanning
-
Reveal a large library in useful layers
Help readers explore a large catalogue with useful topic previews, clear routes to every article, and search that reveals all relevant matches.
- Progressive disclosure
- Browsing
-
Write titles and links that guide readers
Make article lists easier to scan with specific titles, front-loaded summaries, descriptive section headings, and links that name their destinations.
- Labels
- Navigation
-
Recover from an empty search
Make zero-result searches understandable and recoverable with a clear explanation, visible scope, useful next actions, and honest feedback.
- Search
- Empty states
-
Use familiar patterns for discovery
Use familiar navigation and search patterns to help readers find articles, then test whether your distinctive design still makes the next step obvious.
- Jakob's Law
- Finding articles
-
Build a consistent spacing system
Use a small spacing scale to show which interface elements belong together, separate article cards clearly, and give page sections room to breathe.
- Spacing
- Grouping
-
Set a comfortable reading rhythm
Choose a calm text width, line height and heading rhythm for long articles, while giving diagrams and tables the space they need.
- Typography
- Long-form reading
-
Pair visual appeal with usability
A polished article can feel easier to use while hiding real friction. Learn how to shape a calm reading page and test whether readers can actually use it.
- Aesthetics
- Reading experience
-
Test what a prototype can prove
Match each product assumption to evidence that can answer it. A room-booking example separates usability, demand, feasibility and running the service.
- Prototype test
- Evidence