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.
Search is often where editorial products quietly lose their performance budget. The easiest implementation is to send too much data to the browser and call it good enough.
Keep the client index compact
- Titles, descriptions, categories, and tags usually carry enough relevance for a first version.
- URL-synchronized state matters because search is more useful when the result can be shared.
- A noindex search route keeps low-value permutations from leaking into the crawl surface.
Static-first still leaves room for usefulness
The goal is not to mimic a full search engine. The goal is to make discovery fast, predictable, and cheap enough that the rest of the publication can stay mostly server-rendered.
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.
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.
Dispatch
Notes for people shaping content-heavy products.
Occasional essays on editorial systems, search surfaces, and frontend architecture that keeps publishing teams fast.