The idea is to add an automatic theme.json interoperability layer for X, Pro, and Cornerstone.
When we configure global colors, fonts, typography, spacing, and other design tokens in Cornerstone, using the various managers, Cornerstone could automatically generate a compatible theme.json representation. This would allow WordPress core, block-based tools, and third-party plugins to use the same design system, even while X and Pro aren’t block themes.
The generated file could include:
- Global color palettes (Color Manager)
- Global fonts and settings (Font Manager)
- Any variable from the Variable Manager
Standard values could be mapped to the appropriate theme.json sections, while general variables from the Variable Manager could be exported through settings.custom.
Cornerstone should remain the source of truth, with theme.json generated automatically rather than edited independently. The feature could include an optional settings panel allowing users to enable or disable synchronization and choose which variable groups are exported.
This would be a significant improvement because it would:
- Make Cornerstone’s global design system available outside of Cornerstone.
- Improve compatibility with WordPress blocks and third-party plugins.
- Allow WooCommerce (and any other plugin) blocks, block patterns, and widgets to use the same site-wide colors and typography.
- Reduce duplicated design settings across different tools.
- Make custom CSS and development workflows more consistent through standardized variables.
- Help agencies maintain a reusable design system across projects.
- Improve migration and handoff by making global design tokens easier to inspect and reuse.
- Give Variable Manager values a broader purpose beyond Cornerstone-specific output.
- Future-proof Cornerstone sites as WordPress continues moving toward shared design tokens and block-based tooling.
This would not require X or Pro to become block themes. The theme.json file could function as an interoperability and design-token layer, allowing Cornerstone to remain the primary builder while making its global settings accessible to the wider WordPress ecosystem.