Exercise: Communicate using Markdown

[github-actions]

Communicate using Markdown

👋 Hey there @rbkandraden! Welcome to your Skills exercise!

Organize ideas and collaborate using Markdown, a lightweight language for text formatting.

As you complete each step, I will respond in the comments to:

• check your work and give feedback
• share next steps
• occasionally share tips
• congratulate you when you finish!

Good luck and have fun!
- Mona

[github-actions]

Step 1: Add headings

What is Markdown? Markdown is a lightweight syntax for communicating on GitHub. You can format text to add a heading, lists, bold, italics, tables, and many other stylings. You can use Markdown in most places around GitHub such as:

• Comments on issues, pull requests, and discussions
• Files with the .md or .markdown extension
• Snippets of text in Gists

What is a heading? A heading is a larger bit of text at the beginning of a section. There are six sizes.

Example

# This is an `<h1>` heading, which is the largest

## This is an `<h2>` heading

###### This is an `<h6>`heading, which is the smallest

This is an <h1> heading, which is the largest

This is an <h2> heading

This is an <h6> heading, which is the smallest

⌨️ Activity: Create a mardkown file

1. Open a new browser tab, and work on the steps in your second tab while you read the instructions in this tab.

2. In the top navigation, select the Code tab.

3. Create a new branch with the following name:

   start-blog

4. Above the files list, click the Add file button and select Create new file.

5. Use the following file name.

   day-1.md

6. In the editor, on the first line use a level one heading to give the page a title.

   # Daily Learning

7. Add a couple level 2 headings for the names of each of the blog posts.

   ## Morning Planning
   
   ## Review

8. Above the editor, click the Preview toggle to view the rendered version.

9. In the top right, click the Commit changes button and commit directly to the start-blog branch.

10. With our headings created and committed, Mona should be busy reviewing your work and preparing the next steps.

Having trouble? 🤷

• Confirm you are editing the correct file and branch.
• Double check your syntax. The must be a space between the # and first word.

[github-actions]

Please, follow the steps above.
I'll watch your progress in the background to provide feedback. 🧐

[github-actions]

Step 1 - Passed ✅

Status	Description
✅ - Pass	day-1.md file exists
✅ - Pass	One level 1 heading (#) added to day-1.md
✅ - Pass	Two level 2 heading (##) added to day-1.md

[github-actions]

🎉🎉🎉 Nice work! Everything is perfect! 🎉🎉🎉
Preparing content for step 2! One moment... 🤓

[github-actions]

Step 2: Make a list

Markdown supports 3 types of common lists. They include:

• Unordered - Bulleted list
• Ordered - Number list
• Task - Checkbox list

Unordered list

An unordered list is simple to show. Each item is placed on its own line using a -, *, or + character.

- Item 1
- Item 2
- Item 3

• Item 1
• Item 2
• Item 3

Ordered List

A list is changed to ordered by using any number instead of the list character. Notice how markdown automatically handles the counting. Nice!

1. Step 1
1. Step 2
1. Step 3

1. Step 1
2. Step 2
3. Step 3

Task List

A task list is extends the unordered list to use check boxes.
Add empty brackets [ ] for incomplete tasks and filled brackets [x] for complete tasks. Note: The empty required space for empty brackets.

- [x] This task is complete
- [ ] This task is not complete

• This task is complete
• This task is not complete

Tip

Issues and pull requests can use task syntax for conveying progress.

⌨️ Activity: Add ideas and goals to our morning plan

1. On the start-blog branch, open the day-1.md file for editing.

2. Add the following task list below morning planning level two heading to track goals you want to achieve.

   - [ ] Check out the [github blog](https://github.blog/) for topic ideas.
   - [ ] Learn about [GitHub Pages](https://skills.github.com/#first-day-on-github).
   - [ ] Convert my first blog post into an actual webpage.

3. Use the Preview tab to check your Markdown formatting.

4. In the top right, click the Commit changes button and commit directly to the start-blog branch.

5. With our code block committed, Mona should be busy reviewing your work and preparing the next steps.

Having trouble? 🤷

• Confirm you are editing the correct file and branch.
• Double check your syntax. The must be a space inside the [ ] for task lists.

[github-actions]

Please, follow the steps above.
I'll watch your progress in the background to provide feedback. 🧐