Skip to content

Document @theme static #2067

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 25, 2025
Merged

Document @theme static #2067

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
676e29a
document `@theme static`
RobinMalfait Feb 6, 2025
de1f2b1
Update src/docs/theme.mdx
RobinMalfait Feb 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions src/docs/theme.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -499,6 +499,21 @@ For example, this text will fall back to `sans-serif` instead of using `Inter` l

This happens because `var(--font-sans)` is resolved where `--font-sans` is defined _(on `#parent`)_, and `--font-inter` has no value there since it's not defined until deeper in the tree _(on `#child`)_.

### Generating all CSS variables

By default only used CSS variables will be generated in the final CSS output. If you want to always generate all CSS variables, you can use the `static` theme option:

```css
/* [!code filename:app.css] */
/* [!code word:static] */
@import "tailwindcss";

@theme static {
--color-primary: var(--color-red-500);
--color-secondary: var(--color-blue-500);
}
```

### Sharing across projects

Since theme variables are defined in CSS, sharing them across projects is just a matter of throwing them into their own CSS file that you can import in each project:
Expand Down