Promise
Blocks and block themes your editors actually want to use.
Who this is for
- Your team files a ticket every time they need a new page layout
- You’re on a page builder and page loads and licensing costs are both climbing
- You’re still on the classic editor and putting off the migration
- Your content team has design freedom they shouldn’t have, and every page looks different
What you get
- Custom blocks built on the native Gutenberg API, no page builder dependency
- A block theme with your design system encoded in theme.json, so brand rules are enforced by the editor instead of by review
- Block patterns for your common layouts, so publishing is assembly rather than construction
- Migration from classic editor, ACF layouts, or a page builder, with content preserved
- Written documentation and a recorded walkthrough for your editors
How it works
- Editorial audit (1 week). I sit with your content team and find out what they’re actually fighting. The blocks you need are rarely the blocks you’d have specced.
- Design system into theme.json (1–2 weeks). Palette, typography, spacing. This is what makes every later block cheap to build.
- Block development (2–6 weeks, scope-dependent). Built, tested with Jest and PHPUnit, code-reviewed.
- Handoff. Documentation, a walkthrough session, and a recording your next hire can watch.
I had the pleasure of guiding Automattic VIP’s enterprise clients in creating their own Gutenberg blocks. The documentation and code demos I developed, such as those found in repositories like wp-and-js-demo, omars-demo, gutenberg-examples, and pusher-demo, played a significant role in helping their teams become familiar with the block editor.
Other Services