Summary for Theme Developer Handbook Meeting 20 October


Attendance

@kenyasullivan @sheebaabraham @nao @hvillacorte @Kenshino

Introduction

@Kenshino took over the project from Flynn and Liz who had already completed 80-90% of the handbook with the previous team of contributors.

The current project direction is to just finish the To-do and In-progress items in the Trello Board and release the handbook as a version 1. Further will can continue on it after release.

To-do items are not placed in any form of priority and contributors should simply take the article that they feel they can better relate with.

Project Status

There are 9 articles in the ‘To-do’ list and 7 articles on the ‘In-Progress’ list (at time of meeting).

Team members have been asked to assign themselves a deadline on Trello and many committed to finishing it in a week.

General Info

For General formatting for handbook
https://make.wordpress.org/docs/handbook/developer-resources/handbooks/handbooks-style-and-formatting-guide/

To use the [code] shortcode created by the SyntaxHighlighter Evolved plugin
https://en.support.wordpress.com/code/posting-source-code/

To-do list

@Kenshino pointed out that articles can be worked on together by different team members, each taking a different section. This is especially useful for articles that are mostly empty. Team members can add themselves onto the Trello card and comment on the task that they are undertaking.

Team members are also encouraged to add or remove tasks to articles.

State of Team & Direction

There are 10 members for the Theme Developer Handbook team, which I have a record at https://docs.google.com/spreadsheets/d/1hAPORz_yl4UTerPo8Tl5j_Xznfpm_NItrNftoXwBqvA/edit#gid=0

If every team member takes an article and work on it, we would be finished by the end of October.

@Kenshino is anxious to finish the handbook (at least version 1) for the following reasons

  • Themes submitted to the Theme Repository have been dropping in quality. Leading to a 6-7 month wait before Theme Reviewers can even get to a theme that one has submitted. It’s severely exhausting the Theme Review Team because they have to keep catching the same mistakes and do not have a real W.org resource to refer people to.
  • The Helphub Team (Creating a new system and re-writing articles for User Documentation – think ‘How to create a post’ type of articles) needs to know what articles that can off-load to us so that they can concentrate on what they need to do.
All of these projects are quite inter-linked and it looks like ours is easiest to finish so that we can be a form of support.

Open Floor

@kenyasullivan asked about a Github copy of the Theme Developer Handbook. Ideally, in the future, the handbook would have a feedback mechanism at the bottom of the article (similar to the Developer Documentation) and people can then contribute to the handbook.
Github is unlikely going to improve contributions after such a mechanism is put in place.
Team members with immediate questions should feel free to ping @Kenshino on Slack, while non-urgent issues can be placed in Trello.

#summary