chore: Revert updates to honor maintenance mode (#287)

Author: chriswblake

.github/dependabot.yml

@@ -0,0 +1,6 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "monthly"

.github/steps/-step.txt

@@ -0,0 +1 @@
+0

.github/steps/0-welcome.md

@@ -0,0 +1 @@
+<!-- readme -->

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

@@ -0,0 +1,51 @@
+<!--
+  <<< Author notes: Step 1 >>>
+  Choose 3-5 steps for your course.
+  The first step is always the hardest, so pick something easy!
+  Link to docs.github.com for further explanations.
+  Encourage users to open new tabs for steps!
+-->
+
+## Step 1: Add headers
+
+_Welcome to "Communicate using Markdown"! :wave:_
+
+**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:
+
+- 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
+- Sharing snippets of text in [Gists](https://docs.github.com/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)
+
+**What is a _header_?** A header is a larger bit of text at the beginning of a section. There are six sizes.
+
+### Example
+
+```md
+# This is an `<h1>` header, which is the largest
+
+## This is an `<h2>` header
+
+###### This is an `<h6>` header, which is the smallest
+```
+
+#### How it looks
+
+# This is an `<h1>` header, which is the largest
+
+## This is an `<h2>` header
+
+###### This is an `<h6>` header, which is the smallest
+
+### :keyboard: Activity: Edit your file with headers
+
+1. Open a new browser tab, and work on the steps in your second tab while you read the instructions in this tab.
+1. Open the **pull requests** tab.
+1. Click **New pull request**, for the branches to compare, select `base: main` and `compare: start-markdown`.
+1. Click **Create pull request**.
+1. In this pull request, go to the **Files changed** tab. We made an empty file `index.md` for you.
+1. Select **Edit file** from the three dotted **...** menu in the upper right corner of the file view on `index.md`.
+1. On the **Edit file** tab, add a `#`, followed by a **space**, before any content you like to make it an H1 Header. You can add more headers, using one to six `#` characters followed by a **space**.
+1. Above your new content, click **Preview**.
+1. At the bottom of the page, type a short, meaningful commit message that describes the change you made to the file.
+1. Click **Commit 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.

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

@@ -0,0 +1,29 @@
+<!--
+  <<< Author notes: Step 2 >>>
+  Start this step by acknowledging the previous step.
+  Define terms and link to docs.github.com.
+-->
+
+## Step 2: Add an image
+
+_Great job adding headers to the file :sparkles:_
+
+Let's add an image. Include descriptive text in the square brackets. This text is read aloud for people using screen readers. It's also shown at times when your image doesn't display, such as when there's a poor connection. You can see the syntax for images below:
+
+### Example
+
+```md
+![Image of Yaktocat](https://octodex.github.com/images/yaktocat.png)
+```
+
+#### How it looks
+
+<img alt="Image of Yaktocat" src=https://octodex.github.com/images/yaktocat.png width=400>
+
+### :keyboard: Activity: Adding an image
+
+1. As you did before, edit the `index.md` file in this pull request.
+1. In the file, add the correct Markdown for your image of choice. Don't forget to include alt-text!
+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.

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

@@ -1,58 +1,49 @@
-## Step 3: Add a code sample
+<!--
+  <<< Author notes: Step 3 >>>
+  Start this step by acknowledging the previous step.
+  Define terms and link to docs.github.com.
+-->
 
-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.
+## Step 3: Add a code example
 
-> [!TIP]
-> Many programming languages are supported. Try testing out some other file extension types!
+_Great job adding an image to the file :tada:_
 
-### Example: Terminal Command
+Let's add some code blocks. Code blocks can render differently depending on the language.
 
-````md
-```bash
-git clone https://github.com/skills/communicate-using-markdown
+### Example 1
+
+<pre>
+```
+$ git init
+Initialized empty Git repository in /Users/skills/Projects/recipe-repository/.git/
 ```
-````
+</pre>
 
-```bash
-git clone https://github.com/skills/communicate-using-markdown
+#### How it looks
+
+```
+$ git init
+Initialized empty Git repository in /Users/skills/Projects/recipe-repository/.git/
 ```
 
-### Example: Javascript Code
+### Example 2
 
-````md
-```js
+<pre>
+``` javascript
 var myVar = "Hello, world!";
 ```
-````
+</pre>
 
-```js
+#### How it looks
+
+```javascript
 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. 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. 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>
+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.