Initial commit

Author: danielalpizarcer-rgb

.github/steps/1-add-headings.md

@@ -0,0 +1,73 @@
+## Step 1: Add headings
+
+**What is _Markdown_?** Markdown is a [lightweight syntax](https://docs.github.com/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-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](https://docs.github.com/issues/tracking-your-work-with-issues/about-issues), [pull requests](https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests), and [discussions](https://docs.github.com/discussions/collaborating-with-your-community-using-discussions/about-discussions)
+- Files with the `.md` or `.markdown` extension
+- Snippets of text in [Gists](https://docs.github.com/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)
+
+**What is a _heading_?** A heading is a larger bit of text at the beginning of a section. There are six sizes.
+
+### Example
+
+```md
+# 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 markdown file
+
+1. Open a new browser tab, and work on the steps in your second tab while you read the instructions in this tab.
+
+1. In the top navigation, select the **Code** tab.
+
+1. Create a new branch with the following name:
+
+   ```md
+   start-blog
+   ```
+
+1. Above the files list, click the **Add file** button and select **Create new file**.
+
+1. Use the following file name.
+
+   ```md
+   day-1.md
+   ```
+
+1. In the editor, on the first line use a level one heading to give the page a title.
+
+   ```md
+   # Daily Learning
+   ```
+
+1. Add a couple level 2 headings for the names of each of the blog posts.
+
+   ```md
+   ## Morning Planning
+
+   ## Review
+   ```
+
+1. Above the editor, click the **Preview** toggle to view the rendered version.
+
+1. In the top right, click the **Commit changes** button and commit directly to the `start-blog` branch.
+
+1. With our headings created and committed, Mona should be busy reviewing your work and preparing the next steps.
+
+<details>
+<summary>Having trouble? 🤷</summary><br/>
+
+- Confirm you are editing the correct file and branch.
+- Double check your syntax. The must be a space between the `#` and first word.
+
+</details>

.github/steps/2-make-a-task-list.md

@@ -0,0 +1,77 @@
+## Step 2: Make a list
+
+Markdown supports 3 types of common lists. They include:
+
+- [Unordered](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#lists) - Bulleted list
+- [Ordered](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#lists) - Number list
+- [Task](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#task-lists) - Checkbox list
+
+### Unordered list
+
+An unordered list is simple to show. Each item is placed on its own line using a `-`, `*`, or `+` character.
+
+```md
+- 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!
+
+```md
+1. Step 1
+1. Step 2
+1. Step 3
+```
+
+1. Step 1
+1. Step 2
+1. 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.
+
+```md
+- [x] This task is complete
+- [ ] This task is not complete
+```
+
+- [x] This task is complete
+- [ ] This task is not complete
+
+> [!TIP]
+> Issues and pull requests can use task syntax for [conveying progress](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/about-tasklists).
+
+### :keyboard: Activity: Add ideas and goals to our morning plan
+
+1. On the `start-blog` branch, open the `day-1.md` file for editing.
+
+1. Add the following task list below **morning planning** level two heading to track goals you want to achieve.
+
+   ```md
+   - [ ] 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.
+   ```
+
+1. Use the **Preview** tab to check your Markdown formatting.
+
+1. In the top right, click the **Commit changes** button and commit directly to the `start-blog` branch.
+
+1. With our code block committed, Mona should be busy reviewing your work and preparing the next steps.
+
+<details>
+<summary>Having trouble? 🤷</summary><br/>
+
+- Confirm you are editing the correct file and branch.
+- Double check your syntax. The must be a space inside the `[ ]` for task lists.
+
+</details>

.github/steps/3-add-a-code-example.md

@@ -0,0 +1,58 @@
+## Step 3: Add a code sample
+
+Let's learn about [code blocks](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#quoting-code) and [syntax highlighting](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks) based on the language.
+
+> [!TIP]
+> Many programming languages are supported. Try testing out some other file extension types!
+
+### Example: Terminal Command
+
+````md
+```bash
+git clone https://github.com/skills/communicate-using-markdown
+```
+````
+
+```bash
+git clone https://github.com/skills/communicate-using-markdown
+```
+
+### Example: Javascript Code
+
+````md
+```js
+var myVar = "Hello, world!";
+```
+````
+
+```js
+var myVar = "Hello, world!";
+```
+
+### :keyboard: Activity: Adding a code example
+
+1. On the `start-blog` branch, open the `day-1.md` file for editing.
+
+1. Below **Review** level two heading add the following entry recording an awesome code snippet you just learned from the GitHub Blog.
+
+   ````md
+   Convert an image or video from dark mode to light mode using [ffmpeg](https://www.ffmpeg.org)
+
+   ```bash
+   ffmpeg -i input.mp4 -vf "negate,hue=h=180,eq=contrast=1.2:saturation=1.1" output.mp4
+   ```
+   ````
+
+1. Use the **Preview** tab to check your Markdown formatting.
+
+1. In the top right, click the **Commit changes** button and commit directly to the `start-blog` branch.
+
+1. With our code block committed, Mona should be busy reviewing your work and preparing the next steps.
+
+<details>
+<summary>Having trouble? 🤷</summary><br/>
+
+- Confirm you are editing the correct file and branch.
+- Double check your syntax. A code block is three backticks ` ``` ` not three apostrophes `'''`
+
+</details>

.github/steps/4-add-an-image.md

@@ -0,0 +1,74 @@
+## Step 4: Add an image
+
+Let's learn how to include [images in markdown](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#images), using relative urls, absolute urls, sizing, and basic positioning.
+
+### Regular Markdown
+
+Images can be displayed by providing a relative URL to a file in the repository or an absolute URL (to anywhere on the internet).
+
+The descriptive text in the square brackets is displayed if the image is unable to load, and it is also read aloud for people using screen readers.
+
+Note: Markdown syntax doesn't provide an option to change the image size.
+
+### Example
+
+Relative URL to an image in the repository:
+```md
+![Mona the Octocat](myrepo/original.png)
+
+```
+
+Absolute URL to an image on the internet:
+```md
+![Mona the Octocat](https://octodex.github.com/images/original.png)
+```
+
+<img alt="Mona the Octocat" src="https://octodex.github.com/images/original.png" width="200">
+
+### Simple HTML
+
+You will often find the need to reduce the size of an image or simply place it next to some text. Regular HTML syntax provides some additional flexibility.
+
+- The `alt` field specifies the alternative text.
+- The `src` field specifies the source url of the image.
+- A `width` and/or `height` field can be used to specify the size in pixels.
+- The `align` field allows setting a position (`left`, `right`)
+
+```md
+<img alt="Mona the Octocat" src="https://octodex.github.com/images/original.png"
+width="200" align="right">
+```
+
+### :keyboard: Activity: Add some decoration
+
+Our blog post is quite simple right now. Let's add some decoration.
+
+1. On the `start-blog` branch, open the `day-1.md` file for editing.
+
+1. Insert an image below the **Morning Planning** level 1 heading.
+
+   ```md
+   ![Cloudy morning](https://octodex.github.com/images/cloud.jpg)
+   ```
+
+1. Use the **Preview** tab to check your Markdown formatting.
+
+   - Notice the image is too large for our purpose.
+
+1. Replace the simple markdown version with an HTML version that includes size and position info. Much better!
+
+   ```md
+   <img alt="Cloudy morning" src="https://octodex.github.com/images/cloud.jpg" width="100" align="right">
+   ```
+
+1. In the top right, click the **Commit changes** button and commit directly to the `start-blog` branch.
+
+1. With our image added and committed, Mona should be busy reviewing your work and preparing the next steps.
+
+<details>
+<summary>Having trouble? 🤷</summary><br/>
+
+- Confirm you are editing the correct file and branch.
+- Double check your syntax. An HTML image tag must start with `img` and include the `src` property.
+
+</details>

.github/steps/5-merge-your-pull-request.md

@@ -0,0 +1,17 @@
+## Step 5: Finish work
+
+With our first blog post finished, let's merge it into the main branch.
+
+### :keyboard: Activity: Merge blog post
+
+1. In the top navigation, select the **Pull requests** tab.
+
+1. Create a new pull request, using `main` and `compare:start-blog` for the branch details.
+
+1. (Optional) Set a clear title and description for the pull request.
+
+1. Scroll down and click the **Merge** button.
+
+1. Click **Merge pull request**.
+
+1. With the pull request merged, Mona will prepare the final review. Nice work! You are done! 🎉

.github/steps/x-review.md

@@ -0,0 +1,21 @@
+## Review
+
+<img src=https://octodex.github.com/images/chellocat.jpg alt=celebrate width=150 align=right>
+
+_Congratulations! You've completed this exercise!_
+
+Here's a recap of the tasks you've accomplished in this exercise:
+
+1. You added headings to organize content.
+1. You added a tasks list to a plan.
+1. You saved a code snippet in your review for future use.
+1. You added an image to your plan to make it prettier.
+1. And finally, you created finished a blog post using Markdown syntax.
+
+### What's next?
+
+- Take another [GitHub Skills exercise](https://learn.github.com/skills).
+  - Continue with the [GitHub Pages](https://github.com/skills/github-pages) exercise to share your blog posts as an actual webpage.
+- Learn more about [Markdown](https://docs.github.com/github/writing-on-github).
+- Read the GitHub [Getting Started docs](https://docs.github.com/get-started).
+- To find projects to contribute to, check out [GitHub Explore](https://github.com/explore).

.github/workflows/0-start-exercise.yml

@@ -0,0 +1,72 @@
+name: Step 0
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: write
+  actions: write
+  issues: write
+
+env:
+  STEP_1_FILE: ".github/steps/1-add-headings.md"
+
+jobs:
+  start_exercise:
+    if: |
+      !github.event.repository.is_template
+    name: Start Exercise
+    uses: skills/exercise-toolkit/.github/workflows/start-exercise.yml@v0.6.0
+    with:
+      exercise-title: "Communicate using Markdown"
+      intro-message: "Organize ideas and collaborate using Markdown, a lightweight language for text formatting."
+
+  post_next_step_content:
+    name: Post next step content
+    runs-on: ubuntu-latest
+    needs: [start_exercise]
+    env:
+      ISSUE_URL: ${{ needs.start_exercise.outputs.issue-url }}
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Get response templates
+        uses: actions/checkout@v4
+        with:
+          repository: skills/exercise-toolkit
+          path: exercise-toolkit
+          ref: v0.6.0
+
+      - name: Build comment - add step content
+        id: build-comment
+        uses: skills/action-text-variables@v2
+        with:
+          template-file: ${{ env.STEP_1_FILE }}
+          template-vars: |
+            login: ${{ github.actor }}
+            full_repo_name: ${{ github.repository }}
+
+      - name: Create comment - add step content
+        run: |
+          gh issue comment "$ISSUE_URL" \
+            --body "$ISSUE_BODY"
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          ISSUE_BODY: ${{ steps.build-comment.outputs.updated-text }}
+
+      - name: Create comment - watching for progress
+        run: |
+          gh issue comment "$ISSUE_URL" \
+            --body-file "exercise-toolkit/markdown-templates/step-feedback/watching-for-progress.md"
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Enable next step workflow
+        run: |
+          gh workflow enable "Step 1"
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}