Miranda Limonczenko
a91ef3fe10
Moves only. No claim changes and no reworded prose beyond the connective text the new shape needs. Groups the four procedures under one heading, promotes the Edge Functions comparison ahead of them, and folds Deep dive into Resources. Eight top-level headings become five. Debugging moves to its own page. It carried three subsections and shared only the word "function" with the rest of the guide. Every inbound anchor is repointed and the page is registered in the Database sidebar. Heading text that other pages link to is unchanged: Quick demo, Security definer vs invoker, and General logging.
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.