Case study / Editorial
Blog archive
A writing archive with article tiles, filters, tags, categories, reading metadata, and article pages.
- 3
- seed articles
- 2
- taxonomy routes
- 1
- RSS feed
Context / Role / Constraint
What the case needed to solve.
The blog domain holds writing and notes. Its design job is to make browsing, reading, and returning to related material feel natural.
Editorial IA, MDX article system, taxonomy pages, client search, and article reading components.
The archive needed quick filtering without making the main page feel like a generic dashboard.
Case process
From constraint to artifact.
The process is written as a working rail so the decisions can be audited, not only admired.
- 01
Model posts
Created metadata, excerpts, reading time, headings, categories, and tags around MDX content.
Post data layer - 02
Build browse paths
Added article index, taxonomy filters, category pages, tag pages, and related posts.
Archive navigation - 03
Support reading
Added table of contents, reading progress, typography rules, and RSS output.
Article shell
Selected screens / assets
Evidence from the work.
Archive taxonomy
The blog uses categories and tags as wayfinding, while search scans title, excerpt, and body.
- Article index with search
- Category and tag routes
- Reading progress
- Related post rail
Reading flow
The archive shifts from a list of posts to an editorial system with a return path after each article.
Post lists can be navigable but thin; they rarely show why an article belongs to the archive.
Every article carries metadata, taxonomy, table of contents, and related reading.
Result / Learning
What changed.
The app now includes an article index, search, category and tag pages, related posts, table of contents, reading progress, and RSS route.
Related cases
