Skip to content

docs(js): [Experiment] Next.js and Nuxt as guides nested in their runtimes - #19976

Closed
JPeer264 wants to merge 4 commits into
masterfrom
jp/poc-b-runtime-frameworks
Closed

docs(js): [Experiment] Next.js and Nuxt as guides nested in their runtimes#19976
JPeer264 wants to merge 4 commits into
masterfrom
jp/poc-b-runtime-frameworks

Conversation

@JPeer264

@JPeer264 JPeer264 commented Oct 14, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

Warning

Experiment to compare options, not for merge.

DESCRIBE YOUR PR

This moves Next.js and Nuxt into the guides of the runtimes they run on: /guides/node/nextjs/ and /guides/cloudflare/nextjs/, and the same for Nuxt. The platform selector shows them under their runtime, for example "Next.js (Cloudflare)".

  • A folder inside a guide becomes a guide of its own with nestedGuide: true in its index.mdx. Its key stays javascript.nextjs, so includes and supported lists work as before.
  • The Cloudflare guides have their own quick start. With inheritPagesFrom: node/nextjs, they show all other pages of the Node.js guide.
  • The quick starts move into includes per framework, so the Node.js and Cloudflare quick starts share their content.
  • The old /guides/nextjs/ and /guides/nuxt/ URLs and the Cloudflare framework pages redirect to the new guides.

Known issues

  • The Cloudflare guides also show Node.js-only pages, for example the profiling and webpack setup pages.
  • The inherited pages have the same content and <title> in both runtimes.
  • No Bun or Deno guides, because the SDK repo has no tests for Next.js or Nuxt on them.
  • The other Cloudflare frameworks (Astro, SvelteKit and others) stay under Cloudflare → Frameworks.
  • Not tested with a production build, the .md exports or llms.txt.

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace YYYY-MM-DD with the due date. You can update this information later by editing the PR description.

  • Urgent deadline (GA date, etc.): YYYY-MM-DD
  • Other deadline: YYYY-MM-DD
  • No deadline: Not urgent, can wait up to 1 week+

SLA

  • Teamwork makes the dream work, so please add a reviewer to your PRs.
  • Please give the docs team up to 1 week to review your PR unless you've supplied a deadline.

Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

  • Checked Vercel preview for correctness, including links
  • PR was reviewed and approved by any necessary SMEs (subject matter experts)
  • PR was reviewed and approved by a member of the Sentry docs team

JPeer264 and others added 4 commits October 14, 2026 17:32
@JPeer264 @claude
docs(js): [POC B/C] Move runtime quick starts into per-framework incl…
efa32c5 
…udes

The Node.js and Cloudflare quick starts of Next.js and Nuxt now live in
getting-started-node and getting-started-cloudflare includes, keyed by
framework. Nested includes and links use explicit platforms, so the same
content renders correctly under the framework guide and under a runtime
guide. Next.js on Cloudflare is now a full quick start instead of a delta
to the Next.js guide.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@JPeer264 @claude
feat(docs): [POC B] Support guides nested in a runtime guide
3fd1a92 
A folder inside a guide is a guide of its own when its index.mdx sets
`nestedGuide: true`, for example guides/node/nextjs/. Its key uses the
folder name (javascript.nextjs), so includes and `supported` lists work
as for a top-level guide. A nested guide can set `inheritPagesFrom` to
render the pages of another guide for which it has no own file, for
example guides/cloudflare/nextjs/ inherits from node/nextjs.

The doc tree, page generation, MDX lookup, sidebar, PlatformContent,
page heading, platform selector, /platforms/ list and platform-redirect
know about nested guides. The selector shows them under their runtime.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@JPeer264 @claude
docs(js): [POC B] Move Next.js and Nuxt into their runtime guides
591b11e 
Next.js and Nuxt are now nested guides of Node.js
(/guides/node/nextjs/) and Cloudflare (/guides/cloudflare/nextjs/).
The Cloudflare guides have their own quick start and inherit all other
pages from the Node.js guides. The old /guides/nextjs/ and /guides/nuxt/
URLs and the Cloudflare framework pages redirect to the new guides.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@JPeer264 @claude
fix(scripts): [POC B] Accept nested guides in migration items
ce62ad4 
The migration item validator only knew the top-level guide folders, so it
rejected nextjs and nuxt after they moved into the Node.js guide.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Oct 14, 2026 •
edited
Loading

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
develop-docs Ready Ready Preview Oct 14, 2026 4:27pm UTC
sentry-docs Ready Ready Preview Oct 14, 2026 4:27pm UTC

Request Review

@github-actions github-actions Bot added the Priority: Normal Docs review has no urgent deadline label Oct 14, 2026
@codeowner-assignment
codeowner-assignment Bot requested review from a team October 14, 2026 16:22
This was referenced Oct 14, 2026
Closed
Draft
Closed
Draft
@JPeer264

JPeer264 commented Oct 21, 2026

Copy link
Copy Markdown
Member Author

Closing in favor of #19974 (server frameworks) and #19977 (Next.js and Nuxt).

@JPeer264 JPeer264 closed this Oct 21, 2026

This branch was successfully deployed

2 active deployments
Preview – sentry-docs — ce62ad42 Deployed Oct 14, 2026 by vercel[bot]
View deployment
Preview – develop-docs — ce62ad42 Deployed Oct 14, 2026 by vercel[bot]
View deployment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Priority: Normal Docs review has no urgent deadline

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@JPeer264