WordPress Contributor Toolkit 2.0, released on October 23, 2026, brings a redesigned interface, translations into ten languages and an installed size about 350 MB smaller. For people preparing a Contributor Day or looking to work on Core or Gutenberg, the update makes the app easier to set up and use without changing its existing contribution workflows.
The Toolkit is designed to help new contributors work on WordPress without first installing Git, Node.js, npm or Docker. Version 2.0 focuses on the app’s interface, settings, localization and smaller practical fixes, rather than adding a new contribution process.
In short: The [WordPress Contributor Toolkit 2.0 release](https://make.wordpress.org/core/2026/10/23/wordpress-contributor-toolkit-2-0-a-redesigned-app-in-your-language/) keeps the Core and Gutenberg workflows introduced in earlier versions. It adds a WordPress Design System interface, configurable settings, ten interface languages and clearer file-change controls. Contributors can download the app and try it on a real ticket or issue.
What WordPress Contributor Toolkit 2.0 changes
The October 23 announcement describes version 2.0 as a redesign built on the WordPress Design System. The changes cover the app window, including its sidebar, page header, site details, cards, dialogs and bottom tray. People familiar with the block editor should recognize the buttons, notices and dialogs.
Several smaller interface changes address common tasks. The sites list now shows each site’s server status beside its name. Tray buttons have text labels rather than icons alone, warning notices make the next action easier to spot, and the Trac window follows the app’s theme.
These are practical improvements for someone switching between local sites and tickets. Seeing a server’s status in the list, for example, can save a trip into the site details just to check whether it is running. The announcement describes the change, but does not claim a measured time saving.
Settings now cover language, sites and accounts
Version 2.0 adds a settings dialog that can be opened from the app’s cog or the operating system’s app menu. Its General section includes theme and language choices, startup behavior for a site’s server and build watch, whether running processes restart when the app opens, and the default folder for new sites.
The Sites section lets users set the PHP version for each development server and configure the WP_DEBUG and SCRIPT_DEBUG flags. The new values apply when that server starts again, and site details show the settings that will be used on the next start.
An Account section stores the WordPress.org username and event, which are used in a patch handed to a mentor, along with the GitHub account the app uses to open pull requests. The theme can follow the operating system, use light or dark mode, or use a custom background and primary color.
Ten languages, with more possible
The Toolkit’s interface is now translatable, including setup, ticket notices, the review-and-submit flow, the pull request form, terminal and log output, and the app’s own menus and dialogs. Version 2.0 includes Czech, Dutch, English (Canada), English (UK), Galician, Hungarian, Lao, Polish, Serbian and Turkish.
The app follows the operating system’s language by default. Users can select another available language in Settings and relaunch when prompted. A translation is included once it reaches at least 80% completion on translate.wordpress.org, so contributors can help expand the list by translating the Toolkit itself.
That threshold gives a clear route for languages that are not included yet: translation work is itself a contribution. It also means the release’s language list is specific to version 2.0, not a promise that every language is already available.
File changes are easier to review and undo
After a contributor applies a patch or checks out a pull request, site details now show changed files in a folder tree. The app separates files touched by the patch or pull request from other files changed on that ticket. A pencil marks files the contributor has edited since applying the change.
Clicking a file opens it in the user’s editor. Each changed file has its own revert control, so a contributor can undo one experiment without removing the patch being tested. The separate “Discard your changes” action removes the contributor’s work while leaving the applied patch or pull request in place.
The app also keeps Trac ticket details after they are read. A reopened Toolkit still shows the ticket’s summary, status, type, component, milestone and keywords, alongside when the information was fetched. A refresh button can retrieve the latest details.
A smaller download for Contributor Days
The release cuts the installed app size by about 350 MB. According to the announcement, the package no longer includes PHP builds the app does not load, libraries already bundled into the interface, or Chromium language files for languages without an app translation.
The reduction is relevant when a group downloads the Toolkit over the same network at a Contributor Day. The announcement identifies that setting as a reason for the smaller package; it does not provide a download-time benchmark.
Other listed fixes include testing Application Passwords over HTTP in local sites, opening the correct database when SQLite storage is randomized or a custom DB_PATH is used, and stopping the debug.log pane from duplicating a line or replaying the full file after an edit. The pull request preview also avoids listing trunk files when the local trunk is behind.
What contributors should do next
Core and Gutenberg workflows work as they did in version 1.2, according to the release post. The update changes the surrounding experience and adds tools for settings, translations and reviewing local edits, but the source does not announce a replacement workflow.
Contributors can download version 2.0 and test it against a real ticket or issue. If something breaks, the project asks users to open a GitHub issue with the steps and outcome; translation corrections can be submitted through translate.wordpress.org.
FAQ
What is new in WordPress Contributor Toolkit 2.0?
Version 2.0 adds a redesigned interface, a settings dialog, ten languages, clearer changed-file controls and a smaller installed size. The Core and Gutenberg contribution workflows remain the same as in version 1.2.
Does the Toolkit 2.0 release change how contributors submit patches?
No workflow change is described in the announcement. The Core and Gutenberg workflows continue to work as they did in version 1.2.
How can I help translate the Contributor Toolkit?
Contributors can work on the project through translate.wordpress.org. A language is included with the app after it reaches at least 80% translation completion.
Download the Toolkit 2.0 release and test it on a real Core or Gutenberg ticket before using it at your next Contributor Day.