Documentation Team Updates November 8


Theme Developer Handbook

On schedule, will likely release after WCUS.

A feedback mechanism is likely required for the handbooks but is currently on lower priority.

Codex MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies.

Tedious manual work, we would love to have this task be worked on via Contributor Days


The REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) documentation is currently being merged in. A handbook will be first created and in-line doc comments will be done in 4.7 release.

Further work on it is being discussed


Development is slowed down but work is continuing.

Inline Docs

Our primary focus is now on the 4.7 docs audit

Next meetings


#docs, #documentation

Docs Team Update April 23, 2013

This post comes a little bit late for last week but here goes:

This (last) week

  • The newly-launched ‘Adopt a Codex Page’ drive has proven pretty popular, with volunteers adopting 15 of the most popular Codex pages so far
  • @hearvox is working on a new Page Templates page for the Codex that’s shaping up well. Looking to reduce the code-heaviness.
  • @siobhan and @jenmylo are planning to begin work on a new documentation architecture over the several months
  • We’re still ramping up for the 3.6 Codex Sprint, combing through 400 changesets and several hundred still-open tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. tickets. The incoming code reference will alleviate much of this work in the future.
  • @siobhan is organizing a WordPress delegation to attend a docs conference in Cincinnati in June, inviting WP businesses to send someone and looking for interested community members.

Next (this) week

  • We’ll be collecting volunteers to handle bigger parts of the 3.6 Codex Sprint, a make/docs post is forthcoming
  • Work will continue on Adopt a Codex Page, handbooks and moving the new code reference forward

#code-reference, #codex, #documentation