Update _config.yml

[asama1]

No description provided.

[github-learning-lab]

It looks like your pull request description is empty, @asama1.

Did you know? By adding keywords to your pull request, you can automatically close issues.

For example, if you type closes #2 in your pull request description, the open issue will close when this exercise is complete! For more keywords that you can use to close issues, see “Closing issues with keywords".

If you would like assistance troubleshooting the issue you are encountering, create a post on the GitHub Community board. You might also want to search for your issue to see if other people have resolved it in the past.

---

Check below for next steps.

[github-learning-lab]

It looks like you changed your theme, but for this activity we want to use minima.

⌨️ Activity: Change the theme to minima

Let's change the theme to minima:

1. At the top of this Pull Request, click the Files changed tab.
2. Click the icon to enter edit mode and change the theme: to minima.
3. Scroll to the bottom of the window to create a commit.
4. Enter a commit message then click Commit changes.

Don't worry, if you don't like this theme you can always change it later.

If you would like assistance troubleshooting the issue you are encountering, create a post on the GitHub Community board. You might also want to search for your issue to see if other people have resolved it in the past.

---

Watch below for my next comment.

[github-learning-lab]

It looks like your pull request description is empty, @asama1.

Did you know? By adding keywords to your pull request, you can automatically close issues.

For example, if you type closes #2 in your pull request description, the open issue will close when this exercise is complete! For more keywords that you can use to close issues, see “Closing issues with keywords".

If you would like assistance troubleshooting the issue you are encountering, create a post on the GitHub Community board. You might also want to search for your issue to see if other people have resolved it in the past.

---

Check below for next steps.

[github-learning-lab]

Step 5: Create a blog post

⚠️ Do not merge yet! ⚠️

This pull request looks great so far. ✨ You've just edited the _config.yml file! We have some more work to do to create your blog site. You can continue to make commits on your asama1-patch-1 branch and the pull request will update automatically.

⌨️ Activity: Add some content to your blog

Shortcut Note: Click this link to automatically complete steps 1-4.

1. On the "Code" tab, select your asama1-patch-1 branch.

2. Click Create new file.

3. Name the file _posts/YYYY-MM-DD-title.md.

4. Replace the YYYY-MM-DD with today's date, and change the title of your first blog post if you'd like. Note: If you do edit the title, make sure there are hyphens between your words.

   • If your blog post date doesn't follow the correct date convention, you'll receive an error and your site won't build. For more information, see "Page build failed: Invalid post date".

5. Type a quick draft of your blog post. Remember, you can always edit it later.

6. Commit your changes to your branch.

---

Watch below for my response.

[github-learning-lab]

Checking your post

@asama1 I see you created a file, but there are a few things we need to address!

Take a look at your file and make sure it meets the following requirements:

• It is in the _posts directory
• The filename starts with the correct date formatting: YYYY-MM-DD
• The filename includes a post title
• The filename uses the .md extension
• The filename follows Jekyll's specific filename requirements.

⌨️ Activity: Edit your file

1. Click the "Files Changed" tab in this pull request.
2. Click on the pencil icon on the right side of the screen.
3. Make adjustments based on the above errors.
4. Scroll to the bottom, and commit your changes.

If you would like assistance troubleshooting the issue you are encountering, create a post on the GitHub Community board. You might also want to search for your issue to see if other people have resolved it in the past.

---

Watch below for my response.

[github-learning-lab]

Step 6: Add blog post metadata

Now that you've created your Jekyll blog post file, we can add syntax to it. The syntax Jekyll files use is called YAML front matter. It goes at the top of your file and looks something like this:

---
title: "Welcome to my blog"
date: 2019-01-20
---

This example adds a title and date to your blog post. There are other useful things you could add here in the future like layouts, categories, or any other logic that is useful to you. For more information about configuring front matter, see the Jekyll front matter documentation.

⌨️ Activity: Add Front Matter to your Blog Post

1. Click the "Files Changed" tab in this pull request.

2. There are two files in the "Files Changed" tab, the _config.yml file and the _posts/YYYY-MM-DD-title.md file. Make sure to edit the file in the _posts folder.

3. Click on the icon to edit on the right side of the screen.

4. Type the following content at the top of your blog post:

   ---
   title: "YOUR-TITLE"
   date: YYYY-MM-DD
   ---
   

5. Replace YOUR-TITLE with the title for your blog post.

6. Replace YYYY-MM-DD with today's date.

7. Commit your changes to your branch.

---

Watch below for my response.

[github-learning-lab]

Checking your front matter

It looks like there may be some errors in your front matter. Take a look at your front matter and make sure the following is true:

• You used dashes on the first and final line
• You added a page title surrounded in quotes
• You added a date using the correct format

The YAML front matter should be at the top of your blog post file and should look something like this:

---
title: "Your blog post title"
date: YYYY-MM-DD
---

⌨️ Activity: Edit your blog post

1. Click the "Files Changed" tab in this pull request.
2. Scroll past the config file, and find the file that you created.
3. Click on the pencil icon on the right side of the screen.
4. Make adjustments based on the above errors.
5. Scroll to the bottom, and commit your changes.

If you would like assistance troubleshooting the issue you are encountering, create a post on the GitHub Community board. You might also want to search for your issue to see if other people have resolved it in the past.

---

Watch below for my response.

[github-learning-lab]

Checking your front matter

It looks like there may be some errors in your front matter. Take a look at your front matter and make sure the following is true:

• You used dashes on the first and final line
• You added a page title surrounded in quotes
• You added a date using the correct format

The YAML front matter should be at the top of your blog post file and should look something like this:

---
title: "Your blog post title"
date: YYYY-MM-DD
---

⌨️ Activity: Edit your blog post

1. Click the "Files Changed" tab in this pull request.
2. Scroll past the config file, and find the file that you created.
3. Click on the pencil icon on the right side of the screen.
4. Make adjustments based on the above errors.
5. Scroll to the bottom, and commit your changes.

If you would like assistance troubleshooting the issue you are encountering, create a post on the GitHub Community board. You might also want to search for your issue to see if other people have resolved it in the past.

---

Watch below for my response.

[asama1]

Checking your front matter

It looks like there may be some errors in your front matter. Take a look at your front matter and make sure the following is true:

• You used dashes on the first and final line
• You added a page title surrounded in quotes
• You added a date using the correct format

The YAML front matter should be at the top of your blog post file and should look something like this:

---
title: "Your blog post title"
date: YYYY-MM-DD
---

⌨️ Activity: Edit your blog post

1. Click the "Files Changed" tab in this pull request.
2. Scroll past the config file, and find the file that you created.
3. Click on the pencil icon on the right side of the screen.
4. Make adjustments based on the above errors.
5. Scroll to the bottom, and commit your changes.

If you would like assistance troubleshooting the issue you are encountering, create a post on the GitHub Community board. You might also want to search for your issue to see if other people have resolved it in the past.

Watch below for my response.

done