Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update _config.yml #4

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update _config.yml #4

wants to merge 2 commits into from

Conversation

201758
Copy link
Owner

@201758 201758 commented Mar 5, 2022

No description provided.

@github-learning-lab
Copy link

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

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.

Copy link

@github-learning-lab github-learning-lab bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 201758-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 201758-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.

Copy link

@github-learning-lab github-learning-lab bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant