Jon (Kenshino) 8:21 am on November 1, 2018  

Call for Volunteers – HelpHub Migration

Hello!

As you might know from our meeting updates – HelpHub has taken awhile to finally materialise. One of the hurdles was working out a migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. plan. Unfortunately, because of 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/’s unique setup, we were not able to get things automated or even use WordPress’ import mechanisms.

This means that we actually need to specifically do manual migrations from the Staging site – wp-helphub.com to the Production spot WordPress.org/support

How are we doing it?

Specifically – we are doing the following

  1. Use the Copy All Content function of the 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/ editor on an article on the Staging site
  2. Paste it the content onto the Production siteProduction Site A production site is a live site online meant to be viewed by your visitors, as opposed to a site that is staged for development or testing.
  3. Do the same for the title and check the correct taxonomies
  4. In the case that it’s still using a Classic 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’ll have to switch it to Gutenberg blocks
  5. Ensure that all media used (pdfs, images etc) are downloaded and re-uploaded back to WordPress.org/support
  6. Check it for irregularities
  7. Save the draft

You might be able to appreciate that it is a pretty tedious process. By the time you read this post, we should be up to 30 of 170 articles completed. Another 140 articles is a lot to migrate for a team of 5.

Why the rush?

We want HelpHub to be ready for the Gutenberg team to drop in their user documentation. Given that WordPress 5.0 is designated to ship November 19, we don’t have a lot of time left.

We don’t want to leave users in the cold. And you could help us.

What can I do?

If you have some copy pasting skills, a keen eye for detail and an hour free over the next 2 weeks; you can help us!

Drop @atachibana (who’s the Content Lead) a line with your wordpress.org account and registered e-mail address. He will sort you out with the correct access and the know how.

If you have any questions, just ask in #docs on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Reference

P.S. If you received this call of volunteers earlier, we accidentally published it earlier!