feat: Migrate exercise to issue-based flow (skills#274)

* feat: Initial migration with draft content (github-education-experiences#1)

* Add readme and start exercise workflow

* fix: remove extra file

* feat: Add draft step 1

* feat: Add draft step 2

* feat: Add draft step 3

* fix: typos

* feat: Add draft step 4

* feat: Add draft step 5 and review

* feat: Reorder steps 2 and 4

* feat: Rename blog-day-1.md to day-1.md

* feat: Add missing links

* feat: Wording adjustements from review

* feat: Change copy exercise URL

* feat: Rename step 1 files

* chore: Bump exercise toolkit version

* fix: incorrect workflow name

* feat: Add paths filter to triggers

* feat: Show checking work as new comment

* fix: incorrect variable name

* chore: Wording tweaks

* feat: Add help to end of each step

* fix: Remove paths filter from start exercise

* chore: wording tweaks from practice run

* fix: The `-` symbol seems to be unsupported by action-keyphrase-checker

* fix: incorrect file name

* fix: incorrect grading check

* fix: broken step 5 workflow

* chore: Wording tweaks

* Minor wording tweaks

* Minor wording tweaks after test run

* chore: Wording tweak

* fix: Change copy exercise url to skills org

---------

Co-authored-by: Aleksander Fidelus <63016446+FidelusAleksander@users.noreply.github.com>

Author: chriswblake

.github/steps/-step.txt

@@ -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 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.
+
+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/0-welcome.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/1-add-headers.md

@@ -1,49 +1,58 @@
-<!--
-  <<< Author notes: Step 3 >>>
-  Start this step by acknowledging the previous step.
-  Define terms and link to docs.github.com.
--->
+## Step 3: Add a code sample
 
-## Step 3: Add a code example
+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.
 
-_Great job adding an image to the file :tada:_
+> [!TIP]
+> Many programming languages are supported. Try testing out some other file extension types!
 
-Let's add some code blocks. Code blocks can render differently depending on the language.
+### Example: Terminal Command
 
-### Example 1
-
-<pre>
-```
-$ git init
-Initialized empty Git repository in /Users/skills/Projects/recipe-repository/.git/
+````md
+```bash
+git clone https://github.com/skills/communicate-using-markdown
 ```
-</pre>
+````
 
-#### How it looks
-
-```
-$ git init
-Initialized empty Git repository in /Users/skills/Projects/recipe-repository/.git/
+```bash
+git clone https://github.com/skills/communicate-using-markdown
 ```
 
-### Example 2
+### Example: Javascript Code
 
-<pre>
-``` javascript
+````md
+```js
 var myVar = "Hello, world!";
 ```
-</pre>
+````
 
-#### How it looks
-
-```javascript
+```js
 var myVar = "Hello, world!";
 ```
 
 ### :keyboard: Activity: Adding a code example
 
-1. As you did before, edit the file in this pull request.
-1. In the file, add the correct Markdown for a code example of your choice.
+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. Commit your changes.
-1. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.
+
+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>