GitHub Skills
Course feedback #357
Replies: 19 comments 13 replies
-
|
it's not clear to me what's the url of the created page after going through the tutorial. |
Beta Was this translation helpful? Give feedback.
-
|
how did you solve it |
Beta Was this translation helpful? Give feedback.
-
|
the url is https://(your github user).github.io/skills-github-pages/ |
Beta Was this translation helpful? Give feedback.
-
|
btw, I don't think they really care the tutorial feedback at all, don't waste our time here anymore |
Beta Was this translation helpful? Give feedback.
-
|
thank you so much |
Beta Was this translation helpful? Give feedback.
-
|
Loved it! so easy!!!! Been looking for this for a while! |
Beta Was this translation helpful? Give feedback.
-
|
The tutorial is not explained well and no one here helping in solving issues. |
Beta Was this translation helpful? Give feedback.
-
|
Nice tutorial but I'd also appreciate having it in a written form, preferably one page where I can see all the steps in searchable and skimmable manner. |
Beta Was this translation helpful? Give feedback.
-
|
loved it. thank you! i wanna add about me, tabs, tags etc to do more. where do i start to learn all that? |
Beta Was this translation helpful? Give feedback.
-
|
Using GitHub actions is a poor way to write a tutorial. As @subchannel13 above noted, a single page with all steps would be preferable. As is:
I'd been hoping to teach someone with no programming experience to use GitHub pages. I'm not sure it's a good choice; I've been stuck at step 4 in the tutorial. Presumably I did something wrong, but the site builds OK, so who knows what it was? Combine this with the obsolete information about the (removed) Theme Chooser on https://pages.github.com/ (see "Project Site") yields an overall poor experience for new users to GitHub Pages. |
Beta Was this translation helpful? Give feedback.
-
|
here here! well said couldn't agreee more |
Beta Was this translation helpful? Give feedback.
-
|
wow... i thought it was one of the better ones |
Beta Was this translation helpful? Give feedback.
-
|
Hey! Thanks for the feedback! |
Beta Was this translation helpful? Give feedback.
-
README.md got deployed instead of index.md |
Beta Was this translation helpful? Give feedback.
-
|
What up crew it's ya boy the Ninja-man™! I thought the course was very informative and a must due for any loyal to the open source foil kinda developer!lol obviously I'm kidding little adult and dark humor there but anyways love you guys and hope all is well! Stay clean and keep contributing and special shout out to all my Social Ninja Developers out there, "Halla!"🥷🏻🥳🥳😎🥸🤓🙂 |
Beta Was this translation helpful? Give feedback.
-
Scientist! [ |
Beta Was this translation helpful? Give feedback.
-
|
I liked the tutorial! While unconventional, I like that it used Actions. Good pacing, not too wordy or technical. My background: I've used Pages before, but the tutorial caught my eye. I liked it compared to an out-of-date how-to page. So long as it's future-proof (and maintained), it has my endorsement! |
Beta Was this translation helpful? Give feedback.
-
The tutorial was good, and I got a good understanding of GitHub Pages, but I still feel like I do not understand Jekyll. I am building a portfolio where I want to start blogging can someone help me out with Jekyll |
Beta Was this translation helpful? Give feedback.
-
|
Fun course. Github is a magic wonderland. Wow. |
Beta Was this translation helpful? Give feedback.
-
|
I got stuck on step 4. couldn't get past it. added my title and date.. added some other stuff and committed. I find that if you don't do exactly what is asked for it doesn't proceed.. well that is fine. but there needs to be some there should be a way to just manually push forward. a button that say I givee up show me how and move forward mike |
Beta Was this translation helpful? Give feedback.
-
|
Hey! Thanks for the feedback! |
Beta Was this translation helpful? Give feedback.
-
|
It also seems that none of these comments are being looked at by anyone at github.. not respenses to issues or questions |
Beta Was this translation helpful? Give feedback.
-
|
Hey! Thanks for the feedback! |
Beta Was this translation helpful? Give feedback.
-
|
Really liked it. Didn't have any problems. But I've already been using GitHub for a while, so not a total newbie. |
Beta Was this translation helpful? Give feedback.
-
|
I like small-bite-size course like this. It helped me get familiar with GitHub and gain a little bit of confidence in myself. I noticed that some other skill courses have the green mark to check for progress. If we can have that in this Making GitHub Pages tutorial, that would be nice. Awesome job! Appreciate the team behind this course. |
Beta Was this translation helpful? Give feedback.
-
|
The course was helpful. I would suggest one additional instruction at the very end.
|
Beta Was this translation helpful? Give feedback.
-
|
Hey! Thanks for the feedback! |
Beta Was this translation helpful? Give feedback.
-
|
A good practical introduction. I think it could have explained conventions better (e.g. Why is there an underscore before posts? Why is the date then hyphen separated and not underscore separated? Etc.) |
Beta Was this translation helpful? Give feedback.
-
|
This isn't the kind of computing that I grew up with, and I don't like it yet. I'm finding the automation flaky. When I forked the repository, the platform encouraged me to write rules to limit change to it. I wrote a rule that allowed nothing, except for me. That jammed the course from updating README.md, which was the path to the next step in the course. I created my page on the my_pages branch, so I could see the effect of changes as I went. After the merge, I was encouraged to delete my_pages. When I experimentally accepted the encouragement, my github page has correctly gone away. In another repository, I tried to create a theme for the github pages, without having the Jekkle machinery installed, which predictably had no effect. This course does not tell me how to install that machinery. It is possible to get to the errors, in the Actions subsection, where the erroring actions are performed. This is not explained in the course. I mangled a directory name and needed to rename it. There is no direct way to do that, other than by moving files from one directory to another, until it's empty. This is not explained here: (https://docs.github.com/en/repositories/working-with-files/managing-files/renaming-a-file), the option has changed name, and the procedure for moving the file seems to require already knowing that .. represents a parent directory in unix-like systems. I think that I would have preferred a non-procedural list of all of the things that have to be got right, in order for the page to appear, and an only slightly procedural account of where to look for error messages. |
Beta Was this translation helpful? Give feedback.
-
|
Total Github beginner -- I found the tutorial very helpful! the beginning said it'll take me less than an hour and it was really closer to 30 minutes. The steps are clear and as long as I followed them exactly, everything worked out. When I didn't do it exactly (jumped the gun with merging for example) it was a good lesson in problem solving because the solution could be inferred from the instructions. |
Beta Was this translation helpful? Give feedback.
-
|
Not a bad course, I enjoyed. |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
-
We'd love to hear what you thought of this course! Please leave your feedback below and let us know!
Beta Was this translation helpful? Give feedback.
All reactions