Asset locations
Committed public brand assets live underdocs/images/brand/.
| Asset | Use |
|---|---|
supaschema-logo-light.png | Mintlify logo for light mode. |
supaschema-logo-dark.png | Mintlify logo for dark mode. |
supaschema-logo-readme.png | GitHub README logo with a solid background for light and dark GitHub themes. |
supaschema-mark.png | Square 1:1 emblem for icon and favicon derivatives. |
favicon.png | Mintlify favicon. |
github-social-preview.png | Repository social preview uploaded in GitHub settings. |
mintlify-og-background.png | Mintlify social thumbnail background. |
Mintlify usage
Mintlify branding is configured indocs/docs.json.
Use root-relative paths for docs assets:
logo.lightpoints to/images/brand/supaschema-logo-light.png.logo.darkpoints to/images/brand/supaschema-logo-dark.png.faviconpoints to/images/brand/favicon.png.thumbnails.backgroundpoints to/images/brand/mintlify-og-background.png.
thumbnails.background for social previews. It keeps Mintlify’s generated page title and description overlays. Use a global seo.metatags["og:image"] only when every page should use the exact same static image.
Brand
GitHub usage
The root README usesdocs/images/brand/supaschema-logo-readme.png with a repo-relative path. GitHub rewrites relative image paths for the active branch, so keep README images repo-relative instead of using docs-root /images/** paths.
Upload docs/images/brand/github-social-preview.png manually in the repository’s Settings page under Social preview. GitHub does not automatically read that file from the repository.

Generated visuals
Generated benchmark and concept images stay in their existing directories:docs/images/benchmarks/**docs/images/concepts/**
benchmarks/plot-lib.js.
