Title: Docs Team Update 18th December
Author: Siobhan
Published: December 18, 2012

---

 [  ](https://profiles.wordpress.org/siobhan/) [Siobhan](https://profiles.wordpress.org/siobhan/)
6:40 pm _on_ December 18, 2012     
Tags: [docs ( 230 )](https://make.wordpress.org/updates/tag/docs/)

# Docs Team Update 18th December

The past week the major focus of the docs team has been on updating the WordPress
CodexWordPress Codex Living online manual to WordPress.org [https://codex.wordpress.org/](https://codex.wordpress.org/)
to get it up to date after the release of 3.5. On Thursday 13th – Friday 14th we
had a virtual documentation sprint in which we attacked our master list of Codex
updates. We completed almost all of the items on the list! You can see the [completed list here.](https://make.wordpress.org/docs/2012/11/27/if-all-goes-to-plan-wordpress-3-5-will/)

The people involved in the sprint worked really hard. They were: Jerry Bates (@jerrysarcastic),
Jonathan Wold (@sirjonathan), Philip Erb (@philerb), Curtis McHale (@curtismchale),
Mika Epstein ([@ipstenu](https://profiles.wordpress.org/ipstenu/)), Jason Hoffman(@
jhoffm34), and Marko Heijnen (@markoheijnen).

Particular thanks to Drew Jaynes (@DrewAPicture) who helped to drive the whole thing
and worked extremely hard the whole time.

There are some developer items still incomplete, so If anyone on the coreCore Core
is the set of software required to run WordPress. The Core Development Team builds
WordPress. team, or any other developers, could take a quick look and update any
items that would be fantastic. Most of them will only take a few moments to do. 
Just leave a message in the comments to say that you’ve done it and we can tick 
it off.

Since it was so successful, we’d like to have more documentation sprints in the 
future. These will be focused around major updates, ongoing projects, and areas 
that need tackled in the Codex. As well as holding virtual doc sprints, we’re interested
in the idea of running doc sprints at hack days at WordCamps.

Final note: it would help us to compile lists of things that need updated if the
core team could start using the needs-codex tag in their workflow.

[#docs](https://make.wordpress.org/updates/tag/docs/)

### Share this:

 * [  Threads ](https://make.wordpress.org/updates/2012/12/18/support-team-update-18th-december/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/updates/2012/12/18/support-team-update-18th-december/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/updates/2012/12/18/support-team-update-18th-december/?share=bluesky)
 * [  X ](https://make.wordpress.org/updates/2012/12/18/support-team-update-18th-december/?share=x)
 * [  Facebook ](https://make.wordpress.org/updates/2012/12/18/support-team-update-18th-december/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/updates/2012/12/18/support-team-update-18th-december/?share=linkedin)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fupdates%2F2012%2F12%2F18%2Fsupport-team-update-18th-december%2F%23respond&locale=en_US)

 1. ![](https://secure.gravatar.com/avatar/44567cb8c05873e8974341ab91a7aab4473707a8b77edf055314366e13836fec?
    s=32&d=mm&r=g)
 2.  [curtismchale](https://profiles.wordpress.org/curtismchale/)  7:12 pm _on_ December
    18, 2012
 3. Being sort of new to the Codex work, where is this workflow where I could find 
    the needs-codex tag?
 4.  * ![](https://secure.gravatar.com/avatar/19347ef87f4fd5978b2184e7f05af5c780485f69dbfdefccfe3521c732a87f06?
       s=32&d=mm&r=g)
     *  [Drew Jaynes (DrewAPicture)](https://profiles.wordpress.org/drewapicture/)  
       7:22 pm _on_ December 18, 2012
     * You can do a custom query on TracTrac Trac is the place where contributors create
       issues for bugs or feature requests much like GitHub.[https://core.trac.wordpress.org/](https://core.trac.wordpress.org/)..
       This should get you started: [https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&status=reviewing&keywords=~needs-codex&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&status=reviewing&keywords=~needs-codex&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority)
 5. ![](https://secure.gravatar.com/avatar/19347ef87f4fd5978b2184e7f05af5c780485f69dbfdefccfe3521c732a87f06?
    s=32&d=mm&r=g)
 6.  [Drew Jaynes (DrewAPicture)](https://profiles.wordpress.org/drewapicture/)  7:
    27 pm _on_ December 18, 2012
 7. Along the vein of adding the needs-codex keyword to TracTrac Trac is the place 
    where contributors create issues for bugs or feature requests much like GitHub.
    [https://core.trac.wordpress.org/](https://core.trac.wordpress.org/). tickets, 
    it may be advisable to add it following commits, maybe referencing the changset
    and/or comment #. This way, we don’t have to hunt through the ticket to figure 
    out what’s been changed or added.
 8. Here is an example: [https://core.trac.wordpress.org/ticket/21948#comment:11](https://core.trac.wordpress.org/ticket/21948#comment:11)

### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/updates/2012/12/18/support-team-update-18th-december/?output_format=md#respond)󠁿

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fupdates%2F2012%2F12%2F18%2Fsupport-team-update-18th-december%2F&locale=en_US)
to post a comment.

# Post navigation

[← Theme Review Team Update for 12/18](https://make.wordpress.org/updates/2012/12/18/theme-review-team-update-for-1218/)

[Polyglots Team Update 18th December →](https://make.wordpress.org/updates/2012/12/21/polyglots-team-update-18th-december/)