Last update: 26 of April of 2020
Table of contents
In order to contribute to WordPress concerning development multiple possibilities and options exist. These that we presented here are some examples that raise to be a guide at the time of preparing infrastructure, but are many options and possibilities.
We separate the options following the type of contribution that you want to do.
IF you want to develop plugins or themes, we recommended to you to test in stable versions of WordPress, but also to do it in the versions of development of future launchings. For it we left these options you that can be useful:
- VPS with Git: This installation has a Git synchronous with the main branch of WordPress, reason why you will have elements of future versions to prove compatibilities and errors.
Development for the WordPress Community
If you want to test and to develop for the WordPress Community we recommended a type to you of slightly different installation, using the tools that the rest of members of the community uses. For it we left these options you that can be useful:
- VPS with Subversion: This installation has a synchronous Subversion with the main branch of WordPress, reason why you will have elements of future versions to prove compatibilities and errors, in addition to being able to prove pending patches to approve.
From you will be able here to realise some tests and improvements in the code of WordPress on the basis of which the Community contributes. Between some of those things that you can do you have:
- To prove patch of the Trac: Thanks to the installation of the VPS with Subversion you will be able to apply the patches offered by the community in the Trac and to comment envelope they.
- Tests with PHPUnit: When changes of PHP are applied, it is always good idea to pass a test to verify that it does not give to any type of error the change that can come in the patch.