Learnability: Structured Learning - The Basics --> Create content for 'GitLab vs. GitHub'

Summary: 'GitLab vs. GitHub'

The content topic addresses the need to provide very basic information for users new to Git and GitLab by providing them with essentials to help them understand the key differences between GitLab vs GitHub. This can help them in learning GitLab.

Supporting research
  • Recent research revealed that users new to GitLab who have some experience with GitHub may need help in bridging the gap between the two. Presently, they have to search online to understand more about the delta between the two, which may or may not be helpful, depending on what they find. We can help here by: 1) making it easy to locate this content, 2) provide a simple narrative to answer the questions outlined below, and 3) cater the content to align with our messaging of GitLab, if appropriate. Providing this information can help new users understand: the key differences between the two, what the similarities are, etc.

Questions the content should answer

  • "What the difference between GitLab vs. GitHub?" - This can be a broad answer, including aspects like community contributions, to open source, to features, to the DevOps lifecycle, to terminology, etc.
  • "What are the similarities between GitLab vs. GitHub" - This helps answer the other side of the question. We should not assume people know this, so let's be clear in calling out what's the same, in terms of features, capabilities, etc.
  • "How does my existing knowledge of GitHub apply to GitLab?" - This is a common question. If we can explicitly answer this, it'd be helpful for new GitLab users to differentiate what they already know vs. what the need to learn.

Existing content

This would be content that currently exists on the given content topic. In cases where existing content exists, we can just leverage all or some of the existing content.

Examples of other content that answers the questions

Content gaps

These are areas in the existing content that aren't answering the main questions the content topic aims to address.

  • There wasn't GitLab hosted content that addressed the questions.
  • Ideal if content isn't marketing related, used to inform a company/software purchaser which to go with. Content should be aimed towards our users.

What needs to be done?

This section describes the work that needs to be done for this content topic. This could be reusing or adjusting existing content, or creating new content to address any content gaps

How will this content be accessed?

How users access the content is something that needs to be considered. This section documents how we designed the content to be accessed by our users. For example: the tutorials page, YouTube searching, etc

  • XYZ

Where will this content reside?

Related to how content will be accessed, it's also important to understand where this content will reside. For example: YouTube, the docs site, etc.

  • XYZ

Link(s) to the final content

Please link the final content (in the form of MRs) to this issue.

Edited by Adam Smolinski