Docs Team Update 21st March

Last week

  • we’ve implemented a new reporting system on the theme and 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 dev handbooks to try to get things moving along. This seems to be successful so far, particularly with the theme dev handbook. If anyone misses two reports in a row myself or the editor will get in touch with them.
  • we’ve started discussions around creating docs for backbone.js and underscore.js
  • the code reference is coming along nicely. @rmccue and Paul Gibbs have been doing a lot of work on the parser, and @melchoyce has come up with some designs for us. Paul and Ryan need cli at the minute so they’re going to set up a betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. until they’re done.
  • working on help text
  • @DrewAPicture is continuing with preparing the codex sprint stuff

Next week

  • move all of the coding standards to the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook until we’ve decided where they should live
  • start to work on planning out a information architecture for documentation. We are generating a lot of different docs and we need to think about where they are going to live and how different users are going to navigate through them.
  • the Installing WordPress page is the 7th most visited page on wp.org but it’s in need of some love. We’re going to look at the best way to approach this.
  • continuation of work on the help tabs for 3.6

#docs