mirror of
https://github.com/supabase/supabase.git
synced 2026-10-06 09:55:06 +03:00
Danny White
6246f7359f
## What kind of change does this PR introduce? Bug fix ## What is the current behavior? The docs header wordmark renders the Supabase SVG and the "DOCS" suffix flush against each other with no gap. `HeaderLogo` used `buttonVariants`, which applies `space-x-2` for spacing, but the logo images use `m-0!` which cancels that margin-based spacing. The `buttonVariants` call also pulled in button styles that were immediately overridden (`bg-transparent!`, `border-none!`, `shadow-none!`). ## What is the new behavior? `HeaderLogo` is a plain flex link with explicit `gap-1.5`, giving reliable spacing between the wordmark and "DOCS" without the dead `space-x-2` or button style overrides. | Before | After | | --- | --- | | <img width="368" height="126" alt="CleanShot 2026-07-01 at 18 54 20@2x" src="https://github.com/user-attachments/assets/29186264-6fa7-44b1-bf37-7757ff35d740" /> | <img width="370" height="160" alt="CleanShot 2026-07-01 at 18 53 00@2x" src="https://github.com/user-attachments/assets/888e5973-c0ce-480c-acf0-520b26cfa007" /> | <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Style** * Updated the top navigation logo link styling, slightly adjusting spacing and simplifying its appearance. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
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.