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

4 files changed, 0 insertions, 1121 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>
diff --git a/files/pl/mdn/guidelines/writing_style_guide/index.html b/files/pl/mdn/guidelines/writing_style_guide/index.html
deleted file mode 100644
index 893de382b8..0000000000
--- a/files/pl/mdn/guidelines/writing_style_guide/index.html
+++ /dev/null
@@ -1,557 +0,0 @@
----
-title: Przewodnik po stylach dokumentacji MDN
-slug: MDN/Guidelines/Writing_style_guide
-tags:
-  - Dokumentacja
-  - Dokumenty MDN
-  - Przewodnik
-  - Przewodnik stylu MDN
-  - Style w MDN
-translation_of: MDN/Guidelines/Writing_style_guide
-original_slug: MDN/Guidelines/Style_guide
----
-<div>{{MDNSidebar}}</div>
-
-<p><font><font>W celu wyświetlenia dokumentacji w zorganizowany, znormalizowany i łatwy do odczytania sposób, przewodnik stylu Mozilla Developer Network opisuje, w jaki sposób tekst powinien być zorganizowany, zapisany, sformatowany i tak dalej. </font><font>Są to wytyczne, a nie surowe zasady. </font></font><font><font>Jesteśmy bardziej zainteresowani treścią niż formatowaniem, nie jesteś zobowiązany do uczenia się całego przewodnika po stylach MDN przed wniesieniem wkładu. </font><font>Nie bądź jednak zdenerwowany lub zaskoczony, jeśli inny tłumacz zmodyfikuje w późniejszym czasie edytowany przez ciebie artykuł, aby dostosować się go, do głównych wytycznych stawianych dokumnetacji MDN.</font></font></p>
-
-<p>Jeśli szukasz informacji jak dany typ strony powinien być ustrukturyzowany, zobacz poradnik dotyczący <a href="/en-US/docs/MDN/Contribute/Content/Layout">układu stron MDN</a></p>
-
-<p>Aspekty językowe tego przewodnika dotyczą przede wszystkim dokumentacji w języku angielskim. Inne kraje mogą mieć (i mogą tworzyć) przewodniki po stylach we własnym języku. Tłumaczenia takie powinny być opublikowane jako podstrony, na lokalnych stronach MDN, dedykowanych dla danego języka przez zespół zajmujący się tłumaczeniami tzw. zespół lokalizacyjny.</p>
-
-<p>Zapoznaj się ze standardami styli stosowanych do treści witryn innych niż MDN, zobacz <a href="http://www.mozilla.org/en-US/styleguide/" title="http://www.mozilla.org/en-US/styleguide/">Przewodnik po stylach One Mozilla</a>.</p>
-
-<h2 id="Page_name_and_heading_capitalization" name="Page_name_and_heading_capitalization">Podstawy</h2>
-
-<h3 id="Tytuły_stron">Tytuły stron</h3>
-
-<p>Tytuły stron używane są w wynikach wyszukiwania, dzięki temu łatwiej jest znaleźć stronę w wynikach organicznych wyszukiwarek. Tytuły służą również do zachowania odpowiedniej struktury strony. Dlatego wraz z menu okruszkowym lub inaczej okruszkami(z ang. breadcrumbs)  umieszczane są na górze strony, w celu zachowania odpowiedniej jej hierarchii. Tytuł,  wyświetlany na górze w oknie przeglądarki, może różnić się od tzw. slug'a, który jest elemnetem adresu URL, następującym po "<em>&lt;locale&gt;/docs/</em>".</p>
-
-<h4 id="Tytuł_i_wielkie_literykapitaliki">Tytuł i wielkie litery(kapitaliki)</h4>
-
-<p>Tytuły stron i nagłówki sekcji(H1-H6) powinny być formatowane w taki sam sposób jak zdania. Wielka litera powinna być pisana na początku pierwszego słowa, również powinna wystąpić w nazwach własnych. Powinieneś unikać słów pisanych tzw. pismem wielbłądzim(które w anglojęzycznych krajach jest stosowane w tytułach): </p>
-
-<ul>
- <li><span class="correct"><strong>Poprawnie</strong></span>: "Nowa metoda tworzenia rolloverów w JavaScript"</li>
- <li><font color="#ff0000"><strong>Niepoprawnie</strong></font>: "Nowa Metoda Tworzenia Rolloverów w JavaScript"</li>
-</ul>
-
-<p>Mamy wiele starszych stron, które zostały napisane przed ustanowieniem tej reguły stylu. Jeśli chcesz, możesz je aktualizować w razie potrzeby. Stopniowo do nich docieramy.</p>
-
-<h4 id="Choosing_titles_and_slugs">Choosing titles and slugs</h4>
-
-<p>Page slugs should be kept short; when creating a new level of hierarchy, the new level's component in the slug should generally just be a word or two.</p>
-
-<p>Page titles, on the other hand, may be as long as you like, within reason, and they should be descriptive.</p>
-
-<h4 id="Creating_new_subtrees">Creating new subtrees</h4>
-
-<p>When you need to add a number of articles about a topic or topic area, you will typically do so by creating a landing page, then adding subpages for each of the individual articles. The landing page should open with a paragraph or two describing the topic or technology, then provide a list of the subpages with descriptions of each page. You can automate the insertion of pages into the list using a number of macros we've created.</p>
-
-<p>For example, consider the<a href="http://www.mozilla.org/en-US/styleguide/" title="http://www.mozilla.org/en-US/styleguide/"> </a><a href="/en-US/docs/Web/JavaScript">JavaScript</a> guide, which is structured like this:</p>
-
-<ul>
- <li><a href="/en-US/docs/Web/JavaScript/Guide" title="JavaScript/Guide">JavaScript/Guide</a> - Main table-of-contents page</li>
- <li><a href="/en-US/docs/Web/JavaScript/Guide/JavaScript_Overview" title="JavaScript/Guide/JavaScript_Overview">JavaScript/Guide/JavaScript Overview</a></li>
- <li><a href="/en-US/docs/JavaScript/Guide/Functions" title="JavaScript/Guide/Functions">JavaScript/Guide/Functions</a></li>
- <li><a href="/en-US/docs/JavaScript/Guide/Details_of_the_Object_Model" title="JavaScript/Guide/Details_of_the_Object_Model">JavaScript/Guide/Details of the Object Model</a></li>
-</ul>
-
-<p>Try to avoid putting your article at the top of the hierarchy, which slows the site down and makes search and site navigation less effective.</p>
-
-<h3 id="Sections.2C_Paragraphs.2C_Newlines" name="Sections.2C_Paragraphs.2C_Newlines">Sections, paragraphs, and newlines</h3>
-
-<p>Use heading levels in decreasing order: {{HTMLElement("h2")}} then {{HTMLElement("h3")}} then {{HTMLElement("h4")}}, without skipping levels. H2 is the highest level allowed because H1 is reserved for the page title. If you need more than three or four levels of headers you should consider breaking up the article into several smaller articles with a landing page, linking them together using the {{TemplateLink("Next")}}, {{TemplateLink("Previous")}}, and {{TemplateLink("PreviousNext")}} macros.</p>
-
-<p>The enter (or return) key on your keyboard starts a new paragraph. To insert a newline without a space, hold down the shift key while pressing enter.</p>
-
-<h3 id="Text_Formatting" name="Text_Formatting">Text formatting and styles</h3>
-
-<p>Use the "Formatting Styles" drop-down list to apply predefined styles to selected content.</p>
-
-<div class="note"><strong>Note: </strong>The "Note" style is used to call out important notes, like this one.</div>
-
-<div class="warning"><strong>Warning:</strong> Similarly, the "Warning" style creates warning boxes like this.</div>
-
-<p>Unless specifically instructed to do so, <strong>do not</strong> use the HTML <code>style</code> attribute to manually style content. If you can't do it using a predefined class, drop into <a href="https://chat.mozilla.org/#/room/#mdn:mozilla.org">Matrix</a> and ask for help.</p>
-
-<h3 id="Code_sample_style_and_formatting">Code sample style and formatting</h3>
-
-<h4 id="Tabs_and_line_breaks">Tabs and line breaks</h4>
-
-<p>Use two spaces per tab in all code samples. Code should be indented cleanly, with open-brace ("{") characters on the same line as the statement that opens the block. For example:</p>
-
-<pre class="brush: js notranslate">if (condition) {
-  /* handle the condition */
-} else {
-  /* handle the "else" case */
-}
-</pre>
-
-<p>Long lines shouldn't be allowed to stretch off horizontally to the extent that they require horizontal scrolling to read. Instead, break at natural breaking points. Some examples follow:</p>
-
-<pre class="brush: js notranslate">if (class.CONDITION || class.OTHER_CONDITION || class.SOME_OTHER_CONDITION
-       || class.YET_ANOTHER_CONDITION ) {
-  /* something */
-}
-
-var toolkitProfileService = Components.classes["@mozilla.org/toolkit/profile-service;1"]
-                           .createInstance(Components.interfaces.nsIToolkitProfileService);
-</pre>
-
-<h4 id="Inline_code_formatting">Inline code formatting</h4>
-
-<p>Use the "Code" button (labeled with two angle brackets "&lt;&gt;") to apply inline code-style formatting to function names, variable names, and method names (this uses the {{HTMLElement("code")}} element). For example, "the <code class="js plain">frenchText()</code> function".</p>
-
-<p>Method names should be followed by a pair of parentheses: <code>doSomethingUseful()</code>. This helps to differentiate methods from other code terms.</p>
-
-<h4 id="Syntax_highlighting">Syntax highlighting</h4>
-
-<p><img alt='Screenshot of the "syntax highlighting" menu.' src="https://mdn.mozillademos.org/files/7857/syntax-highlighting-menu.png" style="border-style: solid; border-width: 1px; float: right; height: 315px; margin: 2px 4px; width: 183px;">Entire lines (or multiple lines) of code should be formatted using syntax highlighting rather than the {{HTMLElement("code")}} element. Click the "pre" button in the toolbar to create the preformatted content box in which you'll then write your code. Then, with the text entry cursor inside the code box, select the appropriate language from the language list button to the right of the "pre" button, as seen in the screenshot to the right. The following example shows text with JavaScript formatting:</p>
-
-<div class="line number2 index1 alt1">
-<pre class="brush: js notranslate">for (var i = 0, j = 9; i &lt;= 9; i++, j--)
-  document.writeln("a[" + i + "][" + j + "]= " + a[i][j]);</pre>
-</div>
-
-<p>If no appropriate transformation is available, use the <code>pre</code> tag without specifying a language ("No Highlight" in the language menu).</p>
-
-<pre class="notranslate">x = 42;</pre>
-
-<h4 id="Styling_HTML_element_references">Styling HTML element references</h4>
-
-<p>There are various specific rules to follow when writing about HTML elements, in order to consistently describe the various components of elements, and to ensure that they're properly linked to detailed documentation.</p>
-
-<dl>
- <dt>Element names</dt>
- <dd>Use the {{TemplateLink("HTMLElement")}} macro, which creates a link to the page for that element. For example, writing \{{HTMLElement("title")}} produces "{{HTMLElement("title")}}". If you don't want to create a link, <strong>enclose the name in angle brackets</strong> and use "Code (inline)" style (e.g., <code>&lt;title&gt;</code>).</dd>
- <dt>Attribute names</dt>
- <dd>Use <strong>bold face</strong>.</dd>
- <dt>Attribute definitions</dt>
- <dd>Use the {{TemplateLink("htmlattrdef")}} macro (e.g., <span class="nowiki">\{{htmlattrdef("type")}}</span>) for the definition term, so that it can be linked to from other pages, then use the {{TemplateLink("htmlattrxref")}} macro (e.g., <span class="nowiki">\{{htmlattrxref("attr","element")}}</span>) to reference attribute definitions.</dd>
- <dt>Attribute values</dt>
- <dd>Use "Code (inline)" style, and do not use quotation marks around strings, unless needed by the syntax of a code sample. E.g.: When the <strong>type</strong> attribute of an <code>&lt;input&gt;</code> element is set to <code>email</code> or <code>tel</code> ...</dd>
- <dt>Labeling attributes</dt>
- <dd>Use labels like {{HTMLVersionInline(5)}} thoughtfully. For example, use them next to the bold attribute name but not for every occurrence in your body text.</dd>
-</dl>
-
-<h3 id="Latin_abbreviations" name="Latin_abbreviations">Latin abbreviations</h3>
-
-<h4 id="In_notes_and_parentheses" name="In_notes_and_parentheses">In notes and parentheses</h4>
-
-<ul>
- <li>Common Latin abbreviations (etc., i.e., e.g.) may be used in parenthetical expressions and in notes. Use periods in these abbreviations.
-  <ul>
-   <li><span class="correct"><strong>Correct</strong></span>: Web browsers (e.g. Firefox) can be used ...</li>
-   <li><span class="incorrect"><strong>Incorrect</strong></span>: Web browsers e.g. Firefox can be used ...</li>
-   <li><span class="incorrect"><strong>Incorrect</strong></span>: Web browsers, e.g. Firefox, can be used ...</li>
-   <li><span class="incorrect"><strong>Incorrect</strong></span>: Web browsers, (eg: Firefox) can be used ...</li>
-  </ul>
- </li>
-</ul>
-
-<h4 id="In_running_text" name="In_running_text">In running text</h4>
-
-<ul>
- <li>In regular text (i.e. text outside of notes or parentheses), use the English equivalent of the abbreviation.
-  <ul>
-   <li><span class="correct"><strong>Correct</strong></span>: ... web browsers, and so on.</li>
-   <li><span class="incorrect"><strong>Incorrect</strong></span>: ... web browsers, etc.</li>
-   <li><span class="correct"><strong>Correct</strong></span>: Web browsers such as Firefox can be used ...</li>
-   <li><span class="incorrect"><strong>Incorrect</strong></span>: Web browsers e.g. Firefox can be used ...</li>
-  </ul>
- </li>
-</ul>
-
-<h4 id="Meanings_and_English_equivalents_of_Latin_abbreviations" name="Meanings_and_English_equivalents_of_Latin_abbreviations">Meanings and English equivalents of Latin abbreviations</h4>
-
-<table class="fullwidth-table">
- <tbody>
-  <tr>
-   <th>Abbrev</th>
-   <th>Latin</th>
-   <th>English</th>
-  </tr>
-  <tr>
-   <td>cf.</td>
-   <td><em>confer</em></td>
-   <td>compare</td>
-  </tr>
-  <tr>
-   <td>e.g.</td>
-   <td><em>exempli gratia</em></td>
-   <td>for example</td>
-  </tr>
-  <tr>
-   <td>et al.</td>
-   <td><em>et alii</em></td>
-   <td>and others</td>
-  </tr>
-  <tr>
-   <td>etc.</td>
-   <td><em>et cetera</em></td>
-   <td>and so forth, and so on</td>
-  </tr>
-  <tr>
-   <td>i.e.</td>
-   <td><em>id est</em></td>
-   <td>that is, in other words</td>
-  </tr>
-  <tr>
-   <td>N.B.</td>
-   <td><em>nota bene</em></td>
-   <td>note well</td>
-  </tr>
-  <tr>
-   <td>P.S.</td>
-   <td><em>post scriptum</em></td>
-   <td>postscript</td>
-  </tr>
- </tbody>
-</table>
-
-<div class="note">
-<p><strong>Note:</strong> Always consider whether it's truly beneficial to use a Latin abbreviation. Some of these are used so rarely that many readers won't understand the meaning, and others are often confused with one another. And be sure that <strong>you</strong> use them correctly, if you choose to do so. For example, be careful not to confuse "e.g." with "i.e.", which is a common error.</p>
-</div>
-
-<h3 id="Acronyms_and_abbreviations" name="Acronyms_and_abbreviations">Acronyms and abbreviations</h3>
-
-<h4 id="Capitalization_and_periods" name="Capitalization_and_periods">Capitalization and periods</h4>
-
-<p>Use full capitals and delete periods in all acronyms and abbreviations, including organizations such as "US" and "UN".</p>
-
-<ul>
- <li><span class="correct"><strong>Correct</strong></span>: XUL</li>
- <li><span class="incorrect"><strong>Incorrect</strong></span>: X.U.L.; Xul</li>
-</ul>
-
-<h4 id="Expansion" name="Expansion">Expansion</h4>
-
-<p>On the first mention of a term on a page, expand acronyms likely to be unfamiliar to users. When in doubt, expand it, or, better, link it to the article or <a href="/en-US/docs/Glossary">glossary</a> entry describing the technology.</p>
-
-<ul>
- <li><span class="correct"><strong>Correct</strong></span>: "XUL (XML User Interface Language) is Mozilla's XML-based language..."</li>
- <li><span class="incorrect"><strong>Incorrect</strong></span>: "XUL is Mozilla's XML-based language..."</li>
-</ul>
-
-<h4 id="Plurals_of_acronyms_and_abbreviations" name="Plurals_of_acronyms_and_abbreviations">Plurals of acronyms and abbreviations</h4>
-
-<p>For plurals of acronyms or abbreviations, add <em>s</em>. Don't use an apostrophe. Ever. Please.</p>
-
-<ul>
- <li><span class="correct"><strong>Correct</strong></span>: CD-ROMs</li>
- <li><span class="incorrect"><strong>Incorrect</strong></span>: CD-ROM's</li>
-</ul>
-
-<h3 id="Contractions" name="Contractions">Capitalization</h3>
-
-<p>Use standard English capitalization rules in body text, and capitalize "World Wide Web" and "Web".</p>
-
-<h3 id="Contractions" name="Contractions">Contractions</h3>
-
-<p>Use contractions (e.g. "don't", "can't", "shouldn't") if you prefer. We're not that formal!</p>
-
-<h3 id="Pluralization" name="Pluralization">Pluralization</h3>
-
-<p>Use English-style plurals, not the Latin- or Greek-influenced forms.</p>
-
-<ul>
- <li><span class="correct"><strong>Correct</strong></span>: syllabuses, octopuses</li>
- <li><span class="incorrect"><strong>Incorrect</strong></span>: syllabi, octopi</li>
-</ul>
-
-<h3 id="Hyphenation" name="Hyphenation">Hyphenation</h3>
-
-<p>Hyphenate compounds when the last letter of the prefix is a vowel and is the same as the first letter of the root.</p>
-
-<ul>
- <li><font color="green"><strong>Correct</strong></font>: email, re-elect, co-op</li>
- <li><font color="red"><strong>Incorrect</strong></font>: e-mail, reelect, coop</li>
-</ul>
-
-<h3 id="Gender-neutral_language">Gender-neutral language</h3>
-
-<p>It is a good idea to use gender-neutral language in any kind of writing where gender is irrelevant to the subject matter, to make the text as inclusive as possible. So for example, if you are talking about the actions of a specific man, usage of he/his would be fine, but if the subject is a person of either gender, he/his isn't really appropriate.<br>
- <br>
- Let's take the following example:</p>
-
-<blockquote>
-<p>A confirmation dialog appears, asking the user if he allows the web page to make use of his web cam.</p>
-</blockquote>
-
-<blockquote>
-<p>A confirmation dialog appears, asking the user if she allows the web page to make use of her web cam.</p>
-</blockquote>
-
-<p>Both versions in this case are gender-specific. This could be fixed by using gender-neutral pronouns:</p>
-
-<blockquote>
-<p>A confirmation dialog appears, asking the user if they allow the web page to make use of their web cam.</p>
-</blockquote>
-
-<div class="note">
-<p><strong>Note:</strong> MDN allows the use of this very common syntax (which is controversial among usage authorities), in order to make up for the lack of a neutral gender in English. The use of the third-person plural as a neutral gender pronoun (that is, using "they," them", "their," and "theirs") is an accepted practice, commonly known as "<a href="http://en.wikipedia.org/wiki/Singular_they">singular 'they.'</a>"</p>
-</div>
-
-<p>You can use both genders:</p>
-
-<blockquote>
-<p>A confirmation dialog appears, asking the user if he or she allows the web page to make use of his/her web cam.</p>
-</blockquote>
-
-<p>making the users plural:</p>
-
-<blockquote>
-<p>A confirmation dialog appears, asking the users if they allow the web page to make use of their web cams.</p>
-</blockquote>
-
-<p>The best solution, of course, is to rewrite and eliminate the pronouns completely:</p>
-
-<blockquote>
-<p>A confirmation dialog appears, requesting the user's permission for web cam access.</p>
-</blockquote>
-
-<blockquote>
-<p>A confirmation dialog box appears, which asks the user for permission to use the web cam.</p>
-</blockquote>
-
-<p>The last way of dealing with the problem is arguably better, as it is not only grammatically more correct but removes some of the complexity associated with dealing with genders across different languages that may have wildly varying gender rules. This can make translation easier, both for readers reading English, then translating it into their own language as they read, and for localizers translating articles into their own language.</p>
-
-<h3 id="Numbers_and_numerals" name="Numbers_and_numerals">Numbers and numerals</h3>
-
-<h4 id="Dates">Dates</h4>
-
-<p>For dates (not including dates in code samples) use the format "January 1, 1990".</p>
-
-<ul>
- <li><span class="correct"><strong>Correct</strong></span>: February 24, 2006</li>
- <li><span class="incorrect"><strong>Incorrect</strong></span>: February 24th, 2006; 24 February, 2006; 24/02/2006</li>
-</ul>
-
-<p>Alternately, you can use the YYYY/MM/DD format.</p>
-
-<ul>
- <li><span class="correct"><strong>Correct</strong></span>: 2006/02/24</li>
- <li><span class="incorrect"><strong>Incorrect</strong></span>: 02/24/2006; 24/02/2006; 02/24/06</li>
-</ul>
-
-<h4 id="Decades" name="Decades">Decades</h4>
-
-<p>For decades, use the format "1990s". Don't use an apostrophe.</p>
-
-<ul>
- <li><span class="correct"><strong>Correct</strong></span>: 1990s</li>
- <li><span class="incorrect"><strong>Incorrect</strong></span>: 1990's</li>
-</ul>
-
-<h4 id="Plurals_of_numerals" name="Plurals_of_numerals">Plurals of numerals</h4>
-
-<p>For plurals of numerals add "s". Don't use an apostrophe.</p>
-
-<ul>
- <li><span class="correct"><strong>Correct</strong></span>: 486s</li>
- <li><span class="incorrect"><strong>Incorrect</strong></span>: 486's</li>
-</ul>
-
-<h4 id="Commas" name="Commas">Commas</h4>
-
-<p>In running text, use commas only in five-digit and larger numbers.</p>
-
-<ul>
- <li><span class="correct"><strong>Correct</strong></span>: 4000; 54,000</li>
- <li><span class="incorrect"><strong>Incorrect</strong></span>: 4,000; 54000</li>
-</ul>
-
-<h3 id="Punctuation" name="Punctuation">Punctuation</h3>
-
-<h4 id="Serial_comma" name="Serial_comma">Serial comma</h4>
-
-<p><strong>Use the serial comma</strong>. The serial (also known as "Oxford") comma is the comma that appears before the conjunction in a series of three or more items.</p>
-
-<ul>
- <li><span class="correct"><strong>Correct</strong></span>: I will travel on trains, planes, and automobiles.</li>
- <li><span class="incorrect"><strong>Incorrect</strong></span>: I will travel on trains, planes and automobiles.</li>
-</ul>
-
-<div class="note">
-<p><strong>Note:</strong> This is in contrast to the <a href="http://www.mozilla.org/en-US/styleguide/" title="http://www.mozilla.org/en-US/styleguide/">One Mozilla style guide</a>, which specifies that the serial comma is not to be used. MDN is an exception to this rule.</p>
-</div>
-
-<h3 id="Spelling" name="Spelling">Spelling</h3>
-
-<p>For words with variant spellings, always use the first entry at <a href="http://www.answers.com/library/Dictionary">Answers.com</a>. Do not use variant spellings.</p>
-
-<ul>
- <li><span class="correct"><strong>Correct</strong></span>: localize, honor</li>
- <li><span class="incorrect"><strong>Incorrect</strong></span>: localise, honour</li>
-</ul>
-
-<h3 id="Terminology">Terminology</h3>
-
-<h4 id="Obsolete_vs._deprecated">Obsolete vs. deprecated</h4>
-
-<p>It's important to be clear on the difference between the terms <strong>obsolete</strong> and <strong>deprecated</strong>.</p>
-
-<dl>
- <dt>Obsolete:</dt>
- <dd>On MDN, the term <strong>obsolete</strong> marks an API or technology that is not only no longer recommended, but also no longer implemented in the browser. For Mozilla-specific technologies, the API is no longer implemented in Mozilla code; for Web standard technology, the API or feature is no longer supported by current, commonly-used browsers.</dd>
- <dt>Deprecated:</dt>
- <dd>On MDN, the term <strong>deprecated</strong> marks an API or technology that is no longer recommended, but is still implemented and may still work. These technologies will in theory eventually become <em>obsolete</em> and be removed, so you should stop using them. For Mozilla-specific technologies, the API is still supported in Mozilla code; for Web standard technology, the API or feature has been removed or replaced in a recent version of the defining standard.</dd>
-</dl>
-
-<h4 id="HTML_elements">HTML elements</h4>
-
-<p>Use "elements" to refer to HTML and XML elements, rather than "tags". In addition, they should almost always be wrapped in "&lt;&gt;", and should be in the {{HTMLElement("code")}} style. Also, at least the first time you reference a given element in a section should use the {{TemplateLink("HTMLElement")}} macro, to create a link to the documentation for the element (unless you're writing within that element's reference document page).</p>
-
-<ul>
- <li><span class="correct"><strong>Correct</strong></span>: the {{HTMLElement("span")}} element</li>
- <li><span class="incorrect"><strong>Incorrect</strong></span>: the span tag</li>
-</ul>
-
-<h4 id="User_interface_actions">User interface actions</h4>
-
-<p>In task sequences, describe user interface actions using the imperative mood. Identify the user interface element by its label and type.</p>
-
-<ul>
- <li><span class="correct"><strong>Correct</strong></span>: Click the Edit button.</li>
- <li><span class="incorrect"><strong>Incorrect</strong></span>: Click Edit.</li>
-</ul>
-
-<h3 id="Voice">Voice</h3>
-
-<p>While the active voice is generally preferred, the passive voice is also acceptable, given the informal feel of our content. Try to be consistent, though.</p>
-
-<h2 id="Wiki_markup_and_usage">Wiki markup and usage</h2>
-
-<h3 id="External_links">External links</h3>
-
-<p>To automatically create a link to a Bugzilla bug, use this template:</p>
-
-<pre class="notranslate">\{{Bug(322603)}}
-</pre>
-
-<p>This results in:</p>
-
-<p>{{Bug(322603)}}</p>
-
-<p>For WebKit bugs, you can use this template:</p>
-
-<pre class="notranslate">\{{Webkitbug("322603")}}
-</pre>
-
-<p>This results in:</p>
-
-<p>{{Webkitbug("322603")}}</p>
-
-<h3 id="Page_tags">Page tags</h3>
-
-<p>Tags provide meta information about a page and/or indicate that a page has specific improvements needed to its content. Every page in the wiki should have tags. You can find details on tagging in our <a href="/en-US/docs/MDN/Contribute/Howto/Tag">How to properly tag pages</a> guide.</p>
-
-<p>The tagging interface lives at the bottom of a page while you're in edit mode, and looks something like this:</p>
-
-<p><img alt="Screenshot of the UX for adding and removing tags on MDN" src="https://mdn.mozillademos.org/files/7859/tag-interface.png" style="border-style: solid; border-width: 1px; height: 167px; width: 863px;"></p>
-
-<p>To add a tag, click in the edit box at the end of the tag list and type the tag name you wish to add. Tags will autocomplete as you type. Press enter (or return) to submit the new tag. Each article may have as many tags as needed. For example, an article about using JavaScript in AJAX programming might have both "JavaScript" and "AJAX" as tags.</p>
-
-<p>To remove a tag, simply click the little "X" icon in the tag.</p>
-
-<h4 id="Tagging_pages_that_need_work">Tagging pages that need work</h4>
-
-<p>In addition to using tags to track information about the documentation's quality and content, we also use them to mark articles as needing specific types of work.</p>
-
-<h4 id="Tagging_obsolete_pages">Tagging obsolete pages</h4>
-
-<p>Use the following tags for pages that are not current:</p>
-
-<ul>
- <li><em>Junk</em>: Use for spam, pages created by mistake, or content that is so bad that it should be deleted. Pages with this tag are deleted from time to time.</li>
- <li><em>Obsolete</em>: Use for content that is technically superceded, but still valid in context. For example an HTML element that is obsolete in HTML5 is still valid in HTML 4.01. You can also use the <span class="nowiki">{{TemplateLink("obsolete_header")}}</span> macro to put a prominent banner on the topic.</li>
- <li><em>Archive</em>: Use for content that is technically superceded and no longer useful. If possible, add a note to the topic referring readers to a more current topic. For example, a page that describes how to use the Mozilla CVS repository should refer readers to a current topic on using Mercurial repos. (If no corresponding current topic exists, use the <em>NeedsUpdate</em> tag, and add an explanation on the Talk page.) Pages with the Archive tag are eventually moved from the main content of MDN to the <a href="/en-US/docs/Archive">Archive</a> section.</li>
-</ul>
-
-<h3 id="SEO_summary">SEO summary</h3>
-
-<p>The SEO summary is a very short summary of the page. It will be reported as a summary of the article to robots crawling the site, and will then appear in search results for the page. It is also used by macros that automate the construction of landing pages inside MDN itself.</p>
-
-<p>By default, the first pagragraph of the page is used as the SEO summary. However you can override this behavior by marking a section with the <a href="/en-US/docs/Project:MDN/Contributing/Editor_guide/Editing#Formatting_styles">"SEO summary" style in the WYSIWYG editor</a>.</p>
-
-<h3 id="Landing_pages">Landing pages</h3>
-
-<p><strong>Landing pages</strong> are pages at the root of a topic area of the site, such as the main <a href="/en-US/docs/CSS" title="CSS">CSS</a> or <a href="/en-US/docs/HTML" title="HTML">HTML</a> pages. They have a standard format that consists of three areas:</p>
-
-<ol>
- <li>A brief (typically one paragraph) overview of what the technology is and what it's used for. See {{anch("Writing a landing page overview")}} for tips.</li>
- <li>A two-column list of links with appropriate headings. See {{anch("Creating a page link list")}} for guidelines.</li>
- <li>An <strong>optional</strong> "Browser compatibility" section at the bottom of the page.</li>
-</ol>
-
-<h4 id="Creating_a_page_link_list">Creating a page link list</h4>
-
-<p>The link list section of an MDN landing page consists of two columns. These are created using the following HTML:</p>
-
-<pre class="brush: html notranslate">&lt;div class="row topicpage-table"&gt;
-  &lt;div class="section"&gt;
-    ... left column contents ...
-  &lt;/div&gt;
-  &lt;div class="section"&gt;
-    ... right column contents ...
-  &lt;/div&gt;
-&lt;/div&gt;</pre>
-
-<p>The left-hand column should be a list of articles, with an <code>&lt;h2&gt;</code> header at the top of the left column explaining that it's a list of articles about the topic (for example "Documentation and tutorials about foo"); this header should use the CSS class "Documentation". Below that is a <code>&lt;dl&gt;</code> list of articles, with each article's link in a <code>&lt;dt&gt;</code> block and a brief one-or-two sentence summary of the article in the corresponding <code>&lt;dd&gt;</code> block.</p>
-
-<p>The right-hand column should contain one or more of the following sections, in order:</p>
-
-<dl>
- <dt>Getting help from the community</dt>
- <dd>This should provide information on Matrix chat rooms and mailing lists available about the topic. The heading should use the class "Community".</dd>
- <dt>Tools</dt>
- <dd>A list of tools the user can look at to help with the use of the technology described in this section of MDN. The heading should use the class "Tools".</dd>
- <dt>Related topics</dt>
- <dd>A list of links to landing pages for other, related, technologies of relevance. The heading should use the class "Related_Topics".</dd>
-</dl>
-
-<p><strong>&lt;&lt;&lt;finish this once we finalize the landing page standards&gt;&gt;&gt;</strong></p>
-
-<h2 id="Using_inserting_images">Using, inserting images</h2>
-
-<p>It's sometimes helpful to provide an image in an article you create or modify, especially if the article is very technical. To include an image:</p>
-
-<ol>
- <li>Attach the desired image file to the article (at the bottom of every article in edit mode)</li>
- <li>Create an image in the WYSIWYG editor</li>
- <li>In the WYSIWYG editor in the drop-down list listing attachments, select the newly created attachment which is your image</li>
- <li>Press OK.</li>
-</ol>
-
-<h2 id="Other_References">Other References</h2>
-
-<h3 id="Preferred_style_guides" name="Preferred_style_guides">Preferred style guides</h3>
-
-<p>If you have questions about usage and style not covered here, we recommend referring to the <a href="http://www.economist.com/research/StyleGuide/">Economist style guide</a> or, failing that, the <a href="http://www.amazon.com/gp/product/0226104036/">Chicago Manual of Style</a>.</p>
-
-<h3 id="Preferred_dictionary" name="Preferred_dictionary">Preferred dictionary</h3>
-
-<p>For questions of spelling, please refer to <a href="http://www.answers.com/library/Dictionary">Answers.com</a>. The spell-checker for this site uses American English. Please do not use variant spellings (e.g., use <em>honor</em> rather than <em>honour</em>).</p>
-
-<p>We will be expanding the guide over time, so if you have specific questions that aren't covered in this document, please send them to the <a href="/en-US/docs/Project:Community" title="Project:en/Community">MDC mailing list</a> or <a href="/User:Sheppy" title="User:Sheppy">project lead</a> so we know what should be added.</p>
-
-<h3 id="MDC-specific" name="MDC-specific">MDN-specific</h3>
-
-<ul>
- <li><a href="/en-US/docs/Project:Custom_CSS_Classes" title="Project:en/Custom_CSS_Classes">Custom CSS classes</a> defined for all MDC pages.</li>
- <li><a href="/en-US/docs/Project:Custom_Templates" title="Project:en/Custom_Templates">Custom templates</a> created for use on MDC, with explanations.</li>
-</ul>
-
-<h3 id="Other_resources" name="Other_resources">Language, grammar, spelling</h3>
-
-<p>If you're interested in improving your writing and editing skills, you may find the following resources to be helpful.</p>
-
-<ul>
- <li><a href="http://www.amazon.com/Writing-Well-30th-Anniversary-Nonfiction/dp/0060891548">On Writing Well</a>, by William Zinsser (Amazon link)</li>
- <li><a href="http://www.amazon.com/Style-Basics-Clarity-Grace-4th/dp/0205830765/" title="http://www.amazon.com/Style-Lessons-Clarity-Grace-Edition/dp/0321898680">Style: The Basics of Clarity and Grace</a>, by Joseph Williams and Gregory Colomb (Amazon link)</li>
- <li><a href="http://www.bartleby.com/64/">American Heritage Book of English Usage</a></li>
- <li><a href="http://www.wsu.edu/~brians/errors/">Common Errors in English</a></li>
- <li><a href="http://www-personal.umich.edu/~jlawler/aue.html">English Grammar FAQ</a> (alt.usage.english)</li>
- <li><a href="http://www.angryflower.com/bobsqu.gif">Bob's quick guide to the apostrophe, you idiots</a> (funny)</li>
- <li><a href="http://www.amazon.com/Merriam-Websters-Concise-Dictionary-English-Usage/dp/B004L2KNI2" title="http://www.amazon.com/Merriam-Websters-Concise-Dictionary-English-Usage/dp/B004L2KNI2">Merriam-Webster's Concise Dictionary of English Usage</a> (Amazon link): Scholarly but user-friendly, evidence-based advice; very good for non-native speakers, especially for preposition usage.</li>
-</ul>
diff --git a/files/pl/mdn/tools/index.html b/files/pl/mdn/tools/index.html
deleted file mode 100644
index ad6d18d577..0000000000
--- a/files/pl/mdn/tools/index.html
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: MDN user guide
-slug: MDN/Tools
-translation_of: MDN/Tools
-translation_of_original: MDN/User_guide
-original_slug: MDN/User_guide
----
-<div>{{MDNSidebar}}</div><p>The Mozilla Developer Network site is an advanced system for finding, reading, and contributing to documentation and sample code for Web developers (as well as for Firefox and Firefox OS developers). The MDN user guide provides articles detailing how to use MDN to find the documentation you need, and, if you wish, how to help make the material better, more expansive, and more complete.</p>
-&lt;&gt;