delete pages that were never translated from en-US (pl, part 1) (#1549)

2 files changed, 0 insertions, 555 deletions

diff --git a/files/pl/mdn/contribute/howto/create_and_edit_pages/index.html b/files/pl/mdn/contribute/howto/create_and_edit_pages/index.html
deleted file mode 100644
index 4fb13dadc2..0000000000
--- a/files/pl/mdn/contribute/howto/create_and_edit_pages/index.html
+++ /dev/null
@@ -1,179 +0,0 @@
----
-title: How to create and edit pages
-slug: MDN/Contribute/Howto/Create_and_edit_pages
-translation_of: MDN/Contribute/Howto/Create_and_edit_pages
----
-<div>{{MDNSidebar}}</div>
-
-<p><span class="seoSummary">Ten artykuł wdraża nowe osoby wspierające do procesu edycji istniejących stron oraz tworzenia nowych.</span></p>
-
-<h2 id="Edycja_istniejącej_strony">Edycja istniejącej strony</h2>
-
-<p>Aby edytować stronę:</p>
-
-<ol>
- <li>Jeśli znajdujesz się na stronie MDN Web Docs w wersji tylko do odczytu (https://developer.mozilla.org), kliknij <strong>Edit in wiki</strong> w nagłówku artykułu. Przeniesiesz się do edytowalnej wersji wiki strony(https://wiki.developer.mozilla.org), ale nie otworzy to jeszcze interfejsu edycji.</li>
- <li>Kliknij przycisk <strong>Edit</strong> w nagłówku artykułu wiki strony.</li>
- <li>Strona się odświeży wraz z interfejsem edycji gdzie możesz bezpośrednio dodawać i usuwać zawartość strony.</li>
- <li>Dodawaj paragrafy, usuwaj tekst, wstawiaj nagłówki i wykonuj więcej podstawowych operacji związanych z pisaniem i edytowaniem.</li>
-</ol>
-
-<p>Zobacz przewodnik <a href="/en-US/docs/MDN/Contribute/Editor/Basics">Editor UI elements</a> w <a href="/en-US/docs/MDN/Contribute/Editor">MDN Editor guide</a> by uzyskać więcej informacji dotyczących wbudowanego edytora <strong>MDN.</strong></p>
-
-<h3 id="Podgląd_zmian">Podgląd zmian</h3>
-
-<p>Aby zobaczyć zmiany:</p>
-
-<ul>
- <li>Kliknij przycisk <strong>Podgląd</strong> wewnątrz funkcji edycji, na górze lub na dole strony.</li>
- <li>Otworzy się podgląd strony pokazujący twoje poprawki, w nowym oknie lub karcie.</li>
- <li>Za każdym razem, kiedy klikniesz ten przycisk, odświeżysz stronę podglądu wraz z ostanimi zmianami.</li>
-</ul>
-
-<p>Uważaj! Podglądanie strony <strong>nie zachowa</strong> twojego postępu prac. Nie zamykaj karty edycji dopóki nie zapiszesz zmian.</p>
-
-<h3 id="Komentarz_do_wersji">Komentarz do wersji</h3>
-
-<p>After previewing your changes, you will want to <em>save your revision</em>. Before you <strong>save</strong>, look for the revision comment box, below the editing box, leaving a comment to inform other contributors why you made changes. For example, you might have added a new section, changed some words to make the terminology more consistent, rewritten a paragraph to clarify the language, or removed information because it was redundant.</p>
-
-<h3 id="Table_of_Contents">Table of Contents</h3>
-
-<p>The 'On this Page' section of an article, is an auto-generated list of links to the headings on the page. The wording of these can be edited via the headings. It's also possible to remove a table of contents or decrease its number of links, by selecting 'Edit Page Title and Properties', changing the value of the "TOC" drop down.</p>
-
-<h3 id="Tags">Tags</h3>
-
-<p>You can add or remove tags, which describe the page content and purpose, below the editing section. See <a href="/en-US/docs/MDN/Contribute/Tagging">How to properly tag pages</a>, for information on which tags to apply.</p>
-
-<h3 id="Review_needed">Review needed?</h3>
-
-<p>If an expert or experienced contributor should review your edits, please request a technical review (for code, API's, or technologies), and/or an editorial review (for prose, grammar, and content), making sure the appropriate box is checked before you save.</p>
-
-<h3 id="Attach_files">Attach files</h3>
-
-<p>Attaching files requires a special user privilege. See <a href="/en-US/docs/MDN/Contribute/Editor/Basics/Attachments">Attachments in the MDN editor</a> for details, including how to request the upload privilege.</p>
-
-<h3 id="Publish_Discard_or_Keep_editing">Publish, Discard, or Keep editing</h3>
-
-<p>When you finish editing and are happy with your preview, publish your work and comments by clicking the <em>green</em> <strong>Publish</strong> button, to the <strong>right of the page title</strong>, or towards the <strong>bottom of the page</strong>. If you wish to continue working, click <strong>Publish and keep editing</strong>, which publishes your changes and keeps the edit interface open.</p>
-
-<p>If you change your mind, you can discard edits, by clicking the <em>red</em> <strong>Discard</strong> button. Note that discarding changes <em>permanently</em> discards them.</p>
-
-<p>Pressing <strong>Enter</strong> in the Revision Comment field is equivalent to clicking <strong>Publish and Keep Editing</strong>.</p>
-
-<div class="note">
-<p>Note: If attempting to save, but changes are rejected as invalid, and you feel the content is appropriate for MDN, <a href="mailto:mdn-admins@mozilla.com?subject=MDN%3A%20Content%20Rejection%20Appeal&amp;body=%3CDescribe%20the%20content%20you%20were%20trying%20to%20save%20and%20where%20you%20were%20trying%20to%20place%20it.%3E">email the MDN admin team</a> for assistance.</p>
-</div>
-
-<h2 id="Getting_page-creation_permissions">Getting page-creation permissions</h2>
-
-<p>For security reasons, newly-created accounts don't have the ability to create new pages. If you try to do so, you'll see a page instructing you how to get the page created. There are two options:</p>
-
-<ul>
- <li><strong>Ask for the page to be created for you.</strong> To do this, <a href="https://github.com/mdn/sprints/issues/new?template=issue-template.md&amp;projects=mdn/sprints/2&amp;labels=user-report">file a documentation request issue</a>, with the title "Create page: &lt;page title&gt;". Fill out the URL field of the template with the location on MDN where you'd like the page to go if you know where to place it. In the comment text, include information on why this page needs creating.</li>
- <li><strong>Request page creation privileges.</strong> If you request page creation privileges, and they're granted to you, you'll be able to add new pages by following the instructions here. To request these privileges, <a href="mailto:mdn-admins@mozilla.org">email the MDN admin</a> team with your request. Include your username, why you would like to have the ability to create new pages. For instance, you're documenting a new API which involves many new pages, or you'd like to add new terms to the glossary. You should also have made useful contributions to this site's content, and been a contributor for some time. This length of time, and the other factors are collectively considered.</li>
-</ul>
-
-<h2 id="Creating_a_new_page">Creating a new page</h2>
-
-<p>Once you have page-creation permission, you can begin creating pages.</p>
-
-<p>If you do not know where to place a new article, <strong>do not worry.</strong> Put it anywhere, we will find it, move to where it belongs, or merge it into existing content. Whatever makes the most sense. Do not worry about making it perfect. We have happy helper gnomes who help to make your content clean and rather luscious.</p>
-
-<p>There are a few ways to create a new page:</p>
-
-<ul>
- <li><a href="#Missing_page_link">'Missing page' link.</a></li>
- <li><a href="#New_page_without_link">New page without a link.</a></li>
- <li><a href="#Subpage_of_an_existing_page">A subpage of an existing page.</a></li>
- <li><a href="#Clone_of_an_existing_page">Clone of an existing page.</a></li>
- <li><a href="#Link_from_an_existing_page">Link from an existing page.</a></li>
-</ul>
-
-<h3 id="Missing_page_link">'Missing page' link</h3>
-
-<p>As with most wikis, it is possible to create a link to a page that is yet to exist. For example, an author might create a list of all the members of an API, before creating the pages for those members. On MDN, links to non-existent pages are typically displayed in red.</p>
-
-<p>To create a page from a 'missing page' link:</p>
-
-<ol>
- <li>Log into MDN, and have page-creation permission. If not logged in, clicking a 'missing page' link results in a 404 (page not found) error.</li>
- <li>Click the 'missing page' link. If you have page creation permission, the <a href="/en-US/docs/MDN/Contribute/Editor">MDN Editor UI</a> opens, ready for you to create the missing page.</li>
- <li>Write the content of the page, and save it.</li>
-</ol>
-
-<h3 id="New_page_without_link">New page without link</h3>
-
-<p><em>To create a new page without linking from another page</em>, enter a unique page name in the URL field of your browser. For example, if you enter:</p>
-
-<pre class="language-html notranslate">https://wiki.developer.mozilla.org/en-US/docs/FooBar</pre>
-
-<p>MDN Creates a new page, with the title "FooBar", opening the editor for you to add new content. Refer to the <a href="#Editing_an_existing_page">Editing an existing page</a> section of this article, for information on how to use the editor mode.</p>
-
-<p><em>To create a new page without linking from another page</em>:</p>
-
-<ol>
- <li>Log in, and have page-creation permission.</li>
- <li>Enter the following in the URL field of your browser:</li>
-</ol>
-
-<pre class="language-html notranslate">https://wiki.developer.mozilla.org/en-US/docs/new</pre>
-
-<p>MDN Creates a new page, with a place for a title, opening the editor to add new content to this page. Refer to <a href="#Editing_an_existing_page">Editing an existing page</a>, for information on using editor mode.</p>
-
-<h3 id="Subpage_of_an_existing_page">Subpage of an existing page</h3>
-
-<p>To create a page you want to be below an existing page, in the page hierarchy:</p>
-
-<ol>
- <li>If needed, navigate to the wiki site by clicking <strong>Edit in wiki</strong> in the article header.</li>
- <li>On the 'parent' page, click the <strong>Advanced</strong> menu (the gear icon in the toolbar), then click <strong>New sub-page</strong>.</li>
- <li>An editor view opens for creating a new document.</li>
- <li>Add a title for this document, in the <strong>Title</strong> field.</li>
- <li>Change the <strong>Slug</strong> field, if needed. For example, if the title is long, and a shorter URL seems appropriate. This field is automatically filled by the editor, substituting underscores for spaces found in the title, changing only the last part of the URL.</li>
- <li>In the <strong>TOC</strong> field, select heading levels you want to be displayed in the table of contents for the page. Or select 'No table of contents', if one is not needed.</li>
- <li>Write content of the page in the editor pane, saving your changes. Refer to <a href="#Editing_an_existing_page">Editing an existing page</a>, for further information on using editor mode.</li>
-</ol>
-
-<h3 id="Clone_of_an_existing_page">Clone of an existing page</h3>
-
-<p>If there is an existing page, whose format you wish to use as a base for your new page, you can 'clone' that page, and then change its content.</p>
-
-<ol>
- <li>If needed, navigate to the wiki site by clicking <strong>Edit in wiki</strong> in the article header.</li>
- <li>On the original page, click the <strong>Advanced</strong> menu (the gear icon in the toolbar), and click <strong>Clone this page</strong>. An editor view opens, for creating a new document.</li>
- <li>Change the <strong>Title</strong> of the page, as appropriate for the new content. The <strong>Slug</strong> field is updated automatically as you change the <strong>Title</strong> field.</li>
- <li>Change the path portion of the <strong>Slug</strong> field, as needed, to put the new document in a different location in the document hierarchy. In most cases, this is not needed. A cloned page often has similar content to its original, and need to be in a similar location.</li>
- <li>In the <strong>TOC</strong> field, select the heading levels you want to be automatically displayed in the table of contents for this page. Or select 'No table of contents', if one is not needed.</li>
- <li>Write your content in the editor pane, saving your changes. Refer to <a href="#Editing_an_existing_page">Editing an existing page</a>, for more information on using editor mode.</li>
-</ol>
-
-<h3 id="Link_from_an_existing_page">Link from an existing page</h3>
-
-<p>This is a bit of a hybrid. You can create a link on another page, then click the link you just inserted, to create the new page:</p>
-
-<ol>
- <li>Enter the name of your new page, anywhere that makes sense in the text of an existing page.</li>
- <li>Highlight this new name, and <strong>click the Link icon (<img alt="" src="https://developer.mozilla.org/files/3810/link-icon.png" style="float: left; height: 28px; width: 29px;">) </strong>in the editor's toolbar. The <strong>'Update Link'</strong> dialog opens, with the highlighted text in the <strong>'Link To'</strong> field.</li>
- <li><strong>"/en-US/docs/"</strong> is inserted by default, to the beginning of the URL field.<em> Enter the name </em>of the page after "/en-US/docs/". The page name does not have to be the same as the link text.</li>
- <li>Click <strong>OK</strong>, to create and insert the link.</li>
-</ol>
-
-<p>If the page does not yet exist, the link is displayed in red. If the page <em>does</em> exist, the link is displayed blue. If you want to create a new page, but the page title you desire is already taken, check if it makes sense helping edit and improve the page already there. Otherwise, think of a unique title for your new page, and create a link for it. Refer to <a href="https://developer.mozilla.org/Project:en/Page_Naming_Guide" title="Project:en/Page_Naming_Guide">page naming guide</a> for guidelines.</p>
-
-<p>To add content to your new page, click on the red link you just created, after saving and closing the editor. The new page opens in editor mode, enabling you to start writing. Refer to <a href="#Editing_an_existing_page">Editing an existing page</a>, for further information on using editor mode.</p>
-
-<h2 id="Refreshing_page_content">Refreshing page content</h2>
-
-<p>MDN support of KumaScript macros, and integration of content from other pages can sometimes be hampered by the need for caching of pages, for performance reasons. Pages are built from their source, and this output is cached for future requests. From that moment on, any macros (templates), or integrations (using the macro<span class="templateLink"><code><a href="https://developer.mozilla.org/en-US/docs/Template:Page">Page</a></code></span>), will not reflect later changes made to the macro, its output, or the contents of the integrated material.</p>
-
-<ul>
- <li>To manually update a page, force-refresh your Web browser. MDN detects this, triggering a page rebuild, pulling in updated macro output, and integrating page content.</li>
- <li>You can also configure pages to periodically rebuild, automatically. This should not be done unless you expect the page to update frequently. See <a href="/en-US/docs/MDN/Contribute/Tools/Page_regeneration">Page regeneration</a>, for detailed information.</li>
-</ul>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="/en-US/docs/MDN/Contribute/Editor">MDN editor guide</a></li>
- <li><a href="/en-US/docs/MDN/Contribute/Content/Style_guide">MDN style guide</a></li>
-</ul>
diff --git a/files/pl/mdn/contribute/howto/tag/index.html b/files/pl/mdn/contribute/howto/tag/index.html
deleted file mode 100644
index 8cfb4c7145..0000000000
--- a/files/pl/mdn/contribute/howto/tag/index.html
+++ /dev/null
@@ -1,376 +0,0 @@
----
-title: How to properly tag pages
-slug: MDN/Contribute/Howto/Tag
-translation_of: MDN/Contribute/Howto/Tag
----
-<div>{{MDNSidebar}}</div><p><strong>Article tags</strong> are an important way to put visitors in touch with helpful content. Each page should normally have several tags to help keep content organized. <span class="seoSummary">This page explains the best way to tag pages so that our readers can find information and we can keep ourselves organized.</span></p>
-
-<p>For a help with the user interface for editing tags, see the <a href="/en-US/docs/MDN/Contribute/Editor/Basics#The_tags_box">tagging section</a> in our editor guide.</p>
-
-<p>Please use tags properly as explained below. If you don't, our automated tools will not correctly generate lists of content, landing pages, and cross-linking of articles.</p>
-
-<h2 id="How_MDN_uses_tags">How MDN uses tags</h2>
-
-<p>Tags get used on MDN several ways:</p>
-
-<dl>
- <dt>Document categorization</dt>
- <dd>What type of document is it? Is it a reference? A tutorial? A landing page? Our visitors can use these tags to filter searches, so they're really important!</dd>
- <dt>Topic identification</dt>
- <dd>What is the article about? Is it about an API? The DOM? Graphics? Again, these tags are important because they can filter searches.</dd>
- <dt>Technology status</dt>
- <dd>What's the status of the technology? Is it non-standard? Obsolete or deprecated? Experimental?</dd>
- <dt>Skill level</dt>
- <dd>For tutorials and guides, how advanced is the material covered by the article?</dd>
- <dt>Document metadata</dt>
- <dd>The writing community uses tags to keep track of which pages need what kind of work.</dd>
-</dl>
-
-<h2 id="Tag_type_guide">Tag type guide</h2>
-
-<p>Here's a quick guide to the types of tags and possible values for them.</p>
-
-<h3 id="Document_category">Document category</h3>
-
-<p>When you tag an article with one of these categories, you help the automated tools more accurately generate landing pages, tables of contents, and so on. Our new search system will also use these terms so that our visitors can locate reference or guide information at will.</p>
-
-<p>We use the following category names as standard tagging terms:</p>
-
-<dl>
- <dt><code>{{Tag("Intro")}}</code></dt>
- <dd>The article provides introductory material about a topic. Ideally each technology area should have only one "Intro".</dd>
- <dt><code>{{Tag("Featured")}}</code></dt>
- <dd>The article is critical and will display prominently on landing pages. Use this tag sparingly (never more than three documents in each documentation area).</dd>
- <dt><code>{{Tag("Reference")}}</code></dt>
- <dd>The article contains reference material about an API, element, attribute, property, or the like.</dd>
- <dt><code>{{Tag("Landing")}}</code></dt>
- <dd>The page is a landing page.</dd>
- <dt><code>{{Tag("Guide")}}</code></dt>
- <dd>The article is a how-to or guide page.</dd>
- <dt><code>{{Tag("Example")}}</code></dt>
- <dd>The article is a code sample page, or has code samples (that is, actual snippets of useful code, not one-line "syntax examples").</dd>
-</dl>
-
-<h3 id="Topic">Topic</h3>
-
-<p>By identifying the article's topic area, you are helping generate better search results (and landing pages and navigation as well).</p>
-
-<p>While there's some room for flexibility here as we identify new topic areas, we try to limit ourselves to the names of APIs or technologies. Some useful examples:</p>
-
-<ul>
- <li><code>{{Tag("HTML")}}</code></li>
- <li><code>{{Tag("CSS")}}</code></li>
- <li><code>{{Tag("JavaScript")}}</code> (notice the capital "S"!)</li>
- <li><code>{{Tag("Document")}}</code></li>
- <li><code>{{Tag("DOM")}}</code></li>
- <li><code>{{Tag("API")}}</code> for each interface, method and property.</li>
- <li><code>{{Tag("Method")}}</code> for each method of an API</li>
- <li><code>{{Tag("Property")}}</code> for each property of an API</li>
- <li><code>{{Tag("Graphics")}}</code></li>
- <li><code>{{Tag("Firefox OS")}}</code></li>
- <li><code>{{Tag("Gecko")}}</code></li>
- <li><code>{{Tag("XUL")}}</code></li>
- <li><code>{{Tag("XPCOM")}}</code></li>
- <li><code>{{Tag("SVG")}}</code></li>
- <li><code>{{Tag("WebGL")}}</code></li>
- <li><code>{{Tag("Element")}}</code></li>
- <li><code>{{Tag("Node")}}</code></li>
- <li><code>{{Tag("Tools")}}</code></li>
- <li><code>{{Tag("Web")}}</code></li>
-</ul>
-
-<p>In general, your topic identification tag should be the name of an interface with a number of related pages (like <a href="/en-US/docs/Web/API/Node" title="/en-US/docs/Web/API/Node">Node</a>, which has many pages for its various properties and methods), or the name of an overall technology type. You might tag a page about WebGL with <code>Graphics</code> and <code>WebGL</code>, for example, but a page about {{HTMLElement("canvas")}} with <code>HTML</code>, <code>Element</code>, <code>Canvas</code>, and <code>Graphics</code>.</p>
-
-<h3 id="Technology_status">Technology status</h3>
-
-<p>To help the reader understand how viable a technology is, we use tags to label pages as to the status of the technology's specification. This isn't as detailed as actually explaining what the spec is and how far the technology has come in the specification process (that's what the Specifications table is for), but it helps the reader judge, at a glance, whether it's a good idea to use the technology described in the article.</p>
-
-<p>Here are possible values for these tags:</p>
-
-<dl>
- <dt><code>{{Tag("Non-standard")}}</code></dt>
- <dd>Indicates that the technology or API described on the page is not part of a standard, but is considered stable in any implementing browser(s). If you don't use this tag, your readers will assume the technology is standard. The compatibility table on the page should clarify which browser(s) support this technology or API.</dd>
- <dt><code>{{Tag("Deprecated")}}</code></dt>
- <dd>The technology or API covered on the page is marked as deprecated in the specification, and is likely to eventually be removed, but is generally still available in current versions of browsers.</dd>
- <dt><code>{{Tag("Obsolete")}}</code></dt>
- <dd>The technology or API has been deemed obsolete and has been removed (or actively being removed) from all or most current browsers.</dd>
- <dt><code>{{Tag("Experimental")}}</code></dt>
- <dd>The technology is not standardized, and is an experimental technology or API that may or may not ever become part of a standard. It is also subject to change in the browser engine (typically only one) that implements it.</dd>
- <dt><code>{{Tag("Needs Privileges")}}</code></dt>
- <dd>The API requires privileged access to the device on which the code is running.</dd>
- <dt><code>{{Tag("Certified Only")}}</code></dt>
- <dd>The API only works in certified code.</dd>
-</dl>
-
-<p>These tags are no excuse to leave out the <a href="/en-US/docs/Project:Compatibility_tables" title="/en-US/docs/Project:Compatibility_tables">compatibility table</a> in your article!</p>
-
-<h3 id="Skill_level">Skill level</h3>
-
-<p>Use the skill-level tag type only for guides and tutorials (that is, pages tagged <code>Guide</code>) to help users choose tutorials based on how familiar they are with a technology. There are three values for this:</p>
-
-<dl>
- <dt><code>{{Tag("Beginner")}}</code></dt>
- <dd>Articles designed to introduce the reader to a technology they've never used or have only a passing familiarity with.</dd>
- <dt><code>{{Tag("Intermediate")}}</code></dt>
- <dd>Articles for users who have gotten started with the technology but aren't experts.</dd>
- <dt><code>{{Tag("Advanced")}}</code></dt>
- <dd>Articles about stretching the capabilities of a technology and of the reader.</dd>
-</dl>
-
-<h3 id="Document_metadata">Document metadata</h3>
-
-<p>The writing community uses tags to label articles as requiring specific types of work. Here's a list of the ones we use most:</p>
-
-<dl>
- <dt><code>{{Tag("junk")}}</code></dt>
- <dd>The article needs to be deleted.</dd>
- <dt><code>{{Tag("NeedsContent")}}</code></dt>
- <dd>The article is a stub, or is otherwise lacking information. This tag means that someone should review the content and add more details and/or finish writing the article.</dd>
- <dt><code>{{Tag("NeedsExample")}}</code></dt>
- <dd>The article needs one or more examples created to help illustrate the article's point. These examples should use the <a href="/en-US/docs/Project:MDN/Contributing/How_to_help/Code_samples" title="/en-US/docs/Project:MDN/Contributing/How_to_help/Code_samples">live sample system</a>.</dd>
- <dt><code>{{Tag("NeedsLiveSamples")}}</code></dt>
- <dd>The article has one or more examples that need to be updated to use the <a href="/en-US/docs/Project:MDN/Contributing/How_to_help/Code_samples" title="/en-US/docs/Project:MDN/Contributing/How_to_help/Code_samples">live sample system</a>.</dd>
- <dt><code>{{Tag("NeedsUpdate")}}</code></dt>
- <dd>The content is out of date and needs to updating.</dd>
- <dt><code>{{Tag("l10n:exclude")}}</code></dt>
- <dd>The content is not really worth localizing and will not appear on localization status pages.</dd>
- <dt><code>{{Tag("l10n:priority")}}</code></dt>
- <dd>The content is important and should be marked as a priority for MDN translators. Shows up in an extra priority table on localization status pages.</dd>
-</dl>
-
-<h3 id="Web_Literacy_Map">Web Literacy Map</h3>
-
-<p>The <a href="https://webmaker.org" rel="external">WebMaker</a> project, through the <a href="https://webmaker.org/literacy" rel="external">Web Literacy Map</a>, has defined skills needed to optimally read, write, and participate on the Web. We use Web literacy skills as tags on MDN to help our users find the resources that best suit their needs:</p>
-
-<dl>
- <dt>{{Tag("Navigation")}}</dt>
- <dd>The article includes information about how to browse the Web.</dd>
- <dt>{{Tag("WebMechanics")}}</dt>
- <dd>The content has information about how the Web is organized and how it works.</dd>
- <dt>{{Tag("Search")}}</dt>
- <dd>The article explains how to find information, people, and resources on the Web.</dd>
- <dt>{{Tag("Credibility")}}</dt>
- <dd>The information in the article helps the reader understand how to critically evaluate information they find on the Web</dd>
- <dt>{{Tag("Security")}}</dt>
- <dd>The article provides information about how to keep systems, identities, and content safe.</dd>
- <dt>{{Tag("Composing")}}</dt>
- <dd>The document explains how to create and curate content for the Web.</dd>
- <dt>{{Tag("Remixing")}}</dt>
- <dd>The article teaches how to modify existing Web resources to create something new.</dd>
- <dt>{{Tag("Design")}}</dt>
- <dd>Documentation explaining how to enhance visual aesthetics and user experience.</dd>
- <dt>{{Tag("Accessibility")}}</dt>
- <dd>Documents which describe how to communicate in a universally-recognizable way.</dd>
- <dt>{{Tag("CodingScripting")}}</dt>
- <dd>How to write code and/or to create interactive experiences on the Web.</dd>
- <dt>{{Tag("Infrastructure")}}</dt>
- <dd>The document explains how the Internet's technical stack works.</dd>
- <dt>{{Tag("Sharing")}}</dt>
- <dd>The article's content covers ways to create resources with others.</dd>
- <dt>{{Tag("Collaborating")}}</dt>
- <dd>The document provides information about how to work with other people.</dd>
- <dt>{{Tag("Community")}}</dt>
- <dd>The article details how to get involved in Web communities and to understand how they work.</dd>
- <dt>{{Tag("Privacy")}}</dt>
- <dd>The material helps to examine the consequences of sharing data online.</dd>
- <dt>{{Tag("OpenPractices")}}</dt>
- <dd>The article provid=deshow to help keep the Web accessible to everybody</dd>
-</dl>
-
-<h2 id="Putting_it_all_together">Putting it all together</h2>
-
-<p>So to each page you assign tags from several tag types, for example</p>
-
-<dl>
- <dt>A tutorial about WebGL for beginners</dt>
- <dd><code>WebGL</code>, <code>Graphics</code>, <code>Guide</code>, <code>Beginner</code></dd>
- <dt>Reference page for {{HTMLElement("canvas")}}</dt>
- <dd><code>Canvas</code>, <code>HTML</code>, <code>Element</code>, <code>Graphics,</code> <code>Reference</code></dd>
- <dt>A landing page for Firefox OS developer tools</dt>
- <dd><code>Tools</code>, <code>Firefox OS</code>, <code>Landing</code></dd>
-</dl>
-
-<h2 id="Tagging_and_search_filters">Tagging and search filters</h2>
-
-<p>Search filters won't work properly unless we tag MDN pages properly. Here's a table of search filters and which tags they look for.</p>
-
-<div class="note">
-<p><strong>Note:</strong> If multiple tags are listed under "Tag name," that means any one or more of these tags must be present for the article to match.</p>
-</div>
-
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Filter group</th>
-   <th scope="col">Search filter name</th>
-   <th scope="col">Tag name</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <th>Topic</th>
-   <td>Open Web Apps</td>
-   <td>{{Tag("Apps")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>HTML</td>
-   <td>{{Tag("HTML")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>CSS</td>
-   <td>{{Tag("CSS")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>JavaScript</td>
-   <td>{{Tag("JavaScript")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>APIs and DOM</td>
-   <td>{{Tag("API")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>Canvas</td>
-   <td>{{Tag("Canvas")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>SVG</td>
-   <td>{{Tag("SVG")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>MathML</td>
-   <td>{{Tag("MathML")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>WebGL</td>
-   <td>{{Tag("WebGL")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>XUL</td>
-   <td>{{Tag("XUL")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>Marketplace</td>
-   <td>{{Tag("Marketplace")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>Firefox</td>
-   <td>{{Tag("Firefox")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>Firefox for Android</td>
-   <td>{{Tag("Firefox Mobile")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>Firefox for Desktop</td>
-   <td>{{Tag("Firefox Desktop")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>Firefox OS</td>
-   <td>{{Tag("Firefox OS")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>Mobile</td>
-   <td>{{Tag("Mobile")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>Web Development</td>
-   <td>{{Tag("Web Development")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>Add-ons &amp; Extensions</td>
-   <td>{{Tag("Add-ons ")}}|| {{Tag("Extensions")}} || {{Tag("Plugins")}} || {{Tag("Themes")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>Games</td>
-   <td>{{Tag("Games")}}</td>
-  </tr>
-  <tr>
-   <th>Skill level</th>
-   <td>I'm an Expert</td>
-   <td>{{Tag("Advanced")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>Intermediate</td>
-   <td>{{Tag("Intermediate")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>I'm Learning</td>
-   <td>{{Tag("Beginner")}}</td>
-  </tr>
-  <tr>
-   <th>Document type</th>
-   <td>Docs</td>
-   <td><em>This restricts the search to docs content, leaving out Hacks and other MDN content.</em></td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>Demos</td>
-   <td><em>This includes Demo Studio content in the search results.</em></td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>Tools</td>
-   <td>{{Tag("Tools")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>Code Samples</td>
-   <td>{{Tag("Example")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>How-To &amp; Tutorial</td>
-   <td>{{Tag("Guide")}}</td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>Developer Profiles</td>
-   <td><em>This includes developer profiles from the MDN site in the search results.</em></td>
-  </tr>
-  <tr>
-   <th> </th>
-   <td>External Resources</td>
-   <td><em>The dev team is still figuring this out...</em></td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Tagging_problems_you_can_fix">Tagging problems you can fix</h2>
-
-<p>There are several kinds of tag problems you can help fix:</p>
-
-<dl>
- <dt>No tags</dt>
- <dd>Generally articles should have at <em>least</em> a "<a href="/en-US/docs/Project:MDN/Contributing/Tagging_standards#Category" title="/en-US/docs/Project:MDN/Contributing/Tagging_standards#Categories">category</a>" tag and a "<a href="/en-US/docs/Project:MDN/Contributing/Tagging_standards#Topic" title="/en-US/docs/Project:MDN/Contributing/Tagging_standards#Topic">topic</a>" tag. Usually other tags are appropriate as well, but if you can help us ensure that the minimum tags are present, you'll be a documentation hero!</dd>
- <dt>Tags that don't follow our tagging standards</dt>
- <dd>Please fix any documents whose tags don't follow the standards on this page.<br>
- Note that due to a <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=776048">bug in Kuma</a>, some localized tags (such as <code>Référence</code>) may show up on some English pages. These tags are likely to reappear even if you delete them; don't bother trying to fix them until the Kuma bug is fixed.</dd>
- <dt>Incorrect tags</dt>
- <dd>If you're looking at an article about HTML and it's tagged "JavaScript", that's probably wrong! Likewise, if an article discusses Mozilla internals but has a "Web" tag, that's probably wrong too. Remove these tags and add the right tags if they aren't already there. Please also correct misspelled tags (e.g., "Javascript" will still match, since tags are case-insensitive, but let's not be sloppy!).</dd>
- <dt>Missing tags</dt>
- <dd>If an article has some but not all of the tags it needs, feel free to add more. For example, if a page in JavaScript reference is (correctly) tagged "JavaScript" but nothing else, you're invited to tag the page "Reference" as well!</dd>
- <dt>Tag spam</dt>
- <dd>This insidious beast is the most revolting tag problem of all: some Web vermin has deposited its droppings in the page tags (like "Free warez!" or "Hey I was browsing your site and wanted to ask you if you could help me solve this problem I'm having with Flash crashing all the time"). We've got to delete these right away! They're ugly, they're hard to manage if they're allowed to linger too long, and they're terrible for {{Glossary("SEO")}}.</dd>
-</dl>
-
-<p>If you see one (or more) of these problems, please <a href="/en-US/docs/Project:MDN/Contributing/Getting_started#Logging_into_MDN">log into MDN</a> and click EDIT at the top right of the MDN window. Once the editor loads up, scroll down to the bottom of the page, where you'll see the tag box. For more details on the tagging interface, see "<a href="/en-US/docs/Project:MDN/Contributing/Editor_guide#The_tags_box" title="/en-US/docs/Project:MDN/Contributing/Editor_guide#The_tags_box">The tags box</a>" in the <a href="/en-US/docs/Project:MDN/Contributing/Editor_guide" title="/en-US/docs/Project:MDN/Contributing/Editor_guide">MDN editor guide</a>.</p>