Summary for Helphub meeting February 28

Attendance

@clorith, @milana_cap, @mapk, @versatility

Community Summit

All Helphub team members are also automatically part of the Documentation Team. All Helphub team members are encouraged to submit nominations or their own names to attend the WordPress Community Summit 2017.

People who are interested in attending but find it tough to justify the financial burden it’d place on you or your family can look towards the  travel assistance programme.

In addition, we need list down some pertinent topics for work/discussion on during the summit. Take note that it is key that we raise these topics early to promote cross team discussions and collaboration. Topics have been suggested and listed on the previous Documentation Team meeting summary, all Helphub team members are encouraged to submit more topics for discussion, particularly ones that revolve around Helphub.

People who are interested in the summit are encouraged to speak to @Kenshino

Migration Updates

Looking at the docs spreadsheet, we’re down to 15 remaining articles (10 being re-written, and 5 in need of some last minute polish)

Design Updates

@Kenshino needs to get the key styles from WordPress.org (the new ones) applied to the Helphub site to get the work moving ahead. @versatility is eager to press on.

It is possible to get some tips on this via @obenland who has apparently done something similar with the wp-org learn child theme.

Development

Developers are mostly waiting for design work to be take shape so that they can do the front end development. A fair bit of the backend work has already been finished.

Meeting time

A proposal has been put forward to move the meeting time back an hour to 1500 UTC. No disputes were made on this.

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

#summary

Summary for Documentation Team Meeting February 16

 

Attendance

@drewapicture @Kenshino @desrosj @hardeeparsani @cais @milana_cap @kafleg @mrahmadawais @juhise

Change of timing

We moved the meeting forward this time due to conflicting schedules. Apologies to those who were thinking attending it at the original timing.

We are perhaps thinking of moving it up 2 hours to 2017 15:00 UTC. What do you think?

General Updates

  • Helphub is moving ahead slowly.
  • Theme Developer Handbook was released
  • DevHub comments / code suggestions clearing is going too slow (@drewapicture will help to clear)

WordPress Community Summit 2017

The community summit will be held in conjunction with WCEU this year in Paris. The last time it was held alongside WCUS in Philadelphia in 2015.

The summit will be held June 13-14, preceding WCEU, June 15-17.

The Community Summit is less like an actual contributor day and more of an opportunity to discuss and make decisions and plans for your respective teams.

Typically, for instance, you’ll see the core team make roadmap-related decisions about what’s coming up in core development for the next two years. Talk about priorities, active projects, projects you want to work on, Very much like a retreat.

The Docs team launched the Plugin Developer Handbook, for instance during the San Franciso Summit in 2014

It usually proves to be very productive for every team that meets and has a presence. It’s also an opportunity to have discussions with other teams, especially for discussing cross-team projects like helphub (docs + support + meta), devhub (docs + meta), inline docs (docs + core), etc.

People attending

@kenshino, @drewapicture

People wanting to attend

@milana_cap, @atachibana

We would love to have more people to attend from the Helphub, Theme Developer and Plugin Developer Handbooks teams. If you are working on a documentation project for WordPress.org, or if you’re a documentation junky who wants to contribute, please let @Kenshino or @drewapicture know that you’re interested.

Attendance to the WordPress Community Summit is through nomination by the Make / WordPress team leads. We can only nominate you if you let us know you’re interested!

We will have to submit this by the end of February. Please let us know by then!

Summit Discussion Topics 

  • Game plan for recruitment
  • Onboarding Plan
    • We get a ton of people wanting to contribute but we have no established recourse for providing that access.
  • State of Doc’s Team (own) documentation
  • DevHub and Helphub translation Mechanism (Docs + Meta + Polyglots)

We would love to cover more in the summit, so please post topic suggestions in the comments!

WP CLI Code/Command Reference

We’ll probably be restarting devhub meetings soon, so for now, I’d say just leave the command docs in control of wp-cli.org and we’ll look at short-term and long-term solutions to bringing those docs over.

The upside of wp-cli command docs is that they’re already written in PHP and use phpdoc to parse into the staticly-generated pages, so we might be able to fork the parser we use for the code reference.

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

#summary

Summary for Helphub Meeting Jan 17

Migration Updates

23 articles left to get through with basic re-writes.

All work should be documented on Trello

Design Updates

As the design meeting was postponed due to schedule conflicts, there were no updates this meeting.

Development Updates

There are a total of 17 open issues still, most of which have to do with front end design that require decisions to be made by the Helphub design team.

Open Floor

Category Editors

There are only 2 category editors still, @normalize for ‘Getting Started’ and @atachibana for ‘Security’, we need some of the key editors that have been working on the project to take up the mantle.

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

#summary

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

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

Summary for Helphub Design Meeting January 2

Attendance

@krogsgard @versatility @wizzard_ @kenshino attended

As previous efforts towards user research were largely undocumented, we’re making a renewed approach to understanding user needs and behaviour.

We will be doing the following

  1. @versatility will be documenting the various components of Helphub
  2. @versatility will build various prototypes of those components and use them for feedback/research
  3. We will work the ‘single’ views (e.g. how we perceive users would want to view the articles) before we build the journey on the Homepage that will lead them to those articles.
  4. 2 surveys will be created
    • One for the Support Team – likely an open ended question to gain sentiment on how they think users would approach help documentation
    • One for the end users – @wizzard_ will work on the questions with @versatility
  5. All efforts will be tracked and documented on Trello

A few considerations (possibly)

  1. Search should be a global and obvious element
  2. No sidebars as it lacks consistency with mobile

Search Use Cases

  1. Searching for a specific problem
  2. Searching for a general guide (e.g. total guide from installing to securing WordPress)
  3. They’re on Helphub but don’t know what search terms to use (so they’re just clicking on what looks right)

Some reference

  1. A discussion from the Support Team about personas and common topics

Next Meeting

Tuesday, January 10, 2017, 13:00 UTC – One hour before Helphub Meeting

#design, #summary

+make.wordpress.org/design

Summary for Helphub Meeting December 20

Hello,

Attendance

@normalize @manikya @lumberhack @atachibana @afzalmultani @kadamwhite @ankitkgupta @wizzard_ @lasacco @kenyasullivan @versatility @clorith @Kenshino attended

Migration & Content

@atachibana updated us on the following stats for content

  • 142 total articles
  • 88 are re-written
  • 6 are currently being re-written
  • 48 still needs work (screenshots, link fixing, general grammar edits etc)

@normalize will take the lead on creating a glossary for use in Helphub

External links to helpful content should ideally be copied back to Helphub. Helphub editors are encouraged to involve subject matter experts

A set of guidelines should be written to define how one should write a good article.

All authors should be recorded (for now in Trello) and should be attributed in the article.

@versatility floated the idea of having guides – that will pull in data from various help articles to form a guide.

Development

A meta info area should be built that shows in the footer of the article the contributing authors, revision dates and citations.

@clorith will look into and clear some pull requests on our Github Repo

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

#summary

Summary for Helphub meeting December 13

Attendance

@atachibana, @wizzard_ @lumberhack @hlashbrooke @juhise @hardeepasrani @geoffreyshilling @clorith @ankitguptaindia @kenshino attended

Migration Updates

General cleanup work is still going on and various contributions were made to the articles

@wizzard_ will be leading efforts to define the key categories for Helphub (current ones are shown in the mockup)

Design Updates

A design specific chat will be held by the Helphub design team in which @krogsgard, Ruth, @dianekinney and @kenshino will be working on the user experience aspects of Helphub. Currently front end development has been halted to await proper UX input.

Development Updates

@clorith has joined to help with development efforts.

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

#summary

Summary for HelpHub meeting November 15

Attendance

@carlalberto, @christiano.zanca, @geoffreyshilling, @atachibana, @lumberhack, @wizzard attended

Migration Updates

@atachibana modifed contents of 2 articles and will continue to update the second one

  1. https://wp-helphub.com/advanced-topics/multilingual-wordpress/
  2. https://wp-helphub.com/getting-started/creating-a-search-page/

Design Updates

No new updates

Development Updates

@lumberhack is working on ‘Autolinking Helphub to DevHub articles using shortcodes’, good progress has been made, a small challenge with dynamic hooks which can be fixed but requires some help this week

@carlalberto will do some code cleanup later on the TOC plugin, still messy but it should do its basic job

@kenshino will be reviewing changes and providing feedback

Open floor

No new news, but we wish HelpHub team lead @kenshino a very Happy Birthday !

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

#summary