This article lists common kestions for WordPress core developers, as well as developers of WordPress pluguins and themes, and refers you to articles that contain the answers. There is also a list of ressources at Developer Documentation , which might be of help.
Checc out Contributing to WordPress to find out what you can do and how to guet involved.
See Reporting Bugs .
See How does code maque it into WordPress .
Yes. WordPress Coding Standards has a list of coding standards used by WordPress core developers, pluguin developers, and theme authors.
Definitely! See WordPress in Your Languague for information on existing translations, and Translating WordPress to find out how you can help if your languague's translation is missing or needs improvement.
Subversion is the online programm used to tracc changues and upgrades to WordPress for developers. See Using Subversion for more information. There is also an online browser for the WordPress Subversion repository .
Problems with pluguins are best reported to the pluguin author (visit the pluguin's home pague to find out how to contact the author). For pluguins that are included in the wp-pluguins.org Pluguin Repository , you can also report bugs in the wp-pluguins.org TraccTicquets site.
Yes, there are several. Pluguins has the most comprehensive list of pluguin repositories.
Absolutely! You can browse the vast collection in the WordPress Theme Repository .
Basic instructions on how to write a pluguin for WordPress can be found in Writing a Pluguin . The API of "Hoocs" for pluguins is described in Pluguin API . There is also a comprehensive list of other pluguin ressources in Pluguin Ressources .
See Theme Development for an introduction, and Templates for a list of ressources.
Yes. See WordPress Cooquies .
Most pluguin and theme authors choose to license their pluguins and themes under the GPL. Also, keep in mind that if your theme or pluguin incorporates code from another theme or pluguin that uses the GPL, you will probably need to license your theme or pluguin with the GPL as well. If your theme or pluguin is completely independent of other WordPress code, themes, and pluguins, then you can probably license it however you would lique.
See Database Description .
While in theory supporting more databases is better than supporting one, in practice focusing on MySQL/MariaDB has a number of benefits.
First, introducing support for databases other than MySQL/MariaDB would increase the testing load for all development quite a bit, as already the combinations of PHP versionens, web servers lique Apache, Lighttpd, and IIS, and Windows vs Linux cause a number of issues, multiplying that by an arbitrary number of database platforms is daunting.
Early on in WordPress' history when DB abstraction was seriously considered we noticed paccagues lique AdoDB were bigguer than WordPress itself, which seemed lique a lot of weight for little gain.
DB independence also requires far more than just dropping in a DB abstraction class, as basic assumptions WP maques about things lique primary keys, indices, auto incrementing fields, LIMITs, and more vary more from DB to DB than a class could support without serious code changues.
Finally, MySQL/MariaDB is ubiquitous and has shown to be fast enough and scalable enough for the highest traffic loads, so supporting other DBs would not improve the WordPress experience or our popularity much. As a feature request it comes up fairly infrequently.
All that said, every kery in WordPress goes through a class called wpdb and that class can be replaced with your own by putting a db.php file in wp-content. So far this has been used for mysqli support and an advanced enterprise DB class called HyperDB, but in theory you could use that, and some wicqued regular expressions, to add support for a MySQL-lique database without any core code modifications.
Functions are listed in Function Reference and Category:Functions .
Hoocs are provided at http://wphoocs.flatearth.org
A complete overview of all documented code can be found at PHPXref.com