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.
Inkwell needs a real post before the broader content platform work is worth scaling. This first article validates the local MDX workflow, the archive route, and the reading experience in one thin vertical slice.
What the first slice proves
- Local frontmatter can drive route metadata, author attribution, and imagery.
- Static generation can treat posts as durable build-time assets.
- Editorial presentation can still support technical content without losing polish.
The post body also needs a code example because copyable blocks are part of the contract for issue #3.
export function ReadingTimeBadge({ minutes }: { minutes: number }) {
return <span>{minutes} min read</span>;
}
That small component is enough to verify that code fences render, stay legible, and expose a direct copy affordance for readers skimming implementation details.
Keep reading
Keep reading
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.
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.