Content strategy
Designing archive pages that carry their own SEO weight
Why category archives deserve their own voice, metadata, and internal-linking intent instead of behaving like disposable filters.
Archive pages should not feel like accidental byproducts of a taxonomy system. If a category route is indexable, it needs its own framing, its own internal-linking purpose, and enough editorial intent that a reader understands why the page exists.
The archive needs a point of view
- It should explain what kind of work lives inside the category.
- It should link readers toward the strongest representative articles.
- It should reinforce the publication's information architecture instead of duplicating the main archive.
Metadata is part of the product surface
For a portfolio project, category pages are useful because they expose a second layer of SEO competence. They prove that metadata, canonical URLs, and structured data are not glued only onto article routes.
When archive pages share the same content domain as the main blog, they become easier to test and harder to let drift.
Keep reading
Keep reading
Editorial systems
Introducing Inkwell's MDX publishing pipeline
A first production-shaped article that proves local MDX content, static routing, and editorial rendering can move together.
Search experience
Building a static search experience that stays lightweight
A practical approach to search pages that feel responsive without shipping full article bodies or introducing server-side search infrastructure.
Dispatch
Notes for people shaping content-heavy products.
Occasional essays on editorial systems, search surfaces, and frontend architecture that keeps publishing teams fast.