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