As developers and creators, our work is defined by projects. We begin with an idea, move to planning, then build, test, and finally, if we’re persistent (and a bit lucky), we ship. For years, my projects have lived in repositories—lines of code, features, and user interfaces. My latest launch, however, isn’t a GitHub repo or a server deployment. It’s a book. But not a static one—it’s a living, digital resource built for how we work today: “WordPress Blocks and Editor: A Comprehensive Guide.”
The development process was surprisingly familiar. It started with a clear problem to solve. The WordPress block editor (codenamed Gutenberg) is incredibly powerful, yet its learning curve can be steep. I saw developers and site builders stuck on basic blocks, unsure how to leverage full-site editing, create dynamic patterns, or customize the editor for their needs. The market required a structured, practical guide, and the MVP was clear: a book that serves as the definitive manual for the modern WordPress professional.
Next came the Architecture and Planning phase. This wasn’t about choosing a tech stack, but about structuring knowledge. I outlined the table of contents with the same rigor as planning a complex application. What are the core concepts? (The foundation). How do we build on them? (Custom blocks, themes). What are the advanced integrations? (APIs, dynamic content). Each chapter became a module, each section a component, all building toward a functional, complete understanding. Same process, different results.
The website, https://wp-block-editor.com, is the project’s live landing page. It’s built to speak directly to our peers, highlighting not just the chapters, but also the fact that this is a hands-on coding resource. It emphasizes the accompanying GitHub repository as a key feature—not an afterthought.
So, if your next project involves mastering the WordPress Block Editor, I didn’t just write a guide for you—I built a resource with the tools we use every day. Check out the project’s site to see the full scope of what I’ve delivered.
The repo is open, the book is live, and the project is officially shipped.