WordPress Development Resumes After Hiatus

Automattic has announced the resumption of WordPress core development, including Gutenberg and other projects, after a four-month pause. This pause occurred during a crucial period where competitors advanced in ease of use and technological innovation, leaving WordPress behind.

Did the Pause Benefit WordPress?

The pause was initially linked to ongoing litigation with WP Engine. Automattic stated it would return to active contributions only when the legal challenges ceased. While the litigation continues, Automattic has decided to restart development, suggesting a renewed focus on WordPress's future.

“After pausing our contributions to regroup, rethink, and plan strategically, we’re ready to press play again and return fully to the WordPress project… We’re committed to helping it grow and thrive.”

The question remains: was a four-month pause truly necessary to reach this conclusion?

Where Did the Investment Go?

In 2019, Automattic received a $300 million investment from Salesforce Ventures. This was intended to accelerate development across WordPress.com, WordPress VIP, WooCommerce, Jetpack, and contribute to WordPress.org and Gutenberg.

“For Automattic, the funding will allow us to accelerate our roadmap… and increase investing our time and energy into the future of the open source WordPress and Gutenberg.”

While WooCommerce and Jetpack saw increased updates, core WordPress and Gutenberg releases remained relatively steady. This raises questions about the impact of the investment on core development.

Can WordPress Adapt and Compete?

One positive outcome of the pause is the formation of a new WordPress AI team. However, this comes after competitors have already integrated AI, forcing WordPress to play catch-up.

Furthermore, WordPress leadership admits to lacking a long-term roadmap, prioritizing adaptability. While adaptability is important, the lack of a clear vision may contribute to the platform falling behind competitors.

Competitors like Wix, Divi, Elementor, and Beaver Builder have long offered user-friendly, block-based editors. The continued popularity of the Classic Editor plugin highlights the usability challenges faced by Gutenberg.

Key Takeaways

  • Automattic reversed its development pause despite ongoing litigation.
  • WordPress is forming an AI team, but competitors are already ahead.
  • The platform lacks a long-term vision, focusing on adaptability.
  • Significant investments haven't noticeably accelerated core development.
  • Gutenberg's usability remains a concern for many users.
  • WordPress faces a competitive disadvantage in the evolving CMS market.

Automattic's return to development highlights the challenges WordPress faces. The platform must now demonstrate its ability to innovate and meet the needs of modern users to regain its competitive edge. The future of WordPress hinges on its ability to adapt and deliver the tools users demand.