-
Notifications
You must be signed in to change notification settings - Fork 0
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
Getting Started with GitHub #1
Comments
Step 1: Create a Task ListA task list creates checkboxes for people with access 📖in a repository to check off. They're very useful for tracking issues and pull requests. If you include a task list in the body of an issue or pull request, you'll see a progress indicator in your issue list. Watch out! The syntax for task lists is very specific. Be sure to include the spaces where required, or else they won't render. Example markup
Rendered
⌨️ Activity: Add a comment
For a printable version of the steps in this course, check out the Quick Reference Guide. Watch below your comment for my response.
|
|
Step 2: Turn on GitHub PagesNicely done @jlind23! Now let's turn our focus to the content of your portfolio. Because this portfolio will display as a static web page, you'll need to enable GitHub Pages. ⌨️ Activity: Enable GitHub Pages
Return to this issue for next steps. |
Welcome to your repository!
In this repository 📖, you’ll learn how to write with Markdown 📖, a simple and widely used markup language for formatting text. Here, you’ll start building a static webpage for your customized portfolio.
What is Markdown?
Markdown is a lightweight syntax for communicating on GitHub, and many other websites. You can format words as bold or italic, add images, and create lists. Markdown is regular text combined with a few non-alphabetic symbols, such as
#
or*
. You can use Markdown with the formatting toolbar in issues 📖 and pull requests 📖, or you can type the syntax.You can use Markdown most places around GitHub:
.md
or.markdown
extensionFor more information, see “Writing on GitHub” in the GitHub Help.
Let's get started!
The text was updated successfully, but these errors were encountered: