Skip to content

Commit 0f69c66

Browse files
Update to 2 in STEP and README.md
1 parent 7fe2240 commit 0f69c66

File tree

2 files changed

+23
-18
lines changed

2 files changed

+23
-18
lines changed

.github/steps/-step.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
1
1+
2

README.md

Lines changed: 22 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -14,29 +14,34 @@ _Create a site or blog from your GitHub repositories with GitHub Pages._
1414
</header>
1515

1616
<!--
17-
<<< Author notes: Step 1 >>>
18-
Choose 3-5 steps for your course.
19-
The first step is always the hardest, so pick something easy!
20-
Link to docs.github.com for further explanations.
21-
Encourage users to open new tabs for steps!
17+
<<< Author notes: Step 2 >>>
18+
Start this step by acknowledging the previous step.
19+
Define terms and link to docs.github.com.
20+
Historic note: previous version checked for empty pull request, changed to the correct theme `minima`.
2221
-->
2322

24-
## Step 1: Enable GitHub Pages
23+
## Step 2: Configure your site
2524

26-
_Welcome to GitHub Pages and Jekyll :tada:!_
25+
_You turned on GitHub Pages! :tada:_
2726

28-
The first step is to enable GitHub Pages on this [repository](https://docs.github.com/en/get-started/quickstart/github-glossary#repository). When you enable GitHub Pages on a repository, GitHub takes the content that's on the main branch and publishes a website based on its contents.
27+
We'll work in a branch, `my-pages`, that I created for you to get this site looking great. :sparkle:
2928

30-
### :keyboard: Activity: Enable GitHub Pages
29+
Jekyll uses a file titled `_config.yml` to store settings for your site, your theme, and reusable content like your site title and GitHub handle. You can check out the `_config.yml` file on the **Code** tab of your repository.
3130

32-
1. Open a new browser tab, and work on the steps in your second tab while you read the instructions in this tab.
33-
1. Under your repository name, click **Settings**.
34-
1. Click **Pages** in the **Code and automation** section.
35-
1. Ensure "Deploy from a branch" is selected from the **Source** drop-down menu, and then select `main` from the **Branch** drop-down menu.
36-
1. Click the **Save** button.
37-
1. Wait about _one minute_ 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.
38-
> Turning on GitHub Pages creates a deployment of your repository. GitHub Actions may take up to a minute to respond while waiting for the deployment. Future steps will be about 20 seconds; this step is slower.
39-
> **Note**: In the **Pages** of **Settings**, the **Visit site** button will appear at the top. Click the button to see your GitHub Pages site.
31+
We need to use a blog-ready theme. For this activity, we will use a theme named "minima".
32+
33+
### :keyboard: Activity: Configure your site
34+
35+
1. Browse to the `_config.yml` file in the `my-pages` branch.
36+
1. In the upper right corner, open the file editor.
37+
1. Add a `theme:` set to **minima** so it shows in the `_config.yml` file as below:
38+
```yml
39+
theme: minima
40+
```
41+
1. (optional) You can modify the other configuration variables such as `title:`, `author:`, and `description:` to further customize your site.
42+
1. Commit your changes.
43+
1. (optional) Create a pull request to view all the changes you'll make throughout this course. Click the **Pull Requests** tab, click **New pull request**, set `base: main` and `compare:my-pages`.
44+
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.
4045

4146
<footer>
4247

0 commit comments

Comments
 (0)