The WordPress community has long been a pillar of open-source collaboration, innovation, and camaraderie. For over 20 years, it has grown to become one of the most influential platforms for creating websites and managing content. Recent events have exposed a fracture within this tightly knit ecosystem, stemming from a contentious dispute between Matt Mullenweg, the CEO of Automattic, and WP Engine, a managed WordPress hosting provider. This legal battle threatens to undo over two decades of collaboration.
The conflict erupted publicly on September 21, 2024, during the yearly WordCamp U.S. Conference, where Mullenweg’s keynote speech sent shockwaves through the WordPress and Website Development communities. Standing on the stage at the end of the conference, Mullenweg criticized WP Engine, said they are a “cancer” to WordPress—a striking and inflammatory remark that left attendees stunned. In a blog post on WordPress.org posted the same day he stated that they “do not host WordPress websites” because they disable the revisions feature by default. He didn’t stop there either; his actions the last two months have caused many members of the community to reconsider their contributions to the WordPress project.
The underlying issues have simmered for years, and Mullenweg’s remarks were a culmination of tensions. The WordPress Foundation recently updated its trademark guidelines, though notably, the abbreviation “WP” is not included under the protected trademarks. According to Tech Crunch, Mullenweg has asserted that WP Engine is suing Automattic over trademarks and they have been attempting to negotiate a deal with WP Engine for some time. However, WP Engine has charted its own path, creating a range of proprietary solutions and tools. Critics argue Mullenweg is contradicting the ethos of open-source accessibility that WordPress was founded upon by making the inflammatory remarks he made at WordCamp and on the WordPress.org blog.
It’s important to understand the foundation of WordPress itself. WordPress was born in 2003 when Matt Mullenweg and Mike Little forked the now-defunct blogging platform b2/cafelog. This was made possible by the General Public License (GPL) version 2, which allows anyone to modify, redistribute, and even fork open-source software. Ironically, the GPL license that gave birth to WordPress also permits companies like WP Engine to build upon the platform in ways Mullenweg clearly does not approve of. This dynamic underscores a central tension in the current dispute.
One flashpoint in the legal battle involves the popular Advanced Custom Fields plugin, which was recently renamed to Secure Custom Fields on WordPress.org. This rebranding raised eyebrows and led to speculation about whether WordPress.org’s community rules were being bent—or outright broken—to suit certain agendas. Mullenweg, who created this set of rules and has updated them over the years, has been accused of violating them himself with his comments at WordCamp U.S. and when he renamed WP Engine’s plugin on WordPress.org. The optics are troubling for a leader who has championed openness and fairness within the WordPress ecosystem.
Compounding the issue is the growing disillusionment among plugin and theme developers. Many are voluntarily removing their contributions from the WordPress.org repository, citing frustrations with the legal feud and the polarizing rhetoric it has generated. The lawsuit, some argue, is tearing apart a community that took more than two decades to build. The collaborative spirit that once defined WordPress has given way to divisions, with developers and contributors questioning whether their efforts are still aligned with the platform’s original vision.
For many in the community, including myself, siding with WP Engine is not a decision made lightly. I don’t currently make any money from clients using WP Engine, yet I find myself sympathetic to their position. The requirement to check a box affirming, “I am not affiliated with WP Engine in any way, financially or otherwise,” when logging into WordPress.org feels petty and exclusionary. It’s a stark reminder of how far this conflict has devolved from its roots in open-source ideals.
The heart of the matter may lie in economics. WP Engine is worth more than 40 times the $7.5 billion Automattic is valued at, and this disparity may be fueling the dispute. Mullenweg, who has often spoken about WordPress as a mission rather than a profit-driven enterprise, may be grappling with the reality that WP Engine’s success challenges that narrative. But is this reason enough to fracture an entire community? The damage being done extends beyond the two organizations; it jeopardizes the future of WordPress itself.
The implications for WordPress as a platform and WordPress.org as a community are profound. WordPress remains the most popular content management system in the world, powering over 40% of all websites. However, its dominance is not guaranteed. As divisions within the community grow, so does the risk of fragmentation. Developers and contributors are the lifeblood of WordPress, and their exodus could have long-term repercussions. The platform’s strength has always been its vibrant and engaged community, but that strength is now being tested.
What’s more, the community’s trust in its leadership is eroding. Mullenweg’s choice of words and actions have alienated many who once revered him as a visionary. While his contributions to open-source software are undeniable, his handling of this conflict has cast a shadow over his legacy. WordPress.org, the hub for themes, plugins, and resources, risks losing its relevance if the community no longer feels it is a space for collaboration and innovation.
Looking ahead, the question is whether WordPress can survive this internal strife intact. The GPL v2 license ensures that WordPress as open-source software will persist, but the community that has grown around it may not. If the infighting continues, it could pave the way for competing platforms to rise, attracting disillusioned website developers and users. This scenario would weaken WordPress as a whole, diminishing its influence and relevance in the broader tech landscape.
Here’s the thing folks: At its core, this lawsuit is a distraction from the true purpose of WordPress. That is to empower people to create and share content. The open-source ethos that inspired WordPress in 2003 remains as vital as ever, but it must be upheld through collaboration, not conflict. The community deserves better than to be caught in the crossfire of a legal and philosophical battle.
With that… As someone who has built a website development career using the WordPress platform and been part of its community for years, I hope for a resolution that prioritizes unity over division. While I align with WP Engine in this dispute, my ultimate hope is for both sides to recognize the greater good and work towards rebuilding trust. WordPress has the potential to continue thriving as a platform and a community, but only if its leaders and stakeholders can move past their differences and refocus on what truly matters.
When you play with them you have a different understanding.