unslug tr: move

11 files changed, 1369 insertions, 0 deletions

diff --git a/files/tr/orphaned/fennec_(firefox_mobile)/index.html b/files/tr/orphaned/fennec_(firefox_mobile)/index.html
new file mode 100644
index 0000000000..a10390a2d6
--- /dev/null
+++ b/files/tr/orphaned/fennec_(firefox_mobile)/index.html
@@ -0,0 +1,15 @@
+---
+title: Mobile
+slug: Fennec_(Firefox_Mobile)
+tags:
+  - Firefox
+  - Mobile
+  - firefox fennec
+  - mobil
+  - mobile firefox
+---
+<p><img alt="fennec_logo.png" class="internal default" src="/@api/deki/files/4246/=fennec_logo.png"></p>
+<p>Firefox'un cep telefonları için olan sürümüdür. Ekran görüntüleri aşağıdaki gibidir. Yakında daha ayrıntılı bilgiye buradan erişebileceksiniz.</p>
+<p><img alt="fennec_ss1.png" class="internal default" src="/@api/deki/files/4243/=fennec_ss1.png"></p>
+<p><img alt="fennec_ss2.png" class="internal default" src="/@api/deki/files/4244/=fennec_ss2.png"></p>
+<p><img alt="fennect_ss3.png" class="internal default" src="/@api/deki/files/4245/=fennect_ss3.png"></p>
diff --git a/files/tr/orphaned/mdn/community/index.html b/files/tr/orphaned/mdn/community/index.html
new file mode 100644
index 0000000000..76cdfb75bf
--- /dev/null
+++ b/files/tr/orphaned/mdn/community/index.html
@@ -0,0 +1,53 @@
+---
+title: Join the MDN community
+slug: MDN/Community
+tags:
+  - MDN Meta
+  - Rehber
+  - Topluluk
+translation_of: MDN/Community
+---
+<div>{{MDNSidebar}}</div>
+
+<div>{{IncludeSubnav("/en-US/docs/MDN")}}</div>
+
+<div class="summary">
+<p>MDN web dökümanları vikiden daha fazlasıdır: Açık Web teknolojileri hakkında dökümanlar oluşturulan , birlikte çalışan yazılım geliştiricilerinden oluşan bir topluluktur. </p>
+</div>
+
+<p>MDN'e katkıda bulunmanızdan hoşnut oluruz, bunun yanında MDN topluluğuna katılmanız bizi daha da mutlu eder. Aşağıda nasıl bağlanacağınza dair üç adım verilmiştir.</p>
+
+<ol>
+ <li>MDN üyeliği oluşturun.</li>
+ <li>Tartışmalara katılın.</li>
+ <li>Ne olduğunu takip edin.</li>
+</ol>
+
+<h2 id="Topluluk_nasıl_çalışır">Topluluk nasıl çalışır</h2>
+
+<p>Sonraki paragraflar MDN topluluğunun nasıl çalıştığını açıklamaktadır..</p>
+
+<div class="row topicpage-table">
+<div class="section">
+<dl>
+ <dt class="landingPageList"><a href="/en-US/docs/MDN/Community/Roles">Topluluk Görevleri</a></dt>
+ <dd class="landingPageList">Çeşitli sorumluları olan çeştili roller anlatılmaktadır.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/MDN/Community/Doc_sprints">Döküman Turları </a></dt>
+ <dd class="landingPageList">Döküman turlarının organizyonu ve çeşitli öneriler, kısayollar paylaşılmaktadır.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/MDN/Community/Whats_happening">Ne olduğunu Takip Edin</a></dt>
+ <dd class="landingPageList">MDN sizi   <a class="external" href="https://wiki.mozilla.org/MDN">Mozilla Developer Network </a>Topluluğu taradından oluşturulur.  Burada nasıl bilgi paylaşılacağı anlatılmaktadır.</dd>
+</dl>
+
+<dl>
+</dl>
+</div>
+
+<div class="section">
+<dl>
+ <dt class="landingPageList"><a href="/en-US/docs/MDN/Community/Conversations">MDN Topluluk Tartışmaları</a></dt>
+ <dd class="landingPageList">MDN'deki "işler" MDN web sitesinde görülür ancak topluluk tartışmalara (Eşzamanlı) ve Anlık Mesajlaşma toplantıları ile işleyişe katkıda bulunabilir.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/MDN/Community/Working_in_community">Topluluk İçinde Çalışmak</a></dt>
+ <dd class="landingPageList">Katkı hakkındaki en önemli konulardan biri MDN topluluğu ile nasıl çalışılacağını bilmektir. Bu makale çeşitli öneriler ile yazarlar ve geliştiriciler arasında bağlantı  kurmada yardımcı olmayı amaçlamaktadır.</dd>
+</dl>
+</div>
+</div>
diff --git a/files/tr/orphaned/mdn/contribute/howto/do_an_editorial_review/index.html b/files/tr/orphaned/mdn/contribute/howto/do_an_editorial_review/index.html
new file mode 100644
index 0000000000..026332438c
--- /dev/null
+++ b/files/tr/orphaned/mdn/contribute/howto/do_an_editorial_review/index.html
@@ -0,0 +1,48 @@
+---
+title: Bir editör incelemesi nasıl yapılır?
+slug: MDN/Contribute/Howto/Editor_incelemesi_nasil_yapilir
+translation_of: MDN/Contribute/Howto/Do_an_editorial_review
+---
+<div>{{MDNSidebar}}</div><div>{{IncludeSubnav("/en-US/docs/MDN")}}</div>
+
+<p class="summary"><strong>Editör incelemeleri bir yazıda yazım hataları, imla hataları, dil bilgisi, kullanım veya metinsel hataları düzeltmekten ibarettir. Katkıda bulunanların tamamı dil uzmanları değildir, ancak bilgilerine bakılmaksızın, kopyalama, düzenleme ve son okuma/düzeltmeye ihtiyaç duyan son derece yararlı makale yazmış olacaklardır. Bu bir editör incelemesinde yapılır.</strong></p>
+
+<p><span class="seoSummary">Bu makale, MDN'nin içeriğinin doğru olduğundan emin olmak için bir editör incelemesinin nasıl yapılacağını açıklar.</span></p>
+
+<dl>
+ <dt>Görev nedir?</dt>
+ <dd>Bir "editör incelemesi gerektiriyor" olarak işaretlenmiş makalelerin kopyalama-düzenleme ve son okuması/düzenlemesi.</dd>
+ <dt>Nerede yapılması gerekiyor?</dt>
+ <dd>Bir "editör incelemesi gerektiriyor" olarak işaretlenmiş makalelerde yapılması gerekiyor.</dd>
+ <dt>Görevi yapmak için bilmeniz gereken şey nedir?</dt>
+ <dd>İyi İngilizce dil bilgisi ve yazım becerilerine sahip olmanız gerekir. Bir editör incelemesi, dil bilgisi, yazım denetimi ve ifadelerin doğru ve mantıklı olmasını sağlamak ve <a href="/en-US/docs/MDN/Contribute/Guidelines/Writing_style_guide">MDN yazım sitili rehberi</a>nin izlenmesiyle ilgilidir.</dd>
+ <dt>Bunu yapmanın adımları nelerdir?</dt>
+ <dd>
+ <ol>
+  <li>İncelenecek bir makale seçin:
+   <ol>
+    <li><a href="/en-US/docs/needs-review/editorial">Editörlük incelemesine ihtiyaç duyan makaleler listesi</a>ne gidin. Bu liste, editör incelemesinin talep edildiği tüm sayfaları listeler.</li>
+    <li>İngilizce başlığına sahip ve sayfa yolu Template ile başlamayan bir sayfa seçin. (<code>Template:</code> sayfalar MDN makro kodu içermektedir.)</li>
+    <li>Sayfayı yüklemek için makale bağlantısını tıklayın.</li>
+   </ol>
+  </li>
+  <li><a id="core-steps" name="core-steps"></a> Yazım hatalarını, dil bilgisini veya kullanım hatalarını yakından takip ederek makaleyi okuyun. Seçtiğiniz ilk sayfa sizin için uygun değilse farklı bir sayfaya geçmekten çekinmeyin..</li>
+  <li>Herhangi bir hata yoksa makaleyi gözden geçirilmiş olarak işaretlemek için düzenlemenize gerek yoktur. Sayfanın sol kenar çubuğundaki "hızlı inceleme" kutusunu bulun:<br>
+   <img alt="Screenshot of the editorial review request sidebar box" src="https://mdn.mozillademos.org/files/13018/SidebarReviewBoxEditorial.png"></li>
+  <li>Editöryel(<strong>Editorial</strong>) kutusundaki seçimi kaldırın ve Kaydet(<strong>Save) </strong>düğmesine tıklayın.</li>
+  <li>Düzeltilmesi gereken hatalar bulursanız:
+   <ol>
+    <li>Sayfanın üst kısmındaki Düzenle(<strong>Edit</strong>) düğmesini tıklayın; Bu sizi <a href="/en-US/docs/Project:MDN/Contributing/Editor_guide">MDN editör</a>üne getiriyor.</li>
+    <li>Bulduğunuz yazım hatalarını, yazım kurallarını, dilbilgisi veya kullanım hatalarını düzeltin. Her şeyi düzeltmek zorunda değilsiniz, ancak tüm makalenin tam bir incelemesini yaptığınızı makul bir derecede eminseniz, editörlük inceleme talebini yerine getirdiğinizden emin olun..</li>
+    <li>Makalenin en altında Revizyon Yorumu (<strong>Revision Comment)</strong> düğmesine basın; açıklama kısmına 'Editöryel inceleme: sabit yazım hataları, dilbilgisi ve yazım denetimi' gibi birşey yazabilirsiniz. Bu diğer katkıda bulunanlar ve site editorleri tarafından sayfada ne değişti neden değiştiyi bilmeleri içindir.</li>
+    <li>İnceleme Gerekli mi(<strong>Review Needed</strong>)? Editöryel(<strong>Editorial)</strong> kutusunun seçimini kaldırın. Bu, sayfanın Revizyon Yorumu(<strong>Revision Comment</strong>) bölümünün hemen altında yer alır.</li>
+    <li>Yayınla (<strong>Publish)</strong> düğmesine tıklayın.</li>
+   </ol>
+  </li>
+ </ol>
+
+ <div class="note">
+ <p>Değişiklikleriniz kaydedildikten hemen sonra görünmeyebilir; Sayfa işlenirken ve kaydedilirken bir gecikme olabilir.</p>
+ </div>
+ </dd>
+</dl>
diff --git a/files/tr/orphaned/mdn/editor/basics/index.html b/files/tr/orphaned/mdn/editor/basics/index.html
new file mode 100644
index 0000000000..cf3f1475a1
--- /dev/null
+++ b/files/tr/orphaned/mdn/editor/basics/index.html
@@ -0,0 +1,427 @@
+---
+title: MDN editor basics
+slug: MDN/Editor/Basics
+translation_of: MDN/Editor/Basics
+---
+<div>{{MDNSidebar}}</div><p><span class="seoSummary">Editing content on MDN is easy; you can use the built-in WYSIWYG editor to create, edit, and improve articles and other pages almost anywhere on the site.</span> The editor window, shown below, is comprised of eight key boxes. This section will provide information about each section so you know how to use our entire editing environment.</p>
+<div class="note">
+ <p><strong>Note:</strong> We're constantly working on improvements to MDN, so there will be times when this documentation or the screen shots below may be slightly out-of-date. We'll periodically update this documentation, though, to avoid it being unusably behind.</p>
+</div>
+<p><a href="https://mdn.mozillademos.org/files/5315/edit-page-normal-labeled.png"><img alt="" src="https://mdn.mozillademos.org/files/5315/edit-page-normal-labeled.png" style="width: 600px; height: 631px; border-width: 1px; border-style: solid;"></a></p>
+<h2 id="Page_controls">Page controls</h2>
+<p>The page controls area offers buttons affecting the page as a whole:</p>
+<dl>
+ <dt>
+  Save and keep editing</dt>
+ <dd>
+  Saves the page without closing the editor; this lets you periodically save your work, creating an entry in the page history that you can revert to if you need to, or in case you need to stop working and come back to it later. This option is not available when creating new pages. See {{anch("The revision comment box")}} to learn how to include a revision comment on your saved article.</dd>
+ <dt>
+  Save changes</dt>
+ <dd>
+  Saves the page and closes the editor, returning you to view the page in standard browsing mode. See {{anch("The revision comment box")}} to learn how to include a revision comment on your saved article.</dd>
+ <dt>
+  Preview changes</dt>
+ <dd>
+  Opens a new tab or window showing the page as it exists in your editor, rendered as if you were browsing to it. This includes executing any macros you use in-content. Your work is <strong>not</strong> saved when you use this option. This lets you check to be sure you haven't made any errors in your macro syntax or other formatting that may prevent the page from rendering correctly.</dd>
+ <dt>
+  Discard changes</dt>
+ <dd>
+  Cancels your edit, disposing of any changes you've made without saving them. You're returned to the page in standard browsing mode.</dd>
+</dl>
+<h2 id="The_page_info_box">The page info box</h2>
+<p>The page info box contains information about the page, but also can be expanded to offer additional page controls. By default, it displays the page's title and the date and time at which a local draft was saved; the local draft, stored on your computer, is used as a backup in case you accidentally navigate away from the editor or your browser crashes.</p>
+<p>You can click the "Edit Page Title and Properties" link to switch to a view offering additional page controls. This view looks like this:</p>
+<p><img alt="" src="https://mdn.mozillademos.org/files/5317/expanded-page-info.png" style="width: 517px; height: 69px;"></p>
+<p>This view allows you to change the page's display title and the depth of the page's table of contents. The display title is the title shown in the browser's title bar (or tab bar) and as the title of the page at the top of the article and in the breadcrumb bar, as appropriate. It doesn't affect the page's URL.</p>
+<div class="note">
+ <p><strong>Note:</strong> It's worth noting that we prefer short URLs and descriptive titles; for example, the article about the Kuma API has the title "The Kuma API" but its URL slug (the part after the site's root) is Project:MDN/Kuma/API, where "API" represents this page.</p>
+</div>
+<p>The TOC (table of contents) level lets you specify how deeply into the article's heading levels the table of contents automatically displayed on the page should go. By default, heading levels {{HTMLElement("h2")}} through {{HTMLElement("h4")}} are included in the TOC, so that the TOC has a three-level depth. However, you can set this to any of those, as well as "No TOC" (to not display a TOC at all, such as on landing pages) or to show all levels in the TOC.</p>
+<p>As is the case with all changes you might make, changes in the page info box do not take effect unless you save the page.</p>
+<h2 id="The_toolbar">The toolbar</h2>
+<p>The editor's toolbar offers features that let you adjust the appearance and flow of the article as you work. There are two rows of buttons (more if the width of your window is narrow enough that they wrap, but generally two) and a third row that shows the hierarchy of HTML elements leading up to where you are. In the screenshot below, for example, you're writing inside a top-level {{HTMLElement("p")}} block.</p>
+<p><img alt="" src="https://mdn.mozillademos.org/files/5319/edit-toolbar.png" style="width: 771px; height: 88px;"></p>
+<p>The toolbar's buttons are divided into seven groups. Let's look at each; we will examine the buttons in each group in order left-to-right.</p>
+<h3 id="Document_options">Document options</h3>
+<p>The document options box provides options for document-level manipulations:</p>
+<p> </p>
+<dl>
+ <dt>
+  Source mode toggle</dt>
+ <dd>
+  The source mode toggle button lets you toggle between editing using the WYSIWYG interface and in raw HTML source mode. We <strong>strongly</strong> request that you try to avoid using source mode, as it's very easy to wind up with content that doesn't match our style guide or, worse, doesn't work right at all. Currently, though, the editor has some quirks that make it impossible to do certain things without resorting to source mode.</dd>
+ <dt>
+  Save and keep editing</dt>
+ <dd>
+  A duplicate for the main "Save and keep editing" button.</dd>
+ <dt>
+  Save and exit</dt>
+ <dd>
+  Just like the main "Save changes" button.</dd>
+ <dt>
+  Paste as plain text</dt>
+ <dd>
+  Opens a dialog into which you can paste text; the text has all styling stripped from it so that you don't inadvertently introduce unwanted styles into the site content. Once you've pasted your text, you can (optionally) make changes, then click a button to insert it into the article you're working on.</dd>
+</dl>
+<div class="note">
+ <p><strong>Note:</strong> When pasting content into MDN, please be aware that if pasting styled content (including, for example, syntax highlighting in code being copied from another site) that you may be bringing along unwanted and unneeded additional styles or classes. Please be careful not to do this; if necessary, review your edit in source mode to remove these unnecessary styles and classes (or check it before pasting, or use the "Paste as plain text" option instead).</p>
+</div>
+<dl>
+ <dt>
+  Paste from Word</dt>
+ <dd>
+  On Windows, lets you paste text from Microsoft Word and have it adjusted to work reasonably well in MDN's wiki. We prefer for you to not use this (the results will work but are not typically style guide compliant), but it's there for a few teams that need it.</dd>
+ <dt>
+  Check spelling</dt>
+ <dd>
+  Starts the spell checker.</dd>
+ <dt>
+  Spell check as you type</dt>
+ <dd>
+  Presents a submenu that lets you control and configure the as-you-type spell checker.</dd>
+ <dt>
+  Find</dt>
+ <dd>
+  Opens the Find panel in "Find" mode, which lets you search your document for a specified string.</dd>
+ <dt>
+  Replace</dt>
+ <dd>
+  Opens the Find panel in "Find and replace" mode, allowing you to find strings and replace them with new ones.</dd>
+</dl>
+<p>It's worth noting that the Find and Replace buttons both take you to the same dialog box, which offers several configurable options for finding and optionally replacing text.</p>
+<h3 id="Block-level_options">Block-level options</h3>
+<p>These buttons provide options affecting or creating blocks in your article.</p>
+<dl>
+ <dt>
+  Insert/remove bulleted list</dt>
+ <dd>
+  Creates or removes a bulleted list from your article. Once you're working in a bulleted list, each time you press return, you will start a new bullet. The tab key can be used to indent a level, and shift-tab will outdent a level. Pressing return on an empty bullet will exit bullet list mode. Right-clicking on the list lets you choose to edit the list's properties (specifically, the shapes of the bullets).</dd>
+ <dt>
+  Insert/remove numbered list</dt>
+ <dd>
+  Creates or removes a numbered list from your article. Once you're working in a numbered list, each time you press return, you will start a new bullet. The tab key can be used to indent a level, and shift-tab will outdent a level. Pressing return on an empty bullet will exit numbered list mode. Right-clicking the list offers the option to open the properties dialog for the list; the properties include the style of the numbers (numbers, letters, Roman numerals, etc, and what number to start with).</dd>
+ <dt>
+  Definition list</dt>
+ <dd>
+  Creates a new definition list. Definition lists consist of a series of titles and definitions (this list you're reading right now is an example).</dd>
+ <dt>
+  Definition title</dt>
+ <dd>
+  Creates a new title in a definition list. If you're not already editing a definition list, a new one is created for you. Pressing return after entering a definition title automatically starts you editing a definition description.</dd>
+ <dt>
+  Definition description</dt>
+ <dd>
+  Creates a new description in a definition list. Pressing return on a description line automatically starts a new title. Pressing return twice will exit definition list mode.</dd>
+ <dt>
+  Decrease indent</dt>
+ <dd>
+  Shifts the indentation level to the left once; this is the same as shift-tab while in a list.</dd>
+ <dt>
+  Increase indent</dt>
+ <dd>
+  Shifts the indentation level to the right once; this is the same as tab while in a list.</dd>
+ <dt>
+  Blockquote</dt>
+ <dd>
+  Inserts a blockquote. <strong>Please do not use this</strong>. Blockquotes are not part of our standard style guide, and this button will be removed in the near future.</dd>
+ <dt>
+  Image</dt>
+ <dd>
+  Inserts a new image into the article. See {{anch("Adding images to an article")}} below for details on how to use this option.</dd>
+ <dt>
+  Table</dt>
+ <dd>
+  Inserts a table into the article. See {{anch("Working with tables")}} for more information on tables in articles.</dd>
+ <dt>
+  Text color</dt>
+ <dd>
+  Lets you set the text foreground color. <strong>Please do not use this.</strong> We will switch to using CSS styles for all coloring soon.</dd>
+ <dt>
+  Background color</dt>
+ <dd>
+  Lets you set the text background color. <strong>Please do not use this.</strong> We will switch to using CSS styles for all coloring soon.</dd>
+ <dt>
+  Text direction left-to-right</dt>
+ <dd>
+  Sets LTR as the current text typing direction. Used only when covering localization/internationalization topics.</dd>
+ <dt>
+  Text direction right-to-left</dt>
+ <dd>
+  Sets RTL as the current text typing direction. Used only when covering localization/internationalization topics.</dd>
+</dl>
+<h3 id="Maximize">Maximize</h3>
+<p>This is an odd box, in that it consists of just one button: Maximize. This button causes the editor interface (that is, the toolbar and the edit box) to take over your entire browser window, giving you as much space as possible to write.</p>
+<h3 id="Headings">Headings</h3>
+<p>The heading buttons let you insert a heading. Click one of these buttons to create a new heading at the corresponding depth. By default, H2 through H4 are included in the table of contents, but you can change this, as described in {{anch("The page info box")}}.</p>
+<h3 id="Formatting_styles">Formatting styles</h3>
+<p>The next box is a drop-down menu offering a selection of special formatting options. These are:</p>
+<dl>
+ <dt>
+  None</dt>
+ <dd>
+  Removes all styling from the current block.</dd>
+ <dt>
+  Note box</dt>
+ <dd>
+  Creates a note box, as seen below. You should always start a note box with "<strong>Note:</strong>" in bold letters.</dd>
+</dl>
+<div class="note">
+ <p><strong>Note:</strong> This is a note box.</p>
+</div>
+<dl>
+ <dt>
+  Warning box</dt>
+ <dd>
+  Creates a warning box, as seen below. These should always begin with "<strong>Warning:</strong>" in bold letters.</dd>
+</dl>
+<div class="warning">
+ <p><strong>Warning:</strong> This is a warning box.</p>
+</div>
+<pre class="syntaxbox notranslate">foo = bar()</pre>
+<dl>
+ <dt>
+  Callout box</dt>
+ <dd>
+  Creates a new callout box. We are phasing this kind of box out in favor of a new design, <strong>so it shouldn't be used</strong> for new content.</dd>
+ <dt>
+  Two columns</dt>
+ <dd>
+  Makes the selected text or the current block two columns instead of one, on browsers that support it.</dd>
+ <dt>
+  Three columns</dt>
+ <dd>
+  Makes the selected text or the current block three columns instead of one, on browsers that support it.</dd>
+ <dt>
+  Syntax box</dt>
+ <dd>
+  Creates a syntax box, such as the one shown below. You need to use the "PRE" button as well, to create a {{HTMLElement("pre")}} block inside it. You probably won't see the yellow box until you do.</dd>
+ <dt>
+  Right sidebar</dt>
+ <dd>
+  <div class="standardSidebar" style="text-align: center;">
+   <strong>Special note</strong><br>
+   This is a right sidebar.</div>
+  Creates a light grey sidebar that floats to the right of content. You may enter small amounts of text in these boxes to draw special attention to them.</dd>
+ <dt>
+  SEO summary</dt>
+ <dd>
+  This special style is used to indicate a sentence or two that should be used as the article's summary for SEO purposes. It's also used by macros that automatically construct landing pages. If you don't specify this, MDN automatically uses the first paragraph of your article, but sometimes that's not the optimal text (or it's too much text), so this lets you override that.</dd>
+</dl>
+<h3 id="Code_samples_and_redirects">Code samples and redirects</h3>
+<p>These buttons are mostly used for providing preformatted text (usually code samples), but our "insert redirect" button is, for some reason, here too.</p>
+<dl>
+ <dt>
+  PRE</dt>
+ <dd>
+  Inserts a {{HTMLElement("pre")}} (preformatted text) block, or turns the current block into one. All code samples or examples of text output to a terminal should be in one of these blocks.</dd>
+ <dt>
+  Syntax highlighter</dt>
+ <dd>
+  The syntax highlighter lets you choose a language for which to apply syntax highlighting to the{{HTMLElement("pre")}} (preformatted text) block; if you're not already in such a block, this will create one for you. Simply choose the language and you're good to go.</dd>
+ <dt>
+  Insert code sample template</dt>
+ <dd>
+  This button is used by the live sample system to help you quickly insert a new live sample. You don't need to use it, but it's there for convenience. See {{anch("Using the live sample system")}} for details on using this and other live sample features.</dd>
+ <dt>
+  Insert code sample iframe</dt>
+ <dd>
+  Inserts an {{HTMLElement("iframe")}} into the document, displaying a given live sample. See {{anch("Using the live sample system")}} for details on using this and other live sample features.</dd>
+ <dt>
+  Create a redirect</dt>
+ <dd>
+  Inserts a redirect. See {{anch("Creating redirects")}} for further information.</dd>
+</dl>
+<h3 id="Inline_styles_and_links">Inline styles and links</h3>
+<p>The final group of toolbar buttons includes options for creating and maintaining links and anchors, as well as for applying inline styles to content.</p>
+<dl>
+ <dt>
+  Link</dt>
+ <dd>
+  Creates a new link. This button opens the link editor dialog, which is covered under {{anch("Creating and editing links")}} below.</dd>
+ <dt>
+  Unlink</dt>
+ <dd>
+  Removes the link at the insertion point.</dd>
+ <dt>
+  Anchor</dt>
+ <dd>
+  Creates an anchor at the insertion point.</dd>
+ <dt>
+  Bold</dt>
+ <dd>
+  Toggles boldface text mode.</dd>
+ <dt>
+  Italic</dt>
+ <dd>
+  Toggles italic text mode.</dd>
+ <dt>
+  Underline</dt>
+ <dd>
+  Toggles underlined text mode.</dd>
+ <dt>
+  Code</dt>
+ <dd>
+  Toggles {{HTMLElement("code")}} mode. This is used for inline presentation of variable names, function names, object names, filenames, and so forth.</dd>
+ <dt>
+  Strike through</dt>
+ <dd>
+  Toggles strikethrough mode.</dd>
+ <dt>
+  Superscript</dt>
+ <dd>
+  Toggles superscript mode. Please note that we don't use footnotes on MDN, so you should rarely if ever need this button.</dd>
+ <dt>
+  Remove format</dt>
+ <dd>
+  Removes the current formatting from the selection.</dd>
+ <dt>
+  Align left</dt>
+ <dd>
+  Makes the current block left-aligned. <strong>Please do not use this.</strong> We will be using CSS styles for all alignment tasks starting very soon.</dd>
+ <dt>
+  Center</dt>
+ <dd>
+  Centers the current block. <strong>Please do not use this.</strong> We will be using CSS styles for all alignment tasks starting very soon.</dd>
+ <dt>
+  Align right</dt>
+ <dd>
+  Makes the current block right-aligned. <strong>Please do not use this.</strong> We will be using CSS styles for all alignment tasks starting very soon.</dd>
+</dl>
+<h2 id="The_edit_box">The edit box</h2>
+<p>The edit box is, of course, where you actually do your writing. Right-clicking in the edito box will offer appropriate additional options depending on the context of your click; clicking in a table will offer table-related options and clicking in a list will offer list-related options, for example.</p>
+<h2 id="The_revision_comment_box">The revision comment box</h2>
+<p>After you've made your changes, it's strongly recommended you add a comment to your revision. This is displayed in the revision history for the page, as well as on the <a href="/en-US/dashboards/revisions" title="/en-US/dashboards/revisions">Revision Dashboard</a>. It helps to explain or justify your changes to others that may review your work later. To add a revision comment, simply type the note into the revision comment box before clicking either of the save buttons at the top of the page.</p>
+<div class="note">
+ <p><strong>Note:</strong> We know that the revision comment box being so far away from the save buttons doesn't make any sense. We're working on design changes that will fix that.</p>
+</div>
+<h2 id="The_tags_box">The tags box</h2>
+<p>Page tags help categorize and organize information, and help us identify pages that need special attention. Tags are also used to mark pages that are obsolete and may need to be deprecated or even deleted. It's incredibly useful to have good, clean tags on pages, so be sure to have good tags on articles you contribute to.</p>
+<p>The tag box is near the bottom of the editor page, and looks like this:</p>
+<p><img alt="The tag editing box showing three tags." height="80" src="https://mdn.mozillademos.org/files/5291/tagbox1.png" width="785"></p>
+<h3 id="Adding_a_tag">Adding a tag</h3>
+<p>To add a new tag, simply click in the box and start typing:</p>
+<p><img alt="Screen thot: the tag box after typing a new tag but before pressing Enter." height="74" src="https://mdn.mozillademos.org/files/5293/newtag-beforereturn.png" width="784"></p>
+<p>Here we see the three already existing tags (as button-like objects) and our new tag as unadorned text. When we press <kbd>Enter</kbd> or <kbd>Tab</kbd> key (or comma), the new tag is committed to the list, and the list looks like this:</p>
+<p><img alt="Screen shot: the tag box with our new tag in place." height="81" src="https://mdn.mozillademos.org/files/5295/newtag-afterreturn.png" width="784"></p>
+<p>For a list of recommended tags, as well as a usage guide for specific tags, please see <a href="/en-US/docs/Project:MDN/Contributing/Tagging_standards">MDN tagging standards</a>.</p>
+<h3 id="Removing_a_tag">Removing a tag</h3>
+<p>There are two ways to remove a tag: you can click on the "x" icon next to its name in its button, or you can click to its right in the editor box and press the delete key on your keyboard.</p>
+<h3 id="Committing_your_changes">Committing your changes</h3>
+<p>Your changes are not saved unless you click one of the save buttons at the top of the editor window. Scroll back to the top of the window if you don't see the buttons, then click one of the two green save buttons. Now your change has been committed.</p>
+<h2 id="The_reviews_box">The reviews box</h2>
+<p>MDN uses <strong>reviews</strong> to try to monitor and improve the quality of its content. This works by setting a flag on an article indicating that a review is needed. You can learn more about <a href="/en-US/docs/MDN/Contribute/Howto/Do_a_technical_review" title="/en-US/docs/Project:MDN/Contributing/How_to_help#Content_reviews">technical reviews</a> and <a href="/en-US/docs/MDN/Contribute/Howto/Do_an_editorial_review">editorial review</a> in the <a href="/en-US/docs/MDN/Contribute/Howto" title="/en-US/docs/Project:MDN/Contributing/How_to_help">How to</a> guides.</p>
+<p>To request a review on the article you've worked on, simply toggle on the checkbox next to the type of review that's needed. Technical reviews should be requested any time you make changes to the explanation of how something technical works, while editorial reviews are a good idea when you've made changes and would like someone to review your writing and style choices.</p>
+<p>Be sure to click one of the save buttons after making your selections, to commit your review request.</p>
+<h2 id="The_attachments_box">The attachments box</h2>
+<p>The attachments box lets you upload files to MDN for use in MDN content, as well as see what files are being used by the current document.</p>
+<div class="note">
+ <p><strong>Note:</strong> Due to a quirk in our current implementation, files are not associated with pages unless they're actually used in the page. So if you upload an attachment and don't make use of it before you save the article, it will not appear on the attachments list. So be sure to link to it or embed the image right away.</p>
+</div>
+<p>To add an attachment to the page, simply click the "Attach Files" button; this expands the attachment box to look like this:</p>
+<p><img alt="" src="https://mdn.mozillademos.org/files/5321/attachments-empty.png" style="width: 600px; height: 114px;"></p>
+<p>As you see, there's a table that lets you select a file to upload, then give it a title and, optionally, a description and an additional comment. The title is mandatory, and should describe the file so its usage context is understandable. Once the fields are filled out and you've selected your file, click the "Upload" button to send it to MDN.</p>
+<div class="note">
+ <p><strong>Note:</strong> Only a select few types of files are permitted as attachments on MDN: GIF, JPEG, PNG, SVG, and HTML. Photoshop images are permitted but should be avoided except in very specific cases. Any other file types will not be allowed by the upload form.</p>
+</div>
+<p>Feel free to <a href="/en-US/docs/Project:MDN/Contributing/Editor_guide$edit" title="/en-US/docs/Project:MDN/Contributing/Editor_guide$edit">open this page in the editor</a> and look at its attachment list at the bottom to get a feel for it.</p>
+<p>Once a file has been attached, it will appear (by its title, as you specified in the form) in the image properties dialog box when using images in your article. See {{anch("Adding images to an article")}} for details on this interface. To link to other types of files, copy the URL from the attachments box and use that as your link target when adding links to the page using the link button in the toolbar.</p>
+<h2 id="Keyboard_shortcuts">Keyboard shortcuts</h2>
+<p>There are a number of convenient keyboard shortcuts available to help you avoid taking your hands off the keyboard while you work.  The shortcuts are listed for Windows and Linux; on Mac, instead of using the Control key, you can use the Command key.</p>
+<table class="standard-table" style="max-width: 45em;">
+ <tbody>
+  <tr>
+   <th>Shortcut</th>
+   <th>Description</th>
+  </tr>
+  <tr>
+   <td>Ctrl-A</td>
+   <td>Select all</td>
+  </tr>
+  <tr>
+   <td>Ctrl-C</td>
+   <td>Copy to clipboard</td>
+  </tr>
+  <tr>
+   <td>Ctrl-V</td>
+   <td>Paste from clipboard</td>
+  </tr>
+  <tr>
+   <td>Ctrl-X</td>
+   <td>Cut</td>
+  </tr>
+  <tr>
+   <td>Ctrl-Z</td>
+   <td>Undo</td>
+  </tr>
+  <tr>
+   <td>Ctrl-Y</td>
+   <td>Redo</td>
+  </tr>
+  <tr>
+   <td>Ctrl-K</td>
+   <td>Open link editor</td>
+  </tr>
+  <tr>
+   <td>Ctrl-B</td>
+   <td>Bold</td>
+  </tr>
+  <tr>
+   <td>Ctrl-I</td>
+   <td>Italic</td>
+  </tr>
+  <tr>
+   <td>Ctrl-O</td>
+   <td>Toggle <code>&lt;code&gt;</code> style.</td>
+  </tr>
+  <tr>
+   <td>Ctrl-Shift-O</td>
+   <td>Toggle source view mode.</td>
+  </tr>
+  <tr>
+   <td>Ctrl-P</td>
+   <td>Toggles the <code>&lt;pre&gt;</code> style on the current block.</td>
+  </tr>
+  <tr>
+   <td>Ctrl-U</td>
+   <td>Underline</td>
+  </tr>
+  <tr>
+   <td>Ctrl-S</td>
+   <td>Save changes and close the editor</td>
+  </tr>
+  <tr>
+   <td>Ctrl-Shift-S</td>
+   <td>Save changes without closing the editor</td>
+  </tr>
+  <tr>
+   <td>Ctrl-2 through Ctrl-6</td>
+   <td>Select header level 2-6</td>
+  </tr>
+  <tr>
+   <td>Ctrl-Shift-L</td>
+   <td>Toggles between bulleted list, numbered list, and paragraph format</td>
+  </tr>
+  <tr>
+   <td>Tab</td>
+   <td>Increases indent level if in indent mode, otherwise inserts two spaces as a tab.  Inside tables, this jumps to the next cell, or inserts a new row if there is no next cell.  If the cursor is currently in the page title or in a header, the cursor jumps to the next paragraph.</td>
+  </tr>
+  <tr>
+   <td>Shift-Tab</td>
+   <td>Decreases indent level if in indent mode.  Inside tables, this jumps to the previous cell, or inserts a new row if there is no previous cell.  If the cursor is currently in the page title or in a header, the cursor jumps to the next paragraph.</td>
+  </tr>
+  <tr>
+   <td>Shift-Space</td>
+   <td>Inserts a non-breaking space (<code>&amp;nbsp;</code>)</td>
+  </tr>
+  <tr>
+   <td>Shift-Enter</td>
+   <td>
+    <p>Exits out of the current block.  For example, if you're currently editing a<code> &lt;pre&gt; </code>block, shift-Enter exits the block, putting you back in the body of the article.</p>
+    <div class="note style-wrap">
+     <p><strong>Note:</strong> Not currently implemented; see {{bug(780055)}}.</p>
+    </div>
+   </td>
+  </tr>
+ </tbody>
+</table>
+<h6 id="EditorGuideQuicklinks">{{EditorGuideQuicklinks}}<span id="cke_bm_73C" style="display: none;"> </span></h6>
diff --git a/files/tr/orphaned/mdn/editor/index.html b/files/tr/orphaned/mdn/editor/index.html
new file mode 100644
index 0000000000..99c8d58ea1
--- /dev/null
+++ b/files/tr/orphaned/mdn/editor/index.html
@@ -0,0 +1,13 @@
+---
+title: MDN Düzenleyici Rehberi
+slug: MDN/Editor
+tags:
+  - Landing
+  - MDN
+  - NeedsTranslation
+  - TopicStub
+translation_of: MDN/Editor
+---
+<p>Sayfada düzenleme uygulaması MDN Web dökümanları wiki sayfası, yeni içerik sağlamak için kolaylık sağlar. Bu rehber bu düzenleyiciyi nasıl kullanıp üretim verimliliğinizi nasıl arttıracağınızı gösterecek. Lütfen <a href="https://www.mozilla.org/en-US/about/legal/terms/mozilla/">Mozilla Sözleşmesi</a>ni okuyun herhangi bir düzenleme yapmadan evvel.</p>
+
+<p><a href="https://wiki.developer.mozilla.org/en-US/docs/MDN/Contribute/Content/Style_guide">MDN stil rehberi</a> biçimlendirme ve içeriğin stili konusunda bilgilere sahiptir. Tercih edilen dilbilgisi ve yazım kuralları dahil.</p>
diff --git a/files/tr/orphaned/mdn/kuma/server_charts/index.html b/files/tr/orphaned/mdn/kuma/server_charts/index.html
new file mode 100644
index 0000000000..2b3859dfa9
--- /dev/null
+++ b/files/tr/orphaned/mdn/kuma/server_charts/index.html
@@ -0,0 +1,63 @@
+---
+title: Server charts
+slug: MDN/Kuma/Server_charts
+tags:
+  - Kuma
+  - MDN Meta Türkçe
+translation_of: MDN/Kuma/Server_charts
+---
+<div>{{MDNSidebar}}{{IncludeSubnav("/en-US/docs/MDN")}}</div>
+
+<p class="summary"><span class="seoSummary">This page lists MDN server status charts.</span></p>
+
+<h2 id="Last_30_minutes">Last 30 minutes</h2>
+
+<h3 id="Error_Rate">Error Rate</h3>
+
+<p>{{EmbedNewRelicChart("2fKQPvMkSwU", 300)}}</p>
+
+<p>Kuma web app response time (Average)</p>
+
+<p>{{EmbedNewRelicChart("43yJ3xwUecU", 300)}}</p>
+
+<h3 id="Kuma_web_app_response_time_Percentiles">Kuma web app response time (Percentiles)</h3>
+
+<p>{{EmbedNewRelicChart("6NzEi7ZBdoN", 300)}}</p>
+
+<h2 id="Last_24_Hours">Last 24 Hours</h2>
+
+<h3 id="Error_Rate_2">Error Rate</h3>
+
+<p>{{EmbedNewRelicChart("kVeeXx52g0l", 300)}}</p>
+
+<h3 id="Kuma_web_app_response_time_Average">Kuma web app response time (Average)</h3>
+
+<p>{{EmbedNewRelicChart("2yWkQ9WbEZW", 300)}}</p>
+
+<h3 id="Kuma_web_app_response_time_Percentiles_2">Kuma web app response time (Percentiles)</h3>
+
+<p>{{EmbedNewRelicChart("aeFnbLonmvx", 300)}}</p>
+
+<h2 id="Last_3_Days">Last 3 Days</h2>
+
+<h3 id="Error_Rate_3">Error Rate</h3>
+
+<p>{{ EmbedNewRelicChart("iv2F4gQYjFX", 300)}}</p>
+
+<h3 id="Kuma_web_app_response_time_Average_2">Kuma web app response time (Average)</h3>
+
+<p>{{EmbedNewRelicChart("ddTq7AKgyaG", 300)}}</p>
+
+<h3 id="Kuma_web_app_response_time_Percentiles_3">Kuma web app response time (Percentiles)</h3>
+
+<p>{{EmbedNewRelicChart("bRmyM6ujKA8", 300)}}</p>
+
+<h2 id="Last_3_Months">Last 3 Months</h2>
+
+<h3 id="Error_Rate_4">Error Rate</h3>
+
+<p>{{EmbedNewRelicChart("fjJ7HnGYNLd", 300)}}</p>
+
+<h3 id="Kuma_web_app_response_time_Average_3">Kuma web app response time (Average)</h3>
+
+<p>{{EmbedNewRelicChart("sIaVOeAxNx", 300)}}</p>
diff --git a/files/tr/orphaned/mdn/tools/page_watching/index.html b/files/tr/orphaned/mdn/tools/page_watching/index.html
new file mode 100644
index 0000000000..4df3df166a
--- /dev/null
+++ b/files/tr/orphaned/mdn/tools/page_watching/index.html
@@ -0,0 +1,44 @@
+---
+title: Watch or subscribe to a page or set of pages
+slug: MDN/Tools/Page_watching
+translation_of: MDN/Tools/Page_watching
+---
+<div><font><font>{{MDNSidebar}}</font></font></div>
+
+<p><span class="seoSummary"><font><font>MDN'deki bir sayfaya abone olmak, her güncellendiğinde veya değiştirildiğinde e-postayla bilgilendirilmenizi sağlar. </font></font></span><font><font>İzle düğmesi her MDN sayfasının sağ üst köşesinde bulunur. </font><font>Abonelik seçeneklerine erişmek için, imleci İzleme menüsünü açıklamak için İzle düğmesinin üzerine getirin:</font></font></p>
+
+<p><img alt="MDN's Watch menüsünün ekran görüntüsü" src="https://mdn.mozillademos.org/files/12551/MDN_-_Watch_Menu.png" style="border-style: solid; border-width: 1px; display: block; height: 298px; margin: 0 auto; width: 463px;"></p>
+
+<p><font><font>Yalnızca bir sayfayı veya o sayfayı ve alt sayfalarını izlemek için bir seçenek belirleyin.</font></font></p>
+
+<h2 id="Bir_sayfaya_abone_olun"><font><font>Bir sayfaya abone olun</font></font></h2>
+
+<p><font><font>Bir kullanıcı yalnızca bir sayfayı her düzenlediğinde bir e-posta bildirimi almak </font><font>için ilk " </font></font><em><font><font>Sayfa Başlığına</font></font></em><font><font> Abone Ol" seçeneğini tıklayın </font><font>.</font></font></p>
+
+<h2 id="Bir_sayfaya_ve_tüm_alt_makalelerine_abone_olun"><font><font>Bir sayfaya ve tüm alt makalelerine abone olun</font></font></h2>
+
+<p><font><font>Bir kullanıcı o sayfayı ve alt sayfalarını her düzenlediğinde bir e-posta bildirimi almak </font><font>için ikinci " </font></font><em><font><font>Sayfa Başlığına</font></font></em><font><font> ve tüm alt makalelerine </font><font>abone ol" seçeneğini tıklayın </font><font>. </font><font>Buna abonelik talebinde bulunulduktan sonra eklenen alt sayfalar da dahildir, bu nedenle gelecekte daha fazla alt sayfa oluşturulacaksa, bunlar için de bildirim alırsınız.</font></font></p>
+
+<h2 id="Bir_sayfadan_aboneliği_iptal_et"><font><font>Bir sayfadan aboneliği iptal et</font></font></h2>
+
+<p><font><font>Aboneliği iptal etmek ve bir sayfayı izlemeyi durdurmak için, İzleme menüsünü tekrar açın ve " </font></font><em><font><font>Sayfa Başlığından</font></font></em><font><font> Aboneliği İptal </font><em><font>Et</font></em><font> " i tıklayın. </font><font>" </font></font><em><font><font>Sayfa Başlığından</font></font></em><font><font> Aboneliği İptal Et" i yalnızca </font><font>bir sayfaya abone olursanız görürsünüz. </font><font>Artık sayfa her değiştiğinde bir e-posta almayacaksınız.</font></font></p>
+
+<h2 id="Sayfa_değişikliği_e-postaları"><font><font>Sayfa değişikliği e-postaları</font></font></h2>
+
+<p><font><font>Bir sayfaya abone olursanız, her değişiklik kaydedişinde bir e-posta alırsınız. </font><font>Bu e-postalar notifications@developer.mozilla.org adresinden gelir ve MDN hesabınıza kayıtlı e-posta adresine gönderilir. </font><font>Her mesajın bir başlığı vardır:</font></font></p>
+
+<pre class="notranslate"><font><font>[MDN] Sayfa " </font></font><em><font><font>Sayfa başlığı</font></font></em><font><font> " </font><em><font>kullanıcı adına</font></em><font> göre değişti</font></font></pre>
+
+<p><font><font>İleti, başlıktaki bilgilerin tekrarlanmasıyla başlar, ardından içeriğin tam olarak neyin değiştiğini gösteren standart bir farkını sunar. </font><font>Değişiklikler, HTML kaynak kodu olarak gösterilir; bu, MDN bağlamında kullanılmazsa okunması biraz garip olabilir.</font></font></p>
+
+<p><font><font>Farkın altında, değişiklik üzerinde hareket etmek için kullanabileceğiniz faydalı bağlantıların bir listesi vardır:</font></font></p>
+
+<ul>
+ <li><font><font>Değişikliği yapan kullanıcının MDN profilini görüntüleme</font></font></li>
+ <li><font><font>MDN'nin yerinde geçmiş özelliğini kullanarak sayfanın önceki ve yeni sürümlerini karşılaştırın</font></font></li>
+ <li><font><font>Makalenin kendisini tarayıcınızda görüntüleyin</font></font></li>
+ <li><font><font>Makaleyi düzenleyin</font></font></li>
+ <li><font><font>Makalenin geçmişine bakın</font></font></li>
+</ul>
+
+<p><font><font>E-postanın altında, e-postayı hangi aboneliğin oluşturduğunu belirten bir bildirim bulunur, örneğin "HTML öğesi başvurusu ve tüm alt makaleleri üzerinde düzenlemelere abone oldunuz" ve abonelikten çıkma bağlantısı. </font><font>Aboneliği iptal etmek için bağlantıyı tıklatırsanız, bu izleme isteği için artık ileti almayacaksınız.</font></font></p>
diff --git a/files/tr/orphaned/mozilla/add-ons/webextensions/getting_started_with_web-ext/index.html b/files/tr/orphaned/mozilla/add-ons/webextensions/getting_started_with_web-ext/index.html
new file mode 100644
index 0000000000..810b551b81
--- /dev/null
+++ b/files/tr/orphaned/mozilla/add-ons/webextensions/getting_started_with_web-ext/index.html
@@ -0,0 +1,335 @@
+---
+title: Deneyiminize web-ext ile başlayın
+slug: Mozilla/Eklentiler/WebExtensions/Deneyiminize_web-ext_ile_başlayın
+translation_of: Mozilla/Add-ons/WebExtensions/Getting_started_with_web-ext
+---
+<div>{{AddonSidebar}}</div>
+
+<p class="summary">Web-ext bir komut satır aracı olmakla birlikte uygulamaların gelistirmesinde kısmen yardımcı olup bu süreci kolaylaştırmaktadır. Bu Makale web-ext'in yüklenmesi ve çalıştırılması hakkında bilgiler içermektedir.</p>
+
+<h2 id="Installation">Installation</h2>
+
+<p><code>web-ext</code> bir node.js bazlı (açık kaynaklı, işlem bazlı ve ölçeklenebilir) uygulama olup <a href="https://nodejs.org/">nodejs/npm</a> aracı ile yükleyebilirsiniz. Web-ext'in yüklenmesi için kullanılması gereken komut:</p>
+
+<pre class="brush: bash"><code>npm install --global web-ext</code></pre>
+
+<p><code>web-ext</code> requires the current <a href="https://github.com/nodejs/Release#release-schedule">LTS</a> (long-term support) version of <a href="https://nodejs.org/">NodeJS</a>.</p>
+
+<p>To test whether the installation worked run the following command, which displays the <code>web-ext</code> version number:</p>
+
+<pre class="brush: bash"><code>web-ext --version</code></pre>
+
+<h2 id="Using_web-ext">Using web-ext</h2>
+
+<p>Before you start using <code>web-ext</code> locate an example extension to use—if you don't have one, use one from the <a href="https://github.com/mdn/webextensions-examples">webextensions-examples</a> repo.</p>
+
+<h3 id="Testing_out_an_extension">Testing out an extension</h3>
+
+<p>Test an extension in Firefox by <code>cd</code>'ing into your extension's root directory and entering:</p>
+
+<pre class="brush: bash"><code>web-ext run</code></pre>
+
+<p>This starts Firefox and loads the extension temporarily in the browser, just as you can on the <a href="/en-US/docs/Tools/about:debugging#Add-ons">about:debugging page</a>. Note that this <code>web-ext</code> method has the same <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Temporary_Installation_in_Firefox#Limitations">limitations regarding prompts for permissions and restart features</a> as about:debugging.</p>
+
+<p>See the <a href="/en-US/Add-ons/WebExtensions/web-ext_command_reference#web-ext_run">run reference guide</a> to learn more.</p>
+
+<h3 id="Automatic_extension_reloading">Automatic extension reloading</h3>
+
+<p>The <code>run</code> command watches your source files and tells Firefox to reload the extension after you edit and save a file. For example, if you changed the <code>name</code> property in your <code>manifest.json</code> file, Firefox displays the new name. This makes it easy to try out new features because you can see the effect immediately. The automatic reloading feature is active by default, you use it like this:</p>
+
+<pre class="brush: bash"><code>web-ext run</code></pre>
+
+<p>You can also press the <code>r</code> key in the <code>web-ext</code> terminal to trigger an extension reload.</p>
+
+<p>If you experience unexpected behavior with the reloading feature, please <a href="https://github.com/mozilla/web-ext/issues">file a bug</a>. You can also disable reloading like this:</p>
+
+<pre class="brush: bash"><code>web-ext run --no-reload</code></pre>
+
+<div class="note">
+<p>Extension reloading is only supported in Firefox 49 or higher.</p>
+</div>
+
+<h3 id="Testing_in_different_versions_of_Firefox">Testing in different versions of Firefox</h3>
+
+<p>To run your extension in a version of <a href="https://www.mozilla.org/en-US/firefox/">Firefox Desktop</a> other than the default, use the <code>--firefox</code> option to specify a full path to the binary file. Here is an example for Mac OS:</p>
+
+<pre class="brush: bash">web-ext run --firefox=/Applications/FirefoxNightly.app/Contents/MacOS/firefox-bin</pre>
+
+<p>On Windows, the path needs to include <code>firefox.exe</code>, for example:</p>
+
+<pre class="brush: bash">web-ext run --firefox="C:\Program Files\Mozilla Firefox\firefox.exe"</pre>
+
+<p>See the <a href="/en-US/Add-ons/WebExtensions/web-ext_command_reference#web-ext_run">run command</a> reference to learn more.</p>
+
+<h3 id="Testing_in_Firefox_48">Testing in Firefox 48</h3>
+
+<p>Firefox 48 was the first stable version to use the WebExtension platform, but it doesn't allow <code>web-ext</code> to install an extension remotely. You need to run your extension in Firefox 48 using:</p>
+
+<pre class="brush: bash">web-ext run --pre-install</pre>
+
+<h3 id="Testing_in_Firefox_for_Android">Testing in Firefox for Android</h3>
+
+<p>To run your extension in <a href="https://www.mozilla.org/en-US/firefox/mobile/">Firefox for Android</a>, follow these instructions to <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Developing_WebExtensions_for_Firefox_for_Android#Set_up_your_computer_and_Android_emulator_or_device">set up your computer and device</a>.</p>
+
+<p>With your device connected to your development computer, run:</p>
+
+<pre class="brush: bash">web-ext run --target=firefox-android</pre>
+
+<p>This command displays the device ID for your connected Android device or devices. If you don't see a list of device IDs, make sure you set up the device for development correctly.</p>
+
+<p><span style="background-color: #ffffff;">N</span>ow, add the device ID to the command:</p>
+
+<pre class="brush: bash">web-ext run --target=firefox-android --android-device=&lt;device ID&gt;</pre>
+
+<p>If you've multiple versions of Firefox installed, you may need to choose a specific version. For example:</p>
+
+<pre class="brush: bash">web-ext run --target=firefox-android ... --firefox-apk=org.mozilla.firefox</pre>
+
+<p>The first time you run this command, you may need to grant Android permissions for the APK. This is because the command needs read/write access to the device storage, so that Firefox for Android can run on a temporary profile. The <code>web-ext</code> output guides you in how to grant these permissions.</p>
+
+<p>The <code>web-ext</code> command does not alter any of your existing Firefox for Android preferences or data. To see more information about how <code>web-ext</code> is interacting with your device, run the command with <code>--verbose</code>.</p>
+
+<p>See the <a href="/en-US/Add-ons/WebExtensions/web-ext_command_reference#web-ext_run">run command</a> reference to learn more.</p>
+
+<h3 id="Debugging_in_Firefox_for_Android">Debugging in Firefox for Android</h3>
+
+<p>When using <code>web-ext run</code> to test an extension on Firefox for Android, you'll notice a message like this in the console output:</p>
+
+<pre>You can connect to this Android device on TCP port 51499
+</pre>
+
+<p>This is a remote debugger port that you can <a href="/en-US/docs/Tools/Remote_Debugging/Firefox_for_Android#Connecting">connect to with Firefox's developer tools</a>. In this case, you'd connect to host <code>localhost</code> on port <code>51499</code>.</p>
+
+<p>See <a href="/en-US/Add-ons/WebExtensions/Developing_WebExtensions_for_Firefox_for_Android#Debug_your_extension">this guide</a> for more information about debugging an extension on Firefox for Android.</p>
+
+<h3 id="Testing_unsigned_extensions">Testing unsigned extensions</h3>
+
+<p>When you execute <a href="/en-US/Add-ons/WebExtensions/web-ext_command_reference#web-ext_run">web-ext run</a>, the extension gets installed temporarily until you close Firefox. This does not violate any signing restrictions. If instead you create a zip file with <a href="/en-US/Add-ons/WebExtensions/web-ext_command_reference#web-ext_build">web-ext build</a> and try to install it into Firefox, you will see an error telling you that the add-on is not signed. You will need to use an <a href="https://wiki.mozilla.org/Addons/Extension_Signing#Unbranded_Builds">unbranded build</a> or use a <a href="https://www.mozilla.org/en-US/firefox/developer/">development build</a> to install unsigned extensions.</p>
+
+<h3 id="Using_a_custom_profile">Using a custom profile</h3>
+
+<p>By default, the <code>run</code> command will create a temporary Firefox profile. To run your extension with a specific profile use the <code>--firefox-profile</code> option, like this:</p>
+
+<pre class="brush: bash">web-ext run --firefox-profile=your-custom-profile</pre>
+
+<p>This option accepts a string containing the name of your profile or an absolute path to the profile directory. This is helpful if you want to manually configure some settings that will always be available to the <code>run</code> command.</p>
+
+<h3 id="Keeping_profile_changes">Keeping profile changes</h3>
+
+<p>The <code>run</code> command does not save any changes made to the custom profile specified by <code>--firefox-profile</code>. To keep changes, add this option:</p>
+
+<pre class="brush: bash">web-ext run --keep-profile-changes --firefox-profile=your-custom-profile</pre>
+
+<p>This may be helpful if your extension has many different run states.</p>
+
+<div class="warning">
+<p>This option makes the profile specified by <code>--firefox-profile</code> completely insecure for daily use. It turns off auto-updates and allows silent remote connections, among other things. Specifically, it will make destructive changes to the profile that are required for <code>web-ext</code> to operate.</p>
+</div>
+
+<h3 id="Packaging_your_extension">Packaging your extension</h3>
+
+<p>Once you've tested your extension and verified that it's working, you can turn it into a package for submitting to <a href="https://addons.mozilla.org">addons.mozilla.org</a> using the following command:</p>
+
+<pre class="brush: bash"><code>web-ext build</code></pre>
+
+<p>This outputs a full path to the generated <code>.zip</code> file that can be loaded into a browser.</p>
+
+<div class="warning">
+<p>The generated <code>.zip</code> file doesn't work on Firefox without signing or adding <code><a href="/en-US/Add-ons/WebExtensions/manifest.json/applications">applications</a>.gecko.id</code> key into <code><a href="/en-US/Add-ons/WebExtensions/manifest.json">manifest.json</a></code>.  For more information, please refer <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/WebExtensions_and_the_Add-on_ID">WebExtensions and the Add-on ID</a> page.</p>
+</div>
+
+<p><code>web-ext build</code> is designed to ignore files that are commonly not wanted in packages, such as <code>.git</code>, <code>node_modules</code>, and other artifacts.</p>
+
+<p>See the <a href="/en-US/Add-ons/WebExtensions/web-ext_command_reference#web-ext_build">build reference guide</a> to learn more.</p>
+
+<h3 id="Signing_your_extension_for_self-distribution">Signing your extension for self-distribution</h3>
+
+<p>As an alternative to publishing your extension on <a href="https://addons.mozilla.org/">addons.mozilla.org</a>, you can self-host your package file but it needs to be <a href="https://developer.mozilla.org/Add-ons/Distribution">signed by Mozilla</a> first. The following command packages and signs a ZIP file, then returns it as a signed XPI file for distribution:</p>
+
+<pre class="brush: bash"><code>web-ext sign --api-key=$AMO_JWT_ISSUER --api-secret=$AMO_JWT_SECRET </code></pre>
+
+<p>The API options are required to specify your <a href="https://addons.mozilla.org/en-US/developers/addon/api/key/">addons.mozilla.org credentials</a>.</p>
+
+<ul>
+ <li><code>--api-key</code>: the API key (JWT issuer) from <code>addons.mozilla.org</code> needed to sign the extension. This is a string that will look something like <code>user:12345:67</code>.</li>
+ <li><code>--api-secret</code>: the API secret (JWT secret) from <code>addons.mozilla.org</code> needed to sign the extension. This is a string that will look something like <code>634f34bee43611d2f3c0fd8c06220ac780cff681a578092001183ab62c04e009</code>.</li>
+</ul>
+
+<div class="blockIndicator warning">
+<p>If you've <a href="/en-US/docs/Mozilla/Add-ons/Distribution/Submitting_an_add-on">listed</a> the extension on <a href="https://addons.mozilla.org">addons.mozilla.org</a>, see <a href="#Signing_a_test_version_of_a_listed_extension">Signing a test version of a listed extension</a>.</p>
+</div>
+
+<p>See the <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/web-ext_command_reference#web-ext_sign">sign reference guide</a> to learn more.</p>
+
+<h3 id="Signing_extensions_without_an_explicit_ID">Signing extensions without an explicit ID</h3>
+
+<p><code>web-ext</code> supports signing extensions that do not declare the <a href="/en-US/Add-ons/WebExtensions/manifest.json/applications">applications.gecko.id</a> property in their manifest. The first time you sign an extension without an explicit ID, <a href="https://addons.mozilla.org/">addons.mozilla.org</a> will generate an ID and <code>web-ext</code> will save it to <code>.web-extension-id</code> in the working directory. You should save the ID file so that you can sign future versions of the same extension. If you lose the ID file, you will have to add back the <code>applications.gecko.id</code> property or use the <code>--id</code> option when signing, for example:</p>
+
+<pre class="brush: bash"><code>web-ext sign --api-key=... --api-secret=... --id="</code>{c23c69a7-f889-447c-9d6b-7694be8035bc}<code>"</code></pre>
+
+<h3 id="Signing_in_a_restricted_environment">Signing in a restricted environment</h3>
+
+<p>If you're working in an environment that restricts access to certain domains, you can try using a proxy when signing:</p>
+
+<pre class="brush: bash"><code>web-ext sign --api-key=... --api-secret=... --api-proxy=https://yourproxy:6000</code></pre>
+
+<p>See the <a href="/en-US/Add-ons/WebExtensions/web-ext_command_reference#--api-proxy">--api-proxy</a> option to learn more.</p>
+
+<p>The following domains are used for signing and downloading files:</p>
+
+<ul>
+ <li><code>addons.mozilla.org</code></li>
+ <li><code>addons.cdn.mozilla.net</code></li>
+</ul>
+
+<h3 id="Signing_a_test_version_of_a_listed_extension">Signing a test version of a listed extension</h3>
+
+<p>If you've <a href="/en-US/docs/Mozilla/Add-ons/Distribution/Submitting_an_add-on">listed</a> an extension on <a href="https://addons.mozilla.org">addons.mozilla.org</a>, use <code>web-ext</code> to create a signed but <a href="/en-US/docs/Mozilla/Add-ons/Distribution/Submitting_an_add-on#Self-distribution">unlisted</a> version for testing purposes. For example, you may wish to distribute an alpha or beta version to users for early feedback and testing.</p>
+
+<p>First, change the version number in your <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json">manifest.json</a> so that it is different from the latest listed version. Then, create the unlisted version by using the <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/web-ext_command_reference#web-ext_sign">--channel</a></code> option like this:</p>
+
+<pre class="brush: bash">web-ext sign --channel=unlisted --api-key=... --api-secret=...</pre>
+
+<p>This signs and downloads an XPI file that can be installed into Firefox.</p>
+
+<p>Once you've finished testing, <strong>to publish the extension you must define</strong> <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/web-ext_command_reference#web-ext_sign">--channel</a></code><strong> as listed</strong>, as the channel option defaults to the one used previously. So, after incrementing the version in your <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json">manifest.json</a>, run:</p>
+
+<pre class="brush: bash">web-ext sign --channel=listed --api-key=... --api-secret=...</pre>
+
+<p>This publishes and submits your extension for review as if you had uploaded it to <a href="https://addons.mozilla.org">addons.mozilla.org</a>.</p>
+
+<div class="warning">
+<p>Setting <code>--channel=listed</code> for a new version of a listed extension is not well supported. It uploads your new version to <a class="external external-icon" href="https://addons.mozilla.org" rel="noopener">addons.mozilla.org</a> as if you'd <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Distribution/Submitting_an_add-on">submitted it manually</a>. However, the command will fail and you'll have to check <a href="https://addons.mozilla.org/developers/addons">addons.mozilla.org/developers/addons</a> for the correct status.</p>
+</div>
+
+<p>See the <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/web-ext_command_reference#web-ext_sign">sign reference guide</a> to learn more.</p>
+
+<h3 id="Checking_for_code_lint">Checking for code "lint"</h3>
+
+<p>Before trying out your extension with the <a href="/en-US/Add-ons/WebExtensions/web-ext_command_reference#web-ext_run">run</a> command or submitting your package to <a href="https://addons.mozilla.org/en-US/firefox/">addons.mozilla.org</a>, use the <code>lint</code> command to make sure your <a href="/en-US/Add-ons/WebExtensions/manifest.json">manifest</a> and other source files do not contain any errors. You can also set <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/browser_specific_settings">strict_min_version</a> in your extension’s manifest file and lint will report on the permissions, manifest keys, and web extension APIs used that are not available in that version. Example:</p>
+
+<pre class="brush: bash">web-ext lint</pre>
+
+<p>This uses the <a href="https://github.com/mozilla/addons-linter">addons-linter</a> library to walk through your source code directory and report any errors, such as the declaration of an unknown permission.</p>
+
+<p>See the <a href="/en-US/Add-ons/WebExtensions/web-ext_command_reference#web-ext_lint">lint reference guide</a> to learn more.</p>
+
+<h3 id="Setting_option_defaults_in_a_configuration_file">Setting option defaults in a configuration file</h3>
+
+<p>You can specify <code>--config=my-config.js</code> to set default values for any option. Here is an example with the <code>build</code> command:</p>
+
+<pre class="brush: bash">web-ext --config=my-config.js build</pre>
+
+<p>The file should be a CommonJS module <a href="https://nodejs.org/docs/latest/api/modules.html#modules_modules">as understood by NodeJS</a> and must export each configuration value. Here is how you would set the default value of <a href="/en-US/Add-ons/WebExtensions/web-ext_command_reference#--verbose_-v">--verbose</a> to <code>true</code>:</p>
+
+<pre class="brush: javascript">module.exports = {
+  verbose: true,
+};</pre>
+
+<p>If you want to specify options that only apply to a specific command, you nest the configuration under the command name. Here is an example of adding configuration for <a href="/en-US/Add-ons/WebExtensions/web-ext_command_reference#--overwrite-dest_-o">--overwrite-dest</a> that only applies to the <code>build</code> command as well as <a href="/en-US/Add-ons/WebExtensions/web-ext_command_reference#--firefox_-f">--firefox</a> that only applies to the <code>run</code> command:</p>
+
+<pre class="brush: javascript">module.exports = {
+  // Global options:
+  verbose: true,
+  // Command options:
+  build: {
+    overwriteDest: true,
+  },
+  run: {
+    firefox: 'nightly',
+  },
+};</pre>
+
+<p>To create a configuration key for a command line option, you remove the preceding dashes and convert the name to camel case. As you can see from this example, <code>--overwrite-dest</code> was converted to <code>overwriteDest</code>.</p>
+
+<p>If an option can be specified multiple times on the command line then you define it as an array. For example, here is how to specify multiple <a href="/en-US/Add-ons/WebExtensions/web-ext_command_reference#--ignore-files_-i">--ignore-files</a> patterns:</p>
+
+<pre class="brush: javascript">module.exports = {
+  ignoreFiles: [
+    'package-lock.json',
+    'yarn.lock',
+  ],
+};</pre>
+
+<p><code>web-ext</code> will also try to load its configuration options from a <code>"webExt"</code> property included in the <code>package.json</code> file in the current directory:</p>
+
+<pre>{
+  "name": "an-extension-src-dir-with-a-package-json",
+  "version": "1.0.0",
+  ...
+  "webExt": {
+    <span class="blob-code-inner blob-code-marker-addition"><span class="pl-s">"sourceDir": "dist/extension/"</span></span>
+  }
+}
+</pre>
+
+<h3 id="Automatic_discovery_of_configuration_files">Automatic discovery of configuration files</h3>
+
+<p><code>web-ext</code> will load existing configuration files in the following order:</p>
+
+<ul>
+ <li>A config file named <code>.web-ext-config.js</code> in your home directory, for example:
+
+  <ul>
+   <li>On Windows: <code>C:\Users\&lt;username&gt;\.web-ext-config.js</code></li>
+   <li>On macOS: <code>/Users/&lt;username&gt;/.web-ext-config.js</code></li>
+   <li>On Linux: <code>/home/&lt;username&gt;/.web-ext-config.js</code></li>
+  </ul>
+ </li>
+ <li>A config property named <code>"webExt"</code> included in a <code>package.json</code> file in the current directory.</li>
+ <li>A config file named <code>web-ext-config.js</code> in the current directory.</li>
+</ul>
+
+<p>If a home directory config and a local directory config define the same option, the value from the latter file will be used.</p>
+
+<p>To disable automatic loading of configuration files, set this option:</p>
+
+<pre class="brush: bash">web-ext --no-config-discovery run</pre>
+
+<p>To diagnose an issue related to config files, re-run your command with <code>--verbose</code>. This will tell you which config file affected which option value.</p>
+
+<h3 id="Specifying_different_source_and_destination_directories">Specifying different source and destination directories</h3>
+
+<p>The preceding commands use default directories for the extension source and artifact creation (for example, built <code>.zip</code> files). The defaults are:</p>
+
+<ul>
+ <li>Source: The directory you are in.</li>
+ <li>Artifacts: A directory called <code>./web-ext-artifacts</code>, created inside the current directory.</li>
+</ul>
+
+<p>You can specify different source and destination directories using the <code>--source-dir</code> and <code>--artifacts-dir</code> options when running your commands. Their values can be relative or absolute paths, but must always be specified as strings. Here is an example of specifying both options when building an extension:</p>
+
+<pre class="brush: bash"><code>web-ext build --source-dir=webextension-examples/notify-link-clicks-i18n --artifacts-dir=zips</code></pre>
+
+<h3 id="Outputting_verbose_messages">Outputting verbose messages</h3>
+
+<p>To see in detail what web-ext is doing when you run a command, include the <code>--verbose</code> option. For example:</p>
+
+<pre class="brush: bash"><code>web-ext build --verbose</code></pre>
+
+<h3 id="Viewing_all_commands_and_options">Viewing all commands and options</h3>
+
+<p>You can list all commands and options like this:</p>
+
+<pre class="brush: bash"><code>web-ext --help</code></pre>
+
+<p>You can list options for a specific command by adding it as an argument:</p>
+
+<pre class="brush: bash"><code>web-ext --help run</code></pre>
+
+<h3 id="Detecting_temporary_installation">Detecting temporary installation</h3>
+
+<p>Your extension can detect whether it was installed using <code>web-ext run</code>, rather than as a built and signed extension downloaded from <code>addons.mozilla.org</code>. Listen for the {{WebExtAPIRef("runtime.onInstalled")}} event and check the value of <code>details.temporary</code>.</p>
+
+<h3 id="Using_web-ext_from_a_script">Using web-ext from a script</h3>
+
+<p>You can use <code>web-ext</code> as a <code>NodeJS</code> module. Here is <a href="https://github.com/mozilla/web-ext#using-web-ext-in-nodejs-code">more information</a>, with example code.</p>
+
+<h2 id="See_also">See also</h2>
+
+<ul>
+ <li><a class="external external-icon" href="https://github.com/mozilla/web-ext">web-ext repo</a></li>
+ <li>
+  <p><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/web-ext_command_reference">web-ext command reference</a></p>
+ </li>
+</ul>
diff --git a/files/tr/orphaned/tr/index.html b/files/tr/orphaned/tr/index.html
new file mode 100644
index 0000000000..3ad0ab9038
--- /dev/null
+++ b/files/tr/orphaned/tr/index.html
@@ -0,0 +1,63 @@
+---
+title: Mozilla Geliştirici Ağı
+slug: Tr
+tags:
+  - MDC
+  - Mozilla Developer Center
+  - mdc turkey
+  - mdc türkiye
+  - mgm
+  - mozilla geliştirici merkezi
+---
+<h4 id="Firefox_Mobile_-_Android_sürümü_yayınlandı._Test_Etmek_isterseniz_buraya_tıklayınız."><img alt="logo-only-250x250.png" class="internal default" src="/@api/deki/files/4193/=logo-only-250x250.png" style="width: 100px; height: 100px;">Firefox Mobile - Android sürümü yayınlandı. Test Etmek isterseniz <a class="external" href="http://www.mozilla.com/en-US/firefox/beta/" title="http://www.mozilla.com/en-US/firefox/beta/">buraya tıklayınız.</a></h4>
+<p><strong>Firefox 9(veya son çıkan beta) sürümünü test etmek isterseniz <a class="external" href="http://www.mozilla.com/en-US/firefox/all-beta.html" title="http://www.mozilla.com/en-US/firefox/all-beta.html">buraya tıklayınız.</a></strong></p>
+<h4 id="Son_sürümünü_şimdi_indirmek_için_buraya_tıklayınız._Web_uygulama_geliştiricileri_ve_web_tasarımcıları_için_Firefox_5_geliştirici_sürümüne_buradan_erişebilirsiniz.EN_Yeni_Firefox_için_75.000_fazla_temaya_buradan_ulaşabilirsiniz."> Son sürümünü şimdi indirmek için <a class="external" href="http://www.mozilla-europe.org/tr/" title="http://www.mozilla-europe.org/tr/">buraya tıklayınız.</a> Web uygulama geliştiricileri ve web tasarımcıları için Firefox 5 geliştirici sürümüne <a class="external" href="/en/Firefox_5_for_developers" title="https://developer.mozilla.org/en/Firefox_for_developers">buradan</a> erişebilirsiniz.[EN] Yeni Firefox için 75.000+ fazla temaya <a class="external" href="http://www.getpersonas.com" title="http://www.getpersonas.com">buradan ulaşabilirsiniz.</a></h4>
+<div class="geckoVersionNote" style="padding: 10px;">
+ Web Tarayıcıları 2012 anketine katılarak Firefox'un tanıtılmasına yardımcı olabilirsiniz. <a class="external" href="http://bit.ly/ar5OoR" title="http://bit.ly/ar5OoR"><span class="external">Buraya tıklayarak oylamaya katılabilirsiniz.</span></a></div>
+<hr>
+<h2 id="Thunderbird_3_ile_e-postalarınıza_daha_çok_hükmedin!"><a class="external" href="http://tr.www.mozillamessaging.com/tr/thunderbird/" title="Thunderbird 3 İndir"><img alt="download-button-primary.png" class="internal default" src="/@api/deki/files/4194/=download-button-primary.png?size=webview" style="width: 350px; height: 132px;"></a> Thunderbird 3 ile e-postalarınıza daha çok hükmedin!</h2>
+<h2 id="Mobil_Firefox_ile_her_yerde_hızlı_ve_güvenli_internetin_tadını_çıkarın."><a href="/Tr/Fennec_(Firefox_Mobile)" title="Tr/Fennec (Firefox Mobile)"><img alt="fennec_logo.png" class="internal default" src="/@api/deki/files/4246/=fennec_logo.png" style="width: 339px; height: 147px;"></a>Mobil Firefox ile her yerde hızlı ve güvenli internetin tadını çıkarın.</h2>
+<table class="mainpage-table">
+ <tbody>
+  <tr>
+   <td colspan="2">
+    <h2 id="Geliştirme_Konuları">Geliştirme Konuları</h2>
+   </td>
+  </tr>
+  <tr>
+   <td>
+    <dl>
+     <dt>
+      <a class="internal" href="/en/Web_Development" title="En/Web Development">Web geliştirme</a></dt>
+     <dd>
+      Kılavuzlar ve referanslar ile yararlı web siteleri ve web uygulamaları geliştirebilirsiniz.</dd>
+     <dt>
+      <a class="internal" href="/En/Participating_in_the_Mozilla_project" title="En/Participating in the Mozilla project">Mozilla projesine katılmak</a></dt>
+     <dd>
+      Mozilla kodlarını derlemek, geliştirici kılavuzu, hata raporlama, yerelleştirme kılavuzu ve Mozilla projelerine katkı sağlamak adına öğrenebileceğiniz herşey burada yer almaktadır.</dd>
+     <dt>
+       </dt>
+     <dt>
+       </dt>
+    </dl>
+   </td>
+   <td>
+    <dl>
+     <dt>
+      <a class="internal" href="/En/Developing_add-ons" title="en/Developing add-ons">Eklenti Geliştirme</a></dt>
+     <dd>
+      Firefox ve Thunderbird uygulamalarına tema,eklenti geliştirmek isterseniz, işinize yarayacak kaynaklar burada yer almaktadır.</dd>
+     <dt>
+      <a class="internal" href="/En/Using_Mozilla_code_in_other_projects" title="En/Using Mozilla code in other projects">Mozilla kodlarını diğer projelerde kullanımı</a></dt>
+     <dd>
+      Mozilla teknolojisini kendi projelerinizde nasıl kullanabileceğinizi öğrenin.</dd>
+     <dt>
+      <a class="internal" href="/En/Documentation_hot_links" title="En/Documentation hot links">Dökümantasyon sıcak bağlantıları</a></dt>
+     <dd>
+      Son dökümantasyonlar ve bir biri ile ilişikli bağlantıların merkezi bura</dd>
+    </dl>
+   </td>
+  </tr>
+ </tbody>
+</table>
+<p> </p>
diff --git a/files/tr/orphaned/web/html-alani/index.html b/files/tr/orphaned/web/html-alani/index.html
new file mode 100644
index 0000000000..06153ac1c1
--- /dev/null
+++ b/files/tr/orphaned/web/html-alani/index.html
@@ -0,0 +1,103 @@
+---
+title: 'HTML: Hypertext Markup Language'
+slug: Web/HTML-Alani
+tags:
+  - HTML
+  - HTML5
+  - Web
+---
+<div>{{HTMLSidebar}}</div>
+
+<p class="summary"><span class="seoSummary"><strong>HTML</strong><span class="tlid-translation translation" lang="tr"><span title=""> (HyperText Markup Language), Web’in en temel yapı taşıdır.</span> <span title="">Web içeriğinin anlamını ve yapısını tanımlar.</span> <span title="">HTML dışındaki diğer teknolojiler genellikle bir web sayfasının görünümünü / sunumunu (<a href="/tr/docs/Web/CSS">CSS</a>) veya işlevselliğini / davranışını (<a href="/tr/docs/Web/JavaScript">JavaScript</a>) tanımlamak için kullanılır.</span></span></span></p>
+
+<p>"HyperText" (köprü metni, üst metin, hiper metin olarak  da bilinir), web sayfalarını tek bir web sitesi içinde veya web siteleri arasında birbirine bağlayan bağlantıları ifade eder. Bağlantılar, Web'in temel bir özelliğidir. İnternete içerik yükleyerek ve başkaları tarafından oluşturulan sayfalara bağlayarak, World Wide Web’de aktif bir katılımcı olursunuz.</p>
+
+<p>HTML, bir Web tarayıcısında görüntülenmek üzere metin, resim ve diğer içerikleri tanımlamak için "işaretlemeyi" (markup) kullanır.</p>
+
+<p>HTML işaretlemesi {{HTMLElement("head")}}, {{HTMLElement("title")}}, {{HTMLElement("body")}}, {{HTMLElement("header")}}, {{HTMLElement("footer")}}, {{HTMLElement("article")}}, {{HTMLElement("section")}}, {{HTMLElement("p")}}, {{HTMLElement("div")}}, {{HTMLElement("span")}}, {{HTMLElement("img")}}, {{HTMLElement("aside")}}, {{HTMLElement("audio")}}, {{HTMLElement("canvas")}}, {{HTMLElement("datalist")}}, {{HTMLElement("details")}}, {{HTMLElement("embed")}}, {{HTMLElement("nav")}}, {{HTMLElement("output")}}, {{HTMLElement("progress")}}, {{HTMLElement("video")}}, {{HTMLElement("ul")}}, {{HTMLElement("ol")}}, {{HTMLElement("li")}} gibi birçok özel "element" içerir.</p>
+
+<p>Bir HTML elementi, bir belgedeki diğer metinden "&lt;" ve "&gt;" ile çevrelenmiş element adından oluşan "etiketler" ile ayrılır. Bir etiket içindeki bir elementin adı büyük / küçük harf duyarsızdır. Yani, büyük harf, küçük harf veya karışım şeklinde yazılabilir. Örneğin, <code>&lt;title&gt;</code> etiketi <code>&lt;Title&gt;</code>, <code>&lt;TITLE&gt;</code> veya başka bir şekilde yazılabilir.</p>
+
+<p>Aşağıdaki makaleler HTML hakkında daha fazla bilgi edinmenizi sağlayabilir.</p>
+
+<section class="cleared" id="sect1">
+<ul class="card-grid">
+ <li><span>HTML'e Giriş</span>
+
+  <p>Web geliştirmede yeniyseniz, HTML'nin ne olduğunu ve nasıl kullanılacağını öğrenmek için <a href="/en-US/docs/Learn/Getting_started_with_the_web/HTML_basics">HTML Temelleri</a> makalemizi mutlaka okuyun.</p>
+ </li>
+ <li><span>HTML Dersleri</span>
+  <p>HTML'nin yanı sıra dersler ve örneklerin kullanımı hakkında makaleler için, <a href="/en-US/docs/Learn/HTML">HTML Öğrenme Alanı</a>'nı inceleyin..</p>
+ </li>
+ <li><span>HTML Öğelerinin Açıklamaları</span>
+  <p><a href="/en-US/docs/Web/HTML/Reference">Genişletilmiş HTML örnekleri </a>bölümümüzde, HTML'deki her element ve özellik hakkındaki ayrıntıları bulacaksınız.</p>
+ </li>
+</ul>
+
+<div class="row topicpage-table">
+<div class="section">
+<h2 class="Tools" id="Temel_Düzey_Dersleri">Temel Düzey Dersleri</h2>
+
+<p><a href="/en-US/docs/Learn/HTML">HTML Ögrenme Alanımız</a> HTML hakkında hiçbir önbilgi sahibi olmanızı gerektirmeksizin en temelden başlayarak anlatan modüller bulundurmaktadır.</p>
+
+<dl>
+ <dt><a href="/en-US/docs/Learn/HTML/Introduction_to_HTML">HTML'e Giriş </a></dt>
+ <dd>Bu modül, sizi köprüler (linkler) oluşturma ve bir web sayfasını yapılandırmak için HTML'in nasıl kullanılabileceği gibi önemli kavramlara ve sözdizimine alıştırarak temel oluşturur.</dd>
+ <dt><a href="/en-US/docs/Learn/HTML/Multimedia_and_embedding">Multimedia ekleme ve gömme (embed etme) İşlemleri</a></dt>
+ <dd>Bu modül, bir HTML sayfasına multimedia içeriklerin birkaç farklı yol ile nasıl dahil edileceği, videoların, ses dosyalarının ve hatta bir web sayfasının tamamımının bir HTML sayfasına nasıl gömülebileceğini keşfetmenizi sağlar.</dd>
+ <dt><a href="/en-US/docs/Learn/HTML/Tables">HTML tabloları</a></dt>
+ <dd>Bir web sayfasındaki tablo verilerini anlaşılabilir, erişilebilir bir şekilde göstermek zor olabilir. Bu modül, temel tablo elementlerinden {{HTMLElement("caption")}} ve {{HTMLElement("summary")}} gibi daha ileri özelliklere kadar bilgileri kapsar.</dd>
+ <dt><a href="/en-US/docs/Learn/HTML/Forms">HTML formları</a></dt>
+ <dd>Formlar, Web’in çok önemli bir parçasıdır - kaydolma ve giriş yapma, geri bildirim gönderme, ürün satın alma gibi web siteleriyle etkileşimde bulunmak için ihtiyacınız olan işlevselliğin çoğunu sağlar. Bu modül, formların istemci tarafı / front-end kısımlarını oluşturmaya başlamanızı sağlar.</dd>
+ <dt><a href="/en-US/docs/Learn/HTML/Howto">Yaygın HTML problemlerinin çözümleri</a></dt>
+ <dd>Bir web sayfası oluştururken sık karşılaşılan HTML sorunlarının nasıl çözülebileceğini açıklayan içerik bölümlerine bağlantılar sağlar: başlıklarla çalışmak, resimler veya videolar eklemek, içeriği vurgulamak, temel bir form oluşturmak, vb.</dd>
+</dl>
+
+<h2 id="İleri_Düzey_Konular">İleri Düzey Konular</h2>
+
+<dl>
+ <dt class="landingPageList"><a href="/en-US/docs/Web/HTML/CORS_enabled_image">CORS olarak etkinleştirilmiş resim</a></dt>
+ <dd class="landingPageList">{{htmlattrxref("crossorigin", "img")}} özelliği, uygun bir {{glossary("CORS")}} üstbilgisiyle birlikte, {{HTMLElement("img")}} elementi tarafından tanımlanan görüntülerin yabancı kaynaklardan yüklenmesini ve bir {{HTMLElement("canvas")}} elemanında mevcut orijinden yüklenmiş gibi kullanılmasını sağlar.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Web/HTML/CORS_settings_attributes">CORS </a><a href="/en-US/docs/Web/HTML/CORS_settings_attributes">ayarları özellikleri</a></dt>
+ <dd class="landingPageList">{{HTMLElement("img")}} veya {{HTMLElement("video")}} gibi <a href="/en-US/docs/HTTP/Access_control_CORS">CORS</a> desteği sağlayan bazı HTML öğelerinde, öğenin getirilen verileri için CORS isteklerini yapılandırmanıza izin veren bir <code>crossorigin</code> özelliği (<code>crossOrigin</code> özelliği) bulunur.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Web/HTML/Focus_management_in_HTML">HTML'de Focus yönetimi</a></dt>
+ <dd><code><a href="/en-US/docs/Web/API/Document/activeElement">activeElement</a></code> DOM özelliği ve <code><a href="/en-US/docs/Web/API/Document/hasFocus">hasFocus()</a></code> DOM metodu bir kullanıcınin bir web sayfasindaki elementlerle etkileşimlerini izlemenize ve kontrol etmenize yardımcı olur.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Web/HTML/Preloading_content">rel="preload" ile içeriği önceden yükleme</a></dt>
+ <dd class="landingPageList">{{htmlelement("link")}} elementinin <code>preload</code> değerinin {{htmlattrxref("rel", "link")}} özelliği HTML’nizin {{htmlelement("head")}} bölümüne web tarayıcısının sayfayı ilk gösterime hazırlamasından önce, sayfa ilk görüntülendiğinde görünecek olan bölümlerin istenildiği gibi gösterilebilmesi için ihtiyaç duyacağı kaynakları sayfa yüklenmeye ilk başladığında getirmesi için isteklerinizi yazmanıza olanak tanır. Bu, daha önceden kullanılabilir olmalarını sağlar ve sayfanın ilk oluşturma işlemini engelleme olasılığının daha düşük olmasını sağlar ve bu da performans iyileştirmeleri sağlar. Bu makale, önyüklemenin nasıl çalıştığı hakkında temel bir rehberdir.</dd>
+</dl>
+</div>
+
+<div class="section">
+<h2 class="Documentation" id="HTML_öğeleri">HTML öğeleri</h2>
+
+<dl>
+ <dt class="landingPageList"><a href="/en-US/docs/Web/HTML/Reference">HTML öğeleri</a></dt>
+ <dd class="landingPageList">HTML, her biri belirli sayıda <strong>özellik (attribute)</strong> tarafından özelleştirilebilen <strong>elementlerden (HTML elementi)</strong> oluşur. HTML belgeleri birbirine <a href="/en-US/docs/Web/HTML/Link_types">linkler</a> ile bağlanır.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Web/HTML/Element">HTML elementleri</a></dt>
+ <dd class="landingPageList">Tüm {{glossary("HTML")}} {{glossary("Element", "element")}} 'lerinin yer aldığı listeye göz at!</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Web/HTML/Attributes">HTML özellikleri (attribute)</a></dt>
+ <dd class="landingPageList">HTML elementleri özelliklere sahiptirler. Bu özellikler farklı yollarla elementlerin davranışlarını belirler.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Web/HTML/Global_attributes">Global özellikler (attributes)</a></dt>
+ <dd class="landingPageList">Global özellikler <em>standart olmayan elementler dahil</em> tüm HTML elementlerini belirler.<em> </em>Bu HTML5 ile uyumlu olmayan bir belge olsa dahi tum elementleri belirtebileceği anlamına gelir.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Web/HTML/Inline_elements">Inline elementler</a> ve <a href="/en-US/docs/Web/HTML/Block-level_elements">block-level elementler</a></dt>
+ <dd class="landingPageList">HTML elementleri genelde "inline" (satıriçi) veya "block-level" (blok düzeyli) elementlerdir. Bir inline element yalnızca onu tanımlayan etiketlerle sınırlanan alan kadar yer kaplar. Bir block-level element bir "blok" oluşturarak bir ust elementinin tumunu kaplar.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Web/HTML/Link_types">Link tipleri</a></dt>
+ <dd class="landingPageList">HTML'de, iki doküman arasında bağlantılar birçok farklı link tipi ile kurulabilir. Link elementleri {{HTMLElement("a")}}, {{HTMLElement("area")}} and {{HTMLElement("link")}} ile oluşturulabilir.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Web/HTML/Supported_media_formats">HTML audio ve video elementleri tarafından desteklenen media formatları</a></dt>
+ <dd class="landingPageList">{{HTMLElement("audio")}} ve {{HTMLElement("video")}} elementleri audio ve video dosyaları oynatmanıza izin verir. Bu elementler Adobe Flash ve eklentilere alternatif olarak tarayıcıya özgü oynatıcılar sunar.</dd>
+ <dt class="landingPageList"><a href="/en-US/docs/Web/HTML/Kinds_of_HTML_content">HTML içeriğinin çeşitleri</a></dt>
+ <dd class="landingPageList">HTML, her biri belirli bağlamlarda kullanılmasına izin verilen ve başkalarına izin verilmeyen çeşitli içerik türlerinden oluşur. Benzer şekilde, her biri içerebilecekleri başka içerik kategorilerine ve içinde kullanılabilecek veya kullanılamayacak öğelere sahiptir. Bu, bu kategoriler için bir rehberdir.</dd>
+ <dt class="landingPageList"></dt>
+ <dt class="landingPageList"><a href="/en-US/docs/Web/HTML/Quirks_Mode_and_Standards_Mode">Quirks mod(garip mod) and standard mod</a></dt>
+ <dd class="landingPageList">Quirk mod and standard mod hakkında tarihi bilgiler.</dd>
+</dl>
+
+<h2 class="landingPageList" id="İlgili_Konular">İlgili Konular</h2>
+
+<dl>
+ <dt><a href="/en-US/docs/Web/HTML/Applying_color">HTML elementlerini CSS kullanarak renklendirmek</a></dt>
+ <dd>Bu makale HTML içeriklerine  CSS kullanarak renk eklemek için kullanılan çoğu yolu kapsamaktadır. Renklendirilebilecek HTML elementlerini ve bu elementleri hangi CSS özellikleri kullanılarak renklendirilebileceğini gösterir. Örnekler, renk palet araçlarının linkleri ve daha fazlası burada.</dd>
+</dl>
+</div>
+</div>
+<span class="alllinks"><a href="/en-US/docs/tag/HTML">Tümünü Görüntüle...</a></span></section>
diff --git a/files/tr/orphaned/web/javascript/reference/global_objects/array/prototype/index.html b/files/tr/orphaned/web/javascript/reference/global_objects/array/prototype/index.html
new file mode 100644
index 0000000000..19ffe3c80f
--- /dev/null
+++ b/files/tr/orphaned/web/javascript/reference/global_objects/array/prototype/index.html
@@ -0,0 +1,205 @@
+---
+title: Array.prototype
+slug: Web/JavaScript/Reference/Global_Objects/Array/prototype
+translation_of: Web/JavaScript/Reference/Global_Objects/Array/prototype
+---
+<div>{{JSRef("Global_Objects", "Array")}}</div>
+
+<h2 id="Summary" name="Summary">Summary</h2>
+
+<p>The <strong><code>Array.prototype</code></strong> property represents the prototype for the {{jsxref("Global_Objects/Array", "Array")}} constructor.</p>
+
+<div>{{js_property_attributes(0, 0, 0)}}</div>
+
+<h2 id="Description" name="Description">Description</h2>
+
+<p>{{jsxref("Global_Objects/Array", "Array")}} instances inherit from <code>Array.prototype</code>. As with all constructors, you can change the constructor's prototype object to make changes to all {{jsxref("Global_Objects/Array", "Array")}} instances.</p>
+
+<p>Little known fact: <code>Array.prototype</code> itself is an {{jsxref("Global_Objects/Array", "Array")}}:</p>
+
+<pre class="brush: js">Array.isArray(Array.prototype); // true
+</pre>
+
+<h2 id="Properties" name="Properties">Properties</h2>
+
+<dl>
+ <dt><code>Array.prototype.constructor</code></dt>
+ <dd>Specifies the function that creates an object's prototype.</dd>
+ <dt>{{jsxref("Array.prototype.length")}}</dt>
+ <dd>Reflects the number of elements in an array.</dd>
+</dl>
+
+<h2 id="Methods" name="Methods">Methods</h2>
+
+<h3 id="Mutator_methods" name="Mutator_methods">Mutator methods</h3>
+
+<p>These methods modify the array:</p>
+
+<dl>
+ <dt>{{jsxref("Array.prototype.copyWithin()")}} {{experimental_inline}}</dt>
+ <dd>Copies a sequence of array elements within the array.</dd>
+ <dt>{{jsxref("Array.prototype.fill()")}} {{experimental_inline}}</dt>
+ <dd>Fills all the elements of an array from a start index to an end index with a static value.</dd>
+ <dt>{{jsxref("Array.prototype.pop()")}}</dt>
+ <dd>Removes the last element from an array and returns that element.</dd>
+ <dt>{{jsxref("Array.prototype.push()")}}</dt>
+ <dd>Adds one or more elements to the end of an array and returns the new length of the array.</dd>
+ <dt>{{jsxref("Array.prototype.reverse()")}}</dt>
+ <dd>Reverses the order of the elements of an array in place — the first becomes the last, and the last becomes the first.</dd>
+ <dt>{{jsxref("Array.prototype.shift()")}}</dt>
+ <dd>Removes the first element from an array and returns that element.</dd>
+ <dt>{{jsxref("Array.prototype.sort()")}}</dt>
+ <dd>Sorts the elements of an array in place and returns the array.</dd>
+ <dt>{{jsxref("Array.prototype.splice()")}}</dt>
+ <dd>Adds and/or removes elements from an array.</dd>
+ <dt>{{jsxref("Array.prototype.unshift()")}}</dt>
+ <dd>Adds one or more elements to the front of an array and returns the new length of the array.</dd>
+</dl>
+
+<h3 id="Accessor_methods" name="Accessor_methods">Accessor methods</h3>
+
+<p>These methods do not modify the array and return some representation of the array.</p>
+
+<dl>
+ <dt>{{jsxref("Array.prototype.concat()")}}</dt>
+ <dd>Returns a new array comprised of this array joined with other array(s) and/or value(s).</dd>
+ <dt>{{jsxref("Array.prototype.includes()")}} {{experimental_inline}}</dt>
+ <dd>Determines whether an array contains a certain element, returning <code>true</code> or <code>false</code> as appropriate.</dd>
+ <dt>{{jsxref("Array.prototype.join()")}}</dt>
+ <dd>Joins all elements of an array into a string.</dd>
+ <dt>{{jsxref("Array.prototype.slice()")}}</dt>
+ <dd>Extracts a section of an array and returns a new array.</dd>
+ <dt>{{jsxref("Array.prototype.toSource()")}} {{non-standard_inline}}</dt>
+ <dd>Returns an array literal representing the specified array; you can use this value to create a new array. Overrides the {{jsxref("Object.prototype.toSource()")}} method.</dd>
+ <dt>{{jsxref("Array.prototype.toString()")}}</dt>
+ <dd>Returns a string representing the array and its elements. Overrides the {{jsxref("Object.prototype.toString()")}} method.</dd>
+ <dt>{{jsxref("Array.prototype.toLocaleString()")}}</dt>
+ <dd>Returns a localized string representing the array and its elements. Overrides the {{jsxref("Object.prototype.toLocaleString()")}} method.</dd>
+ <dt>{{jsxref("Array.prototype.indexOf()")}}</dt>
+ <dd>Returns the first (least) index of an element within the array equal to the specified value, or -1 if none is found.</dd>
+ <dt>{{jsxref("Array.prototype.lastIndexOf()")}}</dt>
+ <dd>Returns the last (greatest) index of an element within the array equal to the specified value, or -1 if none is found.</dd>
+</dl>
+
+<h3 id="Iteration_methods" name="Iteration_methods">Iteration methods</h3>
+
+<p>Several methods take as arguments functions to be called back while processing the array. When these methods are called, the <code>length</code> of the array is sampled, and any element added beyond this length from within the callback is not visited. Other changes to the array (setting the value of or deleting an element) may affect the results of the operation if the method visits the changed element afterwards. While the specific behavior of these methods in such cases is well-defined, you should not rely upon it so as not to confuse others who might read your code. If you must mutate the array, copy into a new array instead.</p>
+
+<dl>
+ <dt>{{jsxref("Array.prototype.forEach()")}}</dt>
+ <dd>Calls a function for each element in the array.</dd>
+ <dt>{{jsxref("Array.prototype.entries()")}} {{experimental_inline}}</dt>
+ <dd>Returns a new <code>Array Iterator</code> object that contains the key/value pairs for each index in the array.</dd>
+ <dt>{{jsxref("Array.prototype.every()")}}</dt>
+ <dd>Returns true if every element in this array satisfies the provided testing function.</dd>
+ <dt>{{jsxref("Array.prototype.some()")}}</dt>
+ <dd>Returns true if at least one element in this array satisfies the provided testing function.</dd>
+ <dt>{{jsxref("Array.prototype.filter()")}}</dt>
+ <dd>Creates a new array with all of the elements of this array for which the provided filtering function returns true.</dd>
+ <dt>{{jsxref("Array.prototype.find()")}} {{experimental_inline}}</dt>
+ <dd>Returns the found value in the array, if an element in the array satisfies the provided testing function or <code>undefined</code> if not found.</dd>
+ <dt>{{jsxref("Array.prototype.findIndex()")}} {{experimental_inline}}</dt>
+ <dd>Returns the found index in the array, if an element in the array satisfies the provided testing function or -1 if not found.</dd>
+ <dt>{{jsxref("Array.prototype.keys()")}} {{experimental_inline}}</dt>
+ <dd>Returns a new <code>Array Iterator</code> that contains the keys for each index in the array.</dd>
+ <dt>{{jsxref("Array.prototype.map()")}}</dt>
+ <dd>Creates a new array with the results of calling a provided function on every element in this array.</dd>
+ <dt>{{jsxref("Array.prototype.reduce()")}}</dt>
+ <dd>Apply a function against an accumulator and each value of the array (from left-to-right) as to reduce it to a single value.</dd>
+ <dt>{{jsxref("Array.prototype.reduceRight()")}}</dt>
+ <dd>Apply a function against an accumulator and each value of the array (from right-to-left) as to reduce it to a single value.</dd>
+ <dt>{{jsxref("Array.prototype.values()")}} {{experimental_inline}}</dt>
+ <dd>Returns a new <code>Array Iterator</code> object that contains the values for each index in the array.</dd>
+ <dt>{{jsxref("Array.prototype.@@iterator()", "Array.prototype[@@iterator]()")}} {{experimental_inline}}</dt>
+ <dd>Returns a new <code>Array Iterator</code> object that contains the values for each index in the array.</dd>
+</dl>
+
+<h3 id="Generic_methods" name="Generic_methods">Generic methods</h3>
+
+<p>Many methods on the JavaScript Array object are designed to be generally applied to all objects which “look like” Arrays. That is, they can be used on any object which has a <code>length</code> property, and which can usefully be accessed using numeric property names (as with <code>array[5]</code> indexing). <span class="comment">TODO: give examples with Array.prototype.forEach.call, and adding the method to an object like {{jsxref("Global_Objects/JavaArray", "JavaArray")}} or {{jsxref("Global_Objects/String", "String")}}.</span> Some methods, such as {{jsxref("Array.join", "join")}}, only read the <code>length</code> and numeric properties of the object they are called on. Others, like {{jsxref("Array.reverse", "reverse")}}, require that the object's numeric properties and <code>length</code> be mutable; these methods can therefore not be called on objects like {{jsxref("Global_Objects/String", "String")}}, which does not permit its <code>length</code> property or synthesized numeric properties to be set.</p>
+
+<h2 id="Specifications" name="Specifications">Specifications</h2>
+
+<table class="standard-table">
+ <tbody>
+  <tr>
+   <th scope="col">Specification</th>
+   <th scope="col">Status</th>
+   <th scope="col">Comment</th>
+  </tr>
+  <tr>
+   <td>ECMAScript 1st Edition.</td>
+   <td>Standard</td>
+   <td>Initial definition.</td>
+  </tr>
+  <tr>
+   <td>{{SpecName('ES5.1', '#sec-15.4.3.1', 'Array.prototype')}}</td>
+   <td>{{Spec2('ES5.1')}}</td>
+   <td> </td>
+  </tr>
+  <tr>
+   <td>{{SpecName('ES6', '#sec-array.prototype', 'Array.prototype')}}</td>
+   <td>{{Spec2('ES6')}}</td>
+   <td> </td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Browser_compatibility" name="Browser_compatibility">Browser compatibility</h2>
+
+<div>{{CompatibilityTable}}</div>
+
+<div id="compat-desktop">
+<table class="compat-table">
+ <tbody>
+  <tr>
+   <th>Feature</th>
+   <th>Chrome</th>
+   <th>Firefox (Gecko)</th>
+   <th>Internet Explorer</th>
+   <th>Opera</th>
+   <th>Safari</th>
+  </tr>
+  <tr>
+   <td>Basic support</td>
+   <td>{{CompatVersionUnknown}}</td>
+   <td>{{CompatVersionUnknown}}</td>
+   <td>{{CompatVersionUnknown}}</td>
+   <td>{{CompatVersionUnknown}}</td>
+   <td>{{CompatVersionUnknown}}</td>
+  </tr>
+ </tbody>
+</table>
+</div>
+
+<div id="compat-mobile">
+<table class="compat-table">
+ <tbody>
+  <tr>
+   <th>Feature</th>
+   <th>Android</th>
+   <th>Chrome for Android</th>
+   <th>Firefox Mobile (Gecko)</th>
+   <th>IE Mobile</th>
+   <th>Opera Mobile</th>
+   <th>Safari Mobile</th>
+  </tr>
+  <tr>
+   <td>Basic support</td>
+   <td>{{CompatVersionUnknown}}</td>
+   <td>{{CompatVersionUnknown}}</td>
+   <td>{{CompatVersionUnknown}}</td>
+   <td>{{CompatVersionUnknown}}</td>
+   <td>{{CompatVersionUnknown}}</td>
+   <td>{{CompatVersionUnknown}}</td>
+  </tr>
+ </tbody>
+</table>
+</div>
+
+<h2 id="See_also" name="See_also">See also</h2>
+
+<ul>
+ <li>{{jsxref("Global_Objects/Array", "Array")}}</li>
+ <li>{{jsxref("Function.prototype")}}</li>
+</ul>