Theme Developer Handbook released

After around close to 2 years of development, through a total of 3 different teams, we have released the Theme Developer handbook, thereby completing the Developer Hub’s goal of having proper developer docs for the main aspects of WordPress.

This could not have happened without a few of the initial leads and project pushers – @siobhan, @samuelsidler @sewmyheadon @lizkaraffa @thoronas @jcastaneda @grapplerulrich @anthonynotes @topher1kenobe.

The list of people involved (not yet complete) is documented here and last count puts us at close to 100 people involved in the handbook in one way or another.

The handbook has been released in it’s version 1 form and is updated all the way to 4.7.

There’s always more to do and the team continues to manage and improve the handbook on Trello.

Please do give us feedback using the methods detailed here.

We hope this helps everyone make better themes!

Get cracking at https://developer.wordpress.org/themes/

Props to the editors who came in after the handbook progress stalled for awhile @kenyasullivan @xfrontend @burlesonbrad @nao @jacobmc @hardeepasrani @sheebaabraham @boogawooga @rahulsprajapati @viniciuslourenco @kafleg @atachibana @sarahovenall @sushil-adhikari @celloexpressions @juhise

+make.wordpress.org/themes

Agenda for Helphub Design Meeting 17 January 2017

Hello!

Time/date: Tuesday, January 17, 2017, 13:00 UTC in #docs

  1. Attendance
  2. Progress on Tasks
  3. AOB

You can find the main Helphub meeting’s agenda here.

Pinging @krogsgard @versatility @mapk @wizzard_

If I have missed any usernames, it’s not on purpose and do consider yourself invited to the meeting.

#agenda

Agenda for Helphub Meeting Jan 17

Hello!

Time/date: Tuesday, January 17, 2017, 14:00 UTC in #docs

  1. Attendance
  2. Migration Updates
  3. Design Updates
    • We will be having a design specific meeting an hour before this meeting – agenda
  4. Development Updates
  5. AOB

Pinging @atachibana @jon_bossenger @karys @nlarnold1 @greensteph @sarassassin @bethannon1 @juhise @hlashbrooke @sergeybiryukov @bravokeyl @quitevisible @ankitguptaindia @anevins @justingreerbbi @carlalberto @geoffreyshilling @normalize @hardeepasrani @danhgilmore @wizzard_ @cristiano.zanca @tacoverdo @lumberhack @krogsgard @clorith @versatility

If I have missed any usernames, it’s not on purpose and do consider yourself invited to the meeting.

#agenda

Summary for Helphub Meeting Jan 10

Attendance

@chetansatasiya @wizzard_ @hardeepasrani @normalize @juhise @mitraval192 @afazalmultani @sagarprajapati @miyauchi @ramiy @versatility @carl-alberto @kailanitish90 attended

Migration / Content Updates

Categories

The preliminary (2nd time) categories that we’re going with are

  • Installing WordPress
  • Getting Started
  • Security
  • Updating your WordPress
  • Themes
  • Plugins

Glossary

A glossary is being worked on and will likely use custom post types

Category Editors

@normalize will be Category Editor for ‘Getting Started’

Other editors are still pondering.

One-topic Articles

All articles should be on one specific topic only – I think it’s a good idea and this is how we’re separating the Security Articles. E.g. 2FA is one article instead of one sub section in a huge security article.
Editors should sort out articles into bite-able and functional chunks as a priority – In general think about what kind of things people would ask.
Guides
Guides are logical grouping of single topic articles. For example, a person looking into 2FA solutions for security, may also follow a guide that contains that information with other security recommendations. This does not however distract a person looking for specific information.
Trello
All work should be documented on Trello

Design Updates

Design meeting summary is available here

Development Updates

I believe we’re building some solid code now with @netweb, @miyauchi and a few others that are putting up Travis CI and writing Unit Tests.
@carl-alberto is working on the Category Widget
Zenhub
All development efforts are now being managed on Zenhub (an addon for Github). See this link to get started.
Developers
We need more developers so that everyone can have a bite size task. Not a full time job 🙂

Open Floor

A deeper discussion regarding the WP_Versions post type that houses all information about WordPress version was had with @ramiy, he will be submitting a pull request for review. In general, he suggests more information should be placed in meta fields so that it can be retrieved via the REST API.

#summary

Summary for Helphub Design Meeting Jan 10

Attendance

@mapk @krogsgard @v @wizzard_ @versatility @Kenshino @hlashbrooke attended

User Personas

The initial overlook into understanding user motivations has led us to discover the possibility of a need for Guides. Guides are logical grouping of single topic articles. For example, a person looking into 2FA solutions for security, may also follow a guide that contains that information with other security recommendations. This does not however distract a person looking for specific information.

Components Inventory

We are working on on creating a list of components of Helphub so we’ll be able to create quick prototypes for UX testing

Survey

The team with @wizzard_ leading survey efforts will continue to work towards churning our surveys for both users and the Support Team. To better understand user motivations of course.

Information Architecture

Based on the quick general categories that @wizzard_ has created to categorise the articles, a proper IA is being built.

Style guide

While this is more related to content, each basic article should be written on one single topic. This is built to adhere to the known motivation of a user wanting specific information.

Trello

We are working on individual tasks via Trello. Join us there?

Moving ahead

We’re hoping to have some quick development tasks for the developers who are finishing up

Design Lead

A design lead will be nominated to head design efforts. Nominations can be made for self or others.

Read the meeting transcript in the Slack archives. (A Slack account is required)

#summary

REST API Documentation Meeting January 11

After a slow period through the holidays the REST API team will be kicking off the new year later today in #docs at Wednesday, January 11, 2016, 23:00 UTC, to triage TODOs for the REST API documentation.

Agenda

  • Triage top user guide needs
  • Assign authors for priority user guides
  • Triage documentation issues
  • Establish schedule for docs issue scrubs

Agenda for Theme Developer Handbook Meeting January 12

Hello all,

This may be the last meeting before release of version 1 of the handbook.

Time/date:  Thursday, January 12, 2017, 03:00 UTC in #docs

  1. Attendance
  2. Project Status
  3. To-do list
  4. Readiness to release v1 of Handbook
  5. Open Floor

Pinging @kenyasullivan @xfrontend @burlesonbrad @nao @jacobmc @hardeepasrani @sheebaabraham @boogawooga @rahulsprajapati @viniciuslourenco @cais @kafleg @atachibana @miyauchi @juhise

For those not mentioned but would like to contribute to the Theme Developer Handbook, please read this post and join us for the meeting.

Any questions before that can be made in the comments!

#agenda

Agenda for Helphub meeting 10 January 2017

Hello!

 

Time/date: Tuesday, January 10, 2017, 14:00 UTC in #docs

  1. Attendance
  2. Migration Updates
  3. Design Updates
    • We will be having a design specific meeting an hour before this meeting – agenda
  4. Development Updates
  5. AOB

Pinging @atachibana @jon_bossenger @karys @nlarnold1 @greensteph @sarassassin @bethannon1 @juhise @hlashbrooke @sergeybiryukov @bravokeyl @quitevisible @ankitguptaindia @anevins @justingreerbbi @carlalberto @geoffreyshilling @normalize @hardeepasrani @danhgilmore @wizzard_ @cristiano.zanca @tacoverdo @lumberhack @krogsgard @clorith @versatility

If I have missed any usernames, it’s not on purpose and do consider yourself invited to the meeting.

#agenda

Agenda for Helphub Design Meeting 10 January 2017

Hello!

Time/date: Tuesday, January 10, 2017, 13:00 UTC in #docs

  1. Attendance
  2. Progress on Tasks
  3. AOB

You can find the main Helphub meeting’s agenda here.

Pinging @krogsgard @versatility @mapk @wizzard_

If I have missed any usernames, it’s not on purpose and do consider yourself invited to the meeting.

#agenda, #design

Summary for Helphub meeting 3 January 2017

Attendance

@aternus @wizzard_ @normalize @lumberhack @chetansatasiya @adamsilverstein @bhavesh @afzalmultani @clorith @Kenshino attended

Migration

@wizzard_ will come up with a list of suggested categories (top level at least) for teh next meeting

Ideally, editors should pick a category that they are comfortable with and specialise in it. A good example of this is the security category whereby @atachibana is working with @perezbox and @markm , security experts who’re able to offer real subject matter expertise.

Design Updates

We had our first design only meeting for Helphub and the summary is available here – https://make.wordpress.org/docs/2017/01/03/summary-for-helphub-design-meeting-january-2/
The design work will come up fast after we get the user research portion done, do read through the summary and please feel free to post thoughts in the comments.

Development Updates

Some development around getting Travis CI to work were done and more tests need to be created to get it up to scratch.

@lumberhack will be working on the autolinking function while @clorith is tasked to clear PR reviews.

Open Floor

Subscribe to Make / Docs – because pings don’t work now (properly) and we want everyone updated.

Read the meeting transcript in the Slack archives. (A Slack account is required)

#summary