Summary for Helphub Meeting August 2

Attendance

We had a great turn out this meeting – @justingreerbbi @atachibana @normalize @ankitguptaindia @bravokeyl @juhise @greensteph @sarassassin @carlalberto @Kenshino @samuelsidler @hardeepasrani @anevins attended.

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 Updates

A reminder was posted to use the [code] shortcode for all code examples. This is to keep a consistent look through Helphub & DevHub. Old Codex styles should be retired. See https://make.wordpress.org/docs/handbook/helphub/migrating-articles/ about the [[Code]] shortcode.

@atachibana has finished migrating all WordPress version articles. In addition, he has also provided a direction on how we can back-link to other locale codex articles with the 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/ pull request #45. Keeping other locale’s Codex Articles alive is something we have to keep in mind as there are no real translation alternatives for 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/ as of writing. Questions to this directive can be posted to the Github PR.

@juhise has been tasked alongside @ankitguptaindia to make the current Google Spread Sheet that tracks migration and editing up to date and accurate.

@justingreerbbi has started with migration as well

Design Updates

@greensteph and @sarassasin will be working on creating proper style guides that will be used by all articles so that they all maintain a consistent look. These style guides will be posted on the Helphub Handbook

Development Updates

@justingreerbbi will work on submitting a pull request for the read time issues (at time of writing, he has already done so).

@bravokely is working on the responsive styles

@carlalberto will finalise the homepage layout alongside the WordPress versions archive template.

Table of Contents will have it’s functionality copied over from the handbooks

Project Discussions

The Role of Helphub (expanded & explained)

The specific idea is that HelpHub will be laid infront of the forums.

Possibly in the manner of WordPress.org/support (where /support will become helphub’s frontpage) and articles are at WordPress.org/support/articles.

The forums will be at WordPress.org/support/forums

We want people to search through quality articles, and find their own help. And if none are available, then post in the forums, possibly through prompts on our part

Props to @samuelsidler for actually putting that into an actionable idea

Voting Functionality & how it relates to writing better articles*

There was a discussion on the validity of the comment box with the voting functionality. While it gives the ability for users to give useful feedback about the article, it can also be potentially abused and we may simply not have the manpower to sieve through the comments and follow up. Either way, @greensteph and @sarassasin are looking into the 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. aspects of this issue. The Github issue will be used for further discussions.

Acknowledgements

We want to acknowledge the contributors to the articles and this can possibly be tracked for awarding the Doc Contributor badge. @samuelsidler provided a quick mockup so we can see how it might be.

Helphub – Contributors

As we reached the end of our scheduled 1 hour meeting, we have postponed the rest of the topics to the next meeting.

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

#summary