Funding Call: Improving WordPress Block Editor Developer Docs
Two WordPress contributors are seeking backers to fund their work on improving documentation for the block editor, commonly known as Gutenberg. This is an opportunity for the community to directly support a project many developers have been asking for.
Anyone who has built a block for the WordPress editor has likely run into the same wall: meaningful documentation is hard to come by. Recent technical write-ups on block variations and adding custom welcome guides have both highlighted the same issue. Developers describe having to reverse-engineer solutions or resort to trial and error because official guidance is thin. Even exploring the range of available build tools — from create-gluten-block to wp-cli to ACF Blocks — reveals a fragmented ecosystem with no clear, documented standard.
While the reasons for the documentation gap are debatable, and though it has been over a year since the block editor's initial release, the more productive focus is on moving forward. The lack of clear, example-rich documentation is a key barrier. Establishing documented standards with real-world examples would be a significant victory for both the WordPress project and its developer community.
Why Documentation Matters Now
The block editor has proven itself in real-world use. Teams that have switched to working directly in it, for instance, have often found the experience so smooth that they've abandoned other writing tools like Dropbox Paper or Google Docs. The editor is already a central part of the WordPress experience for many.
The next big challenge is making it more accessible to developers. By sponsoring this work, those who benefit from Gutenberg can help improve the quality of its developer resources. Fostering that accessibility is seen as the best way to encourage the new ideas and innovations that will shape the future of blocks in WordPress.
