Miranda Limonczenko
1c8d0bf862
The page was nine flat H2s, and the intro opened with a two-step procedure under no heading, before the CLI is installed. - Group local setup under Set up a local project, and updating and beta builds under Manage your CLI installation. Connect to a hosted project stays top level, since linking is a different goal from local setup. - Put the intro's `init` and `start` list under Quickstart. Every grouped section keeps its heading text, so the slugs are unchanged and the on-page contents nests instead of shrinking.
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.