update based on https://github.com/mdn/yari/issues/2028

11 files changed, 0 insertions, 1505 deletions

diff --git a/files/tr/mozilla/add-ons/sdk/index.html b/files/tr/mozilla/add-ons/sdk/index.html
deleted file mode 100644
index 0cfe0d7301..0000000000
--- a/files/tr/mozilla/add-ons/sdk/index.html
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: Add-on SDK
-slug: Mozilla/Add-ons/SDK
-translation_of: Archive/Add-ons/Add-on_SDK
----
-<p>Add-on SDK ile standart web teknolojilerini kullanarak Firefox eklentileri üretebilirsiniz. SDK, eklentileri yaratabileceğiniz JavaScript API'lerini ve eklentileri oluşturma, çalıştırma, test etme ve paketleme araçlarını içerir.</p>
-
-<hr>
-<h3 id="Öğreticiler">Öğreticiler</h3>
-
-<div class="column-container">
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials#getting-started">Başlarken</a></dt>
- <dd><a href="/en-US/Add-ons/SDK/Tutorials/Installation">SDK nasıl yüklenir </a>ve <a href="/en-US/Add-ons/SDK/Tutorials/Getting_Started_(jpm)">the jpm aracının kullanımı</a> , ve eklentileri paketleme.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials#interact-with-the-browser">Tarayıcı ile etkileşşim</a></dt>
- <dd><a href="/en-US/Add-ons/SDK/Tutorials/Open_a_Web_Page">Open web pages</a>, <a href="/en-US/Add-ons/SDK/Tutorials/Listen_For_Page_Load">listen for pages loading</a>, and <a href="/en-US/Add-ons/SDK/Tutorials/List_Open_Tabs">list open pages</a>.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials#development-techniques">Geliştirme teknikleri</a></dt>
- <dd>Alışılmış geliştirme yöntemlerini öğrenme, örneğin <a href="/en-US/Add-ons/SDK/Tutorials/Unit_testing">unit testing</a>, <a href="/en-US/Add-ons/SDK/Tutorials/Logging">logging</a>, <a href="/en-US/Add-ons/SDK/Tutorials/Creating_Reusable_Modules">creating reusable modules</a>, <a href="/en-US/Add-ons/SDK/Tutorials/l10n">localization</a>, ve <a href="/en-US/Add-ons/SDK/Tutorials/Mobile_development">mobile development</a>.</dd>
-</dl>
-</div>
-
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials#create-user-interfaces">Kullanıcı arayüzü üretme bileşenleri</a></dt>
- <dd>Kullanıcı arayüzü birimlerini yaratın. Mesela <a href="/en-US/Add-ons/SDK/Tutorials/Adding_a_Button_to_the_Toolbar"> araç çubuğu butonları</a>, <a href="/en-US/Add-ons/SDK/Tutorials/Add_a_Context_Menu_Item">içerik menüleri</a>, <a href="/en-US/Add-ons/SDK/Tutorials/Add_a_Menu_Item_to_Firefox">menü nesneleri</a> ve <a href="/en-US/Add-ons/SDK/Tutorials/Display_a_Popup">iletiler</a>.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials#modify-web-pages">Web sayfalarını modifiye edin.</a></dt>
- <dd>Modify pages <a href="/en-US/Add-ons/SDK/Tutorials/Modifying_Web_Pages_Based_on_URL">matching a URL pattern</a> or dynamically <a href="/en-US/Add-ons/SDK/Tutorials/Modifying_the_Page_Hosted_by_a_Tab">modify a particular tab</a>.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Annotator">Putting it together</a></dt>
- <dd>Walkthrough of the Annotator example add-on.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h3 id="Guides">Guides</h3>
-
-<div class="column-container">
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Guides#contributors-guide">Contributor's guide</a></dt>
- <dd>Learn <a href="/en-US/Add-ons/SDK/Guides/Getting_Started">how to start contributing</a> to the SDK, and about the most important idioms used in the SDK code, such as <a href="/en-US/Add-ons/SDK/Guides/Modules">modules</a>, <a href="/en-US/Add-ons/SDK/Guides/Classes_and_Inheritance">classes and inheritance</a>, <a href="/en-US/Add-ons/SDK/Guides/Private_Properties">private properties</a>, and <a href="/en-US/Add-ons/SDK/Guides/Content_Processes">content processes</a>.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Guides#sdk-infrastructure">SDK infrastructure</a></dt>
- <dd>Aspects of the SDK's underlying technology: <a href="/en-US/Add-ons/SDK/Guides/Module_structure_of_the_SDK">modules</a>, the <a href="/en-US/Add-ons/SDK/Guides/Program_ID">Program ID</a>, and the rules defining <a href="/en-US/Add-ons/SDK/Guides/Firefox_Compatibility">Firefox compatibility</a>.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Guides/Content_Scripts">Content scripts</a></dt>
- <dd>A detailed guide to working with content scripts.</dd>
-</dl>
-</div>
-
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Guides#sdk-idioms">SDK idioms</a></dt>
- <dd>The SDK's <a href="/en-US/Add-ons/SDK/Guides/Working_with_Events">event framework</a> and the <a href="/en-US/Add-ons/SDK/Guides/Two_Types_of_Scripts">distinction between add-on scripts and content scripts</a>.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Guides/XUL_Migration_Guide">XUL migration</a></dt>
- <dd>A guide to <a href="/en-US/Add-ons/SDK/Guides/XUL_Migration_Guide">porting XUL add-ons to the SDK</a>. This guide includes a <a href="/en-US/Add-ons/SDK/Guides/XUL_vs_SDK">comparison of the two toolsets</a> and a <a href="/en-US/Add-ons/SDK/Guides/Porting_the_Library_Detector">working example</a> of porting a XUL add-on.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Guides/Multiprocess_Firefox_and_the_SDK">Multiprocess Firefox and the SDK</a></dt>
- <dd>How to check whether your add-on is compatible with multiprocess Firefox, and fix it if it isn't.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h3 id="Reference">Reference</h3>
-
-<div class="column-container">
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/High-Level_APIs">High-Level APIs</a></dt>
- <dd>Reference documentation for the high-level SDK APIs.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Tools">Tools reference</a></dt>
- <dd>Reference documentation for the <a href="/en-US/Add-ons/SDK/Tools/jpm">jpm tool</a> used to develop, test, and package add-ons, the <a href="/en-US/Add-ons/SDK/Tools/console">console</a> global used for logging, and the <a href="/en-US/Add-ons/SDK/Tools/package_json">package.json</a> file.</dd>
-</dl>
-</div>
-
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Low-Level_APIs">Low-Level APIs</a></dt>
- <dd>Reference documentation for the low-level SDK APIs.</dd>
-</dl>
-</div>
-</div>
diff --git a/files/tr/mozilla/add-ons/sdk/tools/index.html b/files/tr/mozilla/add-ons/sdk/tools/index.html
deleted file mode 100644
index 8c67b4644e..0000000000
--- a/files/tr/mozilla/add-ons/sdk/tools/index.html
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Tools
-slug: Mozilla/Add-ons/SDK/Tools
-tags:
-  - Add-on SDK
-  - CFX
-  - JPM
-  - NeedsTranslation
-  - TopicStub
-translation_of: Archive/Add-ons/Add-on_SDK/Tools
----
-<p>Articles listed here provide a reference for the SDK's tools:</p>
-
-<p>{{ LandingPageListSubpages ("/en-US/Add-ons/SDK/Tools", 7) }}</p>
diff --git a/files/tr/mozilla/add-ons/sdk/tools/package_json/index.html b/files/tr/mozilla/add-ons/sdk/tools/package_json/index.html
deleted file mode 100644
index 7b395a2fa1..0000000000
--- a/files/tr/mozilla/add-ons/sdk/tools/package_json/index.html
+++ /dev/null
@@ -1,323 +0,0 @@
----
-title: package.json
-slug: Mozilla/Add-ons/SDK/Tools/package_json
-translation_of: Archive/Add-ons/Add-on_SDK/Tools/package_json
----
-<p>{{AddonSidebar}}</p>
-
-<p><span class="seoSummary"><code>package.json</code> dosyası eklentiniz için manifesto görevi görür, sadece Add-ons Manager'daki (Eklenti Yöneticisi) sunum için betimleyici bilgileri değil, eklentiniz için diğer gerekli meta bilgilerini de içerir.</span></p>
-
-<p>Some of its entries, such as <a href="/en-US/Add-ons/SDK/Tools/package_json#icon"><code>icon</code></a>, <a href="/en-US/Add-ons/SDK/Tools/package_json#name"><code>name</code></a>, and <a href="/en-US/Add-ons/SDK/Tools/package_json#description"><code>description</code></a>, have direct analogues in the <a href="https://developer.mozilla.org/en-US/docs/Install_Manifests">install manifest</a> format, and entries from <code>package.json</code> are written into the install manifest when the add-on is built using <a href="/en-US/Add-ons/SDK/Tools/jpm#jpm_xpi"><code>jpm xpi</code></a>.</p>
-
-<p>Others, such as <a href="/en-US/Add-ons/SDK/Tools/package_json#lib"><code>lib</code></a>, <a href="/en-US/Add-ons/SDK/Tools/package_json#permissions"><code>permissions</code></a>, and <a href="/en-US/Add-ons/SDK/Tools/package_json#preferences"><code>preferences</code></a>, represent instructions to the <a href="/en-US/Add-ons/SDK/Tools/jpm">jpm</a> tool itself to generate and include particular code and data structures in your add-on.</p>
-
-<h2 id="Manifest_oluşturma">Manifest oluşturma</h2>
-
-<p>The <code>package.json</code> file is initially generated in your add-on's root directory the first time you run <a href="/en-US/Add-ons/SDK/Tools/jpm#jpm_init"><code>jpm init</code></a>. It looks like this (assuming the add-on's directory is "my-addon"):</p>
-
-<pre class="brush: json">{
-  "name": "my-addon",
-  "title": "my-addon",
-  "id": "jid1-1FERGV45e4f4f",
-  "description": "a basic add-on",
-  "author": "",
-  "license": "MPL-2.0",
-  "version": "0.1"
-}</pre>
-
-<p>If you are using the new <a href="/en-US/Add-ons/SDK/Tools/jpm">jpm tool</a>, you can easily access manifest data from package.json by requiring it like any other module:</p>
-
-<pre class="brush: js" id="comment_text_1">var title = require("./package.json").title;</pre>
-
-<h2 id="Key_reference">Key reference</h2>
-
-<p><code>package.json</code> may contain the following keys:</p>
-
-<table class="standard-table">
- <tbody>
-  <tr>
-   <td id="author"><code>author</code></td>
-   <td>
-    <p>The name of the package's original author; this could be the name of a person or a company. Defaults to an empty string. It may include a optional URL in parentheses and an email address in angle brackets.</p>
-
-    <p>This value will be used as the add-on's <a href="https://developer.mozilla.org/en-US/docs/Install_Manifests#creator"><code>em:creator</code></a> element in the <code>install.rdf</code> file generated by <code>cfx</code>.</p>
-
-    <div class="note"><strong>Note:</strong> <a href="https://developer.mozilla.org/Add-ons/SDK/Tools/jpm">jpm</a> supports <a href="https://docs.npmjs.com/files/package.json#people-fields-author-contributors">NodeJS people fields</a>.</div>
-   </td>
-  </tr>
-  <tr>
-   <td id="contributors"><code>contributors</code></td>
-   <td>
-    <p>An array of additional <a href="/en-US/Add-ons/SDK/Tools/package_json#author"><code>author</code></a> strings, identifying other contributors to the add-on.</p>
-
-    <p>These values will be used as the add-on's <a href="https://developer.mozilla.org/en-US/docs/Install_Manifests#contributor"><code>em:contributor</code></a> elements in its <code>install.rdf</code>.</p>
-
-    <div class="note"><strong>Note:</strong> This is deprecated along with <code>cfx</code>; it's not available when using <a href="/en-US/Add-ons/SDK/Tools/jpm">jpm</a>.</div>
-   </td>
-  </tr>
-  <tr>
-   <td id="dependencies"><code>dependencies</code></td>
-   <td>
-    <p>A string or an array of strings specifying the names of packages that this add-on requires in order to function properly.</p>
-   </td>
-  </tr>
-  <tr>
-   <td id="description"><code>description</code></td>
-   <td>
-    <p>The add-on's description; this is a human-readable message describing what the add-on does. This defaults to the text "a basic add-on".</p>
-
-    <p>This value will be used as the add-on's <a href="https://developer.mozilla.org/en-US/docs/Install_Manifests#description"><code>em:description</code></a> element in its <code>install.rdf</code>.</p>
-   </td>
-  </tr>
-  <tr>
-   <td id="engines"><code>engines</code></td>
-   <td>
-    <p>Object with supported applications (key) and required version numbers (value). The version number can both specify a minimum and maximum version separated by a space.</p>
-
-    <ul>
-     <li><code>firefox</code>: Firefox Desktop</li>
-     <li><code>fennec</code>: Firefox for Android</li>
-     <li><code>thunderbird</code>: Thunderbird</li>
-     <li><code>seamonkey</code>: SeaMonkey</li>
-     <li>Any application UUID</li>
-    </ul>
-
-    <p>Example:</p>
-
-    <pre>
-<code>  "engines": {
-    "firefox": "&gt;=38.0a1",
-    "fennec": "&gt;=38.0a1"
-  }</code></pre>
-   </td>
-  </tr>
-  <tr>
-   <td id="fullName"><code>fullName</code> {{deprecated_inline}}</td>
-   <td>
-    <div class="note"><strong>Note:</strong> This is deprecated along with <code>cfx</code>; it's not available when using <a href="/en-US/Add-ons/SDK/Tools/jpm">jpm</a>.</div>
-
-    <p>The full name of the package. It can contain spaces.</p>
-
-    <p>If this key is present, its value will be used as the add-on's <a href="https://developer.mozilla.org/en-US/docs/Install_Manifests#name"><code>em:name</code></a> element in its <code>install.rdf</code>.</p>
-   </td>
-  </tr>
-  <tr>
-   <td id="harnessClassID"><code>harnessClassID</code> {{deprecated_inline}}</td>
-   <td>
-    <div class="note"><strong>Note:</strong> This is deprecated along with <code>cfx</code>; it's not available when using <a href="/en-US/Add-ons/SDK/Tools/jpm">jpm</a>.</div>
-
-    <p>String in the <a href="https://developer.mozilla.org/en-US/docs/Generating_GUIDs">GUID format</a>.</p>
-
-    <p>This is used as a <a href="https://developer.mozilla.org/en-US/docs/Creating_XPCOM_Components/An_Overview_of_XPCOM#CID"><code>classID</code></a> of the "harness service" XPCOM component. Defaults to a random GUID generated by <code>cfx</code>.</p>
-   </td>
-  </tr>
-  <tr>
-   <td id="homepage"><code>homepage</code></td>
-   <td>
-    <p>The URL of the add-on's website.</p>
-
-    <p>This value will be used as the add-on's <a href="https://developer.mozilla.org/en-US/docs/Install_Manifests#homepageURL"><code>em:homepageURL</code></a> element in its <code>install.rdf</code>.</p>
-   </td>
-  </tr>
-  <tr>
-   <td id="icon"><code>icon</code></td>
-   <td>
-    <p>The path to an image file containing the icon for the add-on. Optional: you can have no icon field in package.json and put your icon named "icon.png" in the root directory of your add-on. If no icon is specified, the standard add-on icon will be used by default.</p>
-
-    <div class="warning">
-    <p>When using <a href="/en-US/Add-ons/SDK/Tools/jpm">jpm</a>, using a relative path to the data directory (to make it re-usable for add-on HTML content) does not work.</p>
-
-    <p>You can generate the URL to your add-on icon in the data directory using the URL format below, where "your-addon-name" is the value in the name field of package.json.</p>
-
-    <p>resource://@your-addon-name/data/your-icon-name.png</p>
-    </div>
-
-    <p>This value will be used as the add-on's <a href="https://developer.mozilla.org/en-US/docs/Install_Manifests#iconURL"><code>em:iconURL</code></a> element in its <code>install.rdf</code>.</p>
-
-    <p>The icon may be up to 48x48 pixels in size. A larger icon is will work, but may either scaled and possibly distorted) or might break parts of Firefox UI. (If you test this, please add the result here.)</p>
-
-    <p>This can also be an object with the image size as key and the (absolute) location of the image as value. JPM looks for the sizes 64, 48 and 32.</p>
-   </td>
-  </tr>
-  <tr>
-   <td id="icon64"><code>icon64</code> {{deprecated_inline}}</td>
-   <td>
-    <div class="note">
-    <p><strong>Note:</strong> This is deprecated along with <code>cfx</code>; it's not available when using <a href="/en-US/Add-ons/SDK/Tools/jpm">jpm</a>.</p>
-    </div>
-
-    <p><span style="background-color: rgba(212, 221, 228, 0.14902);">The path to an image</span> containing the large icon for the add-on. Defaults to <code>icon64.png</code>. If you don't provide an icon here, the same icon as specified by <code>icon</code> will be used.</p>
-
-    <p>This value will be used as the add-on's <a href="https://developer.mozilla.org/en-US/docs/Install_Manifests#icon64URL"><code>em:icon64URL</code></a> element in its <code>install.rdf</code>.</p>
-
-    <p>The icon may be up to 64x64 pixels in size.</p>
-   </td>
-  </tr>
-  <tr>
-   <td><code>id</code></td>
-   <td>
-    <p>A globally unique identifier for the add-on.</p>
-
-    <p>This value will be used as the add-on's <a href="https://developer.mozilla.org/en-US/docs/Install_Manifests#id"><code>em:id</code></a> element in its <code>install.rdf</code>.</p>
-
-    <p>See the <a href="/en-US/Add-ons/SDK/Guides/Program_ID">Program ID documentation</a>.</p>
-   </td>
-  </tr>
-  <tr>
-   <td><code>lib</code></td>
-   <td>
-    <p>String representing the top-level module directory provided in this add-on. Defaults to "lib".</p>
-
-    <div class="note">
-    <p><strong>Note:</strong> This is deprecated along with <code>cfx</code> and is not available when using <a href="/en-US/Add-ons/SDK/Tools/jpm">jpm</a>.</p>
-    </div>
-   </td>
-  </tr>
-  <tr>
-   <td id="license"><code>license</code></td>
-   <td>
-    <p>The name of the license under which the add-on is distributed, with an optional URL in parentheses. Defaults to <code>"MPL-2.0"</code>.</p>
-
-    <div class="note">
-    <p><strong>Note</strong>: It is recommended that you use an <a href="https://spdx.org/licenses/">SPDX license ID</a>.</p>
-    </div>
-   </td>
-  </tr>
-  <tr>
-   <td><code>locales</code></td>
-   <td>
-    <p>An object holding <a href="/en-US/docs/Glossary/JSON">JSON</a> objects referenced by a <a href="https://wiki.mozilla.org/L10n:Locale_Codes">locale name</a> that use the following keys: <code>title</code>, <code>description</code> and <code>homepage</code>. These JSON objects will be used to localizations for the add-on's meta data shown within the Add-ons Manager.</p>
-
-    <p>See the documentation for <a href="/en-US/Add-ons/SDK/Tutorials/l10n#Using_localized_strings_in_add-on_meta_data">how to localize the add-on's meta data</a>.</p>
-   </td>
-  </tr>
-  <tr>
-   <td id="main"><code>main</code></td>
-   <td>
-    <p>A string representing the name of a program module that is located in one of the top-level module directories specified by <a href="/en-US/Add-ons/SDK/Tools/package_json#lib"><code>lib</code></a>. Defaults to <code>"index.js"</code>.</p>
-   </td>
-  </tr>
-  <tr>
-   <td><code>name</code></td>
-   <td>
-    <p>The add-on's name. This name cannot contain spaces or periods, and defaults to the name of the parent directory.</p>
-
-    <p>When the add-on is built as an XPI, if the <a href="/en-US/Add-ons/SDK/Tools/package_json#fullName"><code>fullName</code></a> and <a href="/en-US/Add-ons/SDK/Tools/package_json#title"><code>title</code></a> keys are not present, <code>name</code> is used as the add-on's <a href="https://developer.mozilla.org/en-US/docs/Install_Manifests#name"><code>em:name</code></a> element in its <code>install.rdf</code>.</p>
-   </td>
-  </tr>
-  <tr>
-   <td id="packages"><code>packages</code></td>
-   <td>
-    <div class="note">
-    <p><strong>Note:</strong> This is deprecated along with <code>cfx</code> and is not available when using <a href="/en-US/Add-ons/SDK/Tools/jpm">jpm</a>.</p>
-    </div>
-
-    <p>A string pointing to a directory containing additional packages. Defaults to <code>"packages"</code>.</p>
-   </td>
-  </tr>
-  <tr>
-   <td id="permissions"><code>permissions</code></td>
-   <td>
-    <p>A set of permissions that the add-on needs.</p>
-
-    <p><strong><code>private-browsing</code></strong>: a boolean indicating whether or not the add-on supports private browsing. If this value is not <code>true</code> or is omitted, then the add-on will not see any private windows or objects, such as tabs, that are associated with private windows. See the documentation for the <a href="/en-US/Add-ons/SDK/High-Level_APIs/private-browsing"><code>private-browsing</code> module</a>.</p>
-
-    <p><strong><code>cross-domain-content</code></strong>: a list of domains for which content scripts are given cross-domain privileges to access content in iframes or to make XMLHTTPRequests. See the documentation for <a href="/en-US/Add-ons/SDK/Guides/Content_Scripts/Cross_Domain_Content_Scripts">enabling cross-domain content scripts</a>.</p>
-
-    <p><strong><code>multiprocess</code></strong>: a Boolean value declaring whether this add-on is, or is not, compatible with <a href="/en-US/Add-ons/Working_with_multiprocess_Firefox">multiprocess Firefox</a>.</p>
-
-    <div class="note">
-    <p><strong>Note</strong> the <code>multiprocess</code> permission is not supported by <a href="/en-US/Add-ons/SDK/Tools/cfx">cfx</a>.</p>
-    </div>
-   </td>
-  </tr>
-  <tr>
-   <td id="preferences"><code>preferences</code></td>
-   <td>
-    <p>An array of <a href="/en-US/docs/Glossary/JSON">JSON</a> objects that use the following keys: <code>name</code>,<code>type</code>, <code>value</code>, <code>title</code>, and <code>description</code>. These JSON objects will be used to create a preferences interface for the add-on in the Add-ons Manager.</p>
-
-    <p>See the documentation for the <a href="/en-US/Add-ons/SDK/High-Level_APIs/simple-prefs"><code>simple-prefs</code> module</a>.</p>
-   </td>
-  </tr>
-  <tr>
-   <td id="preferences-branch"><code>preferences-branch</code></td>
-   <td>Use this to specify an alternative branch for your add-on's simple-prefs. See <a href="/en-US/Add-ons/SDK/High-Level_APIs/simple-prefs#Simple-prefs_in_the_preferences_system">"Simple-prefs in the preferences system"</a> for more details.</td>
-  </tr>
-  <tr>
-   <td><code>title</code></td>
-   <td>
-    <p>The human-readable title of the package; this can contain spaces.</p>
-
-    <p>If this key is present, its value will be used as the add-on's <a href="https://developer.mozilla.org/en-US/docs/Install_Manifests#name"><code>em:name</code></a> element in its <code>install.rdf</code>.</p>
-   </td>
-  </tr>
-  <tr>
-   <td id="translators"><code>translators</code></td>
-   <td>
-    <p>An array of strings listing the people who contributed to the localization of this add-on.</p>
-
-    <p>These values will be used as the add-on's <a href="https://developer.mozilla.org/en-US/docs/Install_Manifests#translator"><code>em:translator</code></a> elements in its <code>install.rdf</code>.</p>
-
-    <div class="note"><strong>Note:</strong> <a href="https://developer.mozilla.org/Add-ons/SDK/Tools/jpm">jpm</a> supports <a href="https://docs.npmjs.com/files/package.json#people-fields-author-contributors">NodeJS people fields</a>.</div>
-   </td>
-  </tr>
-  <tr>
-   <td id="unpack"><code>unpack</code></td>
-   <td>
-    <p>Same as the <code><a href="/en-US/Add-ons/Install_Manifests#unpack">unpack</a></code> in an <code>install.rdf</code> file.</p>
-
-    <p>Useful when the extension contains binaries.</p>
-   </td>
-  </tr>
-  <tr>
-   <td id="updateKey"><code>updateKey</code></td>
-   <td>
-    <p>Same as the <code><a href="/en-US/Add-ons/Install_Manifests#updateKey">updateKey</a></code> in an <code>install.rdf</code> file.</p>
-
-    <p>See <a href="/en-US/Add-ons/SDK/Tools/jpm#Supporting_updates_for_self-hosted_add-ons">Supporting updates for self-hosted add-ons</a>.</p>
-
-    <div class="note">
-    <p><strong>Note:</strong> This key is only available with <a href="/en-US/Add-ons/SDK/Tools/jpm">jpm</a>.</p>
-    </div>
-   </td>
-  </tr>
-  <tr>
-   <td id="updateLink"><code>updateLink</code></td>
-   <td>
-    <p>Same as the <code><a href="/en-US/docs/Extension_Versioning%2C_Update_and_Compatibility#Securing_Updates">updateLink</a></code> for an <code>update.rdf</code> file. Previously was <code><a href="/en-US/Add-ons/SDK/Tools/cfx#updateURL_and_updateLink">--update-link in cfx</a></code>.</p>
-
-    <p>See <a href="/en-US/Add-ons/SDK/Tools/jpm#Supporting_updates_for_self-hosted_add-ons">Supporting updates for self-hosted add-ons</a>.</p>
-
-    <div class="note">
-    <p><strong>Note:</strong> This key is only available with <a href="/en-US/Add-ons/SDK/Tools/jpm">jpm</a>.</p>
-    </div>
-   </td>
-  </tr>
-  <tr>
-   <td id="updateURL"><code>updateURL</code></td>
-   <td>
-    <p>Same as the <code><a href="/en-US/Add-ons/Install_Manifests#updateURL">updateURL</a></code> for an <code>install.rdf</code> file.</p>
-
-    <p>See <a href="/en-US/Add-ons/SDK/Tools/jpm#Supporting_updates_for_self-hosted_add-ons">Supporting updates for self-hosted add-ons</a>.</p>
-
-    <div class="note">
-    <p><strong>Note:</strong> This key is only available with <a href="/en-US/Add-ons/SDK/Tools/jpm">jpm</a>.</p>
-    </div>
-   </td>
-  </tr>
-  <tr>
-   <td id="version"><code>version</code></td>
-   <td>
-    <p>String representing the version of the add-on. Defaults to "0.0.1".</p>
-
-    <p>This value is used as the add-on's <a href="https://developer.mozilla.org/en-US/docs/Install_Manifests#version"><code>em:version</code></a> element in its <code>install.rdf</code>.</p>
-
-    <div class="note">
-    <p><strong>Note:</strong> For <a href="/en-US/Add-ons/SDK/Tools/jpm">jpm</a> the version must be a valid <a href="http://semver.org/">semver</a>.</p>
-    </div>
-   </td>
-  </tr>
- </tbody>
-</table>
-
-<p> </p>
diff --git a/files/tr/mozilla/add-ons/sdk/tutorials/getting_started_(jpm)/index.html b/files/tr/mozilla/add-ons/sdk/tutorials/getting_started_(jpm)/index.html
deleted file mode 100644
index 20e08ba28f..0000000000
--- a/files/tr/mozilla/add-ons/sdk/tutorials/getting_started_(jpm)/index.html
+++ /dev/null
@@ -1,174 +0,0 @@
----
-title: Başlarken(jpm)
-slug: Mozilla/Add-ons/SDK/Tutorials/Getting_Started_(jpm)
-translation_of: Archive/Add-ons/Add-on_SDK/Tutorials/Getting_Started_(jpm)
----
-<p>{{AddonSidebar}}</p>
-
-<div class="note">
-<p>The Add-on SDK includes a command-line tool that you use to initialize, run, test, and package add-ons. The current tool is called jpm, and is based on <a href="http://nodejs.org/">Node.js</a>. It replaces the old cfx tool.</p>
-
-<p>You can use jpm from Firefox 38 onwards.</p>
-
-<p>This article describes how to develop using jpm.</p>
-</div>
-
-<p>This tutorial walks through creating a simple add-on using the SDK.</p>
-
-<h2 id="Ön_koşullar">Ön koşullar</h2>
-
-<p>SDK kullanarak Firefox eklentisi oluşturmak için şu şartların sağlanması gerekir:</p>
-
-<ul>
- <li>Firefox'un 38 ve üs versiyonu. Eğer Firefox'un önceki bir versiyonu ile çalışmanız gerekirse, cfx aracını kullanmanız gerekecektir. <a href="/en-US/Add-ons/SDK/Tutorials/Getting_started_(cfx)">getting started with cfx</a>.</li>
- <li>the command-line jpm tool. See the instructions for <a href="/en-US/Add-ons/SDK/Tools/jpm#Installation">installing jpm</a>. Once you've done that, you'll be looking at a command prompt.</li>
-</ul>
-
-<h2 id="Boş_bir_eklenti_başlatma">Boş bir eklenti başlatma</h2>
-
-<p>Komut satırında, yeni bir dizin oluşturun. Dizine gidin<code>, jpm init </code>komutunu verin ve enter'a basın:</p>
-
-<div class="note">
-<p><code>mkdir </code>komutu yeni bir dizin oluşturur. <code>cd </code>komutu ise belirtilen dizine gider.</p>
-</div>
-
-<pre>mkdir eklentim
-cd eklentim
-jpm init
-</pre>
-
-<p> </p>
-
-<p>Sizden eklentiniz hakkındaki bilgileri sağlamanız istenecektir: bu bilgiler eklentinizin <a href="/en-US/Add-ons/SDK/Tools/package_json">package.json</a>  dosyasını oluşturmak için kullanılır. Enter'a basın ve varsayılan değerleri kabul edin (Daha sonra package.json dosyasından bu verileri değiştirebilirsiniz). <code>jpm init</code> hakkında daha fazla bilgi için <a href="/en-US/Add-ons/SDK/Tools/jpm#Command_reference">jpm komut referansı</a> adresine bakınız</p>
-
-<p>İstenilen değerleri girdikten veya varsayılan değerleri atadıktan hemen sonra, "package.json" dosyasındaki tüm içerik görüntülenir ve size eklentiniz hakkındaki bu bilgileri kabul edip etmediğiniz sorulur. Devam edebilmek için istenilen komut ile kabul edin.</p>
-
-<h2 id="Eklentiyi_hazır_hale_getirme">Eklentiyi hazır hale getirme</h2>
-
-<p>Şimdi eklentinizin kodunu yazabilirsiniz. Unless you've changed the value of "entry point" ("<a href="/en-US/Add-ons/SDK/Tools/package_json#main">main</a>" in package.json), this goes in "index.js" file in the root of your add-on. This file was created for you in the previous step. Open it and add the following code:</p>
-
-<pre class="brush: js">var buttons = require('sdk/ui/button/action');
-var tabs = require("sdk/tabs");
-
-var button = buttons.ActionButton({
-  id: "mozilla-link",
-  label: "Visit Mozilla",
-  icon: {
-    "16": "./icon-16.png",
-    "32": "./icon-32.png",
-    "64": "./icon-64.png"
-  },
-  onClick: handleClick
-});
-
-function handleClick(state) {
-  tabs.open("http://www.mozilla.org/");
-}
-</pre>
-
-<div class="note">
-<p>Note that "entry point" defaults to "index.js" in jpm, meaning that your main file is "index.js", and it is found directly in your add-on's root.</p>
-
-<p>In cfx, the entry point defaults to "main.js", and is located in the "lib" directory under the add-on's root.</p>
-</div>
-
-<p>Kaydedin.</p>
-
-<p>Sonra, eklenti dizinine "<strong>data</strong>" isimli bir klasör oluşturun,</p>
-
-<pre>mkdir data
-</pre>
-
-<p>ve şu üç ikonu "data" klasörüne kaydedin:</p>
-
-<table class="standard-table">
- <tbody>
-  <tr>
-   <td><img alt="" src="https://mdn.mozillademos.org/files/7635/icon-16.png" style="height: 16px; width: 16px;"></td>
-   <td>icon-16.png</td>
-  </tr>
-  <tr>
-   <td><img alt="" src="https://mdn.mozillademos.org/files/7637/icon-32.png" style="height: 32px; width: 32px;"></td>
-   <td>icon-32.png</td>
-  </tr>
-  <tr>
-   <td><img alt="" src="https://mdn.mozillademos.org/files/7639/icon-64.png" style="height: 64px; width: 64px;"></td>
-   <td>icon-64.png</td>
-  </tr>
- </tbody>
-</table>
-
-<p>Komut satırıne geri dönün ve şu komutu verin:</p>
-
-<pre>jpm run</pre>
-
-<p>Bu jpm komutu, yaptığınız bu temel eklentinin hazır bir örneğini Firefox tarayıcınızda açacaktır.</p>
-
-<p>If Firefox can not be located, you may need to provide the path to it (example in Ubuntu):</p>
-
-
-<pre>jpm run -b /usr/bin/firefox</pre>
-
-<p>Firefox açıldığında, tarayıcının sağ üst köşesinde Firefox logosu görülecektir. Logoya tıkladığınızda, tarayıcıda <a href="http://www.mozilla.org/" rel="noreferrer">http://www.mozilla.org/</a> adresine giden yeni bir sekme açılır ve eklenti hazırdır.</p>
-
-<p>It uses two SDK modules: the <a href="/en-US/Add-ons/SDK/Low-Level_APIs/ui_button_action">action button</a> module, which enables you to add buttons to the browser, and the <a href="/en-US/Add-ons/SDK/High-Level_APIs/tabs" rel="noreferrer">tabs</a> module, which enables you to perform basic operations with tabs. In this case, we've created a button whose icon is the Firefox icon, and added a click handler that loads the Mozilla home page in a new tab.</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/7643/mozilla-button.png" style="display: block; height: 221px; margin-left: auto; margin-right: auto; width: 382px;">Try editing this file. For example, we could change the page that gets loaded:</p>
-
-<pre class="brush: js">var buttons = require('sdk/ui/button/action');
-var tabs = require("sdk/tabs");
-
-var button = buttons.ActionButton({
-  id: "mozilla-link",
-  label: "Visit Mozilla",
-  icon: {
-    "16": "./icon-16.png",
-    "32": "./icon-32.png",
-    "64": "./icon-64.png"
-  },
-  onClick: handleClick
-});
-
-function handleClick(state) {
-  tabs.open("https://developer.mozilla.org/");
-}</pre>
-
-<p>At the command prompt, execute <code>jpm run</code> again. This time clicking it takes you to <a href="https://developer.mozilla.org/">https://developer.mozilla.org/</a>.</p>
-
-<h2 id="Packaging_the_add-on">Packaging the add-on</h2>
-
-<p>When you've finished the add-on and are ready to distribute it, you'll need to package it as an XPI file. This is the installable file format for Firefox add-ons. You can distribute XPI files yourself or publish them to <a href="https://addons.mozilla.org" rel="noreferrer">https://addons.mozilla.org</a> so other users can download and install them.</p>
-
-<p>To build an XPI, just execute the command <code>jpm xpi</code> from the add-on's directory:</p>
-
-<pre>jpm xpi
-</pre>
-
-<p>You should see a message like:</p>
-
-<pre>JPM info Successfully created xpi at /path/to/my-addon/@my-addon-0.0.1.xpi
-</pre>
-
-<p>To test that this worked, try installing the XPI file in your own Firefox installation. You can do this by pressing the Ctrl+O key combination (Cmd+O on Mac) from within Firefox, or selecting the "Open" item from Firefox's "File" menu. This will bring up a file selection dialog: navigate to the "@my-addon.xpi" file, open it and follow the prompts to install the add-on.</p>
-
-<p>Note that Firefox by default requires add-ons, even locally developed ones, to be signed. After installation they'll show up disabled in the list of installed add-ons, noting the missing signature. During development, or if you don't plan to distribute, you can open <a>about:config</a> and set <em>xpinstall.signatures.required</em> to <em>false</em> to run it unsigned. This setting applies to any add-on, so take extra care to not accidently install a malicious one from elsewhere.</p>
-
-<p>To distribute your add-on, <a href="https://addons.mozilla.org/en-US/developers/addon/submit/2">submit the XPI file to addons.mozilla.org</a> or run <a href="https://developer.mozilla.org/en-US/Add-ons/SDK/Tools/jpm#jpm_sign">jpm sign</a> if you wish to distribute the add-on on your own server.</p>
-
-<h2 id="Özet">Özet</h2>
-
-<p>In this tutorial we've built and packaged an add-on using three commands:</p>
-
-<ul>
- <li><code>jpm init</code> to initialize an empty add-on template</li>
- <li><code>jpm run</code> to run a new instance of Firefox with the add-on installed, so we can try it out</li>
- <li><code>jpm xpi</code> to package the add-on into an XPI file for distribution</li>
-</ul>
-
-<p>These are the three main commands you'll use when developing SDK add-ons. There's comprehensive <a href="/en-US/Add-ons/SDK/Tools/jpm" rel="noreferrer">reference documentation</a> covering all the commands you can use and all the options they take.</p>
-
-<p>The add-on code itself uses two SDK modules, <a href="/en-US/Add-ons/SDK/Low-Level_APIs/ui_button_action">action button</a> and <a href="/en-US/Add-ons/SDK/High-Level_APIs/tabs" rel="noreferrer">tabs</a>. There's reference documentation for all the <a href="/en-US/Add-ons/SDK/High-Level_APIs" rel="noreferrer">high-level</a> and <a href="/en-US/Add-ons/SDK/Low-Level_APIs" rel="noreferrer">low-level</a> APIs in the SDK.</p>
-
-<h2 id="What's_next">What's next?</h2>
-
-<p>To get a feel for some of the things you can do with the SDK APIs, try working through some of the <a href="/en-US/Add-ons/SDK/Tutorials" rel="noreferrer">tutorials</a>.</p>
diff --git a/files/tr/mozilla/add-ons/sdk/tutorials/index.html b/files/tr/mozilla/add-ons/sdk/tutorials/index.html
deleted file mode 100644
index 56ae76c9d4..0000000000
--- a/files/tr/mozilla/add-ons/sdk/tutorials/index.html
+++ /dev/null
@@ -1,158 +0,0 @@
----
-title: Tutorials
-slug: Mozilla/Add-ons/SDK/Tutorials
-translation_of: Archive/Add-ons/Add-on_SDK/Tutorials
----
-<div class="warning">
-<p>Support for extensions using XUL/XPCOM or the Add-on SDK was removed in Firefox 57, released November 2017. As there is no supported version of Firefox enabling these technologies, this page will be removed by December 2020.</p>
-
-<p>Add-ons using the techniques described in this document are considered a legacy technology in Firefox. Don't use these techniques to develop new add-ons. Use <a href="/en-US/Add-ons/WebExtensions">WebExtensions</a> instead. If you maintain an add-on which uses the techniques described here, consider migrating it to use WebExtensions.</p>
-
-<p><strong>Starting from <a href="https://wiki.mozilla.org/RapidRelease/Calendar">Firefox 53</a>, no new legacy add-ons will be accepted on addons.mozilla.org (AMO) for desktop Firefox and Firefox for Android.</strong></p>
-
-<p><strong>Starting from <a href="https://wiki.mozilla.org/RapidRelease/Calendar">Firefox 57</a>, only extensions developed using WebExtensions APIs will be supported on Desktop Firefox and Firefox for Android. </strong></p>
-
-<p>Even before Firefox 57, changes coming up in the Firefox platform will break many legacy extensions. These changes include multiprocess Firefox (e10s), sandboxing, and multiple content processes. Legacy extensions that are affected by these changes should migrate to use WebExtensions APIs if they can. See the <a href="https://blog.mozilla.org/addons/2017/02/16/the-road-to-firefox-57-compatibility-milestones/">"Compatibility Milestones" document</a> for more information.</p>
-
-<p>A wiki page containing <a href="https://wiki.mozilla.org/Add-ons/developer/communication">resources, migration paths, office hours, and more</a>, is available to help developers transition to the new technologies.</p>
-</div>
-
-<p>This page lists practical hands-on articles about how to accomplish specific tasks using the SDK.</p>
-
-<hr>
-<h3 id="Başlarken">Başlarken</h3>
-
-<div class="column-container">
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Tools/jpm#Installation">Yükleme </a></dt>
- <dd>Eklentileri geliştirmek için kullanacağınız jpm aracı nasıl yüklenir.</dd>
-</dl>
-
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Troubleshooting">Sorun giderme</a></dt>
- <dd>
- <div id="gt-src-tools">
- <div dir="ltr" style="zoom: 1;"><span id="result_box" lang="tr"><span class="hps">Ortak sorunları</span> <span class="hps">tespit etmek</span> <span class="hps">ve</span> <span class="hps">daha fazla</span> <span class="hps">yardım almak</span> <span class="hps">için bazı</span> <span class="hps">göstericiler</span><span>.</span></span></div>
- </div>
- </dd>
-</dl>
-</div>
-
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Getting_Started_(jpm)">Başlarken</a></dt>
- <dd>jpm kullanarak, SDK ile basit bir eklenti yaratmanın gidiş yolu.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h3 id="Kullanıcı_Arayüzü_Yaratma">Kullanıcı Arayüzü Yaratma</h3>
-
-<div class="column-container">
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Adding_a_Button_to_the_Toolbar">Araç çubuğu butonu ekleme</a></dt>
- <dd>Attach a button to the Firefox Add-on toolbar.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Add_a_Menu_Item_to_Firefox">Firefox'a bir menü nesnesi ekleme</a></dt>
- <dd>Add items to Firefox's main menus.</dd>
-</dl>
-</div>
-
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Display_a_Popup">Bir açılır pencere gösterme</a></dt>
- <dd>Display a popup dialog implemented with HTML and JavaScript.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Add_a_Context_Menu_Item">Bir içerik menüsü nesnesi ekleme</a></dt>
- <dd>Add items to Firefox's context menu.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h3 id="Interact_with_the_browser"><a name="interact-with-the-browser">Interact with the browser</a></h3>
-
-<div class="column-container">
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Open_a_Web_Page">Open a web page </a></dt>
- <dd>Open a web page in a new browser tab or window using the tabs module, and access its content.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Listen_for_Page_Load">Listen for page load </a></dt>
- <dd>Use the tabs module to get notified when new web pages are loaded, and access their content.</dd>
-</dl>
-</div>
-
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/List_Open_Tabs">Get the list of open tabs </a></dt>
- <dd>Use the tabs module to iterate through the currently open tabs, and access their content.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h3 id="Modify_web_pages"><a name="modify-web-pages">Modify web pages</a></h3>
-
-<div class="column-container">
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Modifying_Web_Pages_Based_on_URL">Modify web pages based on URL </a></dt>
- <dd>Create filters for web pages based on their URL: whenever a web page whose URL matches the filter is loaded, execute a specified script in it.</dd>
-</dl>
-</div>
-
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Modifying_the_Page_Hosted_by_a_Tab">Modify the active web page </a></dt>
- <dd>Dynamically load a script into the currently active web page.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h3 id="Development_techniques"><a name="development-techniques">Development techniques</a></h3>
-
-<div class="column-container">
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Logging">Logging </a></dt>
- <dd>Log messages to the console for diagnostic purposes.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Creating_reusable_modules">Creating reusable modules </a></dt>
- <dd>Structure your add-on in separate modules to make it easier to develop, debug, and maintain. Create reusable packages containing your modules, so other add-on developers can use them too.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Unit_testing">Unit testing </a></dt>
- <dd>Writing and running unit tests using the SDK's test framework.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Chrome_authority">Chrome authority </a></dt>
- <dd>Get access to the Components object, enabling your add-on to load and use any XPCOM object.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Creating_event_targets">Creating event targets </a></dt>
- <dd>Enable the objects you define to emit their own events.</dd>
-</dl>
-</div>
-
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Listening_for_load_and_unload">Listen for load and unload </a></dt>
- <dd>Get notifications when your add-on is loaded or unloaded by Firefox, and pass arguments into your add-on from the command line.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Using_third-party_modules_(jpm)">Using third-party modules (jpm)</a></dt>
- <dd>Install and use additional modules which don't ship with the SDK itself.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/l10n">Localization </a></dt>
- <dd>Writing localizable code.</dd>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Mobile_development">Mobile development </a></dt>
- <dd>Develop add-ons for Firefox Mobile on Android.</dd>
- <dt><a href="/en-US/Add-ons/Add-on_Debugger">Add-on Debugger</a></dt>
- <dd>Debug your add-on's JavaScript.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h3 id="Putting_it_together"><a name="putting-it-together">Putting it together</a></h3>
-
-<div class="column-container">
-<div class="column-half">
-<dl>
- <dt><a href="/en-US/Add-ons/SDK/Tutorials/Annotator">Annotator add-on </a></dt>
- <dd>A walkthrough of a relatively complex add-on.</dd>
-</dl>
-</div>
-</div>
diff --git a/files/tr/mozilla/participating_in_the_mozilla_project/index.html b/files/tr/mozilla/participating_in_the_mozilla_project/index.html
deleted file mode 100644
index 7d32612744..0000000000
--- a/files/tr/mozilla/participating_in_the_mozilla_project/index.html
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Participating in the Mozilla project
-slug: Mozilla/Participating_in_the_Mozilla_project
-translation_of: Mozilla/Participating_in_the_Mozilla_project
----
-<p>Hataları düzeltmeye ve Mozilla platformunun arkasındaki kod üzerinde çalışmaya yardımcı olmakla ilgileniyorsanız, sizi doğru yönde yönlendirecek belgeleri bulmak için en uygun yer burasıdır.</p>
-
-<table>
- <tbody>
-  <tr>
-   <td style="vertical-align: top;">
-    <h2 id="Genel_başlıklar">Genel başlıklar</h2>
-
-    <dl>
-     <dt><a href="/en-US/docs/Mozilla/Developer_guide">Mozilla geliştirici kılavuzu</a></dt>
-     <dd>Mozilla kod tabanına katkıda bulunmak için geliştirme ipuçları ve kılavuzlar.</dd>
-     <dt><a href="/en-US/docs/Mozilla/Developer_guide/Source_Code">Mozilla kaynak kodu</a></dt>
-     <dd>Mozilla kodunu indirerek veya sürüm kontrolü yoluyla nasıl edineceğiniz ve kodunuzu ağaca nasıl alacağınız hakkında bilgiler.</dd>
-     <dt><a href="/en-US/docs/Mozilla/Developer_guide/Build_Instructions">Belge Oluşturma</a></dt>
-     <dd>Firefox ve Thunderbird dahil olmak üzere Mozilla projelerinin nasıl oluşturulacağı hakkında bilgiler. <em>Bu sayfanın temizlenmesi gerekiyor.</em></dd>
-     <dt><a class="internal" href="/en-US/docs/Mozilla/The_Mozilla_platform" title="En/The Mozilla platform">The Mozilla platform</a></dt>
-     <dd>Tüm API'leri ve teknolojileri dahil olmak üzere Mozilla platformu hakkında ve bunları kendi projelerinizde nasıl kullanacağınız hakkında bilgiler.</dd>
-     <dt><a class="internal" href="/en-US/docs/MDN/Getting_started">Documenting Mozilla</a></dt>
-     <dd>Mozilla ve açık Web için belgelerimizi oluşturmamıza ve geliştirmemize yardımcı olun.</dd>
-     <dt><a class="internal" href="/en-US/docs/Mozilla/Debugging">Debugging</a></dt>
-     <dd>Mozilla kodunda hata ayıklarken izlenecek faydalı ipuçları ve yönergeler.</dd>
-     <dt><a class="internal" href="/en-US/docs/Mozilla/QA">Quality assurance</a></dt>
-     <dd>Test ve hata izleme hakkında bilgiler.</dd>
-     <dt><a class="internal" href="/en-US/docs/Glossary/Localization" title="En/Localization">Localization</a></dt>
-     <dd>Mozilla projelerini, belgelerini ve diğer içeriği birden çok dile çevirmeye ilişkin belgeler.</dd>
-     <dt><a class="internal" href="/en-US/docs/Glossary" title="En/Glossary">Glossary</a></dt>
-     <dd>Mozilla hackerları tarafından kullanılan terimler ve tanımlar.</dd>
-    </dl>
-
-    <h2 id="Proje_sayfaları">Proje sayfaları</h2>
-
-    <dl>
-     <dt><a class="internal" href="/en-US/docs/Mozilla/Thunderbird">Thunderbird</a></dt>
-     <dd>Mozilla'nın e-posta istemcisi</dd>
-     <dt><a class="internal" href="/en-US/docs/Mozilla/Calendar">Calendar</a></dt>
-     <dd>Mozilla takvim projesi.</dd>
-    </dl>
-   </td>
-   <td style="vertical-align: top;">
-    <h2 id="Araçlar">Araçlar</h2>
-
-    <dl>
-     <dt><a class="external" href="https://bugzilla.mozilla.org/">Bugzilla</a></dt>
-     <dd>Bugzilla veritabanı, Mozilla projeleriyle ilgili sorunları izlemek için kullanılır.</dd>
-     <dt><a class="external" href="https://dxr.mozilla.org/">DXR</a></dt>
-     <dd>Web'deki Mozilla kaynak kodu deposuna göz atın ve arayın.</dd>
-     <dt><a class="external" href="http://bonsai.mozilla.org/cvsqueryform.cgi">Bonsai</a></dt>
-     <dd>Bonsai aracı, depodaki hangi dosyayı kimin değiştirdiğini ve ne zaman yaptığını bulmanızı sağlar. (Bu, Firefox 3.0 ve daha eski sürümler içindir.)</dd>
-     <dt><a class="external" href="http://tinderbox.mozilla.org/showbuilds.cgi" title="http://tinderbox.mozilla.org/showbuilds.cgi">Tinderbox</a></dt>
-     <dd><a class="internal" href="/en/Tinderbox" title="En/Tinderbox">Tinderbox</a> ağacın durumunu gösterir (şu anda başarıyla oluşturulmuş olsun ya da olmasın). Çalışan bir ağaçla çalıştığınızdan emin olmak için giriş ve çıkış yapmadan önce bunu kontrol edin.</dd>
-     <dt><a class="internal" href="/en-US/docs/Mozilla/Projects/Crash_reporting" title="en/Crash reporting">Crash tracking</a></dt>
-     <dd>Socorro kaza raporlama sistemi hakkında bilgiler.</dd>
-     <dt><a class="external" href="http://www.mozilla.org/community/developer-forums.html">Developer forums</a></dt>
-     <dd>Mozilla geliştirme sorunları hakkında konuşabileceğiniz konuya özgü tartışma forumları listesi.</dd>
-    </dl>
-   </td>
-  </tr>
- </tbody>
-</table>
diff --git a/files/tr/mozilla/persona/index.html b/files/tr/mozilla/persona/index.html
deleted file mode 100644
index 2e1b435922..0000000000
--- a/files/tr/mozilla/persona/index.html
+++ /dev/null
@@ -1,159 +0,0 @@
----
-title: Persona
-slug: Mozilla/Persona
-translation_of: Archive/Mozilla/Persona
----
-<div class="boxed translate-display">
-<div class="summary"><font><font>Basit, gizlilik-duyarlı tek oturum açma: Kullanıcıların e-posta adresi ile web sitenize oturum izin ve şifre yönetimi kendinizi özgür.</font></font></div>
-
-<div class="column-container">
-<div class="callout-box">
-<p><strong><font><font>Koparmayın veya yardım almak!</font></font></strong></p>
-
-<p><font><font>Takip </font></font><a class="external" href="http://identity.mozilla.com/"><font><font>eden blog</font></font></a><font><font> katılmak, </font></font><a class="link-https" href="https://lists.mozilla.org/listinfo/dev-identity"><font><font>posta listesi</font></font></a><font><font> , bizi bulmak </font></font><a class="link-irc" href="irc://irc.mozilla.org/identity"><font><font>#identity</font></font></a><font><font> üzerindeki </font></font><a class="link-https" href="https://wiki.mozilla.org/IRC"><font><font>IRC</font></font></a><font><font> veya </font></font><a class="link-https" href="https://github.com/mozilla/browserid/issues/new"><font><font>bir hatayı bildirmek</font></font></a><font><font> .</font></font></p>
-</div>
-
-<p><a href="https://login.persona.org/"><font><font>Mozilla Persona</font></font></a><font><font> kullanımı kolay ve dağıtmak için kolay Web için bir çapraz tarayıcı giriş sistemidir. </font><font>Bu çalışır </font></font><a href="https://developer.mozilla.org/en-US/docs/persona/Browser_compatibility"><font><font>, tüm büyük tarayıcılar</font></font></a><font><font> ve yapabilirsiniz </font></font><a href="https://developer.mozilla.org/en-US/docs/Persona/Quick_Setup"><font><font>bugün başlamak</font></font></a><font><font> .</font></font></p>
-
-<p><font><font>Neden web sitenizde Persona kullanmalıyım?</font></font></p>
-
-<ol>
- <li><strong><font><font>Persona tamamen siteye özgü şifreleri ortadan kaldırır</font></font></strong><font><font> , yaratma yönetmek ve güvenli şifreler depolama yükünden kullanıcıları ve web sitelerini serbest.</font></font></li>
- <li><strong><font><font>Persona. Kullanımı kolay</font></font></strong><font><font> bir Persona kullanıcı gibi yeni bir siteye oturum açabilirsiniz sadece iki tıklama ile </font></font><a href="http://voo.st"><font><font>Voost</font></font></a><font><font> hesap oluşturma ile ilişkili sürtünme atlayarak.</font></font></li>
- <li><strong><font><font>Persona uygulanması kolaydır </font></font></strong><strong><font><font>.</font></font></strong><font><font> Geliştiriciler, tek bir öğleden sonra bir siteye Persona ekleyebilirsiniz.</font></font></li>
- <li><strong><font><font>Hiçbir kilit-var</font></font></strong><font><font> . </font><font>Geliştiriciler kendi tüm kullanıcılar için doğrulanmış e-posta adresi almak ve kullanıcılar Persona ile herhangi bir e-posta adresini kullanabilirsiniz.</font></font></li>
-</ol>
-
-<p><font><font>Ayrıca, Persona sadece daha iyi gidiyor: bir inşa var </font></font><strong><font><font>, açık, ademi merkeziyetçi protokol</font></font></strong><font><font> sağlamak için tasarlanmıştır </font></font><strong><font><font>tarayıcılar içine doğrudan entegrasyon</font></font></strong><font><font> ve </font></font><strong><font><font>e-posta sağlayıcıları tarafından doğal destek </font></font></strong><strong><font><font>.</font></font></strong><font><font> otomatik olarak bu gelişmeler yaşayacaksınız bugün Persona uygulamak Siteleri, herhangi bir kodu değiştirmek zorunda kalmadan .</font></font></p>
-</div>
-
-<hr>
-<div class="column-container">
-<h2 id="Sitenizde_Persona_kullanma"><font><font>Sitenizde Persona kullanma</font></font></h2>
-
-
-<div class="column-third">
-<h3 id="Başlarken"><font><font>Başlarken</font></font></h3>
-
-<dl>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/Why_Persona"><font><font>Neden Persona?</font></font></a></dt>
- <dd><font><font>Diğer kimlik ve kimlik doğrulama sistemlerine kıyasla Persona hakkında özel nedir.</font></font></dd>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/Quick_Setup"><font><font>Hızlı kurulum</font></font></a></dt>
- <dd><font><font>Web Persona eklemek nasıl gösteren bir örneklerde.</font></font></dd>
-</dl>
-
-<h3 id="API_başvuru"><font><font>API başvuru</font></font></h3>
-
-<dl>
- <dt><a href="https://developer.mozilla.org/en-US/Persona/The_navigator.id_API"><font><font>navigator.id API</font></font></a></dt>
- <dd><font><font>Tarayıcı API.</font></font></dd>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/Remote_Verification_API"><font><font>Doğrulama API başvuru</font></font></a></dt>
- <dd><font><font>Uzaktan doğrulama API.</font></font></dd>
-</dl>
-</div>
-
-<div class="column-third">
-<h3 id="Kılavuzlar"><font><font>Kılavuzlar</font></font></h3>
-
-<dl>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/Security_Considerations"><font><font>Güvenlik noktaları</font></font></a></dt>
- <dd><font><font>Uygulamaları ve teknikler Persona dağıtım güvenli olduğundan emin olmak için.</font></font></dd>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/Browser_compatibility"><font><font>Tarayıcı uyumluluğu</font></font></a></dt>
- <dd><font><font>Bilgi tam olarak hangi tarayıcıları Persona destek.</font></font></dd>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/Internationalization"><font><font>Uluslararasılaşma</font></font></a></dt>
- <dd><font><font>Persona farklı dilleri nasıl işleyeceğini öğrenin.</font></font></dd>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/The_implementor_s_guide"><font><font>implementor kılavuzu</font></font></a></dt>
- <dd><font><font>Persona için destek ekledik sitelerden ipuçları.</font></font></dd>
-</dl>
-</div>
-
-<div class="column-third">
-<h3 id="Kaynaklar"><font><font>Kaynaklar</font></font></h3>
-
-<dl>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/Libraries_and_plugins"><font><font>Kütüphaneler ve eklentileri</font></font></a></dt>
- <dd><font><font>Sevdiğiniz programlama dili, web çerçeve, blog, ya da içerik yönetim sistemi için bir damla-kütüphane bulun.</font></font></dd>
- <dt><a class="link-https" href="https://github.com/mozilla/browserid-cookbook"><font><font>Persona yemek kitabı</font></font></a></dt>
- <dd><font><font>Persona siteleri için örnek kaynak kodu. </font><font>C # parçacıkları (MVC3), PHP, node.js, ve daha fazlasını içerir.</font></font></dd>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/branding"><font><font>Markalaşma kaynakları</font></font></a></dt>
- <dd><font><font>Düğmeleri ve diğer grafik giriş yap kullanıcılara mevcut Persona yardımcı olur.</font></font></dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<div class="column-container">
-<h2 id="Kimlik_Sağlayıcı_Olmak"><font><font>Kimlik Sağlayıcı Olmak</font></font></h2>
-
-<p><font><font>Eğer bir e-posta sağlayıcısı veya başka bir kimlik-sağlayan hizmet iseniz, bir Persona Kimlik Sağlayıcı olma hakkında bilgi edinmek için aşağıdaki bağlantıları kontrol edin.</font></font></p>
-
-<dl>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/Identity_Provider_Overview"><font><font>IdP Genel Bakış</font></font></a></dt>
- <dd><font><font>Persona Kimlik Sağlayıcıları bir üst düzey görünümü.</font></font></dd>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/Implementing_a_Persona_IdP"><font><font>IDP Uygulamak</font></font></a></dt>
- <dd><font><font>Yerinden Olmuş Kişiler olma teknik detaylar ayrıntılı bir rehber.</font></font></dd>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/.well-known-browserid"><font><font>.well bilinen / browserid</font></font></a></dt>
- <dd><font><font>Yapısı ve amacı genel bir bakış </font></font><code><font><font>.well bilinen / browserid</font></font></code><font><font> yerinden edilmiş kişilerin protokol için onların desteğini tanıtımı için kullanmak dosyaya.</font></font></dd>
-</dl>
-</div>
-
-<hr>
-<div class="column-container">
-<h2 id="Persona_Projesi"><font><font>Persona Projesi</font></font></h2>
-
-<dl>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/Glossary"><font><font>Sözlük</font></font></a></dt>
- <dd><font><font>BrowserID ve Persona terminoloji tanımlanır.</font></font></dd>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/FAQ"><font><font>SSS</font></font></a></dt>
- <dd><font><font>Sık sorulan soruların yanıtları.</font></font></dd>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/Protocol_Overview"><font><font>Protokol genel bakış</font></font></a></dt>
- <dd><font><font>Altta yatan BrowserID protokolünün bir orta düzey teknik bakış.</font></font></dd>
- <dt><a href="https://developer.mozilla.org/en-US/docs/persona/Crypto"><font><font>Kripto</font></font></a></dt>
- <dd><font><font>Persona ve BrowserID arkasında şifreleme kavramlar bir bakış.</font></font></dd>
- <dt><a class="link-https" href="https://github.com/mozilla/id-specs/blob/prod/browserid/index.md"><font><font>Spec</font></font></a></dt>
- <dd><font><font>Derin teknik detaylar burada yaşıyor.</font></font></dd>
- <dt><a href="https://developer.mozilla.org/en-US/docs/Persona/Bootstrapping_Persona"><font><font>Persona web sitesi</font></font></a></dt>
- <dd><font><font>Persona gidiyor almak için, biz de üç barındırma hizmetleri konum </font></font><a class="link-https" href="https://login.persona.org" rel="freelink"><font><font>https://login.persona.org</font></font></a><font><font> : bir geri dönüş Kimlik Sağlayıcı, {{domxref ("navigator.id")}} API'leri taşınabilir uygulanmasını ve bir kimlik belirtilme doğrulama hizmeti.</font></font></dd>
- <dt><a href="https://github.com/mozilla/browserid"><font><font>Persona kaynak kodu</font></font></a></dt>
- <dd><font><font>Persona web sitesi arkasında kod GitHub üzerinde bir depo yaşıyor. </font><font>Istekleri hoş geldiniz çekin!</font></font></dd>
-</dl>
-</div>
-
-<h2 id="Subnav"><font><font>Subnav</font></font></h2>
-
-<ol>
- <li><a href="https://developer.mozilla.org/tr/docs/Persona$edit#"><font><font>Bir web sitesinde Persona kullanma</font></font></a>
-
-  <ol>
-   <li><a href="https://developer.mozilla.org/en-US/docs/Persona/Why_Persona" title="Neden Persona?"><font><font>Neden Persona kullanmanız gerekir?</font></font></a></li>
-   <li><a href="https://developer.mozilla.org/en-US/docs/Persona/Quick_setup" title="Hızlı Başlangıç"><font><font>Başlamak</font></font></a></li>
-   <li><a href="https://developer.mozilla.org/en-US/docs/Persona/The_implementor_s_guide" title="Implementor Kılavuzu"><font><font>Persona uygulanması için ipuçları</font></font></a></li>
-   <li><a href="https://developer.mozilla.org/en-US/docs/Persona/Security_Considerations" title="Güvenlik Kaygıları"><font><font>Güvenlik noktaları</font></font></a></li>
-   <li><a href="https://developer.mozilla.org/en-US/docs/Persona/Browser_compatibility" title="Tarayıcı uyumluluğu"><font><font>Tarayıcı uyumluluğu</font></font></a></li>
-   <li><a href="https://developer.mozilla.org/en-US/docs/Persona/Internationalization" title="Uluslararasılaşma"><font><font>Uluslararasılaşma</font></font></a></li>
-   <li><a href="https://developer.mozilla.org/en-US/Persona/The_navigator.id_API" title="navigator.id API"><font><font>navigator.id API</font></font></a></li>
-   <li><a href="https://developer.mozilla.org/en-US/docs/Persona/Remote_Verification_API" title="Uzaktan Doğrulama API"><font><font>Uzaktan doğrulama API</font></font></a></li>
-   <li><a href="https://developer.mozilla.org/en-US/docs/Persona/Libraries_and_plugins" title="Kütüphaneler ve eklentileri"><font><font>Kütüphaneler ve eklentileri</font></font></a></li>
-   <li><a href="https://developer.mozilla.org/en-US/docs/Persona/branding" title="Markalaşma kaynakları"><font><font>Markalaşma kaynakları</font></font></a></li>
-  </ol>
- </li>
- <li><a href="https://developer.mozilla.org/tr/docs/Persona$edit#"><font><font>Kimlik Sağlayıcı Olmak</font></font></a>
-  <ol>
-   <li><a href="https://developer.mozilla.org/en-US/docs/Persona/Identity_Provider_Overview" title="IdP Genel Bakış"><font><font>IdP Genel Bakış</font></font></a></li>
-   <li><a href="https://developer.mozilla.org/en-US/docs/Persona/Implementing_a_Persona_IdP" title="IDP Uygulamak"><font><font>IDP Uygulamak</font></font></a></li>
-   <li><a href="https://developer.mozilla.org/en-us/docs/Persona/.well-known-browserid" title=".well bilinen en browserid biçimi"><font><font>.well bilinen en browserid biçimi</font></font></a></li>
-  </ol>
- </li>
- <li><a href="https://developer.mozilla.org/tr/docs/Persona$edit#"><font><font>Persona projesi</font></font></a>
-  <ol>
-   <li><a href="https://developer.mozilla.org/en-US/docs/Persona/Glossary" title="Sözlük"><font><font>Sözlük</font></font></a></li>
-   <li><a href="https://developer.mozilla.org/en-us/docs/Persona/FAQ" title="SSS"><font><font>SSS</font></font></a></li>
-   <li><a href="https://developer.mozilla.org/en-us/docs/Persona/Bootstrapping_Persona" title="Persona barındırılan hizmetler"><font><font>Persona barındırılan hizmetler</font></font></a></li>
-   <li><a href="https://developer.mozilla.org/en-US/docs/Persona/Protocol_Overview" title="Protokol genel bakış"><font><font>Protokol genel bakış</font></font></a></li>
-   <li><a href="https://developer.mozilla.org/en-US/docs/persona/Crypto" title="Kripto"><font><font>Kriptografi</font></font></a></li>
-  </ol>
- </li>
-</ol>
-</div>
-
-<p> </p>
diff --git a/files/tr/mozilla/projects/index.html b/files/tr/mozilla/projects/index.html
deleted file mode 100644
index d7e62c6882..0000000000
--- a/files/tr/mozilla/projects/index.html
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Projects
-slug: Mozilla/Projects
-tags:
-  - Landing
-  - Mozilla
-  - NeedsContent
-  - NeedsTranslation
-  - Projects
-  - TopicStub
-translation_of: Mozilla/Projects
----
-<p>Here you'll find links to documentation about various Mozilla projects; these are often parts of Firefox or other products, but may also be used in other projects as well.</p>
-
-<p>{{ LandingPageListSubpages() }}</p>
diff --git a/files/tr/mozilla/projects/necko/index.html b/files/tr/mozilla/projects/necko/index.html
deleted file mode 100644
index 950d678543..0000000000
--- a/files/tr/mozilla/projects/necko/index.html
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Necko
-slug: Mozilla/Projects/Necko
-translation_of: Mozilla/Projects/Necko
----
-<p><strong>Necko bir internet kütüphanesidir ve bu kütüphane platform-alıcısı API'sını bağlantı , protocol ayarlamak için kullanılır.</strong></p>
-
-<p>Şu anda bu sistem sadece Mozilla Distribution'un yapı parçasıdır. Bunun denemesini <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Firefox_build">Yapı Dosyaları</a>ndan bulunabilir. Bunu heryere taşıyarak Mozilla'nın emeğini yani paylaşmayı gösteririz.</p>
-
-<p>Kodu en son sürümünde şuradan izleyin: {{Kaynak("netwerk/")}}</p>
-
-<h2 id="Documents">Documents</h2>
-
-<ul>
- <li><a href="/en-US/docs/Mozilla/Projects/Necko/Necko_walkthrough">A necko code walkthrough</a></li>
- <li><a href="/en-US/docs/Mozilla/Projects/Necko/Architecture">Necko Architecture</a></li>
- <li><a href="/en-US/docs/Mozilla/Projects/Necko/Multithreading">Necko multithreading</a></li>
- <li><a href="/en-US/docs/Mozilla/Projects/Necko/FAQ">Necko FAQ</a></li>
- <li><a href="/en-US/docs/Mozilla/Projects/Necko/Interfaces_overview">Necko Interfaces overview</a></li>
- <li><a href="/en-US/docs/Mozilla/Projects/Necko/HTTP_module">The Necko HTTP module</a></li>
- <li><a href="/en-US/docs/Mozilla/Projects/Necko/Proxies_in_Necko">Proxies in Necko</a></li>
- <li><a href="/en-US/docs/Mozilla/Projects/Necko/Proxy_Auto-Configuration_(PAC)_file">PAC files</a></li>
-</ul>
-
-<h2 id="Community">Community</h2>
-
-<ul>
- <li>View Mozilla forums... {{ DiscussionList("dev-tech-network", "mozilla.dev.tech.network") }}</li>
-</ul>
diff --git a/files/tr/mozilla/qa/bug_writing_guidelines/index.html b/files/tr/mozilla/qa/bug_writing_guidelines/index.html
deleted file mode 100644
index c317b057fa..0000000000
--- a/files/tr/mozilla/qa/bug_writing_guidelines/index.html
+++ /dev/null
@@ -1,237 +0,0 @@
----
-title: Bug report writing guidelines
-slug: Mozilla/QA/Bug_writing_guidelines
-translation_of: Mozilla/QA/Bug_writing_guidelines
----
-<div class="note">
-<p><strong>If you need help with Mozilla software (for example with Firefox, Seamonkey or Thunderbird), use one of the available <a href="http://www.mozilla.org/support/">support options</a>.</strong> Do not edit this page!</p>
-</div>
-
-<p><span class="seoSummary">This page assumes you'd like to contribute to the Mozilla project by collecting enough information to enter a useful bug report in Bugzilla, the Mozilla bug tracking system.</span> Thank you!</p>
-
-<p>If you're new to reporting bugs, you may want to try getting help from the more experienced contributors. See the Community section on the <a href="/en-US/docs/QA">QA</a> page for pointers. If you're going to report a Firefox bug, you can also get assistance in the <span style="font-family: monospace;">#firefox</span> channel on <a href="irc://irc.mozilla.org/firefox">irc.mozilla.org</a>. For other projects (e.g., Thunderbird, SeaMonkey)  you can find the appropriate channel on <a href="https://wiki.mozilla.org/IRC">IRC</a>.</p>
-
-<h2 id="How_to_report_a_bug">How to report a bug</h2>
-
-<h3 id="Open_a_new_bug_report_for_each_issue!">Open a new bug report for each issue!</h3>
-
-<p>So an effective bugfix workflow will be completed for each issue.</p>
-
-<h3 id="Other_details_you_should_heed">Other details you should heed</h3>
-
-<ol>
- <li>Figure out the <strong>steps to reproduce a bug</strong>:
-
-  <ul>
-   <li>If you have <a href="#Writing_precise_steps_to_reproduce">precise steps to reproduce</a> — great! — you're on your way to reporting a useful bug report.</li>
-   <li>If you can reproduce occasionally, but not after following specific steps, you must provide <a href="#specific-types">additional information</a> for the bug to be useful.</li>
-   <li>If you can't reproduce the problem, there's probably no use in reporting it, unless you provide unique information about its occurrence.</li>
-  </ul>
- </li>
- <li>Make sure your software is up to date. Ideally, test an in-development version to see whether your bug has already been fixed (e.g. <a href="http://www.mozilla.com/en-US/firefox/channel/">Firefox Beta, Aurora</a>, or bleeding-edge <a class="link-https" href="https://nightly.mozilla.org/">Nightly</a>).</li>
- <li>When reporting a Firefox bug, first check if you can reproduce the bug in a <a href="https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles">new Firefox profile</a>. If the bug only happens in your existing profile, try to figure out what <a href="https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems">settings, extensions</a>, or <a href="https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data">files in your profile</a> are needed to reproduce the bug.
-  <ul>
-   <li>If the bug seems egregious (i.e. obviously affecting a large portion of users), there's probably something unusual about your setup that's a necessary part of the steps to reproduce the bug. You have much better chances of figuring it out than a developer who does not have access to your system.</li>
-   <li>If the bug falls into one of <a href="#specific-types">specific types of bugs listed in a section below</a>, it may still be useful even if you can't reproduce it in a new Firefox profile.</li>
-  </ul>
- </li>
- <li>Open the <a class="link-https" href="https://bugzilla.mozilla.org/enter_bug.cgi?format=guided">Enter a new bug</a> form, which will guide you through most of the bug reporting process:
-  <ul>
-   <li>Create a Bugzilla account if you don't have one already, select the product having the bug.</li>
-   <li>Enter a <strong>clear unique summary</strong> as <a href="#Writing_a_clear_summary">described below</a>; check if the bug has already been reported (if you want to be more thorough, there's an advanced guide on <a href="/en-US/docs/Screening_duplicate_bugs">screening duplicate bugs</a>).</li>
-   <li>Provide <strong>precise steps to reproduce</strong>, <strong>expected results</strong> and <strong>actual results</strong> as <a href="#Writing_precise_steps_to_reproduce">described in the following section</a>.</li>
-   <li>Provide additional information (also <a href="#Providing_additional_information">described below</a>), especially if you can't reproduce the bug in a new profile; and/or by reporting a <strong>crash</strong>, <strong>memory usage</strong>, <strong>performance</strong>, <strong>regression</strong> bug; or if the problem is with a specific web site.</li>
-  </ul>
- </li>
- <li>If you have multiple issues, please file separate bug reports.</li>
-</ol>
-
-<h2 id="Writing_a_clear_summary">Writing a clear summary</h2>
-
-<p>How would you describe the bug using approximately 10 words? This is the first part of your bug report a triager or developer will see.</p>
-
-<p>A good summary should quickly and uniquely identify a bug report. It should explain the problem, not your suggested solution.</p>
-
-<ul>
- <li>Good: "Cancelling a File Copy dialog crashes File Manager"</li>
- <li>Bad: "Software crashes"</li>
-</ul>
-
-<ul>
- <li>Good: "Down-arrow scrolling doesn't work in &lt;textarea&gt; styled with overflow:hidden"</li>
- <li>Bad: "Browser should work with my web site"</li>
-</ul>
-
-<h2 id="Writing_precise_steps_to_reproduce">Writing precise steps to reproduce</h2>
-
-<p>How can a developer reproduce the bug on his or her own computer?</p>
-
-<p>Steps to reproduce are the <strong>most important part of any bug report</strong>. If a developer is able to reproduce the bug, the bug is very likely to be fixed. If the steps are unclear, it might not even be possible to know whether the bug has been fixed.</p>
-
-<table class="standard-table">
- <tbody>
-  <tr>
-   <th>What should you include in a bug report?</th>
-   <th>Good (precise) example</th>
-   <th>Bad (imprecise)</th>
-  </tr>
-  <tr>
-   <td>Indicate whether you can reproduce the bug at will, occasionally, or not at all.</td>
-   <td>I can reproduce by following these steps:</td>
-   <td></td>
-  </tr>
-  <tr>
-   <td>
-    <p>Describe your method of interacting with Firefox in addition to the intent of each step.</p>
-   </td>
-   <td>
-    <p>1. Start Firefox by clicking on the desktop icon<br>
-     2. Press Cmd+N (or Ctrl+N for Windows users) to open a new browser window<br>
-     3. Paste <a class="link-https" href="https://mail.google.com/" rel="freelink">https://mail.google.com/</a> in the address bar and press Enter</p>
-   </td>
-   <td>Open Gmail in another window</td>
-  </tr>
-  <tr>
-   <td>
-    <p>After your steps, precisely describe the <strong>observed (actual) result</strong> and the <strong>expected result</strong>. Clearly separate facts (observations) from speculations.</p>
-   </td>
-   <td><strong>Expected results</strong>: My Inbox displays correctly.<br>
-    <strong>Actual results</strong>: My inbox displays the message 'Your browser does not support cookies (error -91)'.</td>
-   <td>
-    <p>"It doesn't work"</p>
-
-    <p>"Page displays incorrectly"</p>
-   </td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Providing_additional_information">Providing additional information</h2>
-
-<p>The following information is requested for most bug reports. You can save time by providing this information below the Expected results. If you need to attach multiple files, you can do so after submitting the report.</p>
-
-<h3 id="For_specific_types_of_bugs"><a name="specific-types">For specific types of bugs</a></h3>
-
-<p>If you are reporting a <strong>crash bug</strong>, please <a href="/en-US/docs/How_to_get_a_stacktrace_for_a_bug_report">include a Breakpad ID or attach stack trace</a>, and include the crash signature in the bug summary as well as in the <strong>Crash Signature</strong> field.</p>
-
-<p>If you are reporting a <strong>memory use or leak bug</strong>, please <a href="/en-US/docs/Mozilla/Performance/about:memory">attach the output of about:memory</a>. Ideally, find steps to reproduce an increase in what is shown in about:memory (even after clicking the "Minimize memory usage" button at the bottom). If you have trouble finding steps to reproduce, try the Firefox Support page titled <a href="https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram">Firefox Uses Too Much Memory (Ram) - How to Fix</a>. If you are a C++ developer, <a class="link-https" href="https://developer.mozilla.org/en-US/docs/Mozilla/Performance">more precise tools are available</a>.</p>
-
-<p>If you are reporting a <strong>bug about slowness or high CPU usage</strong>, please <a href="/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem">provide a link to the performance profile in the bug</a>.</p>
-
-<p>If you are reporting a <strong>hang</strong> (beachball on macOS or "not responding" on Windows), please follow the instructions in <a href="/en-US/docs/How_to_Report_a_Hung_Firefox">How to Report a Hung Firefox</a>.</p>
-
-<p>If you are reporting a bug involving a <strong>Flash hang</strong>, please visit <a href="https://wiki.mozilla.org/Flash/Hang_Debugging">https://wiki.mozilla.org/Flash/Hang_Debugging</a> to learn how to provide useful information for developers.</p>
-
-<p>If you are reporting a <strong>bug involving a specific web page</strong>, please try to make a <a href="/en-US/docs/Reducing_testcases">reduced testcase</a> and attach it to the bug report. If you don't have time or expertise, please report the issue to <a href="https://webcompat.com/">webcompat.com</a> instead, where our volunteers will do this for you.</p>
-
-<p>If the bug was <strong>recently introduced</strong>, finding a <a href="http://mozilla.github.io/mozregression/quickstart.html">regression window</a> can help identify the cause of the bug.</p>
-
-<p><a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html#intermittent">What if my bug seems "random" or "intermittent"?</a></p>
-
-<h3 id="For_most_Firefox_bugs">For most Firefox bugs</h3>
-
-<p>You should provide the following information for most Firefox bugs.</p>
-
-<table class="standard-table">
- <tbody>
-  <tr>
-   <th>What should you include in a bug report?</th>
-   <th>Example</th>
-  </tr>
-  <tr>
-   <td>Indicate if the problem can be reproduced using a <a href="https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles">new Firefox profile</a> and any changes you need to make in order to reproduce.</td>
-   <td>The problem can be reproduced in a new profile, but only if Preferences -&gt; Privacy &amp; Security -&gt; Tracking Protection is selected.</td>
-  </tr>
-  <tr>
-   <td>If you can only reproduce with an existing profile try to figure out what <a href="https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems">settings, extensions</a>, or <a href="https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data">files in your profile</a> are needed to reproduce the bug. If you skip the step, <a href="https://support.mozilla.org/en-US/kb/use-troubleshooting-information-page-fix-firefox">save the troubleshooting information from about:support</a> to a file and attach it to the bug report.</td>
-   <td>I can't reproduce in a new profile, about:support information from the offending profile is attached.</td>
-  </tr>
-  <tr>
-   <td>
-    <p>Indicate if the problem can be reproduced using the <a href="https://nightly.mozilla.org/">latest Nightly build</a>. Include the <strong>Build ID</strong> from <a href="https://support.mozilla.org/en-US/kb/use-troubleshooting-information-page-fix-firefox">about:support</a>.</p>
-
-    <p>If possible, test using the new Firefox profile you created. If you need to test the Nightly build with your regular profile, you might want to <a href="https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles">back up the profile</a> first, since the pre-release build may corrupt your data.</p>
-   </td>
-   <td>The problem can be reproduced on the latest Nightly (Build ID 20170416100136).</td>
-  </tr>
- </tbody>
-</table>
-
-
-
-<div class="originaldocinfo">
-<h2 id="Original_document_information">Original document information</h2>
-
-<ul>
- <li>Author(s): Jesse Ruderman, Gervase Markham</li>
- <li>Other Contributors: Eli Goldberg, Claudius Gayle, Jan Leger, Felix Miata, Peter Mock, Chris Pratt, Chris Yeh, and others.</li>
-</ul>
-</div>
-
-
-
-<hr>
-<h2 id="Advanced">Advanced</h2>
-
-<h3 id="Finding_the_correct_product_and_component" name="Finding_the_correct_product_and_component"><strong style="font-weight: bold;">Finding the correct product and component</strong></h3>
-
-<p>You will be asked to categorize your bug into a "product" and a "component" within that product, in order to direct your report to the correct developers.</p>
-
-<p>If you're using Firefox, the bug is most likely in "Firefox", "Toolkit", or "Core".</p>
-
-<ul>
- <li><a class="link-https" href="https://bugzilla.mozilla.org/describecomponents.cgi?product=Firefox">List of components in the "Firefox" product</a> - Most parts of Firefox that you interact with directly</li>
- <li><a class="link-https" href="https://bugzilla.mozilla.org/describecomponents.cgi?product=Toolkit">List of components in the "Toolkit" product</a> - Interface widgets and some frontend features</li>
- <li><a class="link-https" href="https://bugzilla.mozilla.org/describecomponents.cgi?product=Core">List of components in the "Core" product</a> - Web page rendering, networking, etc.</li>
-</ul>
-
-<p>When in doubt, search for similar bugs and see which component they are in.</p>
-
-<p>If none of the components seem appropriate, look for a "General" component in the most appropriate product.</p>
-
-<h3 id="General_Outline_of_a_Bug_Report">General Outline of a Bug Report</h3>
-
-<div class="note">
-<p>Most of the following article has been merged into this page from QMO: How to write a proper bug</p>
-</div>
-
-<ul>
- <li><strong>Summary</strong>: How would you describe the bug in less than 60 characters? It should quickly and uniquely identify a bug report as well as explain the problem, not your suggested solution. Good: "Canceling a File Copy dialog crashes File Manager" Bad: "Software crashes" Bad: "Browser should work with my web site"</li>
- <li><strong>Component</strong>: In which sub-part of the software does it exist? This field is a requirement to submit any bug report. Click the word "Component" to see a description of each component. If none seems appropriate, highlight the "General" component.</li>
- <li><a name="version"> </a><strong>Version</strong>: select the earliest Version with what the problem can be reproduced:
-  <ul>
-   <li>Developers will use that information to narrow down the commit what introduced a regression</li>
-   <li>QA staff needs that information to distinguish bugs with similar symptoms, but different roots.
-    <ul>
-     <li>Bugs that definitively appeared in different <em>Product</em> <em>Versions</em> probably will have different roots</li>
-     <li>But Bugs that started with the same <em>Product</em> <em>Version</em> probably are DUPLICATEs</li>
-    </ul>
-   </li>
-   <li><em>Trunk</em> does not allow any useful query. We have <em>Trunk</em> version bugs from beginning of the project until today, no common characteristics at all what can be tagged with this version. Avoid Trunk, replace it by precise information with what version the problem appeared if you can.</li>
-  </ul>
- </li>
- <li><strong>OS</strong>: On which operating system (OS) did you find it? (E.g. Linux, Windows, and Mac.) Example: "<em>If you know the bug happens on more than one type of operating system, choose "All". If your OS isn't listed, choose Other".</em></li>
- <li><strong>Description</strong>: The details of your problem report, including:
-  <ul>
-   <li><u>Overview</u>: This is a larger detailed restatement of the summary. An example would be: <em>"Drag-selecting any page crashes Mac builds in the NSGetFactory function"</em>.</li>
-   <li><u>Build Id</u>: To find this either go to the "about:support" page via the location bar or, if you have MozQA's <a href="https://addons.mozilla.org/en-US/firefox/addon/nightly-tester-tools/">Nightly Tester Tools</a> extension, then go to Tools | Nightly Tester Tools and select the option that contains the output of the build Id. It should look something like this: <em>"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Firefox/38.0 ID:20150330004006 CSet: 9e57e9776571"</em>.</li>
-   <li><u>Additional Builds and Platforms</u>: Whether or not the bug takes place on other platforms (or browsers, if applicable). It should look something like this: <em>"Doesn't Occur On Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Firefox/38.0 ID:20150330004006 CSet: 9e57e9776571"</em>.</li>
-  </ul>
- </li>
- <li><strong>Steps to Reproduce</strong>: Minimized, easy-to-follow steps that will trigger the bug. If they're necessary, make sure to include any special setup steps. A good example of this would look like the following:<br>
-  1) View any web page. (I used the default sample page, http://www.google.com/).<br>
-  2) Drag-select the page. Specifically, while holding down the mouse button, drag the mouse pointer downwards from any point in the browser's content region to the bottom of the browser's content region.</li>
- <li><strong>Actual Results</strong>: What the application did after performing the above steps. An example would be: <em>The application crashed.</em></li>
- <li><strong>Expected Results</strong>: What the application should have done, were the bug not present. An example would be: <em>The window should scroll downwards. Scrolled content should be selected. Or, at least, the application should not crash.</em></li>
-</ul>
-
-
-
-<div class="originaldocinfo">
-<h4 id="Original_document_information_2">Original document information</h4>
-
-<ul>
- <li>Author(s): Aakash Desai</li>
- <li>Date last modified: June 3, 2013 at 2:41 am PST</li>
-</ul>
-</div>
diff --git a/files/tr/mozilla/qa/index.html b/files/tr/mozilla/qa/index.html
deleted file mode 100644
index 81412404dc..0000000000
--- a/files/tr/mozilla/qa/index.html
+++ /dev/null
@@ -1,251 +0,0 @@
----
-title: 'QA: Quality assurance at Mozilla'
-slug: Mozilla/QA
-tags:
-  - Landing
-  - NeedsTranslation
-  - QA
-  - Testing
-  - TopicStub
-translation_of: Mozilla/QA
----
-<p>The Mozilla Quality Assurance (QA) team drives software quality assurance activities across Mozilla and plays a key role in releasing a diverse range of software products on schedule. Within each project in Mozilla, we work to explore new features, write and execute tests, uncover and file bugs, build and maintain tools, collect and analyze metrics, and support the release world-class products that promote the open Web.</p>
-
-<p><span class="seoSummary">Here you'll find articles and tools to help you gear up to join the QA team testing Firefox to ensure that each release is as good as it can be.</span></p>
-
-<h2 id="Get_started">Get started</h2>
-
-<ul class="card-grid">
- <li><span>How can I help test?</span>
-
-  <p>There are lots of ways for you to become a <a href="/en-US/docs/Mozilla/QA/How_can_I_help_test_">community contributor</a> to the Mozilla quality team.</p>
- </li>
- <li><span>Bugs</span>
-  <p>All Mozilla projects use <a href="https://bugzilla.mozilla.org/">Bugzilla</a> to track bugs. Learn how to <a href="/en-US/docs/Mozilla/QA/Bug_writing_guidelines" title="/en-US/docs/Mozilla/QA/Bug_writing_guidelines">report a bug</a> and get familiar with <a href="/en-US/docs/What_to_do_and_what_not_to_do_in_Bugzilla">what to do in Bugzilla</a>.</p>
- </li>
- <li><span>Events</span>
-  <p>Get involved in our weekly <a href="/en-US/docs/Mozilla/QA/Bug_Verification_Day">Bug Verification Day</a> or <a href="/en-US/docs/Mozilla/QA/Bug_Triage_Day">Bug Triage Day</a>. You may even <a href="/en-US/docs/Mozilla/QA/Organizing_a_Testday">organize a testday</a> for your local community!</p>
- </li>
- <li><span>IRC</span>
-  <p><a href="/en-US/docs/Mozilla/QA/Getting_Started_with_IRC">Get started with IRC</a>, the primary form of communication for members of the Mozilla community.</p>
- </li>
-</ul>
-
-<h2 id="Bugs">Bugs</h2>
-
-<div class="row topicpage-table">
-<div class="section">
-<h3 id="Reporting_bugs">Reporting bugs</h3>
-
-<dl>
- <dt><a href="/en-US/docs/Mozilla/Bugzilla">Bugzilla</a></dt>
- <dd>All Mozilla projects use <a href="https://bugzilla.mozilla.org/">Bugzilla</a> to track bugs. You will need to <a href="https://bugzilla.mozilla.org/createaccount.cgi">create an account with Bugzilla</a> in order to report bugs and triage them.</dd>
- <dt><a href="/en-US/docs/Mozilla/QA/Bug_writing_guidelines" title="/en-US/docs/Mozilla/QA/Bug_writing_guidelines">Bug writing guidelines</a></dt>
- <dd>The more effectively a bug is reported, the more likely that an engineer will actually fix it. By following these guidelines, you can help ensure that your bugs stay at the top of the Mozilla engineers' heap, and get fixed.</dd>
- <dt><a href="/en-US/docs/Mozilla/QA/A_Bugs_Life" title="/en-US/docs/Mozilla/QA/A_Bugs_Life">A Bug's Life</a></dt>
- <dd>This tutorial will give an overview of what happens in the states that a bug will go through as well as how it will go from one to the next within its total life. It also explains the meaning of flags/keywords used in QA.</dd>
- <dt><a href="/en-US/docs/Mozilla/QA/Filing_Crash_Bugs">Filing Crash Bugs</a></dt>
- <dd>This document lists guidelines and tips on how to file bug reports for crashes in a way that helps in debugging and fixing the reported issue.</dd>
-</dl>
-</div>
-
-<div class="section">
-<h3 id="Triaging_bugs">Triaging bugs</h3>
-
-<dl>
- <dt><a href="/en-US/docs/Mozilla/QA/Confirming_unconfirmed_bugs" title="en-US/docs/Confirming unconfirmed bugs">Confirming unconfirmed bugs</a></dt>
- <dd>Identify useful bug reports and close the rest.</dd>
- <dt><a href="/en-US/docs/Mozilla/QA/Triaging_Bugs_for_Firefox" title="/en-US/docs/Mozilla/QA/Triaging_Bugs_for_Firefox">Triaging Bugs for Firefox</a></dt>
- <dd>Information about the entire bug triaging process – from processing incoming bugs to narrowing down the steps to reproducing bugs.</dd>
- <dt><a href="/en-US/docs/Screening_duplicate_bugs">Screening duplicate bugs</a></dt>
- <dd>Help get bugs fixed faster by screening incoming reports for duplicates.</dd>
- <dt><a href="/en-US/docs/What_to_do_and_what_not_to_do_in_Bugzilla">General Guidelines</a></dt>
- <dd>What to do and what not to do in Bugzilla.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h2 id="Manual_testing">Manual testing</h2>
-
-<div class="row topicpage-table">
-<div class="section">
-<dl>
- <dt><a href="/en-US/docs/Mozilla/QA/Test_Case_Writing_Primer">Manual Test Case Writing Primer</a></dt>
- <dd>How to write proper manual test cases</dd>
-</dl>
-</div>
-
-<div class="section">
-<dl>
- <dt><a href="https://testrail.stage.mozaws.net/">TestRail</a></dt>
- <dd>Mozilla QA's manual test cases reside in TestRail. You will need an LDAP account in order to login and execute test cases. Learn more on the <a href="https://wiki.mozilla.org/TestEngineering/Testrail">TestRail wiki page</a>.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h2 id="Automated_testing">Automated testing</h2>
-
-<div class="row topicpage-table">
-<div class="section">
-<dl>
- <dt><a href="/en-US/docs/Mozilla/QA/Automated_testing" title="/en-US/docs/Mozilla/QA/Automated_testing">Automated testing at Mozilla</a></dt>
- <dd>Documentation about creating and using automated tests for Mozilla code.</dd>
- <dt><a href="/en-US/docs/Mozilla/QA/Running_automated_tests">Running automated tests</a></dt>
- <dd>
- <p>This page lists the steps required to run Mozilla's automated test suites.</p>
- </dd>
- <dt><a href="/en-US/docs/Mozilla/QA/Developing_tests" title="en-US/docs/Developing_Tests">Developing tests</a></dt>
- <dd>Ensure that future changes to Mozilla don't break things that currently work correctly.</dd>
- <dt><a href="/en-US/docs/Mozilla/QA/Avoiding_intermittent_oranges" title="en-US/docs/QA/Avoiding intermittent oranges">Avoiding intermittent test failures</a></dt>
- <dd>Suggestions for ways to make your tests more reliable, thereby helping to avoid random, intermittent test failures.</dd>
- <dt><a href="/en-US/docs/Mozilla/QA/Test_Verification">Test Verification</a></dt>
- <dd>When a changeset adds a new test, or modifies an existing test, the test verification (TV) test suite performs additional testing to help find intermittent failures in the modified test as quickly as possible.</dd>
- <dt><a href="/en-US/docs/Mozilla/QA/Mozharness_FAQ">Mozharness FAQ</a></dt>
- <dd>Answers to common questions about Mozharness.</dd>
-</dl>
-</div>
-
-<div class="section">
-<dl>
- <dt><a href="/en-US/docs/Mozilla/QA/Robocop" title="/en-US/docs/Mozilla/QA/Robocop">Robocop</a></dt>
- <dd>Robocop is the automated testing system used for Firefox for Android. Learn its <a href="/en-US/docs/Mozilla/QA/Robocop/Code_style_guidelines">code style guidelines</a></dd>
- <dt><a href="/en-US/docs/Mozilla/QA/Marionette">Marionette</a></dt>
- <dd>Get started with Marionette UI testing.</dd>
- <dt><a href="/en-US/docs/Mozilla/QA/web-platform-tests">web-platform-tests</a></dt>
- <dd>Learn how to use the industry standard, cross-browser, cross-platform <a href="http://testthewebforward.org/docs/">Web runtime testing system</a> from the <a href="https://www.w3.org/">W3C</a> used by Mozilla and others to ensure browser interoperability.</dd>
- <dt><a href="/en-US/docs/Mozilla/QA/external-media-tests">External Media Tests</a></dt>
- <dd>Get started testing HTML5-based video elements using VideoPuppeteer, a <a href="/en-US/docs/Mozilla/QA/Marionette">Marionette</a>- -based test suite used to test sites like YouTube and Netflix.</dd>
- <dt><a href="/en-US/docs/Mozilla/QA/Chrome_tests">Chrome tests</a></dt>
- <dd>A chrome test is basically a <a href="https://developer.mozilla.org/en-US/docs/Mochitest" title="en/Mochitest">Mochitest</a> running with chrome privileges.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h2 id="Firefox_QE">Firefox QE</h2>
-
-<div class="row topicpage-table">
-<div class="section">
-<dl>
- <dt><a href="/en-US/docs/Mozilla/QA/Triaging_Bugs_for_Firefox" title="/en-US/docs/Mozilla/QA/Triaging_Bugs_for_Firefox">Triaging Bugs for Firefox</a></dt>
- <dd>Information about the entire bug triaging process – from processing incoming bugs to narrowing down the steps to reproduce a bug.</dd>
-</dl>
-
-<dl>
- <dt><a href="/en-US/docs/Mozilla/QA/Tips_and_Tricks">Tips and Tricks</a></dt>
- <dd>These tips and tricks will make your life easier when you are testing.</dd>
-</dl>
-<a href="/en-US/docs/Downloading_Nightly_or_Trunk_Builds">Downloading Nightly or Trunk Builds</a>
-
-<dl>
- <dd>Every 24 hours, a "nightly" build is created that testers all over the world download and test, reporting as they go along on any bugs that hit them. </dd>
-</dl>
-</div>
-
-<div class="section">
-<dl>
- <dt><a href="/en-US/docs/Mozilla/Command_Line_Options">Command Line Options</a></dt>
- <dd>Command line options are used to specify various startup options for Firefox.</dd>
- <dt><a href="/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem">Reporting a Performance Problem</a></dt>
- <dd>This article will guide you in reporting a performance problem using the <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler">Gecko Profiler extension</a>.</dd>
- <dt><a href="/en-US/docs/Mozilla/Projects/Crash_reporting">Crash reporting</a></dt>
- <dd>Firefox ships with an open-source crash reporting system.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h2 id="Firefox_for_Android">Firefox for Android</h2>
-
-<div class="row topicpage-table">
-<div class="section">
-<dl>
- <dt><a href="/en-US/docs/Mozilla/QA/Mobile_Firefox">Mobile Firefox</a></dt>
- <dd>Firefox for Android is the mobile version of Firefox with a native Android look and feel.</dd>
- <dt><a href="/en-US/Firefox_for_Android/Compatibility_Testing">Compatibility Testing</a></dt>
- <dd>Help us identify websites that do not work well in Firefox by reporting the specific issues that you find in your investigation.</dd>
-</dl>
-</div>
-
-<div class="section">
-<dl>
- <dt><a href="/en-US/docs/Mozilla/QA/Fennec_Android:_Logging_with_the_Android_Debug_and_Logcat">Logging with the Android Debug Bridge and Logcat</a></dt>
- <dd>This article will provide a walkthrough in downloading and setting up an environment to which one can gain access to and view Android system logs.</dd>
- <dt><a href="/en-US/docs/Mozilla/QA/Firefox_Mobile:_Enabling_the_Error_Console">Enabling the Error Console</a></dt>
- <dd>See the Mozilla Hacks article on <a class="external external-icon" href="https://hacks.mozilla.org/2012/08/remote-debugging-on-firefox-for-android/">Remote Debugging on Firefox for Android</a> for web content. If you need to debug the Firefox browser itself use Android's <a class="external external-icon" href="http://developer.android.com/tools/help/logcat.html">adb logcat</a>.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h2 id="Firefox_OS">Firefox OS</h2>
-
-<div class="row topicpage-table">
-<div class="section">
-<h3 id="Manual_testing_2">Manual testing</h3>
-
-<dl>
- <dt><a href="/en-US/Firefox_OS/Simulator_vs_Emulator_vs_Device">Simulator vs Emulator vs Device</a></dt>
- <dd>These are three basic options when it comes to getting a Firefox OS environment in order to work on, or developing for, Firefox OS.</dd>
- <dt><a href="/en-US/Firefox_OS/Debugging">Debugging</a></dt>
- <dd>Discover the different tools at your disposal to debug your Firefox OS code.</dd>
- <dt><a href="/en-US/Firefox_OS/Developing_Firefox_OS/Filing_bugs_against_Firefox_OS">Reporting Bugs</a></dt>
- <dd>This article provides a guide to filing bugs against the Firefox OS project, including Gaia and B2G.</dd>
-</dl>
-</div>
-
-<div class="section">
-<h3 id="Platform_Gecko">Platform (Gecko)</h3>
-
-<dl>
- <dt><a href="/en-US/Firefox_OS/Platform/Automated_testing">Automated Testing</a></dt>
- <dd>Learn various aspects of testing Firefox OS, including running different tests, automation, and result reporting and tracking.</dd>
- <dt><a href="/en-US/Firefox_OS/Platform/Automated_testing/Gaia_performance_tests">Gaia Performance Tests</a></dt>
- <dd>This article provides information about running performance tests on Gaia, as well as how to create new tests.</dd>
- <dt><a href="/en-US/Firefox_OS/Platform/Feature_support_chart">Feature Support Chart</a></dt>
- <dd>There are several different builds of Firefox OS you can download or build for yourself, and there are some differences between the types of features available on each device.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h2 id="Web_QA">Web QA</h2>
-
-<div class="row topicpage-table">
-<div class="section">
-<dl>
- <dt><a href="/en-US/docs/Mozilla/QA/Reducing_testcases" title="en-US/docs/Reducing testcases">Reducing testcases</a></dt>
- <dd>Improve bug reports by turning broken web pages into simple testcases, which can help developers understand the bug and can also be used for creating automated tests.</dd>
- <dt><a href="/en-US/docs/Mozilla/QA/Managing_Web_QA_XFails">Managing XFails</a></dt>
- <dd>One of the ongoing tasks of the Web QA department is managing xfails. This document will explain what xfails are, and describe the steps one can take to investigate and update them.</dd>
-</dl>
-</div>
-
-<div class="section">
-<dl>
- <dt><a href="/en-US/docs/Mozilla/QA/Running_Web_QA_automated_tests">Running Automated Tests</a></dt>
- <dd>So you’re interested in contributing to Mozilla Web QA automation projects but don’t know where to start? This doc will help you get up and running a set of tests locally.</dd>
-</dl>
-</div>
-</div>
-
-<hr>
-<h2 id="Glossary">Glossary</h2>
-
-<div class="section">
-<dl>
- <dt><a href="/en-US/docs/Glossary/Smoke_Test">Smoke Test</a></dt>
- <dd></dd>
-</dl>
-</div>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="https://lists.mozilla.org/listinfo/dev-quality">Mailing list</a></li>
- <li><a href="https://quality.mozilla.org/">Blog</a></li>
- <li><a href="/en-US/docs/tag/QA" title="en-US/docs/tag/QA">View all documents tagged QA</a></li>
- <li><a href="/en-US/docs/tag/QA:Tools" title="en-US/docs/tag/QA:Tools">View all documents tagged QA:Tools</a></li>
-</ul>