Category Archives: Uncategorized

Mary Hubbard 6:41 pm on January 23, 2026  

Big Picture Goals for 2026

I’ve been here a little over a year now. In that time, I’ve seen what works, where things get stuck, and how much care and effort contributors bring to this project every day. As I shared during State of the Word, 2026 is about momentum. 

Momentum means building on what’s already working, being clearer about direction, and making it easier for people to participate and move forward. It means taking the energy that already exists in this community and turning it into progress that compounds.

This is my first time sharing big picture goals with the Make community. My aim is to be clear about priorities and direction, while keeping the door wide open for collaboration. WordPress works because contributors show up. 2026 is about making it easier for more people to do exactly that.

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Development and WordPress 7.0

2026 will return to 3 releases a year coinciding with our events. With WordPress 7.0 coinciding with WordCamp Asia. 7.0 aims to offer a significant step into Phase 3: Collaboration, with real-time co-editing bringing Google Docs-style collaboration directly into the Editor. 

Efforts are underway to unlock powerful new workflows through the Abilities 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.-powered Command Palette and a standardized WP AI Client API, enabling plugins and hosts to integrate AI assistants in a provider-agnostic way.

Media handling will take a major leap forward in 7.0 with the graduation of client-side media processing into Core. Image resizing, compression, and format handling will increasingly happen directly in the browser, dramatically reducing server load while delivering faster, more reliable uploads for creators.

On the styling front, customization of mobile menus and responsive editing controls will finally give creators the ability to tailor layouts for different screen sizes and hide blocks by viewport, addressing a long-requested community need. The introduction of simplified pattern editing alongside new blocks like Tabs and Icon expands the creative toolkit available out of the box, making design more intuitive for a wider range of creators.

Together, these features represent a cohesive push toward a more collaborative, intelligent, and responsive WordPress experience.

[Get Involved with WordPress Core]

AI Everywhere, With Clear Guardrails and Benchmarks

WordPress will continue to invest in AI in a focused, intentional way. The goal is to make WordPress easier to use, easier to build with, and easier to contribute to, across the entire experience.

Guided by the AI building blocks, AI in WordPress will prioritize a few practical outcomes:

  • Helping people create, edit, and refine content where they already work.
  • Reducing friction in site building, configuration, and common workflows.
  • Supporting contributors and users with clearer guidance, context, and next steps.
  • Lowering the barrier to contribution by helping people find and complete meaningful work.

At the same time, the Core AI team will publish project-wide guidelines for AI usage within WordPress. These guidelines will focus on transparency, user control, data responsibility, and alignment with WordPress values. As AI becomes more embedded across the project, shared expectations matter, both for contributors and for the broader ecosystem.

[Read More from the Core AI Team]

Revamping Meetups

Meetups are the primary front door to the community. Let’s be more intentional about getting new people involved quickly.

As more contributors come in through initiatives like education programs, like Campus Connect and WordPress Credits, mentors should help them find a local 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.. Meetups are often the first place WordPress feels real. They are local, human, and reputable. Many WordCamps started as meetups, and that pathway still matters.

This year, we want to double down on meetups as places of active participation, not passive attendance. As AI tools become more common across the web, the need for shared learning increases. Meetups are where people can sit side by side, learn how these tools actually fit into WordPress workflows, and build confidence together. AI moves fast and we can develop better understanding, judgment, and together as a community.

That means prioritizing issue-focused sessions where people work together on real problems, hands-on learning tied to actual WordPress needs, and clear next steps that move people from meetup participation into contribution.

Meetups are where people build confidence, relationships, and momentum. When they work well, they turn curiosity into commitment. That is why they remain the primary front door to WordPress in 2026.

[Find a Meetup] | [Start a Meetup]

Community, Education, and the Contributor Pipeline

WordPress education programs are scaling quickly. WordPress Credits and WordPress Campus Connect have students arriving ready to participate and eager to contribute.

The project needs to be much clearer about where new contributors should go next and how they get started. Program managers can help connect student groups to Make teams, but that only works if each team is prepared to receive them.

I’d like to ask the Make teams to help make this possible by:

  • Maintaining clear onboarding materials and contribution paths.
  • Identifying approachable first issues or starter tasks.
  • Encouraging mentors who can help new contributors get oriented and moving.

Education is becoming one of WordPress’s strongest growth engines. It brings in new voices, fresh perspectives, and people eager to learn. As contribution continues to grow, the long-requested Contributor Dashboard will help make that work more visible. 

Over time, we want to move toward WordPress Foundation credentials that help standardize how WordPress skills are understood and communicated. These credentials would reflect what someone knows, what they can do, and how they work, giving employers a clearer signal when hiring for WordPress-related roles.

[Learn More About WordPress Education Programs]

Kel Santiago-Pilarski 5:34 am on December 20, 2025
Tags:   

Project Thread: Contributor Dashboard Pilot Project

A Contributor Dashboard Pilot is underway within the WordPress project, building on previous community work, and responding to long-standing requests from the community for better visibility into contributor journeys – how people join, participate, and grow across Make teams.

Contribution activity, especially non-code work is spread across many tools and systems. This makes it difficult to recognize contributors, understand engagement over time, and identify where support is needed.

Project Status

This project is currently in the active pilot development phase, led by @felipevelzani, @unintended8 and @kel-dc.

A limited multi-team pilot launch is planned for the end of February 2026. This project thread will be updated as work progresses.

What We’re Building

We’re building a Contributor Dashboard that maps contributor activity across teams into a shared Contributor Ladder framework:

Connect → Contribute → Engage → Perform → Lead

The ladder is behavior-based and describes patterns of participation over time. It does not rank contributors or imply that some contributions matter more than others. All contribution types and all contributors matter.

The goal is to help teams understand participation patterns, identify where support may be needed, and improve contributor experiences over time.

Why We’re Doing This

The project addresses several challenges across the project:

  • Contribution activity is scattered or not tracked
  • Non-code contributions often lack visibility
  • Teams have limited insight into how contributors progress over time
  • Cross-team onboarding, retention, and engagement patterns are difficult to assess

How We’ll Build the Pilot Dashboard

For the pilot, we’re taking a multi-team approach using a custom 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 that maps existing contribution activity from 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/ systems to ladder stages. This activity-based approach allows us to validate the model, identify data gaps, and gather cross-team insights without introducing new infrastructure or requirements for contributors.

Additional technical details and implementation notes are documented in the project’s public reference materials.  

Scope and Data

This pilot starts intentionally small and focuses on a limited set of existing contribution signals to test the dashboard and ladder approach. It does not aim to capture 100% of all contributions across Make teams.

The pilot does not replace or change Five for the Future, contributor recognition programs, or existing team processes, and it introduces no new requirements for contributors or Make teams.

Contributor privacy is a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. consideration. The dashboard uses existing WordPress.org accounts and activity data, does not display personal or sensitive information, and does not create new contributor profiles.

Hosting

  • The pilot dashboard will be hosted on Pressable to support development, testing, and iteration during the pilot phase, with the intention of moving to WordPress.org infrastructure in a future phase.
  • The custom plugin is designed to work within existing WordPress.org 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. systems and data constraints, without introducing new external dependencies.

Timeline & Milestones

• January–February 2026: Implementation, testing, and review  

• End of February 2026: Pilot launch

How to Get Involved

We’re looking for contributors to help bring this pilot to life and welcome collaboration from across Make teams. For this pilot, we’re especially looking for contributors who can help with the following: 

  • Building and improving the dashboard and plugin
  • Reviewing and validating contribution signals and ladder mappings
  • Testing the dashboard experience and reviewing insights
  • Helping iterate on documentation and communication as the pilot evolves

If you’re interested in getting involved:

We welcome ideas and participation from all Make teams and contributors during the pilot and as the project evolves. Community input will help inform iteration and improvements, while the pilot proceeds unless material concerns are raised around privacy, security, or alignment with WordPress project values.

Props @4thhubbard for post review.

Mary Hubbard 2:13 pm on September 15, 2025  

Announcing the Core Program Team

This program model was first introduced with the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI Team. Building on that experience, I’d like to expand it into an experiment with the launch of the Core Program Team. Tammie Lister has agreed to help as the first team representative.

The goal of this team is to strengthen coordination across Core, improve efficiency, and make contribution easier. It will focus on documenting practices, surfacing roadmaps, and supporting new teams with clear processes.

The Core Program Team will not set product direction. Each Core team remains autonomous. The Program Team’s role is to listen, connect, and reduce friction so contributors can collaborate more smoothly.

You can get involved by joining the #core-program 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 and following updates on the Core Program Team Blog, including a the welcome post that outlines next steps.

I am excited to see how this experiment helps Core teams work together and makes contribution more accessible to everyone.

Props to @karmatosed, @dd32, @desrosj who helped move this forward.

Mary Hubbard 4:38 pm on May 21, 2025  

Restoring Trust while Preserving Safety

In April, @matt wrote about reflection; how, after twenty years, WordPress is still growing, not just in code and contributors, but in responsibility. The Jubilee post invited us to pause and ask what kind of project we want to be for the next twenty.

One piece of that reflection was a review of accounts that had previously been banned from participating in our community spaces, including 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/ and 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/.. This review wasn’t done in isolation. It took collaboration across community teams and a shared commitment to fairness.

Any community as large and global as WordPress will at times feel the tension between openness and accountability. Processes don’t always hold up. Intentions don’t always translate into outcomes. And sometimes, we just get it wrong.

This review wasn’t about undoing everything. It was about restoring trust. Trust in the systems we use to moderate, and trust in the people behind them. Each account was considered in context and with care.

Most were reinstated. And a small number remain blocked, in cases where there were credible threats, harassment, or other actions that compromised the safety of others. In those moments, we choose safety. That’s not always the easiest choice, but it’s the right one.

What’s next

With this review now complete, I’d like to shift focus toward improving how we handle these situations going forward. That includes being more transparent when actions are taken, creating clear and consistent paths for appeal, and documenting decisions in ways that are easier to understand and easier to trust.

It might also be time to take a closer look at how responsibilities move through the project. In areas like moderation and community safety, is it time to establish clearer rotations? Rotating roles can help us avoid centralizing too much authority in any one place, and it guards against the single points of failure that 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. and communities should always aim to minimize. It’s a principle we trust in architecture. It applies equally to people and processes.

Bans and blocks aren’t a sign of failure. They’re part of maintaining a healthy space. But growth means we keep looking at how we apply them with care, with humility, and with a willingness to evolve.

If we continue to center empathy, transparency, and the shared goal of making WordPress better for everyone, we won’t just be stronger. We’ll be ready for whatever comes next.

Props to @jdembowski for help with this post

Destiny Kanno 3:37 am on May 1, 2025  

Review of Blocked Community Members

In an ongoing effort to foster a healthy and inclusive community, we are conducting a thorough review of blocked community members, prioritizing individuals who were blocked between August 2024 and the present date without communication or notification. This initiative spans both the 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/ and 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/. platforms and aims to identify accounts that can be unblocked and reinstated, allowing those members to re-engage with the community.

Unblocking Criteria and Process

The decision to unblock an account will be based on a thorough evaluation of the actions that led to the initial 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.. While some blocks were justified and will be upheld, we acknowledge that mistakes may have occurred, and some members may have been unfairly blocked. Our aim is to correct any past errors and provide a clear path for those members to re-engage with the community. We believe that by working together and fostering open communication, we can move forward and build a stronger, more inclusive community for everyone.

Factors Considered During Review

  • Severity of the Infraction: The nature and severity of the situation that led to the block will be a primary consideration.
  • Time Elapsed: The length of time since the block and any subsequent behavior of the individual will be taken into account.
  • Agreement to Adhere to Community Guidelines: The individual has expressed a commitment to follow the community code of conduct and forum rules.
  • Community Impact: The potential impact of unblocking on the overall community health and well-being will be considered.

Timeline and Communication

We understand that this process may take some time due to the number of accounts under review and the need for a thorough evaluation of each case. Please note that we are prioritizing those who were banned without notice or communication, and spammers will not be notified.

We are committed to providing regular updates on the progress of this initiative and will communicate any significant developments to the community in a timely manner.

Commitment to a Healthy and Inclusive Community

This unblocking initiative reflects our commitment to fostering a welcoming, inclusive, and respectful community where all members feel valued and supported. While maintaining the health and integrity of our community is paramount, we also believe in providing opportunities for individuals to learn, grow, and contribute positively. This initiative is a step towards achieving that balance, and we are hopeful that it will contribute to a stronger and more vibrant community for all.

We appreciate your patience and understanding as we work through this process.

Mary Hubbard 5:29 pm on April 16, 2025  

A New Cadence for WordPress Core

There have been a few questions around our decision regarding the WordPress Release cadence, which I’m glad to address. After years of releasing WordPress three times a year, and a recent discussion with Core committers, we’re making a change — for now.

Starting in 2025, WordPress will move to a single major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. per year, with WordPress 6.8 “Cecil” marking the final major release for the calendar year. From there, the next major release will land in 2026, and we’ll continue on that annual cycle for the time being.

This decision reflects current realities — particularly the energy and resources being diverted due to ongoing legal matters. If those lawsuits are dropped or resolved, we’ll revisit this cadence and strongly consider returning to a three-releases-per-year schedule. That remains the ideal for a fast-moving, community-driven project like WordPress.

In the meantime, the annual cycle gives us the space to focus on essential work that often gets sidelined:

  • Reducing technical debt and long-standing bugs
  • Improving performance across coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
  • Supporting noncommercial community plugins
  • Investing in design, testing, and the broader contributor experience

We’ll continue to issue minor releases as needed for maintenance and security, and we’re introducing quarterly core committer town halls to strengthen collaboration and alignment across teams.

Looking ahead, this cadence puts WordPress 7.0 on track for 2027 — and with the additional time, we’re aiming for more than just a version number. 7.0 will be a milestone: a thoughtful, intentional release that reflects how far the platform has come and the kind of future we’re building toward.

Alex Kirk 4:20 am on January 11, 2025  

Shutting down WordPress.org’s Matrix Server

After careful evaluation and considering the evolving needs of our community, we have decided to shut down the community.wordpress.org Matrix server on January 31, 2025.

With the integration of Single Sign-On (SSO) using WordPress.org accounts on 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/., one of the primary advantages of the Matrix solution—simplified onboarding for new contributors—has been effectively addressed. Additionally, with very low usage and no significant demand for Matrix services, maintaining the server is no longer the best use of our resources.

The links to the team chat pages from the Make homepage have already been removed, and we’ll remove the individual chat pages when the server has shut down.

Thanks to everyone who participated in this effort, especially @ashfame and @psrpinto, but also everyone who helped surface issues with the implementation.

Thank you for your understanding and support. If you have any questions or need help transitioning, please don’t hesitate to comment below.

Mary Hubbard 6:49 pm on November 18, 2024  

Hello, WordPress Community – Let’s Chat!

I’m thrilled to share my first post here on Make WordPress! As the new Director of the WordPress Project, I’m excited to contribute to the ongoing work that shapes WordPress for millions worldwide. I also recognize the challenges ahead and the large shoes I’m stepping into.

Over the last two weeks, I’ve had the privilege of engaging in discussions with a variety of folks from across the community, hearing valuable ideas and some concerns. These conversations have provided great insights, and I’m eager to start diving deeper into the work ahead.

To foster continued open dialogue and collaboration, especially as I ramp up, I’ve scheduled office hours with Matt and myself. This will be a space to connect, share thoughts, and ask questions.

This will be an evolving format, especially to allow for different timezones, and of course I’m open to feedback—looking forward to continuing the conversation!

Let’s build something amazing together.

When: Friday, November 22nd, 10:45AM PST
Where: Zoom Link here
Duration: 1 Hr

Full meeting recording: it can be found here.
Josepha 7:40 pm on August 19, 2024
Tags: training, tutorials, YouTube   

Ramping up WordPress on YouTube

YouTube has become an essential platform for sharing complex ideas with a diverse audience, and our WordPress YouTube channel is no exception. Since 2023, we’ve experienced a 6x increase in monthly views and engagement, driven by the growing availability of WordPress content. Since October 2022, when WPTV content began syncing automatically with YouTube, to the design iterations in 2023 and our participation in the Nonprofit YouTube Partner Program—removing ads from our videos—our channel has become a trusted source of information and inspiration.

In keeping with our commitment to meeting the needs of both current and future users, I’m excited to announce that Jamie Marsland will be taking on the management of the WordPress YouTube channel. Jamie’s extensive experience in the WordPress community and his passion for empowering creators through this medium makes him the ideal person to lead our efforts in expanding and enhancing our YouTube presence.

With over a decade of experience working with WordPress and training others, Jamie brings a wealth of knowledge and expertise to this role. He will oversee the creation of high-quality content, ensuring our channel remains a valuable resource and a source of inspiration for WordPress enthusiasts worldwide while inspiring and empowering other 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. content creators to further the movement.

For those attending WordCamp US, say hello to Jamie in person! And for everyone else, please join me in welcoming him to this new role as we embark on an exciting new chapter for WordPress on YouTube.

#training, #tutorials, #youtube

Angela Jin 4:05 pm on May 13, 2024  

Let’s try out online DEIB course content!

The WordPress community has long advocated for diversity, equity, inclusion, and belonging (DEIB) training. Over the years, teams have explored various avenues, usually engaging diversity consultants. While this has been a valuable experience, extending such training to our vast and diverse community has been challenging, given our global community and the many timezones we cover. 

Today, I am excited to share that Automattic has added 100 licenses to their Paradigm Reach account for WordPress community members. While this isn’t a full solution, I am optimistic that it is a step in the right direction. Paradigm Reach offers a comprehensive suite of online coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. workshops, microlearnings, and resources created by professional experts from around the world. Their platform allows for customization of learning content for users. 

Some recognized limitations and future hopes

In reviewing Paradigm Reach, there are a few limitations I’d like to note. Firstly, only 100 licenses are available. However, the licenses can be reassigned, meaning that when a contributor completes assigned courses, their access can be removed and granted to another contributor. Second, because the usual audience for Paradigm Reach tends to be businesses and employers, some of the examples used are in a more corporate or work setting. However, the content itself is still valuable and principles can be applied to collaboration and engagement in the WordPress community. Lastly, the content is in English, and there are no translations of the material. 

While these limitations are very real, I still believe there is a net positive in introducing Paradigm Reach and that it will help the WordPress community get to a more conscientious and equitable future state. My hope is that through this initial online training, enough community members around the world are able to participate in high quality and consistent DEIB training, and begin to build shared language and understanding around DEIB. Then, a working group of members who have participated in this training can leverage what they have learned to create online DEIB training specifically for the WordPress contributor community, which can be translated and made available at any time, to any one. 

Some more immediate next steps

For starters, it makes sense to try out two courses, an “Intro to DEIB” and an “Advanced DEIB” course. Because the licenses are limited, I’d like to invite the following contributor groups to try out this async training:

  • Contributors who mentor or guide other contributors, like mentors for the Contributor Mentorship Program
  • Contributors who handle sensitive mediation work, like Incident Response Team (IRT) Members (all IRT members are required to complete DEIB training)
  • Contributors who communicate with large, international audiences, like Flagship event organizers
  • Contributors who want to provide DEIB training to others, like DEIB working group leaders
  • Contributors who have never experienced DEIB training previously

While the content should take no more than 3 hours to complete, participants will be given 8 weeks to finish assigned courses. Participants will also be asked to provide feedback on the content and recommendations for improvement. 
If you are interested in taking online DEIB training through Paradigm Reach, please fill out this form. Have questions or comments? Leave those in the comments below!