Maisie is an experiment based on years of creating client themes requiring visual design unsupported by the WordPress block editor.

Production readiness

The next major release of WordPress is the constant target, however unlikely. Which release will this actually be? Impossible to say, and the approach Maisie takes may never be suitable for a serious website.

Design collaboration

I’m not a designer and have no design process to speak of. A constant decision-making battle between coder- and visual-presentation brains tends to drain a little energy from the project. Maisie can benefit greatly from someone with typographical and general design expertise lending an eye.

Reduce theme CSS

The long-term aim is to no longer require custom styles at all to achieve Maisie‘s goals. A promising sign is ~20% of the theme’s CSS has already been dropped since theme development began, made possible due to increased sensitivity around real-world layout requirements by the Gutenberg project.

Remove custom “burger”

The Navigation block solution for exposing a menu on narrower screens suffered from critical bugs for the duration of Maisie‘s development. As a work-around to allow development to continue, an alternate approach has been implemented. This will be reviewed when development churn around the Navigation block begins to settle down.

Remove custom layout

The editor does not include support for CSS Grid-based layouts—yet. Maisie explores a bare-bones approach for this, integrated with the editor’s layout tools.

WooCommerce support

Maisie doesn’t currently provide native support for WooCommerce for a couple of reasons: to prevent bloating the theme for anyone who doesn’t need an e-commerce solution as part of their website, and because WooCommerce support for the modern editor is not great right now. If support for WooCommerce happens it will be via a stand-alone plugin.

Maisie was built for Gutenberg up until the Site editor was released in WordPress 5.9.

Open tickets


Key conversations

Learn about Maisie