Original issue Elchi3/mdn-doc-tests#145.

Check anchor links on the current page and throw an error if those sections do not exist.

Link to #nope should throw:

<h2 id="yay">yay</h2>
<a href="#yay">Link to yay</a>

<a href="#nope">Link to nope</a>

(Probably a regression from changing the selector)

If you have elements inside <pre> (such as <var>, <em>, etc), they are matched as well and the test tells you that there is a class missing.

See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/getTimezoneOffset$edit where this should be just fine:

<pre class="syntaxbox">
  <var>dateObj</var>.getTimezoneOffset()
</pre>

Currently the process to add a new rule is a bit tedious and I often happen to forgot one step, so I would like to ensure that all the steps are properly done by documenting them and checking them using Travis CI.

• Document the process to add a new rule
• Check that all necessary elements are there using Travis CI.

Current behavior:
There is no test regarding potential link duplicates.

Expected behavior:
There should be a test to provide informations regarding duplicates links for SEO purposes.

Plan to action:
This is only a suggested plan to action

1. Add a test getting the number of links for a same URL in an article.
2. Define thresholds to return INFO, ERRORS or WARNINGS depending of the amount of link.
3. Implement the feature.

Actions pending:

• Confirm the plan to action.
• Define thresholds.
• Implement the linting feature.
• Test the linting features.

Original issue: Elchi3/mdn-doc-tests#128.

If you check against an en-US article, let the doc-linter emit...

• a warning if the page contains the words "obvious(ly)", "simply", "easily", "clearly", or "just".
• a warning if the page contains the word "I" (the pronoun).
• an error if the page contains wrong capitalization for the words "JavaScript", "ECMAScript", "HTML", "Firefox", "SpiderMonkey" ... (likely to be extended)
• an error if the page contains the words: "he", "she", "whitelist" or "blacklist".

Original issue Elchi3/mdn-doc-tests#22

There are some rules, which only target the English version of an article. They don't work on localized pages. These rules are:

Old 'en/' URLs
Summary heading
'Example:' headings
API syntax headlines

Those should be adjusted to also work correctly on localizations or be hidden on them.

Sebastian

Original issue: Elchi3/mdn-doc-tests#208.

Guides like Grids within the Learning Area have a summary at the bottom of the article, which provide a conclusion of the previous text.

Those occurrences of 'Summary' headlines must not be marked as errors.

Sebastian

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please see Mozilla-GitHub-Standards or email [email protected].

(Message COC001)

Original issue: Elchi3/mdn-doc-tests#173

A test should be added checking whether a <pre> tag has eval as class name. Instead of eval people should use brush:.... For blocks not needing syntax highlighting they should use brush: plain.

This test could be added to the existing 'pre-without-class' test.

Sebastian

Remove all of these from https://github.com/mdn/doc-linter-rules/blob/master/lib/invalid-macros.js
The only valid macro should be {{compat}} as it uses the BCD project.

      "compatandroid",
      "compatchrome",
      "compatchromemobile",
      "compatedge",
      "compatgeckodesktop",
      "compatgeckofxos",
      "compatgeckomobile",
      "compatibilitytable",
      "compatie",
      "compatnightly",
      "compatno",
      "compatopera",
      "compatoperamobile",
      "compatsafari",
      "compatunknown",
      "compatversionunknown",
      "compatwebkit",

Original issue: Elchi3/mdn-doc-tests#129

The MDN writing style guide says that two spaces should be used in code examples instead of tabs.

So, there should be a test added, which checks that.

Sebastian

Following the conversation in #2 with @Elchi3 regarding the folder name "lib" being potentially ambiguous it would be interesting to change it from "lib" to "rules".

Steps:

• Move the code from lib to rules
• Edit index to import from rules instead of lib
• Edit each tests to import from rules instead of lib

Add a short readme to explain the repository, and link to related repositories.

See original issue: Elchi3/mdn-doc-tests#137

Need to have limits on when large image sizes trigger a warning and extra-large images trigger an error.

Original issue Elchi3/mdn-doc-tests#143.
Test if sources are HTTPS (e.g. images) to prevent mixed content.

I believe images and things we embed are already https pretty much everywhere, but it looks like we are not actually testing it.

https://twitter.com/DevDocs/status/718123621491847168