Improve docs experience for Experience Baseline JTBD: Start a GitLab trial

As part of the FY20-Q4 documentation OKR gitlab-design#692 (closed), this issue pertains to a "job to be done" (JTBD) in GitLab--"Start a GitLab trial"--which has been evaluated by UX as part of an Experience Baseline Review.

If you are working on this issue, review the linked OKR and the Experience Baseline Recommendations Handbook page for more detail. Then review the links below, per the OKR instructions.

UX Evaluation issue - gitlab-org/growth/product#166 (closed)
UX Evaluation video - https://youtu.be/ATfiaU5M7X8
UX recommendations issue - gitlab-org/growth&7

Potential doc work - Evaluate if there is potential to improve on the existing GitLab trial documentation (if any).
Technical writer - @rdickenson
Product designer - @kcomoli

Based on the steps in the OKR epic, use the checkboxes to indicate when each step is complete, and use the format below for notes and plans. You are welcome to alternatively link any/all subsections to an additional issue or a Google doc, to work there instead.

  • Review existing info
  • Review SEO
    • Document and improve SEO
  • Consider potential UI doc link
  • Review and improve documentation content
    • Test the instructions
    • Plan documentation improvements/additions
    • Ask questions of and share plans with Product Designer
    • Implement doc changes

Plans & Notes

1. Review existing info

We discovered that GitLab trial information was already found on https://docs.gitlab.com/ee/subscriptions/ -- both how to sign up, and what happens when the trial expires.

2. Review SEO

a. Document and improve SEO

Relevant Google searches (e.g. 'gitlab free trial') all yield https://about.gitlab.com/free-trial/ which is the best place for this.

3. Consider potential UI doc link

Worked on gitlab-org/growth/product#166 (closed)

4. Review and improve documentation content

Determined that no changes were needed

a. Test the instructions

b. Plan documentation improvements/additions

c. Ask questions of and share plans with Product Designer

d. Implement doc changes

Edited by Mike Lewis