X-comment from +make.wordpress.org/meta: Comment on Make Team Dashboards
Proposal: establishment of a formal WordPress Sustainability Team
The 20th anniversary of WordPress and its role as a dominant CMS mark the moment to act on sustainability now. We (the undersigned) are convinced that WordPress needs an official Sustainability team with the aim of making WordPress and its community lead on sustainability.
Making WordPress leading on sustainability asks for:
- Awareness about the impact of carbon emissions by the web and understanding how to build and work in a more eco-friendly way.
- Guidance for WordPress event organizers to organize events in a more sustainable way.
- Creation and promotion of eco-friendly themes and plugins.
This post contains our vision on sustainability with WordPress, actions of our initiative so far, its focus points, and an explanation of how we see the Sustainability Team functioning in the WordPress community.
Why a Sustainability Team?
Since its inception, WordPress has been a project developed with a mission to build a better web for everyone. The community has enabled the WordPress project to meet the challenges that have arisen during the past 20 years in pursuit of its mission. Now a new challenge is coming up, and we can’t afford to miss it.
Runaway climate change is a fact, and scientifically proven (IPCC Climate Change 2021: The Physical Science Basis). Every industry and sector of society has a role to play in mitigating the consequences. We can no longer look away from climate change, due to carbon emissions. At the same time, the importance of the web is undeniable. The WordPress community has an opportunity to show leadership and set an example on this topic.
We believe that the efforts of a Sustainability team will positively impact other WordPress teams, such as accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), performance and community, and should work in partnership with them. Digital and event sustainability requires collaboration with the rest of the WordPress teams to achieve effective change.
Establishing and building an official team will significantly raise visibility of the efforts to make the WordPress project more sustainable. It will also show the importance of sustainability inside the project and the support of the leadership. As the team would approach sustainability in a holistic way, this could also appeal to contributors with a non-technical background.
Open SourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. projects, such as Drupal or Wagtail, are starting to show a commitment to sustainability. A W3CW3C The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.https://www.w3.org/. working group is producing recommendations to encourage those making websites to follow sustainability guidelines. This would be similar to what has been done with Web Content Accessibility Guidelines.
By creating a Sustainability team, WordPress shows its leadership and willingness to proactively work on a solution for the sustainability challenge.
Team definition
The main objective is to embed sustainable practices into WordPress processes and its community. The WordPress Sustainability team would aim to promote awareness and actions that lead to carbon footprint reduction throughout the WordPress ecosystem.
What has the sustainability initiative done so far?
- A first “Now we have a sustainability channel in Making WordPress Slack, what should we do?” blog post has been published on Make WordPress Project Updates. This has built on sustainability efforts and research with WordCamps and Meetups in previous years.
- The Make WordPress #sustainability channel has grown towards almost 200 members in less than a year.
- There are weekly #sustainability Slack meetings on Friday, 11:00 UTC. Meetings are announced at https://make.wordpress.org/meetings/. Notes are taken from every meeting.
- Multiple contributors are working on a Google document about Making WordCamp more sustainable, bringing together the previous efforts by contributors in the community for raising awareness and sharing resources through the community and marketing teams. The document focuses on suggestions and tips for how events can be more environmentally sustainable and raise awareness. This is a great example of how a Sustainability team can support and work together with other teams. Once the document is finished, the latest version will be shared with the Community Team to add it to the WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. and meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. organizers handbook. Materials will also be shared with the Marketing, Community and Training teams, and explore opportunities for further awareness raising and case studies.
- The WP Sustainable plugin, published by the WordPress Hosting team, has been discussed regularly during the weekly meetings in the Sustainability SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. Contributors have provided suggestions for how the evolving pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party can improve. The group has had talks with the WordPress Hosting team, the WordPress Hosting team feels it makes more sense to let the plugin be a canonical plugin for the Sustainability team.
- Some of the channel contributors had led a sustainability table at WordCamp Barcelona 2023 Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.. You can check the summary published at the #sustainability Slack channel.
- There will be a sustainability table during WordCamp Europe 2023 on Contributor Day.
- The group is presenting a sustainability workshop at WordCamp Europe 2023.
The WordPress Sustainability team’s goals
To make the WordPress ecosystem lead on sustainability, we have formulated three goals to work on:
- Creating and spreading awareness about digital sustainability.
As the most used CMS in the world, WordPress has a significant influence on the impact websites can have on the environment. Often we don’t know how this impact is generated, and what we can do as individuals to reduce the impact. Creating awareness about the impact on the environment is essential to make WordPress a more sustainable ecosystem. - Increasing sustainability during WordPress events.
WordPress events are increasingly thinking about sustainability and need encouragement, support and further development. By producing and maintaining a section on sustainability for the Community handbook, the team will help organizers with a growing reference guide on how they can be as sustainable as possible. - Building an ecosystem that leads on sustainability.
WordPress is a leader in terms of its user base, in influencing website trends, and the size of its community. It’s also a project that stands out in its values. We believe WordPress, as an ecosystem, can lead on sustainability by acknowledging the necessity to act.
If you are interested, you can read more about the vision shared in the first post in 2022 on the Make WordPress Project blog.
The WordPress Sustainability team would acknowledge that a more sustainable world cannot be achieved individually. The team would need to partner with WordPress users, WordPress teams and the WordPress Community and wider in order to move WordPress towards a more sustainable environmental model.
We invite you!
Together, we can achieve more. We invite you to leave your thoughts and feedback as a comment on the proposal below. Please leave a message of support to identify your support for our proposal and to join #sustainability Slack channel and the weekly Slack meetings on Fridays, 11:00 UTC.
—
Proposal from: @littlebigthing, @nahuai, @noradriana, @yellowlime.
Reviewed and supported by (in no particular order): @javiercasares, @estelaris, @hanopcan, @webcommsat
WordPress Contributor Mentorship Program: Pilot Program Proposal
In February 2023, I proposed a project-wide WordPress mentorship program. Positive feedback and support from our community led to the revitalization of the WordPress contributor working group in March 2023, which has since been working on building a mentorship program for our project. Based on feedback from our chats thus far, our group decided to test this idea of project-wide mentorship by running a pilot program.
I’m excited to announce that the contributor working group has now prepared a first draft for a project-wide mentorship program! Read on to find out more.
What is the Contributor Mentorship Program?
The Contributor Mentorship Program aims to provide cohort-based and 1:1 mentorship to new and aspiring contributors. The program is intended as a pathway to help new contributors find their way into WordPress contributions.
It aims to set new contributors up for success by providing them the necessary guidance, skills, and knowledge around the project and helping them make their first contributions.
In its ideal form, the program will:
- Help and inspire its participants to make ongoing contributions to the WordPress project
- Explain the different areas of contribution in the WordPress project to participants
- Help participants to successfully select their area of participation in the WordPress project
- Provide necessary guidance and community connections that will help participants be successful with their contributions
- Help participants find success in their career through successful open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. contributions
A Brief Overview of the Program Plan
The flowchart below offers a high-level pictorial representation of the program flow, which I have tried to explain in brief through this post. A detailed description of the program can also be found in its white paper prepared jointly by the working group.
- A call for mentees (participants) goes out and from the pool of applicants, 10 mentees are selected (primarily new contributors). Mentors are handpicked from a pool of experienced contributors and working group members. Selected mentees and mentors answer a pre-event survey to gauge their knowledge, interest in contribution areas, and confidence-levels. Mentors will receive specific guidance on guiding mentees through the program.
- We invite all Make/Teams to take active part in this initiative to bring contributors to their respective teams. Interested teams can propose their team members as mentors to the program.
- A short cohort of new contributors (not more than 10 mentees) and experienced contributors (not less than five mentors) are to be brought together in a dedicated space (potentially a SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel in Make/WordPress) to work together for a certain period (about four weeks or one month)
- During this time, mentees will learn pre-prepared training material (existing contributor courses in Learn WordPress).
- Each mentee will be assigned a mentor depending on multiple factors such as their locale, time zones, contribution interest, etc. Mentors and mentees will have at least two 1:1 mentoring sessions (over text chat and/or video) throughout the course of the mentorship.
- Additionally, the group will have at least three group mentoring sessions on broad contribution topics (over text or video). Each week, mentees will also report their progress in the Slack channel and will have the space to interact with each other too.
- Once mentees are done with the broad contributor training courses in Learn WordPress (ideally in the first two weeks of the mentorship program), they work with mentors to identify contributor teams of their choice (if not clear already before joining the program) and go on to make a certain number of contributions (depending on the team they select). They will have completed these contributions by the end of the mentorship program. Optionally, should they wish to, mentees will create a three-month contribution and learning plan with their chosen mentor.
- Once all the courses and training sessions are complete, and once mentees have made their initial contributions, they graduate from the program, and the mentorship program wraps up. Mentees will be recognized for their contributions in public on an official WordPress space.
- Once the program concludes, Mentees will continue working with the Make/Team(s) of their choice, and will be connected to multiple team members from their chosen team for ongoing guidance as they continue their contributor journey.
- Post-wrap-up, mentees can continue to reach out to their cohort and mentors for ongoing guidance and support.
To find out about the proposed mentorship program in detail, please check out its white paper by clicking the button below:
How do we measure the success of this program?
The program will be considered extremely successful if:
- At least 80% of the participants of the initial cohort graduate from the program (they complete the course, required lessons, make their initial contributions, and create their three-month plan)
- At least 50% of the participants make ongoing contributions to WordPress as per their contribution plan, three months after completing the mentorship program
Other areas to measure impact:
- Improved confidence after the mentorship program (measured through surveys)
- Improved knowledge after the mentorship program (measured through surveys)
- Feeling of belonging and commitment to WordPress (measured through surveys)
Action Items and Request for Feedback
Request to Make/Teams: The contributor working group invites Make/WordPress Teams to join our pilot program as mentors. If you contribute to a Make/Team and wish to be involved in building this program, please express your interest in the comments.
- First of all, what do you think about this program in its current form? Please share your feedback in the comments of this post.
- You will notice that this post only explains the program in brief. The working group has prepared a white paper that explains the program in detail. Please review it and share your feedback – either as comments in the document or as comments on this blog post.
- Does this program excite you? Would you like to be a part of building a mentorship program for WordPress? We could use your help – Join the WordPress Contributor Working Group – participate in one of our mentorship chats, comment on this post expressing your interest, or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me in Make/WordPress Slack (I‘m @harishanker over there).
Big thanks to all members of the contributor working group in helping draft this proposal!
This post was jointly-written by members of the contributor working group: @adityakane @nao @oglekler @yoga1103 @kirasong @st810amaze @onealtr @carl-alberto @tobifjellner @javiercasares @sz786 @meher @courane01 @jeffpaul @sereedmedia @cbringmann @angelasjin @juliarosia @askdesign @nomadskateboarding @harishanker @javiercasares @gounder @unintended8 @webtechpooja @thewebprincess @unintended8 @desrosj @askdesign @webtechpooja @webcommsat @kcristiano @leonnugraha and @evarlese
#5ftf, #five-for-the-future, #proposal #contributor-working-group #wpcontributors #mentorship-program
Revitalizing the Showcase
Showcase Content Moderation Efforts
The Showcase aims to show the world what can be done with WordPress and help demonstrate the capabilities of WordPress as a publishing platform with a vast array of use cases of sites for personal bloggers and small businesses to enterprise companies and national governments.
With efforts made throughout 2022 to highlight the incredible capabilities of the WordPress platform, solidifying its values and identity, many eyes have been drawn to the opportunity that it presents.
WordPress is a brand that many people are unaware of, but interact with daily. Within the WordPress ecosystem, it’s known for its flexibility, popularity, and freedom to own one’s content. From personal blogs to enterprise websites, millions of sites are powered by WordPress. To highlight the power and breadth of the CMS, the project ought to showcase stunning and unique sites from all across the open web. What better way for WordPress to become a household name than to share and celebrate some of those stories?
The showcase represents the best of what’s possible with WordPress. Infinite possibilities of what you can create on the platform. Millions of sites could make it. Great, right? There are already some guidelines in place for submissions. A little more polish through a few updates could have added benefits to the collection. There are lessons from the guidelines for Moderating Photos that can serve as a beneficial example. First, remember that keeping the guidelines flexible and short can encourage people to submit. Second, it would be overly prescriptive to say things ought to be from specific categories or regions. By design, the Showcase should be diverse in every sense.
Knowing what’s worked well for the Project in the past, like the WP Photo Directory, while aligning it to WordPress brand values will make the Showcase one of WordPress’s most valuable marketing and communications assets.
History
Despite this goal, the existing WordPress.org Showcase has faced long-standing technical and moderation hurdles which made it difficult to keep updated. A variety of discussions about the Showcase’s purpose, design, and moderation are cataloged in Github.
The moderation process is cumbersome, relying heavily on a fragile automation process that has had issues over the years. Editing has been very manual, and elevated editor privileges have created bottlenecks over the years. Revisiting the showcase now should help alleviate some of the issues.
The Showcase receives hundreds of new submissions every year, about a third of which are spam/broken, and many more which do not meet the submission guidelines. Note too that current submission guidelines are open to a lot of interpretation, thus making the entire process of moderating Showcase far more complex than it needs to be.
The Showcase is a valuable asset for the WordPress project and re-starting efforts to keep it current and fresh will surely inspire others of the infinite possibilities of a WordPress-powered website.
Coming up
A companion post outlining the proposed guidelines for the WordPress Showcase has been posted to the Make Marketing blog. If you want to weigh in and get more involved in revitalizing the showcase, the Make Marketing team looks forward to hearing community voices!
Building Blocks: The Evolution of WordPress 2013-2023
Provide feedback via GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ with first-look access to the upcoming WP20 Book.
20 years — a new milestone
On May 27, 2023, WordPress celebrates a significant milestone in its journey as the project reaches its 20th anniversary. As part of the planned activities to mark this achievement, project leadership commissioned a book last year to document the years since its first commissioned work, Milestones – The Story of WordPress (2003-2013.)
The next volume, Building Blocks: The Evolution of WordPress, spans the history of WordPress from 2013-2023 and catalogs its wins, learnings, and everything in between. From changes to how users engage with the platform to confronting a worldwide pandemic, the book reflects on the most impactful moments over the last decade.
As the book gets ready for general release on the anniversary of WordPress, you, the community, have a role to play in ensuring that the story comes to life.
How you can help
You’re invited to play the role of editor by reviewing one or all of the 16 chapters. The book’s chapters are available on GitHub; each chapter has its own markdown file and is immediately available for download.
As you get started, a very important resource that can prove helpful is The WordPress Writing Style Guide.
Please focus on the content in your review rather than syntax, for instance. Here are some tips for what helpful feedback will look like providing additional source materials, including helpful links, offering potential images, spotting potential grammatical issues or typos, as well as any contextual documentation. Unhelpful feedback looks like offering a total rewrite or critique of the writing style.
To log a suggested edit, please create a new GitHub issue (one issue per ticket, please) and assign it to jpantani, who is assisting with this project’s wrangling.
Quick steps to take action
- Step 1: Familiarize yourself with the WordPress voice and tone
- Step 2: Visit and download the WP20-Book repo
- Step 3: Download and review the chapters
- Step 4: Log issue (one issue per ticket) and assign it to jpantani
- (Optional) Step 5: Reach out on Making WordPress slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. #marketing channel and tag @jpantani
Please share your feedback by April 30, 2023.
X-post: Launching the Contributor Working Group: Call for Volunteers
X-comment from +make.wordpress.org/community: Comment on Launching the Contributor Working Group: Call for Volunteers
X-post: Apply to Attend the 2023 Community Summit
X-comment from +make.wordpress.org/community: Comment on Apply to Attend the 2023 Community Summit
Proposal: Creating a WordPress Contributor Mentorship Program
In January 2023, I published a blog post requesting feedback from the community on the contributor journey for the WordPress open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project. There was extensive feedback from contributors around the world who identified gaps in the WordPress contribution flow. Upon analyzing the comments, two major action items stood out as potential solutions to fix these gaps:
- To improve the overall onboarding process in the WordPress project
- To offer more mentorship opportunities in WordPress
WordPress is an open source project that relies heavily on its community of volunteer contributors for its existence. Better onboarding and more mentorship opportunities will go a long way in fostering a vibrant community of committed volunteer contributors. By offering direct support for such contributors, we provide them with a unique learning opportunity that will help them grow as both leaders in the project and professionals in their fields while helping WordPress succeed.
To achieve this goal, I propose a project-wide WordPress contributor mentorship program that aims to empower new and aspiring contributors by helping them succeed in (and with) the project through mentorship.
This initial concept was born out of past discussions with contributors and feedback from the contributor journey blog post. Mentorship in WordPress is not a radically new idea – it has been discussed several times in past community summits and was formally proposed a few years back (in the form of an onboarding team). While the idea did not get a lot of traction in the past, feedback from contributors makes me feel that the time is right to launch such a program. I strongly feel that it will help us build the next generation of WordPress leaders we need to take our project forward through the future. This also ties to one of the big-picture goals for WordPress in 2023, which is to “Establish contributor and mentor programs.”
There are so many moving parts to any mentorship program and several factors that should be considered in order to make it happen. For starters, what will mentorship look like in WordPress? What kind of support do new contributors need? What type of mentorship works best? How can such an idea create a long-term impact? So many questions! Clearly, the idea behind a contributor mentorship program is complex. It should be a cross-team effort and needs the broader support of our global community to make it happen.
A dedicated working group will be needed for a project-wide WordPress contributor mentorship program. To that end, if this proposal moves forward, I’d love to revive the Contributor Working Group under the Make/Community Team.
The working group was founded in September 2020 and led by the amazing @amethystanswers. The group, with an original focus on improving the onboarding process, enhancing new contributor experience, and coordinating with Make/Teams, did a lot of good work such as suggesting improved onboarding flows, and organizing online contributor day events, even as the world struggled from the COVID-19 pandemic. I hope to build on the excellent contributions of the group and its members to kick off work on creating a contributor mentorship program for WordPress and finding ways to improve our onboarding flow.
Request for Feedback
- What are your thoughts on a Mentorship program for WordPress?
- Assuming this proposal gets support from the community, what would we need to make such a mentorship program successful?
- What are your thoughts on restarting the contributor working group?
- And finally – would you like to be a part of this working group to help build a mentorship program for WordPress?
Please share your feedback in the comments by F̶e̶b̶r̶u̶a̶r̶y̶ ̶2̶0̶,̶ ̶2̶0̶2̶3̶ February 27, 2023.
The following folks contributed to or reviewed this post: @angelasjin @cbringmann @tacoverdo @unintended8 @peiraisotta
Discussion: Ending the Eternal September
As part of our ongoing discussion around improving the contributor journey, I recently asked a few folks their thoughts on Eternal September in open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL.. More specifically, I wondered:
- What makes it difficult for our seasoned contributors to mentor new contributors in the open source project?
- What happens for existing contributors when we have an influx of new contributors?
- Where are the pain points for existing contributors when we bring in new contributors?
Some Initial Thoughts
There were a lot of interesting responses, but there we a few common threads I heard:
Lack of Clarity
It’s hard for existing contributors don’t know a new contributor is in their onboarding, and therefore also hard to see if they are stuck or what could get them unstuck.
Lack of Skills
The primary work for teams is focused, i.e., marketing, coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., etc. Welcoming and teaching new contributors is a different skill set from those specific focuses. And ever after accounting for that skills gap, there are unspoken cultural norms to get work looked at and moved forward which takes time and observation to learn, rather than task-oriented training.
Lack of Certainty
No matter whether a new contributor makes a single contribution or returns regularly over the coming months, the time required to make sure they have their bearings is the same. This creates tension among team members/existing contributors—they wonder whether they should prioritize existing work (new contributions) or training/support for new contributors.
What do you think?
I’d like your thoughts on the questions I posed above, but I’d also like you to consider this:
If we believe that speed of feedback on a contribution is key to helping a casual contributor become a regular contributor, then what would a good first contribution experience look like for a mentor?
Big Picture Goals 2023
To round out the excellent vision-setting done in both the State of the Word and Letter to WordPress, here are some goals and projects that we can anticipate in the WordPress project this year.
A Quick Caveat
There are always unexpected projects that arise over the course of the year. And there are big projects to move forward in pieces over the course of multiple years. This project is too big for me to see everything all the time, and I rely on the information from team reps and the vision from project leadership to help navigate any surprises.
If you don’t see a project here, keep in mind that many are still valuable to the overall success of our work.
From 10,000 Feet
There are three pillars that the year’s projects are focused on:
- CMS: Complete the Main Tasks for Phase 2 and begin explorations for Phase 3.
- Community: Re-engage our community through learning, events, and celebrating our 20th year as a project.
- Ecosystem: Update distribution methods and mechanisms for extenders and CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. itself.
I’ve compiled a preliminary list of individual projects that support one of the above goals and are planned for 2023. This list will be updated throughout the year.
CMS
- APIs:
- All those related to Phase 3 of the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ project
- Fonts APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.
- Interactivity API
- BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. API
- Openverse search in Core
- Navigation block
- Media management
- Simplify the release process
- PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. 8.2 compatibility (Core and Gutenberg)
- Block theme dev tools
- Custom CSS
- Custom CSS in Theme Variations
- Template Content Preservation
- Starter Content in Block Themes
- Theme preview
Community
- Community Summit planning and coordination
- Holistic contributor onboarding
- Refinement of Polyglot tools
Maintain learning content speed to shipContinue to ship learning content at the current pace- Update content and refresh design across wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/
- Establish contributor and mentor programs
- Develop a canonical pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party program
Ecosystem
- WordPress Playground
- Explore improvements to our contributor tools
- Create a WordPress brand discipline
- Simplify the release process (also in CMS)
- Refinement of Polyglot tools (also in Community)
- Develop a canonical plugin program (also in Community)
How Can You Help?
I know that our code isn’t the only measure of our success. If you already know what type of contribution you’d like to make, you can check out this list of teams (with links to their community sites) and team reps. If you’re not yet sure, here are the areas that each team falls into:
- Development, Technology, Code: Core/Editor, Mobile, CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress./Tide, Security, Performance
- Design, Product, UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it./UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.: Design, AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), Test, Triage
- Community, Extending WP, Education: Community, Themes, Plugins, Polyglots, Training
- Contributor Experience: MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress., Docs, Hosting, Privacy
- Communications: Marketing, Support, WPTV
A Note on Specialized Groups
A couple of coordinated efforts provide essential support to the progress of multiple teams.
- Triage: The triage effort happens across multiple teams and has two purposes. One purpose is to ensure tickets are sorted and have all the elements needed for someone to work on them. The second purpose is to determine priority. Not everyone has the information to set priority, but anyone can help sort and replicate reported bugs!
- Test: The testing effort also happens across multiple teams and has multiple purposes. One purpose is to validate bugs, bug fixes, and new features before they go to users. The second purpose is to bring continuous, high-quality feedback throughout the release cycle. A lot of that coordination happens on make.wordpress.org/test, but there are also calls to test during various points of the release process in the Core channel.