WordPress Issues - What Can I Do?  [[3. Resources/Readwise/Full Document Contents/Articles/WordPress Issues - What Can I Do|Full Document Contents]] ## Document Notes --- tags: #WordPress #GitHubContribution #UIUX #FeatureRequest - WordPress - GitHubContribution - UIUX Author: Paul C Source: YouTube Reference: [WordPress Issues - What Can I Do?](https://www.youtube.com/watch?v=fQeC9Kv_KwA) date created: 2024-09-14 15:30 --- # Title: How to Contribute to WordPress - Reporting Bugs and Feature Requests on GitHub ## Table of Contents: - [[#Introduction]] - [[#Identifying the Issue]] - [[#Checking Existing Issues on GitHub]] - [[#Submitting a Feature Request]] - [[#Encouraging Community Involvement]] ### References: - GitHub Repository for [WordPress Gutenberg Issues](https://github.com/WordPress/gutenberg/issues) - YouTube Transcript ## 📝 Summary: The video outlines how to contribute to the WordPress community by reporting bugs or submitting feature requests through GitHub. It simplifies the process of checking existing issues and explains how to create a new issue for bugs or feature requests. The goal is to encourage community members to take an active role in improving WordPress by participating in the feedback loop on GitHub. ## 📖 Main Content: In this video, Paul C highlights the common misconception that contributing to WordPress means coding. Instead, contributions can include reporting bugs, requesting new features, and engaging in conversations around existing issues. The video walks through an example of a frustrating bug in Gutenberg’s typography settings and how to navigate GitHub to check for existing reports, or how to submit new ones. ### 🗒️ Notes: - **Common Frustrations**: The video identifies an issue where typography settings in Gutenberg are not saved, forcing users to re-enable settings every time they edit a post. - **Checking Existing Issues**: Before submitting new feature requests or bug reports, it's essential to search the WordPress GitHub repository to see if the issue already exists. - **Submitting a Feature Request**: If no existing issue matches, Paul explains how to create a new feature request, providing detailed information, proposed solutions, and supporting media. - **Community Engagement**: Sharing issues across platforms like Twitter, Facebook groups, or email lists can help raise awareness and encourage more users to contribute to the solution. ## 📖 References: - GitHub: [WordPress Gutenberg Repository](https://github.com/WordPress/gutenberg) - YouTube: [WordPress Issues - What Can I Do?](https://www.youtube.com/watch?v=fQeC9Kv_KwA) ## 🗣️ Paraphrase: 1. *Original*: "Most people think contributing to WordPress means writing code, but you can also contribute by reporting bugs or suggesting new features." *Paraphrase*: "Many assume that contributing to WordPress requires coding, but reporting bugs and proposing new features are also important ways to get involved." 2. *Original*: "Once you’ve submitted the issue, share it with others who may experience the same frustration to raise awareness and get more people involved." *Paraphrase*: "After submitting your issue, it's helpful to share it widely with others who face similar frustrations, which can increase engagement and visibility." ## 📰 Newsletter: 🌟 **Contribute to WordPress without Writing Code!** 🌟 Did you know that you can help improve WordPress even if you're not a developer? Contributing to WordPress isn’t just about coding – you can report bugs or suggest new features to the GitHub repository. Our latest video shows you how to do this step-by-step. From identifying an issue to checking for existing reports, and submitting your own feature request, you’ll be well-equipped to participate in the WordPress community. Watch the full tutorial and take your first step in contributing! 💻 [Watch here](https://www.youtube.com/watch?v=fQeC9Kv_KwA) ## ✅ Action Items: - **Community Education**: As a Developer Advocate, host workshops explaining how non-developers can contribute to WordPress through bug reporting and feature requests. - **Contributor Engagement**: Share relevant issues and feature requests in WordPress communities to promote participation. - **Video Tutorial Series**: Continue creating short, instructional videos showing practical ways to engage with the WordPress ecosystem, beyond coding. ## 🧪 Hypotheses: - Increasing awareness about non-coding contributions will lead to higher engagement in WordPress GitHub issue reporting. - Providing step-by-step tutorials will reduce the intimidation factor for new contributors. ### 📊 Methodology: - Conduct surveys in WordPress forums to assess the current level of community knowledge about non-coding contributions. - Track the number of new GitHub issue submissions after launching educational campaigns. ### ❓ Questions: - How can WordPress streamline the process for non-technical contributors to report issues? - What are the biggest challenges users face when trying to participate in the WordPress feedback loop? ### 🔮 Future Research: - Explore how to improve the GitHub issue submission process to make it more accessible to non-developers. - Study the impact of educational resources on the volume and quality of user contributions. ### 💡 Implications: More accessible contribution pathways could democratize the WordPress development process, enabling a broader base of users to have their voices heard in shaping the platform's future. ### 🧠 Learning Styles Assessment: 1. **Visual Learners (Spatial)**: - **Present**: Screenshots of GitHub, step-by-step visuals. - **Improve**: Include more diagrams and visual flowcharts explaining the process. 2. **Aural Learners (Auditory-Musical)**: - **Present**: Video explanation with clear, verbal instructions. - **Improve**: Provide an audio summary of the process for users to listen on the go. 3. **Verbal Learners (Linguistic)**: - **Present**: Detailed verbal descriptions of each step. - **Improve**: Offer downloadable transcripts and additional reading material. 4. **Physical Learners (Kinesthetic)**: - **Present**: The video encourages hands-on practice by reporting an issue. - **Improve**: Include interactive components or real-time exercises for users to follow along. 5. **Logical Learners (Mathematical)**: - **Present**: The process is broken down logically, with clear steps. - **Improve**: Add troubleshooting sections and problem-solving scenarios. 6. **Social Learners (Interpersonal)**: - **Present**: Encourage participation in community forums. - **Improve**: Offer group workshops or discussion boards where contributors can collaborate. 7. **Solitary Learners (Intrapersonal)**: - **Present**: Self-paced video learning. - **Improve**: Add reflection prompts or personal journaling opportunities for contributors to document their experiences. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure the GitHub interface and video tutorials are fully navigable using screen readers. - **Keyboard Navigation**: Verify all links and actions in the GitHub repository can be accessed via keyboard shortcuts. - **Contrast and Readability**: Improve color contrast in tutorial screenshots to aid users with visual impairments. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - **Cultural Relevance**: The video and GitHub repository should incorporate diverse examples from different cultural backgrounds. - **Inclusive Language**: Ensure the tutorial uses gender-neutral language and avoids technical jargon without explanation. - **Neurodiversity Support**: Break the process down into manageable steps with clear visuals to support neurodiverse users. - **Representation**: Ensure a variety of users are highlighted in the contribution process to foster a sense of belonging. ### ✅ Logical validity: - **Sound Deductive Reasoning**: The argument that contributing is not limited to coding is supported with evidence. - **Logical Fallacies**: None detected in the reasoning; the video is well-structured and informative. ### 🔍 SEO Evaluation: 1. **Keywords**: Terms like "WordPress contributions" and "Gi > [!note]+ Document Notes > tags: [WordPress, GitHubContribution, UIUX, FeatureRequest] > - WordPress > - GitHubContribution > - UIUX > Author: Paul C > Source: YouTube > Reference: [WordPress Issues - What Can I Do?](https://www.youtube.com/watch?v=fQeC9Kv_KwA) > date created: 2024-09-14 15:30 > > # Title: How to Contribute to WordPress - Reporting Bugs and Feature Requests on GitHub > <!-- deep-read:sections start --> ## Table of Contents: 1. [Introduction](#introduction) 2. [Identifying the Issue](#identifying-the-issue) 3. [Checking Existing Issues on GitHub](#checking-existing-issues-on-github) 4. [Submitting a Feature Request](#submitting-a-feature-request) 5. [Encouraging Community Involvement](#encouraging-community-involvement) ### References: - GitHub Repository for [WordPress Gutenberg Issues](https://github.com/WordPress/gutenberg/issues) - YouTube Transcript ## 📝 Summary: The video outlines how to contribute to the WordPress community by reporting bugs or submitting feature requests through GitHub. It simplifies the process of checking existing issues and explains how to create a new issue for bugs or feature requests. The goal is to encourage community members to take an active role in improving WordPress by participating in the feedback loop on GitHub. ## 📖 Main Content: In this video, Paul C highlights the common misconception that contributing to WordPress means coding. Instead, contributions can include reporting bugs, requesting new features, and engaging in conversations around existing issues. The video walks through an example of a frustrating bug in Gutenberg’s typography settings and how to navigate GitHub to check for existing reports, or how to submit new ones. ### 🗒️ Notes: - **Common Frustrations**: The video identifies an issue where typography settings in Gutenberg are not saved, forcing users to re-enable settings every time they edit a post. - **Checking Existing Issues**: Before submitting new feature requests or bug reports, it's essential to search the WordPress GitHub repository to see if the issue already exists. - **Submitting a Feature Request**: If no existing issue matches, Paul explains how to create a new feature request, providing detailed information, proposed solutions, and supporting media. - **Community Engagement**: Sharing issues across platforms like Twitter, Facebook groups, or email lists can help raise awareness and encourage more users to contribute to the solution. ## 📖 References: - GitHub: [WordPress Gutenberg Repository](https://github.com/WordPress/gutenberg) - YouTube: [WordPress Issues - What Can I Do?](https://www.youtube.com/watch?v=fQeC9Kv_KwA) ## 🗣️ Paraphrase: 1. *Original*: "Most people think contributing to WordPress means writing code, but you can also contribute by reporting bugs or suggesting new features." *Paraphrase*: "Many assume that contributing to WordPress requires coding, but reporting bugs and proposing new features are also important ways to get involved." 2. *Original*: "Once you’ve submitted the issue, share it with others who may experience the same frustration to raise awareness and get more people involved." *Paraphrase*: "After submitting your issue, it's helpful to share it widely with others who face similar frustrations, which can increase engagement and visibility." ## 📰 Newsletter: 🌟 **Contribute to WordPress without Writing Code!** 🌟 Did you know that you can help improve WordPress even if you're not a developer? Contributing to WordPress isn’t just about coding – you can report bugs or suggest new features to the GitHub repository. Our latest video shows you how to do this step-by-step. From identifying an issue to checking for existing reports, and submitting your own feature request, you’ll be well-equipped to participate in the WordPress community. Watch the full tutorial and take your first step in contributing! 💻 [Watch here](https://www.youtube.com/watch?v=fQeC9Kv_KwA) ## ✅ Action Items: - **Community Education**: As a Developer Advocate, host workshops explaining how non-developers can contribute to WordPress through bug reporting and feature requests. - **Contributor Engagement**: Share relevant issues and feature requests in WordPress communities to promote participation. - **Video Tutorial Series**: Continue creating short, instructional videos showing practical ways to engage with the WordPress ecosystem, beyond coding. ## 🧪 Hypotheses: - Increasing awareness about non-coding contributions will lead to higher engagement in WordPress GitHub issue reporting. - Providing step-by-step tutorials will reduce the intimidation factor for new contributors. ### 📊 Methodology: - Conduct surveys in WordPress forums to assess the current level of community knowledge about non-coding contributions. - Track the number of new GitHub issue submissions after launching educational campaigns. ### ❓ Questions: - How can WordPress streamline the process for non-technical contributors to report issues? - What are the biggest challenges users face when trying to participate in the WordPress feedback loop? ### 🔮 Future Research: - Explore how to improve the GitHub issue submission process to make it more accessible to non-developers. - Study the impact of educational resources on the volume and quality of user contributions. ### 💡 Implications: More accessible contribution pathways could democratize the WordPress development process, enabling a broader base of users to have their voices heard in shaping the platform's future. ### 🧠 Learning Styles Assessment: 1. **Visual Learners (Spatial)**: - **Present**: Screenshots of GitHub, step-by-step visuals. - **Improve**: Include more diagrams and visual flowcharts explaining the process. 2. **Aural Learners (Auditory-Musical)**: - **Present**: Video explanation with clear, verbal instructions. - **Improve**: Provide an audio summary of the process for users to listen on the go. 3. **Verbal Learners (Linguistic)**: - **Present**: Detailed verbal descriptions of each step. - **Improve**: Offer downloadable transcripts and additional reading material. 4. **Physical Learners (Kinesthetic)**: - **Present**: The video encourages hands-on practice by reporting an issue. - **Improve**: Include interactive components or real-time exercises for users to follow along. 5. **Logical Learners (Mathematical)**: - **Present**: The process is broken down logically, with clear steps. - **Improve**: Add troubleshooting sections and problem-solving scenarios. 6. **Social Learners (Interpersonal)**: - **Present**: Encourage participation in community forums. - **Improve**: Offer group workshops or discussion boards where contributors can collaborate. 7. **Solitary Learners (Intrapersonal)**: - **Present**: Self-paced video learning. - **Improve**: Add reflection prompts or personal journaling opportunities for contributors to document their experiences. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure the GitHub interface and video tutorials are fully navigable using screen readers. - **Keyboard Navigation**: Verify all links and actions in the GitHub repository can be accessed via keyboard shortcuts. - **Contrast and Readability**: Improve color contrast in tutorial screenshots to aid users with visual impairments. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - **Cultural Relevance**: The video and GitHub repository should incorporate diverse examples from different cultural backgrounds. - **Inclusive Language**: Ensure the tutorial uses gender-neutral language and avoids technical jargon without explanation. - **Neurodiversity Support**: Break the process down into manageable steps with clear visuals to support neurodiverse users. - **Representation**: Ensure a variety of users are highlighted in the contribution process to foster a sense of belonging. ### ✅ Logical validity: - **Sound Deductive Reasoning**: The argument that contributing is not limited to coding is supported with evidence. - **Logical Fallacies**: None detected in the reasoning; the video is well-structured and informative. ### 🔍 SEO Evaluation: 1. **Keywords**: Terms like "WordPress contributions" and "GitHub feature requests" are present but could be expanded. 2. **Meta Description**: A concise meta description includes keywords and a call to action. 3. **Title Tag**: The title tag is SEO-friendly, clear, and concise. 4. **Headers**: Headers are well-structured and make use of keywords. 5. **Content Length**: The video transcript and content meet the recommended length for in-depth tutorials. 6. **Internal and External Links**: The video links to relevant GitHub pages and related tutorials. 7. **Mobile Optimization**: Ensure the video and GitHub links are mobile-friendly. 8. **Schema Markup**: Use FAQ schema to improve search visibility. 9. **Social Sharing**: Add share buttons and optimize Open Graph tags. ## 🎯 Conclusion: By showing how non-developers can easily contribute to WordPress through GitHub, this video empowers users to take a more active role in improving the platform. Whether through reporting bugs or suggesting new features, these contributions are crucial for the continued evolution of WordPress. Short Summary for [WordPress Issues - What Can I Do?](https://www.youtube.com/watch?v=fQeC9Kv_KwA) by [Merlin](https://merlin.foyer.work/) Title: Easy Ways to Contribute to WordPress via GitHub for Improving User Experience and Reporting Bugs [00:01](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=1) Getting involved with WordPress even without coding [00:41](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=41) Key to contributing in GitHub [01:23](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=83) When clicking outside, the changes are lost [02:06](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=126) Before creating a new issue, check if someone else has reported the same problem. [02:47](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=167) Address typography settings issues in WordPress [03:27](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=207) Creating a feature request in WordPress [04:09](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=249) Provide detailed information and solutions when addressing WordPress issues. [04:50](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=290) Share WordPress issues on social media and email for more visibility. --------------------------------- Detailed Summary for [WordPress Issues - What Can I Do?](https://www.youtube.com/watch?v=fQeC9Kv_KwA) by [Merlin](https://merlin.foyer.work/) Title: Easy Ways to Contribute to WordPress via GitHub for Improving User Experience and Reporting Bugs [00:01](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=1) Getting involved with WordPress even without coding - Contributing to WordPress doesn't always mean writing code - Report issues or bugs via GitHub to get involved [00:41](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=41) Key to contributing in GitHub - Getting involved and contributing is important for a meaningful return - Submitting to GitHub and the process can be challenging for beginners [01:23](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=83) When clicking outside, the changes are lost - After returning to edit a post or create a new one, the options are gone. - To address this, one can report the issue on the WordPress GitHub repository and get involved in the process. [02:06](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=126) Before creating a new issue, check if someone else has reported the same problem. - Search to see if the issue has already been reported by others. - Avoid creating duplicate issues to reduce redundancy. [02:47](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=167) Address typography settings issues in WordPress - Comment to raise awareness and provide implementation suggestions - Collaborate with others to improve the typography settings [03:27](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=207) Creating a feature request in WordPress - Users can create their own issue if not listed under the issue section. - Users can add a title that clearly explains the feature request. [04:09](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=249) Provide detailed information and solutions when addressing WordPress issues. - Include clear descriptions of the problem and proposed solutions. - Incorporate additional resources like videos or images to enhance understanding and visibility. [04:50](https://www.youtube.com/watch?v=fQeC9Kv_KwA&t=290) Share WordPress issues on social media and email for more visibility. - Utilize GitHub repository to share issues with others. - Engage with people on Twitter, Facebook, or email to gain more attention and push for resolution. <!-- deep-read:sections end --> ## Highlights - The reality is most of us consider a contributor being someone that's writing code and actually getting involved from that side of things. However, that isn't always the case. You can get involved in multiple different ways. This has kind of led me to do a little bit of research and come back with what I consider to be probably the easiest way that any of us can get involved. That's if we see something we don't like, something we want to change, or we find a bug, we actually report it via GitHub to WordPress. Now, there's no guarantees that any of this will actually be picked up and anything done, but the general consensus is if you don't get involved and you don't contribute, you can't really expect much in the way of return on that. Can't say I 100% agree, but let me show you how you go about actually submitting this to GitHub and the whole process because it's not the easiest thing in the world for the uninitiated. ([View Highlight](https://read.readwise.io/read/01j7sges9j1msk7p0p1me1th7e))