Skip toolbar
WordPress.org

Make WordPress

Teams

  • Core

    The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team makes WordPress. Whether you’re a seasoned 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. https://www.php.net/manual/en/index.php, 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., JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com or CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. developer or are just learning to code, we’d love to have you on board. You can write code, fix bugs, debate decisions, and help with development.

  • Design

    The design group is focused on the designing and developing the user interface. It’s a home for designers and UXers alike. There are regular discussions about mockups, design, and user testing.

  • Mobile

    The mobile team builds the iOSiOS The operating system used on iPhones and iPads. and Android apps. Lend them your Kotlin, Swift, or ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org Native skills. The team also needs designers, 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. experts, and testers to give users a smooth experience on every device.

  • Accessibility

    The a11yAccessibility 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) group provides 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) expertise across the project. They make sure that WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and all of WordPress’ resources are accessible.

  • Polyglots

    WordPress is used all over the world in many different languages. If you’re a polyglot, you can help by translating WordPress into your own language or contributing to the GlotPress project, making translations easier and more effective for everyone.

  • Support

    Answering questions in the support forums, IRC, or 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/ is one of the easiest ways to start contributing. Everyone knows the answer to something! Since the forums run on bbPress, you can also contribute by helping make the software behind them even better.

View all teams and their meetings

Latest activity

See the latest happenings across the entire project.

Erick Wambua Test ·

Test Team Chat Agenda: 19th November, 2026

Here is the agenda for the upcoming Test Team Voice Chat scheduled for Thursday, 19 November at 18:00 GMT+3, which will be held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#core-test, #test-chat-agenda

Jonathan Desrosiers Core ·

Reorganizing Trac Notifications in Slack

For as long as the WordPress project has used 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/, wordpress.org has fed notifications for every new ticketticket Created for both bug reports and feature development on the bug tracker. from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and every commit to develop.svn.wordpress.org into the #core channel to keep contributors aware of contributor activity. This practice also extends to the individual component channels (for example, #core-media) using the Component ticket field and a list of relevant file paths, and some channels even subscribe to activity on relevant 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 by the repository owner. https://github.com/ repositories.

This has worked well for over a decade. But recently it’s become clear that the volume of activity is untenable. Channels meant for discussions now function as pseudo-firehose channels. Important discussions become difficult to find and easy to miss entirely, and many contributors have expressed that they are unable to keep up or follow along.

Given this, it’s time to rethink how Trac & GitHub notifications are posted in Slack.

What has changed?

As of r15625-meta, the following changes have been made to Trac notifications in Slack:

  • Individual #core-{component} channels no longer receive commit notifications. These are now fed into #core-{component}-commits.
  • Individual #core-{component} channels no longer receive new ticket notifications. These are now fed into #core-{component}-newtickets.
  • New #core-{component}-firehose channels have been created and serve as a true firehose for all activity directly belonging to the component (new tickets, commits, and all comments on tickets with Component set to the matching value).
  • Commit notifications in #core remain, but now only show the first line (short description) of each commit message.
  • New ticket notifications in #core are unchanged.
  • New #core-gutenberg-firehose, #core-gutenberg-commits, and #core-gutenberg-newtickets channels have been created and are subscribed to the corresponding activity from the WordPress/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/ repository on GitHub.
  • With the new #core-gutenberg-* channels, #core has been unsubscribed from WordPress/gutenberg commit notifications.
  • #core-editor-commits has also been unsubscribed from WordPress/gutenberg commit notifications and will now only show Editor component commits from develop.svn.wordpress.org. Join the #core-gutenberg-commits channel for the activity previously found here.
  • The behavior for individual focuses that do not overlap with a component (for example, rest-api focus and REST API component) is unchanged:
  • Focuses that double as components continue to post new ticket notifications to the main channels (multisite, privacy, and rest-api), but commits now only appear in the new -commits and -firehose channels.

The goal of these changes is to create targeted feeds that give contributors more control, allowing someone to follow or subscribe only to the specific activity streams that are relevant to them without drowning out discussion-based activity.

Were these channels created for every component?

Yes. -firehose, -newtickets, and -commits channels were created for every component, including those where the main channel had never existed. Main #core-{component} channels that didn’t already exist were not created. These channels were also created for components with an archived #core-{component} channel, which was left as archived.

What about subcomponents?

The notifications for each subcomponent have been configured to flow into the three channels belonging to the parent component, unless the subcomponent has its own channel. For example, the Notes subcomponent has #core-notes, so #core-notes-newtickets, #core-notes-commits, and #core-notes-firehose have been created.

What about other #core-name channels that do not map to a component?

Channels such as #core-test and #docs are not a part of this effort; only channels that explicitly belong to a component have been updated. More channels can be updated to follow the same pattern in the future wherever it makes sense. If a non-component-mapped channel has a need for a -newtickets, -commits, and -firehose channel, then please comment below for further assistance.

What about GitHub Activity?

These new channels are meant to only contain Trac/SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. activity. As noted above, #core has been unsubscribed from the WordPress/gutenberg commit notifications because commits from that repository were drowning out important discussions.

Should component maintainers decide that a GitHub repository’s activity is important for their contributor group to follow, new notification channels can be considered. If a component you maintain would benefit from this, please comment below with the changes needed.

What about the pre-existing firehose channels?

The #core-firehose, #core-newtickets, #core-commits, #core-ci-firehose, and all non-CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. firehose channels (e.g. #meta-firehose, #glotpress-firehose, etc.) have not been modified and will continue to function as they always have.

Why does #core-gutenberg-newtickets show open and close activity for issues?

The GitHub Slack integration does not currently support filtering issues notifications by action (opening or closing), so the channel has been subscribed to both for now. This could be set up using GitHub Actions, but that can be a follow up item if necessary.

AI is a Trac component. Why does #core-ai-firehose contain GitHub Activity?

Currently, a large amount of the AI-related work merged into Core is built out in several different repositories maintained on GitHub. The pre-existing subscriptions in this channel have been left as is for the time being.

Can I follow several components at once?

Yes! Because these are Slack channels, you are able to follow as many as you’d like. You can even follow new tickets for one component and commits for another.

Feedback

As always, none of these changes are permanent and adjustments can be made based on community feedback. Please share any you may have below!

A full list of channels created as a part of this change can be found in the collapsed details 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. below.

All Created Channels

Props @jeffpaul, @jorbin, @westonruter for pre-publish review, and @obenland for help on the 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. side.

#slack

Junko Nukaga Community ·

Proposal: An opt-in attendee list for sponsors at WordCamp Asia 2027

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. Asia 2027 team would like to try something new: an opt-in attendee list as a sponsor benefit, so attendees can choose to connect with sponsors before and during the event. This is a one-event pilot. We will measure the results and update the handbook based on what we learn.

Today, the handbook says attendee data cannot be shared with sponsors, so we want to discuss this openly with the community first.

A good moment to try new things

The web is changing fast, and so are our events. Sponsors tell us they want real conversations with agency owners and decision makers. Many attendees also come to WordCamp to find clients, partners, jobs and tools.

Right now, we cannot help these people find each other. Most tech conferences already offer this. We believe we can offer it in our own way: open, transparent, and always the attendee’s choice.

What everyone gets

  • Attendees: a chance to meet the sponsors they care about during the event, and to hear about tools, services, and business opportunities.
  • Agencies and freelancers: a better chance to meet companies that want to work with the WordPress ecosystem.
  • Sponsors: clear value and a reason to keep supporting WordCamps.
  • The community: stronger sponsorship helps keep tickets affordable and supports scholarships and community programs.
  • Other WordCamps: real data from one event, so future flagships and local WordCamps can decide what works for them.

Simple and attendee-first

  • Attendees choose. One unticked checkbox, separate from the ticket. It is never a condition to attend.
  • Before the event, once the sponsor list is final, attendees see the list of sponsors and choose to share only their name, email, and organization. Sponsors can then invite them to meet during the event.
  • Only the top three sponsor tiers take part.
  • Attendees can withdraw at any time.

How we protect attendees

Before any list is shared, each sponsor signs a data sharing agreement with us. @harmonyromo has offered to help us prepare this agreement.

  • If an attendee replies and starts a conversation, the sponsor may keep that contact under its own privacy notice. All other data must be deleted within six months of the event.
  • Sponsors cannot share the list, upload it to advertising platforms, or add people to newsletters or marketing sequences.
  • Sponsors can use it only to contact attendees about their own products and services, as shown when attendees opt in.
  • The agreement is designed to meet GDPR-level standards and applicable local laws.
  • 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/ privacy policy will say that sharing with sponsors is possible.
  • We keep a record of the data processing and a real privacy contact address.
  • Sponsors that break the data sharing agreement lose eligibility for future WordCamp sponsorship.
  • Attendees can withdraw with one click, even after the list is shared. We will tell the sponsors, and they must delete the data within five business days.

Once data is sent, we cannot see how it is used or pull it back. We rely on the signed agreement and its consequences. If something goes wrong, we will act and tell the affected attendees.

How we will learn from it

We will look at:

  • the opt-in rate
  • withdrawals and complaints
  • attendee feedback
  • sponsor feedback and results

After the event, we’ll share the results here. If the pilot works, we’ll propose a handbook update.

Share your feedback

We would love your ideas:

  • How can we make this valuable for both attendees and sponsors?
  • What would make you comfortable to opt in?
  • Have you seen this done well at other events?

Please share your thoughts in the comments. Let’s try something new together!

This idea comes from many people working together. A special thank you to @karenalma for shaping this plan, and to @harmonyromo for offering to help with the legal and privacy side. Thanks also to @adityakane and @malgra for their careful reviews and comments, to @unintended8 and @4thhubbard, and to my fellow WordCamp Asia 2027 leads @wpwebhost, @julians3, and @onealtr and our sponsor team for their ideas and support along the way.

#wordcampasia, #wordcamps

George Mamadashvili Core ·

Miscellaneous Editor Changes in WordPress 7.2

In this post, you will find dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for smaller changes to the editor in WordPress 7.2.

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. Editor

Removed __experimentalGroup prop from InspectorControls

WordPress 7.2 removes the __experimentalGroup prop from InspectorControls and InspectorControls.Slot. Use the group prop instead. (#83171)

The prop was stabilized as group in WordPress 6.2 (#47105). Since then, passing __experimentalGroup logged a deprecation warning that named WordPress 6.4 as the removal version. WordPress 7.2 completes that removal.

Code that still passes __experimentalGroup now renders its controls in the default group, with the block’s other settings. For example, controls meant for the Advanced panel now appear outside it. A ToolsPanelItem meant for a panel such as Typography renders without that panel around it.

To update, rename the prop. The group prop works in WordPress 6.2 and later, so no version check is needed:

// Before
<InspectorControls __experimentalGroup="advanced">
	<TextControl label={ __( 'Custom ID' ) } value={ id } onChange={ setId } />
</InspectorControls>

// After
<InspectorControls group="advanced">
	<TextControl label={ __( 'Custom ID' ) } value={ id } onChange={ setId } />
</InspectorControls>

For the Advanced panel, InspectorAdvancedControls is also available and sets group="advanced" for you.

References:

Deprecated __experimentalImageEditor component: stylesheet moved

The @wordpress/block-editor npm package and the wp.blockEditor global export an __experimentalImageEditor component for building image cropping and editing interfaces. The component was deprecated in WordPress 7.1, so avoid using it.

If your code still uses it, note a CSSCSS Cascading Style Sheets. change in WordPress 7.2. The component’s stylesheet was incorrectly defined in the @wordpress/block-library package. In 7.2 it moves to @wordpress/block-editor. Update any imports of the stylesheet to the new location.

References:

Additional CSS now applies to blocks rendered by a parent block

Starting in WordPress 7.2, Additional CSS (set in a block’s Advanced panel) works for blocks that a parent block renders itself, such as a Navigation Link inside a Navigation block.

Before, that CSS was missing on the front end. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. generated it only for blocks in a parent’s regular inner content. The Navigation block loads its inner blocks from a navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. post, so those blocks skipped that step.

Now the CSS is generated when each block renders, however its parent loaded it. Blocks that already worked are unaffected, and their CSS is not duplicated.

No code changes are needed. Rules that were previously ignored will now apply, so check for any you don’t want.

References:

Core Data

registry.subscribe no longer listens to all stores when the store is not registered yet

Starting in WordPress 7.2, registry.subscribe( listener, storeName ) is more efficient when storeName isn’t registered at the time of the call.

Previously, the listener was attached to the registry-wide listener list, so it ran on every update from every store, both before and after the target store was registered. Now the registry keeps it as a pending listener and connects it to the store once it is registered, so the listener only runs for updates from that store.

Subscribing before a store is registered works as before, and the returned unsubscribe function still works. No code changes are needed. Code that relied on such a listener firing for unrelated stores will see fewer calls, but this was never documented behavior.

References:


Props to @aaronrobertshaw, @ramonopoly, @annezazu, @jsnajdr, @scruffian for content.

#7-2, #dev-notes, #dev-notes-7-2

Krupa Nanda Accessibility ·

Accessibility Team Meeting Agenda: November 19, 2026

This is the proposed agenda for the bi-weekly 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) Team meeting on Thursday, November 199, 2026 at 08:30 PM GMT+5:30

📣 Announcements

Working groups

  • WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the 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. Editor
  • Accessibility-ready Program
  • Documentation about Web Accessibility

Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub is every Tuesday at 16:00 UTC, held in the #accessibility channel on the Make 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/ (registration required).

#accessibility, #agenda

Pooja Derashri Community ·

Monthly Education Buzz Report – October 2026

Welcome to the Monthly Education Buzz Report, your go-to source for highlights and updates on the WordPress Campus Connect, WordPress Credits, and WordPress Student Club education initiatives within the WordPress community. This report celebrates, promotes, and informs people across the WordPress community and beyond about the diverse educational efforts underway.

WordPress Campus Connect

[TBD: one-line October headline.] WordCamp CentralWordCamp Central Website for all WordCamp activities globally. https://central.wordcamp.org includes a list of upcoming and past camp with links to each. lists 15 Campus Connect events held in October across Bangladesh, India, Indonesia, and Costa Rica. Campus Connect now makes up 79 of the 154 community events on the 2026 calendar, according to the Community Events dashboard.

87

Completed Events

105

Participating Institutions

8355+

Students Reached

Ajmer reaches five colleges

WordPress Campus Connect Ajmer 2026 has now completed five partner colleges: Shri RK Patni Girls College (Kishangarh), Government Mahila Engineering College, Star Infotech College, Engineering College Ajmer (hands-on workshop on October 17), and Aryan College. Each college got a pre-session seminar, then a hands-on workshop where students built their first WordPress site and redeemed free hosting and domain credits live. Several colleges also ran advanced WooCommerce tracks.

Lead organizer Bhupendra Singh Shekhawat thanked the WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ Education team for domain and hosting support, which he called the single biggest factor in making the sessions meaningful. Pooja Derashri supported as a mentorEvent Supporter Event Supporter (formerly Mentor) is someone who has already organised a WordCamp and has time to meet with their assigned mentee every 2 weeks, they talk over where they should be in their timeline, help them to identify their issues, and also identify solutions for their issues., along with Anand Upadhyay, Hardik Sharma, Satish Prajapati, Hemant Tejwani, Gajendra Singh, Aman Raj Sain, Richa Shrivastava, and Stuti.

Hackathons instead of talks in Bangladesh

In Dhaka, @devmuhib ran a hackathon-format pilot at Stamford University Bangladesh after noticing how much students there like challenge-based activities. WordPress.com provided the domain and hosting for wphackathon.com and offered free domain and hosting to up to 100 participants. Read more in a community blog post.

The format spread. At WordPress Campus Connect Rajshahi 2026 at Varendra University (October 14), about 90 students built about 57 websites in a hands-on hackathon, and interested students applied for WordPress Credits. The organizers now plan to grow the university’s student club. At Presidency University, Dhaka, a two-day Campus Connect ended with 50 websites and 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/ profiles. Full recap on WordCamp Central.

Kolhapur: a team that runs without its leads

Makarand Mane’s Kolhapur team ran two more events. Campus Connect #3 at Dr. D. Y. Patil Polytechnic (October 3) had 59 of 60 registered students attend, run by two organizers and volunteers while four organizers were at 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. Rajasthan. Digvijay Zite coordinated with the college and facilitated. Campus Connect #4 at Dr. Bapuji Salunkhe Institute of Engineering and Technology (October 17) had 56 of 78 registered students attend. The team split students across three labs with three facilitators, Digvijay Zite, Makarand Mane, and first-time facilitator Harshad Dhale. Smaller groups of 20 to 25 made it much easier to give each student attention, a useful lesson for colleges with limited lab space.

Campus Connects held in October

  • Kolhapur, India: Dr. D. Y. Patil Polytechnic (October 3), 59 students; BSIET (October 17), 56 students.
  • Rajshahi, Bangladesh: Varendra University (October 14), about 90 students, about 57 websites, organized by Nazmul Hosen.
  • Puttar, India: Shodhan and four facilitators Ashwini, Nishmitha, Venu, Chethan) ran a two-day workshop at Sacred Heart College (October 15 to 16). Students received Campus Connect badges and printed certificates.
  • Ajmer, India: Engineering College Ajmer (October 17) and Aryan College completed the five-college series.
  • Dhaka, Bangladesh: Presidency University, two days (around October 25), 50 websites. Stamford University hackathon pilot.
  • Tegal, Indonesia: WPCC TCS Tegal (October 25), with @kharisulistiyo facilitating the hands-on workshop.
  • WordCamp Sylhet, Bangladesh: @chaion07 hosted an Education Table on October 2, Contributor’s Day at WordCamp Sylhet 2026.
  • WordCamp Rajasthan happened on October 3 & 4 with an Education Table on Contributor’s Day, led by Makarand Mane.

Program updates

  • Online-only institutions: Kaito asked how to support an online-only university, since Campus Connect is an in-person format. @peiraisotta had a similar case, and Rocío Valdivia proposed an exception in the guidelines for institutions that are 100% online, so in-person campuses keep the in-person format. @webtechpooja agreed and offered to update the guidelines. Kaito will test an online Campus Connect and report back on student engagement.

Planning your own event? Join the #campusconnect 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.

WordPress Credits

As of the November 1 monthly snapshot, the program counts 52 partner institutions, 370 graduates,743 WordPress sites created, and 517 first contributions made. The live dashboard shows 1042 students joined to date across 17 countries, contributing to18 WordPress teams, with an 88% graduation rate and 80% of graduates recommending the program.

Sponsorship tiers for 2027

On October 22, @peiraisotta published WordPress Credits is opening sponsorship tiers. The program will pilot tiers in 2027, from in-kind “Friend” support up to a “Partner” tier at $30,000+ per year. Current sponsors will be contacted directly to choose a tier.

The new Partners page and sponsor application form went live on the Education Hub the same week, with five levels: Friend, Supporter, Backer, Champion, and Partner. Sponsors can now manage their offers and codes, which students claim directly on the site.

Student-led highlights

  • A Campus Connect as a Credits project: WordPress Campus Connect Universidad Fidélitas 2026 is the WordPress Credits contribution project of three students, @nicolegomez, @yiqi10, and @gabrielrc, with Nicole as Lead Organizer, was a great event.
  • One graduate, four teams: a student mentored by Nazmul Hosen finished the 150-hour course with 20 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. patterns, 32 photos in the Photo Directory, 402 translations, and the website design for WordPress Youth Day Nicaragua, from Figma to the live site.
  • High school translators: students from Liceo Experimental Bilingüe José Figueres Ferrer visited Universidad Fidélitas on October 1 and set their project: translating 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. into Costa Rican Spanish. The school is now discussing adding the program to its International Baccalaureate curriculum.
  • Photos from Costa Rica: several new Fidélitas students chose the Photos team, contributing environmental and landscape photography.
  • Testing the AI-Powered WordPress course: students were invited to complete the course with different AI tools and compare the experience, counted as a contribution to the Training team. The feedback form is live; if you have completed this course, we would be glad to collect your feedback.

New cohorts and partners

  • Fidélitas, Costa Rica: the largest intake of the month. Dozens of new students introduced themselves in #wpcredits through October, alongside students from Colegio Universitario de Cartago.
  • Universidad del Valle, Nicaragua: the first Nicaraguan university in the program, starting with an Intro to contribution course (50-hour) pilot while the course is added to its curriculum.
  • Indonesia: Institut Teknologi Tangerang Selatan (ITTS) started a cohort of 13 students on the WPCredits Foundation course. Universitas Muhammadiyah Purwokerto (UMP) signed its agreement and enrolled 5 students in Foundations.
  • Europe: New students from the University of Bologna, University of Pisa, Politecnico di Bari, and the School of Arts in Zaragoza. A University of Pisa graduate will present the program at WordCamp Pisa. Haaga-Helia University (Finland) got its own 100-hour Foundations track.
  • More new students: Unifranz (Bolivia), Kishoreganj Polytechnic Institute (Bangladesh; a student who first heard about Credits at a Campus Connect, graduated, and is now actively mentoring new students), and new arrivals from Uganda and India.
  • D. Y. Patil School of Engineering and Management, India: 30 students are actively continuing the internship.
  • CUC, Costa Rica: interns started on the Developer Track, building features for the program’s own platform as their contribution project.

MentorsEvent Supporter Event Supporter (formerly Mentor) is someone who has already organised a WordCamp and has time to meet with their assigned mentee every 2 weeks, they talk over where they should be in their timeline, help them to identify their issues, and also identify solutions for their issues.

  • 6 new mentors joined the mentor team. More people from Pakistan, Latvia, and Spain started the Mentors course, and we added 1 WP Credits Program managerProgram Manager Program Managers (formerly Super Deputies) are Program Supporters who can perform extra tasks on WordCamp.org like creating new sites and publishing WordCamps to the schedule. to the program.

Courses and tracks

  • Two courses moved to the Education Platform with autograding: WordPress Credits Foundations replaced the original 150-hour course on October 1, and WordPress Credits: Intro to Contribution replaced the 50-hour course on October 12. Students use a Student Report Card on the Education platform, and once it is complete, they get a code that unlocks their certificate.
  • Developer Track support: @alanabwarner published a guide for mentors without CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. experience and updated the final lesson to point students to Good First Bugs on Core TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. and good first issues on 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/. @celigaroe asked the Core team to review the track, and @Ryanwelcher offered to record a video for students.
  • Polyglots videos in Spanish: @roblesloaiza published two WordPress.tv videos on contributing subtitles and contributing to translation.
  • Coming next: the Translation Track is being connected to the platform, and a Social Impact (NGO) program is in review for a pilot with Fidélitas students. Two draft courses explore lessons built with WordPress Playground.

Platform and outreach

WordPress Student Clubs

The baseline audit of all recognized clubs, proposed by @devmuhib in September, was set to start in October.

  • Government Mahila Engineering College, Ajmer: a new peer-learning WordPress Student Club began under the college’s Training and Placement Cell, led by student coordinators Sakshi Bhiryani and Chahat Chouhan (3rd year, CSE) with support from WordPress Community Ajmer. Sessions so far: website basics (October 22), WordPress Studio and the dashboard (October 26, online), and day one of a two-day portfolio website build led by Richa Shrivastava, 4th-year CSE (October 27).
  • Varendra University, Rajshahi: after their October 14 Campus Connect, organizers plan regular learning sessions to keep the university’s student club active.

Other Happenings

Get Involved

Education Initiatives

WordPress Education offers three practical ways for learners to develop skills, gain practical experience, and build confidence as 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. contributors.

See something in the community that should be noted here or in a future newsletter? Comment below!

Stay tuned for next month’s update!

#campus-connect, #education-buzz, #wpcredits

Amy Kamala Hosting ·

Hosting Team Meeting Agenda 11-18-2026

Next Meeting

The next meetings will be in the #hosting 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 on Wednesday, November 18, 2026 at 0900 UTC and Wednesday, November 18, 2026 at 1800 UTC. Hope to see you there!

Agenda

Anything else? Please leave a comment with any additions or suggestions for the meeting.

Props to @jazzs3quence for the pre-publish review!

#agenda, #hosting-community, #meetings, #weekly-hosting-chat

Isabel Brison Core ·

API for style state-aware block styling controls

Custom 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. controls can now make use of the responsive and pseudo state styling system in the block editor. To implement this, controls for editing styles need to read and update the block’s style attribute for the state selected in the editor. 7.2 exposes a public 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. for this.

The following hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. and selectors from @wordpress/block-editor work with both viewport and pseudo states:

getSelectedBlockStyleState reads the selected state;
hasSelectedBlockStyleState checks whether a non-default state is selected;

getStyleForState Returns the style object for the selected state;
setStyleForState Sets the new style on the selected state.

import {
    getStyleForState,
    setStyleForState,
    store as blockEditorStore,
} from '@wordpress/block-editor';
import { useSelect } from '@wordpress/data';

const selectedState = useSelect(
    ( select ) =>
        select( blockEditorStore ).getSelectedBlockStyleState( clientId ),
    [ clientId ]
);

const stateStyle = getStyleForState( attributes.style, selectedState ) || {};

setAttributes( {
    style: setStyleForState( attributes.style, selectedState, {
        ...stateStyle,
        dimensions: {
            ...stateStyle.dimensions,
            minHeight: '50vh',
        },
    } ),
} );

Displaying controls in the toolbar and inspector

By default inspector controls are hidden when a style state is selected. To display custom controls in the inspector when a viewport or a pseudo state is enabled, the style-state slot is available:

<InspectorControls group="style-state">
    <MyStyleStateControl />
</InspectorControls>

To display custom controls in the block toolbar when a viewport state is enabled, there is also a style-state slot:

<BlockControls group="style-state">
    <MyViewportControl />
</BlockControls>

(The default block toolbar slots aren’t currently hidden for pseudo states.)

Obtaining media query strings

For viewport state integrations that need media query strings, @wordpress/global-styles-engine also exports getViewportMediaQueries:

import { getViewportMediaQueries } from '@wordpress/global-styles-engine';

const mediaQueries = getViewportMediaQueries( {
    mobile: '480px',
    tablet: '782px',
} );

// {
//   '@mobile': '@media (width <= 480px)',
//   '@tablet': '@media (480px < width <= 782px)',
// }

Calling getViewportMediaQueries with no parameters will return the default coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. media queries (with 480px for mobile and 782px for tablet).

PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher code can use the corresponding wp_get_viewport_media_queries helper:

<?php
$media_queries = wp_get_viewport_media_queries(
    array(
        'mobile' => '480px',
        'tablet' => '782px',
    ),
    array(
        'include_desktop' => true,
    )
);

// Includes @mobile and @tablet, plus:
// '@desktop' => '@media (width > 782px)'

Calling wp_get_viewport_media_queries with no parameters will return the default core media queries (with 480px for mobile and 782px for tablet).
include_desktop defaults to false.

See the block editor data reference and 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/ PR #82741.


Props to @andrewserong, @aaronrobertshaw and @talldanwp for review.

#7-2, #dev-notes, #dev-notes-7-2

Jb Audras Core ·

Dev Chat Agenda – November 17, 2026

UPDATE: due to the 7.1.5 release, the weekly devchat has been postponed to Thursday, November 19, 2026, at 15:00 UTC.

The next WordPress Developers Chat will take place on Wednesday, November 18, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting focuses on upcoming releases and CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development, with time for discussions and open floor.

If you have requests for help with a ticketticket Created for both bug reports and feature development on the bug tracker. or another discussion topic, please post details in the comments section at the end of this agenda, or bring it up in Dev Chat during open floor.

Announcements 📢

WordPress 7.2

General

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

Open floor  🎙️

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

#7-2, #agenda, #core, #dev-chat

Dennis Snell

Proposal: Disable WPCS UsedPropertyNotSnakeCase rule.

This rule rejects property accesses for properties not named in snake_case, but readers generally have to accept whatever objects are passed into them.

It’s debatable how properties should be defined, but we should not encourage developers to break code on property access. Adding additional property names to the exclusion list is a never-ending catch-up game after the linter has required defective code as well.

I would like to discuss setting <severity>0</severity> for this rule so that we can avoid either requiring people to either write broken code or pollute the codebase with fragile phpcs:disable comments.

Reply

Marius L. J. Core ·

Preparing for jQuery 4 with WordPress 7.2

The last major jQuery update in WordPress was to version 3 back in 2020, and was a process carried out over multiple releases, with the final step culminating in the disabling of jQuery Migrate by default (this final step was never finalized at the time).

WordPress 7.2 will ship with jQuery Migrate 3.6.0 to prepare for updating to jQuery 4 in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Doing so will help extenders catch deprecation notices in their code for features that may no longer be available in jQuery 4.

The planned process is currently:

  • Update jQuery Migrate in WordPress 7.2
  • Update to the latest release of jQuery and jQuery Migrate tentatively planned for WordPress 7.3 depending on test results. Updating to the latest jQuery UIUI User interface and other libraries dependent on jQuery is also planned for 7.3.
  • Disable jQuery Migrate by default at the end of 2027 (WordPress 7.5 or 7.6, depending on the release cadence for next year), this is also dependent on testing and research into the potential impact on the ecosystem.

You can follow the progress of updating to jQuery 4 in #60478


Props to @davidbaumwald and @pbiron for copy review.

#7-2, #dev-notes, #dev-notes-7-2, #jquery

BackuPs

I found a jquery 4.0 issue in wordpress 7.2 running jQuery Migrate 3.6.0

  Uncaught SyntaxError: import declarations may only appear at top level of a module jquery.form.js:22:1

Reply

Not sure which team to contribute to?

Check out our contributor wizard and find how to get started.