Request for Feedback: Make/Team Dashboards

Dashboards are more than just a collection of numbers and graphs; they are the pulse of a project. In the WordPress ecosystem, where collaboration and open-source principles guide us, dashboards can be a powerful team tool. Here’s why:

  • Improved visibility and communication: Dashboards can provide a centralized place for team members to view key metrics and data, such as the number of open and closed issues, the number of commits made, and the number of tests passed. This can help improve visibility and communication across the team and ensure everyone is aware of the progress. Additionally, this can show progress to those seeking opportunities to contribute where help is most needed.
  • Better decision-making: Dashboards can help teams make better decisions by giving them data-driven insights. This information can help them identify areas where they are doing well and where additional help is requested. 
  • Increased transparency: Dashboards can help increase transparency within the team by clarifying what is being worked on and what progress is being made. This can help to build trust and collaboration.

Which teams will be involved?

While feedback from all teams is needed, Sustainability and 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. teams are vital to this success.

Open-source sustainability is a multifaceted concept beyond just keeping a project alive. It’s about creating an ecosystem where the software, the community that builds it, and the organizations that rely on it can thrive long-term. 

The Sustainability Team can foster gathering information, identifying metrics, and partnering with the Meta Team on proposed tools to help us reach these goals.

Recap of progress thus far

Building stats dashboards is not a new idea; various contributor teams have considered the idea or have created proposals for the same in the past. Here’s a non-exhaustive summary of the work done so far. 

Feedback requests: Your Voice Matters

Examples of how other various open-source projects measure the health of their organizations can be found at

  • Active contributors to WordPress:
    • What metrics would you like to see on a team dashboard? 
    • How would you use a team dashboard?
    • How do we help ourselves (and future contributors) determine the right metrics?
  • WordPress Team Reps:
    • What metrics would be most helpful for you to track to represent your team effectively?
    • What would help you make data-informed decisions or help you focus on your top priorities?
  • WordPress Project Leadership 
    • What metrics would you like to see on a team dashboard to help you make informed decisions about your project?
    • How would you use this data?
  • Hosts, Plugins, Themes, SaaS, and Extender Ecosystem: 
    • What metrics and statistics would you like to see from teams throughout the WordPress Project?
    • What data would help you support your customers? 
    • How would data help your organization contribute to WordPress?
    • What data do you want to know regarding how your organization contributes?
  • Agencies from solo entrepreneurs through enterprise agencies (& their customers):
    • What metrics would be most helpful for you to track to manage your team’s workload and deliver high-quality results to your clients?
    • What metrics might your customers want to know?
    • What data do you want to know or have visible regarding how you or your organization contributes?

Conclusion: The Community’s Role in Dashboard Success

Your feedback is not just welcomed; it’s essential. 

Dashboards can be a cornerstone in the success of open-source projects like WordPress. They can help us be more transparent, make better decisions, and ultimately, create a more robust and inclusive community.

We invite you to leave your thoughts, suggestions, and insights in the comments below. Your voice can help shape the future of dashboards within the WordPress community.

Please share your feedback by: Wednesday October 11, 2023

The following people contributed to this post: @harishanker

Proposal: Documentation translation / localization

¡Hola! WordPress features an extensive array of documentation, but it’s primarily available in English and distributed across multiple platforms. This poses a significant challenge, as over half of WordPress installations globally are in languages other than English. Consequently, many users cannot easily access documentation in their native tongue. So, how can we address this issue?

Current Status

The bulk of WordPress documentation resides on two primary websites: 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. and While there are additional resources like manuals, tutorials, and forums, these two websites serve as the cornerstone for end-users, advanced users, and developers alike.

While some sections have been translated into other languages, the vast majority of this valuable content remains English-exclusive.

Final Objective

Given that over half of all WordPress installations are in languages other than English, our goal is to translate and sustainably maintain all the documentation in the world’s primary languages, with room for future expansion.

In the initial phase, we will focus on translating documentation tailored for end-users, advanced users, and developers. Subsequent stages will include additional resources such as Learn WordPress, Team Handbooks, and other related materials.

Previous discussions on the topic

Implementation Strategy

The method of achieving this monumental task is the proverbial million-dollar question. It has undergone extensive consideration, collaboration, and refinement across all involved teams. While it may not be the perfect plan, it is the most viable one we have arrived at after four iterative cycles of improvement.

Acknowledging that there are ongoing developments within the WordPress ecosystem, such as 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. Phase 3 and Phase 4. Although we’ve considered these, incorporating them at this stage is not feasible.

This proposal offers a realistic pathway to making WordPress documentation accessible to a global audience.

Centralizing Documentation Creation

The initial step in our strategy is to consolidate all documentation into a single, easily accessible location. Currently, the creation and discussion of documentation are scattered across various platforms such as Google Docs, 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., and WordPress itself.

To simplify maintenance and access, we have decided to host the foundational documentation on GitHub. Each segment of documentation will have its own dedicated repository, enabling individual teams to work in a more organized and efficient manner. This structure will also facilitate separate issue tracking and discussions for each repository, while allowing cross-repository conversation through project links.

Language-Specific Organization

To accommodate translations, each repository will feature folders named after the ISO codes of the languages into which the documentation will be translated. Initially, these folders will include “en” for English, and subsequently extend to other languages like “de” for German, “es” for Spanish, “fr” for French, and “it” for Italian.

Teams and Notifications

To stay abreast of changes in documentation, we’ll establish three tiers of teams that mirror the existing structure of the Polyglots community.

1. Repository Maintainers: These individuals will be responsible for the overall functionality of each repository. They will manage other teams and ensure that any updates are correctly implemented.

2. General Translation Editors (GTEGeneral Translation Editor General Translation Editor – One of the polyglots team leads in a geographic region Further information at GTEs will oversee each language-specific documentation group. Their role involves validating translations and ensuring their accuracy. There will be as many GTEs as there are languages to translate.

3. Translators: These contributors will carry out the actual translation work from one language to another.

When a change is made to any piece of documentation, the translators will receive notifications to update their translations accordingly. Should any language have pending translations, the respective managers will be alerted for validation and approval.

Those charged with high-level maintenance of the documentation will also keep track of the synchronization configurations between GitHub and WordPress, ensuring a seamless workflow and timely updates.

Translation Strategy

GlotPress, the WordPress built-in translation system, will not be used in this initiative to allow greater flexibility to adapt translations. The use of Machine Translation or Translation Memory will be at the discretion of the translators.

Given our scalability objectives, we’re focusing initially on translating into “general” language variants rather than “localized” ones. For example, we won’t distinguish between “Spanish from Spain” and “Spanish from Mexico,” or between “French from France” and “French from Canada.” Instead, our target is to cover the main languages spoken across all WordPress installations, with approximate percentage distributions as follows:

  • DE – German (6%)
  • EN – English (48%)
  • ES – Spanish (7%)
  • FR – French (5%)
  • IT – Italian (4%)
  • JA – Japanese (6%)
  • PT – Portuguese (5%)
  • RU – Russian (3%)

This coverage would extend to over 80% of existing WordPress installations.

Management for each translation team will occur through dedicated channels in the Global SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at workspace (e.g., #docs-de). These channels will allow contributors worldwide to collaborate effectively. We’ll also establish translation guidelines for each language to ensure the text aligns with cultural norms and linguistic nuances, whether formal or informal.

Content Structure and Format

All documents will be stored in Markdown format, compatible with GitHub’s native editing capabilities. This ensures a user-friendly interface accessible via a web browser, although more advanced GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. users are free to use the tools they prefer for translation work.

Each document will feature an initial H1 headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. (or “#” in Markdown) that designates the document title, followed by a final H2 header (or “##” in Markdown) labeled “Changelog” to log major updates transparently.

The information architecture will mirror the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL structure: language-specific folders will be followed by root files, which will contain an `` and any additional folders or subfolders needed for organizing the content. This approach enables the use of localized URLs for each language, further enhancing 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). (

Publication Process

The final decision to publish documentation will rest with the maintainers of each respective project. Maintainers will have access to a configuration file, often referred to as a “manifest,” where they can list the Markdown files hosted on GitHub along with corresponding WordPress slugs, content architecture, and priority ranking for menu arrangement.

Furthermore, the manifest will specify the unique slugs, URLs, or identifiers for different languages. This enables a seamless transition between language versions, allowing users to switch easily from one to another. Once content is integrated into this manifest, it will automatically be converted from Markdown to HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. or the relevant 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. format.

The power of the global community

One of the revolutionary aspects of this system is its capacity to enable content creation directly in languages other than English. While this introduces a layer of complexity requiring coordination, it opens up new avenues for content generation. A contributor who may not be proficient in English but is fluent in French, Spanish, or Italian can now create original content.

In this way, the system empowers the community to produce content in a non-English language first, which can then be translated into English. This democratizes the content creation process and harnesses the talents of over half of WordPress users worldwide who are non-English speakers.

Challenges Ahead

While this proposal paints an optimistic picture, the implementation is far from simple. Numerous elements, including content management, translation coordination, technology interfaces, and overall project management, contribute to the intricacy of this initiative.

However, many of these challenges have already been anticipated, and others will undoubtedly emerge as the project progresses. One promising aspect is that once we successfully translate one repository, the subsequent translations should unfold more smoothly, given that the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. process remains consistent across all elements.

In essence, this initiative is an ambitious undertaking, but its scalability and adaptability make it a worthy challenge, promising significant benefits for the global WordPress community.

Just the Beginning: A Unified Vision for WordPress Documentation

As initially mentioned, WordPress documentation exists in a myriad of locations and formats. This project serves as a foundational step toward standardizing tools and practices. It aims to create a centralized repository where everyone knows where to find information, can trace the history of changes, and receives due credit for their contributions in both creating and translating content.

But the initiative goes beyond mere standardization. WordPress has a rich ecosystem that includes an expansive Lean WordPress site, replete with numerous manuals, tutorials, and community-driven projects. Each Make Team within the community has its body of documentation, offering insights into how our community operates. This is invaluable information that could benefit a wider audience, particularly those who may be deterred from participating because they lack proficiency in English.

As our community continues to grow, open and inclusive communication becomes increasingly vital. This initiative not only promotes that growth but also democratizes access to information. In doing so, it makes it possible for a more diverse range of individuals to engage with the community in meaningful ways, even in teams where language has previously been a barrier.

Thanks to @estelaris, @nullbyte, @milana_cap, @otto, @clorith, @kenshino, @coachbirgit, @femkreations for the review, proofreading and hours spent on this proposal.

#docs, #documentation, #i18n, #l10n

Proposal for Establishing a Make Diversity, Equity, Inclusion, and Belonging (“DEIB”) Team within the WordPress Community

TL;DR: This proposal suggests establishing a Make Diversity, Equity, Inclusion, and Belonging (“DEIB”) team within the WordPress community to enhance and support the existing DEIB initiatives. Building upon the tireless work of fellow community members, this new team would provide a more structured and coordinated approach towards ensuring that all community members feel valued, included, and able to contribute to their full potential within the safety of our code of conduct.

This team aims to be a shared resource to all other Make WordPress teams. The team’s roles and responsibilities include broadening representation, cultivating an inclusive culture, promoting equitable opportunities, facilitating collaboration, and continuous assessment and improvement. The team will work towards clear objectives and tangible outcomes, such as increased representation, improved inclusivity, and increased access to opportunities.


As we work towards establishing an official DEIB team, a new channel on Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at serves as a collaborative space for all members of the working group.

Whether you’re here to contribute to the ongoing efforts or simply to observe and learn, we’re glad to have you with us.

Please join #deib-working-group and collaborate on 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. DEIB Project Tracker

The Why

As an active contributing member of the WordPress community for over a decade, I have witnessed the need for a more structured approach to diversity, equity, inclusion, and belonging (DEIB) within our community. Although my background doesn’t include formal academic training in DEIB, my extensive firsthand experiences and keen observations have shaped my deep understanding in this area. I have faced setbacks, and seen fellow community members experience discrimination and ignorance. These experiences have motivated me to develop this proposal.

While several teams within the community promote diversity, equity, inclusion, and belonging (DEIB), there is a need for a more structured and coordinated approach to these efforts in support of the whole project. A formal DEIB team would provide this structure, enhancing the existing initiatives and filling gaps where needed.

This formal proposal has evolved from an initial public idea exploration, which can be found in this blog post on my personal site. For a more in-depth exploration of this rationale, please refer to our whitepaper, “Proposal for Establishing a Formal Diversity, Equity, Inclusion, and Belonging (DEIB) Team“.

Before delving into the proposal, it is important to acknowledge and thank all the community members who have dedicated their time and skills to raise awareness and educate about DEIB. Their tireless work has laid a strong foundation for the generations and iterations to come within the WordPress community. Thank you!

The How: Proposed Role and Responsibilities

The Make DEIB team could become a shared resource to other Make teams, and could include the following roles and responsibilities:

  1. Broaden Representation: The DEIB team would work to ensure that all members of the WordPress community, regardless of their background, have a voice and feel included. This could involve outreach to underrepresented groups, efforts to make the community more welcoming and inclusive, and initiatives to promote diversity in leadership roles.
  2. Cultivate an Inclusive Culture: The DEIB team would work to create a culture where everyone feels valued and included. This could involve training and education on DEIB issues, efforts to promote respectful and inclusive communication, and initiatives to celebrate the diversity of the WordPress community.
  3. Promote Equitable Opportunities: The DEIB team would work to ensure that opportunities within the WordPress community are accessible to all. This could involve efforts to make training and education opportunities more inclusive, initiatives to promote equitable access to resources, and work to ensure that all community members have the opportunity to contribute and participate.
  4. Facilitate Collaboration: The DEIB team would work closely with other teams within the WordPress community to coordinate DEIB efforts. This could involve sharing resources, collaborating on initiatives, and promoting DEIB across the community.
  5. Continuous Assessment and Improvement: The DEIB team would implement regular assessments of DEIB initiatives and make necessary improvements. This could involve collecting and analyzing data on DEIB efforts, seeking feedback from the community, and making changes based on this feedback.

For a more detailed discussion of these roles and responsibilities, please check out the white paper for the proposed Make Diversity, Equity, Inclusion, and Belonging (“DEIB”) Team by clicking the button below:

Enhancing and Supporting Existing DEIB Initiatives

The DEIB team would work closely with other Make WordPress teams, working groups, and initiatives that touch on DEIB topics, and leverage existing work to support 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.

Objectives and Tangible Outcomes:

The DEIB team would have clear objectives and tangible outcomes, particularly regarding the identified gaps and overlaps. These could include:

  1. Increased Representation: Measurable increase in the representation of underrepresented groups within the WordPress community, particularly in leadership roles.
  2. Improved Inclusivity: Measurable improvements in the inclusivity of the WordPress community, as indicated by community surveys or other feedback.
  3. Increased Access to Opportunities: Measurable increase in the 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). ( of opportunities within the WordPress community, such as training and education opportunities.
  4. Effective Collaboration: Evidence of effective collaboration with other teams within the WordPress community, such as shared initiatives or resources.
  5. Continuous Improvement: Regular assessments of DEIB initiatives and evidence of improvements based on these assessments.

Mid-Term Strategy for the DEIB Team:

Over the next 3-5 years, the DEIB team will focus on several key strategic initiatives to achieve its mission and vision:

  1. Develop DEIB Guidelines: We will develop comprehensive DEIB guidelines for the WordPress community. These guidelines will provide clear expectations and best practices for promoting diversity, equity, inclusion, and belonging within the community.
  2. Implement DEIB Training: We will implement and enhance existing DEIB training for all members of the WordPress community. This training will educate community members about the importance of DEIB and provide them with the tools and knowledge they need to promote these principles in their work and interactions.
  3. Establish DEIB Metrics: We will establish clear metrics for measuring the success of our DEIB efforts. These metrics will help us track our progress, identify areas for improvement, and ensure that we are effectively promote DEIB within the community.
  4. Promote Diverse Leadership: We will launch initiatives to promote diverse leadership within the WordPress community. This could include mentorship programs, leadership training for underrepresented groups, and efforts to ensure diverse representation in decision-making processes.
  5. Enhance Community Engagement: We will enhance community engagement by creating opportunities for all community members to contribute to DEIB efforts. This could include community forums, DEIB working groups, and opportunities for feedback and input on DEIB initiatives.
  6. Collaborate with Existing Teams: We will work closely with existing teams within the WordPress project to coordinate and enhance DEIB efforts. This will help to ensure that DEIB is integrated into all aspects and that our efforts are aligned and complementary.

By focusing on these initiatives, the DEIB team can help to ensure that the WordPress community is a place where everyone feels valued, included, and able to contribute to their full potential.

Please refer to the whitepaper for a more comprehensive understanding of these objectives and tangible outcomes.

Your turn: share your thoughts!

By establishing a formal DEIB team, the WordPress community can enhance its commitment to diversity, equity, inclusion, and belonging, ensuring that all community members feel valued, included, and able to contribute to their full potential within the safety of our community code of conduct.

I invite all community members to provide feedback, thoughts, and suggestions on this proposal. Your input is invaluable as we work together towards a more inclusive and diverse WordPress community. Together, we can achieve more. Please leave your thoughts and feedback as a comment on the proposal below. 

Proposal from: Birgit Olzem (@coachbirgit

Reviewed and supported by (in no particular order): @martatorre, @jillbinder @courane01, @angelasjin @harishanker @bph @francina @annebovelett @kau-boy @devinmaeztri @evelina87

#5ftf, #deib, #wpdiversity

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). (, 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. 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 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 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 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 The WordPress community has its own Slack Channel at 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 Plugin Directory 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 There are many teams that people can participate in, each with a different focus. 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: 

  1. 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.
  2. 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.
  3. 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 flowchart depicting the contribution flow of the proposed mentorship program
  • 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 The WordPress community has its own Slack Channel at 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 @mikeschroder @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

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

#5ftf, #five-for-the-future, #proposal

Now we have a sustainability channel in Making WordPress Slack, what should we do?

At WCEU 2022, Nora Ferreirós from the Spanish WordPress community, asked Matt and Josepha about their thoughts on supporting sustainability concerns within the community. Matt suggested setting up a new sustainability channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at group, and there are now over 100 people in that channel! Josepha is open to discuss suggestions of specific issues that can be addressed.

This is fantastic progress! It demonstrates a growing interest in the WordPress community to come together and discuss sustainability concerns, both at leadership and community level. 

There are many questions worth addressing around this, especially as sustainability and maintaining the WordPress project are complex topics.

But before we dive into the specifics, perhaps it is best to take a moment to visualise what a sustainable WordPress community might actually be?

What are the tools, behaviours and systems we could co-create? What does being a member of a sustainable WordPress community feel like? What do other communities looking into ours observe? What are the things we want to move away from that hamper our progress to becoming more sustainable?

We wish to ignite a conversation about the art of the possible.

In the words of William Arthur Ward “If you can imagine it, you can achieve it. If you can dream it, you can become it”

We invite contributors from the whole WordPress community to share their visions for what we could do together: what does a truly sustainable WordPress community look like to you?

Let’s allow ourselves to dream big!

What can I do?

Start by being part of a WordPress community who openly discusses and actively works on sustainability issues. 

Leave a comment on this post to share or link to your thoughts on what a truly sustainable WordPress community looks like to YOU,

If you want to do more, join the sustainability Slack channel to take the conversation within the community further:

  • build on and discuss the visions shared by others;
  • contribute ideas on what we should do next;
  • share other sustainability work in the WordPress space that you find interesting.

 Here’s how to sign up to WordPress Slack.

You could also contribute to the on-going work of the performance team.

A few prompts to help you think about your vision

If you’re new to considering what a sustainable future might be like for WordPress, that’s ok. You’re not alone. We’re all exploring new possibilities here, and that’s the point. As a person new to this realm you are the perfect person to bring fresh ideas and perspectives to the table! Everyone is welcome to share their vision for what the future could be.

Here are a few prompts to get you going.

How can we help people understand what sustainability truly is?

  • Decarbonisation is often described interchangeably with sustainability. But decarbonisation is only one aspect of what needs to happen to create a truly sustainable future. This confusion leads many people to believe the only way you can make digital technologies more sustainable is by focusing on performance gains that reduce electricity consumption. The reality is this is just one aspect of what is possible. What else is possible?
  • There are many approaches to improving sustainability, some of which can be done in a way that respects the rights of people to thrive, and some of which abuse those. How can we communicate these ideas?
  • Many people still do not see sustainability as a positive move and may feel it would compromise their ability to grow a business effectively or innovate and push WordPress forward. How can we change perceptions of how a greener future for WordPress will benefit all of us?

How can we embrace the diversity of the WordPress community?

A sustainable future is one that embraces everyone’s differences and similarities.

  • The people that make up the WordPress community are multi-national, multi-cultural and multi-disciplinary. Sustainability will mean different things in different contexts. For example sustainability in the Global South might feel very different for someone in the Global North. How can we embrace a diversity of viewpoints and celebrate that?
  • The WordPress community manifests both physically, through WordCamps and meetups, as well as digitally through the software and documentation we produce. What are the tools we might build, the resources we could create and the conversations we could start that would benefit all our different manifestations?


The WordPress community isn’t new to working on sustainability issues. In fact Josepha mentioned that back in 2019 a group of people came to talk to her about the topic. 

We’d like to acknowledge the work done by Abha Thakor, for leading an informal sustainability group, and the recently created performance team for working hard at optimizing the software. These are great pillars to build on.

We look forward to seeing what a truly sustainable WordPress community looks like to YOU. Share your thoughts below.


Post written collaboratively by @hanopcan, @littlebigthing, @noradriana, @nahuai and @Thijs Buijs


Proposal to remove spam/dormant Five for the Future pledges

Last fall Andrea wrote about several challenges with the Five for the Future website that are preventing it from fulfilling its intended purpose. I’d like to start working on the first challenge of addressing spam or dormant pledges.

The Challenge

Many of the pledges have no recent activity on their profiles, or none at all; many only have personal activity (maintaining a 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 Plugin Directory or can be cost-based plugin from a third-party in the directory, asking for help in the support forums, etc); and many don’t participate in the Making WP SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at, where contributors primarily coordinate.

That inaccuracy weakens the value of sincere and active pledges. It also makes it difficult and impractical for team representatives to use the pledge lists to recruit contributors for projects. The lists for Core and Community have over 1,300 and 1,400 people respectively, many of whom seemingly have not contributed, are unlikely to contribute, and/or are inconvenient to contact.


To help surface active pledges, I’m proposing that we email all pledged 5ftF companies to request that they review, update, and confirm pledged contributors, teams, and hours. If they do not confirm within a reasonable period of time, their pledge would be removed.

Longer term, 5ftF could better identify and credit both code and non-code contributions. That would also help to keep pledges up to date.

To do this, we could automatically detect contribution based on Profile activity, and automatically remove pledges from folks who haven’t contributed in the past 6 months. In order to do that accurately, though, we’ll have to start crediting more non-code contributions, which often aren’t reflected on Profiles.

To track those, each team could request an activity that’s important to them, such as writing documentation; making changes to a Figma mockup; moderating a WPTV video; etc. We could also add a few things that cover all teams, like attending a Slack meeting, and giving/receiving props in the #props channel on Slack.

Once those are added to Profiles, then we could add an automated task to the 5ftF site which would examine all pledges every day. For those who haven’t contributed in 6 months, we’d un-publish their pledge, and send them a polite email to let them know. If removing them was a mistake, or they’d like to start contributing again, they can contact their team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.. Teams reps will be able to re-publish their pledge.


What do you think of this proposed next step? Are there problems that aren’t addressed, ways to improve it, or is there a better idea altogether? Please reply before March 31st.