Matt Mullenweg Publicly Ponders “Year of Iteration”  🔗 **Source:** [Matt Mullenweg Publicly Ponders “Year of Iteration”](https://jamesgiroux.ca/matt-mullenweg-publicly-ponders-year-of-iteration/) > [!note]+ Document Notes > tags: > - WordPress > - YearOfIteration > - MattMullenweg > - Gutenberg > Author: James Giroux > Source: jamesgiroux.ca > Reference: None > date created: 2024-09-10 16:00 > > # Title: The Case for a ‘Year of Iteration’ in WordPress > <!-- deep-read:sections start --> ## Table of Contents: - [Summary](#summary) - [Main Content](#main-content) - [Notes](#notes) - [References](#references) - [Paraphrase](#paraphrase) - [Newsletter](#newsletter) - [Action Items](#action-items) - [Hypotheses](#hypotheses) - [Methodology](#methodology) - [Questions](#questions) - [Future Research](#future-research) - [Implications](#implications) - [Logical validity](#logical-validity) - [Conclusion](#conclusion) ## 📝 Summary: James Giroux explores Matt Mullenweg’s proposal for a ‘Year of Iteration’ in WordPress development, which aims to focus on refining existing features, fixing bugs, and improving user experience rather than introducing new functionality. This idea emerged from a broader conversation about the complexity of the WordPress codebase, the challenges developers face with Gutenberg, and the decline in WordPress’s market share among top websites. Giroux discusses how such a year could impact various aspects of the ecosystem, from education and training to recruitment, extenders, and users. ## 📖 Main Content: In a recent discussion, Matt Mullenweg, co-founder of WordPress, hinted at the possibility of taking a "Year of Iteration" to focus on fixing and simplifying the current state of the WordPress codebase. This comes at a time when the WordPress ecosystem is facing challenges, with market share dropping and developers feeling the pressure of rapid changes brought on by Gutenberg. Giroux outlines the potential benefits of such a year, including improved onboarding, updated documentation, and a better experience for developers and users alike. Giroux argues that the rapid pace of development has left gaps in training, documentation, and contributor recruitment. With each new release, educators and trainers face the challenge of keeping materials up-to-date, while developers struggle to understand the changes in the codebase. A year dedicated to iteration would provide time to address these gaps, refine the WordPress experience, and allow extenders (plugin and theme developers) to adapt to the block-based future of WordPress. ### Key Impacts: 1. **Training and Education**: The fast pace of development has left educational resources outdated. A year of iteration would allow for the updating of tutorials, guides, and video content, making WordPress more accessible to new users. 2. **Documentation**: Developers, especially those unfamiliar with JavaScript or Gutenberg, struggle to keep up with WordPress’s evolving codebase. A year of iteration would help improve documentation, making it easier for developers to contribute to the project. 3. **Recruitment of Contributors**: WordPress has seen a decline in new contributors, with recruitment and onboarding lagging behind the pace of innovation. A year of iteration could focus on mentorship and new contributor pathways, helping to grow the community. 4. **Extenders**: Many developers who built their businesses around Classic themes and plugins need time to transition to a block-based future. A year of iteration would allow them to solidify their business models and explore new opportunities with blocks. 5. **Users**: Simplifying the WordPress experience, particularly the admin interface and user experience, would benefit the wide range of WordPress users, from small businesses to enterprises. ## 🗒️ Notes: - Matt Mullenweg proposed the idea of a “Year of Iteration” during a conversation about the state of Gutenberg and WordPress development. - WordPress is losing market share among top websites. - A year of iteration would focus on refining existing features, improving documentation, and simplifying the user experience. - This initiative would benefit developers, trainers, educators, extenders, and users alike. - Giroux believes a Year of Iteration could help onboard new contributors, update outdated training materials, and solidify the foundation of WordPress as it pushes into enterprise and government sectors. ## 📖 References: - Giroux, James. "The Case for a Year of Iteration in WordPress." https://jamesgiroux.ca ## 🗣️ Paraphrase: 1. James Giroux reflects on the possibility of a Year of Iteration in WordPress, proposed by Matt Mullenweg. Giroux suggests that the rapid pace of development has left behind gaps in training, documentation, and contributor recruitment, and a dedicated year could address these issues by focusing on refining the platform rather than introducing new features. 2. Giroux points out that the WordPress ecosystem, particularly for developers and users, would greatly benefit from a year focused on iteration. This would give plugin and theme developers time to adapt to Gutenberg, while also simplifying the experience for end-users through improvements to the user interface and educational resources. ## 📰 Newsletter: 📢 Big news in the WordPress community! Matt Mullenweg recently floated the idea of a ‘Year of Iteration’—a period where the focus would shift to refining existing features, fixing bugs, and improving the user experience, rather than pushing out new functionality. This could be a game-changer for developers, trainers, and users alike, allowing for updated training materials, better documentation, and a more user-friendly experience. Keep an eye on the WordPress roadmap as this conversation unfolds! #WordPress #Gutenberg #YearOfIteration ## ✅ Action Items: This article aligns closely with my work in WordPress advocacy and education. A Year of Iteration would provide a valuable opportunity to update and improve training materials, which is crucial for onboarding new contributors and supporting educators. The focus on simplifying WordPress would also make it more accessible, which aligns with my goal of fostering a more inclusive and sustainable open-source community. As I pursue an OSPO director role, this concept could serve as a model for balancing innovation with long-term support and community building. ## 🧪 Hypotheses: - A Year of Iteration would lead to a measurable increase in new WordPress contributors as educational and documentation gaps are filled. - Extenders (plugin and theme developers) would benefit from a more stable foundation, leading to more block-based products in the WordPress marketplace. ### 📊 Methodology: To explore these hypotheses, a study could analyze contributor activity before and after the Year of Iteration, measuring the number of new contributors and the quality of contributions. For extenders, tracking the adoption of block-based themes and plugins over time could offer insights into the impact of this initiative. ### ❓ Questions: - How would a Year of Iteration affect the overall pace of innovation in WordPress? - Would simplifying the WordPress user interface lead to a higher adoption rate among small businesses and enterprises? ### 🔮 Future Research: Future research could focus on the long-term effects of a Year of Iteration on WordPress’s market share, particularly among top websites. Additionally, studying the recruitment and retention of new contributors during this period could provide valuable insights for future open-source projects. ### 💡 Implications: A Year of Iteration could set a precedent for balancing innovation with sustainability in open-source projects. If successful, it could inform how other projects approach long-term planning, community support, and recruitment. ### ✅ Logical validity: The article presents a well-reasoned argument for why a Year of Iteration would benefit WordPress. Giroux supports his claims with evidence of WordPress’s declining market share and the challenges developers face with the rapid pace of innovation. The article provides sound reasoning for focusing on refining existing features before pushing new functionality. **Strong Reasoning Identified**: - **Causal Reasoning**: The connection between rapid innovation and the challenges faced by educators and developers is clearly established. - **Balanced and Nuanced Views**: Giroux acknowledges the need for innovation but argues that pausing to refine and simplify would strengthen the ecosystem in the long run. ### 🎯 Conclusion: A Year of Iteration could offer significant benefits to the WordPress ecosystem, providing a much-needed pause to refine, fix, and simplify existing features. This approach would address gaps in education, documentation, and contributor recruitment while allowing developers and businesses to adjust to the block-based future of WordPress. Giroux’s article lays out a compelling case for why now is the time to consider such an initiative. <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/Matt Mullenweg Publicly Ponders “Year of Iteration”|Matt Mullenweg Publicly Ponders “Year of Iteration”, James Giroux]] ## Highlights - So, necessarily, folks prioritize. We eliminate edge cases and lower-traffic tutorial content in favour of our big hitters. A year of iteration would allow for updating tutorial and video content that in some areas may be quite legacy at this point. ([View Highlight](https://read.readwise.io/read/01j7f98g9mx5ytz3b1jawpyb93)) - I know for me, pre-COVID I was in the ‘it’ generation of WordPress. Somehow I’ve grown older and now there’s a generation behind me. But I’ve been so focused on how I did WordPress that I haven’t figured out how to adapt to a new generation of contributors. ([View Highlight](https://read.readwise.io/read/01j7f98ga6kjq29xw3v8m8fmdm))