Howdy! This is a rough draft of the handbook for contributing to WordPress core.
Work here is still in progress. Some pages are only outlines and there are many other topics left to explore.
We’re tracking the progress of this contributor handbook in a spreadsheet. If you’re interested in helping, find someone from the docs team, particularly @samuelsidler (sams on IRC).
If you are a core contributor who wants to help, you can:
- You can leave comments on any of these pages, which can be incorporated into the main text. Particularly helpful when fixing Jorbin’s typos.
- Or, write something on your own blog and suggest we include it here.
- Or, track down a core developer who can give you access to this site.
Random notes on things that need a lot of work:
- The Submitting a Patch page
- The Design Decisions page
- The Licensing page
- Points of contact for questions
- Localization, testing, documenting, support, etc. — Contributing_To_WordPress / @andrewspittle @hanni, perhaps my WCNW presentation could be a useful ref too , I was _greatly_ (read, saved, cribbed etc) influenced by Jorbin’s fantastic DC presentation and following blog post
- Good first bugs?
- Creating and Applying Patches
- Specific tutorials. Offers on wpdevel Done
- The Trac section needs some expansion on these topics:
- How a ticket progresses
- Our keyword-based workflow
- Opening a ticket
- Closing a ticket
- Reopening a ticket
- Need something more on backwards and forwards compatibility.
- Writing tests
- Submitting a patch
- Coding standards (CSS, JS, inline) Done
- Finding an SVN client
- Things you need to know about Running Trunk such as why you need to define ‘WP_DEBUG’ and ‘SCRIPT_DEBUG’ as true