Summary for Helphub Meeting 15 August 2017


@kenshino @sergey @picturecities @davidmlentz @bravokeyl @aion11 @atachibana @mapk @andrealeebishop @joyously @clorith @milana_cap

MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. / Editing

Content is shaping up to a final state at steadily pace and can be released as is. Editing work on Helphub should be viewed as an iterative process. It is reported (by @atachibana) that HelpHub team has more than 3 active editors. @joyously pointed out that the migration workflow is hard to understand in Documentation Handbook – @atachibana @bishop will help to work on it.


Design is currently focused on UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it., @mapk is doing marvelous job on reporting issues and proposing solutions. Aim is to get back to UX design once the UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. gets to a level where developers and editors can actually use the site in a proper manner.. Testing UX with real users could give valuable feedback and @mapk volunteered to help with this.


Huge leap has been done since last meeting. Travis issues have been fixed and theme styles converted to sass partials for easier collaboration. All thanks to @clorith. UX issues are also started to be taken care of. It is noted that introducing sass and gulp can result in narrowing possible contribution to code due to lack of guidelines on how to use them.


GITGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. Submodules

It is suggested by @kenshino to use GIT Submodules as the method to pull in plugins that that are already pre-approved by 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. or the Helphub Team (such as Jetpack, SyntaxHighlighter etc). This way these pre-approved plugins can skip Travis and reduce the complexity on the code base. Custom built plugins by our collaborators should still be submitted via the normal commit and subsequent code review process.


As proposed on last meeting, in attempt to move things forward Development team had first bugscrubs last week. Attempt seem to be successful which will be reported in separate post.

Conclusions / Tasks

It is quite unclear how to contribute to HelpHub team, or Documentation team in general. We want more people to be able to help…. Helphub so we’re working on the following tasks:

  • Better explanation of how to contribute to HelpHub with content – allocated to @atachibana and @andrealeebishop
  • UX testing with real users – allocated to @mapk
  • Detailed guide for contributing to HelpHub with code (including setting up development environment and using grunt, gulp and sass) – allocated to @clorith and @milana_cap
  • GIT workflow explained and documented – allocated to @kenshino

Read the meeting transcript in the Slack archives.

The bug scrub transcript is available here.

(A Slack account is required)