New reference libraries, roles guide refresh, Next.js 16 migration and more platform updates

This month we’ve introduced a bunch of behind-the-scenes improvements to the documentation platform, surfaced more reference docs, and improved the Roles guide.

We’ve added more libraries to our typescript reference docs. You’ll now see @sanity/blueprints, next-sanity, and more libraries soon.

The roles and permissions API guide now uses the Access API instead of the older Roles APIs. You can still use the previous approach, but for new code we suggest the Access API.

We’ve migrated the entire Sanity docs site to Next 16, which unlocked a wide range of improvements including dramatically faster loads, better performance, improved UX, and reduced client-side errors. This refactor also lays the groundwork for upcoming cacheComponent support via next-sanity, ensuring Sanity docs continues to use the latest features and capabilities of our platform.

Are you a part of our Discord community? If so, you may have seen the #releases channel change from an RSS feed to our new releases bot. It’s built with Sanity Functions and should provide a better experience if you follow our updates through Discord. Perhaps you’re reading this there right now.

The Sanity docs now detect and respond to HTTP Accept headers with appropriate content and a matching Content-Type header. Most documentation pages support Accept: text/markdown, while our HTTP API Reference pages support Markdown, YAML, and JSON requests.

This feature ensures that Sanity docs properly handle incoming agentic AI / LLM requests and respond with the most performative content.

We’ve added broad categories to our changelog section and improved the sidebar filtering UI/UX. You can now explore changes by high-level category , or drill down into specific subsets of products.

Easily navigate between categories or related changelog entries with the new header breadcrumb, inline filtering, and “previous/next changelog” buttons.