Getting Started

This page gives you a clear guide on what you need to do in order to get started with contributing to WordPress core. Below you will find a list of items that need to be taken care of, with links leading to more specific tutorials on the individual steps.

Everything described here is recommended to efficiently contribute to WordPress core. Where possible, different choices are highlighted to leave enough flexibility to account for your typical workflows. If you are planning to join a contributor day in the WordPress core team, following these steps in advance will ensure you maximize your outcome of that day since often-times several of them can be time-consuming during contributor days, particularly due to slow internet connections.

Joining communication channels Joining communication channels

Communication in WordPress commonly happens either asynchronously on Trac, which is the issue tracker used by the project, or in live chat on Slack, which is a popular instant messaging service used by many organizations. Here is how you get access to these two tools:

  1. Sign up for a account and complete the instructions. You may optionally sign up at with the same email address if you’d like to have a profile picture (recommended). This account can be used for all contributing activities.
  2. In order to join the international WordPress Slack team and thus be able to participate in core team meetings and other discussions, you need to receive an invite. Visit the WordPress + Slack page while being logged in with your account, and click the link to receive the invite per email.
  3. Via the email, log in to the Slack team. For email address, use {username} where {username} is your user name you picked for If possible, pick the same username for Slack.

Top ↑

Setting up your development environment Setting up your development environment

In order to contribute to WordPress core, you need a local development environment and a checkout of WordPress trunk, which is the development version of WordPress. Be aware that this is not the same as the latest downloadable WordPress release.

Setting up a local server Setting up a local server

Download and install a local development environment on your machine. You have a few options here:

  • The recommended way is to use a software called Varying Vagrant Vagrants (or VVV), which is a Vagrant configuration tailored specifically for WordPress development. Please follow the handbook instructions on how to install VVV.
  • If you already have an environment that includes a webserver with PHP, MySQL/MariaDB and SSH access and you prefer working with that system, it is perfectly fine to decide on using another environment. Popular alternatives include DesktopServerMAMP, WampServer, XAMPP, and others. Be aware though that none of them is optimized for WordPress core development, so a little more groundwork will be necessary in that case.

Top ↑

Setting up a version control system Setting up a version control system

Install a version control system to use for WordPress core. Here you have two options:

  • WordPress core by default uses Subversion (or SVN) for version control, which works relatively similar to Git, but is a little older. While most people prefer working with Git, the SVN commands you typically use when developing for WordPress core are trivial and almost the same as their Git counterparts. VVV already has SVN pre-installed. If you are using another environment or prefer to also use SVN directly on your computer, there is a handbook tutorial guiding you through the process.
  • Alternatively, you can install Git from the Git project website. On many environments, for example VVV, you will already find it pre-installed. If you prefer using a visual UI in addition, feel free to use a client app such as Sourcetree, or GitHub Desktop (which works particularly well when used together with GitHub).

Top ↑

Setting up a WordPress development repository Setting up a WordPress development repository

Set up the development version of WordPress in your development environment. Again, this is a significantly easier process if you are using VVV for your setup. How you proceed depends on whether you decided to use SVN or Git for version control in the second step:

And with that, you’re ready to get started with contributing!

Top ↑

What is next? What is next?

If you plan to attend a contributor day, the above prerequisites will give you a jumpstart so that you can immediately focus on learning how to actually contribute. If you are not visiting this page because you are going to attend a contributor day or if you are already interested in diving in deeper, the best way to proceed is to learn more about why contributing to core is important and which processes are involved. In case you immediately prefer working with tickets instead, this introduction to Trac will help you get familiar.