Johanne Courtright joined the Jukebox podcast to describe how years of agency work pushed her to extend Gutenberg. After moving from Dreamweaver and static HTML into WordPress in 2011, her agency projects relied on custom post types, ACF, API integrations and precise layouts. When Gutenberg arrived she learned React, adopted the Interactivity API and reduced jQuery dependency so she could build block-driven, production-ready sites without the bloat of third-party builders.
Agency needs versus Core philosophy
Agencies typically need fine-grained, predictable control: consistent breakpoints, responsive padding and type scale, branded color systems and client-friendly editing experiences. Core WordPress intentionally targets the 80/20 problem—cover common workflows without becoming opinionated for every use case. Johanne’s view is that Core is a great foundation, but agencies regularly require extras Core doesn’t provide. Instead of opposing non-Gutenberg solutions, she extended Core’s approach with lightweight themes, minimal CSS/JS and plugins that layer in agency-level controls.
Groundworx: design principles and scope
Groundworx (groundworx.dev) is Johanne’s collection of enhancements and blocks designed to sit comfortably with Gutenberg’s architecture. The project splits into two areas: extensions that enhance existing Core blocks and a set of purpose-built blocks for recurring agency patterns. The goal is augmentation rather than replacement—provide the extra levers agencies need while avoiding conflicts with Core’s evolution.
Key improvements included
– Responsive controls with multiple breakpoints for headings, paragraphs and list styles.
– Column counts and breakpoint-aware grids and lists so layout adapts predictably.
– Group-level options like full-height sticky behavior and reversed stacking to change order across viewports.
– Performance-first video handling and responsive media configurations.
– theme.json patterns and presets that favor swapping values over structural changes, making theme switches less disruptive.
Custom blocks and repeatable patterns
Johanne built components that match common agency requirements: accordions that transform into tabs at a chosen breakpoint, media-content split blocks, card and card-reveal blocks, and a navigation block suite. They emphasize semantic output, CSS-grid-friendly markup and performance, so sites remain accessible and easy to style without excessive wrappers.
Rethinking navigation
Groundworx’s navigation system stores reusable menu structures in a custom post type, echoing Core’s reusable block idea but adding agency-focused options. The objective is one HTML source that adapts across desktop, mobile and vertical layouts without duplicating menus. The navigation leverages the Interactivity API and supports full-height side menus, breakpoint-driven layout shifts, submenus that become accordions on small screens and branded regions—allowing consistent, flexible navigation patterns across projects.
Theme strategy and portability
Johanne prefers to keep themes narrowly focused on typography, color keys and brand tokens so functionality does not live in theme templates. Her theme.json-driven strategy uses clear keys and labels to make theme swaps a matter of changing values instead of reworking structure. She would like theme.json to better support custom variables or additional named palettes (for example, more explicit navigation color keys) so designers can avoid injecting manual CSS variables.
Adoption challenges and mindset
Moving a team from classic theming or page builders to a block-first workflow is a cultural and technical shift. The editor’s architecture, tooling and ways of thinking about layout differ significantly, and some developers find the learning curve steep. Utility CSS frameworks like Tailwind can also clash with WordPress expectations. However, teams that invest the time to reverse-engineer Gutenberg often appreciate the lower markup bloat, improved flexibility and better client editing experiences.
Core, plugins and deciding scope
Johanne accepts that not every feature belongs in Core. Many Groundworx features are deliberately targeted at the agency 20% that need fine controls. She’s mindful of the GPL ecosystem and the chance that well-adopted ideas may eventually influence Core. Her priority was shipping practical solutions instead of waiting for Core adoption.
Discovery, directories and ecosystem needs
A persistent problem Johanne highlighted is discovery: the official plugin and theme directories need better search, clearer metadata (for example, whether a plugin is native block-first or still relies on jQuery) and curated listings. Better discovery and metadata would help users and agencies find compatible, well-made block tools and help block-based businesses grow.
Business and community perspective
Groundworx offers both free and commercial options. Johanne builds primarily to solve her own agency needs, but releases work for others when it’s broadly useful. She doesn’t expect overnight commercial success; she sees the block product space as maturing and believes better ecosystem tooling and discovery will enable more sustainable businesses.
Where to find Johanne and Groundworx
See Groundworx at groundworx.dev. Johanne is active on X and engages with the WordPress community there; she welcomes feedback and collaboration as the block editor, theme.json and Core continue to evolve.
Bottom line
Johanne’s work demonstrates a pragmatic path for agencies adopting Gutenberg: keep themes light, build flexible blocks and responsive controls, and prioritize semantics and performance. Groundworx shows how targeted extensions can close practical gaps while remaining compatible with Core’s long-term direction, making block-based, agency-grade sites faster to build and easier for clients to manage.