Remove meta site

files/en-us/_redirects.txt

@@ -5406,7 +5406,6 @@
 /en-US/docs/MDN/Contribute/Content/Specification_tables	/en-US/docs/MDN/Writing_guidelines/Page_structures/Specification_tables
 /en-US/docs/MDN/Contribute/Content/Style_guide	/en-US/docs/MDN/Writing_guidelines/Writing_style_guide
 /en-US/docs/MDN/Contribute/Creating_and_editing_pages	/en-US/docs/MDN/Writing_guidelines/Howto/Creating_moving_deleting
-/en-US/docs/MDN/Contribute/Documentation_priorities	https://mdn-contributor-docs.mozilla.org/legacy/documentation-priorities/
 /en-US/docs/MDN/Contribute/Does_this_belong	/en-US/docs/MDN/Writing_guidelines/What_we_write
 /en-US/docs/MDN/Contribute/Editor/Live_samples	/en-US/docs/MDN/Writing_guidelines/Page_structures/Live_samples
 /en-US/docs/MDN/Contribute/FAQ	/en-US/docs/MDN/Contribute

files/en-us/mdn/community/issues/issue_triage/index.md

@@ -105,7 +105,7 @@ Definitions:
 
 Generally speaking, critical issues should be fixed immediately, and would probably be handled by MDN staff/peers. And Tier 1 issues are more important than Tier 2 issues. Folks that are interested in tackling the highest priority MDN issues should always tackle Tier 0 issues if any are available, before moving on to Tier 1 then Tier 2 issues.
 
-> **Note:** For definitions of Tier 1 and Tier 2, see the [MDN documentation priority list](https://mdn-contributor-docs.mozilla.org/legacy/documentation-priorities/).
+> **Note:** For definitions of Tier 1 and Tier 2, see the [MDN documentation priority list](/en-US/docs/MDN/Community/Documentation_priority/).
 
 ### Provide further information
 

files/en-us/mdn/community/priority/index.md

@@ -0,0 +1,181 @@
+---
+title: Documentation priority
+slug: MDN/Community/Documentation_priority
+page-type: mdn-community-guide
+tags:
+  - meta
+  - community-guidelines
+  - governance
+---
+
+{{MDNSidebar}}
+
+## Assessing the priority of documentation
+
+This document describes the different priority tiers on MDN, and states what documentation topics exist inside each tier — we are calling them **Tier 1** and **Tier 2**.
+
+The purpose of this document is:
+
+- To help apply priority measures to content bugs during our triage process, which in turn helps contributors to make a decision about what bugs to work on by finding out which ones are most important right now.
+- To help contributors that want to work on a specific topic area rather than a specific bug decide which one would be most useful to give their time to (for example, folks that like to run automated cleanup scripts on MDN).
+
+The relative importance of these docs has been decided purely by looking at page view figures. There are lots of measures we could have used, but page views is objective and still a good indicator — more important web technologies are looked up more often, and therefore fixing problems with those docs seems most critical.
+
+Also bear in mind that these Tiers are made up of isolated document trees (i.e. the linked page, plus all of the documents in the hierarchy below it). Sometimes a Tier 1 document will link to a Tier 2 document, or vice versa, and that is OK.
+
+The numbers in parentheses after each document tree represent the number of documents under that tree. These numbers will likely change over time, so may need revisiting before too long.
+
+## Tier 1
+
+Tier 1 content (approx. 4150 pages) is the most important content on MDN.
+This content has the most readers and is considered to cover the most important technologies for the web.
+
+- [Accessibility](/en-US/docs/Web/Accessibility)
+- [CSS](/en-US/docs/Web/CSS)
+- [Events](/en-US/docs/Web/Events)
+- [HTML](/en-US/docs/Web/HTML)
+- [HTTP](/en-US/docs/Web/HTTP)
+- [JavaScript](/en-US/docs/Web/JavaScript)
+- [Learn web development](/en-US/docs/Learn)
+- [Media](/en-US/docs/Web/Media)
+- [Performance](/en-US/docs/Web/Performance)
+- [Privacy](/en-US/docs/Web/Privacy)
+- [Progressive web apps](/en-US/docs/Web/Progressive_web_apps)
+- [Security](/en-US/docs/Web/Security)
+- [Web APIs](/en-US/docs/Web/API). The interfaces in the following groups are Tier 1 (see the [Tier 1 WebAPIs](#tier_1_webapis) section below for a further breakdown of what this includes :
+
+  - Canvas API
+  - Clipboard API
+  - DOM
+  - DOM Events
+  - Fetch API
+  - File API
+  - HTML DOM
+  - URL API
+  - Web Storage API
+  - WebSockets API
+  - XMLHttpRequest
+
+- [Web App Manifests](/en-US/docs/Web/Manifest)
+- [WebAssembly](/en-US/docs/WebAssembly)
+- [Web components](/en-US/docs/Web/Web_Components)
+
+## Tier 2
+
+Tier 2 content (approx. 6502 pages) is less commonly-used, but useful nonetheless.
+
+- [CSS Houdini](/en-US/docs/Web/Guide/Houdini)
+- [Game development docs](/en-US/docs/Games)
+- [Guides](/en-US/docs/Web/Guide)
+- [MathML](/en-US/docs/Web/MathML)
+- [MDN meta-documentation](/en-US/docs/MDN) . This is important, but fixes would be mainly dealt with by the MDN core team)
+- [SVG](/en-US/docs/Web/SVG)
+- [The MDN Web Docs glossary](/en-US/docs/Glossary)
+- [WebAPIs](/en-US/docs/Web/API) that aren't in the "Tier 1 WebAPIs" list
+- [WebExtensions](/en-US/docs/Mozilla/Add-ons/WebExtensions) . Not really web platform, but still important)
+
+## Other content
+
+There is other content on MDN that is outside our web platform technology remit such as archived content and Firefox-specific docs (e.g. DevTools, platform internals).
+This content is not prioritized and we are looking for a home for it and considering archiving it if no longer useful.
+We would not recommend that our community spends any time working on any areas not specifically listed in this document in **Tier 1 or Tier 2**.
+
+## Tier 1 WebAPIs
+
+The following API interface reference documents (and their child pages) are currently considered Tier 1.
+For more information on the rationale for these groupings and priorities, see the work done in <https://github.com/mdn/sprints/issues/3327>.
+
+### Canvas API
+
+- [`CanvasGradient`](/en-US/docs/Web/API/CanvasGradient)
+- [`CanvasPattern`](/en-US/docs/Web/API/CanvasPattern)
+- [`CanvasRenderingContext2D`](/en-US/docs/Web/API/CanvasRenderingContext2D)
+- [`ImageBitmap`](/en-US/docs/Web/API/ImageBitmap)
+- [`ImageBitmapRenderingContext`](/en-US/docs/Web/API/ImageBitmapRenderingContext)
+- [`ImageData`](/en-US/docs/Web/API/ImageData)
+- [`OffscreenCanvas`](/en-US/docs/Web/API/OffscreenCanvas)
+- [`Path2D`](/en-US/docs/Web/API/Path2D)
+- [`TextMetrics`](/en-US/docs/Web/API/TextMetrics)
+
+### Clipboard API
+
+- [`Clipboard`](/en-US/docs/Web/API/Clipboard)
+- [`ClipboardEvent`](/en-US/docs/Web/API/ClipboardEvent)
+- [`ClipboardItem`](/en-US/docs/Web/API/ClipboardItem)
+
+### DOM
+
+> **Note:** "DOM" is only a partial group — we only included the interface docs with the highest page views, to keep the size of Tier 1 down to a manageable number. Other DOM interfaces not in this list are in Tier 2.
+
+- [`AbortController`](/en-US/docs/Web/API/AbortController)
+- [`CustomEvent`](/en-US/docs/Web/API/CustomEvent)
+- [`Document`](/en-US/docs/Web/API/Document)
+- [`DOMParser`](/en-US/docs/Web/API/DOMParser)
+- [`Element`](/en-US/docs/Web/API/Element)
+- [`Event`](/en-US/docs/Web/API/Event)
+- [`EventTarget`](/en-US/docs/Web/API/EventTarget)
+- [`HTMLCollection`](/en-US/docs/Web/API/HTMLCollection)
+- [`MutationObserver`](/en-US/docs/Web/API/MutationObserver)
+- [`Node`](/en-US/docs/Web/API/Node)
+- [`NodeList`](/en-US/docs/Web/API/NodeList)
+
+### DOM Events
+
+> **Note:** "DOM Events" is only a partial group — we only included the interface docs with the highest page views, to keep the size of Tier 1 down to a manageable number. Other DOM Events interfaces not in this list are in Tier 2.
+
+- [`EventListener`](/en-US/docs/Web/API/EventTarget/addEventListener)
+- [`KeyboardEvent`](/en-US/docs/Web/API/KeyboardEvent)
+
+### Fetch API
+
+- [`Headers`](/en-US/docs/Web/API/Headers)
+- [`Request`](/en-US/docs/Web/API/Request)
+- [`Response`](/en-US/docs/Web/API/Response)
+
+### File API
+
+- [`Blob`](/en-US/docs/Web/API/Blob)
+- [`File`](/en-US/docs/Web/API/File)
+- [`FileList`](/en-US/docs/Web/API/FileList)
+- [`FileReader`](/en-US/docs/Web/API/FileReader)
+- [`FileReaderSync`](/en-US/docs/Web/API/FileReaderSync)
+
+### HTML DOM
+
+> **Note:** "HTML DOM" is only a partial group — we only included the interface docs with the highest page views, to keep the size of Tier 1 down to a manageable number. Other HTML DOM interfaces not in this list are in Tier 2.
+
+- [`History`](/en-US/docs/Web/API/History)
+- [`HTMLAudioElement`](/en-US/docs/Web/API/HTMLAudioElement)
+- [`HTMLCanvasElement`](/en-US/docs/Web/API/HTMLCanvasElement)
+- [`HTMLElement`](/en-US/docs/Web/API/HTMLElement)
+- [`HTMLFormElement`](/en-US/docs/Web/API/HTMLFormElement)
+- [`HTMLInputElement`](/en-US/docs/Web/API/HTMLInputElement)
+- [`HTMLTextAreaElement`](/en-US/docs/Web/API/HTMLTextAreaElement)
+- [`Location`](/en-US/docs/Web/API/Location)
+- [`Navigator`](/en-US/docs/Web/API/Navigator)
+- [`NavigatorLanguage`](/en-US/docs/Web/API/Navigator/language)
+- [`NavigatorOnLine`](/en-US/docs/Web/API/Navigator/onLine)
+- [`Window`](/en-US/docs/Web/API/Window)
+
+### URL API
+
+- [`URL`](/en-US/docs/Web/API/URL)
+- [`URLSearchParams`](/en-US/docs/Web/API/URLSearchParams)
+- [`URLUtilsReadOnly`](/en-US/docs/Web/API/WorkerLocation)
+
+### Web Storage API
+
+- [`Storage`](/en-US/docs/Web/API/Storage)
+- [`StorageEvent`](/en-US/docs/Web/API/StorageEvent)
+
+### WebSockets API
+
+- [`CloseEvent`](/en-US/docs/Web/API/CloseEvent)
+- [`MessageEvent`](/en-US/docs/Web/API/MessageEvent)
+- [`WebSocket`](/en-US/docs/Web/API/WebSocket)
+
+### XMLHttpRequest
+
+- [`FormData`](/en-US/docs/Web/API/FormData)
+- [`XMLHttpRequest`](/en-US/docs/Web/API/XMLHttpRequest)
+- [`XMLHttpRequestEventTarget`](/en-US/docs/Web/API/XMLHttpRequestEventTarget)

files/en-us/mdn/community/pull_requests/index.md

@@ -125,10 +125,12 @@ Don't:
 
 - Try to cram multiple fixes into a single pull request. It makes it a lot harder to review, and raises suspicions (some people might think you are trying to hide some malicious code in between the valid changes).
 
-## Opening a pull request
+## Deployment timeline
 
-## Reviewing a pull request
+After your pull request is merged, it can take up to 48 hours before merged changes are live on the [production site](https://developer.mozilla.org/), but it's usually quicker.
 
-## Pull requests we accept
+- The site build runs every 24 hours at around 19:00 US/Eastern time, and is deployed immediately after.
+- Once deployment has occurred, it can take up to 24 hours for the CDN to invalidate caches and serve new content.
 
-## Idle pull requests
+There are tools to see the state of deployed content such as [whatsdeployed.io](https://whatsdeployed.io/s/DLi/mdn/content) which let you see if your changes have been deployed.
+The same tool can also be used to [see if `translated-content` is live](https://whatsdeployed.io/s/16d/mdn/translated-content) after merging a pull request in the [`transpated-content` repository](https://github.com/mdn/translated-content).

files/en-us/mdn/contribute/index.md

@@ -127,11 +127,11 @@ We will add more tasks here as time goes on.
 
 You can also look at priority ratings to give you an idea of what the most important work is to work on — we've started giving content bug issues labels of P0, P1, P2, P3, and P4 to signify how important they are, with lower numbers being more important than higher numbers.
 
-These are figured out during the regular MDN bug triage process, based on the [MDN documentation priority list](https://mdn-contributor-docs.mozilla.org/legacy/documentation-priorities/).
+These are figured out during the regular MDN bug triage process, based on the [MDN documentation priority list](/en-US/docs/MDN/Community/Documentation_priority/).
 
 ### Other task types
 
-If our main priorities listed above don't interest you, you can find a number of other, more general task types to get involved with below, split up by skillset.
+If our main priorities listed above don't interest you, you can find a number of other, more general task types to get involved with below, split up by skill set.
 
 If you are more interested in words, you could do the following:
 

files/en-us/mdn/writing_guidelines/content_reuse/index.md

@@ -0,0 +1,35 @@
+---
+title: Content reuse policy
+slug: MDN/Writing_guidelines/Content_reuse
+page-type: mdn-writing-guide
+tags:
+  - meta
+  - writing-guide
+---
+
+{{MDNSidebar}}
+
+In general, we do not approve of copying content from other sources and putting it on MDN.
+MDN should be made up of original content wherever possible.
+If we receive a pull request and discover that it contains plagiarized content, we will close it and request that the submitter resubmit the change with the content rewritten into their own words.
+
+## If you want to reuse or republish content
+
+> **Note:** Unless there is a good reason to republish the content, we will probably say "no".
+> The MDN writing team's decision is final.
+
+If someone wants to donate an article to MDN that they previously published on their blog or it makes sense to copy a complex reference sheet to MDN, there may be justification for republishing it. For these cases, discuss your plan with the MDN team beforehand:
+
+- [Create a GitHub issue](https://github.com/mdn/mdn/issues/new/choose) that explains your intention.
+  - Describe what you would like to copy or republish.
+  - Provide a URL to the resource.
+  - Explain why you think it's appropriate.
+
+**If the content is published under a closed license:**
+
+- If you hold the rights to the content, state this and your express agreement to republish it on MDN.
+- If you do not hold the rights to the content, include the author/publisher on the issue if possible, or include details of how they could be contacted so we can ask them for permission to republish the content.
+
+**If the content is published under an open license:**
+
+- Say what it is, and link to the license so we can check whether it is compatible with [MDN's license](https://developer.mozilla.org/en-US/docs/MDN/About#using_mdn_web_docs_content).

files/en-us/mdn/writing_guidelines/howto/browser_compat_data/index.md

@@ -0,0 +1,19 @@
+---
+title: How to update browser compatibility tables
+slug: MDN/Writing_guidelines/Howto/Browser_compat_data
+tags:
+  - meta
+  - writing-guide
+page-type: mdn-writing-guide
+---
+
+{{MDNSidebar}}
+
+## Updating browser compatibility tables
+
+The browser compatibility table shown near the bottom of many MDN document pages is generated from the `browser-compat-data` project.
+To make this data available in multiple projects programmatically, a Node.js package is built from the [`browser-compat-data` repository](https://github.com/mdn/browser-compat-data) and published to npm.
+For an example of how this looks like, see the [JavaScript Array page](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array#browser_compatibility) which shows the compatibility table for the `Array` object.
+
+If you'd like to make or suggest changes to the content of the browser compatibility table on any given MDN document page, you can either use the `Report problems with this data on GitHub` link in the upper-right
+corner of the table you wish to edit, or go to the [`browser-compat-data` repository](https://github.com/mdn/browser-compat-data) and see the [contribution guide](https://github.com/mdn/browser-compat-data/blob/main/docs/contributing.md).

files/en-us/mdn/writing_guidelines/howto/code_examples/index.md

@@ -0,0 +1,27 @@
+---
+title: How to add code examples
+slug: MDN/Writing_guidelines/Howto/Code_examples
+tags:
+  - meta
+  - writing-guide
+page-type: mdn-writing-guide
+---
+
+{{MDNSidebar}}
+
+## Adding code examples
+
+There are a lot of code examples on MDN, and you'll probably want to add some as you contribute content to the project. This page describes the types of code examples available to use on MDN.
+
+There are four types of code examples used:
+
+- [Static examples](/MDN/Structures/Code_examples#Static_examples)
+  — Plain code blocks, possibly with a screenshot to statically show the result of such code if it were to be run.
+- [MDN "live samples"](/MDN/Structures/Code_examples#Traditional_live_samples)
+  — A macro that takes plain code blocks, dynamically puts them into a document inside an `<iframe>` element, and embeds it into the page to show the code running live.
+- [GitHub "live samples"](/MDN/Structures/Code_examples#GitHub_live_samples)
+  — A macro that takes a document in a GitHub repo inside the [MDN organization](https://github.com/mdn), puts it inside an `<iframe>` element, and embeds it into the page to show the code running live.
+- [Interactive examples](/MDN/Structures/Code_examples#Interactive_examples)
+  — Our system for creating live interactive examples that show the code running live but also allow you to change code on the fly to see what the effect is.
+
+For a complete description of this topic, see [the MDN code examples page](/MDN/Structures/Code_examples) and for code style guidance, see the [MDN code example guidelines](/MDN/Guidelines/Code_guidelines).

files/en-us/mdn/writing_guidelines/howto/images_media/index.md

@@ -9,11 +9,76 @@ page-type: mdn-writing-guide
 
 {{MDNSidebar}}
 
+## Adding images
+
+To add an image to a document, add your image file to the document's folder, and then reference the image from within the document's  `index.md` file, using an `<img>` or [the equivalent Markdown syntax](https://github.github.com/gfm/#images).
+
+Let's walk through an example:
+
+1. Start with a fresh working branch with the latest content from the `main` branch of the `mdn` remote.
+
+   ```sh
+   cd ~/path/to/mdn/content
+   git checkout main
+   git pull mdn main
+   # Run "yarn" again just to ensure you've
+   # installed the latest Yari dependency.
+   yarn
+   git checkout -b my-images
+   ```
+
+2. Add your image to the document folder. For this example, let's assume
+   we're adding a new image to the `files/en-us/web/css` document.
+
+   ```sh
+   cd ~/path/to/mdn/content
+   cp ../some/path/my-cool-image.png files/en-us/web/css/
+   ```
+
+3. Run `filecheck` on each image which will complain if something's wrong.
+   For more details, see the [Compressing images](#compressing-images) section.
+
+   ```sh
+   yarn filecheck files/en-us/web/css/my-cool-image.png
+   ```
+
+4. Reference your image in a document, for example, with an `<img>` element inside `files/en-us/web/css/index.html`:
+
+   ```html
+   <img src="my-cool-image.png" alt="My cool image" />
+   ```
+
+5. Add and commit all of the deleted, created, and modified files, as well as
+   push your branch to your fork:
+
+   ```sh
+   git add files/en-us/web/css/my-cool-image.png files/en-us/web/css/index.html
+   git commit
+   git push -u origin my-images
+   ```
+
+6. Now you're ready to create your
+   [pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request).
+
+## Compressing images
+
+When you add images to MDN, you should make sure that they are compressed as much as possible without degrading quality, to save on download size for our readers.
+In fact, if you don't do this our CI process will fail and the build results will warn you that some of your images are too big.
+
+The best way to compress them is by using the built-in compression tool.
+You can compress an image appropriately by using the `filecheck` command with the `--save-compression` option.
+This option compresses the image as much as possible and replaces the original with the compressed version.
+For example:
+
+```sh
+yarn filecheck files/en-us/web/css/my-cool-image.png --save-compression
+```
+
+## Adding videos
+
 MDN Web Docs is not a very video-heavy site, but there are certain places where video content makes sense to use as part of an article.
 This article discusses when including videos in articles is appropriate and provides tips on how to create simple but effective videos on a budget.
 
-## Using video content
-
 There are several arguments against using video content for technical documentation, particularly for reference material and advanced level guides. Some of these are listed below:
 
 - Video is linear.