Summary for Docs Team Meeting 1 April 2019

Attendance

@milana_cap @nosolosw @joyously @chrisvanpatten @kafleg @makewebbetter @aduth @jankimoradiya @immeet94 @kenshino attended

HelpHub Development

We’re currently trying to move issues form GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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 be the repository owner. https://github.com/ to MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. to give proper visibility over bugs that affect the code base that was merged into 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/

The team is working on checking if the issues are reproducible on WordPress.org and will migrate related issues.

@milana_cap has updated the list of developers that contributed code to HelpHub. We’re working out which badge to give (Meta or Doc) and will finalise this soon

@milana_cap and @clorith are working on a monthly bug scrub date/time

HelpHub Design

It’s been raised that the forum and HelpHub landing pages are too similar. A discussion will be needed with @iviolini and @clorith to work this through

GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ Handbook

@nosolosw mentioned that the Gutenberg docs have improved quite a bit thanks to the efforts of many people, and the main issue now is discoverability

It was recommended by both @Kenshino and @chrisvanpatten to get the contents of the current Gutenberg developer documentation into a DevHub handbook as a main focus and work out both the technical roadmap and the content re-ordering at a later stage.

@nosolosw will be conferring with the Gutenberg team over the next few days.

Google Season of Docs

In short – there’s 3 months that a technical writer (or more) that can sign up to write docs for WordPress.org

We could decide where the focus should be. It could be working on improving Gutenberg Docs or making sure we look at the other handbooks to review the level of technical writing that we’re at

@chanthaboune is looking into how we’d apply as WordPress.org and mentors are needed for this effort. If you’re interested, take a look at https://developers.google.com/season-of-docs/docs/mentor-guide and let us know you’re interested either via DM on Slack, a message in #docs or a comment on this P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. post!

Documentation Team Badges

After a bit of discussion, we’ve landed at a criteria

  • Documentation Contributor: You have contributed over X number of changes across HelpHub or DevHub.
  • Documentation Team: You regularly attend Documentation Team meetings and you are either a project lead or a team lead of a project.

Contributor badges are likely to be permanent and Team badges denote current activity over a period of 2 months.

We’ll likely have to work on the criteria a little more and will make a separate P2 post to solicit feedback before confirming it.

Maintenance of Theme Developer Handbook

The Docs Team would like to bring in the Theme Review Team to take ownership of the Theme Review Handbook (just as Plugins has done so for the plugins handbook).

@kafleg has been requested to form a team and work with @atachibana to bring the theme handbook up to speed.

You can read a transcript of the meeting via https://wordpress.slack.com/archives/C02RP4WU5/p1554130866012100