Skip to content

Improve user experience with direct transfer documentation

Daphne Kua requested to merge dkua1-master-patch-209e into master

What does this MR do and why?

A prospect is moving from GitLab self-managed to GitLab.com and they were not sure how to get started with the importing using Direct Transfer documentation. See Slack (internal link) or the second question of the screenshot: image

This MR:

  • Define a clear section on "Getting started" and placing the import steps under the section.
  • Move non-critical things to know about the feature after the "Getting started" section.
  • Create a new troubleshooting page for the troubleshooting section so that the feature page is not lengthy with information (Section on cancelling a running import is moved to the troubleshooting page). Related MR to add the page to navbar: gitlab-docs!4734 (closed).

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After
https://docs.gitlab.com/ee/user/group/import Main page: https://main-ee-150607.docs.gitlab-review.app/ee/user/group/import/index.html, Troubleshooting page: https://main-ee-150607.docs.gitlab-review.app/ee/user/group/import/import_troubleshooting.html

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Edited by Daphne Kua

Merge request reports