Miranda Limonczenko
7df1b930fc
Group the page's seven flat sections into three, so the top level fits the 5 +/- 1 chunking limit and the action path runs uninterrupted. - Open with a concept group, Choose an auth mode, holding the mode table - Gather the six patterns under Secure your function - Keep Environment variables last as the fact group - Add an intro outline linking the three groups, and a group introduction - Move the Authorization headers link below the mode table, so the table's introduction sits next to the table Every heading text is unchanged, so every slug is preserved and the in-page link to External webhooks still resolves.
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.