Our Learn web development pages get over a million views per month, and have active forums where people go to ask for general help, or request that their assessments be marked. We’d love some help with answering posts, and growing our learning community.
In the MDN learning forum, there are two main types of post that we’d like you to help out with answering:
- General questions about web development.
- Specific questions asking for help or assessment with the skill tests and assessments that appear on the Learn web development section on MDN.
- Helping people with their code problems is a great way to learn more about web technologies — as you research a solution and write an answer to someone's question, you will gain a deeper understanding of the subject, and improve your skills.
- As you get more involved in the MDN community, you'll get to know Mozilla staff and other community members, giving you a valuable network of contacts for getting help with your own issues and increasing your visibility.
- Helping to answer coding questions is largely its own reward, but it will also demonstrate your expertise in web technologies and possibly even help you with your course, or job opportunities.
- The language of the forum is English — you should have a reasonable proficiency with the English language, but it really doesn't need to be perfect. We have people from all over the world visiting our forums, and we want everyone who visits us to feel as comfortable and included as possible.
- First of all, sign up for an MDN account, if you don’t already have one. You don’t absolutely need to do this to help in the learning area, but it will be useful in the long run.
- Also sign up for Mozilla Discourse, if you haven’t already.
- Have a look at Learn web development section and gain a basic level of familiarity with what’s there, if you haven't already (see the Structure of the MDN Learning Area section below for help).
- Have a look at the learning forum and see if there are any posts that have no replies — this is the best place to start.
- Hint: If you can’t find any that have no replies, check some of the other ones that were recently updated and see if you can add anything useful that has not already been said.
- If the post you are replying to is a general ask for help, reply to them, and give them as much help as you’ve got time for.
- If the post you are replying to is requesting an assessment for one of the "test your skill"/"assessment" tasks:
- Identify which article/task is being assessed, and find the associated marking guide for it. It is totally OK to ask the person who submitted the post if they can give you the link to the assessment/skill test.
- Identify the person’s code — they should give it to you in the form of a codepen/jsfiddle/jsbin link, or similar. If they don’t provide it in a form that is easy to assess, it is perfectly OK to ask them to put it in codepen, jsfiddle, or similar.
- A common problem is when people post their code directly into a discourse message — discourse renders HTML elements and turns quotes into smartquotes, which breaks code. It is much better to get it sent over as a URL to a shareable code editor app.
- Read through the code and assess it
- Does it work, and does it give you the result that it should give?
- If not, why doesn’t it work?
- Are there any tips you can give the person to make the code better (more efficient, best practice, etc.)?
- Give them a report on how they did:
- Some of the marking guides suggest a marking scheme with points for each bit of the question, but you don’t need to be that accurate.
- If the person did great except for a few nitpicks, tell them the nitpicks, but give them lots of praise too.
- If the person was nearly there but it wasn’t quite right, tell them they did great, but then share the fixes they'd need to make it work, and perhaps even link to the marking guide so they can see what we did.
- If the person is not really anywhere near a working solution, be kind and encouraging and try to give them a few clues as to what direction they should go in. Give them another chance to try to do it better.
- If you need assistance with anything, ask for help in the MDN Web Docs chat room on Matrix.
Important: Above all, be patient, be friendly, be kind. Remember — most of these folks are beginners.
When helping answer questions related to the Learn web development section of MDN, it is a good idea to have a look around it and gain a basic level of familiarity with what’s there.
- Have a look through the page structure in general.
- Especially look at the types of assessments available,
- Have a look at the GitHub repos associated with the learning area (most of the files are available in https://github.com/mdn/learning-area/, some are in https://github.com/mdn/css-examples/tree/master/learn). Most of the examples learners will want help with are contained here.
- Each assessment/skill test has an associated marking guide and recommended solution available, to help you assess their work.
- There are patterns that make it easier to find these resources, for example:
It will seem tricky to navigate around all this to begin with, but you’ll find it easier in time, as you become more familiar with the exercises.