Course feedback

[cmwilson21]

We'd love to hear what you thought of this course! Please leave your feedback below and let us know!

[varmor]

It was great, this course was easy to follow, and provided a good amount of knowledge about markdown files, and its syntax, It could have been little comprehensive, and covered all aspects of markdown, but it still a good course to begin with.

[wbryceangell]

I've been using GitHub for work for years now and did not realize that I could use markdown in issues and pull requests! Thanks for this course!

[anhnlh]

A good starter for markdown, but I suggest some examples of well-known and well-documented repositories as part of the course to show learners best practices.

[exc304]

I'm always a fan of learning more. Do you happen to have any repos you'd recommend?

[vukasinterzic]

Good starter course on Markdown ❤️

But I feel that both Learn modules and this exercise are missing some very basic and often needed code blocks, such as tables, links and escape characters.

[exc304]

Ohhh yeah, tables would really be a good one to cover in an intro course. They're a liiiiiitle tricky to get right the first couple times, but once you do, it's easy to get better at making them.

This course did cover links, SORT OF. Not directly. With the Step 2, for Images. I think this course could be enhanced by including links in the same step with images. Or just point out they're similar.

[eoyugi]

i loved it because it was both challenging and inspiring ,my added knowledge was to see that i could host markdown as a live website

[rishabdesai]

The course proved incredibly helpful in teaching me the markdown syntax and pull-request concepts.
Initially, I found the first chapter a bit challenging to grasp, requiring several readings to understand the steps thoroughly.
However, once I got past that hurdle, the rest of the chapters was much easier to follow.

I would recommend incorporating small screenshots for each step in the first chapter to make it more accessible for beginners.
Nevertheless, thank you for providing such a valuable course.

[exc304]

This course provides a very approachable method to learning the basics of markdown. Not only that, it takes you seamlessly through the paces of common GitHub activities like creating a repo, branching, editing files, commits, and merges.

And, if you have a keen eye, you can see and understand what those GitHub actions are doing as you both contribute to your PR in real time. 😉

👏 well done GitHub

Tips:

As long as you follow the instructions to use separate browser tabs for the instructions and editing the index.md file in the beginning + throughout, you will be successful. I personally prefer separate browser windows (instead of tabs), that way I am able to work split screen.

I'm somewhat experienced with markdown already from collaborating on project teams over the years. I enjoy creating Pull Request templates for my projects, so it is nice to see these items covered in this course, with practical examples and reasons to use them. I know many dev teams would benefit from taking this course. Especially if it's just for fun!

Feedback:

While stepping through some of the instructions, I noticed there are other ways of accomplishing a task in a step. For example, Images. You can totally use the Copy/Paste function and GitHub automatically generates the markdown for you, e.g., [image](url)
I did that very thing with the screenshot I provided above. 😊

💞 I really enjoyed this experience overall. Thank you.

[Plexusphere]

This course is incredibly good. I just recently came to GitHub and I had fun attending this course, the instructions were clear and I learned a lot. Thanks for this opportunity! ❤️

[mjbear]

Overall I'm really pleased with this course.

Some of the steps in Step 1 could use some more details to avoid confusion. For example a note to submit the PR before the edit functionality is available. In my frustration I ended up merging the PR which threw things off -- it would be helpful if there was a warning not to merge the PR.

In Step 2, it could be helpful to emphasize in this pull request (maybe even add an emoji). Possibly also a reminder note in the line for Commit your changes to the start-markdown branch

Update: To others, the key is the Github Actions workflows which hint at which branch they hook in on. Live and learn!

[unstoppableayush]

It was very good.

[TheGreatRandino]

Complete trash!!!!!! and waste of time!!!!!!!!!!!!!!!
what's the meaning of ''' javascript ?? I tried ` `` html and saw no difference
Then I tried viewing as web page
What's next?
You can enable GitHub Pages and see your Markdown file as a website!
Under your repository name at the upper right, click ⚙️ Settings.
Then on the lower left, click Pages in the Code and automation section.
In the GitHub Pages section, ensure "Deploy from a branch" is selected never saw this........
from the Source drop-down menu, and then select main from the Branch drop-down menu as your GitHub Pages publishing source.
Click the Save button.
Wait about 30 seconds then refresh the page. When you see "Your site is published at ..." you can click on the link to see your published site.

[Erick-Porto]

This course is incredibly good. Recently, I decided to improve my knowledge about github and learn more about and the course taught me a lot. This course is incredibly good. Recently, I decided to improve my knowledge about github and learn more about and the course taught me a lot. But how do I finish in the "Learn new skills" tab of github education?