initial commit

33 files changed, 2982 insertions, 0 deletions

diff --git a/files/id/mozilla/add-ons/index.html b/files/id/mozilla/add-ons/index.html
new file mode 100644
index 0000000000..f25d110860
--- /dev/null
+++ b/files/id/mozilla/add-ons/index.html
@@ -0,0 +1,16 @@
+---
+title: Add-ons
+slug: Mozilla/Add-ons
+translation_of: Mozilla/Add-ons
+---
+<p>{{AddonSidebar}}</p>
+
+<p><span class="seoSummary">Add-ons Menambah fungsi baru pada aplikasi berbasis <span class="seoSummary"><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Gecko">Gecko</a></span> seperti Firefox, SeaMonkey dan Thunderbird. Ada dua jenis "add-on" :  <a href="/en-US/docs/Extensions" title="Extensions">Extensions</a> menambahkan fitur ke aplikasi, sedangkan <a href="https://developer.mozilla.org/id/docs/Mozilla/Add-ons$edit#Themes">Tema</a> merubah tampilan pada aplikasi.</span></p>
+
+<p>Keduanya (Extention, dan Tema) ditemukan dalam <a href="https://addons.mozilla.org/">addons.mozilla.org</a>, dikenal juga sebagai AMO. Ketika Anda <a href="https://developer.mozilla.org/en-US/Add-ons/Submitting_an_add-on_to_AMO">masukan add-ons ke AMO</a> mereka meninjau, dan setelah melewati tinjauan maka mereka menyajikan untuk pengguna. Anda tidak harus masukan add-on ke AMO, tetapi anda lakukan, <span id="result_box" lang="id"><span class="hps">pengguna dapat</span> <span class="hps">menaruh keyakinan </span><span class="hps">bahwa</span> <span class="hps">mereka</span> <span class="hps">telah ditinjau</span></span>, dan Anda dapat keuntungan dari visibilitas AMO sebagai sumber add-on yang berguna.</p>
+
+<p><span id="result_box" lang="id"><span class="atn hps">Add-</span><span>ons</span> <span class="hps">dapat </span><span class="hps">mempengaruhi perilaku</span> <span class="hps">aplikasi</span> <span class="hps">host</span> <span class="hps">mereka</span></span>. Kami telah membangun <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Add-on_guidelines">sekumpulan panduan</a> untuk membantu memastikan bahwa mereka telah didukung mendapatkan pengalaman yang baik pada pengguna. Panduan ini digunakan untuk beberapa add-on, apakah mereka juga ditaruh di <a href="https://addons.mozilla.org/">addons.mozilla.org</a> atau tidak.</p>
+
+<h2 id="Extentions"><strong>Extentions</strong></h2>
+
+<p>Extention menambah fungsi dari aplikasi Mozzila seperti Firefox dan Thunderbird. Extension dapat menambahkan fitur pada peramban, seperti mengatur tab, dan mereka dapat merubah konten web untuk meningkatkan pengguanan atau keamanan website tertentu.</p>
diff --git a/files/id/mozilla/add-ons/setting_up_extension_development_environment/index.html b/files/id/mozilla/add-ons/setting_up_extension_development_environment/index.html
new file mode 100644
index 0000000000..6519e6752d
--- /dev/null
+++ b/files/id/mozilla/add-ons/setting_up_extension_development_environment/index.html
@@ -0,0 +1,167 @@
+---
+title: Setting up an extension development environment
+slug: Mozilla/Add-ons/Setting_up_extension_development_environment
+translation_of: Archive/Add-ons/Setting_up_extension_development_environment
+---
+<p>This article gives suggestions on how to set up your Mozilla application for extension development. Unless otherwise specified, these suggestions apply to both Firefox and Thunderbird as well as SeaMonkey version 2.0 and above.</p>
+
+<h3 id="Overview">Overview</h3>
+
+<ul>
+ <li>Create a development <a href="#Development_profile">user profile</a> to run your development firefox session; with special <a href="#Development_preferences">development preferences</a> in <code>about:config</code>.</li>
+ <li>Install some Firefox <a href="#Development_extensions">development extensions</a> to your dev profile.</li>
+ <li>Edit files in the extensions folder of your profile and restart the application with the dev profile.</li>
+</ul>
+
+<h3 id="Development_profile">Development profile</h3>
+
+<p>To avoid performance degradation from development-related prefs and extensions, and to avoid losing your personal data, you can use a separate profile for development work.</p>
+
+<p>You can run two instances of Thunderbird or Firefox at the same time by using separate profiles and starting the application with parameters <code>-no-remote</code> and <code>-P ProfileName</code>. For example, the following command will start Firefox with a profile called "dev" whether an instance of Firefox is already running or not. (If there is no "dev" user yet, you'll get the profile selection screen instead, where you can create one.)</p>
+
+<p>On Ubuntu (and many other Linux distributions):</p>
+
+<pre>/usr/bin/firefox -no-remote -P dev</pre>
+
+<p>On some other distributions of Linux/Unix:</p>
+
+<pre>/usr/local/bin/firefox -no-remote -P dev
+</pre>
+
+<p>On Mac OS Snow Leopard (10.6) and newer:</p>
+
+<pre class="eval">/Applications/Firefox.app/Contents/MacOS/firefox-bin -no-remote -P dev &amp;
+</pre>
+
+<p>On Mac OS Leopard (10.5) and older, you must request the 32-bit portion of the Universal Binary (<a class="link-https" href="https://bugzilla.mozilla.org/show_bug.cgi?id=622970" title="https://bugzilla.mozilla.org/show_bug.cgi?id=622970">https://bugzilla.mozilla.org/show_bug.cgi?id=622970</a>):</p>
+
+<pre class="eval">arch -arch i386 /Applications/Firefox.app/Contents/MacOS/firefox-bin -no-remote -P dev &amp;
+</pre>
+
+<p>On Windows:</p>
+
+<pre class="eval">Start -&gt; Run "%ProgramFiles%\Mozilla Firefox\firefox.exe" -no-remote -P dev
+</pre>
+
+<p>On Windows 64 bit:</p>
+
+<pre class="eval">Start -&gt; Run "%ProgramFiles(x86)%\Mozilla Firefox\firefox.exe" -no-remote -P dev</pre>
+
+<p>To start Thunderbird or SeaMonkey instead of Firefox, substitute "thunderbird" or "seamonkey" for "firefox" in the examples above.</p>
+
+<p>Note that you can run Firefox using your regular profile while developing.</p>
+
+<p>Parameter <code>-P ProfileName</code> doesn't imply <code>-no-remote</code>, therefore use them together. Otherwise, if you already run a Firefox instance without <code>-no-remote</code>, and you attempt to start another instance with <code>-P ProfileName</code> but again without <code>-no-remote</code>, that second invocation would ignore its <code>-P ProfileName</code> parameter, but instead it would open a new blank window for the already running instance (sharing its profile, sessions etc.).</p>
+
+<p><span style="line-height: 1.5;">(There is a thread in the </span><a class="external" href="http://forums.mozillazine.org/" style="line-height: 1.5;" title="http://forums.mozillazine.org/">Mozillazine forums</a><span style="line-height: 1.5;"> that explains how to use both stable and development versions of Firefox to check extension compatibility. See </span><a class="external" href="http://forums.mozillazine.org/viewtopic.php?t=613873" style="line-height: 1.5;">Installing Firefox 3 or Minefield while keeping Firefox 2</a><span style="line-height: 1.5;">.)</span></p>
+
+<h3 id="Development_command_flags">Development command flags</h3>
+
+<p>As of Gecko 2 (Firefox 4), JavaScript files are cached ("fastload"). The <code>-purgecaches</code> command-line flag disables this behavior. Alternatively, you can set the MOZ_PURGE_CACHES environment variable. See <a class="link-https" href="https://bugzilla.mozilla.org/show_bug.cgi?id=531886" title="https://bugzilla.mozilla.org/show_bug.cgi?id=531886">this bug</a> for more information.</p>
+
+<h3 id="Development_preferences">Development preferences</h3>
+
+<p><span style="line-height: 1.5;">There is a set of development preferences that, when enabled, allows you to view more information about application activity, thus making debugging easier. However,  these preferences can degrade performance, so you may want to use a separate development profile when you enable these preferences.</span></p>
+
+<h4 id="Accessing_Firefox_development_preferences">Accessing Firefox development preferences</h4>
+
+<p>To change preference settings in Firefox or SeaMonkey, type <code style="font-size: 14px;">about:config </code>in the Location Bar. You can also use the <a class="external" href="http://addons.mozilla.org/en-US/firefox/addon/7434/" title="http://addons.mozilla.org/en-US/firefox/addon/7434/">Extension Developer's Extension</a>, which provides a menu interface for Firefox settings. Alternatively, install <span style="line-height: 1.5;">the</span><span style="line-height: 1.5;"> </span><a href="https://addons.mozilla.org/en-US/firefox/addon/developer-profile/" style="line-height: 1.5;" title="https://addons.mozilla.org/en-US/firefox/addon/developer-profile/">Developer Profile</a><span style="line-height: 1.5;"> to set the preferences listed below and skip the rest of this section.</span></p>
+
+<h4 id="Accessing_Thunderbird_development_preferences">Accessing Thunderbird development preferences</h4>
+
+<p>To change preference settings in Thunderbird, open the "Preferences" (Unix) or "Options" (Windows) interface. On the "Advanced" page, select the "General" tab then click the "Config Editor" button.</p>
+
+<h4 id="Recommended_development_preferences">Recommended development preferences</h4>
+
+<p><span style="line-height: 1.5;">Not all preferences are defined by default, and are therefore not listed</span><span style="line-height: 1.5;"> by default. You will have to create new (boolean) entries for them. </span><span style="line-height: 1.5;">For more information about Mozilla preferences, refer to the mozillaZine article on "</span><a class="external" href="http://kb.mozillazine.org/About:config" style="line-height: 1.5;" title="http://kb.mozillazine.org/About:config">about:config</a><span style="line-height: 1.5;">". (Tip: Download addon <a href="https://addons.mozilla.org/en-US/firefox/addon/devprefs/">DevPrefs</a>, it will automatically handle this)</span></p>
+
+<ul>
+ <li><strong>javascript.options.showInConsole</strong> = <strong>true</strong>. Logs errors in chrome files to the <a href="/en/Error_Console" title="en/Error_Console">Error Console</a>.</li>
+ <li><strong>nglayout.debug.disable_xul_cache</strong> = <strong>true</strong>. Disables the XUL cache so that changes to windows and dialogs do not require a restart. This assumes you're <a href="#Using_directories_rather_than_JARs">using directories rather than JARs</a>. Changes to XUL overlays will still require reloading of the document overlaid.</li>
+ <li><strong>browser.dom.window.dump.enabled</strong> = <strong>true</strong>. Enables the use of the <span style="font-family: Courier New;">dump()</span> statement to print to the standard console. See <span style="font-family: Courier New;">{{ Domxref("window.dump") }}</span> for more info. You can use <span style="font-family: Courier New;">{{ Interface("nsIConsoleService") }}</span> instead of <code>dump()</code> from a privileged script.</li>
+ <li><strong>javascript.options.strict</strong> = <strong>true</strong>. Enables strict JavaScript warnings in the Error Console. Note that since many people have this setting turned off when developing, you will see lots of warnings for problems with their code in addition to warnings for your own extension. You can filter those with <a class="link-https" href="https://addons.mozilla.org/en-US/firefox/addon/1815">Console<sup>2</sup></a>.</li>
+ <li><strong>devtools.chrome.enabled = true.</strong> This enables to run JavaScript code snippets in the chrome context of the Scratchpad from the Tools menu. Don't forget to switch from content to browser as context.</li>
+ <li><strong>devtools.debugger.remote-enabled = true.</strong> This adds a "Browser Debugger" entry to the "Web Developer" submenu of the "Tools" menu.  The <a href="/en/Tools/Debugger" title="/en/Tools/Debugger">Browser Debugger</a> can be used to debug the JavaScript code of extensions. The {{pref("devtools.chrome.enabled")}} preference must also be set to true for the Browser Debugger to be enabled.</li>
+ <li><strong>extensions.logging.enabled</strong> = <strong>true</strong>. This will send more detailed information about installation and update problems to the <a href="/en/Error_Console" title="en/Error Console">Error Console</a>. (Note that the extension manager automatically restarts the application at startup sometimes, which may mean you won't have time to see the messages logged before the automatic restart happens. To see them, prevent the automatic restart by setting the environment NO_EM_RESTART to 1 before starting the application.)</li>
+ <li><strong>nglayout.debug.disable_xul_fastload = true</strong>. For Gecko 2.0+ (Firefox 4.0+). See <a class="link-https" href="https://bugzilla.mozilla.org/show_bug.cgi?id=531886" title="https://bugzilla.mozilla.org/show_bug.cgi?id=531886">this bug</a> for more information. Although the bug has been closed, it is believed that this pref is still relevant.</li>
+ <li>You might also want to set <strong>dom.report_all_js_exceptions = true</strong>. See <a class="internal" href="/en/Exception_logging_in_JavaScript" title="en/Exception logging in JavaScript">Exception logging in JavaScript</a> for details.</li>
+ <li><strong>devtools.errorconsole.deprecation_warnings = true</strong>. Detect deprecated code use.</li>
+</ul>
+
+<p></p><div class="warning"><strong>Never</strong> set {{pref("nglayout.debug.disable_xul_fastload")}} to true in a production environment; it exists solely to aid in debugging. In particular, add-ons should never change this preference.</div>.<p></p>
+
+<div class="note">
+<p><strong>Note:</strong>The Error Console is disabled by default starting in {{Gecko("2.0")}}. You can re-enable it by changing the <code>devtools.errorconsole.enabled</code> preference to <code>true</code> and restarting the browser. With this, <code>javascript.options.showInConsole</code> is also set to <code>true</code> by default.</p>
+</div>
+
+<div class="note">
+<p><strong>Tip:</strong> Download the addon <a href="https://addons.mozilla.org/en-US/firefox/addon/devprefs/">DevPrefs </a>from AMO to automatically configure the preferences.</p>
+</div>
+
+<h4 id="Development_extensions"><span style="font-size: 1.428em; letter-spacing: -0.5px; line-height: 20px;">Development extensions</span></h4>
+
+<p>These extensions may help you with your development.</p>
+
+<ul>
+ <li><a class="link-https" href="https://addons.mozilla.org/en-US/firefox/addon/6622">DOM Inspector</a>, used to inspect and edit the live DOM of any web document or XUL application (Firefox and Thunderbird)</li>
+ <li><a class="external" href="http://www.hacksrus.com/%7Eginda/venkman/">Venkman</a>, a JavaScript Debugger (<a class="external" href="http://addons.mozilla.org/en-US/firefox/addon/216" title="http://addons.mozilla.org/en-US/firefox/addon/216">Firefox version</a>, <a class="external" href="http://addons.mozilla.org/en-US/thunderbird/addon/216" title="http://addons.mozilla.org/en-US/thunderbird/addon/216">Thunderbird version</a>)</li>
+ <li><a href="http://kewisch.wordpress.com/2013/09/22/thunderbird-developer-tools-wrapup/">Thunderbird Developer Tools</a>, enables debugging Thunderbird remotely using using Firefox developer tools</li>
+ <li><a class="link-https" href="https://addons.mozilla.org/en-US/firefox/addon/7434/">Extension Developer's Extension</a> a suite of tools for extension development (Firefox)</li>
+ <li><a class="link-https" href="https://addons.mozilla.org/en-US/firefox/addon/extension-test/">Extension Test</a> an add-on which makes it easier to detect problems which will lead to rejection by addons.mozilla.org</li>
+ <li><a class="external" href="http://console2.mozdev.org/">Console²</a> enhanced JavaScript console (<a class="external" href="http://addons.mozilla.org/en-US/firefox/addon/1815" title="http://addons.mozilla.org/en-US/firefox/addon/1815">Firefox version</a>, <a class="external" href="http://addons.mozilla.org/en-US/thunderbird/addon/1815" title="http://addons.mozilla.org/en-US/thunderbird/addon/1815">Thunderbird version</a>)</li>
+ <li><a class="link-https" href="https://addons.mozilla.org/firefox/addon/5058">Javascript Command</a> for writing/testing javascript on Firefox windows</li>
+ <li><a class="link-https" href="https://addons.mozilla.org/firefox/addon/5058">Inspect Context</a> Open <a class="link-https" href="https://addons.mozilla.org/en-US/firefox/addon/6622">DOM Inspector</a> at this node from Inspect on context menu.</li>
+ <li><a class="link-https" href="https://addons.mozilla.org/en-US/firefox/addon/4453/">Chrome List</a> navigate and view files in chrome:// (<a class="external" href="http://addons.mozilla.org/en-US/firefox/addon/4453" title="http://addons.mozilla.org/en-US/firefox/addon/4453">Firefox version</a>, <a class="external" href="http://addons.mozilla.org/en-US/thunderbird/addon/4453" title="http://addons.mozilla.org/en-US/thunderbird/addon/4453">Thunderbird version</a>)</li>
+ <li><a class="external" href="http://webdesigns.ms11.net/chromeditp.html">Chrome Edit Plus</a> a user file editor (Firefox and Thunderbird)</li>
+ <li><a class="link-https" href="https://addons.mozilla.org/en-US/developers/tools/builder">Add-on Builder</a> a web-based application that generates an extension skeleton (Firefox, Thunderbird, and others)</li>
+ <li><a class="link-https" href="https://addons.mozilla.org/firefox/addon/1843">Firebug</a> a variety of development tools (Firefox)</li>
+ <li><a class="external" href="http://dactyl.sf.net/pentadactyl/">Pentadactyl</a>, a general purpose extension with builtin tools for extension development, including a command line with chrome JavaScript evaluation (including property and function argument completion) and the ability to demand-load external JavaScript and CSS files into window chrome.</li>
+ <li><a class="external" href="http://getfirebug.com/releases/chromebug/">Chromebug</a> combines elements of a JavaScript debugger and DOM (Firefox, "kinda works for Thunderbird")</li>
+ <li><a class="link-https" href="https://github.com/bard/mozrepl/wiki">MozRepl</a> explore and modify Firefox and other Mozilla apps while they run (Firefox, Thunderbird version is <a href="https://github.com/bard/mozrepl/issues/47">not working</a>)</li>
+ <li><a class="external" href="http://www.mouseless.de/index.php?/content/view/18/31/">ExecuteJS</a> an enhanced JavaScript console (<a class="link-https" href="https://addons.mozilla.org/firefox/addon/1729">Firefox version</a>, <a class="external" href="http://xsidebar.mozdev.org/modifiedmisc.html#executejs">Thunderbird version</a> is <a href="https://code.google.com/p/executejs/issues/detail?id=6">not working</a>)</li>
+ <li><a class="external" href="http://xpcomviewer.mozdev.org">XPCOMViewer</a> an XPCOM inspector (Firefox and Thunderbird)</li>
+ <li><a class="internal" href="/en/JavaScript/Shells" title="En/JavaScript shells">JavaScript shells</a> to test snippets of JavaScript (Firefox and Thunderbird)</li>
+ <li><a class="link-https" href="https://addons.mozilla.org/en-US/firefox/addon/5817">SQLite Manager</a> to manage the SQLite database (Firefox and Thunderbird)</li>
+ <li><a class="external" href="http://www.rumblingedge.com/viewabout/">ViewAbout</a> enables access to various about: dialogs from the View menu (<a class="link-https" href="https://addons.mozilla.org/en-US/firefox/addon/9695">Firefox version</a>, <a class="link-https" href="https://addons.mozilla.org/en-US/thunderbird/addon/9695">Thunderbird version</a> )</li>
+ <li><a class="external" href="http://code.google.com/p/crashme/">Crash Me Now!</a> useful for testing debug symbols and the crash reporting system (Firefox and Thunderbird)</li>
+ <li><a href="https://addons.mozilla.org/en-US/firefox/addon/javascript-object-examiner/" title="https://addons.mozilla.org/en-US/firefox/addon/javascript-object-examiner/">Javascript Object Examiner</a> displays JavaScript object methods and properties for any available scope</li>
+ <li><a href="https://addons.mozilla.org/en-US/firefox/addon/developer-profile/" title="https://addons.mozilla.org/en-US/firefox/addon/developer-profile/">Developer Profile</a> sets up the development environment described above when installed (Firefox and Fennec)</li>
+</ul>
+
+<h3 id="Firefox_extension_proxy_file">Firefox extension proxy file</h3>
+
+<p>Extension files are normally installed in the user profile. However, it is usually easier to place extension files in a temporary location, which also protects source files from accidental deletion. This section explains how to create a proxy file that points to an extension that is installed in a location other than the user profile.</p>
+
+<ol>
+ <li>Get the extension ID from the extension's install.rdf file.</li>
+ <li>Create a file in the "<code>extensions</code>" directory under your profile directory with the extension's ID as the file name (for example "<code>your_profile_directory/extensions/{46D1B3C0-DB7A-4b1a-863A-6EE6F77ECB58}</code>"). (<a class="external" href="http://kb.mozillazine.org/Profile_folder">How to find your profile directory</a>) Alternatively, rather than using a GUID, create a unique ID using the format "name@yourdomain" (for example <span class="nowiki"><code>chromebug@mydomain.com</code></span>) - then the proxy filename will be same as that ID, with no curly brackets {}.</li>
+ <li>
+  <p>The contents of this file should be the path to the directory that contains your install.rdf file, for example <code><span class="nowiki">/full/path/to/yourExtension/</span></code> on Mac and Linux, and <code><span class="nowiki">C:\full\path\to\yourExtension\</span></code> on Windows. Remember to include the closing slash and remove any trailing whitespace.</p>
+
+  <ul>
+   <li>Note: If you already installed the extension via XPI, you should uninstall it first before creating the pointer file.</li>
+   <li>Also note that the use of proxy files requires that the extension's chrome.manifest defines its chrome urls using traditional directories, rather than a JARed structure. See below.</li>
+  </ul>
+ </li>
+ <li>Place the file in the extensions folder of your profile and restart the application.</li>
+</ol>
+
+<h3 id="Using_directories_rather_than_JARs">Using directories rather than JARs</h3>
+
+<p>Regardless of whether you choose to eventually package your extension's chrome in a JAR or in directories, developing in directories is simpler. If you choose a JARed structure for releasing, you can still develop with a directory structure by editing your chrome.manifest. For example, rather than having</p>
+
+<pre class="eval">content	myExtension	jar:chrome/myExtension.jar!/content/
+</pre>
+
+<p>use</p>
+
+<pre class="eval">content	myExtension	chrome/content/
+</pre>
+
+<p>{{ h1_gecko_minversion("Preventing the first launch extension selector", "8.0") }}</p>
+
+<p>Starting in Firefox 8, on the first launch of a new version of Firefox, it presents user interface letting users select which third party add-ons to keep. This lets them weed out add-ons that were installed without their knowledge, or that are no longer needed.</p>
+
+<p>However, this interface can be disruptive when debugging add-ons. You can avoid this by setting the preference <code>extensions.autoDisableScopes</code> to 14.</p>
+
+<p>{{ languages( { "de": "de/Einrichten_einer_Entwicklungsumgebung_für_Erweiterungen", "fr": "fr/Configuration_d'un_environnement_de_développement_d'extensions", "ja": "ja/Setting_up_extension_development_environment", "zh-cn": "cn/Setting_up_extension_development_environment", "pl": "pl/Przygotowanie_środowiska_programowania_rozszerzenia", "ru": "ru/Настройка_среды_разработки_расширений" } ) }}</p>
diff --git a/files/id/mozilla/add-ons/webextensions/apa_itu_webextensions/index.html b/files/id/mozilla/add-ons/webextensions/apa_itu_webextensions/index.html
new file mode 100644
index 0000000000..63c093bc53
--- /dev/null
+++ b/files/id/mozilla/add-ons/webextensions/apa_itu_webextensions/index.html
@@ -0,0 +1,34 @@
+---
+title: Apa itu WebExtensions?
+slug: Mozilla/Add-ons/WebExtensions/Apa_Itu_WebExtensions
+translation_of: Mozilla/Add-ons/WebExtensions/What_are_WebExtensions
+---
+<div>{{AddonSidebar}}</div>
+
+<p><span id="result_box" lang="id"><span title="Add-ons extend and modify the functionality of a web browser.">Add-ons memperluas dan memodifikasi fungsi dari web browser. </span><span title="They are written using standard Web technologies - JavaScript, HTML, and CSS - plus some dedicated JavaScript APIs.">Mereka ditulis menggunakan teknologi Web standar - JavaScript, HTML, dan CSS - ditambah beberapa API JavaScript. </span><span title="Among other things, add-ons can add new features to the browser or change the appearance or content of particular websites.
+
+">Antara lain, add-ons dapat menambahkan fitur baru untuk browser atau mengubah tampilan atau konten dari situs web tertentu.</span></span></p>
+
+<p><span id="result_box" lang="id"><span title="WebExtensions are a cross-browser system for developing browser add-ons.">WebExtensions adalah sistem cross-browser untuk mengembangkan browser add-ons. </span><span title="To a large extent the API is compatible with the extension API supported by Google Chrome and Opera.">Untuk sebagian besar API tersebut kompatibel dengan</span></span> <a class="external external-icon" href="https://developer.chrome.com/extensions">ekstensi API</a> <span id="result_box" lang="id"><span title="To a large extent the API is compatible with the extension API supported by Google Chrome and Opera.">yang didukung oleh Google Chrome dan Opera</span></span>. <span id="result_box" lang="id"><span title="Extensions written for these browsers will in most cases run in Firefox or Microsoft Edge with just a few changes.">Ekstensi ditulis untuk browser ini dalam banyak kasus akan berjalan di Firefox atau Microsoft Edge hanya</span></span> <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Porting_from_Google_Chrome">dengan beberapa perubahan</a>. <span id="result_box" lang="id"><span title="The API is also fully compatible with multiprocess Firefox.
+
+">API ini juga sepenuhnya kompatibel dengan</span></span> <a href="https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox">multiprocess Firefox</a>.</p>
+
+<p><span id="result_box" lang="id"><span title="We're also intending to extend the APIs to support the needs of add-on developers, so if you have ideas, we'd love to hear them.">Kami juga berniat untuk memperpanjang API untuk mendukung kebutuhan para pengembang, jadi jika Anda memiliki ide, kami akan senang mendengar mereka. </span><span title="You can reach us on the dev-addons mailing list or #webextensions on IRC.
+
+">Anda dapat menghubungi kami</span></span> <a class="external external-icon" href="https://mail.mozilla.org/listinfo/dev-addons">dev-addons mailing list</a> atau <a href="irc://irc.mozilla.org/webextensions">#webextensions</a> di <a class="external external-icon" href="https://wiki.mozilla.org/IRC">IRC</a>.</p>
+
+<p><span id="result_box" lang="id"><span title="Before WebExtensions, you could develop Firefox add-ons using one of three different systems: XUL/XPCOM overlays, bootstrapped extensions, or the Add-on SDK.">Sebelum WebExtensions, Anda bisa mengembangkan Firefox add-ons menggunakan salah satu dari tiga sistem yang berbeda</span></span>: <a href="/en-US/Add-ons/Overlay_Extensions">XUL/XPCOM overlays</a>, <a href="/en-US/docs/Mozilla/Add-ons/Bootstrapped_extensions">bootstrapped extensions</a>, atau <a href="/en-US/docs/Mozilla/Add-ons/SDK">Add-on SDK</a>. <span id="result_box" lang="id"><span title="In the future, WebExtensions will be the recommended way to develop Firefox add-ons, and other systems will be deprecated.
+">Di masa depan, WebExtensions akan menjadi cara yang direkomendasikan untuk mengembangkan add-ons pada </span></span><span lang="id"><span title="In the future, WebExtensions will be the recommended way to develop Firefox add-ons, and other systems will be deprecated.
+">Firefox, dan sistem lainnya akan dihentikan.</span></span></p>
+
+<h2 id="Apa_berikutnya"><span id="result_box" lang="id"><span title="What's next?
+">Apa berikutnya?</span></span></h2>
+
+<ul>
+ <li><span id="result_box" lang="id"><span title='To try out some example WebExtensions, see our "webextensions-examples" GitHub repo.
+    '>Untuk mencoba beberapa contoh WebExtensions, lihat</span></span> <a href="https://github.com/mdn/webextensions-examples">"webextensions-examples" GitHub repo</a>.</li>
+ <li><span id="result_box" lang="id"><span title="To learn about the structure of a WebExtension, see Anatomy of a WebExtension.
+    ">Untuk mempelajari tentang struktur WebExtension, lihat</span></span> <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Anatomy_of_a_WebExtension">Anatomy of a WebExtension</a>.</li>
+ <li><span id="result_box" lang="id"><span title="To learn about the structure of a WebExtension, see Anatomy of a WebExtension.
+    "> </span><span title="To walk through the development of a simple WebExtension, see Your first WebExtension.">Berjalan melalui pengembangan WebExtension sederhana</span></span>, lihat <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Your_first_WebExtension">Your first WebExtension</a>.</li>
+</ul>
diff --git a/files/id/mozilla/add-ons/webextensions/api/browsersettings/index.html b/files/id/mozilla/add-ons/webextensions/api/browsersettings/index.html
new file mode 100644
index 0000000000..2372f738e0
--- /dev/null
+++ b/files/id/mozilla/add-ons/webextensions/api/browsersettings/index.html
@@ -0,0 +1,63 @@
+---
+title: browserSettings
+slug: Mozilla/Add-ons/WebExtensions/API/browserSettings
+translation_of: Mozilla/Add-ons/WebExtensions/API/browserSettings
+---
+<div>{{AddonSidebar}}</div>
+
+<div>Enables an extension to modify certain global browser settings. Each property of this API is a {{WebExtAPIRef("types.BrowserSetting", "BrowserSetting")}} object, providing the ability to modify a particular setting.</div>
+
+<div></div>
+
+<div>Because these are global settings, it's possible for extensions to conflict. See the documentation for <code><a href="/en-US/Add-ons/WebExtensions/API/types/BrowserSetting/set">BrowserSetting.set()</a></code> for details of how conflicts are handled.</div>
+
+<div></div>
+
+<div>
+<p>To use this API you need to have the "browserSettings" <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/permissions">permission</a>.</p>
+</div>
+
+<h2 id="Properties">Properties</h2>
+
+<dl>
+ <dt>{{WebExtAPIRef("browserSettings.allowPopupsForUserEvents")}}</dt>
+ <dd>Determines whether code running in web pages can display popups in response to user events.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.cacheEnabled")}}</dt>
+ <dd>Determines whether the browser cache is enabled or not.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.closeTabsByDoubleClick")}}</dt>
+ <dd>Determines whether the selected tab can be closed with a double click.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.contextMenuShowEvent")}}</dt>
+ <dd>Determines the mouse event that triggers a context menu popup.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.ftpProtocolEnabled")}}</dt>
+ <dd>Determines whether the FTP protocol is enabled.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.homepageOverride")}}</dt>
+ <dd>Read the value of the browser's home page.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.imageAnimationBehavior")}}</dt>
+ <dd>Determines how the browser treats animated images.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.newTabPageOverride")}}</dt>
+ <dd>Reads the value of the browser's new tab page.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.newTabPosition")}}</dt>
+ <dd>Controls the position of newly opened tabs relative to already open tabs.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.openBookmarksInNewTabs")}}</dt>
+ <dd>Determines whether bookmarks are opened in the current tab or a new tab.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.openSearchResultsInNewTabs")}}</dt>
+ <dd>Determines whether search results are opened in the current tab or a new tab.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.openUrlbarResultsInNewTabs")}}</dt>
+ <dd>Determines whether address bar autocomplete suggestions are opened in the current tab or a new tab.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.overrideDocumentColors")}}</dt>
+ <dd>Controls whether the user-chosen colors override the page's colors.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.useDocumentFonts")}}</dt>
+ <dd>Controls whether the browser will use the fonts specified by a web page or use only built-in fonts.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.webNotificationsDisabled")}}</dt>
+ <dd>Prevents websites from showing notifications using the <code><a href="/en-US/docs/Web/API/notification">Notification</a></code> Web API.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.zoomFullPage")}}</dt>
+ <dd>Controls whether zoom is applied to the entire page or to text only.</dd>
+ <dt>{{WebExtAPIRef("browserSettings.zoomSiteSpecific")}}</dt>
+ <dd>Controls whether page zoom is applied on a per-site or per-tab basis. If {{WebExtAPIRef("privacy.websites")}}<code>.resistFingerprinting</code> is true, this setting has no effect and zoom is applied on a per-tab basis.</dd>
+</dl>
+
+<h2 id="Browser_compatibility">Browser compatibility</h2>
+
+<p>{{Compat("webextensions.api.browserSettings")}}</p>
+
+<p>{{WebExtExamples("h2")}}</p>
diff --git a/files/id/mozilla/add-ons/webextensions/api/index.html b/files/id/mozilla/add-ons/webextensions/api/index.html
new file mode 100644
index 0000000000..9b63bd59e8
--- /dev/null
+++ b/files/id/mozilla/add-ons/webextensions/api/index.html
@@ -0,0 +1,50 @@
+---
+title: JavaScript APIs
+slug: Mozilla/Add-ons/WebExtensions/API
+tags:
+  - NeedsTranslation
+  - TopicStub
+translation_of: Mozilla/Add-ons/WebExtensions/API
+---
+<div>{{AddonSidebar}}</div>
+
+<div>
+<p>The WebExtension JavaScript APIs can be used inside the add-on's <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Anatomy_of_a_WebExtension#Background_scripts">background scripts</a> and in any <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/User_interface_components#Browser_actions">browser action</a> or <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/User_interface_components#Page_actions">page action</a> popups that the add-on defines. A few of these APIs can also be accessed by an add-on's <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Anatomy_of_a_WebExtension#Content_scripts">content scripts</a> (see the <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Content_scripts#WebExtension_APIs">list in the content script guide</a>).</p>
+
+<p>To use the more powerful APIs you need to <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/permissions">request permission</a> in your add-on's manifest.json.</p>
+
+<p>You can access the APIs using the <code>browser</code> namespace:</p>
+
+<pre class="brush: js line-numbers  language-js"><code class="language-js"><span class="keyword token">function</span> <span class="function token">logTabs</span><span class="punctuation token">(</span>tabs<span class="punctuation token">)</span> <span class="punctuation token">{</span>
+  console<span class="punctuation token">.</span><span class="function token">log</span><span class="punctuation token">(</span>tabs<span class="punctuation token">)</span><span class="punctuation token">;</span>
+<span class="punctuation token">}</span>
+
+browser<span class="punctuation token">.</span>tabs<span class="punctuation token">.</span><span class="function token">query</span><span class="punctuation token">(</span><span class="punctuation token">{</span>currentWindow<span class="punctuation token">:</span> <span class="keyword token">true</span><span class="punctuation token">}</span><span class="punctuation token">,</span> logTabs<span class="punctuation token">)</span><span class="punctuation token">;</span></code></pre>
+</div>
+
+<div>
+<p>Many of the APIs are asynchronous, returning a <code><a href="/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise">Promise</a></code>:</p>
+
+<pre class="brush: js line-numbers  language-js"><code class="language-js"><span class="keyword token">function</span> <span class="function token">logCookie</span><span class="punctuation token">(</span>c<span class="punctuation token">)</span> <span class="punctuation token">{</span>
+  console<span class="punctuation token">.</span><span class="function token">log</span><span class="punctuation token">(</span>c<span class="punctuation token">)</span><span class="punctuation token">;</span>
+<span class="punctuation token">}</span>
+
+<span class="keyword token">function</span> <span class="function token">logError</span><span class="punctuation token">(</span>e<span class="punctuation token">)</span> <span class="punctuation token">{</span>
+  console<span class="punctuation token">.</span><span class="function token">error</span><span class="punctuation token">(</span>e<span class="punctuation token">)</span><span class="punctuation token">;</span>
+<span class="punctuation token">}</span>
+
+<span class="keyword token">var</span> setCookie <span class="operator token">=</span> browser<span class="punctuation token">.</span>cookies<span class="punctuation token">.</span><span class="keyword token">set</span><span class="punctuation token">(</span>
+  <span class="punctuation token">{</span>url<span class="punctuation token">:</span> <span class="string token">"https://developer.mozilla.org/"</span><span class="punctuation token">}</span>
+<span class="punctuation token">)</span><span class="punctuation token">;</span>
+setCookie<span class="punctuation token">.</span><span class="function token">then</span><span class="punctuation token">(</span>logCookie<span class="punctuation token">,</span> logError<span class="punctuation token">)</span><span class="punctuation token">;</span></code></pre>
+</div>
+
+<div>
+<p>Note that this is different from Google Chrome's extension system, which uses the <code>chrome</code> namespace instead of <code>browser</code>, and which uses callbacks instead of promises for asynchronous functions. As a porting aid, the Firefox implementation of WebExtensions supports <code>chrome</code> and callbacks as well as <code>browser</code> and promises. Mozilla has also written a polyfill which enables code that uses <code>browser</code> and promises to work unchanged in Chrome: <a class="external external-icon" href="https://github.com/mozilla/webextension-polyfill">https://github.com/mozilla/webextension-polyfill</a>.</p>
+
+<p>Microsoft Edge uses the <code>browser</code> namespace, but doesn't yet support promise-based asynchronous APIs. In Edge, for the time being, asynchronous APIs must use callbacks.</p>
+
+<p>Not all browsers support all the APIs: for the details, see <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Browser_support_for_JavaScript_APIs">Browser support for JavaScript APIs</a>.</p>
+</div>
+
+<div>{{SubpagesWithSummaries}}</div>
diff --git a/files/id/mozilla/add-ons/webextensions/api/notifikasi/index.html b/files/id/mozilla/add-ons/webextensions/api/notifikasi/index.html
new file mode 100644
index 0000000000..e4fb084bb2
--- /dev/null
+++ b/files/id/mozilla/add-ons/webextensions/api/notifikasi/index.html
@@ -0,0 +1,62 @@
+---
+title: notifikasi
+slug: Mozilla/Add-ons/WebExtensions/API/notifikasi
+tags:
+  - API
+  - Add-ons
+  - Ekstensi
+  - Notifikasi
+  - WebExtensions
+translation_of: Mozilla/Add-ons/WebExtensions/API/notifications
+---
+<div>{{AddonSidebar}}</div>
+
+<p>Tampilkan pemberitahuan kepada pengguna, menggunakan mekanisme pemberitahuan sistem operasi yang mendasarinya. Karena API ini menggunakan mekanisme pemberitahuan sistem operasi, detail tentang bagaimana pemberitahuan muncul dan berperilaku mungkin berbeda sesuai dengan sistem operasi dan pengaturan pengguna.</p>
+
+<p>Untuk menggunakan API ini Anda harus memiliki izin "notifikasi"</p>
+
+<h2 id="Tipe">Tipe</h2>
+
+<dl>
+ <dt>{{WebExtAPIRef("notifications.NotificationOptions")}}</dt>
+ <dd>Menentukan isi pemberitahuan.</dd>
+ <dt>{{WebExtAPIRef("notifications.TemplateType")}}</dt>
+ <dd>Jenis pemberitahuan. Misalnya, ini menentukan apakah pemberitahuan dapat memuat gambar.</dd>
+</dl>
+
+<h2 id="Fungsi">Fungsi</h2>
+
+<dl>
+ <dt>{{WebExtAPIRef("notifications.clear()")}}</dt>
+ <dd>Hapus pemberitahuan khusus, berikan ID-nya.</dd>
+ <dt>{{WebExtAPIRef("notifications.create()")}}</dt>
+ <dd>Buat dan tampilkan pemberitahuan baru.</dd>
+ <dt>{{WebExtAPIRef("notifications.getAll()")}}</dt>
+ <dd>Dapatkan semua notifikasi.</dd>
+ <dt>{{WebExtAPIRef("notifications.update()")}}</dt>
+ <dd>Perbarui notifikasi</dd>
+</dl>
+
+<h2 id="Events">Events</h2>
+
+<dl>
+ <dt>{{WebExtAPIRef("notifications.onButtonClicked")}}</dt>
+ <dd>Dipecat ketika pengguna mengklik tombol di notifikasi.</dd>
+ <dt>{{WebExtAPIRef("notifications.onClicked")}}</dt>
+ <dd>Dipecat ketika pengguna mengklik pemberitahuan, tetapi tidak pada tombol.</dd>
+ <dt>{{WebExtAPIRef("notifications.onClosed")}}</dt>
+ <dd>Dipecat ketika pemberitahuan ditutup, baik oleh sistem atau karena pengguna memecatnya.</dd>
+ <dt>{{WebExtAPIRef("notifications.onShown")}}</dt>
+ <dd>Dipecat segera setelah pemberitahuan telah ditampilkan.</dd>
+</dl>
+
+<h2 id="Kompatibilitas_peramban">Kompatibilitas peramban</h2>
+
+<p>{{Compat("webextensions.api.notifications")}}</p>
+
+<p>{{WebExtExamples("h2")}}</p>
+
+<div class="note"><strong>Ucapan terima kasih</strong>
+
+<p>API ini berdasarkan pada API Chromium <a href="https://developer.chrome.com/extensions/notifications"><code>chrome.notifications</code></a>.</p>
+</div>
diff --git a/files/id/mozilla/add-ons/webextensions/api/windows/createtype/index.html b/files/id/mozilla/add-ons/webextensions/api/windows/createtype/index.html
new file mode 100644
index 0000000000..569dbc0b97
--- /dev/null
+++ b/files/id/mozilla/add-ons/webextensions/api/windows/createtype/index.html
@@ -0,0 +1,65 @@
+---
+title: windows.CreateType
+slug: Mozilla/Add-ons/WebExtensions/API/windows/CreateType
+translation_of: Mozilla/Add-ons/WebExtensions/API/windows/CreateType
+---
+<div>{{AddonSidebar()}}</div>
+
+<p>Menentukan jenis browser window yang akan dibuat.</p>
+
+<h2 id="Tipe">Tipe</h2>
+
+<p>Nilai dari tipe ini adalah <code>strings</code>. Nilai yang tersedia adalah:</p>
+
+<ul>
+ <li><code>"normal"</code></li>
+ <li><code>"popup"</code></li>
+ <li><code>"panel"</code></li>
+ <li><code>"detached_panel"</code></li>
+</ul>
+
+<h2 id="Browser_compatibility">Browser compatibility</h2>
+
+<p class="hidden">The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out <a href="https://github.com/mdn/browser-compat-data">https://github.com/mdn/browser-compat-data</a> and send us a pull request.</p>
+
+<p>{{Compat("webextensions.api.windows.CreateType")}}</p>
+
+<p>{{WebExtExamples}}</p>
+
+<div class="note"><strong>Acknowledgements</strong>
+
+<p>This API is based on Chromium's <a href="https://developer.chrome.com/extensions/windows#type-CreateType"><code>chrome.windows</code></a> API. This documentation is derived from <a href="https://chromium.googlesource.com/chromium/src/+/master/chrome/common/extensions/api/windows.json"><code>windows.json</code></a> in the Chromium code.</p>
+
+<p>Microsoft Edge compatibility data is supplied by Microsoft Corporation and is included here under the Creative Commons Attribution 3.0 United States License.</p>
+</div>
+
+<div class="hidden">
+<pre>// Copyright 2015 The Chromium Authors. All rights reserved.
+//
+// Redistribution and use in source and binary forms, with or without
+// modification, are permitted provided that the following conditions are
+// met:
+//
+//    * Redistributions of source code must retain the above copyright
+// notice, this list of conditions and the following disclaimer.
+//    * Redistributions in binary form must reproduce the above
+// copyright notice, this list of conditions and the following disclaimer
+// in the documentation and/or other materials provided with the
+// distribution.
+//    * Neither the name of Google Inc. nor the names of its
+// contributors may be used to endorse or promote products derived from
+// this software without specific prior written permission.
+//
+// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+</pre>
+</div>
diff --git a/files/id/mozilla/add-ons/webextensions/api/windows/index.html b/files/id/mozilla/add-ons/webextensions/api/windows/index.html
new file mode 100644
index 0000000000..d0611824cd
--- /dev/null
+++ b/files/id/mozilla/add-ons/webextensions/api/windows/index.html
@@ -0,0 +1,127 @@
+---
+title: windows
+slug: Mozilla/Add-ons/WebExtensions/API/windows
+tags:
+  - API
+  - Add-ons
+  - Extensions
+  - Interface
+  - NeedsTranslation
+  - Non-standard
+  - Reference
+  - TopicStub
+  - WebExtensions
+  - Windows
+translation_of: Mozilla/Add-ons/WebExtensions/API/windows
+---
+<div>{{AddonSidebar}}</div>
+
+<p>Interact with browser windows. You can use this API to get information about open windows and to open, modify, and close windows. You can also listen for window open, close, and activate events.</p>
+
+<h2 id="Types">Types</h2>
+
+<dl>
+ <dt>{{WebExtAPIRef("windows.WindowType")}}</dt>
+ <dd>The type of browser window this is.</dd>
+ <dt>{{WebExtAPIRef("windows.WindowState")}}</dt>
+ <dd>The state of this browser window.</dd>
+ <dt>{{WebExtAPIRef("windows.Window")}}</dt>
+ <dd>Contains information about a browser window.</dd>
+ <dt>{{WebExtAPIRef("windows.CreateType")}}</dt>
+ <dd>Specifies the type of browser window to create.</dd>
+</dl>
+
+<h2 id="Properties">Properties</h2>
+
+<dl>
+ <dt>{{WebExtAPIRef("windows.WINDOW_ID_NONE")}}</dt>
+ <dd>The <code>windowId</code> value that represents the absence of a browser window.</dd>
+ <dt>{{WebExtAPIRef("windows.WINDOW_ID_CURRENT")}}</dt>
+ <dd>The <code>windowId</code> value that represents the current window.</dd>
+</dl>
+
+<h2 id="Functions">Functions</h2>
+
+<dl>
+ <dt>{{WebExtAPIRef("windows.get()")}}</dt>
+ <dd>Gets details about a window, given its ID.</dd>
+ <dt>{{WebExtAPIRef("windows.getCurrent()")}}</dt>
+ <dd>Gets the current window.</dd>
+ <dt>{{WebExtAPIRef("windows.getLastFocused()")}}</dt>
+ <dd>Gets the window that was most recently focused — typically the window 'on top'.</dd>
+ <dt>{{WebExtAPIRef("windows.getAll()")}}</dt>
+ <dd>Gets all windows.</dd>
+ <dt>{{WebExtAPIRef("windows.create()")}}</dt>
+ <dd>
+ <p>Creates a new window.</p>
+ </dd>
+ <dt>{{WebExtAPIRef("windows.update()")}}</dt>
+ <dd>Updates the properties of a window. Use this to move, resize, and (un)focus a window, etc.</dd>
+ <dt>{{WebExtAPIRef("windows.remove()")}}</dt>
+ <dd>Closes a window, and all its tabs.</dd>
+</dl>
+
+<h2 id="Events">Events</h2>
+
+<dl>
+ <dt>{{WebExtAPIRef("windows.onCreated")}}</dt>
+ <dd>Fired when a window is created.</dd>
+ <dt>{{WebExtAPIRef("windows.onRemoved")}}</dt>
+ <dd>Fired when a window is closed.</dd>
+ <dt>{{WebExtAPIRef("windows.onFocusChanged")}}</dt>
+ <dd>Fired when the currently focused window changes.</dd>
+</dl>
+
+<h2 id="Browser_compatibility">Browser compatibility</h2>
+
+<p>{{Compat("webextensions.api.windows")}}</p>
+
+<div class="hidden note">
+<p>The "Chrome incompatibilities" section is included from <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Chrome_incompatibilities"> https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Chrome_incompatibilities</a> using the <a href="/en-US/docs/Template:WebExtChromeCompat">WebExtChromeCompat</a> macro.</p>
+
+<p>If you need to update this content, edit <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Chrome_incompatibilities">https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Chrome_incompatibilities</a>, then shift-refresh this page to see your changes.</p>
+</div>
+
+<h3 id="Edge_incompatibilities">Edge incompatibilities</h3>
+
+<p>Promises are not supported in Edge. Use callbacks instead.</p>
+
+<p>{{WebExtExamples("h2")}}</p>
+
+<div class="note"><strong>Acknowledgements</strong>
+
+<p>This API is based on Chromium's <a href="https://developer.chrome.com/extensions/windows"><code>chrome.windows</code></a> API. This documentation is derived from <a href="https://chromium.googlesource.com/chromium/src/+/master/chrome/common/extensions/api/windows.json"><code>windows.json</code></a> in the Chromium code.</p>
+
+<p>Microsoft Edge compatibility data is supplied by Microsoft Corporation and is included here under the Creative Commons Attribution 3.0 United States License.</p>
+</div>
+
+<div class="hidden">
+<pre>// Copyright 2015 The Chromium Authors. All rights reserved.
+//
+// Redistribution and use in source and binary forms, with or without
+// modification, are permitted provided that the following conditions are
+// met:
+//
+//    * Redistributions of source code must retain the above copyright
+// notice, this list of conditions and the following disclaimer.
+//    * Redistributions in binary form must reproduce the above
+// copyright notice, this list of conditions and the following disclaimer
+// in the documentation and/or other materials provided with the
+// distribution.
+//    * Neither the name of Google Inc. nor the names of its
+// contributors may be used to endorse or promote products derived from
+// this software without specific prior written permission.
+//
+// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+</pre>
+</div>
diff --git a/files/id/mozilla/add-ons/webextensions/browser_support_for_javascript_apis/index.html b/files/id/mozilla/add-ons/webextensions/browser_support_for_javascript_apis/index.html
new file mode 100644
index 0000000000..96ab65479e
--- /dev/null
+++ b/files/id/mozilla/add-ons/webextensions/browser_support_for_javascript_apis/index.html
@@ -0,0 +1,21 @@
+---
+title: Browser support for JavaScript APIs
+slug: Mozilla/Add-ons/WebExtensions/Browser_support_for_JavaScript_APIs
+translation_of: Mozilla/Add-ons/WebExtensions/Browser_support_for_JavaScript_APIs
+---
+<div>{{AddonSidebar}}</div>
+
+
+
+<p>{{WebExtAllCompatTables}}</p>
+
+<div class="note"><strong>Acknowledgments</strong>
+
+<p>Microsoft Edge compatibility data is supplied by Microsoft Corporation and is included here under the Creative Commons Attribution 3.0 United States License.</p>
+</div>
+
+<h2 id="See_also">See also</h2>
+
+<ul>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Browser_compatibility_for_manifest.json">Browser compatibility for manifest.json</a></li>
+</ul>
diff --git a/files/id/mozilla/add-ons/webextensions/content_scripts/index.html b/files/id/mozilla/add-ons/webextensions/content_scripts/index.html
new file mode 100644
index 0000000000..da5a653034
--- /dev/null
+++ b/files/id/mozilla/add-ons/webextensions/content_scripts/index.html
@@ -0,0 +1,554 @@
+---
+title: Content scripts
+slug: Mozilla/Add-ons/WebExtensions/Content_scripts
+translation_of: Mozilla/Add-ons/WebExtensions/Content_scripts
+---
+<div>{{AddonSidebar}}</div>
+
+<p>A content script is a part of your extension that runs in the context of a particular web page (as opposed to background scripts which are part of the extension, or scripts which are part of the web site itself, such as those loaded using the {{HTMLElement("script")}} element).</p>
+
+<p><a href="/en-US/Add-ons/WebExtensions/Background_scripts">Background scripts</a> can access all the <a href="/en-US/Add-ons/WebExtensions/API">WebExtension JavaScript APIs</a>, but they can't directly access the content of web pages. So if your extension needs to do that, you need content scripts.</p>
+
+<p>Just like the scripts loaded by normal web pages, content scripts can read and modify the content of their pages using the standard DOM APIs.</p>
+
+<p>Content scripts can only access <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Content_scripts#WebExtension_APIs">a small subset of the WebExtension APIs</a>, but they can <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Content_scripts#Communicating_with_background_scripts">communicate with background scripts</a> using a messaging system, and thereby indirectly access the WebExtension APIs.</p>
+
+<div class="note">
+<p>Note that content scripts are blocked on the following domains:</p>
+
+<ul style="display: grid;">
+ <li>accounts-static.cdn.mozilla.net</li>
+ <li>accounts.firefox.com</li>
+ <li>addons.cdn.mozilla.net</li>
+ <li>addons.mozilla.org</li>
+ <li>api.accounts.firefox.com</li>
+ <li>content.cdn.mozilla.net</li>
+ <li>content.cdn.mozilla.net</li>
+ <li>discovery.addons.mozilla.org</li>
+ <li>input.mozilla.org</li>
+ <li>install.mozilla.org</li>
+ <li>oauth.accounts.firefox.com</li>
+ <li>profile.accounts.firefox.com</li>
+ <li>support.mozilla.org</li>
+ <li>sync.services.mozilla.com</li>
+ <li>testpilot.firefox.com</li>
+</ul>
+
+<p>If you try to inject a content script into a page in these domains, it fails and the page logs a <a href="/en-US/docs/Web/HTTP/CSP">CSP</a> error.</p>
+
+<p>Because these restrictions include addons.mozilla.org, users may attempt to use your extension immediately after installation—only to find that it doesn't work! You may want to add an appropriate warning, or an <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/onboarding_upboarding_offboarding_best_practices">onboarding page</a> to move users away from <code>addons.mozilla.org</code>.</p>
+</div>
+
+<div class="note">
+<p>Values added to the global scope of a content script with <code>let foo</code> or <code>window.foo = "bar"</code> may disappear due to bug <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1408996">1408996</a>.</p>
+</div>
+
+<h2 id="Loading_content_scripts">Loading content scripts</h2>
+
+<p>You can load a content script into a web page in one of three ways:</p>
+
+<ol>
+ <li>
+  <dl>
+   <dt>At install time, into pages that match URL patterns.</dt>
+   <dd>Using the <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/content_scripts">content_scripts</a></code> key in your <code>manifest.json</code>, you can ask the browser to load a content script whenever the browser loads a page whose URL <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Match_patterns">matches a given pattern</a>.</dd>
+  </dl>
+ </li>
+ <li>
+  <dl>
+   <dt>At runtime, into pages that match URL patterns.</dt>
+   <dd>Using the {{WebExtAPIRef("contentScripts")}} API, you can ask the browser to load a content script whenever the browser loads a page whose URL <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Match_patterns">matches a given pattern</a>. (This is similar to method 1, <em>except</em> that you can add and remove content scripts at runtime.)</dd>
+  </dl>
+ </li>
+ <li>
+  <dl>
+   <dt>At runtime, into specific tabs.</dt>
+   <dd>Using the <code><a href="/en-US/Add-ons/WebExtensions/API/Tabs/executeScript">tabs.executeScript()</a></code> API, you can load a content script into a specific tab whenever you want. (For example, in response to the user clicking on a <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Browser_action">browser action</a>.)</dd>
+  </dl>
+ </li>
+</ol>
+
+<p>There is only one global scope <em>per frame, per extension</em>. This means that variables from one content script can directly be accessed by another content script, regardless of how the content script was loaded.</p>
+
+<p>Using methods (1) and (2), you can only load scripts into pages whose URLs can be represented using a <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Match_patterns">match pattern</a>.</p>
+
+<p>Using method (3), you can also load scripts into pages packaged with your extension, but you can't load scripts into privileged browser pages (like "<code>about:debugging</code>" or "<code>about:addons</code>").</p>
+
+<h2 id="Content_script_environment">Content script environment</h2>
+
+<h3 id="DOM_access">DOM access</h3>
+
+<p>Content scripts can access and modify the page's DOM, just like normal page scripts can. They can also see any changes that were made to the DOM by page scripts.</p>
+
+<p>However, content scripts get a "clean" view of the DOM. This means:</p>
+
+<ul>
+ <li>Content scripts cannot see JavaScript variables defined by page scripts.</li>
+ <li>If a page script redefines a built-in DOM property, the content script sees the original version of the property, not the redefined version.</li>
+</ul>
+
+<p>In Firefox, this behavior is called <a href="/en-US/docs/Mozilla/Tech/Xray_vision">Xray vision</a>.</p>
+
+<p>Consider a web page like this:</p>
+
+<pre class="brush: html notranslate">&lt;!DOCTYPE html&gt;
+&lt;html&gt;
+  &lt;head&gt;
+    &lt;meta http-equiv="content-type" content="text/html; charset=utf-8" /&gt;
+  &lt;/head&gt;
+
+  &lt;body&gt;
+    &lt;script src="page-scripts/page-script.js"&gt;&lt;/script&gt;
+  &lt;/body&gt;
+&lt;/html&gt;</pre>
+
+<p>The script <code>page-script.js</code> does this:</p>
+
+<pre class="brush: js notranslate">// page-script.js
+
+// add a new element to the DOM
+let p = document.createElement("p");
+p.textContent = "This paragraph was added by a page script.";
+p.setAttribute("id", "page-script-para");
+document.body.appendChild(p);
+
+// define a new property on the window
+window.foo = "This global variable was added by a page script";
+
+// redefine the built-in window.confirm() function
+window.confirm = function() {
+  alert("The page script has also redefined 'confirm'");
+}</pre>
+
+<p>Now an extension injects a content script into the page:</p>
+
+<pre class="brush: js notranslate">// content-script.js
+
+// can access and modify the DOM
+let pageScriptPara = document.getElementById("page-script-para");
+pageScriptPara.style.backgroundColor = "blue";
+
+// can't see page-script-added properties
+console.log(window.foo);  // undefined
+
+// sees the original form of redefined properties
+window.confirm("Are you sure?"); // calls the original window.confirm()</pre>
+
+<p>The same is true in reverse; page scripts cannot see JavaScript properties added by content scripts.</p>
+
+<p>This means that content scripts can rely on DOM properties behaving predictably, without worrying about its variables clashing with variables from the page script.</p>
+
+<p>One practical consequence of this behavior is that a content script doesn't have access to any JavaScript libraries loaded by the page. So, for example, if the page includes jQuery, the content script can't see it.</p>
+
+<p>If a content script needs to use a JavaScript library, then the library itself should be injected as a content script <em>alongside</em> the content script that wants to use it:</p>
+
+<pre class="brush: json notranslate">"content_scripts": [
+  {
+    "matches": ["*://*.mozilla.org/*"],
+    "js": ["jquery.js", "content-script.js"]
+  }
+]</pre>
+
+<div class="blockIndicator note">
+<p><strong>Note:</strong> Firefox <em>does</em> provide some APIs that enable content scripts to access JavaScript objects created by page scripts, and to expose their own JavaScript objects to page scripts.</p>
+
+<p>See <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Sharing_objects_with_page_scripts">Sharing objects with page scripts</a> for more details.</p>
+</div>
+
+<h3 id="WebExtension_APIs">WebExtension APIs</h3>
+
+<p>In addition to the standard DOM APIs, content scripts can use the following WebExtension APIs:</p>
+
+<dl>
+ <dt>From <code><a href="/en-US/Add-ons/WebExtensions/API/extension">extension</a></code>:</dt>
+ <dd>
+ <ul>
+  <li><code><a href="/en-US/Add-ons/WebExtensions/API/extension#getURL()">getURL()</a></code></li>
+  <li><code><a href="/en-US/Add-ons/WebExtensions/API/extension#inIncognitoContext">inIncognitoContext</a></code></li>
+ </ul>
+ </dd>
+ <dt>From <code><a href="/en-US/Add-ons/WebExtensions/API/runtime">runtime</a></code>:</dt>
+ <dd>
+ <ul>
+  <li><code><a href="/en-US/Add-ons/WebExtensions/API/runtime#connect()">connect()</a></code></li>
+  <li><code><a href="/en-US/Add-ons/WebExtensions/API/runtime#getManifest()">getManifest()</a></code></li>
+  <li><code><a href="/en-US/Add-ons/WebExtensions/API/runtime#getURL()">getURL()</a></code></li>
+  <li><code><a href="/en-US/Add-ons/WebExtensions/API/runtime#onConnect">onConnect</a></code></li>
+  <li><code><a href="/en-US/Add-ons/WebExtensions/API/runtime#onMessage">onMessage</a></code></li>
+  <li><code><a href="/en-US/Add-ons/WebExtensions/API/runtime#sendMessage()">sendMessage()</a></code></li>
+ </ul>
+ </dd>
+ <dt>From <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/i18n">i18n</a></code>:</dt>
+ <dd>
+ <ul>
+  <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/i18n/getMessage">getMessage()</a></code></li>
+  <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/i18n/getAcceptLanguages">getAcceptLanguages()</a></code></li>
+  <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/i18n/getUILanguage">getUILanguage()</a></code></li>
+  <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/i18n/detectLanguage">detectLanguage()</a></code></li>
+ </ul>
+ </dd>
+ <dt>From <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/menus">menus</a></code>:</dt>
+ <dd>
+ <ul>
+  <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/menus/getTargetElement">getTargetElement</a></code></li>
+ </ul>
+ </dd>
+ <dt>Everything from:</dt>
+ <dd><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/storage">storage</a></code></dd>
+</dl>
+
+<h3 id="XHR_and_Fetch">XHR and Fetch</h3>
+
+<p>Content scripts can make requests using the normal <code><a href="/en-US/docs/Web/API/XMLHttpRequest">window.XMLHttpRequest</a></code> and <code><a href="/en-US/docs/Web/API/Fetch_API">window.fetch()</a></code> APIs.</p>
+
+<div class="blockIndicator note">
+<p>In Firefox, content script requests (for example, using <code><a href="/en-US/docs/Web/API/Fetch_API/Using_Fetch">fetch()</a></code>) happen in the context of an extension, so you must provide an absolute URL to reference page content.</p>
+
+<p>In Chrome, these requests happen in context of the page, so they are made to a relative URL.  For example, <code>/api</code> is sent to <code>https://<strong>«</strong><var>current page URL</var><strong>»</strong>/api</code>.</p>
+</div>
+
+<p>Content scripts get the same cross-domain privileges as the rest of the extension: so if the extension has requested cross-domain access for a domain using the <code><a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/permissions">permissions</a></code> key in <code>manifest.json</code>, then its content scripts get access that domain as well.</p>
+
+<p>This is accomplished by exposing more privileged XHR and fetch instances in the content script, which has the side-effect of not setting the <code><a href="/en-US/docs/Web/HTTP/Headers/Origin">Origin</a></code> and <code><a href="/en-US/docs/Web/HTTP/Headers/Referer">Referer</a></code> headers like a request from the page itself would; this is often preferable to prevent the request from revealing its cross-origin nature.</p>
+
+<div class="blockIndicator note">
+<p>In Firefox, extensions that need to perform requests that behave as if they were sent by the content itself can use  <code>content.XMLHttpRequest</code> and <code>content.fetch()</code> instead.</p>
+
+<p>For cross-browser extensions, the presence of these methods must be feature-detected.</p>
+</div>
+
+<h2 id="Communicating_with_background_scripts">Communicating with background scripts</h2>
+
+<p>Although content scripts can't directly use most of the WebExtension APIs, they can communicate with the extension's background scripts using the messaging APIs, and can therefore indirectly access all the same APIs that the background scripts can.</p>
+
+<p>There are two basic patterns for communicating between the background scripts and content scripts:</p>
+
+<ul>
+ <li>You can send <strong>one-off messages</strong> (with an optional response).</li>
+ <li>You can set up a <strong>longer-lived connection between the two sides</strong>, and use that connection to exchange messages.</li>
+</ul>
+
+<h3 id="One-off_messages">One-off messages</h3>
+
+<p>To send one-off messages, with an optional response, you can use the following APIs:</p>
+
+<table class="fullwidth-table standard-table">
+ <thead>
+  <tr>
+   <th scope="row"></th>
+   <th scope="col">In content script</th>
+   <th scope="col">In background script</th>
+  </tr>
+ </thead>
+ <tbody>
+  <tr>
+   <th scope="row">Send a message</th>
+   <td><code><a href="/en-US/Add-ons/WebExtensions/API/runtime/sendMessage">browser.runtime.sendMessage()</a></code></td>
+   <td><code><a href="/en-US/Add-ons/WebExtensions/API/Tabs/sendMessage">browser.tabs.sendMessage()</a></code></td>
+  </tr>
+  <tr>
+   <th scope="row">Receive a message</th>
+   <td><code><a href="/en-US/Add-ons/WebExtensions/API/runtime/onMessage">browser.runtime.onMessage</a></code></td>
+   <td><code><a href="/en-US/Add-ons/WebExtensions/API/runtime/onMessage">browser.runtime.onMessage</a></code></td>
+  </tr>
+ </tbody>
+</table>
+
+<p>For example, here's a content script that listens for click events in the web page.</p>
+
+<p>If the click was on a link, it sends a message to the background page with the target URL:</p>
+
+<pre class="brush: js notranslate">// content-script.js
+
+window.addEventListener("click", notifyExtension);
+
+function notifyExtension(e) {
+  if (e.target.tagName != "A") {
+    return;
+  }
+  browser.runtime.sendMessage({"url": e.target.href});
+}</pre>
+
+<p>The background script listens for these messages and displays a notification using the <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/notifications">notifications</a></code> API:</p>
+
+<pre class="brush: js notranslate">// background-script.js
+
+browser.runtime.onMessage.addListener(notify);
+
+function notify(message) {
+  browser.notifications.create({
+    "type": "basic",
+    "iconUrl": browser.extension.getURL("link.png"),
+    "title": "You clicked a link!",
+    "message": message.url
+  });
+}
+</pre>
+
+<p>(This example code is lightly adapted from the <a href="https://github.com/mdn/webextensions-examples/tree/master/notify-link-clicks-i18n">notify-link-clicks-i18n</a> example on GitHub.)</p>
+
+<h3 id="Connection-based_messaging">Connection-based messaging</h3>
+
+<p>Sending one-off messages can get cumbersome if you are exchanging a lot of messages between a background script and a content script. So an alternative pattern is to establish a longer-lived connection between the two contexts, and use this connection to exchange messages.</p>
+
+<p>Both sides have a <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/Port">runtime.Port</a></code> object, which they can use to exchange messages.</p>
+
+<p>To create the connection:</p>
+
+<ul>
+ <li>One side listens for connections using <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/onConnect">runtime.onConnect</a></code></li>
+ <li>The other side calls:
+  <ul>
+   <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/tabs/connect">tabs.connect()</a></code> (if connecting to a content script)</li>
+   <li><code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/connect">runtime.connect()</a></code> (if connecting to a background script)</li>
+  </ul>
+ </li>
+</ul>
+
+<p>This returns a <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/Port">runtime.Port</a></code> object.</p>
+
+<ul>
+ <li>The <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/onConnect">runtime.onConnect</a></code> listener gets passed its own <code><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/Port">runtime.Port</a></code> object.</li>
+</ul>
+
+<p>Once each side has a port, the two sides can:</p>
+
+<ul>
+ <li>Send messages using <code>runtime.Port.postMessage()</code></li>
+ <li>Receive messages using <code>runtime.Port.onMessage()</code></li>
+</ul>
+
+<p>For example, as soon as it loads, the following content script:</p>
+
+<ul>
+ <li>Connects to the background script</li>
+ <li>Stores the <code>Port</code> in a variable <code>myPort</code></li>
+ <li>Listens for messages on <code>myPort</code>  (and logs them)</li>
+ <li>Uses <code>myPort</code> to sends messages to the background script when the user clicks the document</li>
+</ul>
+
+<pre class="brush: js notranslate">// content-script.js
+
+let myPort = browser.runtime.connect({name:"port-from-cs"});
+myPort.postMessage({greeting: "hello from content script"});
+
+myPort.onMessage.addListener(function(m) {
+  console.log("In content script, received message from background script: ");
+  console.log(m.greeting);
+});
+
+document.body.addEventListener("click", function() {
+  myPort.postMessage({greeting: "they clicked the page!"});
+});</pre>
+
+<p>The corresponding background script:</p>
+
+<ul>
+ <li>Listens for connection attempts from the content script</li>
+ <li>When receiving a connection attempt:
+  <ul>
+   <li>Stores the port in a variable named <code>portFromCS</code></li>
+   <li>Sends the content script a message using the port</li>
+   <li>Starts listening to messages received on the port, and logs them</li>
+  </ul>
+ </li>
+ <li>Sends messages to the content script, using <code>portFromCS</code>, when the user clicks the extension's browser action</li>
+</ul>
+
+<pre class="brush: js notranslate">// background-script.js
+
+let portFromCS;
+
+function connected(p) {
+  portFromCS = p;
+  portFromCS.postMessage({greeting: "hi there content script!"});
+  portFromCS.onMessage.addListener(function(m) {
+    portFromCS.postMessage({greeting: "In background script, received message from content script:" + m.greeting});
+  });
+}
+
+browser.runtime.onConnect.addListener(connected);
+
+browser.browserAction.onClicked.addListener(function() {
+  portFromCS.postMessage({greeting: "they clicked the button!"});
+});
+</pre>
+
+<h4 id="Multiple_content_scripts">Multiple content scripts</h4>
+
+<p>If you have multiple content scripts communicating at the same time, you might want to store connections to them in an array.</p>
+
+<ul>
+</ul>
+
+<pre class="brush: js notranslate">// background-script.js
+
+let ports = []
+
+function connected(p) {
+  ports[p.sender.tab.id] = p
+  //...
+}
+
+browser.runtime.onConnect.addListener(connected)
+
+browser.browserAction.onClicked.addListener(function() {
+  ports.forEach( p =&gt; {
+        p.postMessage({greeting: "they clicked the button!"})
+    })
+});
+</pre>
+
+<ul>
+</ul>
+
+<h3 id="Choosing_between_one-off_messages_and_connection-based_messaging">Choosing between one-off messages and connection-based messaging</h3>
+
+<p>The choice between one-off and connection-based messaging depends on how your extension expects to make use of messaging.</p>
+
+<p>The recommended best practices are:</p>
+
+<dl>
+ <dt>Use one-off messages when…</dt>
+ <dd>
+ <ul>
+  <li>Only one response is expected to a message.</li>
+  <li>A small number of scripts listen to receive messages ({{WebExtAPIRef("runtime.onMessage")}} calls).</li>
+ </ul>
+ </dd>
+ <dt>Use connection-based messaging when…</dt>
+ <dd>
+ <ul>
+  <li>Scripts engage in sessions where multiple messages are exchanged.</li>
+  <li>The extension need to know about task progress, needs to know if a task is interrupted, or may want to interrupt a task initiated using messaging.</li>
+ </ul>
+ </dd>
+</dl>
+
+<h2 id="Communicating_with_the_web_page">Communicating with the web page</h2>
+
+<p>By default, content scripts don't get access to objects created by page scripts. However, they can communicate with page scripts using the DOM <code><a href="/en-US/docs/Web/API/Window/postMessage">window.postMessage</a></code> and <code><a href="/en-US/docs/Web/API/EventTarget/addEventListener">window.addEventListener</a></code> APIs.</p>
+
+<p>For example:</p>
+
+<pre class="brush: js notranslate">// page-script.js
+
+let messenger = document.getElementById("from-page-script");
+
+messenger.addEventListener("click", messageContentScript);
+
+function messageContentScript() {
+  window.postMessage({
+    direction: "from-page-script",
+    message: "Message from the page"
+  }, "*");
+}
+</pre>
+
+<pre class="brush: js notranslate">// content-script.js
+
+window.addEventListener("message", function(event) {
+  if (event.source == window &amp;&amp;
+      event.data &amp;&amp;
+      event.data.direction == "from-page-script") {
+    alert("Content script received message: \"" + event.data.message + "\"");
+  }
+});</pre>
+
+<p>For a complete working example of this, <a href="https://mdn.github.io/webextensions-examples/content-script-page-script-messaging.html">visit the demo page on GitHub</a> and follow the instructions.</p>
+
+<div class="warning">
+<p><strong>Be very careful when interacting with untrusted web content in this manner!</strong> Extensions are privileged code which can have powerful capabilities and hostile web pages can easily trick them into accessing those capabilities.</p>
+
+<p>To give a trivial example, suppose the content script code that receives the message does something like this:</p>
+
+<pre class="brush: js example-bad notranslate">// content-script.js
+
+window.addEventListener("message", function(event) {
+  if (event.source == window &amp;&amp;
+      event.data.direction   &amp;&amp;
+      event.data.direction == "from-page-script") {
+    eval(event.data.message);
+  }
+});</pre>
+
+<p>Now the page script can run any code with all the privileges of the content script.</p>
+</div>
+
+<h2 id="Using_eval_in_content_scripts">Using <code>eval()</code> in content scripts</h2>
+
+<dl>
+ <dt>In Chrome</dt>
+ <dd>{{jsxref("eval")}} always runs code in the context of the <strong>content script</strong>, not in the context of the page.</dd>
+ <dt>In Firefox</dt>
+ <dd>
+ <p>If you call <code>eval()</code>, it runs code in the context of the <strong>content script</strong>.</p>
+
+ <p>If you call <code>window.eval()</code>, it runs code in the context of the <strong>page</strong>.</p>
+ </dd>
+</dl>
+
+<p>For example, consider a content script like this:</p>
+
+<pre class="brush: js notranslate">// content-script.js
+
+window.eval('window.x = 1;');
+eval('window.y = 2');
+
+console.log(`In content script, window.x: ${window.x}`);
+console.log(`In content script, window.y: ${window.y}`);
+
+window.postMessage({
+  message: "check"
+}, "*");</pre>
+
+<p>This code just creates some variables <code><var>x</var></code> and <code><var>y</var></code> using <code>window.eval()</code> and <code>eval()</code>,  logs their values, and then messages the page.</p>
+
+<p>On receiving the message, the page script logs the same variables:</p>
+
+<pre class="brush: js notranslate">window.addEventListener("message", function(event) {
+  if (event.source === window &amp;&amp; event.data &amp;&amp; event.data.message === "check") {
+    console.log(`In page script, window.x: ${window.x}`);
+    console.log(`In page script, window.y: ${window.y}`);
+  }
+});</pre>
+
+<dl>
+ <dt>In Chrome, this produces output like this:</dt>
+ <dd>
+ <pre class="notranslate">In content script, window.x: 1
+In content script, window.y: 2
+In page script, window.x: undefined
+In page script, window.y: undefined</pre>
+ </dd>
+ <dt>In Firefox, this produces output like this:</dt>
+ <dd>
+ <pre class="notranslate">In content script, window.x: undefined
+In content script, window.y: 2
+In page script, window.x: 1
+In page script, window.y: undefined</pre>
+ </dd>
+</dl>
+
+<p>The same applies to <code><a href="/en-US/docs/Web/API/WindowOrWorkerGlobalScope/setTimeout">setTimeout()</a></code>, <code><a href="/en-US/docs/Web/API/WindowOrWorkerGlobalScope/setInterval">setInterval()</a></code>, and <code><a href="/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function">Function()</a></code>.</p>
+
+<div class="blockIndicator warning">
+<p><strong>Be very careful when running code in the context of the page!</strong> </p>
+
+<p>The page's environment is controlled by potentially malicious web pages, which can redefine objects you interact with to behave in unexpected ways:</p>
+
+<pre class="brush: js example-bad notranslate">// page.js redefines console.log
+
+let original = console.log;
+
+console.log = function() {
+  original(true);
+}
+</pre>
+
+
+<pre class="brush: js example-bad notranslate">// content-script.js calls the redefined version
+
+window.eval('console.log(false)');
+</pre>
+</div>
diff --git a/files/id/mozilla/add-ons/webextensions/index.html b/files/id/mozilla/add-ons/webextensions/index.html
new file mode 100644
index 0000000000..a486f8391c
--- /dev/null
+++ b/files/id/mozilla/add-ons/webextensions/index.html
@@ -0,0 +1,91 @@
+---
+title: WebExtensions
+slug: Mozilla/Add-ons/WebExtensions
+tags:
+  - NeedsTranslation
+  - TopicStub
+translation_of: Mozilla/Add-ons/WebExtensions
+---
+<div>{{AddonSidebar}}</div>
+
+<p>WebExtensions adalah sistem cross-browser untuk mengembangkan browser add-ons. Untuk sebagian besar API tersebut kompatibel dengan <a class="external-icon external" href="https://developer.chrome.com/extensions">extension API</a> yang didukung oleh Google Chrome dan Opera. Ekstensi ditulis untuk browser ini dalam banyak kasus akan berjalan di Firefox atau <a href="https://developer.microsoft.com/en-us/microsoft-edge/platform/documentation/extensions/">Microsoft Edge</a> hanya dengan <a href="/en-US/Add-ons/WebExtensions/Porting_from_Google_Chrome">beberapa perubahan</a>. API ini juga sepenuhnya kompatibel dengan <a href="/en-US/Firefox/Multiprocess_Firefox">multiprocess Firefox</a>.</p>
+
+<p>Kami juga berniat untuk memperpanjang API untuk mendukung kebutuhan para pengembang, jadi jika Anda memiliki ide, kami akan senang mendengar mereka. Anda dapat menghubungi kami <a href="https://mail.mozilla.org/listinfo/dev-addons">dev-addons mailing list</a> atau <a href="irc://irc.mozilla.org/webextensions">#webextensions</a> di <a href="https://wiki.mozilla.org/IRC">IRC</a>.</p>
+
+<div class="row topicpage-table">
+<div class="section">
+<h3 id="Memulai">Memulai</h3>
+
+<ul>
+ <li><a href="/en-US/Add-ons/WebExtensions/What_are_WebExtensions">Apa Itu WebExtensions?</a></li>
+ <li><a href="/en-US/Add-ons/WebExtensions/Your_first_WebExtension">WebExtension Pertama Anda</a></li>
+ <li><a href="/en-US/Add-ons/WebExtensions/Your_second_WebExtension">WebExtension Kedua Anda</a></li>
+ <li><a href="/en-US/Add-ons/WebExtensions/Anatomy_of_a_WebExtension">Anatomi dari WebExtension</a></li>
+ <li><a href="/en-US/Add-ons/WebExtensions/Examples">Contoh WebExtensions</a></li>
+</ul>
+
+<h3 id="Bagaimana">Bagaimana</h3>
+
+<ul>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Intercept_HTTP_requests">Menangkap HTTP requests</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Modify_a_web_page">Merubah halaman web</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Add_a_button_to_the_toolbar">Menambah button ke toolbar</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Implement_a_settings_page">Implementasi pengaturan halaman</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Interact_with_the_clipboard">Interaksi dengan clipboard</a></li>
+ <li>Memanipulasi tab browser</li>
+ <li>Akses dan modifikasi bookmarks</li>
+ <li>Akses dan modifikasi cookies</li>
+</ul>
+
+<h3 id="Konsep">Konsep</h3>
+
+<ul>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API">Meninjau JavaScript API</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/User_interface_components">Komponen User interface</a></li>
+ <li><a href="/en-US/Add-ons/WebExtensions/Content_scripts">Content scripts</a></li>
+ <li><a href="/en-US/Add-ons/WebExtensions/Match_patterns">Match patterns</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Internationalization">Internasionalisasi</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_Security_Policy">Content Security Policy</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_messaging">Native messaging</a></li>
+</ul>
+
+<h3 id="Porting">Porting</h3>
+
+<ul>
+ <li><a href="/en-US/Add-ons/WebExtensions/Porting_from_Google_Chrome">Porting  ekstensi Google Chrome</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Porting_a_legacy_Firefox_add-on">Porting legacy Firefox add-on</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Embedded_WebExtensions">Embedded WebExtensions</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Comparison_with_the_Add-on_SDK">Perbandingan dengan the Add-on SDK</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Comparison_with_XUL_XPCOM_extensions">Perbandingan dengan XUL/XPCOM extensions</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Chrome_incompatibilities">Chrome incompatibilities</a></li>
+</ul>
+
+<h3 id="Alur_Kerja_Firefox">Alur Kerja Firefox</h3>
+
+<ul>
+ <li><a href="/en-US/Add-ons/WebExtensions/Temporary_Installation_in_Firefox">Pemasangan</a></li>
+ <li><a href="/en-US/Add-ons/WebExtensions/Debugging">Debugging</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Getting_started_with_web-ext">Memulai dengan web-ext</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/web-ext_command_reference">Referensi perintah web-ext</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/WebExtensions_and_the_Add-on_ID">WebExtensions dan Add-on ID</a></li>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Publishing_your_WebExtension">Penerbitan WebExtension anda</a></li>
+</ul>
+</div>
+
+<div class="section">
+<h3 id="Reference">Reference</h3>
+
+<ul>
+ <li><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/API">JavaScript API overview</a></li>
+ <li><a href="/en-US/Add-ons/WebExtensions/Browser_support_for_JavaScript_APIs">Browser compatibility tables for JavaScript APIs</a></li>
+</ul>
+
+<h4 id="JavaScript_APIs">JavaScript APIs</h4>
+
+<div class="twocolumns">{{ ListSubpages ("/en-US/Add-ons/WebExtensions/API") }}</div>
+
+<h4 id="Manifest_keys">Manifest keys</h4>
+
+<div class="twocolumns">{{ ListSubpages ("/en-US/Add-ons/WebExtensions/manifest.json") }}</div>
+</div>
+</div>
diff --git a/files/id/mozilla/add-ons/webextensions/your_first_webextension/index.html b/files/id/mozilla/add-ons/webextensions/your_first_webextension/index.html
new file mode 100644
index 0000000000..27204f8504
--- /dev/null
+++ b/files/id/mozilla/add-ons/webextensions/your_first_webextension/index.html
@@ -0,0 +1,153 @@
+---
+title: WebExtensions Pertama Anda
+slug: Mozilla/Add-ons/WebExtensions/Your_first_WebExtension
+translation_of: Mozilla/Add-ons/WebExtensions/Your_first_WebExtension
+---
+<div>{{AddonSidebar}}</div>
+
+<p><span id="result_box" lang="id"><span>Dalam</span> <span>artikel ini kita</span> <span>akan</span> mulai <span>menciptakan</span> <span>WebExtension</span> <span>untuk</span> <span>Firefox</span><span>,</span> <span>dari awal sampai akhir</span><span>.</span> <span>add</span><span>-on</span> ini <span>hanya menambahkan</span> <span>garis</span> <span>merah untuk</span> <span>setiap</span> <span>halaman</span> <span>yang dimuat dari</span> <span>"</span><span>mozilla.org</span><span>"</span> <span>atau</span> <span>subdomainnya</span><span>.</span></span></p>
+
+<p><span class="short_text" id="result_box" lang="id"><span>Kode sumber untuk</span> <span>contoh ini</span> <span>ada pada</span> <span>GitHub</span></span>: <a href="https://github.com/mdn/webextensions-examples/tree/master/borderify">https://github.com/mdn/webextensions-examples/tree/master/borderify</a>.</p>
+
+<p>Pertama, anda membutuhkan Firefox versi 45 atau lebih baru.</p>
+
+<h2 id="Menulis_sebuah_WebExtension">Menulis sebuah WebExtension</h2>
+
+<p>Buat sebuah directory baru dan arahkan kesana:</p>
+
+<pre class="brush: bash">mkdir borderify
+cd borderify</pre>
+
+<h3 id="manifest.json">manifest.json</h3>
+
+<p>Sekarang buat file baru dengan nama "manifest.json" di dalam folder "borderify". Berikan kode seperti berikut:</p>
+
+<pre class="brush: json">{
+
+  "manifest_version": 2,
+  "name": "Borderify",
+  "version": "1.0",
+
+  "description": "Adds a red border to all webpages matching mozilla.org.",
+
+  "icons": {
+    "48": "icons/border-48.png"
+  },
+
+  "content_scripts": [
+    {
+      "matches": ["*://*.mozilla.org/*"],
+      "js": ["borderify.js"]
+    }
+  ]
+
+}</pre>
+
+<ul>
+ <li>Tiga key pertama: <code><a href="/en-US/Add-ons/WebExtensions/manifest.json/manifest_version">manifest_version</a></code>, <code><a href="/en-US/Add-ons/WebExtensions/manifest.json/name">name</a></code>, dan <code><a href="/en-US/Add-ons/WebExtensions/manifest.json/version">version</a></code>, <span id="result_box" lang="id"><span>adalah wajib</span> <span>dan mengandung</span> <span>metadata</span> <span>dasar</span> <span>untuk</span> <span>add</span><span>-on</span></span>.</li>
+ <li><code><a href="/en-US/Add-ons/WebExtensions/manifest.json/description">description</a></code> <span id="result_box" lang="id"><span>adalah</span> <span>opsional</span><span>,</span> <span>tetapi dianjurkan</span><span>:</span> <span>ini akan ditampilkan</span> <span>dalam</span> <span>Add-ons</span> Manager</span>.</li>
+ <li><code><a href="/en-US/Add-ons/WebExtensions/manifest.json/icons">icons</a></code> <span id="result_box" lang="id"><span>adalah opsional</span><span>,</span> <span>tetapi</span> <span>dianjurkan</span><span>:</span> <span>memungkinkan</span> <span>Anda untuk menentukan</span> <span>sebuah ikon</span> <span>untuk</span> <span>add-on</span><span>,</span> <span>yang akan ditampilkan</span> <span>dalam</span></span> Add-ons Manager.</li>
+</ul>
+
+<p><span class="short_text" id="result_box" lang="id"><span>Kunci </span></span><span class="short_text" lang="id"><span>yang paling menarik</span> <span> di sini adalah</span></span> <code><a href="/en-US/Add-ons/WebExtensions/manifest.json/content_scripts">content_scripts</a></code>, <span id="result_box" lang="id"><span>yang memberitahu</span> <span>Firefox</span> <span>untuk memuat</span></span> script ke Halaman web dengan URL yang cocok dengan pola tertentu. Dalam hal ini, Kita akan meminta Firefox untuk memuat script yang di disebut "borderify.js" ke semua halaman HTTP atau HTTPS yang disajikan dari "mozilla.org" atau subdomainnya.</p>
+
+<ul>
+ <li><a href="/en-US/Add-ons/WebExtensions/Content_scripts">Learn more about content scripts.</a></li>
+ <li><a href="/en-US/Add-ons/WebExtensions/Match_patterns">Learn more about match patterns</a>.</li>
+</ul>
+
+<div class="note">
+<p>Jika anda menggunakan Firefox versi 48 kebawah, <span id="result_box" lang="id"><span>Anda</span> <span>juga</span> <span>akan</span> <span>memerlukan key</span> <span>tambahan yang disebut</span></span> <code><a href="/en-US/Add-ons/WebExtensions/manifest.json/applications">applications</a></code>:</p>
+
+<pre class="brush: json">"applications": {
+  "gecko": {
+    "id": "borderify@example.com",
+    "strict_min_version": "42.0",
+    "strict_max_version": "50.*",
+    "update_url": "https://example.com/updates.json"
+  }
+}</pre>
+</div>
+
+<h3 id="iconsborder-48.png">icons/border-48.png</h3>
+
+<p>Add-on <span id="result_box" lang="id"><span>harus memiliki</span> <span>ikon</span><span>.</span> <span>Ini</span> <span>akan ditampilkan</span> <span>di sebelah</span> <span>list add-on</span> <span>di</span></span> Add-ons Manager. Manifest.json menjanjikan <span id="result_box" lang="id"><span>bahwa kita akan memiliki</span> <span>ikon di</span></span> "icons/border-48.png".</p>
+
+<p>Membuat sebuah folder "ikon" pada folder "borderify". Simpan ikon dengan nama "border-48.png".  Anda dapat menggunakan <a href="https://github.com/mdn/webextensions-examples/blob/master/borderify/icons/border-48.png">salah satu dari contoh kami</a>, <span id="result_box" lang="id"><span>yang</span> <span>diambil dari</span> <span>ikon</span></span> Google Material Design iconset, <span id="result_box" lang="id"><span>dan</span> <span>digunakan di bawah</span> <span>ketentuan lisensi</span></span> <a href="https://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-ShareAlike</a>.</p>
+
+<p><span id="result_box" lang="id"><span>Jika</span> <span>Anda memilih</span> <span>untuk menggunakan</span> <span>ikon</span> <span>Anda sendiri</span><span>,</span> <span>itu</span> <span>harus</span> <span>berukuran</span> <span>48x48 pixel</span><span>.</span> <span>Anda</span> <span>juga bisa menggunakan</span> <span>ikon</span> <span>96x96</span> <span>pixel</span><span>,</span> <span>untuk</span> <span>display resolusi tinggi</span><span>,</span> <span>dan jika</span> <span>Anda</span> <span>melakukan hal ini</span> <span>akan</span> <span>ditentukan</span> <span>property</span> <span>96</span> <span>milik</span> <span>ikon</span> <span>objek</span> <span>di</span> <span>manifest.json</span></span>:</p>
+
+<pre class="brush: json">"icons": {
+  "48": "icons/border-48.png",
+  "96": "icons/border-96.png"
+}</pre>
+
+<p><span id="result_box" lang="id"><span>Atau, Anda bisa</span> <span>menggunakan</span> <span>file</span> <span>SVG</span><span>,</span> <span>dan itu</span> <span>akan</span> <span>ditingkatkan</span> <span>dengan benar</span><span>.</span></span></p>
+
+<ul>
+ <li><a href="/en-US/Add-ons/WebExtensions/manifest.json/icons">Learn more about specifying icons.</a></li>
+</ul>
+
+<h3 id="borderify.js">borderify.js</h3>
+
+<p><span id="result_box" lang="id"><span>Akhirnya</span><span>,</span> <span>buat file dengan nama</span> <span>"</span><span>borderify.js</span><span>"</span> pada folder <span>"</span><span>borderify</span><span>"</span><span>.</span> Berikan kode seperti berikut<span>:</span></span></p>
+
+<pre class="brush: js">document.body.style.border = "5px solid red";</pre>
+
+<p><span id="result_box" lang="id"><span>Script ini</span> <span>akan dimuat</span> <span>ke dalam</span> <span>halaman</span> <span>yang cocok dengan</span> <span>pola yang diberikan</span> <span>dalam key</span> <span>content_scripts pada</span> <span>manifest.json</span><span>.</span> <span>Script</span> <span>memiliki akses langsung ke</span> <span>dokumen</span><span>,</span> <span>seperti</span> <span>script</span> <span>dimuat oleh</span> <span>halaman itu sendiri</span></span>.</p>
+
+<ul>
+ <li><a href="/en-US/Add-ons/WebExtensions/Content_scripts">Learn more about content scripts.</a></li>
+</ul>
+
+<h2 id="Trying_it_out">Trying it out</h2>
+
+<p><span id="result_box" lang="id"><span>Pertama</span><span>,</span> <span>periksa</span> <span>bahwa Anda memiliki</span> <span>file</span> <span>yang tepat</span> <span>di tempat yang tepat</span><span>:</span></span></p>
+
+<pre>borderify/
+    icons/
+        border-48.png
+    borderify.js
+    manifest.json</pre>
+
+<h3 id="Pemasangan">Pemasangan</h3>
+
+<p>Buka "about:debugging" di Firefox, klik "Load Temporary Add-on" dan pilih file pada folder add-on anda:</p>
+
+<p>{{EmbedYouTube("cer9EUKegG4")}}</p>
+
+<p>Add-on <span id="result_box" lang="id"><span class="alt-edited">kini akan</span> <span>diinstal</span><span>,</span> <span>dan</span> <span>akan</span> <span class="alt-edited">tetap sampai</span> <span>Anda me-restart</span> <span>Firefox</span></span>.</p>
+
+<p><span id="result_box" lang="id"><span>Atau, Anda dapat</span> <span>menjalankan</span> <span>WebExtension</span> <span>dari baris perintah</span> <span>menggunakan </span></span><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Getting_started_with_web-ext">web-ext</a> tool.</p>
+
+<h3 id="Testing">Testing</h3>
+
+<p><span id="result_box" lang="id"><span>Sekarang</span> <span>coba kunjungi</span> <span>halaman</span> <span>dengan domain</span> <span>"</span><span>mozilla.org</span><span>"</span><span>,</span> <span>dan</span> <span>Anda akan melihat</span> <span>garis merah</span> <span>melingkar pada</span> <span>halaman:</span></span></p>
+
+<p>{{EmbedYouTube("rxBQl2Z9IBQ")}}</p>
+
+<div class="note">
+<p><span id="result_box" lang="id"><span>Jangan</span> <span>mencobanya pada</span> <span>addons.mozilla.org</span><span>!</span> <span>skrip</span> <span>konten</span> <span>saat ini</span> <span>diblokir pada</span> <span>domain tersebut.</span></span>.</p>
+</div>
+
+<p><span id="result_box" lang="id"><span>Coba</span> <span>bereksperimen</span> <span>sedikit</span><span>.</span> <span>Edit</span> script <span>konten</span> <span>untuk mengubah</span> <span>warna garis</span><span>,</span> <span>atau melakukan</span> <span>sesuatu yang lain untuk</span> <span>konten halaman</span><span>.</span> <span>Simpan</span> <span>script konten</span><span>,</span> <span>kemudian muat kembali</span> <span>file</span> <span>add</span><span>-on</span> <span>dengan mengklik</span> <span>button "</span><span>Reload</span><span>" pada</span> about<span>:</span><span>debugging</span><span>.</span> <span>Anda</span> <span>dapat</span> <span>melihat perubahan</span> <span>segera.</span></span></p>
+
+<p>{{EmbedYouTube("NuajE60jfGY")}}</p>
+
+<ul>
+ <li><a href="/en-US/Add-ons/WebExtensions/Temporary_Installation_in_Firefox">Learn more about loading add-ons</a></li>
+</ul>
+
+<h2 id="Packaging_dan_publishing">Packaging dan publishing</h2>
+
+<p><span id="result_box" lang="id"><span>Bagi orang lain yang akan untuk</span> <span>menggunakan</span> <span>add</span><span>-on</span><span>, Anda</span> <span>perlu memaketkan</span> <span>itu</span> <span>dan</span> <span>mengirimkannya ke</span> <span>Mozilla</span> <span>untuk</span> <span>penandaan</span><span>.</span> <span>Untuk mempelajari lebih lanjut</span> <span>tentang itu</span><span>, lihat</span></span> <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Publishing_your_WebExtension">"Publishing your WebExtension"</a>.</p>
+
+<h2 id="Apa_berikutnya"><span class="short_text" id="result_box" lang="id"><span>Apa berikutnya?</span></span></h2>
+
+<p><span id="result_box" lang="id"><span>Sekarang</span> <span>Anda punya</span> <span>ide dari</span> <span>proses pengembangan</span> <span>WebExtension</span> <span>untuk</span> <span>Firefox</span><span>, coba:</span></span></p>
+
+<ul>
+ <li><a href="/en-US/Add-ons/WebExtensions/Anatomy_of_a_WebExtension">reading more about the anatomy of WebExtensions</a></li>
+ <li><a href="/en-US/Add-ons/WebExtensions/Your_second_WebExtension">writing a more complex WebExtension</a></li>
+ <li><a href="/en-US/Add-ons/WebExtensions/API">reading about the JavaScript APIs available to WebExtensions.</a></li>
+</ul>
diff --git a/files/id/mozilla/connect/index.html b/files/id/mozilla/connect/index.html
new file mode 100644
index 0000000000..e9d3f28280
--- /dev/null
+++ b/files/id/mozilla/connect/index.html
@@ -0,0 +1,95 @@
+---
+title: Connect with Mozilla
+slug: Mozilla/Connect
+translation_of: Mozilla/Connect
+---
+<div class="summary">
+<p><span class="seoSummary"><font><font>Aktifkan, menginspirasi dan berkolaborasi untuk membuat Web platform utama yang digunakan untuk menciptakan pengalaman di semua perangkat yang terhubung.</font></font></span></p>
+</div>
+
+
+<div>
+<div class="column-container dev-program-callouts dev-program-block dev-program-first dev-program-column-wrapper">
+<div class="dev-program-callout">
+<div class="callout-link-container">
+<h2 id="Blog_Hacks"><font><font>Blog Hacks</font></font></h2>
+
+<p><font><font>Sebuah sumber daya utama bagi orang untuk mengembangkan Open Web, blog Mozilla Hacks menawarkan berita dan diskusi tentang terbaru dalam teknologi Web dan fitur browser.</font></font></p>
+
+<div class="callout-link-wrapper"><a class="callout-link ignore-external" href="https://hacks.mozilla.org/" style="white-space: normal;"><font><font>Baca sekarang</font></font> </a></div>
+</div>
+</div>
+
+<div class="dev-program-callout">
+<div class="callout-link-container">
+<h2 id="Bantuan_Q_A"><font><font>Bantuan Q &amp; A</font></font></h2>
+
+<p><font><font>Diskusikan Web dan Web aplikasi pada Stack Overflow, di mana Anda dapat bertukar pikiran dengan pengembang web lainnya. </font><span class="smaller"><strong><font>{{anch ("diskusi Developer", "Cari Q &amp; A di bawah")}}</font></strong></span></font></p>
+
+<div class="callout-link-wrapper"><a class="callout-link ignore-external" href="http://stackoverflow.com/r/mozilla" style="white-space: normal;"><font><font>Mozilla Q &amp; A pada Stack Overflow</font></font> </a></div>
+</div>
+</div>
+
+<div class="dev-program-callout">
+<div class="callout-link-container">
+<h2 id="Bergabunglah_MDN"><font><font>Bergabunglah MDN</font></font></h2>
+
+<p><font><font>Mendaftar untuk MDN! </font><font>Anda akan dapat mengedit dokumentasi di sini, membuat profil untuk memamerkan pekerjaan Anda, dan mendapatkan akses ke fitur dari waktu ke waktu seperti yang kita menggulung mereka keluar.</font></font></p>
+
+<div class="callout-link-wrapper"><a class="callout-link" href="/profile/edit" style="white-space: normal;"><font><font>Bergabung atau masuk</font></font> </a></div>
+</div>
+</div>
+</div>
+
+<div class="dev-program-explanation dev-program-block">
+<h2 id="Terhubung_dengan_Mozilla"><font><font>Terhubung dengan Mozilla</font></font></h2>
+
+<p><font><font>Pengembang menciptakan masa depan dengan membangun layanan dan aplikasi untuk orang di seluruh dunia. </font><font>Tujuan Hubungan Pengembang Mozilla adalah untuk membantu pengembang untuk menggunakan teknologi web terbuka dan standar untuk berhasil dalam mencapai tujuan mereka. </font><font>Selain dokumentasi di sini di MDN, kami menawarkan bantuan dan sumber lainnya menuju tujuan ini, melalui berbagai saluran. </font><font>Kami mengundang Anda untuk menghubungkan, belajar, dan berbagi pengetahuan Anda sendiri.</font></font></p>
+
+<p><font><font>Kami menawarkan bantuan melalui Q &amp; A pada Stack Overflow, untuk memecahkan masalah teknis yang spesifik dan tantangan yang mungkin Anda miliki. </font><font>Kami juga memiliki newsletter menjaga Anda informasi tentang kejadian terbaru dalam adegan web sekitar aplikasi web dan banyak lagi. </font></font><a href="https://marketplace.firefox.com/developers/#newsletter-signup"><font><font>Langganan Apps &amp; Hacks buletin.</font></font></a></p>
+
+<p><font><font>Kami memiliki banyak rencana dan ide-ide untuk iteratif memperluas Hubungan Pengembang penawaran kami, dan kami ingin Anda terlibat seperti yang kita melakukannya! </font><font>Jadi, </font></font><a href="http://stackoverflow.com/r/mozilla"><font><font>ikuti tag pada Stack Overflow</font></font></a><font><font> , </font></font><a href="https://hacks.mozilla.org/"><font><font>berlangganan ke blog Hacks</font></font></a><font><font> , </font></font><a href="https://marketplace.firefox.com/developers/#newsletter-signup"><font><font>berlangganan newsletter,</font></font></a><font><font> dan </font></font><a href="/profile/edit"><font><font>mendaftar untuk sebuah account</font></font></a><font><font> !</font></font></p>
+</div>
+
+<div class="column-container dev-program-block">
+<div class="column-half" id="Developer_discussions">
+<h2 id="Q_A_pada_Stack_Overflow_Lihat_semua_Q_A_..."><font><font>Q &amp; A pada Stack Overflow </font></font><a class="heading-link" href="http://stackoverflow.com/r/mozilla"><font><font>Lihat semua Q &amp; A ...</font></font></a></h2>
+
+<p><font><font>Kami memiliki Q &amp; A untuk membahas tantangan dan masalah ketika mengembangkan, khususnya untuk Firefox OS dan Open Web di ponsel. </font><font>Ini tersedia di Stack Overflow di bawah URL mudah </font></font><a href="http://stackoverflow.com/r/mozilla"><font><font>http://stackoverflow.com/r/mozilla</font></font></a><font><font> .</font></font></p>
+
+
+<div class="stack-form"><font><font>Bentuk Stack</font></font></div>
+
+<h3 id="Terbaru_Q_A_Topik"><font><font>Terbaru Q &amp; A Topik</font></font></h3>
+</div>
+
+<div class="column-half dev-program-hacks dev-program-block"> </div>
+</div>
+
+<p class="dev-program-block"><img alt="Pengembang pada lokakarya Firefox OS di Madrid." src="https://mdn.mozillademos.org/files/7479/PhonesUp.jpg" style="display: block; height: 359px; margin: 0px auto; max-width: 100%; width: 720px;"></p>
+
+<div class="column-container dev-program-block">
+<div class="column-7 dev-program-events">
+<h2 id="Dimana_Mozilla_Lihat_peserta_dan_rincian_pada_halaman_Acara_kami_..."><font><font>Dimana Mozilla? </font></font><a class="heading-link" href="https://developer.mozilla.org/en/events"><font><font>Lihat peserta dan rincian pada halaman Acara kami ...</font></font> </a></h2>
+
+<p><font><font>Berikut ini adalah daftar peristiwa di mana perwakilan Mozilla akan berbicara. </font><font>Pastikan untuk berbicara dengan mereka!</font></font></p>
+</div>
+
+<div class="column-5">
+<h2 id="Sumber_lainnya"><font><font>Sumber lainnya</font></font></h2>
+
+<ul class="no-bullets">
+ <li><a href="http://www.youtube.com/user/mozhacks"><font><font>Mozilla Hacks di YouTube</font></font></a>
+
+  <ul>
+   <li><a href="http://www.youtube.com/playlist?list=PLo3w8EB99pqIHIUUv08hBCHq1OgPKhdo0"><font><font>Video Firefox OS</font></font></a></li>
+   <li><a href="http://www.youtube.com/playlist?list=PLo3w8EB99pqLZNY22xKbTEzMfYo9PXAlm"><font><font>Firefox Developer Tools video</font></font></a></li>
+  </ul>
+ </li>
+ <li><a href="https://twitter.com/mozhacks"><font><font>mozhacks di Twitter</font></font></a></li>
+</ul>
+</div>
+</div>
+</div>
+
+<p> </p>
diff --git a/files/id/mozilla/firefox/edisi_pengembang/index.html b/files/id/mozilla/firefox/edisi_pengembang/index.html
new file mode 100644
index 0000000000..6f3a9a91bf
--- /dev/null
+++ b/files/id/mozilla/firefox/edisi_pengembang/index.html
@@ -0,0 +1,57 @@
+---
+title: Edisi Pengembang
+slug: Mozilla/Firefox/Edisi_Pengembang
+translation_of: Mozilla/Firefox/Developer_Edition
+---
+<div>{{FirefoxSidebar}}</div><p><img alt="" src="https://mdn.mozillademos.org/files/9069/firefox-dev-ed_logo-only_1024.png" style="display: block; height: 256px; margin-left: auto; margin-right: auto; width: 256px;"></p>
+
+<p style="text-align: center;">Sebuah versi Firefox yang dikhususkan untuk para web developer.</p>
+
+<p><a href=" https://www.mozilla.org/en-US/firefox/developer/" style="width: 250px; display: block; margin-left: auto; margin-right: auto; padding: 10px; text-align: center; border-radius: 4px; background-color: #81BC2E; white-space: nowrap; color: white; text-shadow: 0px 1px 0px rgba(0, 0, 0, 0.25); box-shadow: 0px 1px 0px 0px rgba(0, 0, 0, 0.2), 0px -1px 0px 0px rgba(0, 0, 0, 0.3) inset;">Unduh Firefox Edisi Pengembang</a></p>
+
+<hr>
+<div class="column-container">
+<div class="column-half">
+<h3 id="Fitur_Firefox_terbaru"><strong>Fitur Firefox</strong> terbaru</h3>
+
+<p>Firefox Edisi Pengembang menggantikan kanal Aurora pada <a href="https://wiki.mozilla.org/Release_Management/Release_Process">Proses Rilis Firefox</a>. Seperti Aurora, fitur-fitur baru akan tersedia pada versi ini setiap enam minggu, setelah distabilkan dari Nightly build.</p>
+
+<p>Dengan menggunakan Edisi Pengembang, anda mendapatkan akses ke fitur peralatan dan platform 12 minggu lebih awal dari rilis Firefox utama.</p>
+
+<p><a href="/en-US/Firefox/Releases/35">Temukan apa yang baru dalam Edisi Pengembang</a>.</p>
+</div>
+
+<div class="column-half">
+<h3 id="Peralatan_pengembang_eksperimental"><strong>Peralatan pengembang eksperimental</strong></h3>
+
+<p>Kami akan memasukkan fitur-fitur eksperimental yang belum masuk di versi biasa.</p>
+
+<p>Sebagai contoh, Edisi Pengembang memasukkan <a href="/en-US/docs/Tools/Firefox_Tools_Adapter">Firefox Tools Adapter</a>, yang dapat membuat anda terhubung dengan<a href="/en-US/docs/"> peralatan pengembang Firefox</a> ke browser lain seperti Chrome pada Android atau Safari di iOS.</p>
+</div>
+</div>
+
+<div class="column-container">
+<div class="column-half">
+<h3 id="Profil_terpisah"><strong>Profil terpisah</strong></h3>
+
+<p>Firefox Edisi Pengembang menggunakan profil terpisah dari versi Firefox lain yang terinstall di komputer anda. Artinya, anda bisa menjalankan Edisi Pengembang bersamaan dengan Firefox versi biasa atau Beta.</p>
+</div>
+
+<div class="column-half">
+<h3 id="Dibuat_untuk_pengembang_web"><strong>Dibuat untuk pengembang web</strong></h3>
+
+<p>Kami telah mengatur beberapa pengaturan untuk pengembang web. Sebagai contoh, chrome dan debug remote telah diaktifkan dari awal.</p>
+</div>
+</div>
+
+<div class="column-container">
+<div class="column-half">
+<h3 id="Tema_tersendiri"><strong>Tema tersendiri</strong></h3>
+
+<p>Termasuk di dalamnya akses cepat ke fitur pengembang.</p>
+</div>
+
+<div class="column-half"> </div>
+</div>
+
+<p> </p>
diff --git a/files/id/mozilla/firefox/index.html b/files/id/mozilla/firefox/index.html
new file mode 100644
index 0000000000..cf3e7acc66
--- /dev/null
+++ b/files/id/mozilla/firefox/index.html
@@ -0,0 +1,75 @@
+---
+title: Firefox
+slug: Mozilla/Firefox
+tags:
+  - Firefox
+  - Landing
+  - Mozilla
+translation_of: Mozilla/Firefox
+---
+<div>{{FirefoxSidebar}}</div>
+
+<p><span class="short_text" id="result_box" lang="id"><span class="hps"><a href="https://www.mozilla.org/firefox/">Firefox</a></span> <span class="hps">adalah peramban</span> <span class="hps">populer</span> milik <span class="hps">Mozilla</span></span>, tersedia untuk berbagai platforms, termasuk Windows, Mac OS X dan Linux pada desktop dan perangkat mobile Android. Dengan kompatibilitas luas, teknologi Web terbaru dan alat pengembangan yang kuat, <span id="result_box" lang="id"><span class="hps">Firefox</span> <span class="hps">adalah yang terbesar</span> <span class="hps">untuk </span><span class="hps">pengguna </span><span class="hps">dan pengembang</span> <span class="hps">web</span></span>.</p>
+
+<p>Firefox adalah sebuah proyek open sorce, <span id="result_box" lang="id"><span class="hps">sebagian besar</span> <span class="hps">kode ini</span> <span class="hps">disumbangkan oleh</span></span> komunitas besar relawan kami. <span id="result_box" lang="id"><span class="hps">Di sini Anda</span> <span class="hps">akan</span> <span class="hps">belajar cara</span> <span class="hps">untuk berkontribusi pada</span> <span class="hps">proyek</span> <span class="hps">Firefox</span> <span class="hps">dan Anda juga</span> <span class="hps">akan menemukan link ke</span> <span class="hps">informasi tentang</span> <span class="hps">pembuatan</span> <span id="result_box" lang="id"><span class="hps">add-ons</span></span> <span class="hps">Firefox</span></span>, memakai alat pengembang Firefox, dan tugas lainnya.</p>
+
+<div class="summary">
+<p><span class="short_text" id="result_box" lang="id"><span class="hps">Pelajari cara membuat</span> <span class="hps">add</span><span class="atn">-</span><span>ons</span> <span class="hps">Firefox</span></span>, <span id="result_box" lang="id"><span class="hps">cara mengembangkan</span> <span class="hps">dan membuat</span> <span class="hps">Firefox</span> <span class="hps">sendiri</span></span>, dan cara <span id="result_box" lang="id"><span class="hps">internal dari</span> <span class="hps">Firefox</span> <span class="hps">dan</span> <span class="hps">subproyek-nya</span> <span class="hps">bekerja</span></span>.</p>
+</div>
+
+<ul class="card-grid">
+ <li><span>Catatan rilis pengembang</span>
+
+  <p><a href="https://developer.mozilla.org/en-US/Firefox/Releases">Catatan rilis pengembang terfokus</a>; <span id="result_box" lang="id"><span class="hps">mempelajari </span><span class="hps">kemampuan baru untuk</span><span class="hps"> situs</span> <span class="hps">web</span> <span class="atn hps">dan add-</span><span>ons</span> <span class="hps">di</span> <span class="hps">setiap versi</span> <span class="hps">Firefox</span></span>.</p>
+ </li>
+ <li><span>Documentasi proyek</span>
+  <p><span id="result_box" lang="id"><span class="hps">Dapatkan</span> <span class="hps">informasi rinci</span> <span class="hps">tentang <a href="https://developer.mozilla.org/en-US/docs/Mozilla">internal</a></span><a href="https://developer.mozilla.org/en-US/docs/Mozilla"> <span class="hps">Firefox</span></a> <span class="hps">dan</span> <span class="hps"><em>build system</em>-nya</span></span>, <span id="result_box" lang="id"><span class="hps">sehingga Anda bisa</span> <span class="hps">menemukan jalan di sekitar</span><span class="hps"> kode</span></span>.</p>
+ </li>
+ <li><span>Panduan pengembang</span>
+  <p><a href="https://developer.mozilla.org/en-US/docs/Developer_Guide">Panduan pengembang</a> kami <span id="result_box" lang="id"><span class="hps">memberi</span> <span class="hps">rincian tentang bagaimana</span><span class="hps"> mendapatkan</span> <span class="hps">dan</span> <span class="hps">mengkompilasi source code </span></span>Firefox, <span id="result_box" lang="id"><span class="hps">bagaimana menemukan</span> <span class="hps">jalan anda</span></span>, dan <span class="short_text" id="result_box" lang="id"><span class="hps">bagaimana</span> <span class="hps">berkontribusi pada proyek</span></span>.</p>
+ </li>
+</ul>
+
+<h2 id="sect1"></h2>
+
+<h2 id="Channel_Firefox">Channel Firefox</h2>
+
+<p>Firefox tersedia dalam lima <strong>channel</strong>.</p>
+
+<h3 id="Firefox_Nightly">Firefox Nightly</h3>
+
+<p>Each night we build Firefox from the latest code in <a href="/en-US/docs/mozilla-central">mozilla-central</a>. These builds are for Firefox developers or those who want to try out the very latest cutting edge features while they're still under active development.</p>
+
+<p><a href="https://nightly.mozilla.org/" style="width: 250px; display: block; margin-left: auto; margin-right: auto; padding: 10px; text-align: center; border-radius: 4px; background-color: #81BC2E; white-space: nowrap; color: white; text-shadow: 0px 1px 0px rgba(0, 0, 0, 0.25); box-shadow: 0px 1px 0px 0px rgba(0, 0, 0, 0.2), 0px -1px 0px 0px rgba(0, 0, 0, 0.3) inset;">Download Firefox Nightly</a></p>
+
+<h3 id="Firefox_Developer_Edition">Firefox Developer Edition</h3>
+
+<p>This is a version of Firefox tailored for developers. Every six weeks, we take the features in Firefox Nightly that are stable enough and create a new version of Firefox Developer Edition. We also add some extra features for developers that are only available in this channel.</p>
+
+<p><a href="/en-US/Firefox/Developer_Edition">Learn more about Firefox Developer Edition</a>.</p>
+
+<p><a href="https://www.mozilla.org/firefox/developer/" style="width: 250px; display: block; margin-left: auto; margin-right: auto; padding: 10px; text-align: center; border-radius: 4px; background-color: #81BC2E; white-space: nowrap; color: white; text-shadow: 0px 1px 0px rgba(0, 0, 0, 0.25); box-shadow: 0px 1px 0px 0px rgba(0, 0, 0, 0.2), 0px -1px 0px 0px rgba(0, 0, 0, 0.3) inset;">Download Firefox Developer Edition</a></p>
+
+<h3 id="Firefox_Beta">Firefox Beta</h3>
+
+<p>After spending six weeks in Firefox Developer Edition, we take the features that are stable enough, and create a new version of Firefox Beta. Firefox Beta builds are for Firefox enthusiasts to test what's destined to become the next released Firefox version.</p>
+
+<p><a href="https://www.mozilla.org/firefox/channel/#beta" style="width: 250px; display: block; margin-left: auto; margin-right: auto; padding: 10px; text-align: center; border-radius: 4px; background-color: #81BC2E; white-space: nowrap; color: white; text-shadow: 0px 1px 0px rgba(0, 0, 0, 0.25); box-shadow: 0px 1px 0px 0px rgba(0, 0, 0, 0.2), 0px -1px 0px 0px rgba(0, 0, 0, 0.3) inset;">Download Firefox Beta</a></p>
+
+<h3 id="Firefox">Firefox</h3>
+
+<p>After stabilizing for another six weeks in Beta, we're ready to ship the new features to hundreds of millions of users in a new release version of Firefox.</p>
+
+<p><a href="https://www.mozilla.org/firefox/channel/#firefox" style="width: 250px; display: block; margin-left: auto; margin-right: auto; padding: 10px; text-align: center; border-radius: 4px; background-color: #81BC2E; white-space: nowrap; color: white; text-shadow: 0px 1px 0px rgba(0, 0, 0, 0.25); box-shadow: 0px 1px 0px 0px rgba(0, 0, 0, 0.2), 0px -1px 0px 0px rgba(0, 0, 0, 0.3) inset;">Download Firefox</a></p>
+
+<h3 id="Firefox_Extended_Support_Release_(ESR)">Firefox Extended Support Release (ESR)</h3>
+
+<p>Firefox ESR is the long-term support edition of Firefox for desktop for use by organizations including schools, universities, businesses and others who need extended support for mass deployments.</p>
+
+<p><a href="/en-US/Firefox/Firefox_ESR">Learn more about Firefox Extended Support Release</a>.</p>
+
+<p><a href="https://www.mozilla.org/firefox/organizations/all/" style="width: 250px; display: block; margin-left: auto; margin-right: auto; padding: 10px; text-align: center; border-radius: 4px; background-color: #81BC2E; white-space: nowrap; color: white; text-shadow: 0px 1px 0px rgba(0, 0, 0, 0.25); box-shadow: 0px 1px 0px 0px rgba(0, 0, 0, 0.2), 0px -1px 0px 0px rgba(0, 0, 0, 0.3) inset;">Download Firefox ESR</a></p>
+
+<h2 id="Firefox_profiles">Firefox profiles</h2>
+
+<p>If you find yourself using multiple Firefox channels—or just multiple configurations—on a regular basis, you should read how to <a href="/en-US/docs/Mozilla/Firefox/Multiple_profiles">use multiple Firefox profiles</a> by turning Firefox's Profile Manager and other profile management tools to your advantage.</p>
diff --git a/files/id/mozilla/firefox/privacy/index.html b/files/id/mozilla/firefox/privacy/index.html
new file mode 100644
index 0000000000..fe82422987
--- /dev/null
+++ b/files/id/mozilla/firefox/privacy/index.html
@@ -0,0 +1,22 @@
+---
+title: Privacy
+slug: Mozilla/Firefox/Privacy
+tags:
+  - NeedsTranslation
+  - Privacy
+  - Security
+  - TopicStub
+translation_of: Mozilla/Firefox/Privacy
+---
+<div>{{FirefoxSidebar}}</div>
+
+<p class="summary">This document lists privacy-related documentation.</p>
+
+<p>{{ ListSubpages () }}</p>
+
+<h2 id="See_also">See also</h2>
+
+<ul>
+ <li><a href="https://support.mozilla.org/en-US/products/firefox/privacy-and-security">Privacy and security settings</a></li>
+ <li><a href="https://developer.mozilla.org/en-US/docs/Web/Security">Web Security</a></li>
+</ul>
diff --git a/files/id/mozilla/firefox/privacy/storage_access_policy/errors/cookieblockedtracker/index.html b/files/id/mozilla/firefox/privacy/storage_access_policy/errors/cookieblockedtracker/index.html
new file mode 100644
index 0000000000..f4415aedc2
--- /dev/null
+++ b/files/id/mozilla/firefox/privacy/storage_access_policy/errors/cookieblockedtracker/index.html
@@ -0,0 +1,33 @@
+---
+title: 'Blocked: Storage access requests from trackers'
+slug: Mozilla/Firefox/Privacy/Storage_access_policy/Errors/CookieBlockedTracker
+translation_of: Mozilla/Firefox/Privacy/Storage_access_policy/Errors/CookieBlockedTracker
+---
+<div>{{FirefoxSidebar}}</div>
+
+<h2 id="back_up_from_last_user">back up from last user</h2>
+
+<h2 id="What_went_wrong">What went wrong?</h2>
+
+<p>A request to access cookies or storage was blocked because the browser identified it as coming from a tracker and content blocking is enabled.</p>
+
+<p>The permission can be changed or removed by:</p>
+
+<ul>
+ <li>Going to <em>Preferences &gt; Content Blocking </em>and either
+
+  <ul>
+   <li>adding an exception with the <em>Manage Exceptions</em>… button</li>
+   <li>choosing the <em>Custom</em> Content Blocking and unchecking the <em>Tracker</em> checkbox</li>
+  </ul>
+ </li>
+</ul>
+
+<p>If the blocked resource doesn't need authentication, you can fix the warning message by adding a <code>crossorigin="anonymous"</code> attribute to the relevant element.</p>
+
+<h2 id="See_also">See also</h2>
+
+<ul>
+ <li><a href="https://support.mozilla.org/en-US/kb/content-blocking">Content </a><a href="https://support.mozilla.org">support.mozilla.org</a></li>
+ <li><a href="/en-US/docs/Web/HTML/CORS_settings_attributes">The <code>crossorigin</code> attribute</a></li>
+</ul>
diff --git a/files/id/mozilla/firefox/privacy/storage_access_policy/errors/index.html b/files/id/mozilla/firefox/privacy/storage_access_policy/errors/index.html
new file mode 100644
index 0000000000..a1e1f54a75
--- /dev/null
+++ b/files/id/mozilla/firefox/privacy/storage_access_policy/errors/index.html
@@ -0,0 +1,24 @@
+---
+title: Errors
+slug: Mozilla/Firefox/Privacy/Storage_access_policy/Errors
+tags:
+  - Cookies
+  - Errors
+  - NeedsTranslation
+  - Storage
+  - TopicStub
+  - storage access policy
+translation_of: Mozilla/Firefox/Privacy/Storage_access_policy/Errors
+---
+<div>{{FirefoxSidebar}}</div>
+
+<p>This page lists the errors that can be raised due to Firefox's anti-tracking functionality, governed by the <a href="/en-US/docs/Mozilla/Firefox/Privacy/Storage_access_policy">Storage access policy</a>. You can find further information about them by clicking on the links below:</p>
+
+<p>A request to access cookies or storage was blocked because</p>
+
+<ul>
+ <li><a href="/en-US/docs/Mozilla/Firefox/Privacy/Storage_access_policy/Errors/CookieBlockedByPermission">of custom cookie permission</a></li>
+ <li><a href="/en-US/docs/Mozilla/Firefox/Privacy/Storage_access_policy/Errors/CookieBlockedTracker">it came from a tracker and content blocking is enabled</a></li>
+ <li><a href="/en-US/docs/Mozilla/Firefox/Privacy/Storage_access_policy/Errors/CookieBlockedAll">we are blocking all storage access requests</a></li>
+ <li><a href="/en-US/docs/Mozilla/Firefox/Privacy/Storage_access_policy/Errors/CookieBlockedForeign">we are blocking all third-party storage access requests and content blocking is enabled</a></li>
+</ul>
diff --git a/files/id/mozilla/firefox/privacy/storage_access_policy/index.html b/files/id/mozilla/firefox/privacy/storage_access_policy/index.html
new file mode 100644
index 0000000000..801d5bfad1
--- /dev/null
+++ b/files/id/mozilla/firefox/privacy/storage_access_policy/index.html
@@ -0,0 +1,261 @@
+---
+title: 'Storage access policy: Block cookies from trackers'
+slug: Mozilla/Firefox/Privacy/Storage_access_policy
+tags:
+  - NeedsTranslation
+  - Privacy
+  - TopicStub
+  - storage access policy
+  - tracking protection
+translation_of: Mozilla/Firefox/Privacy/Storage_access_policy
+---
+<div>{{FirefoxSidebar}}</div>
+
+<p class="summary">Firefox includes a new storage access policy that blocks cookies and other site data from third-party tracking resources. This policy is designed as an alternative to the <a href="/en-US/docs/Mozilla/Cookies_Preferences">older cookie policies</a>, which have been available in Firefox for many years. This policy protects against cross-site tracking while minimizing the site breakage associated with traditional cookie blocking. This article explains how the policy works and how you can test it.</p>
+
+<h2 id="Testing_in_Firefox">Testing in Firefox</h2>
+
+<p>This cookie policy has been available in Firefox since version 63. This documentation describes the policy that we intend to ship to Firefox Release users, but may not match what is implemented in the current Release version of Firefox. That's because we document new aspects of the policy as soon as they land in <a href="https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly">Firefox Nightly</a>, our pre-release channel. Firefox Nightly may also contain experimental features that we don't yet plan to ship to Release users; experimental features will not be included in this documentation, but may nevertheless impact the functionality of domains classified as trackers.</p>
+
+<p>We recommend sites test with <a href="https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly">Firefox Nightly</a>, as this includes the newest version of our protections. As described above, note that Nightly may include additional protections that end up getting removed or changed before they reach our Release users. We’ll keep this page updated with the newest information as we strengthen our protections.</p>
+
+<p>These protections are on by default in Nightly. The cookie policy can be enabled in other versions of Firefox through the <a href="https://support.mozilla.org/en-US/kb/content-blocking">Content Blocking settings</a> (these steps will vary by version; the linked documentation includes a dropdown to select the appropriate Firefox version).</p>
+
+<h3 id="Report_Broken_Sites">Report Broken Sites</h3>
+
+<p>If you find a website broken as a result of this change, file a bug under the Tracking Protection component within the Firefox product on <a href="https://bugzilla.mozilla.org/enter_bug.cgi?assigned_to=nobody%40mozilla.org&amp;blocked=1480137&amp;bug_file_loc=http%3A%2F%2F&amp;bug_ignored=0&amp;bug_severity=normal&amp;bug_status=NEW&amp;cf_fx_iteration=---&amp;cf_fx_points=---&amp;cf_platform_rel=---&amp;cf_status_firefox62=---&amp;cf_status_firefox63=---&amp;cf_status_firefox64=---&amp;cf_status_firefox_esr60=---&amp;cf_status_geckoview62=---&amp;cf_tracking_firefox62=---&amp;cf_tracking_firefox63=---&amp;cf_tracking_firefox64=---&amp;cf_tracking_firefox_esr60=---&amp;cf_tracking_firefox_relnote=---&amp;cf_tracking_geckoview62=---&amp;component=Tracking%20Protection&amp;contenttypemethod=list&amp;contenttypeselection=text%2Fplain&amp;defined_groups=1&amp;flag_type-203=X&amp;flag_type-37=X&amp;flag_type-41=X&amp;flag_type-5=X&amp;flag_type-607=X&amp;flag_type-721=X&amp;flag_type-737=X&amp;flag_type-748=X&amp;flag_type-787=X&amp;flag_type-799=X&amp;flag_type-800=X&amp;flag_type-803=X&amp;flag_type-835=X&amp;flag_type-846=X&amp;flag_type-855=X&amp;flag_type-864=X&amp;flag_type-914=X&amp;flag_type-916=X&amp;flag_type-929=X&amp;flag_type-930=X&amp;flag_type-933=X&amp;form_name=enter_bug&amp;maketemplate=Remember%20values%20as%20bookmarkable%20template&amp;op_sys=Unspecified&amp;priority=--&amp;product=Firefox&amp;rep_platform=Unspecified&amp;target_milestone=---&amp;version=unspecified">Bugzilla</a>. Alternatively you can report broken sites directly in Firefox by clicking "Report a Problem" in the Content Blocking section of the <a href="https://support.mozilla.org/en-US/kb/control-center-site-privacy-and-security-firefox">Control Center</a> (this shortcut may not be available in all versions of Firefox).</p>
+
+<h2 id="Tracking_protection_explained">Tracking protection explained</h2>
+
+<p>How does Firefox determine which resources are tracking resources?</p>
+
+<p>Firefox uses the Tracking Protection list to determine which resources are tracking resources. The Tracking Protection list is <a href="https://github.com/disconnectme/disconnect-tracking-protection/issues">maintained by Disconnect</a>. When the list is applied in Firefox, we make two important changes:</p>
+
+<ul>
+ <li>First, we only use the "Basic Protection" version of the list, which <a href="https://github.com/mozilla-services/shavar-prod-lists#blacklist">excludes some categories of trackers</a>. In the future, we may expand our protections to use the "Strict Protection" version of the list.</li>
+ <li>Second, Firefox uses an additional "<a href="https://github.com/mozilla-services/shavar-prod-lists/blob/master/disconnect-entitylist.json">entity list</a>", which prevents <a href="https://github.com/mozilla-services/shavar-prod-lists#entity-list">domains from being classified as trackers when they are loaded on a top-level site owned by the same organization</a>.</li>
+</ul>
+
+<p>Firefox uses the built-in <a href="https://support.mozilla.org/en-US/kb/tracking-protection">Tracking Protection</a> URL classifier to determine which resources match the tracking protection list. Domains are matched against the list in accordance with the <a href="https://developers.google.com/safe-browsing/v4/urls-hashing#suffixprefix-expressions">SafeBrowsing v4 specification</a>. Specifically, we check the exact hostname of the resource against the list, as well as the last four hostnames formed by starting with the last five components and successively removing the leading component. Consider the following examples:</p>
+
+<table class="standard-table">
+ <thead>
+  <tr>
+   <th scope="col">Hostname on the list</th>
+   <th scope="col">Hostname of resource</th>
+   <th scope="col">Matched</th>
+  </tr>
+ </thead>
+ <tbody>
+  <tr>
+   <td><code>example.com</code></td>
+   <td><code>example.com</code></td>
+   <td>Yes</td>
+  </tr>
+  <tr>
+   <td><code>example.com</code></td>
+   <td><code>a.b.example.com</code></td>
+   <td>Yes</td>
+  </tr>
+  <tr>
+   <td><code>blah.example.com</code></td>
+   <td><code>example.com</code></td>
+   <td>No</td>
+  </tr>
+  <tr>
+   <td><code>a.b.example.com</code></td>
+   <td><code>c.d.example.com</code></td>
+   <td>No</td>
+  </tr>
+  <tr>
+   <td><code>blah.example.com</code></td>
+   <td><code>foo.blah.example.com</code></td>
+   <td>Yes</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="What_does_the_storage_access_policy_block">What does the storage access policy block?</h2>
+
+<p>The storage access policy blocks resources identified as trackers from accessing their cookies and other site storage when they are loaded in a third-party context. This prevents those resources from retrieving tracking identifiers stored in cookies or site storage and using them to identify users across visits to multiple first parties. Specifically, Firefox does this by imposing the following restrictions:</p>
+
+<p>Cookies:</p>
+
+<ul>
+ <li>Block {{httpheader("Cookie")}} request headers and ignore {{httpheader("Set-Cookie")}} response headers.</li>
+ <li>Return an empty string for calls to {{domxref("Document.cookie")}} and ignore requests to set cookies via <code>Document.cookie</code>.</li>
+</ul>
+
+<p>DOM Storage:</p>
+
+<ul>
+ <li><a href="/en-US/docs/Web/API/Web_Storage_API">localStorage</a>: <code><a href="/en-US/docs/Web/API/Window/localStorage">Window.localStorage</a></code>: read and write attempts throw a <code>SecurityError</code> exception.  Prior to Firefox 70: <code><a href="/en-US/docs/Web/API/Window/localStorage">Window.localStorage</a></code> is <code>null</code>. Thus, attempts to read and write using this object will throw a <code>TypeError</code> exception.</li>
+ <li><a href="/en-US/docs/Web/API/Web_Storage_API">sessionStorage</a>: read and write attempts are permitted.</li>
+ <li><a href="/en-US/docs/Web/API/IndexedDB_API">IndexedDB</a>: read and write attempts throw a <code>SecurityError</code> exception.</li>
+</ul>
+
+<p>Messaging and Workers:</p>
+
+<ul>
+ <li><a href="/en-US/docs/Web/API/Broadcast_Channel_API">Broadcast Channel</a>: attempts to create a new {{domxref("BroadcastChannel")}} will throw a <code>SecurityError</code> exception.</li>
+ <li><a href="/en-US/docs/Web/API/Web_Workers_API">Shared Worker</a>: attempts to create a new {{domxref("SharedWorker")}} will throw a <code>SecurityError</code> exception.</li>
+ <li><a href="/en-US/docs/Web/API/Service_Worker_API">Service Worker</a>: attempts to create a new {{domxref("ServiceWorker")}} will throw a <code>SecurityError</code> exception.</li>
+</ul>
+
+<p>DOM Cache:</p>
+
+<ul>
+ <li>Calls to {{domxref("CacheStorage")}} will always reject with a <code>SecurityError</code>.</li>
+</ul>
+
+<p>Browser caches:</p>
+
+<ul>
+ <li>The <a href="/en-US/docs/Mozilla/HTTP_cache">HTTP cache</a>, the Image cache, and the <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Alt-Svc">Alternative Services (Alt-Svc) cache</a> are all partitioned for tracking resources, such that each top-level origin will have a separate partition and tracking resources on different top-level origins will be cached separate from each other.</li>
+</ul>
+
+<p>Network connections:</p>
+
+<ul>
+ <li><a href="https://wiki.mozilla.org/Security/Server_Side_TLS#Session_Resumption">TLS sessions</a> will not be resumed using a session ticket when an HTTPS connection is made to an embedded third-party resource that is classified as a tracker.</li>
+ <li><a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Connection_management_in_HTTP_1.x#Persistent_connections">HTTP connection reuse</a> by domains classified as trackers is limited to requests that occur under the same top-level origin. For example, a request for content from tracker.example on news.example will not reuse an HTTP connection with a request for content from tracker.example on shopping.example or with requests that occur when tracker.example is visited directly (i.e., as a first party).</li>
+</ul>
+
+<h3 id="What_is_not_blocked_by_the_policy">What is not blocked by the policy?</h3>
+
+<ol>
+ <li>This policy does not currently restrict third-party storage access for resources that are not classified as tracking resources. We may choose to apply additional restrictions to third-party storage access in the future.</li>
+ <li>The restrictions applied by the policy will not prevent third-party scripts classified as tracking resources from accessing storage in the main context of the page. These scripts can continue to use storage scoped to the top-level origin.</li>
+ <li>Origins classified as trackers will have access to their own storage when they are loaded in a first-party context.</li>
+ <li>Cross-origin resources loaded from the same eTLD+1 as the top-level context will still have access to their storage.</li>
+ <li>Origins normally classified as trackers will <a href="https://github.com/mozilla-services/shavar-prod-lists#entity-list">not be blocked if the top-level page origin is determined to be from the same organization as them</a>.</li>
+</ol>
+
+<h2 id="Storage_access_grants">Storage access grants</h2>
+
+<p>In order to improve web compatibility and permit third-party integrations that require storage access, Firefox will grant storage access scoped to the first party for a particular third-party origin as described in this section. Currently, Firefox includes some web compatibility heuristics that grant storage access to third-party resources classified as trackers when a user interacts with those third parties. We do this when we expect that not granting access would cause the web page to break. We also support an initial implementation of the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Storage_Access_API">Storage Access API</a>, through which embedded {{htmlelement("iframe")}}s can request storage access by calling {{domxref("Document.requestStorageAccess()")}}. Although both of these approaches provide the same level of storage access, we recommend third parties switch to using the Storage Access API in order to guarantee their access to storage.</p>
+
+<h3 id="Automatic_storage_access_upon_interaction">Automatic storage access upon interaction</h3>
+
+<p>In order to improve web compatibility, Firefox currently includes some heuristics to grant storage access automatically to third parties that receive user interaction. These heuristics are intended to allow some third-party integrations that are common on the web to continue to function. They are intended to be temporary and will be removed in a future version of Firefox. They should not be relied upon for current and future web development.</p>
+
+<p>Third-party storage access may be granted to resources that have been classified as tracking resources when a user gesture triggers a pop-up window that has <a href="/en-US/docs/Web/API/Window/opener">opener access</a> to the originating document. When that occurs, there are two possible ways a third-party origin can be granted access:</p>
+
+<ul>
+ <li>The origin of the resource that is initially loaded in the pop-up window is granted storage access on the opener document if that origin has received user interaction as a first party within the past 30 days.</li>
+ <li>After the initial resource is loaded in the pop-up window, the window may go through a series of redirects to other hosts. If a user interacts with the pop-up window following a redirect, the origin of the content loaded in the pop-up window is given storage access on the opener document.</li>
+</ul>
+
+<h3 id="Scope_of_storage_access">Scope of storage access</h3>
+
+<p>When storage access is granted, it is scoped to the origin of the opener document or subdomains of that origin. Access that is granted on the subdomain of an origin does not extend to the top-level origin. As an example, if a resource from <code>tracker.example</code> is granted storage access on <code>foo.example.com</code>, then <code>tracker.example</code> will be able to access its cookies on <code>bar.foo.example.com</code> but not <code>example.com</code>. Instead, if <code>tracker.example</code> were granted access on <code>example.com</code> it would be able to access its storage on <code>bar.foo.example.com</code>, <code>foo.example.com</code>, and <code>example.com</code>.</p>
+
+<p>When storage access is granted to <code>tracker.example</code> on <code>example.com</code>, all resources loaded from <code>tracker.example</code> on any top-level document loaded from <code>example.com</code> are immediately given storage access. This includes all resources loaded in the main context of the page, embedded <code>&lt;iframe&gt;</code>s, and resources loaded within embedded <code>&lt;iframe&gt;</code>s. Storage access is not extended to other resources loaded on <code>example.com</code> (e.g. <code>other-tracker.example</code>), nor to other first parties on which <code>tracker.example</code> is embedded (e.g. <code>example.org</code>).</p>
+
+<p>Storage access grants extend into the first level of nested contexts, but no further. This means that <code>&lt;iframe&gt;</code>s embedded in the main context of the page and loaded from a domain classified as a tracker will have full access to all storage locations accessible through JavaScript. Similarly, requests for resources loaded in <code>&lt;iframe&gt;</code>s embedded in the main context of the page will have access to HTTP cookies. However, further nested contexts, including but not limited to those from the origin classified as a tracker, will not be granted storage access.</p>
+
+<p>Consider the following embedding scenarios on a top-level page loaded from <code>example.com</code> on which <code>tracker.example</code> has been granted storage access.</p>
+
+<table class="standard-table">
+ <thead>
+  <tr>
+   <th scope="col">Embedding</th>
+   <th scope="col">tracker.example resource storage access</th>
+  </tr>
+ </thead>
+ <tbody>
+  <tr>
+   <td>An image is loaded from <code>tracker.example</code> and embedded in the main context of <code>example.com</code>.</td>
+   <td>HTTP: Yes<br>
+    JS: N/A</td>
+  </tr>
+  <tr>
+   <td><code>example.com</code> embeds an <code>&lt;iframe&gt;</code> from <code>example.org</code>. That <code>&lt;iframe&gt;</code> goes on to load an image from <code>tracker.example</code>.</td>
+   <td>HTTP: Yes<br>
+    JS: N/A</td>
+  </tr>
+  <tr>
+   <td><code>example.com</code> embeds an <code>&lt;iframe&gt;</code> from <code>example.org</code>. That <code>&lt;iframe&gt;</code> goes on to embed an <code>&lt;iframe&gt;</code> from <code>tracker.example</code>.</td>
+   <td>HTTP: Yes<br>
+    JS: No</td>
+  </tr>
+  <tr>
+   <td><code>example.com</code> embeds an <code>&lt;iframe&gt;</code> from <code>tracker.example</code>.</td>
+   <td>HTTP: Yes<br>
+    JS: Yes</td>
+  </tr>
+  <tr>
+   <td><code>example.com</code> embeds an <code>&lt;iframe&gt;</code> from <code>example.com</code> (same origin). The nested <code>&lt;iframe&gt;</code> embeds an <code>&lt;iframe&gt;</code> from <code>tracker.example</code>.</td>
+   <td>HTTP: Yes<br>
+    JS: No</td>
+  </tr>
+ </tbody>
+</table>
+
+<h3 id="Storage_access_expiration">Storage access expiration</h3>
+
+<p>The storage access grant expires after 30 days. Domains classified as tracking resources may be granted third-party storage access on multiple first parties, and the storage permission for each party expires independently. The above heuristics will also serve to extend the lifetime of a third-party storage permission on origins that have already been granted access.  Each time the heuristic is activated, or a success call to the Storage Access API is made, the pre-existing storage access expiration will be extended by 30 days, counting from the time the previous access was granted.</p>
+
+<p>Please note that in the future we expect to make changes to how long storage access will remain valid for.  As mentioned before, the way to know that you will be able to use storage as a third-party going forward will be using the Storage Access API.</p>
+
+<h2 id="Debugging">Debugging</h2>
+
+<p>We encourage site owners to test their sites, particularly those that rely on third-party content integrations. We’ve added several new features to Firefox to make testing easier.</p>
+
+<h3 id="Developer_Tools_notifications">Developer Tools notifications</h3>
+
+<p>The <a href="/en-US/docs/Tools/Network_Monitor">Network Monitor</a> in Firefox Developer Tools now includes an indicator for all resource requests that have been classified as tracking resources. This indicator is shown as a shield icon in the domain column. In the sample image below, <code>trackertest.org</code> is classified as a tracking resource, while the request to example.com is not.</p>
+
+<p><img alt="network requests in Firefox devtools indicating which ones are tracking resources with a small shield icon" src="https://mdn.mozillademos.org/files/16181/Screen_Shot_2018-09-21_at_10.34.22_AM.png" style="border-style: solid; border-width: 1px; display: block; height: 57px; margin: 0px auto; width: 600px;"></p>
+
+<h3 id="Adding_custom_domains_to_the_Tracking_Protection_list">Adding custom domains to the Tracking Protection list</h3>
+
+<p>Curious how things will work if a third-party domain on your site were classified as a tracker? We’ve added a preference that allows you to add custom domains to the Tracking Protection URL classifier. To do so:</p>
+
+<ol>
+ <li>Type <code>about:config</code> in your address bar. If you are presented with a page that warns you "This may void your warranty!", click "I accept the risk!"</li>
+ <li>Right click on the next page and click "New" &gt; "String".</li>
+ <li>For the preference name enter "urlclassifier.trackingAnnotationTable.testEntries".</li>
+ <li>For the preference value enter comma separated origins that you’d like to have classified as trackers. E.g. "example.net,example.org".</li>
+</ol>
+
+<div class="warning">
+<p><strong>Warning</strong>: Be sure to remove these entries after you have finished testing.</p>
+</div>
+
+<h2 id="FAQ">FAQ</h2>
+
+<p>This cookie policy has the potential to lead to site breakage, but has been designed to allow common third-party integrations to continue to work while preventing cross-site tracking. In this section we describe the functionality you can expect in different integration scenarios.</p>
+
+<h3 id="Will_this_storage_access_policy_block_ads_from_displaying_on_my_website">Will this storage access policy block ads from displaying on my website?</h3>
+
+<p>No — this feature only restricts access to cookies and site data that can be used to track users across websites. Blocking tracking identifiers does not prevent the display of advertisements.</p>
+
+<h3 id="I_use_a_third-party_analytics_service_that_is_classified_as_a_tracker._Will_I_still_receive_analytics_data">I use a third-party analytics service that is classified as a tracker. Will I still receive analytics data?</h3>
+
+<p>This depends on how the third-party analytics service is implemented. Third-party analytics providers will no longer be able to user their third-party storage to collect data. This means that providers using cookies which are scoped to their third-party domain, or local storage and other site data stored under their origin, will no longer have access to those identifiers across other websites.</p>
+
+<p>If these services are embedded into the main context of the page, they can continue to use first-party cookies and site storage to track users across page visits on that specific first-party domain.</p>
+
+<h3 id="I_use_third-party_services_for_social_login_like_and_share_button_integration._Will_my_users_still_be_able_to_make_use_of_these_services">I use third-party services for social login, like, and share button integration. Will my users still be able to make use of these services?</h3>
+
+<p>This depends on how the social integration is implemented. We expect that many of the popular social integrations will continue to function as they do under Firefox’s current cookie policy with some minor differences in the user experience.</p>
+
+<p>A social content provider that is classified as a tracker will not have access to their third-party cookies when the user first visits a new first party. Thus, the user may appear logged out to the service despite being logged in when they visit the provider’s website directly. Depending on the type of integration, the user may have to take some action to interact with the social content provider before the provider is given access to their cookies. For example:</p>
+
+<ul>
+ <li>For social login, the user may have to click a login button on the first party.</li>
+ <li>For social like or share buttons, the user will have to first interact with the button in a logged-out state. Once they do, many social content providers will prompt them to log in.</li>
+</ul>
+
+<p>After these interactions, the provider will receive third-party storage access if they prompt the user in a way that is captured by the storage access activation heuristics described above. These providers should consider switching to explicitly request storage access through the Storage Access API as soon as possible. An <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1469714">initial implementation of this API</a> is currently available in Nightly.</p>
+
+<h3 id="I_use_third-party_pixels_and_other_tools_to_measure_the_effectiveness_of_my_ad_campaigns._Will_I_still_be_able_to_measure_the_conversion_rate_of_my_ads">I use third-party pixels and other tools to measure the effectiveness of my ad campaigns. Will I still be able to measure the conversion rate of my ads?</h3>
+
+<p>This depends on how the third party has implemented the measurement tool, but generally ad conversion measurement will be more difficult. Consider the following examples:</p>
+
+<ol>
+ <li>You run an ad on a social media website that is seen several times by a user, but never clicked. That user later visits your website, which includes a conversion tracking tag from the same social media website. This type of conversion is often referred to as a “view-through conversion.” Since the social media website does not have access to their third-party storage, they will not recognize the user as the same user that saw the advertisements on their website and the conversion will not be tracked. We expect that most view-through conversion tracking techniques will no longer work, including those offered by display networks.</li>
+ <li>You run an ad on a display network or social media website that is clicked by a user. That user lands on your website, which includes a conversion tracking tag from the same website that displayed your ad. This type of conversion is often referred to as a “click-through conversion.” Since the social media site or display network will not have access to their third-party storage, they will not recognize the user as the same user that saw the advertisements on their website and the conversion will not be tracked. We expect that this version of click-through conversion will no longer work.</li>
+ <li>You run an ad that appears on a social media website. A user clicks on your advertisement and is taken to a landing page that contains a conversion tracking tag from the third-party network. On the social media website, the network annotates the advertisement landing page URL with a query parameter that signals that the visit was the result of a click on an advertisement. On your website, the display network’s tag checks the URL query parameters and saves any ad tracking parameters to first-party storage. If a user later completes a conversion event, the network’s tag checks first-party storage to determine which click (or clicks) was responsible for the visit. We expect that click-through conversion implemented in this way will continue to work.</li>
+</ol>
diff --git a/files/id/mozilla/firefox/releases/index.html b/files/id/mozilla/firefox/releases/index.html
new file mode 100644
index 0000000000..af6a0b7c7a
--- /dev/null
+++ b/files/id/mozilla/firefox/releases/index.html
@@ -0,0 +1,12 @@
+---
+title: Firefox developer release notes
+slug: Mozilla/Firefox/Releases
+tags:
+  - Firefox
+  - NeedsTranslation
+  - TopicStub
+translation_of: Mozilla/Firefox/Releases
+---
+<div>{{FirefoxSidebar}}</div><p>Dibawah ini anda bisa menemukan link ke catatan rilis pengembang untuk setiap rilis Firefox. Catatan yang ditulis dengan cinta ini memberikan detail tentang fitur dan API yang ditambahkan dan di tingkatkan serta bug yang disingkirkan pada setiap versi Firefox. Semuanya ditulis untuk memberikan informasi yang diperlukan oleh pengembang. Terima kasih.</p>
+
+<div class="multiColumnList">{{ListSubpages("",1,1,1)}}</div>
diff --git a/files/id/mozilla/gecko/index.html b/files/id/mozilla/gecko/index.html
new file mode 100644
index 0000000000..a2fb0f60ab
--- /dev/null
+++ b/files/id/mozilla/gecko/index.html
@@ -0,0 +1,69 @@
+---
+title: Gecko
+slug: Mozilla/Gecko
+translation_of: Mozilla/Gecko
+---
+<div class="summary">
+ <p><span class="seoSummary"><strong>Gecko</strong> adalah nama dari pengatur tata letak yang dikembangkan oleh Proyek Mozilla. It was originally named NGLayout. Gecko's function is to read web content, such as <a href="/en-US/docs/HTML" title="HTML">HTML</a>, <a href="/en-US/docs/CSS" title="CSS">CSS</a>, <a href="/en-US/docs/XUL" title="XUL">XUL</a>, <a href="/en-US/docs/JavaScript" title="JavaScript">JavaScript</a>, and render it on the user's screen or print it. In XUL-based applications Gecko is used to render the application's user interface as well.</span></p>
+</div>
+<p>Gecko di gunakan di banyak aplikasi, termasuk beberapa peramban (browsers), contohnya Firefox, SeaMonkey, dll. (for a complete list, please refer to <a class="external" href="http://en.wikipedia.org/wiki/Gecko_%28layout_engine%29#Web_browsers" rel="external" title="http://en.wikipedia.org/wiki/Gecko_(layout_engine)#Web_browsers">Wikipedia's article on Gecko</a>.) Products using the same version of Gecko have identical support for standards.</p>
+<table class="topicpage-table">
+ <tbody>
+  <tr>
+   <td>
+    <h2 class="Documentation" id="Documentation">Documentation</h2>
+    <dl>
+     <dt>
+      <a href="/en-US/docs/Gecko_FAQ" title="Gecko_FAQ">Gecko FAQ</a></dt>
+     <dd>
+      Frequently asked questions about Gecko.</dd>
+     <dt>
+      <a href="/en-US/docs/Gecko_DOM_Reference" title="https://developer.mozilla.org/en-US/docs/Gecko_DOM_Reference">Gecko DOM reference</a></dt>
+     <dd>
+      Reference to the DOM.</dd>
+     <dt>
+      <a href="/en-US/docs/Gecko-Specific_DOM_Events" title="Gecko/Gecko event reference">Gecko event reference</a></dt>
+     <dd>
+      Reference to events used within Gecko and Mozilla applications; for web-standard DOM events, see the <a href="/en-US/docs/DOM/DOM_event_reference" title="DOM/DOM event reference">DOM event reference</a>.</dd>
+     <dt>
+      <a href="/en-US/docs/Gecko/Versions" title="Gecko/Versions">Gecko versions and application versions</a></dt>
+     <dd>
+      Versions of Gecko and the applications they're used in.</dd>
+     <dt>
+      <a class="external" href="/en-US/docs/Introduction_to_Layout_in_Mozilla" title="https://developer.mozilla.org/en-US/docs/Introduction_to_Layout_in_Mozilla">Introduction to Layout in Mozilla</a></dt>
+     <dd>
+      Tech Talk on layout.</dd>
+     <dt>
+      <a href="/en-US/docs/Embedding_Mozilla" title="Embedding_Mozilla">Embedding Mozilla</a></dt>
+     <dd>
+      Using Gecko in your own application.</dd>
+     <dt>
+      <a href="/en-US/docs/Character_Sets_Supported_by_Gecko" title="Character Sets Supported by Gecko">Character sets supported by Gecko</a></dt>
+     <dd>
+      A list of the character sets supported by Gecko.</dd>
+     <dt>
+      <a href="/en-US/docs/Gecko/HTML_parser_threading" title="Gecko/HTML_parser_threading">HTML parser threading</a></dt>
+     <dd>
+      Description of multithreading in the HTML parser.</dd>
+     <dt>
+      {{interwiki('wikimo', 'Gecko:Home_Page', 'Gecko Homepage on MozillaWiki')}}</dt>
+     <dd>
+      Home for the active developers. Roadmaps and more up-to-date resources.</dd>
+    </dl>
+    <p><span class="alllinks"><a href="/en-US/docs/tag/Gecko" title="tag/Gecko">View All...</a></span></p>
+   </td>
+   <td>
+    <h2 class="Community" id="Community">Community</h2>
+    <ul>
+     <li>View Mozilla forums... {{DiscussionList("dev-tech-layout", "mozilla.dev.tech.layout")}}</li>
+    </ul>
+    <h2 class="Related_Topics" id="Related_Topics">Related Topics</h2>
+    <dl>
+     <dd>
+      <a href="/en-US/docs/Web_Standards" title="Web_Standards">Web Standards</a>, <a href="/en-US/docs/XUL" title="XUL">XUL</a>, <a href="/en-US/docs/Embedding_Mozilla" title="Embedding_Mozilla">Embedding Mozilla</a>, <a href="/en-US/docs/Developer_Guide" title="Developing_Mozilla">Developing Mozilla</a></dd>
+    </dl>
+   </td>
+  </tr>
+ </tbody>
+</table>
+<p> </p>
diff --git a/files/id/mozilla/index.html b/files/id/mozilla/index.html
new file mode 100644
index 0000000000..ecbabce71c
--- /dev/null
+++ b/files/id/mozilla/index.html
@@ -0,0 +1,13 @@
+---
+title: Mozilla
+slug: Mozilla
+tags:
+  - NeedsTranslation
+  - TopicStub
+translation_of: Mozilla
+---
+<div>
+ {{draft}}</div>
+<p>This will soon be an awesome landing page for Mozilla internals. For now, it's not.</p>
+<div>
+ {{LandingPageListSubpages}}</div>
diff --git a/files/id/mozilla/localization/index.html b/files/id/mozilla/localization/index.html
new file mode 100644
index 0000000000..ea5809653c
--- /dev/null
+++ b/files/id/mozilla/localization/index.html
@@ -0,0 +1,30 @@
+---
+title: Pelokalan di Mozilla
+slug: Mozilla/Localization
+tags:
+  - ButuhPenerjemahan
+  - Landing
+  - Localization
+  - Mozilla
+  - NeedsTranslation
+  - Pelokalan
+  - Pendaratan
+  - Penerjemahan
+  - RintisanTopik
+  - TopicStub
+  - Translation
+  - l10n
+translation_of: Mozilla/Localization
+---
+<p><span class="seoSummary"><strong>Pelokalan</strong> (L10n) adalah proses menerjemahkan antarmuka pengguna sebuah perangkat lunak dari satu bahasa ke bahasa yang lain, dan menyesuaikannya agar sesuai dengan kultur setempat. Semua sumber daya tersedia bagi siapa saja yang berminat dalam aspek teknis untuk terlibat dalam pelokalan, bagi para pengembang dan semua kontributor.</span></p>
+
+<h2 id="Lihat_pula">Lihat pula</h2>
+
+<dl>
+ <dt><a href="/id/docs/Project:MDN/Localizing" title="/en-US/docs/Project:MDN/Localizing">Pelokalan MDN</a></dt>
+ <dd>Sumber daya ini mencakup pelokalan dokumentasi di MDN.</dd>
+ <dt><a href="/id/Apps/Build/Localization">Pelokalan aplikasi</a></dt>
+ <dd>Kumpulan dokumen ini secara khusus digunakan untuk pelokalan aplikasi, termasuk aplikasi Firefox OS.</dd>
+ <dt><a href="/en-US/docs/Web/API/L10n">L10n</a></dt>
+ <dd>Dokumen referensi untuk API L10n yang digunakan Mozilla dalam pelokalan Firefox OS.</dd>
+</dl>
diff --git a/files/id/mozilla/localization/localizing_with_verbatim/index.html b/files/id/mozilla/localization/localizing_with_verbatim/index.html
new file mode 100644
index 0000000000..14e7d665b6
--- /dev/null
+++ b/files/id/mozilla/localization/localizing_with_verbatim/index.html
@@ -0,0 +1,158 @@
+---
+title: Pelokalan dengan Verbatim
+slug: Mozilla/Localization/Localizing_with_Verbatim
+translation_of: Mozilla/Localization/Localizing_with_Pontoon
+---
+<p><span class="seoSummary">Verbatim adalah suatu alat berbasis web (khususnya Pootle yang dihosting Mozilla) untuk melokalkan konten web Mozilla. Alat tersebut dapat digunakan untuk melokalkan berbagai proyek Mozilla dan mampu mendukung bahasa apa saja. Panduan ini akan membantu Anda melakukan pelokalan proyek Mozilla pada umumnya.</span> Tutorial yang disediakan di sini akan memberi Anda landasan yang bermanfaat dalam penggunaan Verbatim untuk melokalkan setiap proyek Mozilla yang ingin Anda ikut sertakan dalam upaya komunitas pelokalan Anda. Kita akan membahas proyek-proyek khusus yang sedang menggunakan Verbatim, cara untuk mulai menggunakan Verbatim, dan pekerjaan-pekerjaan yang umumnya dapat diselesaikan dengan Verbatim.</p>
+
+<h2 id="Mulai_menggunakan_Verbatim">Mulai menggunakan Verbatim</h2>
+
+<p>Being that it is web-based, localizers must be online to use Verbatim. There are essentially two ways to get started with Verbatim: start a new localization or join an existing localization community's efforts. Either way, you will need to follow these steps to start working on a Verbatim project.</p>
+
+<table style="border-color: #000000; border-style: solid; width: 100%;">
+ <thead>
+  <tr style="text-align: center;">
+   <th scope="col" style="text-align: center;"><strong>Start a new localization on Verbatim</strong></th>
+   <th scope="col" style="text-align: center;"><strong>Join an existing localization on Verbatim</strong></th>
+  </tr>
+ </thead>
+ <tbody>
+  <tr>
+   <td>
+    <ol>
+     <li>Point your browser to <a class="external" href="http://localize.mozilla.org/">http://localize.mozilla.org</a>. This is where Verbatim is hosted.</li>
+    </ol>
+   </td>
+   <td>
+    <ol>
+     <li>Point your browser to <a class="external" href="http://localize.mozilla.org/">http://localize.mozilla.org</a>. This is where Verbatim is hosted.</li>
+    </ol>
+   </td>
+  </tr>
+  <tr>
+   <td>
+    <ol start="2">
+     <li>If you have a Mozilla LDAP account, simply sign in using your LDAP credentials. If not, register for an account and sign in once you've completed registration. The links for both are located in the upper right-hand corner of the page.</li>
+    </ol>
+   </td>
+   <td>
+    <ol start="2">
+     <li>If you have a Mozilla LDAP account, simply sign in using your LDAP credentials. If not, register for an account and sign in once you've completed registration. The links for both are located in the upper right-hand corner of the page.</li>
+    </ol>
+   </td>
+  </tr>
+  <tr>
+   <td>
+    <ol start="3">
+     <li>File a <a class="link-https" href="https://bugzilla.mozilla.org/enter_bug.cgi?alias=&amp;assigned_to=nobody%40mozilla.org&amp;blocked=&amp;bug_file_loc=https%3A%2F%2Flocalize.mozilla.org%2F&amp;bug_severity=normal&amp;bug_status=NEW&amp;cf_blocking_191=---&amp;cf_blocking_192=---&amp;cf_status_191=---&amp;cf_status_192=---&amp;cf_status_firefox10=---&amp;cf_status_firefox11=---&amp;cf_status_firefox8=---&amp;cf_status_firefox9=---&amp;cf_tracking_firefox10=---&amp;cf_tracking_firefox11=---&amp;cf_tracking_firefox8=---&amp;cf_tracking_firefox9=---&amp;comment=I%20would%20like%20to%20request%20that%20you%20add%20the%20%5Binsert%20your%20locale%20code%20here%5D%20as%20a%20new%20localization%20in%20Verbatim.%0D%0A%0D%0A%5BAdd%20any%20other%20comments%20you%20may%20have%20here.%5D&amp;component=Verbatim&amp;contenttypeentry=&amp;contenttypemethod=autodetect&amp;contenttypeselection=text%2Fplain&amp;data=&amp;defined_groups=1&amp;dependson=&amp;description=&amp;flag_type-4=X&amp;flag_type-607=X&amp;form_name=enter_bug&amp;keywords=&amp;maketemplate=Remember%20values%20as%20bookmarkable%20template&amp;op_sys=All&amp;priority=--&amp;product=Webtools&amp;qa_contact=verbatim%40webtools.bugs&amp;rep_platform=All&amp;requestee_type-325=&amp;requestee_type-4=&amp;requestee_type-607=&amp;short_desc=Request%20for%20new%20localization%20on%20Verbatim&amp;status_whiteboard=&amp;target_milestone=---&amp;version=Trunk" title="https://bugzilla.mozilla.org/enter_bug.cgi?alias=&amp;assigned_to=nobody%40mozilla.org&amp;blocked=&amp;bug_file_loc=https%3A%2F%2Flocalize.mozilla.org%2F&amp;bug_severity=normal&amp;bug_status=NEW&amp;cf_blocking_191=---&amp;cf_blocking_192=---&amp;cf_status_191=---&amp;cf_status_192=---&amp;cf_status_firefox10=---&amp;cf_status_firefox11=---&amp;cf_status_firefox8=---&amp;cf_status_firefox9=---&amp;cf_tracking_firefox10=---&amp;cf_tracking_firefox11=---&amp;cf_tracking_firefox8=---&amp;cf_tracking_firefox9=---&amp;comment=I%20would%20like%20to%20request%20that%20you%20add%20the%20%5Binsert%20your%20locale%20code%20here%5D%20as%20a%20new%20localization%20in%20Verbatim.%0D%0A%0D%0A%5BAdd%20any%20other%20comments%20you%20may%20have%20here.%5D&amp;component=Verbatim&amp;contenttypeentry=&amp;contenttypemethod=autodetect&amp;contenttypeselection=text%2Fplain&amp;data=&amp;defined_groups=1&amp;dependson=&amp;description=&amp;flag_type-4=X&amp;flag_type-607=X&amp;form_name=enter_bug&amp;keywords=&amp;maketemplate=Remember%20values%20as%20bookmarkable%20template&amp;op_sys=All&amp;priority=--&amp;product=Webtools&amp;qa_contact=verbatim%40webtools.bugs&amp;rep_platform=All&amp;requestee_type-325=&amp;requestee_type-4=&amp;requestee_type-607=&amp;short_desc=Request%20for%20new%20localization%20on%20Verbatim&amp;status_whiteboard=&amp;target_milestone=---&amp;version=Trunk">bug</a> using this prefilled bugzilla template. Add your locale code and language name to the description field, as well as any other information you'd like to share. See the following example.</li>
+    </ol>
+
+    <div class="note"><strong>Example</strong>: I would like to request that you add the <em><strong>en-US</strong></em> as a new localization in Verbatim. The langauge is <em><strong>English</strong></em>. Also, I like cookies. Lots and lots of cookies. I can easily be motivated by any and all baked goods.</div>
+   </td>
+   <td>
+    <ol start="3">
+     <li><a class="link-https" href="https://wiki.mozilla.org/Category:L10n_Teams" title="https://wiki.mozilla.org/Category:L10n_Teams">Contact the community</a> to find out which projects they need you to concentrate your efforts on. See the following example for what you could include in your email to the community leaders.</li>
+    </ol>
+
+    <div class="note"><strong>Example</strong>: I would like to join your localization efforts on Verbatim for this locale. Where would be the best place for me to begin? Also, I would like to buy you a drink to encourage you to let me join the team!</div>
+   </td>
+  </tr>
+ </tbody>
+</table>
+
+<p>Now that you're registered and logged in, we'll outline the general translation workflow, using the <a class="link-https" href="https://localize.mozilla.org/projects/mdn" title="https://localize.mozilla.org/projects/mdn/">MDN project page</a> as our example.</p>
+
+<h2 id="Translating">Translating</h2>
+
+<p>First thing's first, you need to find untranslated source strings to translate.</p>
+
+<ol>
+ <li>Navigate to the <a class="link-https" href="https://localize.mozilla.org/projects/mdn" title="https://localize.mozilla.org/projects/mdn/">MDN project page</a>.</li>
+ <li>Select your language from the <strong>Overview</strong> tab.</li>
+ <li>Now click on the the <strong>Translate</strong> tab. This tab will display the directories for the MDN user interface.</li>
+ <li>Select the <strong>LC Messages</strong> directory. This is where the project's <code>.po</code> files containing translatable strings are located. You will now see an overview of each <code>.po</code> file.</li>
+ <li>In the summary column, the number of words untranslated will be shown as a link. Click on that link to be taken directly to the first string that needs to be translated.</li>
+</ol>
+
+<p>Now you're ready to contribute translations and you won't believe how easy it is. Check it out, you can contribute translations in two simple steps:</p>
+
+<ol>
+ <li>Simply type your translation in the box to below the English string</li>
+ <li>Select <strong>Suggest</strong>. If you have approval permission, select <strong>Submit</strong>. You will then be taken to the next string that needs translating.</li>
+ <li>Hooray! You're translating! Repeat steps one and two for the remainder of the untranslated strings.</li>
+</ol>
+
+<div class="note"><strong>Note</strong>: If you come across a string that already has a suggested translation, you can still suggest your own translation if you feel it is more accurate.</div>
+
+<h3 id="Some_extra_cool_features_on_Verbatim">Some extra cool features on Verbatim</h3>
+
+<p>Here are a few additional items about the Verbatim interface that you should be aware of. Some of these can be seen in the screen shot below.</p>
+
+<p><a href="/@api/deki/files/5930/=Translate_Tab.png" title="Translate Tab.png"><img alt="Translate Tab.png" class="default internal" src="/@api/deki/files/5930/=Translate_Tab.png" style="height: 221px; width: 1113px;"></a></p>
+
+<ul>
+ <li>You can copy the English string over to the translation box by clicking the <strong>Copy</strong> icon.</li>
+ <li>You can use machine translation by clicking on the <strong>Google Translate</strong> icon.</li>
+ <li>You can move forward and back through the strings by clicking the <strong>Next</strong> and <strong>Previous</strong> buttons.</li>
+ <li>You can navigate directly to a particular string by clicking it's string number on the far left.</li>
+ <li>You can mark a translation as <strong>Fuzzy</strong> if you think there could be a better way to say something. This will mark it so it can be found and updated later. Remember that only submitted strings will be commited to the localization's repository, not fuzzy strings. If strings remain marked as fuzzy, the source string will appear in your localized version instead of a translated string.</li>
+ <li>You can add notes about a particular string in the <strong>Translator Comments</strong> section.</li>
+ <li>When translating a string with both singular and plural forms you will see two boxes on the right hand side. The box for the singular form is labeled <strong>Plural Form 0</strong> and the box for the plural form is labeled <strong>Plural Form 1</strong>.</li>
+</ul>
+
+<h2 id="Additional_tasks">Additional tasks</h2>
+
+<p>If you are a localizer with approval priviledges, here are a few more tasks that you should be aware of.</p>
+
+<h3 id="Review_suggested_translations">Review suggested translations</h3>
+
+<ol start="1">
+ <li>Click on the <strong>Review</strong> tab. It will show how many strings are waiting for review for each <code>.po</code> file.<a href="/@api/deki/files/5931/=Review_Tab1.png" title="Review Tab1.png"><img alt="Review Tab1.png" class="internal rwrap" src="/@api/deki/files/5931/=Review_Tab1.png?size=webview" style="float: right; height: 145px; width: 274px;"></a></li>
+ <li>Select <strong style="font-weight: bold;">Review</strong><strong> suggestions</strong> to start approving suggestions. It will take you to the first string that needs to be reviewed.</li>
+ <li>You can accept the suggestion by clicking the green checkmark or reject the suggestion by clicking the red X (see the screen shot from the previous section).</li>
+</ol>
+
+<p>It is important to note that <em>only</em> submitted strings will appear in your localized pages. Neither suggestions nor fuzzy strings will appear. Before commiting your final localized product, make sure all strings have been submitted.</p>
+
+<h3 id="Using_VCS_on_Verbatim">Using VCS on Verbatim</h3>
+
+<p>VCS (<strong>V</strong>ersion <strong>C</strong>ontrol <strong>S</strong>ystem) is the repository system we use to update the project's strings as well as push your translated content onto the web. The difference between the two tasks is simply a matter of which link to click.</p>
+
+<p><img alt="VCS.png" class="internal rwrap" src="/@api/deki/files/5925/=VCS.png" style="float: right;">To push your strings onto the web and see your changes, simply select the <strong>Commit to VCS</strong> link underneath each file name. It usually takes about an hour before you can see your changes on the project site.</p>
+
+<p>To update your <code>.po</code> files with new untranslated strings, simple select the <strong>Update from VCS</strong> link underneath each file name.</p>
+
+<p> </p>
+
+<div class="note"><br>
+<strong>Note</strong>: Some projects are automatically updated nightly while others require you to manually update them to receive new source content. Be sure to pay close attention to this, as it can alter your workflow.</div>
+
+<h2 id="Translating_Verbatim_files_with_an_external_application">Translating Verbatim files with an external application</h2>
+
+<p>While in the <strong>Translate</strong> tab, you have the option to export the <code>.po </code>and <code>.xliff</code> files and translate the strings with an external application (i.e., a text editor or translation memory tool).</p>
+
+<ol>
+ <li>To download the <code>.po</code> file, select the <strong>Download</strong> link found underneath each file name. To download the .<code>xliff</code> file, select the <strong>Download XLIFF</strong> link.</li>
+ <li>Proceed to translate the strings using your selected tool.</li>
+</ol>
+
+<p>Once you've finished your translations, you'll need to upload your file to Verbatim. You can do this from the <strong>Translate</strong> tab.</p>
+
+<ol>
+ <li>Navigate to the bottom of the files list to the <strong>Upload File</strong> section.</li>
+ <li>Click on the <strong>Browse</strong> button and select the file you wish to upload.</li>
+ <li>Select an upload setting from the options provided.</li>
+ <li>Once your upload setting has been selected, click <strong>Upload</strong>.</li>
+</ol>
+
+<div class="warning">
+<p class="warning"><strong>Important</strong>: There have been some problems in the past with community members updating their source strings while others are in the process of localizing the previous updated files. This can cause community members to overlook new source strings, producing untranslated strings in a localized project. Be sure to coordinate these manual updates within your community to avoid this problem.</p>
+</div>
+
+<h2 id="You're_ready_to_go!">You're ready to go!</h2>
+
+<p>Whew! You've arrived at the end! Time to take what you've learned and put it to good use spreading Mozilla to everyone in your region. Have fun and <a class="link-mailto" href="mailto:l10n-drivers@mozilla.com" title="l10n-drivers@mozilla.com">let us know</a> if you run into any difficulties. We'll be happy to help in any way we can.</p>
+
+<p> </p>
+
+<p><a href="/en/Localization_Quick_Start_Guide:_Translation" title="Localization Quick Start Guide: Translation">Back: Quick Start Guide</a></p>
diff --git a/files/id/mozilla/localization/quick_start_guide/index.html b/files/id/mozilla/localization/quick_start_guide/index.html
new file mode 100644
index 0000000000..216207c9c4
--- /dev/null
+++ b/files/id/mozilla/localization/quick_start_guide/index.html
@@ -0,0 +1,50 @@
+---
+title: Panduan memulai cepat pelokalan
+slug: Mozilla/Localization/Quick_start_guide
+tags:
+  - ButuhPenerjemahan
+  - Guide
+  - Localization
+  - Mozilla
+  - NeedsTranslation
+  - Panduan
+  - Pelokalan
+  - Penerjemahan
+  - RintisanTopik
+  - TopicStub
+  - Translation
+translation_of: Mozilla/Localization/Quick_start_guide
+---
+<p>Selamat datang di pelokalan Mozilla (singkatnya L10n)!</p>
+
+<p>Entah Anda berada di sini untuk memulai pelokalan Anda sendiri dalam proyek Mozilla ataupun untuk bergabung dalam upaya pelokalan yang sedang berlangsung, Anda datang ke tempat yang tepat! <span class="seoSummary">Panduan ini memuat semua informasi dasar dan teknis yang Anda perlukan untuk terlibat dalam program L10n Mozilla.</span> Kami akan menunjukkan kepada Anda langkah-langkah untuk memulainya, dari pengaturan awal hingga pengetesan dan perilisan pelokalan Anda sendiri. Dalam prosesnya, Anda akan mempelajari berbagai proyek yang di dalamnya Anda dapat berkontribusi dan semua alat yang digunakan untuk pelokalan.</p>
+
+<p>Bilamana kita berhadapan dengan kasus-kasus khusus, kita mengambilnya dari proyek Firefox sebagai proyek yang paling banyak dilakukan pelokalan di Mozilla. Dan ketika Anda hampir menyelesaikan panduan ini, Anda seharusnya mampu melakukan perubahan pada pengaturan lokal Firefox Anda dan menyaksikan perubahan pada antarmukanya. Akhir kata, setelah Anda menyelesaikan panduan ini, Anda akan memiliki semua alat yang diperlukan untuk mulai berkontribusi!</p>
+
+<p>Ingat, panduan ini hanya memuat instruksi seputar aspek teknis L10n Mozilla saja. Kunjungi halaman <a class="link-https" href="https://wiki.mozilla.org/L10n:Localization_Process" title="https://wiki.mozilla.org/L10n:Overview">Proses L10n</a> untuk mempelajari keseluruhan prosesnya.</p>
+
+<div style="width: 25%; background-color: #4AA02C; float: left; display: block; margin: 1.5%; border: 1px solid #C4C295; text-align: center; padding: 2.5%; padding-top: 0px;">
+<h2 id="Pengaturan_awal"><a href="/id/docs/Mozilla/Localization/Quick_start_guide/Initial_setup" title="id/Localization_Quick_Start_Guide/Initial_setup">Pengaturan awal</a></h2>
+Persiapan teknis sebelum melakukan pelokalan.</div>
+
+<div style="width: 25%; background-color: #A2BFF4; float: left; display: block; margin: 1.5%; border: 1px solid #C4C295; text-align: center; padding: 2.5%; padding-top: 0px;">
+<h2 id="Tahap_penerjemahan"><a href="/en-US/docs/Mozilla/Localization/Quick_start_guide/Translation_phase" title="id/Localization_Quick_Start_Guide/Translation_phase">Tahap penerjemahan</a></h2>
+Tutorial penggunaan alat L10n untuk penerjemahan.</div>
+
+<div style="width: 25%; background-color: orange; float: left; display: block; margin: 1.5%; border: 1px solid #C4C295; text-align: center; padding: 2.5%; padding-top: 0px;">
+<h2 id="Tahap_QA"><a href="/id/docs/Mozilla/Localization/Quick_start_guide/QA_phase" title="id/Localization_Quick_Start_Guide/QA_phase">Tahap QA</a></h2>
+Tutorial pengetesan L10n.</div>
+
+<div style="width: 92%; background-color: #C0C0C0; float: left; display: block; margin: 1.5%; border: 1px solid #C4C295; text-align: center; padding: 2.5%; padding-top: 0px;">
+<h2 id="Tahap_perilisan"><a href="/id/docs/Mozilla/Localization/Quick_start_guide/Release_phase" title="id/Localization_Quick_Start_Guide/Release_phase">Tahap perilisan</a></h2>
+Langkah-langkah mengirimkan pekerjaan pelokalan Anda.</div>
+
+<div style="background-color: white; border: 3px solid; display: block; padding: 20px; margin-top: 20px;">Keempat tahap ini merupakan sisi teknis dari program L10n. Untuk mempelajari lebih lanjut tentang semua ini, silakan klik salah satu tautan di atas. Untuk mendapatkan gambaran besarnya, kami sarankan Anda memulai dengan boks hijau dan melanjutkannya secara bertahap.</div>
+
+<p> </p>
+
+<div class="note"><strong>Note</strong>: This guide is written for two types of contributors: those starting a new localization and those joining an existing localization. It is important to know which information applies to which type of contributor. To help you filter through to the most applicable information, note that all information that is unique to those starting a new localization will be in <span style="color: #daa520;">orange font</span>. All information that is unique to those joining an existing localization will be in <span style="color: #0000ff;">blue font</span>.</div>
+
+<p class="note"> </p>
+
+<p>{{ Next("Localization_Quick_Start_Guide/Initial_setup") }}</p>
diff --git a/files/id/mozilla/localization/quick_start_guide/qa_phase/index.html b/files/id/mozilla/localization/quick_start_guide/qa_phase/index.html
new file mode 100644
index 0000000000..0ee69f43e4
--- /dev/null
+++ b/files/id/mozilla/localization/quick_start_guide/qa_phase/index.html
@@ -0,0 +1,197 @@
+---
+title: Tahap QA
+slug: Mozilla/Localization/Quick_start_guide/QA_phase
+translation_of: Mozilla/Localization/Quick_start_guide/QA_phase
+---
+<p>Setelah hasil kerja keras anda dalam melokalisasi kami yakin bahwa anda tidak hanya ingin melihat hasil kerja anda tapi juga ingin memastikan bahwa itu tepat! Jika anda tidak begitu awam dengan kode, anda pasti khawatir akan merusak sesuatu (oops!). Sekarang kami akan menuntun anda melakukan test kualitas pekerjaan anda untuk memastikan anda berada di jalur yang tepat.</p>
+
+<p>Jika anda melokalisasi halaman Mozilla, hasil pekerjaan anda akan ditampilkan<strong> </strong>segera setelah anda menyelesaikannya tanpa membutuhkan paket bahasa. Seperti halnya kasus ini, bagian dari pedoman ini tidak sepenuhnya dapat di aplikasikan oleh anda. Silahkan tekan tombol <strong>Next </strong>pada bagian paling bawah laman jika anda ingin melewati.</p>
+
+<p>Untuk melihat hasil pekerjaan anda di Firefox (atau dalam aplikasi Mozilla yang lain), anda butuh paket bahasa yang terinstal pada direktori anda.</p>
+
+<h2 id="Manual_automated_builds">Manual &amp; automated builds</h2>
+
+<p>Dengan menekan tombol, beberapa alat L10n (seperti Narro and Koala) secara otomatis membuat paket bahasa untuk anda. Jika anda menggunakan salah satu dari alat tersebut, silahkan menuju ke bagian <a href="https://developer.mozilla.org/en/Localization_Quick_Start_Guide:_QA#Seeing_your_work">Melihat pekerjaan anda</a>, Sekarang mari menuju ke pembuatan paket bahasa anda sendiri secara manual.</p>
+
+<div class="note"><strong>Note</strong>: Remember all of those pre-requisite tools we asked you to install in the <a href="/en/Localization_Quick_Start_Guide#Local_environment_tools" title="https://developer.mozilla.org/en/Localization_Quick_Start_Guide#Local_environment_tools">initial setup</a>? Here's where you'll need almost all of them. If you haven't installed them yet, <em>now</em> is the time to do it.</div>
+
+<h3 id="Persiapan">Persiapan</h3>
+
+<p>Kita akan menggunakan file direktori berikut sebagai contoh:</p>
+
+<pre style="margin-left: 40px;">your working directory <em>(root)/</em>
+    mozilla-aurora <em>(en-US source, pulled from <a class="external" href="http://hg.mozilla.org/releases/mozilla-aurora" rel="external" title="http://hg.mozilla.org/releases/mozilla-aurora">http://hg.mozilla.org/releases/mozilla-aurora</a></em>  <em>)</em>/
+    l10n-central <em>(directory for L10n directories, one per L10n; often referred to as "l10n base")/</em>
+       your-locale-code <em>(a directory with your L10n files, in this example we'll use x-testing)</em>
+
+<strong>Example</strong>: <code>root/mozilla-aurora</code> &amp; <code>root/l10n-central/x-testing</code>
+</pre>
+
+<p>Additionally, you will need to c</p>
+
+<p>Please either follow the above structure closely or adjust the commands below according to your custom setup.</p>
+
+<p>To copy this file to the appropriate directory, do the following:</p>
+
+<ol>
+ <li>Navigate to your working directory from your command-line terminal (i.e., where you created the folder structure described above).</li>
+ <li>Enter the following commands:</li>
+</ol>
+
+<pre style="margin-left: 40px;">mkdir -p l10n-central/x-testing/toolkit/
+
+cp mozilla-aurora/toolkit/locales/en-US/defines.inc l10n-central/x-testing/toolkit/defines.inc
+</pre>
+
+<p>Tah-dah! Copied!</p>
+
+<p>Finally, you will need a file called <code>.mozconfig</code> to proceed with manual builds. This file contains the necessary build instructions.</p>
+
+<p>To create and configure this file, follow these instructions:</p>
+
+<ol>
+ <li>Update the Mozilla source code:</li>
+</ol>
+
+<p style="margin-left: 40px;"><code>$ cd mozilla-aurora<br>
+ $ hg pull -u</code></p>
+
+<ol start="2" style="list-style-type: decimal;">
+ <li>Enter the following command to create the <code>.mozconfig</code> file: <code>$ nano -w .mozconfig</code></li>
+ <li>Enter the following lines in your <code>.mozconfig</code> file:</li>
+</ol>
+
+<pre style="margin-left: 40px;">mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../firefox-build
+ac_add_options --disable-compile-environment
+ac_add_options --with-l10n-base=../l10n-central # path relative to MOZ_OBJDIR
+ac_add_options --enable-application=[<em>browser or mail</em>]
+</pre>
+
+<p style="margin-left: 40px;">You will need to specify which application you're localizing in the fourth line (e.g., for Firefox, that's <code>browser</code>, Thunderbird would be <code>mail</code>).</p>
+
+<ol start="4" style="list-style-type: decimal;">
+ <li>Enter the following command to perform the configuration: <code>$ mach configure</code></li>
+ <li>Once your command-line finishes spitting out the config command's output, navigate to the newy created directory:<code> $ cd ../firefox-build/browser/locales</code></li>
+</ol>
+
+<p>Now you're ready to build! At this point you can choose between two build options. You can either:</p>
+
+<ul>
+ <li><a href="/en/Creating_a_Language_Pack#Creating_a_langpack" title="https://developer.mozilla.org/en/Creating_a_Language_Pack#Creating_a_langpack">Create a langpack</a>, which is installed <em>on top of</em> your Mozilla application, or</li>
+ <li><a href="/en/Creating_a_Language_Pack#L10n_binary_repack" title="https://developer.mozilla.org/en/Creating_a_Language_Pack#L10n_binary_repack">Repack the application's binary</a> (aka, a L10n repack), which allows you to install <em>next</em> to your existing Mozilla application installation and use separately.</li>
+</ul>
+
+<p>Visit the links above to learn how to make these testing builds.</p>
+
+<h2 id="Testing_your_L10n_seeing_your_work">Testing your L10n &amp; seeing your work</h2>
+
+<p>Now that you have your langpack or L10n repack, let's discuss seeing your work and testing it in the application.</p>
+
+<p>Testing the langpack will put you one step closer to having your localization added to the L10n releases. Follow the steps below to test your localization:</p>
+
+<ol>
+ <li>Install Aurora in your preferred language.</li>
+ <li>Install the <code>.xpi</code> langpack you just created (or exported).</li>
+ <li>Set your language using the Quick Locale Switcher or Locale Switcher add-ons by navigating to Tools-&gt;Language-&gt;Your localization's language code.</li>
+ <li>Restart your browser and start testing!</li>
+</ol>
+
+<p>Now you should be able to see all of your work up to this point. Click <a class="link-https" href="https://wiki.mozilla.org/MozillaQualityAssurance:l10n_checklist" title="https://wiki.mozilla.org/MozillaQualityAssurance:l10n_checklist">here</a> for guidelines on how to test your localization.</p>
+
+<h2 id="Don't_lose_your_work!">Don't lose your work!</h2>
+
+<p>You're work is <em>SO</em> important! We would really hate to see you lose any of it. After you test your localization, you should send it to a remote repository, which will serve as a backup for your work and will let others follow your progress. We're going to go through the process below.</p>
+
+<p>The official localization teams use repositories at <a class="external" href="http://hg.mozilla.org/" rel="external" title="http://hg.mozilla.org/">hg.mozilla.org</a>. Before a team becomes official, we like to get the localizers comfortable with the Hg commands that allow for cloning, pulling, committing, and pushing work to an experimental repository.  We use a web service called <a class="external" href="http://www.bitbucket.org/" rel="external" title="http://www.bitbucket.org/">Bit Bucket</a> to start the learning process.</p>
+
+<div class="note"><strong>Note</strong>: You must have Mercurial configured before you begin. That step is back on the initial setup page. If you haven't done that yet, don't worry, we'll wait for you!</div>
+
+<h3 class="note" id="Pushing_to_your_repository">Pushing to your repository</h3>
+
+<p>There are a couple of things you should take note of before you push to your repository:</p>
+
+<ul>
+ <li>Make sure that your files have been encoded in Unicode without BOM (byte order mark).</li>
+ <li>Remember that here you are pushing an entire directory, not a <code>.zip</code> archive file or an <code>.xpi</code> lang pack.</li>
+</ul>
+
+<p>The instructions below will help you learn how to use your Hg repository.</p>
+
+<ol>
+ <li><span style="color: #daa520;">After your new repository is created by the l10n-drivers</span>, please visit the URL for your repo. We'll use x-testing here for our example. You can do this by entering the following URL into your browser: <code><a class="external" href="http://hg.mozilla.org/l10n-central/x-testing" rel="freelink">http://hg.mozilla.org/l10n-central/x-testing</a></code></li>
+ <li>Now, navigate to your locale's directory on your local machine.</li>
+</ol>
+
+<p style="margin-left: 40px;">If you're using Koala, this should be located at <code>/path/to/your/koala.project/locale/3.6/x-testing</code>, otherwise, it should be located at <code>/path/to/your/working_dir/l10n_base/x-testing</code>.</p>
+
+<p style="margin-left: 40px;">In this directory, you should have an hg repository. You might have created it yourself by running <code>hg init</code> or <code>hg clone</code> or you might have had it created by Koala when you were setting up a new localization project. Also at this point, you shouldn't have any uncommitted changes (i.e., running the <code>hg status </code>command should show nothing). Let's see what the last revision in this repository is.</p>
+
+<ol start="3" style="list-style-type: decimal;">
+ <li style="">Enter the following command: <code>$ hg log -l 1</code></li>
+</ol>
+
+<p style="margin-left: 40px;">You should see an output similar to the one below:</p>
+
+<pre style="margin-left: 40px;">changeset:   0:7c543e8f3a6a
+tag:         tip
+user:        Your Name &lt;email@example.com&gt;
+date:        Mon Nov 23 18:08:25 2009 +0100
+summary:     Added search bar strings
+</pre>
+
+<ol start="4" style="list-style-type: decimal;">
+ <li>Now compare the local repository on your machine with the remote Hg repository by entering this command: <code>$ hg outgoing <a class="external" href="http://hg.mozilla.org/l10n-central/x-testing" rel="freelink">http://hg.mozilla.org/l10n-central/x-testing</a></code></li>
+</ol>
+
+<p style="margin-left: 40px;">The <code>hg outgoing</code> command compares the two repositories and lists all changesets that are present locally, but not in the remote repository. These changesets will need to be "pushed" to the remote repository. You can expect to see output like this:</p>
+
+<pre style="margin-left: 40px;">comparing with http://hg.mozilla.org/l10n-central/x-testing
+searching for changes
+
+changeset:   0:7c543e8f3a6a
+tag:         tip
+user:        Your Name &lt;email@example.com&gt;
+date:        Mon Nov 23 18:08:25 2009 +0100
+summary:     Added search bar strings
+</pre>
+
+<ol start="5" style="list-style-type: decimal;">
+ <li>Let's now push this changeset. Enter the following command:<code> hg push <a class="external" href="http://hg.mozilla.org/l10n-central/x-testing" rel="freelink">http://hg.mozilla.org/l10n-central/x-testing</a></code></li>
+ <li>Mercurial will connect to your repo and ask you to provide your account information (i.e., the username and the password).</li>
+</ol>
+
+<pre style="margin-left: 40px;">real URL is http://hg.mozilla.org/l10n-central/x-testing
+pushing to http://hg.mozilla.org/l10n-central/x-testing
+searching for changes
+http authorization required
+realm: hg.mozilla.org HTTP
+user: your_id
+password:
+</pre>
+
+<p style="margin-left: 40px;">After you enter your account information, the changeset will be pushed.</p>
+
+<pre style="margin-left: 40px;">adding changesets
+adding manifests
+adding file changes
+added 1 changesets with 2 changes to 2 files
+bb/acl: your_id is allowed. accepted payload.
+quota: 979.7 KB in use, 150.0 MB available (0.64% used)
+</pre>
+
+<p>Your changeset has been successfully pushed to your repository!</p>
+
+<p>As you begin to move through your translations, you should <code>commit</code> the changes locally and <code>push</code> your work to this experimental repository. For instance, if you have finished translating all the <code>.dtd</code> and <code>.properties</code> files in your <code>x-testing/browser/chrome/browser/</code> directory, then you should run these commands:</p>
+
+<pre style="">$ hg status
+$ hg commit -m "Translated browser/chrome/browser/"
+$ hg outgoing
+$ hg push http://hg.mozilla.org/l10n-central/x-testing</pre>
+
+<p>Note that due to the distributed nature of Hg, <code>hg commit</code> saves the changes locally (i.e., in your computer's Hg repository). You can see the history of commits with <code>hg log</code>. After doing <code>hg commit</code>, you still need to send the changes to the remote repository. This is where <code>hg push</code> comes in. This sends your commits to the remote repository.</p>
+
+<p>Now you're ready to proceed to the release phase!</p>
+
+<p> </p>
+
+<p>{{ PreviousNext("Localization_Quick_Start_Guide/Translation_phase", "Localization_Quick_Start_Guide/Release_phase") }}</p>
diff --git a/files/id/mozilla/localization/web_localizability/index.html b/files/id/mozilla/localization/web_localizability/index.html
new file mode 100644
index 0000000000..e4ff426a11
--- /dev/null
+++ b/files/id/mozilla/localization/web_localizability/index.html
@@ -0,0 +1,33 @@
+---
+title: Kemampulokalan Web
+slug: Mozilla/Localization/Web_Localizability
+tags:
+  - Internationalization
+  - Localizability
+  - Localization
+  - NeedsTranslation
+  - TopicStub
+  - Web Development
+translation_of: Mozilla/Localization/Web_Localizability
+---
+<p>Kemampulokalan (atau singkatnya <em>l12y</em>) adalah karakteristik yang terkandung dalam suatu aplikasi atau konten yang memungkinkan untuk dilakukan pelokalan. Daftar berikut ini berisi tautan ke halaman yang menjabarkan langkah-langkah untuk membuat konten web dapat dilokalkan.  Dokumentasi dibagi menjadi 4 bagian:</p>
+
+<ol>
+ <li><a href="/en/Web_Localizability/Creating_localizable_web_content" title="en/Web Localizability/Creating localizable web content">How to create localizable content.</a></li>
+ <li><a href="/en/Web_Localizability/Localization_formats" title="en/Web Localizability/Localization formats">How to choose the right localization format.</a></li>
+ <li><a href="/en/Web_Localizability/Creating_localizable_web_applications" title="en/Web Localizability/Creating localizable web applications">How to create localizable web applications.</a></li>
+ <li><a href="/en/Web_Localizability/Setting_up_the_infrastructure" title="en/Web Localizability/Setting up the infrastructure">How to set up the infrastructure for localization.</a></li>
+</ol>
+
+<h3 id="Why_localizability_is_important">Why localizability is important</h3>
+
+<p>There are many reasons why you should start thinking about making your web app localizable as soon as possible.</p>
+
+<ol>
+ <li>You will make localizer's life easier, for which they will be grateful.</li>
+ <li>You will have quality content, localized and adapted to the needs of the local market.</li>
+ <li>Extending you web app to support new languages will be easy.</li>
+ <li>The content will be easier to maintain and update.</li>
+ <li>You will end up writing more semanticly-correct code, which is good for your SEO.</li>
+ <li>By reviewing your content and code for l12y, you will find and fix bugs in your original language too.</li>
+</ol>
diff --git a/files/id/mozilla/mercurial/basics/index.html b/files/id/mozilla/mercurial/basics/index.html
new file mode 100644
index 0000000000..e3b797d0f2
--- /dev/null
+++ b/files/id/mozilla/mercurial/basics/index.html
@@ -0,0 +1,60 @@
+---
+title: Dasar-dasar Mercurial
+slug: Mozilla/Mercurial/Basics
+translation_of: Mozilla/Mercurial/Basics
+---
+<p>Saya ingin berbagi pengetahuan denganmu tentang <a href="/en/Mercurial" title="en/Mercurial">Mercurial</a> yang mungkin dapat melindungimu dari frustasi. Halaman ini memang sinis dan survival-oriented. Tetapi saya masih menganggap Mercurial sedikit lebih baik dari pada CVS. —<a href="/User:Jorend" title="User:Jorend">jorendorff</a> 16:06, 12 May 2008 (PDT)</p>
+
+<p> </p>
+
+<h3 id="Expectations" name="Expectations">Expectations</h3>
+
+<p><strong>Mercurial bukan CVS.</strong> Perintah-perintahnya tidak sama. The konsepnya tidak sama. <a href="/en/Mozilla/Mercurial/How_Is_Mercurial_different_from_CVS" title="en/Mozilla/Mercurial/How_Is_Mercurial_different_from_CVS">Bagaimana Mercurial berbeda dengan CVS?</a></p>
+
+<p><strong>Sepanan ini sudah terisi.</strong> Anda dapat menembak dirimu sendiri. Anda dapat kehilangan pekerjaan. Perkakasa sudah mencoba melindungi Anda , tetapi kecelakan tetap dapat terjadi. Ada dua kesalahan umum: (a) Anda menjalankan perintah tanpa mengetahui apa yang akan dilakukan oleh perintah tersebut; (b) Anda melakukan <code>hg commit</code>atau <code>hg qrefresh</code> dengan salah paham pada status direktori kerja Anda. Oleh karena itu tanpa sengaja Anda membuat commit pada perubahan yang sebenarnya tidak ingin Anda buat commit; atau tanpa sengaka Anda membuat commit sebuah merge yang rusak; dlsb. Seringkali kesalahan seperti ini tidak langsung ketahuan.</p>
+
+<p>Forewarned is forearmed. Don't do these things. Don't run commands without knowing what they're going to do—<code>hg help</code> is your friend. Don't commit without diffing and thinking. And don't let yourself get into "play mode" and stop paying attention to the fact that what you're playing with is your own uncommitted work.</p>
+
+<p><strong>Mercurial is not magic dust.</strong> Mercurial is flexible, powerful, and fun. It lets you attempt stuff you never would have tried in CVS. But of course not everything turns out to have been a good idea. (For example, we tried sharing patch queues. It sort of sucked.)</p>
+
+<h3 id="Avoiding_trouble" name="Avoiding_trouble">Avoiding trouble</h3>
+
+<p><strong>Use the latest stable release of Mercurial.</strong></p>
+
+<p><strong>Learn how to get your bearings.</strong> Use read-only commands (like <code>hg status</code>, <code>hg head</code>, <code>hg parents</code>, <code>hg log</code>, <code>hg diff</code>, <code>hg outgoing</code>) to check the status of your repository. This is a key skill.</p>
+
+<p><strong>Configure a <a class="external" href="https://www.mercurial-scm.org/wiki/MergeToolConfiguration">merge program</a> and make sure you know how to use it. DO IT NOW.</strong> Otherwise you will likely screw up your repository at some point.</p>
+
+<p>Mercurial doesn't leave conflict markers in your files; instead, it wants you to fix the conflicts <em>immediately</em>, using a merge program (like <code>kdiff3</code>) which it can launch for you.</p>
+
+<p>This can be error-prone. By default, Mercurial uses the first merge program it finds on your system, and merge programs can have a learning curve. Mercurial does not do a good job of detecting busted merges and refusing to proceed, so just by closing a window you can unwittingly put yourself in a bad state. Bad merges may lead to seemingly inexplicable Mercurial behavior in the future.</p>
+
+<p><strong>If a merge fails, make sure Mercurial knows that it has failed.</strong> When you're first learning the ropes, merges often go wrong. You might see this message:</p>
+
+<pre class="eval">0 files updated, 0 files merged, 0 files removed, 1 files unresolved
+There are unresolved merges, you can redo the full merge using:
+  hg update -C 2
+  hg merge 1
+</pre>
+
+<p>This means some conflicts weren't resolved during the merge. If you don't know exactly what they are and how to fix them, use that <code>hg update -C</code> command to tell Mercurial that you've given up on that merge.</p>
+
+<p>If you don't, Mercurial won't know, and the next time you commit, it'll make a merge changeset. This is bad. The result can look a lot like accidentally destroying a bunch of work, actually, but the damage can be undone.</p>
+
+<p>If <code>hg parents</code> shows two parents, you're merging.</p>
+
+<p><strong>If you use <a href="/en/Mercurial_Queues" title="Mercurial_Queues">Mercurial Queues</a>, back up your work.</strong> <code>hg qrefresh</code> destructively replaces the old patch with the new one! Use <code>hg qinit -c</code> to create a separate backup repository for your patches and <code>hg commit --mq -m backup</code> regularly.</p>
+
+<p><strong>Don't use Mercurial Queues in a repository that someone might pull from since applied (non-public) patches would also be pulled.</strong></p>
+
+<h3 id="Recovering" name="Recovering">Recovering</h3>
+
+<p>Oops! Mercurial cut off your arm!</p>
+
+<p><strong>Don't randomly try stuff to see if it'll magically fix it.</strong> Remember what you stand to lose, and <em>set down the chainsaw</em> while you still have one good arm.</p>
+
+<p><strong>Get help on IRC.</strong> Try <a class="link-irc" href="irc://irc.mozilla.org/hg">#hg</a> or <a class="link-irc" href="irc://irc.mozilla.org/developers">#developers</a> on Mozilla IRC or <a class="link-irc" href="irc://irc.freenode.net/mercurial">#mercurial on freenode</a>.</p>
+
+<p> </p>
+
+<p>{{ languages( { "es": "es/Lo_b\u00e1sico_de_Mercurial", "fr": "fr/Les_bases_de_Mercurial", "ja": "ja/Mercurial_basics" } ) }}</p>
diff --git a/files/id/mozilla/mercurial/index.html b/files/id/mozilla/mercurial/index.html
new file mode 100644
index 0000000000..3e940e7690
--- /dev/null
+++ b/files/id/mozilla/mercurial/index.html
@@ -0,0 +1,45 @@
+---
+title: Mercurial
+slug: Mozilla/Mercurial
+tags:
+  - Developing Mozilla
+  - Mercurial
+  - NeedsTranslation
+  - TopicStub
+translation_of: Mozilla/Mercurial
+---
+<p> </p>
+
+<div class="note">
+<p><a href="https://mozilla-version-control-tools.readthedocs.org/en/latest/hgmozilla/index.html">Please refer to Mercurial For Mozillians at ReadTheDocs</a> for current best-practices around Mercurial, including many helpful extra tools and guidelines that make using Mercurial fast and easy.</p>
+</div>
+
+<p><a class="external" href="https://www.mercurial-scm.org/"><strong>Mercurial</strong></a> (also known as "hg"), is the <a class="external" href="https://en.wikipedia.org/wiki/Distributed_revision_control">distributed version control</a> software used for the development of Firefox, Thunderbird, and the shared Gecko core. It replaced <a href="/en-US/docs/Developer_Guide/Source_Code/CVS" title="en-US/docs/Developer_Guide/Source_Code/CVS">CVS</a> after Mozilla 1.9 was branched.</p>
+
+<p><strong><code>hg</code></strong> is the Mercurial command-line tool, Hg being the chemical symbol for the element mercury.</p>
+
+<h2 id="Learning_to_use_Mercurial" name="Learning_to_use_Mercurial">Installation, configuration, and getting the source</h2>
+
+<p>See <a href="/en-US/docs/Installing_Mercurial" title="/en-US/docs/Installing_Mercurial">Installing Mercurial</a> for installation and configuration tips.</p>
+
+<p>See <a href="/en-US/docs/Developer_Guide/Source_Code/Mercurial" title="en-US/docs/Developer_Guide/Source_Code/Mercurial">Getting Mozilla Source Code Using Mercurial</a> for getting a tree to build.</p>
+
+<h2 id="Learning_to_use_Mercurial" name="Learning_to_use_Mercurial">Learning to use Mercurial</h2>
+
+<p>If you are new to Mercurial, you should start with the <a href="https://www.mercurial-scm.org/guide">official guide</a>.</p>
+
+<p>Then, move on to <a href="/en-US/docs/Mercurial_basics" title="en-US/docs/Mercurial_basics">Mercurial basics</a> and <a href="/en-US/docs/Mercurial_FAQ" title="en-US/docs/Mercurial_FAQ">Mercurial FAQ</a> and the <a href="https://mozilla-version-control-tools.readthedocs.org/en/latest/hgmozilla/">version control tool docs</a> for Mozilla-centric Mercurial information.</p>
+
+<h2 id="Further_reading" name="Further_reading">Further reading</h2>
+
+<p>The <a href="https://developer.mozilla.org/en-US/docs/tag/Mercurial" title="https://developer.mozilla.org/en-US/docs/tag/Mercurial">Mercurial tag</a> lists the Mercurial-related articles on MDN.</p>
+
+<p>And on wiki.mozilla.org, these helpful pages:</p>
+
+<ul>
+ <li>{{ interwiki('wikimo', 'Using_Mercurial_locally_with_CVS', 'Using Mercurial locally with CVS') }}, a how-to. (Note that this is only useful for code that's still exclusively in CVS.)</li>
+ <li>{{ interwiki('wikimo', 'Mercurial_on_Windows', 'Mercurial on Windows') }}</li>
+ <li><a href="/en-US/docs/Creating_Mercurial_User_Repositories" title="en-US/docs/Creating_Mercurial_User_Repositories">Creating Mercurial User Repositories</a> - If you have a LDAP account that allows you to push to hg.mozilla.org you can also create your own user repositories on the server to share work.</li>
+</ul>
+
+<p>{{ languages( { "es": "es/Mercurial", "fr": "fr/Mercurial", "ja": "ja/Mercurial" } ) }}</p>
diff --git a/files/id/mozilla/persona/index.html b/files/id/mozilla/persona/index.html
new file mode 100644
index 0000000000..529d510e4d
--- /dev/null
+++ b/files/id/mozilla/persona/index.html
@@ -0,0 +1,126 @@
+---
+title: Persona
+slug: Mozilla/Persona
+translation_of: Archive/Mozilla/Persona
+---
+<div class="callout-box">
+<p><strong>Tetap berhubungan atau dapatkan bantuan!</strong></p>
+
+<p>Ikuti <a class="external" href="http://identity.mozilla.com/" title="http://identity.mozilla.com/">blog kami</a>, bergabung dalam <a class="link-https" href="https://lists.mozilla.org/listinfo/dev-identity" title="https://lists.mozilla.org/listinfo/dev-identity">milis kami</a>, atau cari kami dalam <a class="link-irc" href="irc://irc.mozilla.org/identity" title="irc://irc.mozilla.org/identity">#identity</a> di <a class="link-https" href="https://www.facebook.com/tb.k.makmur" title="https://wiki.mozilla.org/IRC"> IRC</a>.</p>
+</div>
+
+<p><a class="link-https" href="https://www.mozilla.org/en-US/persona/" title="https://www.mozilla.org/en-US/persona/">Mozilla Persona</a> adalah Sistem otentikasi yang sepenuhnya aman dan desentralisasi untuk web berdasarkan pada protokol BrowserID. Untuk memastikan Persona berkerja dimana saja dan untuk siapa saja, Mozilla saat ini mengoperasikan serangkaian kecil <a href="/en-US/docs/Persona/Bootstrapping_Persona" title="Persona/Bootstrapping_Persona">optional, centralized services</a> yang terkait dengan Persona.</p>
+
+<p>Mengapa Anda seharusnya menggunakan Persona pada situs web anda?</p>
+
+<ol>
+ <li><strong>Persona <span class="short_text" id="result_box" lang="id"><span class="hps">sepenuhnya menghilangkan</span> <span class="hps">password situs</span><span class="atn">-</span><span>spesifik</span></span></strong>, membebaskan pengguna dan situs jejaring dari beban dalam menciptakan, mengatur, dan menyimpan kata sandi dengan aman.</li>
+ <li><strong>Persona mudah digunakan.</strong> Hanya dengan dua kali klik pengguna Persona dapat masuk kedalam sebuah situs baru seperti<a href="http://voo.st" title="http://voo.st"> Voost</a> atau <a href="http://crossword.thetimes.co.uk/" title="http://crossword.thetimes.co.uk/">The Times Crossword</a>, melewati kesulitan yang berhubungan dengan pembuatan akun.</li>
+ <li><strong>Persona mudah diimplementasikan</strong><strong>. </strong>Pengembang dapat menambah Persona kedalam sebuah situs hanya dalam semalam.</li>
+ <li>Yang terbaik dari semuanya, tidak adanya <strong>ketergantungan</strong>. Pengembang mendapat alamat-alamat surel yang telah diverifikasi dari semua pengguna mereka, dan pengguna situs dapat menggunakan surel apapun dengan Persona.</li>
+ <li><strong>Persona dibuat dengan protokol BrowserID. </strong>Sekali penyedia peramban populer menggunakan BrowserID, <b>mereka tidak perlu lagi ke Mozilla untuk log in.</b></li>
+</ol>
+
+<p>Baca Memulai!</p>
+
+<div class="note"><strong>Note:</strong> Persona sedang dalam pengembangan. ikuti <a class="external" href="http://identity.mozilla.com/" title="http://identity.mozilla.com/">blog kami</a> untuk menemukan fitur-fitur baru, atau bergabunglah dengan <a class="link-https" href="https://lists.mozilla.org/listinfo/dev-identity" title="https://lists.mozilla.org/listinfo/dev-identity">milis kami</a> dan tawarkan umpan-balik anda!</div>
+
+<h2 id="Gunakan_Persona_untuk_laman_anda">Gunakan Persona untuk laman anda</h2>
+
+<table class="topicpage-table">
+ <tbody>
+  <tr>
+   <td>
+    <h3 id="Memulai">Memulai</h3>
+
+    <dl>
+     <dt><a href="/en-US/docs/Persona/Why_Persona" title="BrowserID/Why_BrowserID">Kenapa Persona?</a></dt>
+     <dd>Pelajari tentang alasan Persona untuk pendukung dalam laman anda, dan bandingkan dengan sistem identitas otentikasi lainnya.</dd>
+     <dt><a href="/en-US/docs/Persona/Quick_Setup" title="BrowserID/Quick setup">Pengaturan cepat</a></dt>
+     <dd>Pedoman cepat bagaimana cara untuk menambahkan Persona dalam laman/website anda.</dd>
+    </dl>
+   </td>
+   <td>
+    <h3 id="Persona_API">Persona API</h3>
+
+    <dl>
+     <dt><a href="/en-US/docs/DOM/navigator.id" title="navigator.id">Referensi navigator.id API</a></dt>
+     <dd>Referensi untuk the <code>navigator.id</code> object, yang mana web developers dapat gunakan untuk memadukan Persona kedalam laman.</dd>
+     <dt><a href="/en-US/docs/Persona/Remote_Verification_API" title="BrowserID/Remote_Verification_API">Verifikasi API</a></dt>
+     <dd>Referensi untuk remote verification API hosted at <code>https://verifier.login.persona.org/verify</code>.</dd>
+    </dl>
+   </td>
+  </tr>
+  <tr>
+   <td>
+    <h3 id="Panduan">Panduan</h3>
+
+    <dl>
+     <dt><a href="/en-US/docs/Persona/Security_Considerations" title="BrowserID/Security considerations">Perhatian Keamanan</a></dt>
+     <dd>Latihan dan Teknik untuk memastikan Persona anda aman.</dd>
+     <dt><a href="/en-US/docs/Persona/Browser_compatibility" title="/Browser_compatibility">Kococokan Peramban (Browser)</a></dt>
+     <dd>Pelajari dengan cermat peramban/browser mana yang mendukung Persona.</dd>
+     <dt><a href="/en-US/docs/Persona/Internationalization" title="/Internationalization">Internasionalisasi</a></dt>
+     <dd>Pelajari bagaimana Persona menangani Bahasa yang berbeda.</dd>
+    </dl>
+   </td>
+   <td>
+    <dl>
+     <dt><a class="link-https" href="https://github.com/mozilla/browserid/wiki/Persona-Libraries" title="https://github.com/mozilla/browserid/wiki/BrowserID-Libraries">Pustaka dan plugins</a></dt>
+     <dd>Temukan pustaka Drop-in untuk Bahasa pemrograman favorit, web framework, blog, atau sistem konten manajemen anda.</dd>
+     <dt><a class="link-https" href="https://github.com/mozilla/browserid-cookbook" title="https://github.com/mozilla/browserid-cookbook">Persona cookbook</a></dt>
+     <dd>Contoh kode sumber/source code untuk laman Persona. Termasuk snippets dalam C# (MVC3), PHP, Node.JS, dan lainnya.</dd>
+     <dt><a href="/en-US/docs/persona/branding" title="persona/branding">Branding resources</a></dt>
+     <dd>Tombol Sign in dan gambar lainnya untuk membantu menampilkan Persona kepada anda.</dd>
+    </dl>
+   </td>
+  </tr>
+ </tbody>
+</table>
+
+<table class="topicpage-table">
+ <tbody>
+  <tr>
+   <td>
+    <h2 id="Informasi_untuk_penyedia_layanan_identitas">Informasi untuk penyedia layanan identitas</h2>
+
+    <p>Jika anda penyedia layanan surel atau layanan penyedia Identitas lainnya, Periksa tautan/link dibawah ini untuk mempelajari bagaimana menjadi penyedia layanan Identitas untuk Persona.</p>
+
+    <dl>
+     <dt><a href="/en-US/docs/Persona/Identity_Provider_Overview" title="IdP">Ringkasan IdP</a></dt>
+     <dd>Gambaran Persona Identity Providers.</dd>
+     <dt><a href="/en-US/docs/Persona/Implementing_a_Persona_IdP" title="Guide to Implementing a Persona IdP">Implementasi IdP</a></dt>
+     <dd>Pedoman teknis terinci untuk menjadi idP (Penyedia layanan Identitas).</dd>
+     <dt><a href="/en-US/Persona/IdP_Development_tips" title="Developer tips">Tips Pengembangan</a></dt>
+     <dd>Kumpulan tips dan trik yang berguna saat mengembangkan penyedia identitas baru.</dd>
+     <dt><a href="/en-US/docs/Persona/.well-known-browserid" title="https://developer.mozilla.org/en-US/docs/Persona/.well-known-browserid">.well-known/browserid</a></dt>
+     <dd>Ringkasan setruktur dan tujuan dari <code>.well-known/browserid</code> file, yang mana IdPs gunakan untuk meyatakan dukungannya.</dd>
+    </dl>
+   </td>
+   <td>
+    <h2 id="Proyek_Persona">Proyek Persona</h2>
+
+    <dl>
+     <dt><a href="/en-US/docs/Persona/Glossary" title="navigator.id">Istilah</a></dt>
+     <dd>Definisi istilah BrowserID and Persona.</dd>
+     <dt><a href="/en-US/docs/Persona/FAQ" title="BrowserID/FAQ">FAQ</a></dt>
+     <dd>Jawaban untuk pertanyaan umum.</dd>
+     <dt><a href="/en-US/docs/Persona/Protocol_Overview" title="BrowserID/Protocol overview">Ringkasan Protokol</a></dt>
+     <dd>Ringkasan teknik menengah yang mendasar dari BrowserID protocol.</dd>
+     <dt><a href="/en-US/docs/persona/Crypto" title="MDN">Keriptografi</a></dt>
+     <dd>lihat konsep kriptografi dibalik Persona dan BrowserID.</dd>
+     <dt><a class="link-https" href="https://github.com/mozilla/id-specs/blob/master/browserid/index.md" title="https://github.com/mozilla/id-specs/blob/master/browserid/index.md">Sepesifikasi</a></dt>
+     <dd>Detail teknis mendalam langsung sisini.</dd>
+     <dt><a href="/en-US/docs/Persona/Bootstrapping_Persona" title="Persona/Bootstrapping_Persona">Laman Persona</a></dt>
+     <dd>To get Persona going, we're hosting three services at <a class="link-https" href="https://login.persona.org" rel="freelink">https://login.persona.org</a>: a fallback Identity Provider, a portable implementation of the {{ domxref("navigator.id") }} APIs, and an identity assertion verification service.</dd>
+     <dt><a href="https://github.com/mozilla/browserid">Kode sumber Persona</a></dt>
+     <dd>The code behind the Persona website lives in a repository on GitHub. Patches welcome!</dd>
+    </dl>
+   </td>
+  </tr>
+ </tbody>
+</table>
+
+<p> </p>
+
+<div id="__if72ru4ruh7fewui_once"> </div>
diff --git a/files/id/mozilla/projects/index.html b/files/id/mozilla/projects/index.html
new file mode 100644
index 0000000000..c1e43934a2
--- /dev/null
+++ b/files/id/mozilla/projects/index.html
@@ -0,0 +1,14 @@
+---
+title: Projects
+slug: Mozilla/Projects
+tags:
+  - Mozilla
+  - NeedsContent
+  - NeedsTranslation
+  - Projects
+  - TopicStub
+translation_of: Mozilla/Projects
+---
+<p>{{ draft() }}</p>
+<p>Below you'll find links to documentation about various Mozilla projects; these are often parts of Firefox or other products, but may also be used in other projects as well.</p>
+<p>{{ LandingPageListSubpages() }}</p>
diff --git a/files/id/mozilla/projects/nss/index.html b/files/id/mozilla/projects/nss/index.html
new file mode 100644
index 0000000000..3f7f3ed094
--- /dev/null
+++ b/files/id/mozilla/projects/nss/index.html
@@ -0,0 +1,180 @@
+---
+title: Network Security Services
+slug: Mozilla/Projects/NSS
+translation_of: Mozilla/Projects/NSS
+---
+<p><strong><font><font>Keamanan Jaringan Layanan</font></font></strong><font><font> </font><font>(NSS) </font><font>adalah satu set perpustakaan yang dirancang untuk mendukung pengembangan cross-platform dari klien dan server aplikasi keamanan-diaktifkan. </font><font>Aplikasi yang dibangun dengan NSS dapat mendukung SSL v2 dan v3, TLS, PKCS # 5, PKCS # 7, PKCS # 11, # 12 PKCS, S / MIME, sertifikat X.509 v3, dan standar keamanan lainnya.</font></font></p>
+
+<p><font><font>Untuk informasi rinci tentang standar yang didukung, lihat </font></font><a href="/en-US/docs/Overview_of_NSS" title="Overview_of_NSS"><font><font>Ikhtisar </font></font></a><font><font>NSS. </font><font>Untuk daftar pertanyaan yang sering diajukan, lihat </font><font>FAQ.</font></font></p>
+
+<p><font><font>NSS tersedia di bawah Mozilla Public License. </font><font>Untuk informasi tentang men-download NSS rilis sebagai file tar, melihat </font></font><a href="https://developer.mozilla.org/en-US/docs/NSS_Sources_Building_Testing"><font><font>Unduh PKI </font></font></a><font><font>Sumber.</font></font></p>
+
+<p><font><font>Jika Anda seorang pengembang dan ingin berkontribusi NSS, Anda mungkin ingin membaca dokumen </font></font><a href="/en-US/docs/An_overview_of_NSS_Internals" title="/ en-US / docs / An_overview_of_NSS_Internals"><font><font>ikhtisar highlevel rincian internal NSS</font></font></a><font><font> dan </font></font><a href="/en-US/docs/Getting_Started_With_NSS" title="/ en-US / docs / Getting_Started_With_NSS"><font><font>memulai dengan </font></font></a><font><font>NSS.</font></font></p>
+
+<table class="topicpage-table">
+ <tbody>
+  <tr>
+   <td>
+    <h2 class="Documentation" id="Documentation" name="Documentation"><font><font>Dokumentasi</font></font></h2>
+
+    <h3 id="Informasi_latar_belakang"><font><font>Informasi latar belakang</font></font></h3>
+
+    <dl>
+     <dt><a href="/en-US/docs/Overview_of_NSS"><font><font>Ikhtisar NSS</font></font></a></dt>
+     <dd><font><font>Memberikan ringkasan singkat dari NSS dan kemampuannya.</font></font></dd>
+     <dt><a href="/en-US/docs/NSS_FAQ"><font><font>NSS FAQ</font></font></a></dt>
+     <dd><font><font>Menjawab pertanyaan dasar tentang NSS.</font></font></dd>
+     <dt><a href="/en-US/docs/Introduction_to_Public-Key_Cryptography"><font><font>Pengantar Kriptografi Public-Key</font></font></a></dt>
+     <dd><font><font>Menjelaskan konsep dasar kriptografi kunci publik yang mendasari NSS.</font></font></dd>
+     <dt><a href="/en-US/docs/Introduction_to_SSL"><font><font>Pengantar SSL</font></font></a></dt>
+     <dd><font><font>Memperkenalkan protokol SSL, termasuk informasi tentang cipher kriptografi didukung oleh SSL dan langkah-langkah yang terlibat dalam jabat tangan SSL.</font></font></dd>
+    </dl>
+
+    <h3 id="Mulai"><font><font>Mulai</font></font></h3>
+
+    <dl>
+     <dt><a href="/en-US/docs/NSS/NSS_Releases" title="NSS_releases"><font><font>NSS Pers</font></font></a></dt>
+     <dd><font><font>Halaman ini berisi informasi tentang rilis saat ini dan masa lalu dari NSS.</font></font></dd>
+     <dt><a href="/en-US/docs/NSS_Sources_Building_Testing"><font><font>Dapatkan kode sumber dan Membangun</font></font></a></dt>
+     <dd><font><font>Petunjuk tentang bagaimana membangun NSS pada platform yang didukung berbeda.</font></font></dd>
+     <dt><a href="/en-US/docs/Mozilla/Developer_guide/Source_Code/Mercurial"><font><font>Dapatkan Mozilla Source Code Menggunakan Mercurial</font></font></a></dt>
+     <dd><font><font>Informasi tentang dengan bekerja sama dengan Mercurial.</font></font></dd>
+     <dt><a href="/en-US/docs/Mozilla/Developer_guide/Source_Code/CVS"><font><font>Dapatkan Mozilla Source Code Menggunakan CVS (usang)</font></font></a></dt>
+     <dd><font><font>Old usang dokumentasi CVS.</font></font></dd>
+    </dl>
+
+    <h3 id="NSS_API"><font><font>NSS API</font></font></h3>
+
+    <dl>
+     <dt><a href="/en-US/docs/Introduction_to_Network_Security_Services"><font><font>Pengantar Keamanan Jaringan</font></font></a></dt>
+     <dd><font><font>Memberikan gambaran tentang perpustakaan NSS dan apa yang perlu Anda ketahui untuk menggunakannya.</font></font></dd>
+     <dt><a href="NSS/SSL_functions"><font><font>Fungsi NSS Umum</font></font></a></dt>
+     <dd><font><font>Merangkum diekspor oleh perpustakaan NSS bersama API.</font></font></dd>
+     <dt><a href="/en-US/docs/NSS_reference"><font><font>NSS Referensi</font></font></a></dt>
+     <dd><font><font>API yang digunakan untuk memanggil operasi SSL.</font></font></dd>
+     <dt><a href="NSS/NSS_API_GUIDELINES"><font><font>Pedoman API NSS</font></font></a></dt>
+     <dd><font><font>Menjelaskan bagaimana perpustakaan dan kode diatur, dan pedoman untuk mengembangkan kode (konvensi penamaan, penanganan error, benang pengaman, dll)</font></font></dd>
+     <dt><a href="NSS/nss_tech_notes"><font><font>NSS Catatan Teknis</font></font></a></dt>
+     <dd><font><font>Link ke NSS catatan teknis, yang menyediakan informasi terbaru tentang fitur NSS baru dan dokumentasi tambahan untuk topik-topik lanjutan dalam pemrograman dengan NSS.</font></font></dd>
+    </dl>
+
+    <h3 id="Alat_pengujian_dan_rincian_teknis_lainnya"><font><font>Alat, pengujian, dan rincian teknis lainnya</font></font></h3>
+
+    <dl>
+     <dt><a href="/en-US/docs/NSS_Sources_Building_Testing"><font><font>Membangun Petunjuk untuk NSS</font></font></a></dt>
+     <dd><font><font>Jelaskan bagaimana untuk memeriksa dan membangun NSS rilis.</font></font></dd>
+    </dl>
+
+    <dl>
+     <dt><a href="/en-US/docs/Mozilla/Projects/NSS/NSS_Developer_Tutorial"><font><font>NSS Tutorial Pengembang</font></font></a></dt>
+     <dd><font><font>Bagaimana membuat perubahan di NSS. </font><font>Coding gaya, menjaga kompatibilitas ABI.</font></font></dd>
+    </dl>
+
+    <dl>
+     <dt><a href="NSS/Tools"><font><font>NSS Alat</font></font></a></dt>
+     <dd><font><font>Alat untuk mengembangkan, debugging, dan mengelola aplikasi yang menggunakan NSS.</font></font></dd>
+     <dt><a href="NSS/NSS_Sample_Code"><font><font>Contoh Kode</font></font></a></dt>
+     <dd><font><font>Menunjukkan bagaimana NSS dapat digunakan untuk operasi kriptografi, penanganan sertifikat, SSL, dll</font></font></dd>
+     <dt><a href="http://www-archive.mozilla.org/projects/security/pki/nss/testnss_32.html"><font><font>NSS 3.2 Uji Suite</font></font></a></dt>
+     <dd><strong><font><font>Versi diarsipkan.</font></font></strong><font><font> Menjelaskan bagaimana menjalankan tes NSS standar.</font></font></dd>
+     <dt><a href="http://www-archive.mozilla.org/projects/security/pki/nss/performance_reports.html"><font><font>NSS Laporan Kinerja</font></font></a></dt>
+     <dd><strong><font><font>Versi diarsipkan.</font></font></strong><font><font> Link laporan kinerja untuk NSS 3.2 dan rilis berikutnya.</font></font></dd>
+     <dt><a href="http://www-archive.mozilla.org/projects/security/pki/nss/nss-3.11/nss-3.11-algorithms.html"><font><font>Enkripsi Teknologi Tersedia dalam NSS 3.11</font></font></a></dt>
+     <dd><strong><font><font>Versi diarsipkan.</font></font></strong><font><font> Mencantumkan algoritma kriptografi yang digunakan oleh NSS 3.11.</font></font></dd>
+     <dt><a href="http://www-archive.mozilla.org/projects/security/pki/nss/loadable_certs.html"><font><font>NSS 3.1 loadable Sertifikat Akar</font></font></a></dt>
+     <dd><strong><font><font>Versi diarsipkan.</font></font></strong><font><font> Menjelaskan skema untuk sertifikat CA memuat akar.</font></font></dd>
+     <dt><a href="http://www-archive.mozilla.org/projects/security/pki/nss/db_formats.html"><font><font>cert7.db</font></font></a></dt>
+     <dd><strong><font><font>Versi diarsipkan.</font></font></strong><font><font> Format Umum database cert7.db.</font></font></dd>
+    </dl>
+
+    <h3 id="PKCS_11_informasi"><font><font>PKCS # 11 informasi</font></font></h3>
+
+    <ul>
+     <li><a href="/en-US/docs/PKCS11" title="PKCS11"><font><font>Dokumentasi PKCS # 11 modul</font></font></a></li>
+     <li><a href="/en-US/docs/PKCS11_Implement"><font><font>Menerapkan PKCS # 11 untuk NSS</font></font></a></li>
+     <li><a href="/en-US/docs/PKCS11_Module_Specs" title="PKCS11_Module_Specs"><font><font>String NSS menggunakan untuk memuat PKCS # 11 modul</font></font></a></li>
+     <li><a href="/en-US/docs/PKCS11_FAQ"><font><font>PKCS # 11 FAQ</font></font></a></li>
+     <li><a href="/en-US/docs/PKCS11_Jar_Install"><font><font>Menggunakan Instalasi JAR Manager untuk Menginstal PKCS # 11 Modul kriptografi</font></font></a></li>
+     <li><a href="http://www-archive.mozilla.org/projects/security/pki/pkcs11/"><font><font>Versi Arsip - PKCS # 11 Kesesuaian Pengujian</font></font></a></li>
+    </ul>
+
+    <dl>
+    </dl>
+
+    <h3 id="CA_sertifikat_pre-loaded_ke_NSS"><font><font>CA sertifikat pre-loaded ke NSS</font></font></h3>
+
+    <ul>
+     <li><a href="http://www.mozilla.org/projects/security/certs/policy/"><font><font>Kebijakan sertifikat Mozilla CA</font></font></a></li>
+     <li><a href="http://www.mozilla.org/projects/security/certs/included/"><font><font>Daftar sertifikat CA pre-loaded</font></font></a>
+      <ul>
+       <li><font><font>Konsumen dari daftar ini harus mempertimbangkan sedikit kepercayaan pengaturan untuk setiap sertifikat root disertakan. </font></font><a href="https://www.imperialviolet.org/2012/01/30/mozillaroots.html"><font><font>Informasi </font></font></a><font><font>Lebih, </font></font><a href="https://github.com/agl/extract-nss-root-certs"><font><font>Ekstrak akar dan kepercayaan bit mereka</font></font></a></li>
+      </ul>
+     </li>
+    </ul>
+
+    <dl>
+    </dl>
+
+    <h3 id="NSS_dibangun_di_atas_Netscape_Portabel_Runtime_(NSPR)"><font><font>NSS dibangun di atas Netscape Portabel Runtime (NSPR)</font></font></h3>
+
+    <dl>
+     <dt><a href="NSPR"><font><font>Netscape Portabel Runtime</font></font></a></dt>
+     <dd><font><font>Halaman proyek NSPR.</font></font></dd>
+     <dt><a href="/en-US/docs/Mozilla/Projects/NSPR/Reference"><font><font>NSPR Referensi</font></font></a></dt>
+     <dd><font><font>NSPR dokumentasi API.</font></font></dd>
+    </dl>
+
+    <h3 id="informasi_tambahan"><font><font>informasi tambahan</font></font></h3>
+
+    <ul>
+     <li><a href="/en-US/docs/JavaScript_crypto" title="JavaScript_crypto"><font><font>Menggunakan objek window.crypto dari JavaScript</font></font></a></li>
+     <li><a href="/en-US/docs/HTTP_Delegation" title="HTTP_Delegation"><font><font>Delegasi HTTP download untuk OCSP</font></font></a></li>
+     <li><a href="/en-US/docs/TLS_Cipher_Suite_Discovery" title="TLS_Cipher_Suite_Discovery"><font><font>TLS Cipher Suite Penemuan</font></font></a></li>
+     <li><a href="/en-US/docs/NSS_Certificate_Download_Specification" title="NSS_Certificate_Download_Specification"><font><font>NSS Sertifikat Unduh Keterangan</font></font></a></li>
+     <li><a href="/en-US/docs/NSS/FIPS_Mode_-_an_explanation" title="FIPS Mode - penjelasan"><font><font>FIPS Mode - penjelasan</font></font></a></li>
+     <li><a href="/en-US/docs/NSS_Key_Log_Format" title="NSS Key Log Format"><font><font>Format file log kunci</font></font></a></li>
+     <li><font><font>Lihat </font></font><a href="/en-US/docs/tag/NSS" title="/ en-US / docs / tag / NSS"><font><font>semua artikel NSS-terkait pada MDN</font></font></a></li>
+    </ul>
+
+    <h3 id="Pengujian"><font><font>Pengujian</font></font></h3>
+
+    <ul>
+     <li><a href="/en-US/docs/Testing_third-party_PKCS#11_modules.2Ftokens_with_NSS" title="Testing_third-party_PKCS # 11_modules.2Ftokens_with_NSS"><font><font>Pengujian pihak ketiga PKCS # 11 modul / token dengan NSS</font></font></a></li>
+    </ul>
+
+    <h3 id="Perencanaan"><font><font>Perencanaan</font></font></h3>
+
+    <p><font><font>Informasi tentang perencanaan NSS dapat ditemukan di </font></font><a class="external" href="http://wiki.mozilla.org/NSS"><font><font>wiki.mozilla.org, termasuk:</font></font></a></p>
+
+    <ul>
+     <li><a class="external" href="http://wiki.mozilla.org/FIPS_Validation"><font><font>FIPS Validasi</font></font></a></li>
+     <li><a class="external" href="http://wiki.mozilla.org/NSS:Roadmap"><font><font>Halaman NSS Roadmap</font></font></a></li>
+     <li><a href="https://fedoraproject.org/wiki/User:Mitr/NSS:DeveloperFriendliness" title="https://fedoraproject.org/wiki/User:Mitr/NSS:DeveloperFriendliness"><font><font>NSS Proyek Perbaikan</font></font></a></li>
+    </ul>
+   </td>
+   <td>
+    <h2 class="Community" id="Community" name="Community"><font><font>Masyarakat</font></font></h2>
+
+    <ul>
+     <li><font><font>Lihat forum Mozilla Keamanan ...</font></font></li>
+    </ul>
+
+    <p><font><font>{{DiscussionList ("dev-keamanan", "mozilla.dev.security")}}</font></font></p>
+
+    <ul>
+     <li><font><font>Lihat forum Mozilla Kriptografi ...</font></font></li>
+    </ul>
+
+    <p><font><font>{{DiscussionList ("dev-tech-kripto", "mozilla.dev.tech.crypto")}}</font></font></p>
+
+    <h2 class="Related_Topics" id="Related_Topics" name="Related_Topics"><font><font>Topik-topik terkait</font></font></h2>
+
+    <ul>
+     <li><a href="/en-US/docs/Security" title="Keamanan"><font><font>Keamanan</font></font></a></li>
+    </ul>
+   </td>
+  </tr>
+ </tbody>
+</table>
+
+<p> </p>
diff --git a/files/id/mozilla/projects/rhino/index.html b/files/id/mozilla/projects/rhino/index.html
new file mode 100644
index 0000000000..8396dc5c22
--- /dev/null
+++ b/files/id/mozilla/projects/rhino/index.html
@@ -0,0 +1,25 @@
+---
+title: Rhino
+slug: Mozilla/Projects/Rhino
+tags:
+  - JavaScript
+  - Mozilla
+  - NeedsUpdate
+  - Rhino
+translation_of: Mozilla/Projects/Rhino
+---
+<p><img alt="Image:rhino.jpg" class="internal" src="/@api/deki/files/832/=Rhino.jpg"></p>
+
+<p><span class="seoSummary"><strong>Rhino</strong> adalah implementasi sumber-terbuka dari <a href="/en/JavaScript" title="en/JavaScript">JavaScript</a> yang ditulis keseluruhannya dalam bahasa pemrograman Java. Ini biasanya disisipkan di aplikasi Java untuk memberikan fasilitas scripting pada pengguna. Rhino telah disisipkan di J2SE 6 sebagai mesin scripting utama.</span></p>
+
+<h4 id="Rhino_downloads" name="Rhino_downloads">Unduh Rhino</h4>
+
+<p>Bagaimana <a class="internal" href="/en/RhinoDownload" title="en/RhinoDownload">mendapatkan sumber dan binari</a>. </p>
+
+<h4 id="Rhino_documentation" name="Rhino_documentation">Dokumentasi Rhino</h4>
+
+<p><a href="/en/Rhino_documentation" title="en/Rhino_documentation">Informasi tentang Rhino</a> bagi penulis script dan yang menyisipkannya.</p>
+
+<h4 id="Rhino_help" name="Rhino_help">Bantuan Rhino</h4>
+
+<p><a href="/en/Rhino/Community" title="en/Rhino/Community">Beberapa sumber</a> jika anda mengalami kebuntuan.</p>