— Documentation: Foundations & Next Steps On Content Strategy
The documentation looks dated, and the navigation is confusing. We’re long overdue for an overhaul, but we’ve been putting it off for years because it’s prohibitively time-consuming due to hardcoded links and serious SEO concerns. We need to fix this before moving forward.
We will use an off-the-shelf Next.js template—similar to the Next.js documentation itself—called AriaDocs for a drag-and-drop facelift with a modern suite of features developers have come to expect.
We will build a custom, automated system to handle routing, redirects, and internal linking. This system will be built around a build-time script that ensures all content URLs are permanent, all legacy paths are correctly redirected, and all internal links are unbreakable, all leveraging next.config.js.
Goal: All content will be served from clean, permanent, and SEO-friendly absolute URLs.
Mechanism: Every MDX file will define its public URL via a frontmatter property.
--
id: 'a2b4c6d8-e1f3-4a5b-9c8d-7e6f5a4b3c2d'
title: 'My Awesome Post'
seoPath: '/guides/my-awesome-post'
--
Content goes here...
The build script will use these seoPath values to generate rewrite rules in next.config.js, mapping the public URL to the underlying Next.js page structure.
Edge Cases: The build script will enforce the following rules: