Handbooks Step 1: Creating the Table of Contents

We’re at the first stage of the handbooks, creating the table of contents. Here’s what you do:

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 Developer Handbooks

I have created two spreadsheets for these handbooks. Please go into the spreadsheets and start adding sections to the ToC. I’ve added links to ToC that were suggest to me for inspiration.

By creating the ToC like this we’ll be able to get an overview of the whole thing before we start creating pages. You can find them at:

• Plugin Developer Handbook
• Theme Developer Handbook

The ToC should be finished by 21st January. We’ll review where we are at next week’s chat.

@rachelbaker will be the editor for the Theme Developer Handbook so she’ll be taking the lead on that one.

Am still looking for an editor for the Plugin Dev Handbook let me know.

When the ToC is finished I’ll create the pages and we’ll move on to the next step.

Contributor Handbooks

Most of these will be created at make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//area/handbook

You can see examples at:

• Mobile
• Docs

Polyglots will be created on make/docs. We’re using Edit Flow to manage the editorial workflow here. If anyone else wants to build theirs on make/docs just let me know.

Core is a little bit different. It’s already got a lot of content there. I’m going to do an audit of the current content and then work with @japh and @danielbachhuber to see what we need to add and what needs to be fleshed out.

If you have any questions or if there’s anything that I’ve missed let me know.

#handbooks