Welcome to the next-slug-splitter demo. This is a light page — it contains
only standard Markdown elements and no custom React components.
Why does this matter?
In a typical Next.js content site, every page that shares a dynamic route
(e.g. [...slug].tsx) bundles the same JavaScript — including heavy components
that only a few pages actually use.
next-slug-splitter solves this by:
Scanning your MDX content at build time
Detecting which pages use custom React components
Generating dedicated route handlers for those "heavy" pages
Keeping the shared catch-all route lean for "light" pages like this one