Miranda Limonczenko
8cc89fb9c1
The page's subtitle promises deploying to the Supabase Platform, but the body stopped at `supabase stop` and never mentioned signing in, linking, or project refs. A reader who finished `supabase start` had no signal that their setup was local-only. - Add a section after Stop local services that names the gap and links to the page that owns the procedure. - Say at `supabase init` that it creates local files only. - Extend the opening value statement and the intro navigation to cover the goal this adds. No commands here. Local development workflow owns signing in and linking, so this page points at it rather than carrying a second copy.
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.