Repository navigation
Global Styles and Design Tokens
Shared systems are optional. A request for a website, a conversion or a more efficient layout does not automatically authorize creating shared styles or tokens.
The assistant should ask once, unless you already chose:
Would you like shared Global Styles, Design Tokens, or both for reuse across pages? Otherwise I'll keep this layout's styling local.
| Choice | Intended result |
|---|---|
| Local styling | New styling belongs to the individual blocks |
| Global Styles | Reusable style rules are intentionally shared across components/pages |
| Design Tokens | Reusable values are intentionally managed as tokens |
| Both | Shared values and reusable component styles form a coordinated system |
Consent to one is not consent to the other. Existing theme inheritance and shared references are preserved during targeted edits. The assistant can inspect them without introducing new dependencies.
The tested Pro 2.8.0-beta.1 workflow includes Design Tokens, Style Book guidance, expanded selectors and portable design-system imports. Tokens are not merely arbitrary CSS variables: registered tokens also carry editor metadata. Preserve existing variables where appropriate without assuming they are registered portable tokens.
After you opt in:
- Inventory existing theme variables, Global Styles and registered tokens.
- Choose names and the system's owner before adding another competing layer.
- Start with values and components that actually repeat.
- Keep one-off adjustments local to their block.
- Test an import on a disposable destination before applying it to an established system.
- Read back shared records and check more than one affected page after changes.
The tested design-system import is missing-only. Importing a differently colored system over existing names does not necessarily rebrand the destination; existing values can be preserved. Same names can also carry different meanings across sites.
Do not overwrite destination styles to resolve a collision without reviewing what uses them. A variable defined only in an external stylesheet is not automatically a portable registered token.
The optional example kit demonstrates two presets, six sections, native queries, an accordion and a form on disposable local sites. It deliberately introduces shared styles and tokens and requires explicit opt-in to both.
Its setup scripts, test mail sink and minimal theme are local test infrastructure. They are not a production deployment recipe or a default dependency for generated pages. The raw exports contain source-site IDs and URLs; use the documented remapping workflow.
For storage fields, checksummed saves and the native import contract, read the beta guide. For the normal decision boundary, read styling scope.
Wiki home · Repository · Latest release · Report an issue
The wiki covers GenerateBlocks Skills; plugin features depend on the installed GenerateBlocks/Pro version. Detailed authoring rules are maintained in the repository's skill files.
GenerateBlocks Skills
Start
Build
- Styling and Responsive Design
- Global Styles and Design Tokens
- Conversion Workflows
- Dynamic Content
- Interactive Blocks and Forms
- Building a Website
- WordPress Editing and Publishing
Reference and Help