mirror of
https://github.com/supabase/supabase.git
synced 2026-10-08 02:45:07 +03:00
Claude
5474577292
- Lift PromptPanel from apps/docs into packages/ui-patterns so Studio and Docs share one component; update both docs importers and drop the old file (no shim) - Rebuild the Workers empty state as a 3/5 hero + 2/5 PromptPanel grid; render CLI / config.toml / cURL tabs through CodeBlock for language-correct highlighting - Rename the product back to "Workers" (PRODUCT_NAME / CLI_NAME) and fix the hardcoded "Compute" copy on the index page; correct the skill region to us-west-2 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XQ5b58nwfCGsifA7PCheQb
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 developers' guide and contributing guide.