Summary for HelpHub meeting 20 May 2019

Attendance

@atachibana @milana_cap @kenshino @mkaz @joyously @FahimMurshed @ibdz @juhise @truongwp @Marcio Zebedeu @bharatkambariya @justinahinon @aurooba attended

Phase 1.5 – Development

No updates. In last weekend, @milana_cap had been organizing local WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more..

Design

@ibdz is now officially leading design for HelpHub, and he is already done some work with the WordPress Versions table page.
He has some design pattern of responsive table that needs to be discussed in design meeting this week, and will leave comments for these design label issues:

https://github.com/WordPress/HelpHub/issues?q=is%3Aopen+is%3Aissue+label%3Adesign

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

@milana_cap lead Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.’s docs team and redirected 96 pages or 87% of queued tasks. Thank you all: @Zoran Koneski @colovicc @zdravkosokcevic100 @bloop434 @lazarus9 @zockey @MilosJS

@aurooba will have a Contributor Day on this Saturday in Calgary.
2 Version pages were missing in Codex.

@atachibana fixed 3.9.5 and will fix 1.5.1.1

AOB

There are 2 proposals on 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/.. Please feel free to comment.

What’s the best way to use the More Info section?
https://make.wordpress.org/docs/2019/05/13/the-best-way-to-use-the-more-info-section/

Proposal: WordPress Developer Handbook for common topics
https://make.wordpress.org/docs/2019/05/19/proposal-wordpress-developer-handbook-for-common-topics/

HelpHub Bug Scrub Notes, 26 April 2019

HelpHub bug scrub is back. For the time being we’re planning to hold these once a month. If there’s a need, we’ll reconsider this decision. All the meetings will be happening in #meta-helphub channel.

At this point, HelpHub has two places for issues: Trac and Github. Our aim is to move all Phase 1.5 issues from 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 TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. as these issues are really just fixes for what is already live at wordpress.org/support. Phase 2 is planned to be worked on at Github for now.

Responsibility for Trac issues is very unclear and should be discussed between docs and 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. teams. We don’t want to step on each other’s toes so it would be beneficial for both teams to make it clear who’s responsible for responses and decisions regarding reported issues.

At this bug scrub meeting we were discussing only Phase 1.5 issues.

Content

Content has only one issue on Github. @atachibana said he’ll comment on it and close it.

Another content related issue is opened on track https://meta.trac.wordpress.org/ticket/4195. It is highly recommended that content reps of documentation team get involved in discussion.

Design

We need decisions for 3 design related issues on Github. Also, we should see if @iviolini is still available for the project.

Development

Good first issues

During bug scrub we detected several issues that can be labeled as “good first issue”. They require either simple fix or just copying code from Github PR.

  1. https://meta.trac.wordpress.org/ticket/4267 – need switching h2 for h1 as explained here
  2. https://github.com/WordPress/HelpHub/issues/239 – has code in PR
  3. https://github.com/WordPress/HelpHub/issues/232 – has code in PR
  4. https://github.com/WordPress/HelpHub/issues/230 – has code in PR
  5. https://github.com/WordPress/HelpHub/issues/229 – has code in PR

Need discussion

1. https://github.com/WordPress/HelpHub/issues/237

We have to decide which is appropriate for HelpHub

  • To keep the order of TOC as like as (paper) book, or
  • To show the latest article as like as Search results

2. https://github.com/WordPress/HelpHub/issues/231

We need to properly redirect this URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org https://wordpress.org/support/category/. It’s not directly accessible from anywhere but it is possible to arrive from, let’s say, here https://wordpress.org/support/category/advanced-topics/ by editing URL.

Ready for coding

  • https://github.com/WordPress/HelpHub/pull/261 – has PR but the code is violating WPCSWordPress Coding Standards A collection of PHP_CodeSniffer rules (sniffs) to validate code developed for WordPress. It ensures code quality and adherence to coding conventions, especially the official standards for WordPress Core.
  • https://github.com/WordPress/HelpHub/issues/214 – it’s been suggested that we should omit children from TOC but at the meeting we agreed that we want children – ignore the code in PR
  • https://github.com/WordPress/HelpHub/issues/111 – we don’t use Handbook pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party so we can’t replicate the toggles. We should, however, try to style everything else.

Attendance

@atachibana @sergeybiryukov @felipeelia @milana_cap

You can read a transcript of the meeting at https://wordpress.slack.com/archives/CG47GT4G2/p1556290821016800

The next bug scrub will happen in late May. Date and time will be discussed and published prior.

#bug-scrub

HelpHub Bug Scrub

HelpHub bug scrub is back. We’ll test Friday 3PM UTC as possible time for regular monthly bug scrub.

We’ll go through 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/ issues for Phase 1.5.

Content issues: https://github.com/WordPress/HelpHub/issues?q=is%3Aissue+is%3Aopen+label%3A%22Phase+1.5+-+Content%22

Design issues: https://github.com/WordPress/HelpHub/issues?q=is%3Aissue+is%3Aopen+label%3A%22Phase+1.5+-+Design%22

Development issues: https://github.com/WordPress/HelpHub/issues?q=is%3Aissue+is%3Aopen+label%3A%22Phase+1.5+-+Development%22

Pinging @atachibana for content and @iviolini for design issues. Everyone are welcome to attend and participate.

Bug scrub will happen in #meta-helphub channel on

Friday, April 26, 2019, 15:00 UTC

#bug-scrub

Summary for HelpHub Meeting 22 April 2019

Attendance

@makewebbetter @milana_cap @softservenet @atachibana

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

@atachibana will take a look at content related 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/ issue and confirm its validity. https://github.com/WordPress/HelpHub/issues/247

Phase 1.5 Design

There are 3 design related Phase 1.5 issues on Github: https://github.com/WordPress/HelpHub/issues?q=is%3Aissue+is%3Aopen+label%3A%22Phase+1.5+-+Design%22

We need some decisions made by @iviolini here.

Phase 1.5 Development

We have 8 development related issues: https://github.com/WordPress/HelpHub/issues?q=is%3Aissue+is%3Aopen+label%3A%22Phase+1.5+-+Development%22t%22

Some have ready PRs with conflicts and some need decisions to be made. But first of all, we need to clean up the code to comply with WPCSWordPress Coding Standards A collection of PHP_CodeSniffer rules (sniffs) to validate code developed for WordPress. It ensures code quality and adherence to coding conventions, especially the official standards for WordPress Core.. Hopefully this will be finished by the end of the week so we can start merging PRs again. Once the WPCS issues are done we can resolve conflicts on PRs and hand them over 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. team.

All issues with PR’s are valid for on 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//support

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/ Docs

No updates from @daveryan.

HelpHub localisation

Discussion is going on here https://make.wordpress.org/polyglots/2019/02/25/helphub-localisation-plan/

Notes from first meeting https://make.wordpress.org/polyglots/2019/03/27/helphub-localisation-plan-meeting-notes/

Everyone are welcome to get involved.

Bug scrub

We’ll have one bug scrub this week just to cleanup the Phase 1.5 issues from Github: https://github.com/WordPress/HelpHub/issues?q=is%3Aissue+is%3Aopen+label%3A%22Phase+1.5%22

On Friday, 26th April, the same time as regular meetings – 3PM UTC.

Friday, April 26, 2019, 15:00 UTC

After that we’ll set regular bug scrubs once a month, as a start. Everyone are welcome to attend.

AOB

@softservenet volunteered to keep an eye on new WordPress versions and update History page: https://wordpress.org/support/article/history/

This can be considered as one of the “Content” tasks for the Contributor Badge criteria.

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

Agenda for HelpHub meeting 22 April 2019

Hello all,

Next HelpHub meeting will happen on

Monday, April 22, 2019, 15:00 UTC
  1. Attendance
  2. Phase 1.5 Check-in
  3. Detailed content discussions
    • Content MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. Check-in (@atachibana)
    • 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/ Docs (@daveryan)
  4. HelpHub localisation
  5. Setup regular development bug scrub
  6. AOB

Helpful Links

  • HelpHub Staging – https://wp-helphub.com/
  • GitHub repo – https://github.com/WordPress/HelpHub
  • State of HelpHub (read for Phase 2) – https://make.wordpress.org/docs/2018/02/26/state-of-helphub-february-2018/
  • Previous Docs Team minutes – https://make.wordpress.org/docs/2019/04/08/summary-for-docs-team-meeting-1-april-2019/

Summary for HelpHub Meeting 8 April 2019

Attendance

@kenshino, @atachibana, @softservenet, @milana_cap, @bph, @subrataemfluence, @aion11, @kartiks16, @makewebbetter, @fitehal, @immeet94, @felipeelia, @casiepa

Development Phase 1.5

Until 5.2 is out @clorith is going to be busy with Health Check pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, after which we are planning to re-activate bugscrubs. Meanwhile, all Phase 1.5 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/ issues have to be checked, valid ones sent 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. team and invalid ones closed. Kartik Shukla volunteered to help @milana_cap with this.

Time and date for a temp bugscrub will be published soon.

Content Phase 1.5

Almost all Release Notes (Version Page) were migrated to HelpHub.
Thank you @kartiks16, @thompsqj, @jarretc, @subrataemfluence, @audrasjb

Now we are transferring Codex pages to matched HelpHub Page. Refer below spreadsheet and click below tab. Stats are bottom of the each sheet.
https://docs.google.com/spreadsheets/d/1PeHj7pSFLcdMbIC41JJdzEkl12TJT3mwWyzQv2mi01U/edit#gid=554277336

@atachibana will follow up with @iviolini about the archive page for the Release Notes.

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/ Docs

Besides explanation for each blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., we are missing some basic end user Gutenberg docs. @atachibana will write call for help with this. Here is a document with comments on existing classic editor docs: https://docs.google.com/spreadsheets/d/1PeHj7pSFLcdMbIC41JJdzEkl12TJT3mwWyzQv2mi01U/edit#gid=2125284625

We will keep these pages and create new ones for block editor.

HelpHub Localisation

Technical discussion going on here: https://make.wordpress.org/polyglots/2019/03/27/helphub-localisation-plan-meeting-notes/

Anyone with some tech capabilities or an understanding of the needs of Docs (HelpHub) is welcome to chime in.

HelpHub & Docs Badges

General agreement is published here: https://make.wordpress.org/docs/2019/04/08/summary-for-docs-team-meeting-1-april-2019/

We still need to define details: the amount of contribution needed for Contributor badge, 2 months active contribution (leading a project or part of it) for Team badge, a way we select if multiple people are willing to lead same project or feature..

Docs Contributor badge should be specific for people who write Docs for HelpHub / DevHub or maybe the Docs Handbook. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Inline Docs should get the Core Contributor Badge (this is the current case). If you’ve written code for HelpHub or DevHub – you should get the Meta Contributor badge.

@kenshino will write a separate p2 post about this as soon as @atachibana evaluate the amount of contribution needed for Contributor badge.

Google Season of Docs

If you’d like to volunteer as a mentor, please comment on this post https://make.wordpress.org/docs/2019/04/08/summary-for-docs-team-meeting-1-april-2019/

AOB

@casiepa raised a question about documenting WordPress.tv APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.. He created meta ticket for creating another DevHub handbook where docs for all WordPress APIs will live.

https://meta.trac.wordpress.org/ticket/4376

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

Agenda for HelpHub meeting 8 April 2019

Hello all,

Next HelpHub meeting will happen on

Monday, April 8, 2019, 15:00 UTC
  1. Attendance
  2. Phase 1.5 Check-in
  3. Detailed content discussions
    • Content MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. Check-in (@atachibana)
    • 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/ Docs (@daveryan)
  4. HelpHub localisation
  5. Setup regular development bug scrub
  6. HelpHub & Docs Badges
  7. AOB

Helpful Links

  • HelpHub Staging – https://wp-helphub.com/
  • GitHub repo – https://github.com/WordPress/HelpHub
  • State of HelpHub (read for Phase 2) – https://make.wordpress.org/docs/2018/02/26/state-of-helphub-february-2018/
  • Previous Docs Team minutes – https://make.wordpress.org/docs/2019/04/08/summary-for-docs-team-meeting-1-april-2019/

HelpHub Localisation Plan Meeting

Tuesday, 26th March 2019, at 2PM UTC

Documentation, polyglots and community teams are joining forces in an effort to make localisation come through for HelpHub. The same system could possibly be used for localising Make / Community handbooks.

Detailed explanation can be found here: HelpHub Localisation Plan.

The first meeting will be conducted via Zoom (downloading app is mandatory but registering to the website is not needed). Link for the meeting will be shared afterwards.

Meeting will happen on

Tuesday, March 26, 2019, 14:00 UTC

Everyone interested are welcome to participate.

Summary for HelpHub Team Meeting 25 February 2019

Attendees: @atachibana @softservenet @felipeelia @kartiks16

Phase 1.5 Check-in

Status: https://docs.google.com/spreadsheets/d/1PeHj7pSFLcdMbIC41JJdzEkl12TJT3mwWyzQv2mi01U/edit#gid=554277336
Phase 1.5 Contents were migrated 37/53 (70%).
Version Texts were migrated 48/349 (38%).

If anyone has interests in these activities, please read this document or contact @atachibana https://make.wordpress.org/docs/handbook/helphub/migrating-articles/

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/ User Docs

In previous meeting, we decided to re-use Gutenberg Help contents of WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/. I listed up current HelpHub contents that should be modified to adapt them.
https://docs.google.com/spreadsheets/d/1PeHj7pSFLcdMbIC41JJdzEkl12TJT3mwWyzQv2mi01U/edit#gid=2125284625
Also, we should prepare special pages such as accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) or troubleshooting.

HelpHub localization

@kenshino posted localiation plan of HelpHub at Polyglots
https://make.wordpress.org/polyglots/2019/02/25/helphub-localisation-plan
Any comments and questions are welcome.

Agenda for HelpHub meeting 25 February 2019

Hello all,

Next HelpHub meeting will happen on

Monday, February 25, 2019, 15:00 UTC
  1. Attendance
  2. Phase 1.5 Check-in
  3. Detailed content discussions
    • Content MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. Check-in
    • 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/ User Docs contribution from WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/
  4. HelpHub localisation
    • Draft here – https://docs.google.com/document/d/1d5a64LN564zB-HrxvRr9u1zKepD5yaVYb-cL02r5euQ/edit?ts=5c47e862
  5. AOB

Helpful Links

  • HelpHub Staging – https://wp-helphub.com/
  • GitHub repo – https://github.com/kenshino/helphub
  • State of HelpHub (read for Phase 2) – https://make.wordpress.org/docs/2018/02/26/state-of-helphub-february-2018/
  • Last HelpHub meeting minutes – https://make.wordpress.org/docs/2019/01/28/summary-for-docs-team-meeting-28-january-2019/