Files
supabase/apps/docs
Miranda Limonczenko 67bc1c64c9 docs(database): show the setup SQL by default in Returning data sets
The tab group defaulted to Data, so a reader going top to bottom never saw
the create table statements and hit 'type planets does not exist' at the next
snippet. The Data tab is an illustration. The SQL tab is the part you run.

Adjusts the lead-in sentence so it still introduces both tabs.
2026-09-30 14:36:22 -07:00
..
2026-07-01 12:59:00 +02:00
2026-09-30 18:34:09 +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 style guide for how to write a page, and the developers' guide and contributing guide for repo mechanics. If you write with an AI coding agent, use the /write-the-docs skill to draft and /edit-the-docs to revise an existing page.