Skip to content

Document edcast support

Samantha Lee requested to merge document-edcast-support into master

Why is this change being made?

This MR will commit the support path for 3 audiences on GitLab Learn - team members, customers, and wider community.

The biggest question right now is community support. I'm unsure if we should be sending community members to submit support tickets at all. I'm discussing with support in this issue to determine how free and paid customers can be sorted using this support ticket method. It is also unclear who will be answering questions about GitLab Learn for the wider community. cc @Josh_Zimmerman

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)
Edited by Samantha Lee

Merge request reports