Merge pull request #740 from xebia/2-what-is-github.md

expand on what gists actually are and how they are used

Author: barneschism

learn-pr/github/introduction-to-github/includes/2-what-is-github.md

@@ -120,13 +120,42 @@ Congratulations, you just created a new file in your repository! You have also c
 
 Before we review branches and commits in the next unit, let’s quickly review gists, wikis, and GitHub pages because they're similar to repositories.
 
-### What are gists
+### What are gists?
 
-Now that we have a good understanding of repositories, we can review gists. Similarly to repositories, gists are a simplified way to share code snippets with others.
+Gists are a feature of GitHub that allows users to share code snippets, notes, or other small pieces of information in a lightweight and convenient way. They are essentially mini Git repositories, which means you can fork, clone, and version-control them just like a full repository. Gists are particularly useful for sharing quick solutions, configuration files, or examples without the need to create a full repository.
 
-Every gist is a Git repository, which you can fork and clone and be made either public or secret. Public gists are displayed publicly where people can browse new ones as they’re created. Public gists are also searchable. Conversely, secret gists aren't searchable, but they aren’t entirely private. If you send the URL of a secret gist to a friend, they'll be able to see it.
+#### Key Features of Gists:
+1. **Public and Secret Gists**:
+   - **Public Gists**: These are visible to everyone and can be discovered through GitHub's search functionality. They are ideal for sharing code snippets or solutions that you want to make available to the broader community.
+   - **Secret Gists**: These are not searchable or publicly listed, but they are not entirely private. Anyone with the URL can access them. They are useful for sharing code with a limited audience, such as collaborators or friends.
 
-To learn more about gists, see the linked article in our Resources section at the end of this module titled *Creating Gists*.
+2. **Version Control**:
+   - Every change made to a gist is tracked, allowing you to view the history of edits. This makes it easy to revert to a previous version or see how the snippet has evolved over time.
+
+3. **Forking and Cloning**:
+   - Like repositories, gists can be forked and cloned. This allows others to build upon your work or adapt it to their needs.
+
+4. **Embedding**:
+   - Gists can be embedded into websites or blogs, making them a great tool for sharing code examples in tutorials or documentation.
+
+5. **Markdown Support**:
+   - Gists support Markdown formatting, which means you can include rich text, headings, links, and even images alongside your code. This is particularly useful for adding context or explanations to your snippets.
+
+6. **Collaboration**:
+   - While gists are typically used for individual snippets, they can also be shared and collaborated on by multiple users. Forking and commenting on gists enable lightweight collaboration.
+
+#### Use Cases for Gists:
+- Sharing quick code examples or solutions.
+- Storing configuration files or scripts for personal use.
+- Creating templates for commonly used code patterns.
+- Sharing error logs or debugging information with others.
+- Embedding code snippets in blogs, forums, or documentation.
+
+#### Limitations of Gists:
+- Gists are not entirely private, even if marked as secret. Anyone with the URL can access them, so they should not be used for sensitive or confidential information.
+- They are best suited for small snippets or single files. For larger projects or multi-file structures, a full repository is more appropriate.
+
+To learn more about how to create and manage gists, refer to the GitHub documentation in the Resources section of this module or visit the [GitHub Gists documentation](https://docs.github.com/en/github/writing-on-github/creating-gists).
 
 ### What are wikis?