Community Feedback Goes Live on the Next.js 13 Docs
Documentation improves when feedback is easy to give and easy to act on. That was the thinking behind enabling Vercel’s commenting feature (beta) on the public Next.js 13 documentation, not just on internal previews. So far, 2,286 participants have started 509 discussion threads, with 347 issues resolved. The docs are live at beta.nextjs.org/docs for anyone who wants to contribute.
Adding Context to Every Comment
Previously, feedback on the Next.js docs funneled in from Twitter, Slack, GitHub, Discord, and other channels. While the volume was useful, those channels lack one crucial thing: context. A comment attached directly to a Preview Deployment is pinned to the exact DOM element, which means reviewers don't need to screenshot, annotate, or describe where a problem is located—the "where" is built into the comment itself.
“The commenting product was originally designed for private usage, so I was a little hesitant to add it to a public, high-visibility site with 'everybody with the public link can comment' permissions. But my worries were misplaced. The gift of community feedback is incredible.”
Malte Ubl - Vercel CTO
More Feedback, Not More Overwhelm
Lowering the barrier to entry paid off: over 2,000 reviewers have left comments so far. Beyond the raw numbers, the community also answered each other's questions in the threads, which eased the load on the Next.js team. Centralizing feedback in one place helped the team keep pace with the higher volume without losing track of individual issues.
With a comment attached to a Preview Deployment, proper context is the default. A reviewer doesn't have to switch tools or add extra detail; the comment itself carries the necessary information about UI, copy, or interaction.
Closing the Loop with Reviewers
The feedback loop doesn't stop when a comment is posted. Reviewers get email notifications when their comments are resolved, confirming that their input was seen and addressed. When a new deployment is pushed to the same git branch, Preview Deployments notify reviewers so they can refresh and see the latest changes. That clear back-and-forth keeps community members engaged and informed.
Iterating Faster with Precise Targets
Because comments anchor directly to the DOM element, the Next.js team knows exactly what needs attention. That precision helped the team address related issues in larger batches, leading to more efficient iteration cycles. With more information and clearer targets, acting on feedback required less time hunting for the problem and more time fixing it.
Bringing the Workflow to Your Own Previews
The commenting feature is available to everyone. To enable it on your own Vercel Preview Deployments, opt into the comments public beta, open a preview branch, and feedback can start flowing. For new projects, use a template or sign up for a free Vercel account to get started.
