So while you're going through this course, you might encounter situations where you get stuck for some reason.
- Maybe you have some doubt about a topic that we've just discussed.
- Maybe you're having trouble setting up your developer environment.
- Maybe you're having trouble executing some command or some piece of code.
- Or maybe you have doubts about some related topic that we haven't covered in this course.
- It really could be anything.
If you have a question, please don't hesitate to ask.
One of the main advantages of being a student in this course is that you can get help from experts easily.
So let's make it clear how you can get help in two parts:
First, where to ask questions, and second, how to ask questions.
Let's start with the first part - where to ask questions.
Show the user dashboard, highlighting the links mentioned below.
The Web Development community within Pupilfirst School is the place to go if you need a coach or a teaching assistant to answer any question you have. You can access the community from your Dashboard - the link will be shown in the course card, or via the Communities tab up top.
Show the Discuss tab of an example target.
You can also browse questions that were asked previously about certain lessons via the Discuss tab, that takes you to the community as well.
Show an example post in the community.
The community is structured as an online forum - it's an excellent space for asking longer, more detailed questions, and to get answers from coaches, or from your peers.
You might have noticed that we've sent you an invite to join a Discord Server. Discord is great for quick chats with other students who are also taking the course. But, if you have questions that you want answered by either coaches or teaching assistants, please create a post in the Web Development community, not on Discord.
Onto the second part of the video - how to ask for help.
When asking questions, the main thing you want to make sure is to provide as much information as possible. We'll cover this topic in more detail in WD201 - the next course, but for now, I'll give you a few examples. If you encountered an error while trying to run a program, you should definitely share the exact error message and the command that you ran to get the error. If there are any extra logs, share those as well. Sometimes if the problem is visual in nature, screenshots also help. If you're trying to diagnose a specific section of code, share that section of code, and describe what's going wrong. In general, there's no such thing as too much information when diagnosing issues, more is almost always better.
Finally, when asking or answering questions or generally interacting with other people in the community, or in the Discord, please make sure you abide by the community guidelines - a link to the same will be provided below this video. Let's try to make sure that everbody feels welcome in asking and answering questions.
We're looking forward to seeing your queries. Bye for now!