The WordPress Criticism Debate - Redressing the Balance  [[3. Resources/Readwise/Full Document Contents/Articles/The WordPress Criticism Debate - Redressing the Balance|Full Document Contents]] ## Document Notes --- tags: #WordPress #Criticism #DeveloperWorkflow #WordPressCommunity - WordPress - Criticism - DeveloperWorkflow Author: [Content Creator] Source: [YouTube Transcript - "The WordPress Criticism Debate - Redressing the Balance"] Reference: [YouTube Link](https://www.youtube.com/watch?v=kgL7o5ND1kY) date created: {{2024-09-14}} {{15:30}} --- # Title: The WordPress Criticism Debate - Redressing the Balance ## Table of Contents: - [[#Introduction]] - [[#User Feedback]] - [[#Criticisms and Responses]] - [[#Developer Workflow Suggestions]] - [[#Conclusion]] ### References: - YouTube Transcript - Additional user feedback from the WP Minute and other forums ## 📝 Summary: This video covers key discussions around criticism of WordPress, focusing on issues raised by users regarding the Gutenberg editor, full-site editing, and developer workflows. It explores responses from both developers and community members and includes suggestions on improving the user experience and contributing to WordPress. ## 📖 Main Content: The WordPress Criticism Debate aims to address growing concerns from content creators, developers, and users about the current direction of WordPress development. A major theme is the complexity and inconsistency of the user interface in Gutenberg and full-site editing, with feedback suggesting a need for a more intuitive, role-based UI. The video also emphasizes the importance of contributing to the WordPress community by reporting bugs, requesting features, and participating in discussions on GitHub. ### 🗒️ Notes: - **User Frustrations**: Many users find the Gutenberg editor confusing, especially with hidden or inconsistent settings. - Users expressed concerns about needing to dig through options, making workflow more complex. - Suggestions were made to implement a "Basic" and "Advanced" mode to cater to different users. - **Developer Workflow**: There is a call for streamlining development processes, particularly around reporting issues and suggesting feature enhancements. - Developers suggested creating templates or automating some tasks to help speed up bug reporting and feedback loops. - **Criticism Acceptance**: The debate focuses on how criticism can be constructive when aimed at improving WordPress. Many contributors feel frustrated by slow feature rollouts and inconsistencies in UX design, but are optimistic about potential solutions. - **Community Involvement**: Contributors are encouraged to take an active role in improving the platform, particularly by engaging in GitHub discussions and advocating for changes. ## 📖 References: - YouTube Transcript: "The WordPress Criticism Debate - Redressing the Balance" - GitHub: [WordPress Project](https://github.com/WordPress) - WP Minute Podcast ## 🗣️ Paraphrase: 1. *Original*: "Contribution to WordPress doesn’t just mean coding. It could be reporting bugs or requesting features on GitHub. Anyone can help improve the platform." *Paraphrase*: "You don’t have to be a developer to contribute to WordPress. Reporting issues or suggesting new features on GitHub is just as valuable." 2. *Original*: "The simplicity of the UI has led to frustration, as users often need to dig through layers of options to find what they need." *Paraphrase*: "While the UI aims to be simple, it often results in users struggling to locate necessary settings, leading to increased frustration." ## 📰 Newsletter: 🎉 **Community Spotlight**: In this month’s edition, we explore some of the ongoing debates within the WordPress community. One hot topic is the Gutenberg editor's complex UI, which has led to a variety of opinions from developers and users alike. Many suggest introducing a "Basic" and "Advanced" mode to streamline the experience. On the development front, contributors are encouraged to report bugs and suggest features on GitHub, ensuring that the community's voice is heard. Don’t forget to check out our latest tutorials on optimizing your workflows with the newest WordPress updates! 🌟 [Read more](https://www.example.com) ## ✅ Action Items: - **Improve Contributor Engagement**: As a Developer Advocate, focus on educating new contributors on how to engage with WordPress development, specifically via GitHub for feature requests and bug reporting. - **Promote Clearer UI/UX**: Align feedback on improving WordPress’s interface with ongoing open-source efforts. Advocate for a more streamlined role-based experience that caters to both beginners and advanced users. - **Prepare Talks/Workshops**: As part of your mission to support open-source, prepare sessions that explain how to navigate WordPress GitHub discussions and submit features or issues effectively. ## 🧪 Hypotheses: - WordPress users would benefit from a more flexible, role-based user interface. - Community engagement increases when users understand the process of contributing to WordPress, beyond coding. ### 📊 Methodology: - Conduct user surveys across WordPress communities to gather insights on pain points in the UI. - Compare the user experiences of Gutenberg vs. third-party page builders like Bricks to identify common issues and strengths. ### ❓ Questions: - What specific areas of the Gutenberg UI do users find most confusing? - How could the developer community better streamline reporting and feedback loops? ### 🔮 Future Research: - Investigate alternative UI/UX models for WordPress to cater to different skill levels. - Explore how contributions could be made easier for non-developers in the WordPress ecosystem. ### 💡 Implications: Future research could influence significant improvements in WordPress's user interface, potentially making it more appealing to a broader audience and increasing community contributions. ### 🧠 Learning Styles Assessment: 1. **Visual Learners (Spatial)**: - **Present**: Screenshots and live examples are used. - **Improve**: Add more infographics and flowcharts to explain complex UI steps. 2. **Aural Learners (Auditory-Musical)**: - **Present**: Live stream discussions. - **Improve**: Provide downloadable audio summaries for auditory learners. 3. **Verbal Learners (Linguistic)**: - **Present**: Detailed verbal explanations. - **Improve**: Use analogies or storytelling for better comprehension. 4. **Physical Learners (Kinesthetic)**: - **Improve**: Suggest real-time problem-solving tasks to encourage hands-on learning. 5. **Logical Learners (Mathematical)**: - **Present**: Clear logical steps for troubleshooting. - **Improve**: Provide more data-driven solutions. 6. **Social Learners (Interpersonal)**: - **Present**: Opportunities for live community interaction. - **Improve**: Create group tasks or challenges. 7. **Solitary Learners (Intrapersonal)**: - **Present**: Reflection points in the discussion. - **Improve**: Encourage personal journaling or feedback. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure that all video captions and transcripts are accurate and well-formatted. - **Keyboard Navigation**: The content can be navigated easily, but enhancements like tabbing sequences should be explored. - **Contrast and Readability**: Improve contrast for better accessibility. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - **Inclusive Language**: The transcript avoids exclusionary terms, but more diverse cultural examples could enhance engagement. - **Neurodiversity Support**: Simplify sentences and use clear headings to make content accessible for neurodiverse individuals. ### ✅ Logical Validity: - **Sound Deductive Reasoning**: The argument for more role-based control of WordPress UI is logical and well-supported. - **Logical Fallacies**: None detected. ### 🔍 SEO Evaluation: 1. **Keywords**: Keywords like "Gutenberg criticism" are present but could be expanded. 2. **Meta Description**: Length is fine but could benefit from a stronger call to action. 3. **Title Tag**: The title tag is optimized. 4. **Headers**: Headers are well-structured, but incorporating more subheadings could improve readabilit > [!note]+ Document Notes > tags: [WordPress, Criticism, DeveloperWorkflow, WordPressCommunity] > - WordPress > - Criticism > - DeveloperWorkflow > Author: [Content Creator] > Source: [YouTube Transcript - "The WordPress Criticism Debate - Redressing the Balance"] > Reference: [YouTube Link](https://www.youtube.com/watch?v=kgL7o5ND1kY) > date created: {{2024-09-14}} {{15:30}} > > # Title: The WordPress Criticism Debate - Redressing the Balance > <!-- deep-read:sections start --> ## Table of Contents: 1. [Introduction](#Introduction) 2. [User Feedback](#User-Feedback) 3. [Criticisms and Responses](#Criticisms-and-Responses) 4. [Developer Workflow Suggestions](#Developer-Workflow-Suggestions) 5. [Conclusion](#Conclusion) ### References: - YouTube Transcript - Additional user feedback from the WP Minute and other forums ## 📝 Summary: This video covers key discussions around criticism of WordPress, focusing on issues raised by users regarding the Gutenberg editor, full-site editing, and developer workflows. It explores responses from both developers and community members and includes suggestions on improving the user experience and contributing to WordPress. ## 📖 Main Content: The WordPress Criticism Debate aims to address growing concerns from content creators, developers, and users about the current direction of WordPress development. A major theme is the complexity and inconsistency of the user interface in Gutenberg and full-site editing, with feedback suggesting a need for a more intuitive, role-based UI. The video also emphasizes the importance of contributing to the WordPress community by reporting bugs, requesting features, and participating in discussions on GitHub. ### 🗒️ Notes: - **User Frustrations**: Many users find the Gutenberg editor confusing, especially with hidden or inconsistent settings. - Users expressed concerns about needing to dig through options, making workflow more complex. - Suggestions were made to implement a "Basic" and "Advanced" mode to cater to different users. - **Developer Workflow**: There is a call for streamlining development processes, particularly around reporting issues and suggesting feature enhancements. - Developers suggested creating templates or automating some tasks to help speed up bug reporting and feedback loops. - **Criticism Acceptance**: The debate focuses on how criticism can be constructive when aimed at improving WordPress. Many contributors feel frustrated by slow feature rollouts and inconsistencies in UX design, but are optimistic about potential solutions. - **Community Involvement**: Contributors are encouraged to take an active role in improving the platform, particularly by engaging in GitHub discussions and advocating for changes. ## 📖 References: - YouTube Transcript: "The WordPress Criticism Debate - Redressing the Balance" - GitHub: [WordPress Project](https://github.com/WordPress) - WP Minute Podcast ## 🗣️ Paraphrase: 1. *Original*: "Contribution to WordPress doesn’t just mean coding. It could be reporting bugs or requesting features on GitHub. Anyone can help improve the platform." *Paraphrase*: "You don’t have to be a developer to contribute to WordPress. Reporting issues or suggesting new features on GitHub is just as valuable." 2. *Original*: "The simplicity of the UI has led to frustration, as users often need to dig through layers of options to find what they need." *Paraphrase*: "While the UI aims to be simple, it often results in users struggling to locate necessary settings, leading to increased frustration." ## 📰 Newsletter: 🎉 **Community Spotlight**: In this month’s edition, we explore some of the ongoing debates within the WordPress community. One hot topic is the Gutenberg editor's complex UI, which has led to a variety of opinions from developers and users alike. Many suggest introducing a "Basic" and "Advanced" mode to streamline the experience. On the development front, contributors are encouraged to report bugs and suggest features on GitHub, ensuring that the community's voice is heard. Don’t forget to check out our latest tutorials on optimizing your workflows with the newest WordPress updates! 🌟 [Read more](https://www.example.com) ## ✅ Action Items: - **Improve Contributor Engagement**: As a Developer Advocate, focus on educating new contributors on how to engage with WordPress development, specifically via GitHub for feature requests and bug reporting. - **Promote Clearer UI/UX**: Align feedback on improving WordPress’s interface with ongoing open-source efforts. Advocate for a more streamlined role-based experience that caters to both beginners and advanced users. - **Prepare Talks/Workshops**: As part of your mission to support open-source, prepare sessions that explain how to navigate WordPress GitHub discussions and submit features or issues effectively. ## 🧪 Hypotheses: - WordPress users would benefit from a more flexible, role-based user interface. - Community engagement increases when users understand the process of contributing to WordPress, beyond coding. ### 📊 Methodology: - Conduct user surveys across WordPress communities to gather insights on pain points in the UI. - Compare the user experiences of Gutenberg vs. third-party page builders like Bricks to identify common issues and strengths. ### ❓ Questions: - What specific areas of the Gutenberg UI do users find most confusing? - How could the developer community better streamline reporting and feedback loops? ### 🔮 Future Research: - Investigate alternative UI/UX models for WordPress to cater to different skill levels. - Explore how contributions could be made easier for non-developers in the WordPress ecosystem. ### 💡 Implications: Future research could influence significant improvements in WordPress's user interface, potentially making it more appealing to a broader audience and increasing community contributions. ### 🧠 Learning Styles Assessment: 1. **Visual Learners (Spatial)**: - **Present**: Screenshots and live examples are used. - **Improve**: Add more infographics and flowcharts to explain complex UI steps. 2. **Aural Learners (Auditory-Musical)**: - **Present**: Live stream discussions. - **Improve**: Provide downloadable audio summaries for auditory learners. 3. **Verbal Learners (Linguistic)**: - **Present**: Detailed verbal explanations. - **Improve**: Use analogies or storytelling for better comprehension. 4. **Physical Learners (Kinesthetic)**: - **Improve**: Suggest real-time problem-solving tasks to encourage hands-on learning. 5. **Logical Learners (Mathematical)**: - **Present**: Clear logical steps for troubleshooting. - **Improve**: Provide more data-driven solutions. 6. **Social Learners (Interpersonal)**: - **Present**: Opportunities for live community interaction. - **Improve**: Create group tasks or challenges. 7. **Solitary Learners (Intrapersonal)**: - **Present**: Reflection points in the discussion. - **Improve**: Encourage personal journaling or feedback. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure that all video captions and transcripts are accurate and well-formatted. - **Keyboard Navigation**: The content can be navigated easily, but enhancements like tabbing sequences should be explored. - **Contrast and Readability**: Improve contrast for better accessibility. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - **Inclusive Language**: The transcript avoids exclusionary terms, but more diverse cultural examples could enhance engagement. - **Neurodiversity Support**: Simplify sentences and use clear headings to make content accessible for neurodiverse individuals. ### ✅ Logical Validity: - **Sound Deductive Reasoning**: The argument for more role-based control of WordPress UI is logical and well-supported. - **Logical Fallacies**: None detected. ### 🔍 SEO Evaluation: 1. **Keywords**: Keywords like "Gutenberg criticism" are present but could be expanded. 2. **Meta Description**: Length is fine but could benefit from a stronger call to action. 3. **Title Tag**: The title tag is optimized. 4. **Headers**: Headers are well-structured, but incorporating more subheadings could improve readability. ## 🎯 Conclusion: The WordPress criticism debate shines a light on the need for better community engagement and user interface improvements, particularly within Gutenberg. By embracing feedback and streamlining developer workflows, WordPress can continue to evolve as a platform that caters to both beginners and seasoned professionals. Short Summary for [The WordPress Criticism Debate - Redressing the Balance](https://www.youtube.com/watch?v=kgL7o5ND1kY) by [Merlin](https://merlin.foyer.work/) Title: The WordPress Criticism Debate - Redressing the Balance [00:00](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=0) A follow-up to the criticism of WordPress in a live stream with new points to discuss. [02:06](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=126) Contribution to the WordPress project comes in multiple formats. [05:52](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=352) Encouraging community engagement and feedback for improving WordPress discussions. [07:41](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=461) Being part of the community and voicing concerns [11:22](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=682) The confusion and frustration around reporting bugs and requests in WordPress. [13:29](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=809) Implementing simple mode alongside advanced mode for client ease [17:26](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=1046) WordPress Gutenberg development process criticized for lack of speed [19:09](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=1149) Lack of consistency in design across different aspects of WordPress dashboard. [22:55](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=1375) Debate on integrating Gutenberg into WordPress core [24:50](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=1490) Debate on WordPress Gutenberg adoption [28:26](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=1706) Using a blueprint site for easy setup [29:53](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=1793) Defending the relevance and validity of creators in the WordPress space [33:41](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=2021) Debate on client access to WordPress dashboard [35:22](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=2122) WordPress 6.6 introduces complicated tools like CSS grid with non-standard naming conventions. [39:07](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=2347) Brizy's strength lies in Brizy Cloud, but it has not gained traction as expected. [40:51](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=2451) WordPress development pace and user satisfaction [44:26](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=2666) Builder integration in WordPress [46:21](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=2781) WordPress end of life caused trust erosion [49:43](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=2983) Uncertainty surrounding the future of WordPress due to changes in pricing model. [51:12](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=3072) Maxi Blocks offers free blocks but charges for designs and patterns as a business model. [54:35](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=3275) Anticipation for WordPress version 2.0 features. [56:10](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=3370) Not considering launching full paid courses [59:30](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=3570) Encouraging respectful discussions and diverse opinions. [1:01:01](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=3661) Get involved in the community and join the conversation. --------------------------------- Detailed Summary for [The WordPress Criticism Debate - Redressing the Balance](https://www.youtube.com/watch?v=kgL7o5ND1kY) by [Merlin](https://merlin.foyer.work/) Title: The WordPress Criticism Debate - Redressing the Balance [00:00](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=0) A follow-up to the criticism of WordPress in a live stream with new points to discuss. - The speaker and others watched a follow-up live stream on wp minute with Matt and Mark. - The speaker has some new points to discuss based on the follow-up and other recent developments. [02:06](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=126) Contribution to the WordPress project comes in multiple formats. - Contribution can involve bug reporting, feature requests, and getting involved with GitHub. - Involvement in contribution doesn't always require creating content like live streams and videos. [05:52](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=352) Encouraging community engagement and feedback for improving WordPress discussions. - Creating a monthly Roundup live stream to address questions and discuss topics related to WordPress. - Promoting respectful and constructive participation to gather diverse perspectives for a better understanding of WordPress ecosystem. [07:41](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=461) Being part of the community and voicing concerns - Engaging in conversations and tagging in relevant discussions opens up avenues to express concerns and frustrations more vocally. - Participating in live streams and being involved helps in sharing different points of view and shaping WordPress criticism. [11:22](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=682) The confusion and frustration around reporting bugs and requests in WordPress. - Confusion arises from multiple platforms for bug reporting and communication like GitHub, Slack, and track on wordpress.org. - Users struggle to understand where to report issues, leading to frustration and feeling of being ignored. [13:29](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=809) Implementing simple mode alongside advanced mode for client ease - Providing basic options for users who prefer simplicity in content creation - Introducing advanced mode with full settings access for those who require more control [17:26](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=1046) WordPress Gutenberg development process criticized for lack of speed - The criticism is about the slow development process of Gutenberg, which has been in development for six years. - The suggestion is to prioritize making Gutenberg fully featured based on feedback and community needs before moving on to additional phases. [19:09](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=1149) Lack of consistency in design across different aspects of WordPress dashboard. - Challenges with disjointed design and user experience. - Comparison with platforms like Wix, Squarespace, and Webflow. [22:55](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=1375) Debate on integrating Gutenberg into WordPress core - Discussions regarding the potential impact of integrating Gutenberg - Consideration of alternative solutions already in the market [24:50](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=1490) Debate on WordPress Gutenberg adoption - Gutenberg core vs plugin development cycle differences - Divergence in popularity and usage compared to other page builders [28:26](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=1706) Using a blueprint site for easy setup - Setting up a blueprint site in Gutenberg for preset options and configurations - Blueprint site saves time by avoiding repetitive setup tasks and enabling/disabling specific options as needed [29:53](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=1793) Defending the relevance and validity of creators in the WordPress space - Addressing comments undermining the importance of creators like Imran Jeffrey and others - Explaining the frustrations and similarities felt across the creator communities [33:41](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=2021) Debate on client access to WordPress dashboard - Discussion on whether clients should have full access to WordPress dashboard with tools like Bricks and Guttenberg - Some prefer creating a hybrid dashboard using Advanced Custom Fields and Classic Editor for client convenience [35:22](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=2122) WordPress 6.6 introduces complicated tools like CSS grid with non-standard naming conventions. - Usage of groups and complex terminologies in Gutenberg makes it difficult for most users. - The inherent problem of migrating content from one page builder to another due to data limitations. [39:07](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=2347) Brizy's strength lies in Brizy Cloud, but it has not gained traction as expected. - Brizy Cloud offers a clean interface to work with WordPress, but it's not seamless. - There is no automated way to migrate ACF custom post types, taxonomies, etc. to Jet Engine from Brizy. [40:51](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=2451) WordPress development pace and user satisfaction - Users are frustrated with the slow release of new features. - Finding the balance between fast and slow releases is challenging. [44:26](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=2666) Builder integration in WordPress - Constructive criticism on reliance on plugins and manual changes in Builder tools. - Recognition and respect for the challenges faced by developers in improving existing products like Quickly. [46:21](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=2781) WordPress end of life caused trust erosion - Early adopters and developers shocked by the sudden end of life - Support and bug fixes until 2025 insufficient for ongoing projects [49:43](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=2983) Uncertainty surrounding the future of WordPress due to changes in pricing model. - Discussion on potential charges for wireframes and other features. - Impact on lifetime deal owners and speculation on the future direction of WordPress. [51:12](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=3072) Maxi Blocks offers free blocks but charges for designs and patterns as a business model. - Professional pattern designs can speed up the design process and enhance the theme's capabilities. - The trend towards purchasing lifetime deals with fully featured products indicates a shift towards simplifying website design with pre-designed elements. [54:35](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=3275) Anticipation for WordPress version 2.0 features. - Excitement for potential improvements and enhancements in components. - Encouragement for user involvement in enhancing WordPress features and addressing bugs through various methods. [56:10](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=3370) Not considering launching full paid courses - Plans to focus on micro or mini courses for specific topics - Exploring courses focusing on practical projects like building a real estate website [59:30](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=3570) Encouraging respectful discussions and diverse opinions. - Open invitation for Matt and others to join live streams for valuable discussions and insights. - Upcoming live stream dedicated to discussing WordPress-related topics with a diverse panel. [1:01:01](https://www.youtube.com/watch?v=kgL7o5ND1kY&t=3661) Get involved in the community and join the conversation. - Participate in discussions via Twitter, messages, and emails. - Provide feedback and be part of the live streams. <!-- deep-read:sections end --> ## Highlights - if we're going to criticize then we should put ourselves in a position where we as creators content creators go and actually contribute to Wordpress now contrib contribution is something that I think most of us have probably looked at and thought that contribution just basically means you gain in start coding and I think the reality of it is that's kind of come up to me anyway the last day or so is that contribution to the WordPress project Pro actually comes in multiple different formats and one of those formats is that you can get involved in if you find bugs reporting them if you find you know features that are lacking or you want feature requests and things get involved with the GitHub side of things so I released a video probably about an hour ago that shows anybody that would be interested in that side of things exactly how to do it and I take that on board and yeah I can't say that there's anything wrong with that yet if we want to complain about it we we do have to be involved in trying to make that change and that change may not always come in ([View Highlight](https://read.readwise.io/read/01j7s233mxmw58r1mwm34ethhg))