mirror of
https://github.com/supabase/supabase.git
synced 2026-10-15 06:09:08 +03:00
Alaister Young
358be92043
Follow-up to the font fix: drop the Google Fonts <link> and self-host all three families via @font-face in fonts.css, matching next/font (which self-hosts them on the Next build). Keeps self-hosted / offline studio working — no runtime CDN dependency. - Inter + Source Code Pro reuse the woff2 fonts/index.ts already ships. - Manrope: vendored latin + latin-ext subset variable woff2 (fonts/manrope/, from @fontsource-variable/manrope) with the standard Google unicode-ranges; no italic axis. Weight ranges mirror fonts/index.ts. - __root.tsx: remove the googleapis/gstatic preconnects + stylesheet link. Verified in a browser against the built bundle: Inter (body), Manrope (headings) and Source Code Pro (mono) all load from local /assets/*.woff2, and no fonts.googleapis/gstatic references remain in the client output.
Styles
When to write custom styles
Tailwind should be sufficient to cover the majority of styling needs. We typically only write custom styles here in the event where we're working with an external library and we need to override some styles (e.g Monaco, or even our own UI library).
Ideally, keep custom styling here to a minimum, use tailwind directly in the pages and components where possible, so that we have less code to maintain.
If you're writing custom styles
Group custom styles into separate stylesheets based on their context. For styles which are generic and global, we can write them in main.scss.