Ivan VasilovandClaude Opus 4.7
c64f18d790
Each app's `tailwind.config.{js,ts,cjs}` was a thin wrapper that called
the shared `config/tailwind.config` function with a `content` array and
any app-specific `theme.extend`. The theme extensions were already
extracted into `apps/<app>/styles/tailwind.config.css` in prior commits,
so the remaining piece is the content paths — which move into the same
CSS file as `@source` directives.
Changes per app:
- Added `@source` directives to each `tailwind.config.css` matching the
content globs from the deleted JS config.
- Updated each app's main CSS entry's `@config` directive to point
directly at the shared `packages/config/tailwind.config.js`.
- Deleted `apps/<app>/tailwind.config.{js,ts,cjs}` (7 files).
`apps/lite-studio` gets its first `tailwind.config.css` (previously it
had no theme extensions to migrate). Lives at `app/tailwind.config.css`
next to `app.css`.
Shared config changes:
- `packages/config/tailwind.config.js` now `module.exports = uiConfig`
directly (a Tailwind config object) instead of the `wrapper` function.
Apps no longer call the wrapper from JS. Dropped the unused `wrapper`,
`arrayMergeFn`, `deepMerge`, and `plugin` imports/declarations.
- `apps/studio/types/config.d.ts` updated to declare the module as a
`Config` object instead of a wrapper function.
- `apps/ui-library/components.json` shadcn config: `tailwind.config` set
to empty string (CSS-first marker).
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.