Skip to content
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

Add learning area guidelines #37792

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

chrisdavidmills
Copy link
Contributor

Description

This PR is my first attempt at writing new guidelines to cover the updated Learn web development section, partner links, etc.

Motivation

Additional details

Related issues and pull requests

@chrisdavidmills chrisdavidmills requested review from a team as code owners January 24, 2025 17:01
@chrisdavidmills chrisdavidmills requested review from hamishwillee and removed request for a team January 24, 2025 17:01
@chrisdavidmills chrisdavidmills marked this pull request as draft January 24, 2025 17:01
@github-actions github-actions bot added the Content:Meta Content in the meta docs label Jan 24, 2025
@github-actions github-actions bot added the size/m [PR only] 51-500 LoC changed label Jan 24, 2025
Copy link
Collaborator

@hamishwillee hamishwillee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For some reason it is asking me for a review on this draft. Adding this comment to move it off my queue. If you need me to look at it, specifically re-request.

@chrisdavidmills chrisdavidmills requested review from hamishwillee and removed request for hamishwillee January 28, 2025 09:23
@chrisdavidmills
Copy link
Contributor Author

For some reason it is asking me for a review on this draft. Adding this comment to move it off my queue. If you need me to look at it, specifically re-request.

That's fine mate. There is no reason you need to look at this one, although obviously, you can if you want to.

I've tried removing you, but it has you stuck at the top of the reviewers list, even thought you are not checked. Really weird.


- Won't add these links in a way that compromises the integrity of MDN's content and is openly spammy; only where we feel they are genuinely useful.
- Will always make sure a free option is available beside anything that is paywalled. In many cases, we've managed to convince our partners to make content available for free that was previously paywalled.
- Will clearly mark partner content with a "MDN Curriculum partner" label, so you can clearly tell them apart from other links.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the "learn web development (LWD)" area and "curriculum" are two separate areas of the site. Using curriculum on the LWD pages is a bit confusing.

Are they a partner or a sponsor? Curriculum, LWD, or both? Maybe we should go with "MDN sponsored link" ?

It would be helpful to have instructions here as to the order of links in a list of links:

  1. internal content,
  2. free content, with a note that partners should be listed first in this category, and must be identified as a sponsored link.
  3. mixed free/paywall content - again, noting partners should be listed first in this group and must be identified as a sponsored link.

And a note that we do not link to sites where all content is paywalled (and if this changes, sponsors first)

MDN Learn Web Development (also known as Learn)'s target audience is people who are not expert front-end developers — this includes students, junior or trainee web developers, hobbyists, and teachers looking for best practice guidance on what to teach their students.

> [!NOTE]
> We are avoiding using the word "beginner", as that term is subjective — for example, some beginners to web development may have previous programming experience in non-web languages and therefore may find certain topics easy, whereas others may find certain topics quite difficult. In addition, someone who has worked as a web designer professionally for many years might be an expert in HTML and CSS, but still be a beginner in JavaScript.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I avoid the term 'junior' for these reasons and use the term 'beginner' precisely for the last point in this sentence

> Try this...
```

- **Challenges**: Learn content includes challenges periodically to test that the reader understands the topics they have learnt about before moving on to the next article. These are currently written in a few different styles, for example see [Challenge: Structuring a page of content](/en-US/docs/Learn_web_development/Core/Structuring_content/Structuring_a_page_of_content) and [Test your skills: HTML images](/en-US/docs/Learn_web_development/Core/Structuring_content/HTML_images/Test_your_skills:_HTML_images), but we intend to improve the consistency and experience her in the future.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Challenges**: Learn content includes challenges periodically to test that the reader understands the topics they have learnt about before moving on to the next article. These are currently written in a few different styles, for example see [Challenge: Structuring a page of content](/en-US/docs/Learn_web_development/Core/Structuring_content/Structuring_a_page_of_content) and [Test your skills: HTML images](/en-US/docs/Learn_web_development/Core/Structuring_content/HTML_images/Test_your_skills:_HTML_images), but we intend to improve the consistency and experience her in the future.
- **Challenges**: Learn content includes challenges periodically to test that the reader understands the topics they have learnt about before moving on to the next article. These are currently written in a few different styles, for example see [Challenge: Structuring a page of content](/en-US/docs/Learn_web_development/Core/Structuring_content/Structuring_a_page_of_content) and [Test your skills: HTML images](/en-US/docs/Learn_web_development/Core/Structuring_content/HTML_images/Test_your_skills:_HTML_images), but we intend to improve the consistency and experience of these in the future.

- The fundamental technologies required at the start of a web developer's journey in our [Core modules](/en-US/docs/Learn_web_development/Core).
- "Second wave" topics representing useful next steps for relative beginners to move on to once they've mastered the Core modules, in our [Extensions modules](/en-US/docs/Learn_web_development/Extensions).

Learn is not intended to be the place on MDN for introductory content on _all_ topics. This means that niche topics such as MathML and Web Games, and advanced or specialist topics such as regular expressions, performance testing, WebRTC, and WebGPU, do not belong on Learn.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Learn is not intended to be the place on MDN for introductory content on _all_ topics. This means that niche topics such as MathML and Web Games, and advanced or specialist topics such as regular expressions, performance testing, WebRTC, and WebGPU, do not belong on Learn.
Learn is not intended to be the place on MDN for introductory content on _all_ topics. This means that niche topics such as MathML and Web Games, and advanced or specialist topics such as regular expressions, performance testing, WebRTC, and WebGPU, do not belong in Learn.


Learn is not intended to be the place on MDN for introductory content on _all_ topics. This means that niche topics such as MathML and Web Games, and advanced or specialist topics such as regular expressions, performance testing, WebRTC, and WebGPU, do not belong on Learn.

If you do not see a topic covered on Learn and you think it should be covered, don't just try to add it — discuss it with us first (see [Suggesting content](/en-US/docs/MDN/Writing_guidelines/What_we_write#suggesting_content)).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you do not see a topic covered on Learn and you think it should be covered, don't just try to add it — discuss it with us first (see [Suggesting content](/en-US/docs/MDN/Writing_guidelines/What_we_write#suggesting_content)).
If you do not see a topic covered in Learn and you think it should be covered, don't just try to add it — discuss it with us first (see [Suggesting content](/en-US/docs/MDN/Writing_guidelines/What_we_write#suggesting_content)).

@github-actions github-actions bot added the merge conflicts 🚧 [PR only] label Jan 31, 2025
Copy link
Contributor

This pull request has merge conflicts that must be resolved before it can be merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:Meta Content in the meta docs merge conflicts 🚧 [PR only] size/m [PR only] 51-500 LoC changed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants