Update quickstart footers in getting started category

[emilyistoofunky]

What article on docs.github.com is affected?

• "Set up Git"
• "Create a repo
• "Fork a repo"
• "Be social"

What part(s) of the article would you like to see updated?

Problem: Each article in the Quickstart map topic (https://docs.github.com/en/github/getting-started-with-github/quickstart) has a footer that links to each article in the category. These footers are inconsistently formatted and their purpose is unclear. A new user may think they have to go through these articles in a prescribed order or be confused that each footer asks “What do you want to do next?” when they do not know what they want to do.

• The footer also links to https://github.bokerqi.topmunity/ and implies that it’s a social hangout area of the site, this should be updated

Solution:

• Create a content design plan using this template and post it in this issue.
• Update the footer to give the quickstart audience a better understanding of what to click next.
• Remove incorrect/outdated information.

Additional information

This issue is for a special project and is not currently available for contributors to work on.

[codewithdev]

@janiceilene I would like to work on this.

[janiceilene]

Thanks @codewithdev 🎉

[codewithdev]

Just curious 🤔 to know about the Content Design Template before working on this particular issue. I found that the link mentioned in the Issue (https://github.com/github/docs-content/blob/main/contributions/open-source-content-design-template.md) is not working.

[janiceilene]

Whoops, sorry about that broken link @codewithdev! Here's the template:

We use a content design process to create project plans that clearly communicate user needs and product goals, and outline how documentation for a specific project will meet both. Creating a project plan also ensures that we aren't duplicating any content or efforts, and that the right places are updated.

## Content plan

Briefly summarize the problem and its impact on GitHub's users, or describe the new content and the problem it solves for customers.
- What's the goal of documentation for this project?
- What will customers need from docs to be successful?

### Audiences

Describe the groups of people who will be using these docs.

### Documentation plan

Create a detailed list of the articles to create or update. Tip: Make sure to consider audit log and permissions content.

### Questions

If you have any questions after writing a plan, ask them here!

[codewithdev]

Content Plan

The Footer created for each Map topic in the Quickstart articles is inconsistently formatted. Generally, the user may find the footer articles as another category of topics that is already present in the given article or they will get confused what they should do next.
However, Structuring the footer in such a way that each linked content would help users to explore more about GitHub and its product. It should be consistent from the user's perspective and must focus on what information users can expect from the article.

Audiences

For New users, QuickStart topics may sound insightful and quite informative. They can use it to set up Git, fork a repo, and find more information on how they can collaborate with others.

Documentation Plan

Here is the set of changes that I prefer to frame the footers in Map topics.

• Footers in Set up Git may contain information about Creating a Repo or alternatively, user can Fork a Repository to contribute or understand the codebase of projects.
• Create a Repo demonstrate how repositories are created. Another way to create a repository that enables the user to contribute locally from the computer is to Clone a Repo.
• Summarizing how users can Connect with people and collaborating with others.
• Summarizing how GitHub Community Support can be a great platform to discuss and get the help of others.

[janiceilene]

👏 Congrats on your first content design @codewithdev! I'll triage this for review ⚡

[felicitymay]

Hi @codewithdev - thanks for writing a content design plan for this issue and for your pull request to update the docs accordingly 💖

As you have already raised a pull request with your changes based on this plan, I'm going to go and review the pull request instead of the plan. 👀

---

General background, for future reference.

The aim of writing a content design plan is to explain the changes that you plan to make to the docs. This allows you to talk through the changes before you edit the docs. That way we can ensure that you don't waste time making changes that we can't accept. Usually, you would not start to edit the docs until your plan has been approved.

We've only recently started asking OS contributors if they'd like to design content changes, so the expected workflow might not be clear in our contributing docs. I'll ask our OS contributors team to take a look at this.

[codewithdev]

Hi @codewithdev - thanks for writing a content design plan for this issue and for your pull request to update the docs accordingly 💖

As you have already raised a pull request with your changes based on this plan, I'm going to go and review the pull request instead of the plan. 👀

The aim of writing a content design plan is to explain the changes that you plan to make to the docs. This allows you to talk through the changes before you edit the docs. That way we can ensure that you don't waste time making changes that we can't accept. Usually, you would not start to edit the docs until your plan has been approved.

@felicitymay Thanks for the review ✨. I'll make sure to wait first until my content design plan gets approved.