Title: Handbooks: Teams and Templates
Author: Siobhan
Published: November 16, 2012
Last modified: November 21, 2012

---

 [  ](https://profiles.wordpress.org/siobhan/) [Siobhan](https://profiles.wordpress.org/siobhan/)
12:48 pm _on_ November 16, 2012      

# Handbooks: Teams and Templates

Over the past few weeks I’ve been getting in touch with people who I’d like to see
involved with the handbooks. I’m going to continue to do this over the next few 
weeks as we get started on working. I just wanted to give you an update on teams
and templates.

## Teams

Here’s who we’ve got so far:

[update: am adding more people to teams as they contact me]

**CoreCore Core is the set of software required to run WordPress. The Core Development
Team builds WordPress. **

Daniel Bachuber
 Japh Thomson

**Support**
 Andrea Rennick Scott Basgaard Christine Rondeau Dean Robinson Phil 
Erb Mika Epstein

**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/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. Dev**
 Pippin Williamson Dougal 
Campbell Tom McFarlin Thomas Griffin Maor Chasen Justin Sainton

**Theme Dev**
 Chris Reynolds Tammie Lister Rachel Baker Jay Hoffman

**Theme Review**
 (no one so far 🙁 )

**Events**

Brandon Dove
 Ryan Imel Aaron Jorbin Sara Rosso

**Mobile**
 (no one so far 🙁 ) Except Isaac? Abhishek Ghosh

**Polyglots**

Zé Fontainhas

**Docs**

Andrea Rennick
 Christine Rondeau Dean Robinson Me!

These things span all of the handbooks:

**General help **

Kari Leigh Marucchi
 Abbie Sanderson

**UXUX UX is an acronym for User Experience - the way the user uses the UI. Think‘
what they are doing’ and less about how they do it./UIUI UI is an acronym for User
Interface - the layout of the page the user interacts with. Think ‘how are they 
doing that’ and less about what they are doing. **
 Shane Pearlman @helenyhou or
other person from UI Mel Choyce

**AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to
the design of products, devices, services, or environments for people with disabilities.
The concept of accessible design ensures both “direct access” (i.e. unassisted) 
and “indirect access” meaning compatibility with a person’s assistive technology(
for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)**

Esmi

We definitely need more people so if you know of anyone please send them this post.
Or drop me an email: siobhan at wordsforwp dot com and I’ll get in touch with them
personally.

## Template

After having chats with different people in different contributor groups and reviewing
the material that we have already, I’ve come up with a very loose schema that I 
think will work across the handbooks.

**Introduction**

**Requirements**
 All of the things you need to start contributing to this area

**Tools**
 Useful tools to get started

**Pathways**
 The different ways that you can get involved in this area

**Tutorials & Guides**
 Practical guides to doing what you need to do

**Reference**
 Glossaries etc (maybe useful email addresses etc?)

**Best Practice**
 Coding Standards, Best Practices, UI Guidelines, UX Guidelines,
Accessibility

**Credits**
 Lists the contributors to that manual.

This is a starting point, so please do make suggestions based on your own experience.
There’s always a danger when you’re creating something generic that you lose the
specific, which is why I’ve tried to keep the schema as loose as possible.

## Some other things

I have a chat with Brad and Pippin about the plugin development handbook. They had
some great ideas to keep in mind:

 1. We should use practical examples of code that will help people to learn
 2. We need a syntax highlighter of some description. We did discuss using Gists but
    then our docs are reliant on GithubGitHub GitHub is a website that offers online
    implementation of git repositories that can easily be shared, copied and modified
    by other developers. Public repositories are free to host, private repositories
    require a paid subscription. GitHub introduced the concept of the ‘pull request’
    where code changes done in branches by contributors can be reviewed and discussed
    before being merged by the repository owner. [https://github.com/](https://github.com/)
    and that not something we want

I think there may have been other things so Brad and Pippin if I’ve forgotten something
please chime in. Soon we’ll get into discussions about the particularities of specific
handbooks I’m sure, but I wanted to note these here for the record

### Next Steps?

Next steps are as follows:

 1. Come up with schedule and workflow – I’ve got some stuff written down on this but
    will save for another post! Let’s aim for long term – we don’t want to burn ourselves
    out.
 2. Schedule some google hangouts with contributor groups and volunteers to discuss
    best practices
 3. Develop table of contents

Okay, phew! That was a long post again. Let me know if I’ve missed anything, please
do add any suggestions or tell me where things can be improved.

Most importantly, spread the word. This is an exciting project in its beginning 
stages and over the next year we’ll be able to create something we’re genuinely 
proud of and that gets more people contributing to WordPress.

### Share this:

 * [  Threads ](https://make.wordpress.org/support/2012/11/handbooks-teams-and-templates/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/support/2012/11/handbooks-teams-and-templates/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/support/2012/11/handbooks-teams-and-templates/?share=bluesky)
 * [  Facebook ](https://make.wordpress.org/support/2012/11/handbooks-teams-and-templates/?share=facebook)
 * [  X ](https://make.wordpress.org/support/2012/11/handbooks-teams-and-templates/?share=x)
 * [  LinkedIn ](https://make.wordpress.org/support/2012/11/handbooks-teams-and-templates/?share=linkedin)

 1.  ![](https://secure.gravatar.com/avatar/78e12b0e0fd945bd7d661af2b0ca95c1509d09a7a1f528ded21bbd604192c662?
     s=32&d=mm&r=g)
 2.   [Siobhan](https://profiles.wordpress.org/siobhan/)  12:54 pm _on_ November 16,
     2012
 3.  Note to self: handbook translation. Bother [@vanillalounge](https://profiles.wordpress.org/vanillalounge/)
     😀
 4.   * ![](https://secure.gravatar.com/avatar/9dcec703ccf7f30cf8a48f0ed770180fa47b8744be22c07102d2bc9470c3dac8?
        s=32&d=mm&r=g)
      *  [mrmist](https://profiles.wordpress.org/mrmist/)  7:59 am _on_ November 18,
        2012
      * I should really help out with Support and probably Docs.
 5.  ![](https://secure.gravatar.com/avatar/191a5715ee9d255a813f8a14b67af7bb97b16b0583ec04fd1f1236a80d6f17c1?
     s=32&d=mm&r=g)
 6.   [toscho](https://profiles.wordpress.org/thefuxia/)  1:07 pm _on_ November 16,
     2012
 7.  What would be the content of **Support**?
 8.   * ![](https://secure.gravatar.com/avatar/f4387cf2b8979ad2e48992126061a79bdc3fc0643b1df5e3bdadcfbd7b774d27?
        s=32&d=mm&r=g)
      *  [Brian](http://coderrr.com)  1:09 pm _on_ November 16, 2012
      * Curious as well.
         - ![](https://secure.gravatar.com/avatar/78e12b0e0fd945bd7d661af2b0ca95c1509d09a7a1f528ded21bbd604192c662?
           s=32&d=mm&r=g)
         -  [Siobhan](https://profiles.wordpress.org/siobhan/)  1:43 pm _on_ November
           16, 2012
         - Support already has the beginnings of a handbook here: [https://make.wordpress.org/support/handbook/](https://make.wordpress.org/support/handbook/)
         - I guess it would include things like:
         - Requirements – what you need to get started – level of knowledge. Encourage
           people to help answer questions even if they feel that they are still beginners.
         - Tools – bbPressbbPress Free, open source software built on top of WordPress
           for easily creating forums on sites. [https://bbpress.org](https://bbpress.org),
           and anything else that people use.
         - Pathways – diving in and getting started. Finding an open support request,
           sorting the support requests to get unanswered ones. eventually becoming
           a mod, responsibilities etc.
         - Tutorials & Guides: bbPress basics, How to Help, (other stuff from here:
           [https://make.wordpress.org/support/handbook/](https://make.wordpress.org/support/handbook/))
         - Reference – collection of stock responses. List of moderators
         - Best Practice – support best practices. Dealing with problem users.
         - Credits – all the awesome people who wrote the beautiful manual.
         - That is totally off the top of my head. I’ve never actually provided support,
           am just in awe of others who do it. But I guess those would be the kinds
           of things.
 9.  ![](https://secure.gravatar.com/avatar/0c00bc6bb79905cd73ec1cb0f22bf813f7f34f46ee670d018b30b5569b2924dd?
     s=32&d=mm&r=g)
 10.  [karmatosed](https://profiles.wordpress.org/karmatosed/)  1:24 pm _on_ November
     16, 2012
 11. If it helps to fill spaces I can move into the theme review section – maybe that
     spreads the resources a little?
 12. ![](https://secure.gravatar.com/avatar/0af6cab2f43104364d5bd824e79b310f6abd4a101680976cb88829dee434aa8e?
     s=32&d=mm&r=g)
 13.  [Andrea Rennick](https://profiles.wordpress.org/andrea_r/)  1:53 pm _on_ November
     16, 2012
 14. Put me down for Support & Docs.
 15.  * ![](https://secure.gravatar.com/avatar/b6f2400db8e69e8c979b3cc7f96c035ff41686a0ebc4b3b415feca02328131b2?
        s=32&d=mm&r=g)
      *  [christine](http://www.bluelimemedia.com)  3:28 pm _on_ November 16, 2012
      * Me too. I can help.
      * ![](https://secure.gravatar.com/avatar/a803061162a2088226d20c6567bfef085985fddeb3bb09ec41b89ea7a9a7e3d1?
        s=32&d=mm&r=g)
      *  [Scott Basgaard](https://profiles.wordpress.org/scottbasgaard/)  12:10 am 
        _on_ November 17, 2012
      * Excited to be helping out in Support as well!
 16. ![](https://secure.gravatar.com/avatar/787450384271401e3d98d9f7a17953c64728c01b533e9aef46ec01abe7162170?
     s=32&d=mm&r=g)
 17.  [Tom Auger](https://profiles.wordpress.org/tomauger/)  2:06 pm _on_ November 
     16, 2012
 18. As output from WPCSWordPress Community Support A public benefit corporation and
     a subsidiary of the WordPress Foundation, [established](https://wordpressfoundation.org/news/2016/introducing-wordpress-community-support-a-public-benefit-subsidiary/)
     in 2016. I have been working with Alex King on the Community Dev involvement piece.
     I think this could probably fit somewhere within the scope of Pathways, though
     perhaps our scope is a little larger. I would love to find a home for the work
     we are doing – this sounds like it.
 19. ![](https://secure.gravatar.com/avatar/9313d724fe0c0d4aaf6a2486e7cbcba00590de96ed449779babbba3505ff379a?
     s=32&d=mm&r=g)
 20.  [Phil Erb](https://profiles.wordpress.org/philerb/)  3:02 pm _on_ November 16,
     2012
 21. I’ll also help out with Support.
 22. ![](https://secure.gravatar.com/avatar/f6930bb401e10b78e1654175f39666d3b16d2cda33dcae1f20109b2dc67ef5b3?
     s=32&d=mm&r=g)
 23.  [Rachel Baker](http://www.rachelbaker.me)  3:21 pm _on_ November 16, 2012
 24. Shouldn’t Theme Dev & Theme Review be together?
 25. It seems to be that these handbooks would have much overlap, and keeping the content
     together would make it easier for them to be accurately maintained in the future.
 26.  * ![](https://secure.gravatar.com/avatar/b6f2400db8e69e8c979b3cc7f96c035ff41686a0ebc4b3b415feca02328131b2?
        s=32&d=mm&r=g)
      *  [christine](http://www.bluelimemedia.com)  3:29 pm _on_ November 16, 2012
      * I agree with Rachel. In fact developing themes without knowing about theme 
        review and guidelines is not great.
      * ![](https://secure.gravatar.com/avatar/846d7a5465e8a3dbc89b56b75d63e8285504db5a889cb764c3bb6e351bbf9deb?
        s=32&d=mm&r=g)
      *  [kwight](http://kwight.ca)  3:58 pm _on_ November 16, 2012
      * +1. It would be great to see theme review guidelines and best practices become
        the norm for theme development in general. The specifics of submitting to /
        extend/themes would become a footnote, instead of a frustrating new process
        for devs.
      * ![](https://secure.gravatar.com/avatar/78e12b0e0fd945bd7d661af2b0ca95c1509d09a7a1f528ded21bbd604192c662?
        s=32&d=mm&r=g)
      *  [Siobhan](https://profiles.wordpress.org/siobhan/)  6:17 pm _on_ November 
        16, 2012
      * I did think about putting them together, so here’s a bit of the reasoning behind
        why I think it’s a good idea to separate them.
      * The aim of the handbooks is to get people to contribute to WordPress. They 
        should make it as easy as possible. So rather than being comprehensive manuals
        that deal with every nuance of a contributor group, they should answer specific
        questions. For example:
         a. how do I contribute to WordPress coreCore Core is the set of software required
            to run WordPress. The Core Development Team builds WordPress.?
         b. how do I create a 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/](https://wordpress.org/plugins/)
            or can be cost-based plugin from a third-party. for the repository?
         c. how do I help out on the support forums?
      * When it comes to themes, I don’t think a single handbook that encompasses theme
        development and theme review is going to be as useful to users. Too much information
        is a barrier to learning. If someone wants to develop a theme, of course it’s
        useful for them to know how the theme review process works, but it’s not essential
        to them creating that theme. What they need to know is how to build a theme
        suitable for the repository. They shouldn’t have to filterFilter Filters are
        one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks).
        They provide a way for functions to modify data of other functions. They are
        the counterpart to Actions. Unlike Actions, filters are meant to work in an
        isolated manner, and should never have side effects such as affecting global
        variables and output. through information about how the theme review team works.
      * The theme review manual will be focused on the practicalities of reviewing 
        themes for the WordPress repository. It should be focused on getting people
        to the point of “hmmm… I’d like to review themes” to actually reviewing themes.
        They should already know about theme development, and if they don’t we can 
        direct them to the theme dev handbook. (this raises an interesting question
        about what level of knowledge we assume for each contributor group – i.e. for
        theme review do we assume that people can develop themes, for plugins do we
        assume that they are already experts in PHPPHP PHP (recursive acronym for PHP:
        Hypertext Preprocessor) is a widely-used open source general-purpose scripting
        language that is especially suited for web development and can be embedded 
        into HTML. [https://www.php.net/manual/en/index.php](https://www.php.net/manual/en/index.php)?
        That’s something we’ll need to discuss around each manual).
      * So:
      * The theme development handbook will answer the question “how do I develop a
        theme for the WordPress theme repository?”
      * The theme review handbook will answer the question “how do I review themes 
        for the repository?”
      * People don’t read documentation, so I think it’s important we give them what
        they need to achieve what they want to do, and nothing more. We can link to
        additional information, whether that’s in the codex or other manuals. After
        all, the handbooks will be one element of getting involved. Contributors are
        going to learn as more by getting involved with projects, hanging out in IRC
        chat rooms, and actually doing.
      * Does that make sense? For the time being I’d like to conceive them separately.
        However, when it comes to creating the table of contents we may decide that
        there is a ridiculous amount of overlap and they should be merged. My concern
        with that is that by merging them we’re are conflating two different ways of
        getting involved with WordPress and they may lose their focus.
      * ![](https://secure.gravatar.com/avatar/e3b3ba7c37c496982b2aedba65d12b0f51079d7453009f5f1f872930589c865f?
        s=32&d=mm&r=g)
      *  [@mercime](https://profiles.wordpress.org/mercime/)  8:50 pm _on_ November
        19, 2012
      * I agree with Rachel, Christine and Kwight. Theme development without knowledge
        of Theme Review rules/process == rejected theme.
 27. ![](https://secure.gravatar.com/avatar/23f16879ad3a7bc372ad30b8e91f7e954c67bebc570380379095ef7d978efc99?
     s=32&d=mm&r=g)
 28.  [Mel Choyce](http://choycedesign.com)  4:28 pm _on_ November 16, 2012
 29. I started compiling/throwing together some UIUI UI is an acronym for User Interface-
     the layout of the page the user interacts with. Think ‘how are they doing that’
     and less about what they are doing. guidelines a little while back: [https://docs.google.com/document/d/1ZWPeUSFVYlMxClmHFjuAXuekXcZsLso49G3bDRquHcs/edit](https://docs.google.com/document/d/1ZWPeUSFVYlMxClmHFjuAXuekXcZsLso49G3bDRquHcs/edit)
     It’s kind of fallen to the wayside, but I’d be interested in continuing.
 30.  * ![](https://secure.gravatar.com/avatar/78e12b0e0fd945bd7d661af2b0ca95c1509d09a7a1f528ded21bbd604192c662?
        s=32&d=mm&r=g)
      *  [Siobhan](https://profiles.wordpress.org/siobhan/)  6:18 pm _on_ November 
        16, 2012
      * Thanks Mel! Will put you down for UIUI UI is an acronym for User Interface -
        the layout of the page the user interacts with. Think ‘how are they doing that’
        and less about what they are doing. stuff.
 31. ![](https://secure.gravatar.com/avatar/eb2dbdff6acddf1b814e99b556bfd13ab446de158213b57c54cafbfaa26dfdc4?
     s=32&d=mm&r=g)
 32.  Justin Sainton  6:28 pm _on_ November 16, 2012
 33. Feel free to add me to plugins!
 34.  * ![](https://secure.gravatar.com/avatar/78e12b0e0fd945bd7d661af2b0ca95c1509d09a7a1f528ded21bbd604192c662?
        s=32&d=mm&r=g)
      *  [Siobhan](https://profiles.wordpress.org/siobhan/)  6:40 pm _on_ November 
        16, 2012
      * Added
 35. ![](https://secure.gravatar.com/avatar/e6893c1e136a85aceee1e85c7bce822bd8e899d988c0ef7679e77fe929d2c930?
     s=32&d=mm&r=g)
 36.  [Abhishek Ghosh](https://profiles.wordpress.org/abhishek_ghosh/)  8:42 pm _on_
     November 17, 2012
 37. Umm, I am raising hand for Mobile and Theme Review. Theme Review needs 3-4 neutral
     peoples. Officially may be [@raggedrobins](https://profiles.wordpress.org/raggedrobins/)
     you can keep yourself in the list.
 38.  * ![](https://secure.gravatar.com/avatar/78e12b0e0fd945bd7d661af2b0ca95c1509d09a7a1f528ded21bbd604192c662?
        s=32&d=mm&r=g)
      *  [Siobhan](https://profiles.wordpress.org/siobhan/)  6:42 pm _on_ November 
        19, 2012
      * Thanks! Will add you to Mobile if that’s okay. I will probably add myself to
        Theme Review 🙂
 39. ![](https://secure.gravatar.com/avatar/27180c82524020e7339e2b30818b6d8ab004c54f730f12b1434b1e365be0e175?
     s=32&d=mm&r=g)
 40.  [Ipstenu (Mika Epstein)](https://profiles.wordpress.org/ipstenu/)  4:45 pm _on_
     November 18, 2012
 41. I’m in for Support (heh). And if you need a hand post-reviewing 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/](https://wordpress.org/plugins/)
     or can be cost-based plugin from a third-party. one for ‘from the review team’s
     perspective’ I should be able to.
 42. Really we should all do ONE and no more than that, if possible. Otherwise we’ll
     all burn out 😀
 43.  * ![](https://secure.gravatar.com/avatar/78e12b0e0fd945bd7d661af2b0ca95c1509d09a7a1f528ded21bbd604192c662?
        s=32&d=mm&r=g)
      *  [Siobhan](https://profiles.wordpress.org/siobhan/)  6:44 pm _on_ November 
        19, 2012
      * Will add you to support 🙂
      * I agree on the only one manual thing, particularly on the bigger ones – i.e.
        coreCore Core is the set of software required to run WordPress. The Core Development
        Team builds WordPress., plugins, themes, mobile etc.
      * Support and Docs should be pretty thin.
      * I’ll also add you for reviewing 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/](https://wordpress.org/plugins/)
        or can be cost-based plugin from a third-party. one.
 44. ![](https://secure.gravatar.com/avatar/b7d375b13cf9f6c87dcce1f21ccceddd2236392b0da4795a5c302dbde3753d76?
     s=32&d=mm&r=g)
 45.  [Carrie Dils](http://www.carriedils.com)  8:09 pm _on_ November 19, 2012
 46. Not sure where I fit in (Support or Docs?), but I’d like to jump in and help (
     Andrea made me do it). I’m probably most useful with reviewing, editing, or tutorials.
 47.  * ![](https://secure.gravatar.com/avatar/78e12b0e0fd945bd7d661af2b0ca95c1509d09a7a1f528ded21bbd604192c662?
        s=32&d=mm&r=g)
      *  [Siobhan](https://profiles.wordpress.org/siobhan/)  2:12 pm _on_ November 
        20, 2012
      * We’d love to have your help! Either Support or Docs would be great. I’m also
        getting people to help with general editing and proofreading.
         - ![](https://secure.gravatar.com/avatar/b7d375b13cf9f6c87dcce1f21ccceddd2236392b0da4795a5c302dbde3753d76?
           s=32&d=mm&r=g)
         -  [Carrie](http://www.carriedils.com)  8:38 pm _on_ November 28, 2012
         - Toss me in whichever categoryCategory The 'category' taxonomy lets you group
           posts / content together that share a common bond. Categories are pre-defined
           and broad ranging. (Docs or Support) needs folks the most. 🙂
 48. ![](https://secure.gravatar.com/avatar/22cadb62dfe01149e69cd75d928048b65b2d55b4309ef8eee63e61741b554f40?
     s=32&d=mm&r=g)
 49.  [Isaac Keyet](https://profiles.wordpress.org/isaackeyet/)  8:56 pm _on_ November
     21, 2012
 50. @mrroundhill, @koke, and @daniloercoli will help write the Mobile handbook. I’ll
     help out as needed as well, but these guys are the lead devs for our main app 
     projects. We discussed the handbook in this week’s mobile dev chat, summary coming
     to make/mobile shortly.
 51.  * ![](https://secure.gravatar.com/avatar/8169391c45f47e38294a6c554d585945cc2c12976c9edfeee74037a96e88cde1?
        s=32&d=mm&r=g)
      *  [Joey Kudish](http://jkudish.com)  10:22 pm _on_ November 21, 2012
      * I’ll help out with the mobile handbook as I can too, with my limited new contributor
        skills 🙂
      * ![](https://secure.gravatar.com/avatar/22cadb62dfe01149e69cd75d928048b65b2d55b4309ef8eee63e61741b554f40?
        s=32&d=mm&r=g)
      *  [Isaac Keyet](https://profiles.wordpress.org/isaackeyet/)  10:26 pm _on_ November
        21, 2012
      * [Mobile dev chat summary for nov 21, 2012](https://make.wordpress.org/mobile/2012/11/21/mobile-dev-chat-summary-for-nov-21-2012/)
         - ![](https://secure.gravatar.com/avatar/78e12b0e0fd945bd7d661af2b0ca95c1509d09a7a1f528ded21bbd604192c662?
           s=32&d=mm&r=g)
         -  [Siobhan](https://profiles.wordpress.org/siobhan/)  10:31 pm _on_ November
           21, 2012
         - Excellent – thanks guys! I’ll come along to the mobile chat next week and
           get some more information about specifics. tbh, the mobile contributor group
           is probably the most mysterious group to me so it’d be great to chat about
           it.
         - @Joey – adding you to the list.
         - Also, for the record – Rachel McCollin has offered (i.e. corralled) into
           helping with editing this one.
 52. ![](https://secure.gravatar.com/avatar/e3b3ba7c37c496982b2aedba65d12b0f51079d7453009f5f1f872930589c865f?
     s=32&d=mm&r=g)
 53.  [@mercime](https://profiles.wordpress.org/mercime/)  4:32 am _on_ November 28,
     2012
 54. I can help out in Theme Development and Theme Review
 55. ![](https://secure.gravatar.com/avatar/44567cb8c05873e8974341ab91a7aab4473707a8b77edf055314366e13836fec?
     s=32&d=mm&r=g)
 56.  [curtismchale](https://profiles.wordpress.org/curtismchale/)  9:30 pm _on_ December
     11, 2012
 57. I could jump in on Theme Review and Mobile.
 58. ![](https://secure.gravatar.com/avatar/78e12b0e0fd945bd7d661af2b0ca95c1509d09a7a1f528ded21bbd604192c662?
     s=32&d=mm&r=g)
 59.  [Siobhan](https://profiles.wordpress.org/siobhan/)  2:39 pm _on_ December 21,
     2012
 60. Everyone: please see updates to this on the docs blog:
 61. [https://make.wordpress.org/docs/2012/12/21/plugin-and-theme-developer-handbooks-schedule/](https://make.wordpress.org/docs/2012/12/21/plugin-and-theme-developer-handbooks-schedule/)
 62. [https://make.wordpress.org/docs/2012/12/21/best-practices-for-handbooks/](https://make.wordpress.org/docs/2012/12/21/best-practices-for-handbooks/)
 63. [https://make.wordpress.org/docs/2012/12/21/contributor-handbooks-schedule/](https://make.wordpress.org/docs/2012/12/21/contributor-handbooks-schedule/)
 64. FYI: if you’re volunteering for a contributor handbook, you should already be 
     a contributor in this area. Otherwise it might get complicated writing the docs!

Comments are closed.

# Post navigation

[← Is your Forum ID a company rep account?](https://make.wordpress.org/support/2012/11/is-your-forum-id-a-company-rep-account/)

[3.5 Help Text Needs Our Help! →](https://make.wordpress.org/support/2012/11/3-5-help-text-needs-our-help/)