Developing Learn WordPress

Development for Learn WordPress takes place on 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 be the repository owner.

Reporting bugs & enhancements

If you find a bug on the site or would like to suggest a new enhancement, please log an issue on GitHub. If you are unsure if your issue has already been posted, you can search the existing issues and ask in the #training and #meta-learn channels on the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at You don’t need to tag anyone on GitHub – the repository is monitored and new issues are automatically brought to the attention of the maintainers.

Please be as descriptive as possible when creating an issue – include as much information as you can, along with screenshots and any other relevant information.

If an issue already exists for what you want to post, then please comment on the issue to provide more information or even to simply agree with what is being proposed.

Top ↑

Contributing code

Anyone can contribute code to Learn WordPress. In order to run the site locally, you can clone the GitHub repository and follow the instructions to set it up. The repository readme lists the prerequisites for your system in order to run the code, as well as how to troubleshoot the most common issues. The development environment for Learn WordPress can be run from this repository without the need to set up the rest of 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. on your local machine.

Development on all properties is managed by the Meta team. Their handbook has some useful information about how to contribute using Git. All contributions are displayed on your profile.

If you have questions about Learn WordPress development, please use 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.-learn channel on Slack to discuss issues.

Top ↑

Working on issues

If you find an issue you’d like to work on, please go ahead and fork the repository to create your patch. You’re welcome to comment on an issue and ask to have it assigned to you.

If you’re looking for something to work on, please take a look at this list of open issues.

Top ↑

Creating a pull request

Please first open an ideas issue to suggest new commands, or open an issue in the appropriate repository to suggest enhancements to existing commands. Opening an issue before submitting a pull request helps us provide architectural and implementation guidance before you spend too much time on the code.

Once you’ve decided to commit the time to see your pull request through, please fork the Learn WordPress repository to your GitHub account, and clone that repository locally to work on. Follow the readme instructions to get the local development environment set up.

The Learn WordPress-specific coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. functionality exists in the wporg-learn 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 Plugin Directory or can be cost-based plugin from a third-party, and any theme-related functionality is in the wporg-learn-2020 theme. When you are ready, create a branch that includes your suggested updates, and create the pull request from that branch.

While we don’t require specific naming conventions for branches, it is helpful if you name it using the format {type}/{issueid-name}. For example, /bugfix/874-fix-tutorial-padding or /feature/875-add-language-filtering.

If there are any testing steps that are needed to review your pull request, please include them in the description. Please also include any relevant issue labels in the pull request.

Take a look at this pull request for a good example.

Last updated: