The recent conflict between WP Engine and WordPress has ignited a firestorm of discussion within the web development community, and as a web designer, I feel it’s crucial to articulate my stance on this matter. Both parties have made decisions that warrant scrutiny, and while I support WordPress as a product, I have significant criticisms of both WP Engine and Automattic.

WP Engine’s approach to WordPress raises serious ethical concerns. By altering the platform to disable core features and then offering those features back to customers for a fee, WP Engine is providing a version of WordPress that is essentially worse than the product itself. This practice undermines the open-source principles that make WordPress so powerful and accessible to everyone. When users are forced to pay for features that should be freely available, it creates an imbalanced relationship between a hosting provider and the open-source community that WordPress represents. This commercialization of fundamental WordPress functionalities not only diminishes the user experience but also threatens the very foundation of the platform, which relies on collaboration and community support.

On the other hand, I also find Matt Mullenweg’s decision to cut off WP Engine customers from WordPress.org’s resources to be an overreach. I understand the need to protect the integrity of the WordPress ecosystem, but punishing the end-users—many of whom may be unaware of the complexities behind the scenes—creates friction and unease in the community, especially for agencies striving to provide reliable web services to their clients. By restricting access to resources, Mullenweg risks alienating a segment of the WordPress user base, which can lead to distrust and division within the community. He also creates a situation where the security of literally thousands of websites could get compromised by outdated plugins. The focus should be on fostering collaboration and finding common ground, rather than exacerbating conflicts that could ultimately harm users and developers alike.

It’s vital to acknowledge that both WP Engine and Automattic have their respective roles in the WordPress ecosystem. WP Engine has built a business on the back of WordPress, and their actions can be seen as a bid to maximize profits at the expense of ethical practices. Meanwhile, Automattic, as the steward of WordPress, has the responsibility to maintain the integrity of the platform. However, heavy-handed tactics, such as restricting access to resources, can backfire and lead to greater discord within the community.

In this landscape of conflicting interests, my allegiance lies firmly with WordPress. Not with WP Engine, not with Automattic and certainly not with CEO Matt Mullenweg.

WordPress has revolutionized the way we build websites, enabling countless individuals and businesses to establish their online presence. Its open-source nature is a testament to the power of community collaboration and shared innovation. As we navigate the challenges posed by this ongoing conflict, it is crucial to prioritize the core values that have made WordPress a cornerstone of the web: accessibility, collaboration, and inclusivity.

So to sum it up, while I condemn WP Engine’s exploitative practices, I also caution against extreme measures taken by Automattic that could alienate users and set them in a disadvantage. I hope that both parties can find a path toward reconciliation that prioritizes the community and the open-source ethos that defines WordPress. In doing so, we can ensure that the platform continues to thrive and serve as a valuable resource for developers and users alike.