Files
supabase/apps/docs
Cursor AgentandDanny White 0e81cfc939 merge origin/master into dnywh/feat/studio-replication-stepped-create
Phase A: bring the create-pipeline wizard integration branch onto current
master. Keep master's replication list/detail, v2 publications, and pipeline
action reliability; preserve the wizard create routes, isolated chrome, and
stepped UI. Point list Add pipeline at /new and migrate wizard publication
reads to v2 names/detail queries.

Co-authored-by: Danny White <dnywh@users.noreply.github.com>
2026-09-18 06:23:29 +00:00
..
2026-07-01 12:59:00 +02:00

Reference Docs

Supabase Reference Docs

Maintainers

If you are a maintainer of any tools in the Supabase ecosystem, you can use this site to provide documentation for the tools & libraries that you maintain.

DocSpec

We use documentation specifications which can be used to generate human-readable docs.

  • OpenAPI: for documenting API endpoints.
  • SDKSpec (custom to Supabase): for SDKs and client libraries.
  • ConfigSpec (custom to Supabase): for configuration options.
  • CLISpec (custom to Supabase): for CLI commands and usage.

The benefit of using custom specifications is that we can generate many other types from a strict schema (eg, HTML and manpages). It also means that we can switch to any documentation system we want. On this site we use Next.js, but on Supabase's official website, we use a custom React site and expose only a subset of the available API for each tool.

Contributing

To contribute to docs, see the developers' guide and contributing guide.