Skip to content

Conversation

github-learning-lab[bot]
Copy link

Step 3: Add headers

As you saw on your website, your portfolio doesn't have much content yet. We'll learn how to edit the file in this pull request to incorporate some Markdown headers.

You can see an example of a header at the top of this page! Just like in HTML, a header is a larger bit of text at the beginning of a section. There are six sizes.

Example

# 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

In issues, pull requests, and comments, you can use the text formatting toolbar.

The toolbar isn't available everywhere. When you edit a file, you must type the # symbols manually.

⌨️ Activity: Edit your file with headers

  1. In this pull request, click the Files changed tab.
  2. To edit the file titled _includes/01-name.md, click the small pencil ✏️ or select "Edit file" from the three dotted ... menu in the upper right corner of the file view.
  3. On the Edit file tab, add a #, followed by a space, before the content to make it an H1 Header. You can add more headers, using one to six # characters followed by a space.
  4. Above your new content, click Preview changes.
  5. At the bottom of the page, type a short, meaningful commit message that describes the change you made to the file.
  6. Click Commit changes.

Watch below for my response.

Added name
@github-learning-lab
Copy link
Author

You've made a change to this file, but I don't see a header yet. Add another commit with a header. You can continue to make commits on a branch even after you open a pull request.

⌨️ Activity: Add a header

  1. Click the "Files changed" tab.
  2. Scroll to find the _includes/01-name.md.
  3. Click the 📝 pencil icon.
  4. Add a header by including a # hash followed by a space.
  5. Scroll to the bottom and commit your changes to your branch.

If you would like assistance troubleshooting, 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!

Copy link
Owner

@FuckStickFunFuck FuckStickFunFuck left a comment

Choose a reason for hiding this comment

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

Changed Name

@FuckStickFunFuck
Copy link
Owner

Changed Name added header

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.

2 participants