Stop letting WordPress break your design system, Dmitry Mayorov | EvolveDigital Toronto 2026
Summary
Dmitry Mayorov, a Front-End Engineer at Fueled (formerly TenUp), presented a comprehensive approach to making WordPress work within enterprise design systems without compromising brand consistency. Speaking at EvolveDigital Toronto 2026, Mayorov addressed the fundamental tension between WordPress's built-in flexibility and the need for strict design system adherence in enterprise environments. Drawing from Fueled's work with high-profile clients including the Biden administration, TechCrunch, Starbucks, Hilton, and Blackstone, he demonstrated practical solutions for constraining WordPress's extensive customization options.
The presentation was structured in two parts: first explaining design system principles as token architecture and component libraries that ensure consistency across platforms, and second showing how WordPress can be configured to support these principles. Mayorov emphasized that WordPress's flexibility is a feature, not a flaw, noting the platform's evolution from blog to comprehensive CMS and e-commerce solution. However, he argued that this flexibility must be controlled when working with enterprise brands that have strict guidelines.
The speaker demonstrated four key tools for achieving design system compliance: theme.json as a style dictionary replacement, custom blocks as React component alternatives, block styles as theme providers, and patterns for pre-built layouts. Through live demonstrations, he showed the contrast between default WordPress button customization (allowing unlimited color, size, and spacing changes) versus a controlled custom button block with only approved variations (fill/outline styles and predefined sizes).
Mayorov acknowledged challenges with WordPress's CSS architecture, comparing it to 'injecting CSS with a syringe into different places of a bubble,' and expressed wishes for better foundational defaults and vertical rhythm handling. He recommended starting with official WordPress documentation on theme.json and emphasized the importance of maintaining core block markup when possible, only creating custom blocks when structural changes are necessary.
The session concluded with practical advice on managing WordPress updates and maintaining design system integrity over time.
Key Takeaways
- •WordPress flexibility can be controlled through theme.json settings to disable dangerous customization features like gradients and arbitrary spacing
- •theme.json's custom settings function as a style dictionary, converting JSON tokens into CSS custom properties for consistent theming
- •Custom blocks should replace core blocks when structural markup changes are needed, but core blocks can be constrained when markup is acceptable
- •Block styles can act as theme providers, applying coordinated token changes across multiple components simultaneously
- •Patterns enable editors to quickly deploy pre-built, design-system-compliant layouts without recreating complex structures
- •WordPress's CSS architecture requires careful management due to styles being injected in multiple locations rather than following inverted triangle methodology
- •Enterprise clients with strong brand guidelines require WordPress implementations that prevent editors from breaking design consistency
- •Custom blocks are safer for long-term maintenance than heavily modified core blocks, as they won't break with WordPress updates
- •The visual parity between editor and front-end experiences eliminates mental overhead for content creators
- •WordPress multisite can leverage shared themes to deploy design systems across multiple properties
- •Documentation and schema availability make theme.json configuration accessible through AI tools like ChatGPT
- •When core block markup is sufficient, constraining options is preferable to building custom alternatives
Transcript
We are ready for let's call it the official beginning of the WordPress track now. Um so next up we have Dimmitri. He's from uh ABC Fuel. Um, and he's going to be talking about one of my favorite subjects and how WordPress is kind of becoming, you know, having its own like built-in design system. You can really integrate for uh into components and building your own components and editing controls and lots of things. Uh, actually if anyone was here last year, him and I did a similarly inspired tal...
