build: lint Markdown (#416)

.markdownlint.json

@@ -0,0 +1,4 @@
+{
+  "extends": "@electron/lint-roller/configs/markdownlint.json",
+  "no-shortcut-reference-links": false
+}

.markdownlintignore

@@ -0,0 +1,2 @@
+docs/**
+node_modules/**

README.md

@@ -58,7 +58,7 @@ This repository contains the code for two related things:
 
 The content of this repository is organized as follows:
 
-```
+```text
 └─ root
     |
     ├─ .github/workflows → The definitions for the GitHub actions

blog/10-years-of-electron.md

@@ -94,7 +94,7 @@ maintainers. What is each Working Group (WG) responsible for nowadays?
 Around the same time we shifted to the governance model, we also moved Electron's ownership from
 GitHub [to the OpenJS Foundation](https://www.electronjs.org/blog/electron-joins-openjsf).
 Although the original core team still works at Microsoft today, they are only a part of a larger
-group of collaborators that form Electron governance.
+group of collaborators that form Electron governance.[^2]
 
 While this model isn’t perfect, it has suited us well through a global pandemic and ongoing
 macroeconomic headwinds. Going forward, we plan on revamping the governance charter to

blog/electron-13-0.md

@@ -56,7 +56,7 @@ More information about these and future changes can be found on the [Planned Bre
 - Added new `session.storagePath` API to get the path on disk for session-specific data.[28866](https://github.com/electron/electron/pull/28866)
 - Added support for passing DOM elements over the context bridge. [#26776](https://github.com/electron/electron/pull/26776)
 - Added `process.uptime()` to sandboxed renderers. [#26684](https://github.com/electron/electron/pull/26684)
-- Added missing fields to the parameters emitted as part of the `context-menu `event.[#26788](https://github.com/electron/electron/pull/26788)
+- Added missing fields to the parameters emitted as part of the `context-menu` event.[#26788](https://github.com/electron/electron/pull/26788)
 - Added support for registering Manifest V3 extension service workers.
 - Added ‘registration-completed’ event to ServiceWorkers. [#27562](https://github.com/electron/electron/pull/27562)
 

blog/jasper.md

@@ -59,7 +59,7 @@ Once Jasper is configured, the following screen appears. From left to right, you
 
 This "stream" is the core feature of Jasper. For example, if you want to see "issues that are assigned to @zeke in the electron/electron repository", you create the following stream:
 
-```
+```text
 repo:electron/electron assignee:zeke is:issue
 ```
 

blog/new-website.md

@@ -165,7 +165,6 @@ Thank you!
 
 [atom]: https://atom.io
 [cask]: https://caskroom.github.io
-[crowdin.com/project/electron]: https://crowdin.com/project/electron
 [crowdin]: https://crowdin.com/project/electron
 [electron/electron-apps]: https://github.com/electron/electron-apps
 [electron/electron-i18n]: https://github.com/electron/electron-i18n#readme

blog/s3-bucket-change.md

@@ -15,12 +15,12 @@ Electron is changing its primary S3 bucket, you may need to update your build sc
 
 A significant amount of Electron's build artifacts are uploaded to an S3 bucket called `gh-contractor-zcbenz`. As part of ongoing infrastructure/ownership migrations that started way back in 2020, we will be changing everything that used `gh-contractor-zcbenz` from its old home in S3 to a new storage system hosted at `https://artifacts.electronjs.org`. The path prefix that most of our assets use is changing slightly as well. Examples are included below:
 
-**Before:** https://gh-contractor-zcbenz.s3.amazonaws.com/atom-shell/dist/v17.0.0/node.lib  
+**Before:** https://gh-contractor-zcbenz.s3.amazonaws.com/atom-shell/dist/v17.0.0/node.lib
 **After:** https://artifacts.electronjs.org/headers/dist/v17.0.0/node.lib
 
 The important things here are the **Hostname** changed and the `/atom-shell` **prefix** changed. Another example, this time for debug symbols:
 
-**Before:** https://gh-contractor-zcbenz.s3.amazonaws.com/atom-shell/symbols/path/to/symbol.pdb  
+**Before:** https://gh-contractor-zcbenz.s3.amazonaws.com/atom-shell/symbols/path/to/symbol.pdb
 **After:** https://artifacts.electronjs.org/symbols/path/to/symbol.pdb
 
 Again, the hostname changed and the `/atom-shell` prefix was changed.

blog/website-hiccups.md

@@ -41,7 +41,7 @@ there's an Electron app for that, too.
 Check out [devdocs-app](https://electronjs.org/apps/devdocs-app)
 on the Electron site.
 
-[![](https://user-images.githubusercontent.com/8784712/27121730-11676ba8-511b-11e7-8c01-00444ee8501a.png)](https://electronjs.org/apps/devdocs-app)
+[![devdocs-app](https://user-images.githubusercontent.com/8784712/27121730-11676ba8-511b-11e7-8c01-00444ee8501a.png)](https://electronjs.org/apps/devdocs-app)
 
 If you like to install apps without using your mouse or trackpad, give
 [Electron Forge](https://electronforge.io/)'s `install` command a try:

blog/webview-fix.md

@@ -16,12 +16,12 @@ A vulnerability has been discovered which allows Node.js integration to be re-en
 
 An application is affected if _all_ of the following are true:
 
-1.  Runs on Electron 1.7, 1.8, or a 2.0.0-beta
-2.  Allows execution of arbitrary remote code
-3.  Disables Node.js integration
-4.  Does not explicitly declare `webviewTag: false` in its webPreferences
-5.  Does not enable the `nativeWindowOption` option
-6.  Does not intercept `new-window` events and manually override `event.newGuest` without using the supplied options tag
+1. Runs on Electron 1.7, 1.8, or a 2.0.0-beta
+2. Allows execution of arbitrary remote code
+3. Disables Node.js integration
+4. Does not explicitly declare `webviewTag: false` in its webPreferences
+5. Does not enable the `nativeWindowOption` option
+6. Does not intercept `new-window` events and manually override `event.newGuest` without using the supplied options tag
 
 Although this appears to be a minority of Electron applicatons, we encourage all applications to be upgraded as a precaution.
 

package.json

@@ -19,8 +19,10 @@
     "write-translations": "docusaurus write-translations",
     "write-heading-ids": "docusaurus write-heading-ids",
     "update-l10n-sources": "ts-node scripts/update-l10n-sources.ts",
-    "lint": "prettier . --check && eslint \"src/**/*.{js,jsx,ts,tsx}\" \"scripts/**/*.{js,ts}\"",
-    "lint:fix": "prettier . --write && eslint \"src/**/*.{js,jsx,ts,tsx}\" \"scripts/**/*.{js,ts}\" --fix",
+    "lint:eslint": "eslint \"src/**/*.{js,jsx,ts,tsx}\" \"scripts/**/*.{js,ts}\"",
+    "lint:markdown": "electron-markdownlint \"**/*.md\"",
+    "lint": "prettier . --check && npm run lint:eslint && npm run lint:markdown",
+    "lint:fix": "prettier . --write && npm run lint:eslint --fix && npm run lint:markdown --fix",
     "test": "jest",
     "pre-build": "ts-node ./scripts/pre-build.ts",
     "governance": "node ./scripts/governance.js",
@@ -78,6 +80,7 @@
     "@docusaurus/module-type-aliases": "^2.2.0",
     "@docusaurus/types": "^2.1.0",
     "@electron/docs-parser": "^1.0.1",
+    "@electron/lint-roller": "^1.5.0",
     "@tsconfig/docusaurus": "^1.0.6",
     "@types/fs-extra": "^9.0.13",
     "@types/jest": "^26.0.23",

src/plugins/README.md

@@ -26,7 +26,7 @@ code that acts as the page template.
 
 This is what the plugin code looks like:
 
-```
+```text
 plugins/my-plugin
 └── index.js
 ```
@@ -71,7 +71,7 @@ component into the same folder as pages handled by `@docusaurus/content-plugin-p
 Because of some bundler magic, we can use the `@site` prefix from the plugin to specify
 the site root.
 
-```
+```text
 src/pages
 ├── _my-page.jsx
 ├── _my-page.module.scss