Skip to content

docs(skill): declare the design tokens in @theme, not in theme.json #1

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
ogorzalka merged 1 commit into from
Sep 28, 2026
Merged

docs(skill): declare the design tokens in @theme, not in theme.json #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 3 additions & 2 deletions resources/boost/skills/pollora-theming/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ themes/my-theme/
│ └── index.blade.php
├── functions.php # Theme registration entry point
├── style.css # WordPress theme metadata (name, version, description)
├── theme.json # Block editor / Full Site Editing config
├── theme.json # Base block editor config; the build adds the @theme tokens
├── vite.config.js # Vite build configuration
├── tailwind.config.js # Tailwind (v3) or not needed (v4 auto-detection)
└── package.json
Expand Down Expand Up @@ -182,7 +182,8 @@ return [

- **Never create WordPress PHP template files** — use Blade exclusively
- Theme providers in `app/Providers/` are auto-discovered
- The `theme.json` file controls block editor settings (colors, fonts, spacing)
- Design tokens (colours, font sizes, fonts, radii) go in the `@theme static` block of `app.css`, with concrete values; `wordpressThemeJson` writes them into the built `theme.json` the editor reads. Never `@import "tailwindcss" theme(static)` (it puts Tailwind's whole palette in the editor), never `var(--wp--preset--…)` inside `@theme` (a cycle once copied)
- The root `theme.json` is the base: layout, spacing, `fontFace`, editor settings. A slug defined there wins over `@theme`; a whole family can be taken out of the generation with `disableTailwindColors` / `disableTailwindFontSizes` / `disableTailwindFonts` / `disableTailwindBorderRadius`
- Tailwind CSS v4 is auto-detected — no configuration file needed
- Build output goes to `public/build/theme/{theme-name}/`
- Use `Asset` facade in service providers, not in hookable classes
Loading