Learnability: Structured Learning - Beyond Basics --> Create content for 'What's this/that? (CI)'

Summary: 'What' are these's this/that?'

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 what some of the navigation items are. This can help them in applying their knowledge of Git and GitLab to their job.

Supporting research
  • Recent research revealed that users new to GitLab may not fully understand how to accurately apply their learnings, thus far, towards the GitLab application/UI. As a result, they have to search online to understand this topic, 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 and existing users better understand the GitLab UI and to use it.

We have to consider: at this point, a new user has gone through the 'Basics' section is now looking through the UI trying to apply that newly gained knowledge by going through the UI of the product. We can guide them through that process by clarifying the purpose of each area without asking the user to learn for themselves through trial and error.

Questions the content should answer

  • "What's CI/CD?" - for this, explain what this is with examples.

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.

  • It seems there's ample content on this topic. We just have to make sure it's being presented for multiple audiences.

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

  • Ensure the content makes sense for new GitLab users (both Developers and non-Developers)

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