Docs Team Update: May 29, 2014

The following is a summary of the topics discussed during our weekly Docs chat:

1. DevHub: @siobhan said Post2Posts will be used to make everything relational, and @Rarst is looking at the best way to implement that. @coffee2code will implement source code on the individual pages, as well as the examples functionality. A link will be added at the top of the Codex to direct people to the new code reference. Feedback is still needed on implementing explanations in the code reference, and differentiation on the search results pages.

2. Handbooks: @blobaugh posted a summary of the weekly Handbooks chat containing the current status of both Developer Handbooks. Part One of the Theme Developer Handbook is on schedule for completion by June 7. One section of the 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Developer Handbook is complete, and 2 more are near completion. Contact @blobaugh and @sewmyheadon at the email addresses listed in the post if you’re interested in getting involved. The next Docs Sprint is Saturday, June 7, 2014 at 10am PDT in Seattle. Contributors can also participate virtually in the #wordpress-sfd IRC channel.

3. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. string feedback: TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket #28199 is a request to improve the upgrade translations text, and needs feedback from the Docs team. @siobhan added her feedback to the ticket.

You can read the chat logs here.

#docs