<h2>Path routing over subdomains</h2><p>We intentionally kept the blog under `/blog` instead of creating a separate hostname for user-generated content. That preserves brand continuity and avoids making the editorial surface feel detached from the product.</p><p>The route architecture was already in place, so the real work became replacing the weak content layer and leveling up the reading experience.</p><h2>Operational notes</h2><ul><li>Use a single visual system so the transition from product to blog feels native.</li><li>Keep cache strategy simple while the editorial workflow is still evolving.</li><li>Design storage seams early so you can swap file-backed content for a managed backend later.</li></ul>

## Path routing over subdomains

We intentionally kept the blog under `/blog` instead of creating a separate hostname for user-generated content. That preserves brand continuity and avoids making the editorial surface feel detached from the product.

The route architecture was already in place, so the real work became replacing the weak content layer and leveling up the reading experience.

## Operational notes

- Use a single visual system so the transition from product to blog feels native.
- Keep cache strategy simple while the editorial workflow is still evolving.
- Design storage seams early so you can swap file-backed content for a managed backend later.

I appreciate the honesty around storage seams. So many examples skip the part where content actually needs to live somewhere durable.

#opennext

Stories tagged opennext

What we learned shipping Next.js on Cloudflare without splitting the product apart