Ivan VasilovandClaude Opus 4.7
9b985e3876
Introduces `packages/config/tailwind.config.css` as the CSS-first orchestration layer shared by every app. It collects three things that were previously duplicated across every app's main CSS entry: - `@import` of `packages/ui/build/css/source/global.css` — the design system's CSS variable definitions. - `@import` of `dark.css`, `light.css`, and `classic-dark.css` — per-mode overrides for those variables. - `@import` of `packages/config/tailwind-utilities/hit-area.css` — the v4-native `hit-area-*` utility port. And one new thing: - `@custom-variant dark` matching v3's `darkMode: ['class', '[data-theme*='dark']']` — active on `.dark` or `[data-theme*='dark']`, on the element itself or any ancestor, with zero-specificity via `:where()`. Every app's main CSS entry now reads: @import 'tailwindcss'; @import '.../packages/config/tailwind.config.css'; @import './tailwind.config.css'; @config '.../packages/config/tailwind.config.js'; The four duplicated imports (global + three themes + hit-area) disappear from each app's entry file. The `@config` bridge stays for now; the declarative theme still lives in the JS config. The next commit will merge `tailwind.config.js` and `ui.config.js` into a single JS plugin loaded by this CSS file, at which point the `@config` line goes away. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.