---
title: "New Supabase Docs, built with Next.js"
description: "Supabase released a new version of its documentation, rebuilding the site with Next.js after outgrowing Docusaurus. The earlier setup became harder to maintain as client-library versioning expanded, contributions grew more difficult, and the docs remained separate from Supabase’s Next.js and Turborepo monorepo. To reduce migration risk, the team first created a one-week Next.js MVP that copied Docusaurus, then spent a month developing the new release with two full-time developers. It introduces a new design, a single sidebar for broader discoverability, and reference pages that group all functions in a library while improving TypeDoc-based generation. Future work described includes unified authentication, project-specific documentation, runnable Postgres WASM examples, interactive tutorials, improved Postgres full-text search, and balancing sparse and overly verbose content."
---

# New Supabase Docs, built with Next.js

[Supabase](https://yomu.fyi/company/supabase) · jonny · Dec 12, 2022

**Type:** Announcement

## Summary

Supabase released a new version of its documentation, rebuilding the site with Next.js after outgrowing Docusaurus. The earlier setup became harder to maintain as client-library versioning expanded, contributions grew more difficult, and the docs remained separate from Supabase’s Next.js and Turborepo monorepo. To reduce migration risk, the team first created a one-week Next.js MVP that copied Docusaurus, then spent a month developing the new release with two full-time developers. It introduces a new design, a single sidebar for broader discoverability, and reference pages that group all functions in a library while improving TypeDoc-based generation. Future work described includes unified authentication, project-specific documentation, runnable Postgres WASM examples, interactive tutorials, improved Postgres full-text search, and balancing sparse and overly verbose content.

## Context

Supabase’s documentation had become difficult to maintain as its client libraries gained versioning. Contributors and team members had trouble fixing and writing documentation, and the Docusaurus-based site was the only project outside the company’s shared Next.js and Turborepo setup.

## Approach / What changed

The team migrated the docs to Next.js by first building a one-week MVP that copied Docusaurus rather than adding new product features during migration. After switching to that MVP, two developers spent a month adding a new design, unified sidebar navigation, consolidated reference pages, and improved TypeDoc-based generation.

## Takeaways

- The initial Next.js migration succeeded by treating it as an MVP and reproducing the existing Docusaurus experience instead of attempting a broader redesign.
- The new reference layout places all functions from a library on one page, allowing discovery through the site search or the browser’s find command.
- Planned additions include unified authentication, project-specific URLs and keys in documentation, runnable Postgres WASM examples, interactive tutorials, and Postgres full-text search.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [Developer Experience](https://yomu.fyi/topic/developer-experience), [Migrations](https://yomu.fyi/topic/migration)

- Source: [Supabase](https://supabase.com/blog/new-supabase-docs-built-with-nextjs)
- Source URL: https://supabase.com/blog/new-supabase-docs-built-with-nextjs
- Ingested by Yomu: 2026-08-29T01:15:21.467Z

[Read original post](https://supabase.com/blog/new-supabase-docs-built-with-nextjs)
