Learnability: Structured Learning - The Basics --> Create content for 'How does Git work?'

Summary: 'How does Git work?'

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 how Git works to form an accurate mental model. This can help them in learning Git and GitLab. A great example of such content: https://towardsdatascience.com/getting-started-with-gitlab-the-absolute-beginners-guide-ea9e5cadac8b

Supporting research
  • Recent research revealed that users new to GitLab may may not know how Git works. This is particularly true for non-Developers. As a result, they have to search online to understand more about how Git works, 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.

Questions the content should answer

  • "How does Git work?" - Describe how Git works with an example for readers to follow. Ideal to cover several common scenarios. Ex: commit, merge, repositories, branching, etc

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.

  • Content doesn't exist that presently answers the above questions, in a beginner-level manner

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

  • Content needs to be created that answers the basic (but broad) question above

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 Diana Logan