15eb27fb19
* docs: improve Facebook OAuth guide with troubleshooting and clearer instructions - Add explicit callback URI pattern with link to dashboard - Add dedicated "Configure email permissions" section with caution admonition - Add "Testing your integration" section explaining development mode - Add "Going live with App Review" section with step-by-step guide - Add "Troubleshooting" section for common issues - Add error handling to JavaScript code examples - Fix Swift example with complete ASWebAuthenticationSession implementation - Add note about checking pub.dev for latest Flutter package version Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * Apply suggestions from code review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * docs: improve Facebook OAuth guide with troubleshooting and clearer instructions - Add explicit callback URI pattern with link to dashboard - Add dedicated "Configure email permissions" section with caution admonition - Add "Testing your integration" section explaining development mode - Add "Going live with App Review" section with step-by-step guide - Add "Troubleshooting" section for common issues - Add error handling to JavaScript code examples - Update Swift example to use webAuthenticationSession environment - Add note about checking pub.dev for latest Flutter package version Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * style: run format * Apply suggestions from code review Co-authored-by: Chris Chinchilla <chris.ward@supabase.io> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Chris Chinchilla <chris.ward@supabase.io>
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.
Versioning
All tools have versioned docs, which are kept in separate folders. For example, the CLI has the following folders and files:
cli: the "next" release.cli_spec: contains the DocSpec for the "next" release (see below).cli_versioned_docs: a version of the documentation for every release (including the most current version).cli_versioned_sidebars: a version of the sidebar for every release (including the most current version).
When you release a new version of a tool, you should also release a new version of the docs. You can do this via the command line. For example, if you just released the CLI version 1.0.1:
npm run cli:version 1.0.1
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 developers' guide and contributing guide.