Docs Team Intro
Hi there, I’m Siobhan McKeown, and I’m currently acting rep for the newly formed docs team. Docs was previously included in support but after documentation-related discussions at the summit it was decided that docs could do with its own group. Hopefully this will encourage more people to help to keep the codex updated, and should raise awareness that docs isn’t restricted to the codex, but anywhere that content or documentation is required, we can help out.
It’s a pretty new group at the moment, but this is what I’d love to see the docs group help out with:
- updating the Codex
- improvements to UI help and text
- contributor handbooks
- developer docs
- any other content/doc-related tasks that other teams want to chuck at us.
To get involved with docs, you can jump in with editing the codex, or get involved with one of the projects that we are currently setting up.
These are:
1) Handbooks – a collection of contributor handbooks for guiding people through the process of contributing to WordPress. We currently have 35 volunteers for the handbooks. We’re a little light on contributors to the mobile and theme review manuals – if anyone knows of anyone who can help send them my way!
If you don’t feel that you’re enough of a WordPress expert to write content from scratch you can still get involved. We’re building a team of editors and proofreaders who will responsible for making everything consistent. It’s a great way to learn!
2) User Guide – this is nearly finished. A user guide (with lots of pilfered content from WordPress.com) that will help users to use WordPress. This will need to be updated any time that WordPress is updated. It also needs to find its final home.
3) Help tabs – this is currently in inception. Am hoping that it will be a review of content in the Help tabs with a view to making improvements alongside the UI improvements for genuinely helpful help.
Also ongoing is the Codex, which will need to be updated with the release of WordPress 3.5. There is a team of people who always work hard to get this done. This is usually done via the wp-docs mailing list, but with the new P2 we’ll hopefully see more activity there.
Whenever a new release appears I’ll post a list of things that need updated in the codex.
We are conducting some research into the types of documentation that different WordPress users/developers want to see. Once that is finished and the docs team has had time to digest it we can create a long-term roadmap for documentation.
In the meantime, if there are any docs you would like to see let us know here.
Jane Wells 4:23 pm on November 20, 2012 Permalink |
Hi @raggedrobins. Not sure who/when/why someone started calling a user guide something other than a handbook, but it was just meant to be one of the handbooks, not an entirely separate entity. Handbooks weren’t ever meant to be limited to contributor areas, they were meant to cover all the areas where people need to learn how to use WordPress.
etc
I think somewhere along the way it’s gotten skewed based on how people view their own roles, maybe? I’m concerned about the big separation that it looks like has started. I hope it is not to late to stop and take a breath, and reduce/remove this separation of intent.
Siobhan 4:42 pm on November 20, 2012 Permalink |
We discussed this in an IRC chat back in August: https://irclogs.wordpress.org/chanlog.php?channel=wordpress-sfd&day=2012-08-16&sort=asc#m178
Somewhere in there our wires must have gotten crossed. The user manual was called the user handbook but we changed it as it didn’t semantically make sense. The other manuals were at core/handbook/, events/handbook etc etc.
As far as I am aware, the handbooks are specifically for contributing to WordPress (whether that’s theme review, theme dev, support, docs, core etc etc). It make sense to separate these from the user manual as it differentiates between a) people who contribute to WordPress, and b) people who use WP, whether that’s as a user, admin, editor, or whatever. Though I hadn’t heard anything about an administrator manual (or any other user types).
Maybe we need to have another discussion about intention? Am happy to do so.
Ipstenu (Mika Epstein) 5:11 pm on November 20, 2012 Permalink |
It was because the ‘Support Handbook’ and the ‘User Handbook’ apparently confused the heck out of people.
Jane Wells 8:32 pm on November 20, 2012 Permalink |
“Support” should have been “Forum Moderator.”
Jane Wells 8:24 pm on November 20, 2012 Permalink |
So there seems to have been a huge drop somewhere along the way, and now there are dozens of people excited about writing contributor handbooks (which should be coming out of the contributor groups themselves, really) and no handbooks to teach people how to actually make themes, plugins, etc. That really bums me out.
Siobhan 9:00 pm on November 20, 2012 Permalink |
There will be handbooks for developing themes and plugins.
Making a theme or plugin and submitting it to the WordPress repo is contributing to WordPress.
Jane Wells 9:12 pm on November 20, 2012 Permalink |
We need to get on the same page with lingo them, because it sounds like you are using words that have specific meaning already. Putting a theme in the repo is a contribution to the ecosystem, but that is not a contributor group. Since you came in as an acting team rep just this week, we should probably set up a chat to go over background stuff so you have the same grounding, vocabulary, etc as the others.
Siobhan 9:30 pm on November 20, 2012 Permalink
That would be helpful. For reference, the handbooks I proposed are:
Core
Support
Documentation
Polyglots
Mobile
Theme Review
Developing WordPress Themes (in adherence to the theme review guidelines)
Developing Plugins for the repo
Events
The original post is here: http://make.wordpress.org/support/2012/11/handbooks/
kwight 5:44 pm on November 20, 2012 Permalink |
Hello everyone,
My name is Kirk, I’m a theme developer and I’m one of the volunteers for the Theme Review Team. I’d be happy to help out with the theme review docs as much as I can.
Has there been any discussion regarding time commitment? As with a lot of volunteers, availability waxes and wanes – are we asking for a certain amount of time per week/month or anything like that?..
Siobhan 6:02 pm on November 20, 2012 Permalink |
Hi Kirk! We’d love to have you on board! I think that the theme review manual won’t be too huge. It’ll be mostly a matter of reviewing what is already available, researching what needs to be added, and packaging it up into a lovely theme review manual that new reviewers can use to get started and current reviewers can use as a reference.
In terms of time commitment – I’m just working out a schedule. Because Christmas is about to hit us I think the bulk of the work will start in January. And it’s going to be a long time frame (8 -10 months) so I can’t imagine that theme review will require more than a few hours per week. Especially since there is so much content there. Does that help?
kwight 7:47 pm on November 23, 2012 Permalink |
Great, sounds good!
kwight 8:25 pm on November 26, 2012 Permalink |
Just so I’m clear, the Theme Review Handbook and the Theme Review Guidelines will be two separate things? Clarifying with Chip Bennett over here: http://make.wordpress.org/themes/2012/11/26/wordpress-3-5-guidelines-revisions/#comment-24432
Siobhan 8:35 pm on November 26, 2012 Permalink |
Yup – two different things. The theme review guidelines will be included in the theme review handbook (and anywhere else they are needed, no doubt).
As Chip said on his post – the handbook is more of a “how to get involved” tool. It should get someone from starting out with theme review to being an awesome reviewer.
kwight 8:50 pm on November 26, 2012 Permalink |
Got it.
I’m assuming each of the handbooks is a site/grouping of web pages?