Files
supabase/apps/learn
Ivan VasilovandClaude Opus 4.7 9b985e3876 chore(config): add shared tailwind.config.css outer shell
Introduces `packages/config/tailwind.config.css` as the CSS-first
orchestration layer shared by every app. It collects three things that
were previously duplicated across every app's main CSS entry:

- `@import` of `packages/ui/build/css/source/global.css` — the design
  system's CSS variable definitions.
- `@import` of `dark.css`, `light.css`, and `classic-dark.css` — per-mode
  overrides for those variables.
- `@import` of `packages/config/tailwind-utilities/hit-area.css` — the
  v4-native `hit-area-*` utility port.

And one new thing:

- `@custom-variant dark` matching v3's
  `darkMode: ['class', '[data-theme*='dark']']` — active on `.dark` or
  `[data-theme*='dark']`, on the element itself or any ancestor, with
  zero-specificity via `:where()`.

Every app's main CSS entry now reads:

  @import 'tailwindcss';
  @import '.../packages/config/tailwind.config.css';
  @import './tailwind.config.css';
  @config '.../packages/config/tailwind.config.js';

The four duplicated imports (global + three themes + hit-area) disappear
from each app's entry file. The `@config` bridge stays for now; the
declarative theme still lives in the JS config. The next commit will
merge `tailwind.config.js` and `ui.config.js` into a single JS plugin
loaded by this CSS file, at which point the `@config` line goes away.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-04 14:35:20 +02:00
..
2026-02-04 21:36:24 -03:30
2026-02-04 21:36:24 -03:30
2026-02-04 21:36:24 -03:30
2026-02-04 21:36:24 -03:30
2026-02-04 21:36:24 -03:30
2026-02-04 21:36:24 -03:30
2026-02-04 21:36:24 -03:30
2026-02-04 21:36:24 -03:30
2026-02-04 21:36:24 -03:30
2026-02-04 21:36:24 -03:30

Plan: Course 1: Supabase Foundations Learn the basics of Supabase: database, auth, and RLS. 5 chapters.

Course 2: Project: Smart Office 15 Build a realtime room-booking dashboard using Supabase. 15 chapters. Course 3: Supabase Internals: Performance & Scaling. Learn how to profile queries, tune indexes, and scale Postgres with Supabase. 20 chapters. Course 4: Supabase Internals: Debugging & Operations. Understand how to diagnose slow queries, use read replicas, and manage production workloads. 20 chapters.

——— This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Inter, a custom Google Font.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.

Supabase types

To regenerate the Supabase database types, run

supabase gen types --local > registry/default/fixtures/database.types.ts