Files
supabase/apps/studio/styles
Alaister Young 3d698fb0d8 chore(studio): port <Head> + favicons + fonts to TanStack root route
- Move every static meta/link from pages/_app.tsx's <Head> and
  MetaFaviconsPagesRouter into the root route's head() so TanStack
  Start emits them via HeadContent. Covers viewport, og:image,
  googlebot, msapplication-*, theme-color, 8 apple-touch-icon-
  precomposed, 7 PNG favicons, shortcut icon, manifest, and the
  IS_PLATFORM API preconnect.
- Drop next/font from the compat path: styles/fonts.css declares the
  local CustomFont via @font-face and sets --font-custom /
  --font-source-code-pro. Source Code Pro loads from Google Fonts via
  a <link> in head(). pages/_app.tsx keeps its next/font setup for
  the Next build.
- Add a small DynamicTitle effect so useCustomContent('app:title')
  can override the default "Supabase" title at runtime, mirroring
  <title>{appTitle ?? 'Supabase'}</title> in _app.tsx.
2026-04-21 16:23:37 +08:00
..

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.