Codex tools: Log in
Thank you for contributing to the project we all love! Your participation is vital to the WordPress project.
WordPress is a user-driven project, and all developments and enhancements depend on users like you! Please consider contributing to the project and the WordPress Community in one or more of the ways outlined below. Contributions from users like you keep the project vibrant, alive and on the path of progress.
What can you do to keep WordPress going? Read on...
All of the documentation at the Codex has been produced by users like you and me! The many different ways in which you can volunteer your time and effort to improve the quality and scope of documentation are outlined in Contributing to the Codex.
You can also help by translating the Codex (see the section just below).
For more information on how to contribute to WordPress Core, make sure to check out the Core Contributor Handbook.
Translating WordPress describes the process of translating the WordPress software, so that people can use WordPress for blogs in languages other than English. This article and its companion, WordPress in Your Language, also tell you how to find and join the teams that are translating WordPress and the Codex (see the above Documentation section for information about the Codex).
The WP Polyglots blog is for questions, suggestions and discussions related to translating WordPress; please feel free to join in.
Another valuable contribution you can make is donating some of your time to help other users of WordPress. All WordPress related support at the WordPress Support Forum is provided free of cost, and the involvement of users is essential to maintain this.
Another support mechanism for WordPress users is IRC. There is an IRC channel for discussions on WordPress topics on the IRC FreeNode Server at #wordpress, and you can help by answering questions there. For more information on this see IRC and WordPress IRC Live Help.
You can help with the development of the WordPress software, whether or not you are a software developer.
One way to participate in WordPress development is to suggest features and participate in the development planning process. Even if you aren't a developer, you can help build consensus and formalize proposals, boiling down long email threads and IRC logs to their essence, so that developers can quickly ascertain what the community is hoping to achieve with a particular feature.
Another valuable contribution a non-developer (or developer) can make to WordPress development is to test WordPress. Before every stable release of WordPress, pre-release versions are made to enable testing. You can download the pre-releases and test them, so that the WordPress developers can fix problems before the new version is made available to the public. If you would like to get involved in this effort, join the wp-testers mailing list, where new releases are announced and discussed.
If you want to be on the bleeding edge of development, even before pre-release versions are put together, you can also check out the latest software from the WordPress Subversion (SVN) repository, as outlined in Using Subversion. Or, you can get the "nightly build" (which is created from the Subversion repository, and available as a zip file) at http://wordpress.org/nightly-builds/wordpress-latest.zip -- almost as up-to-date as the instantaneous Subversion repository.
If you find bugs while testing pre-release or already-released versions of WordPress, see the section just below.
Another way you can contribute to WordPress development is by reporting any problems you find with the WordPress software. The process of reporting bugs is described in Reporting Bugs -- please start by reading that article. Once you have understood the bug reporting process, you can search the WordPress Trac database to see if your issue has already been reported, and if not, file a new report. Your help with reporting bugs will be highly appreciated.
If you are a software developer, you can also help the development of WordPress by fixing problems that have been reported by you or another person in the WordPress Trac database. This process is also known as "patching", and is described in Reporting Bugs. That article also has some suggestions on how to find bugs to fix.
You can also subscribe to the wp-hackers mailing list to participate in discussions regarding WordPress development. All contributions, ideas and suggestions are welcome at the mailing list. Sometimes, requests are also made on the list asking for the help of volunteers to assist in the improvement and development of specific functionality.
If you are not familiar with the patching process or how to use Subversion, we recommend OpenHatch Training Missions as an easy learning tool.
Occasionally there are also bug days on the #wordpress-bugs IRC channel. You can read about what happens in a bug day in WordPress Bug Hunts, and subscribe to either the wp-hackers or wp-testers mailing list to find out when they happen.
You may also be interested to read this page on How does code make it into WordPress. It details how bug fixes, code and new features are included into the next releases of WordPress.
If you enjoy WordPress or find it to be useful, put a link to WordPress on your site. You can do this with a text link, or use one of the many WordPress logos and buttons on your site with a link to http://wordpress.org. Show you care.
The WordPress Community exists because everyone takes part in some way, by giving their time, energy, and sometimes even money, because they believe in the valuable services WordPress provides. We invite you to join the community in whatever way you feel is appropriate, and giving money to WordPress Theme and Plugin authors and developers who give so freely of their creativity and expertise by offering their services for free to all WordPress users is a good place to start.
If you use a WordPress Theme or Plugin and your WordPress blog depends upon it, contact the author and find out how you can give back and support their continued efforts. It takes a lot of time and energy to create and then support their Themes and Plugins, keeping them updated as WordPress changes and bugs are found. Many take donations or appreciate it when you blog about their Plugin or Theme. Others offer their Plugins and Themes as experiential portfolios - you play with it, you like it, you hire them. Most clearly indicate how they appreciate compensation for their hard work - give back to WordPress by giving back to them.
The more the WordPress Community supports the programmers, developers, testers, and challengers, the stronger and better WordPress becomes. Sometimes that means donating money, sometimes it means saying thank you.
Just remember, every contribution counts, no matter what it looks like. It takes every one of us to make WordPress better.