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

16 files changed, 0 insertions, 2022 deletions

diff --git a/files/hu/_wikihistory.json b/files/hu/_wikihistory.json
deleted file mode 100644
index a768f67f81..0000000000
--- a/files/hu/_wikihistory.json
+++ /dev/null
@@ -1,566 +0,0 @@
-{
-  "Bevezetés_a_dokumentumobjektum-modellbe": {
-    "modified": "2019-03-23T23:46:33.058Z",
-    "contributors": [
-      "teoli",
-      "Csörföly D"
-    ]
-  },
-  "CSS": {
-    "modified": "2019-09-11T03:36:12.939Z",
-    "contributors": [
-      "SphinxKnight",
-      "tetkosimi",
-      "teoli",
-      "CsörfölyD"
-    ]
-  },
-  "CSS/CSS_Grid_Layout": {
-    "modified": "2019-03-18T21:34:45.745Z",
-    "contributors": [
-      "kecskeskrisztian"
-    ]
-  },
-  "CSS/font-weight": {
-    "modified": "2020-11-12T12:54:39.738Z",
-    "contributors": [
-      "evasimonyi"
-    ]
-  },
-  "CSS/text-decoration": {
-    "modified": "2020-11-12T10:40:09.368Z",
-    "contributors": [
-      "evasimonyi"
-    ]
-  },
-  "DOM": {
-    "modified": "2019-03-24T00:03:55.193Z",
-    "contributors": [
-      "ethertank",
-      "fscholz",
-      "Csörföly D"
-    ]
-  },
-  "DOM/HTMLBRElement": {
-    "modified": "2019-03-23T23:31:58.209Z",
-    "contributors": [
-      "khalid32",
-      "urbalazs"
-    ]
-  },
-  "Glossary": {
-    "modified": "2020-10-07T11:10:36.306Z",
-    "contributors": [
-      "peterbe",
-      "SphinxKnight",
-      "Szelmat",
-      "wbamberg",
-      "david_ross"
-    ]
-  },
-  "Glossary/AJAX": {
-    "modified": "2020-07-28T09:05:23.645Z",
-    "contributors": [
-      "mmarci72"
-    ]
-  },
-  "Glossary/API": {
-    "modified": "2020-03-23T13:25:05.816Z",
-    "contributors": [
-      "Zoldszemesostoros"
-    ]
-  },
-  "Glossary/Abstraction": {
-    "modified": "2020-07-27T18:42:18.284Z",
-    "contributors": [
-      "mmarci72"
-    ]
-  },
-  "Glossary/CSS": {
-    "modified": "2020-07-28T08:31:28.048Z",
-    "contributors": [
-      "mmarci72"
-    ]
-  },
-  "Glossary/Callback_function": {
-    "modified": "2020-11-18T15:57:46.953Z",
-    "contributors": [
-      "evasimonyi"
-    ]
-  },
-  "Glossary/Elso_osztalyu_funkciok": {
-    "modified": "2019-03-18T20:56:29.186Z",
-    "contributors": [
-      "Szelmat"
-    ]
-  },
-  "Glossary/JavaScript": {
-    "modified": "2020-11-16T15:08:28.654Z",
-    "contributors": [
-      "meskobalazs",
-      "Szelmat"
-    ]
-  },
-  "Glossary/Node.js": {
-    "modified": "2019-03-18T20:56:27.754Z",
-    "contributors": [
-      "Szelmat"
-    ]
-  },
-  "Glossary/bongeszo": {
-    "modified": "2020-07-28T08:32:30.144Z",
-    "contributors": [
-      "mmarci72"
-    ]
-  },
-  "Learn": {
-    "modified": "2020-11-16T14:42:59.018Z",
-    "contributors": [
-      "meskobalazs",
-      "Zoldszemesostoros",
-      "SphinxKnight",
-      "qcz",
-      "lacsaba",
-      "entriek"
-    ]
-  },
-  "Learn/HTML": {
-    "modified": "2020-07-16T22:22:18.146Z",
-    "contributors": [
-      "chrisdavidmills"
-    ]
-  },
-  "Learn/HTML/Bevezetes_a_HTML-be": {
-    "modified": "2020-07-16T22:22:48.153Z",
-    "contributors": [
-      "tetkosimi"
-    ]
-  },
-  "Learn/Ismerkedés_a_Világhálóval": {
-    "modified": "2020-07-29T16:23:02.755Z",
-    "contributors": [
-      "szcsl"
-    ]
-  },
-  "Learn/Ismerkedés_a_Világhálóval/Alapvető_programok_telepítése": {
-    "modified": "2020-07-31T12:06:30.955Z",
-    "contributors": [
-      "szcsl"
-    ]
-  },
-  "Learn/Ismerkedés_a_Világhálóval/Hogy_fog_kinézni_a_weboldalunk": {
-    "modified": "2020-08-02T13:33:58.088Z",
-    "contributors": [
-      "szcsl"
-    ]
-  },
-  "Learn/JavaScript": {
-    "modified": "2020-07-16T22:29:39.465Z",
-    "contributors": [
-      "entriek"
-    ]
-  },
-  "Learn/JavaScript/Első_lépések": {
-    "modified": "2020-07-16T22:29:51.271Z",
-    "contributors": [
-      "Aioiui"
-    ]
-  },
-  "Learn/Server-side": {
-    "modified": "2020-07-16T22:35:58.128Z",
-    "contributors": [
-      "chrisdavidmills"
-    ]
-  },
-  "MDN": {
-    "modified": "2020-02-19T19:33:49.798Z",
-    "contributors": [
-      "jswisher",
-      "SphinxKnight",
-      "wbamberg",
-      "meskobalazs",
-      "ziyunfei"
-    ]
-  },
-  "MDN/Contribute": {
-    "modified": "2019-01-16T19:05:51.848Z",
-    "contributors": [
-      "wbamberg",
-      "meskobalazs",
-      "Mars"
-    ]
-  },
-  "MDN/Contribute/Getting_started": {
-    "modified": "2020-09-30T17:11:57.281Z",
-    "contributors": [
-      "chrisdavidmills",
-      "meskobalazs",
-      "nagyll92",
-      "wbamberg",
-      "hu-nemtom",
-      "bencelaszlo",
-      "misibacsi",
-      "zamcsaba"
-    ]
-  },
-  "MDN/Contribute/Localize": {
-    "modified": "2019-01-16T22:09:06.657Z",
-    "contributors": [
-      "wbamberg",
-      "meskobalazs",
-      "jswisher"
-    ]
-  },
-  "MDN/Contribute/Localize/Oldalak_fordítása": {
-    "modified": "2019-12-17T21:18:30.022Z",
-    "contributors": [
-      "wbamberg",
-      "meskobalazs"
-    ]
-  },
-  "Mozilla": {
-    "modified": "2019-03-23T23:33:12.472Z",
-    "contributors": [
-      "evilpie"
-    ]
-  },
-  "Tools": {
-    "modified": "2020-07-16T22:44:15.072Z",
-    "contributors": [
-      "SphinxKnight",
-      "kamryn12"
-    ]
-  },
-  "Web": {
-    "modified": "2019-03-23T23:25:29.899Z",
-    "contributors": [
-      "saboarpad",
-      "Rwin",
-      "barineveronika",
-      "csehferi70@gmail.com",
-      "teoli"
-    ]
-  },
-  "Web/API": {
-    "modified": "2020-03-29T19:59:47.494Z",
-    "contributors": [
-      "duduindo",
-      "teoli",
-      "Sheppy"
-    ]
-  },
-  "Web/API/Document": {
-    "modified": "2020-10-15T22:28:55.605Z",
-    "contributors": [
-      "sideshowbarker"
-    ]
-  },
-  "Web/API/Document/createTextNode": {
-    "modified": "2020-10-15T22:28:37.188Z",
-    "contributors": [
-      "sarkiroka"
-    ]
-  },
-  "Web/API/Fetch_API": {
-    "modified": "2020-11-30T07:30:25.951Z",
-    "contributors": [
-      "evasimonyi"
-    ]
-  },
-  "Web/API/File": {
-    "modified": "2019-03-23T22:02:41.390Z",
-    "contributors": [
-      "chrisdavidmills"
-    ]
-  },
-  "Web/API/Geolocation": {
-    "modified": "2019-03-23T22:46:03.917Z",
-    "contributors": [
-      "fscholz"
-    ]
-  },
-  "Web/API/WebXR_Device_API": {
-    "modified": "2020-10-15T22:31:19.815Z",
-    "contributors": [
-      "Peilei0313"
-    ]
-  },
-  "Web/API/Window": {
-    "modified": "2020-10-15T22:20:56.772Z",
-    "contributors": [
-      "chrisdavidmills"
-    ]
-  },
-  "Web/API/Window.stop": {
-    "modified": "2019-03-23T23:25:32.999Z",
-    "contributors": [
-      "jsx",
-      "mark_b"
-    ]
-  },
-  "Web/API/Window/alert": {
-    "modified": "2020-10-15T22:20:45.271Z",
-    "contributors": [
-      "sarkiroka"
-    ]
-  },
-  "Web/API/Worker": {
-    "modified": "2019-03-23T22:21:12.416Z",
-    "contributors": [
-      "Csucsu734"
-    ]
-  },
-  "Web/API/XMLHttpRequest": {
-    "modified": "2020-10-15T21:58:25.775Z",
-    "contributors": [
-      "dominicus-75",
-      "fscholz"
-    ]
-  },
-  "Web/API/XMLHttpRequest/XMLHttpRequest_hasznalata": {
-    "modified": "2020-10-15T22:19:50.902Z",
-    "contributors": [
-      "dominicus-75"
-    ]
-  },
-  "Web/CSS/Tools": {
-    "modified": "2019-03-23T22:57:26.063Z",
-    "contributors": [
-      "velvel53"
-    ]
-  },
-  "Web/CSS/Tools/Border-radius_bemutato": {
-    "modified": "2019-03-23T22:57:32.009Z",
-    "contributors": [
-      "nemesreviz"
-    ]
-  },
-  "Web/Guide": {
-    "modified": "2019-03-23T23:16:53.049Z",
-    "contributors": [
-      "Onsteroids"
-    ]
-  },
-  "Web/Guide/API": {
-    "modified": "2019-09-11T09:42:54.699Z",
-    "contributors": [
-      "SphinxKnight",
-      "Sheppy"
-    ]
-  },
-  "Web/Guide/Grafika": {
-    "modified": "2019-05-08T07:13:14.821Z",
-    "contributors": [
-      "tetkosimi"
-    ]
-  },
-  "Web/HTML": {
-    "modified": "2019-05-09T07:19:07.882Z",
-    "contributors": [
-      "tetkosimi",
-      "JLorand",
-      "teoli",
-      "dbs"
-    ]
-  },
-  "Web/HTML/Element": {
-    "modified": "2019-03-23T23:31:53.992Z",
-    "contributors": [
-      "teoli"
-    ]
-  },
-  "Web/HTML/Element/article": {
-    "modified": "2020-10-15T21:59:45.091Z",
-    "contributors": [
-      "parphis"
-    ]
-  },
-  "Web/HTML/Element/br": {
-    "modified": "2020-03-29T20:04:13.246Z",
-    "contributors": [
-      "duduindo",
-      "teoli",
-      "urbalazs"
-    ]
-  },
-  "Web/HTML/Element/section": {
-    "modified": "2020-10-15T21:59:45.803Z",
-    "contributors": [
-      "parphis"
-    ]
-  },
-  "Web/JavaScript": {
-    "modified": "2019-03-18T20:56:29.622Z",
-    "contributors": [
-      "Szelmat",
-      "pannisimai",
-      "tacsipacsi",
-      "entonibaba0720",
-      "bencelaszlo",
-      "szabopeterakos",
-      "Ferik355",
-      "teoli",
-      "fscholz",
-      "CsörfölyD"
-    ]
-  },
-  "Web/JavaScript/Guide": {
-    "modified": "2020-03-12T19:37:34.357Z",
-    "contributors": [
-      "teoli",
-      "Csörföly D",
-      "CsörfölyD"
-    ]
-  },
-  "Web/JavaScript/Guide/Bevezetés": {
-    "modified": "2020-03-12T19:43:36.391Z",
-    "contributors": [
-      "RMarcell"
-    ]
-  },
-  "Web/JavaScript/Reference": {
-    "modified": "2020-11-19T10:10:24.248Z",
-    "contributors": [
-      "Sealdolphin",
-      "tomuwhu",
-      "bencelaszlo",
-      "Minat"
-    ]
-  },
-  "Web/JavaScript/Reference/Errors": {
-    "modified": "2020-03-12T19:47:09.844Z",
-    "contributors": [
-      "Sheppy"
-    ]
-  },
-  "Web/JavaScript/Reference/Errors/Bad_return_or_yield": {
-    "modified": "2020-03-23T13:33:05.843Z",
-    "contributors": [
-      "Zoldszemesostoros",
-      "sanyoca"
-    ]
-  },
-  "Web/JavaScript/Reference/Errors/Stmt_after_return": {
-    "modified": "2020-03-23T13:42:19.587Z",
-    "contributors": [
-      "Zoldszemesostoros",
-      "sanyoca"
-    ]
-  },
-  "Web/JavaScript/Reference/Errors/Unexpected_token": {
-    "modified": "2020-03-12T19:47:09.248Z",
-    "contributors": [
-      "dorionka"
-    ]
-  },
-  "Web/JavaScript/Reference/Errors/Érvénytelen_típus": {
-    "modified": "2020-04-19T20:35:18.887Z",
-    "contributors": [
-      "tacsipacsi",
-      "sanyoca"
-    ]
-  },
-  "Web/JavaScript/Reference/Global_Objects": {
-    "modified": "2020-03-12T19:45:17.938Z",
-    "contributors": [
-      "Abro"
-    ]
-  },
-  "Web/JavaScript/Reference/Global_Objects/Array": {
-    "modified": "2019-12-26T16:08:19.491Z",
-    "contributors": [
-      "ferenczcsibiattila",
-      "kdex"
-    ]
-  },
-  "Web/JavaScript/Reference/Global_Objects/Array/keys": {
-    "modified": "2020-10-15T22:04:22.331Z",
-    "contributors": [
-      "parphis"
-    ]
-  },
-  "Web/JavaScript/Reference/Global_Objects/Array/of": {
-    "modified": "2020-10-15T22:21:12.095Z",
-    "contributors": [
-      "szilijanos"
-    ]
-  },
-  "Web/JavaScript/Reference/Global_Objects/Array/sort": {
-    "modified": "2019-09-04T07:17:17.546Z",
-    "contributors": [
-      "krisz094",
-      "KissBalazs",
-      "chvik",
-      "sonny89",
-      "brncsk",
-      "LeFizzy"
-    ]
-  },
-  "Web/JavaScript/Reference/Global_Objects/Error": {
-    "modified": "2020-11-22T11:34:23.222Z",
-    "contributors": [
-      "Sealdolphin"
-    ]
-  },
-  "Web/JavaScript/Reference/Global_Objects/Függvény": {
-    "modified": "2020-11-16T15:30:24.183Z",
-    "contributors": [
-      "meskobalazs",
-      "iamdue",
-      "copas2",
-      "dorionka"
-    ]
-  },
-  "Web/JavaScript/Reference/Global_Objects/NaN": {
-    "modified": "2020-11-19T09:58:46.355Z",
-    "contributors": [
-      "Sealdolphin"
-    ]
-  },
-  "Web/JavaScript/Reference/Global_Objects/String": {
-    "modified": "2020-10-15T22:17:15.870Z",
-    "contributors": [
-      "Zoldszemesostoros",
-      "SphinxKnight",
-      "pfeihun",
-      "N3U2O"
-    ]
-  },
-  "Web/JavaScript/Reference/Statements": {
-    "modified": "2020-03-12T19:41:42.255Z",
-    "contributors": [
-      "fscholz"
-    ]
-  },
-  "Web/JavaScript/Reference/Statements/try...catch": {
-    "modified": "2020-10-15T22:00:49.343Z",
-    "contributors": [
-      "Zoldszemesostoros",
-      "suckee86"
-    ]
-  },
-  "Web/JavaScript/a_javascript_ujboli_bemutatasa": {
-    "modified": "2020-03-12T19:48:54.218Z",
-    "contributors": [
-      "kisjoke91"
-    ]
-  },
-  "Web/Reference": {
-    "modified": "2019-03-23T22:43:43.697Z",
-    "contributors": [
-      "MR-AMIR"
-    ]
-  },
-  "Web/Reference/API": {
-    "modified": "2019-03-23T22:43:40.626Z",
-    "contributors": [
-      "barcai"
-    ]
-  },
-  "WebSockets": {
-    "modified": "2019-03-23T22:56:13.956Z",
-    "contributors": [
-      "EvanDotPro"
-    ]
-  }
-}
\ No newline at end of file
diff --git a/files/hu/archive/b2g_os/biztonság/index.html b/files/hu/archive/b2g_os/biztonság/index.html
deleted file mode 100644
index e7ace850ae..0000000000
--- a/files/hu/archive/b2g_os/biztonság/index.html
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: Firefox OS security
-slug: Archive/B2G_OS/Biztonság
-translation_of: Archive/B2G_OS/Security
----
-<p>The following articles cover security-related topics about Firefox OS. This includes overall security features as well as application security and how the install process is kept secure.</p>
-<table class="topicpage-table">
-  <tbody>
-    <tr>
-      <td>
-        <h2 class="Documentation" id="Documentation" name="Documentation">Firefox OS security documentation</h2>
-        <dl>
-          <dt>
-            <a href="/en-US/docs/Mozilla/Firefox_OS/Security/Security_model" title="/en-US/docs/Mozilla/Firefox_OS/Security/Security_model">The Firefox OS security model</a></dt>
-          <dd>
-            An overview of the Firefox OS security model.</dd>
-          <dt>
-            <a href="/en-US/docs/Mozilla/Firefox_OS/Security/System_security" title="/en-US/docs/Mozilla/Firefox_OS/Security/Security_model">System security</a></dt>
-          <dd>
-            Details of security controls built-in to the FirefoxOS runtime.</dd>
-          <dt>
-            <a href="/en-US/docs/Mozilla/Firefox_OS/Security/Application_security" title="/en-US/docs/Mozilla/Firefox_OS/Security/Application_security">Application security in Firefox OS</a></dt>
-          <dd>
-            An overview of how applications are made secure on Firefox OS.</dd>
-          <dt>
-            <a href="/en-US/docs/Mozilla/Firefox_OS/Security/Installing_and_updating_applications" title="/en-US/docs/Mozilla/Firefox_OS/Security/Installing_and_updating_applications">Securely installing and updating applications</a></dt>
-          <dd>
-            How Firefox OS securely installs and updates applications.</dd>
-          <dt>
-            <a href="/en-US/docs/Mozilla/Firefox_OS/Security/Software_permissions" title="/en-US/docs/Mozilla/Firefox_OS/Security/Software_permissions">Software permissions in Firefox OS</a></dt>
-          <dd>
-            A guide to what types of software have permission to perform various tasks on Firefox OS.</dd>
-          <dt>
-            <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Security/Debugging_and_security_testing" title="/en-US/docs/Mozilla/Firefox_OS/Security/Debugging_and_security_testing#Marionette.3A_A_JavaScript_debugging_shell_for_Firefox_OS"><span style="display: none;"> </span>Debugging and security testing with Firefox OS</a></dt>
-          <dd>
-            This guide shows you the basic security testing steps, from opening a remote JavaScript debugger to setting up an intercepting HTTP(S) proxy against a desktop version of Firefox OS</dd>
-        </dl>
-        <p><span class="alllinks"><a href="/en-US/docs/tag/B2G" title="/en-US/docs/tag/B2G">View All...</a></span></p>
-      </td>
-      <td>
-        <h2 class="Community" id="Community" name="Community">Getting help from the community</h2>
-        <p>If you're working with Firefox OS, or developing applications you'd like to run on Firefox OS devices, there are community resources to help you!</p>
-        <ul>
-          <li>Consult the Boot to Gecko project forum: {{ DiscussionList("dev-b2g", "mozilla.dev.b2g") }}</li>
-        </ul>
-        <ul>
-          <li>Ask your question on Mozilla's Boot to Gecko IRC channel: <a class="link-irc" href="irc://irc.mozilla.org/b2g" title="irc://irc.mozilla.org/b2g">#b2g</a></li>
-        </ul>
-        <p><span class="alllinks"><a class="external" href="http://www.catb.org/~esr/faqs/smart-questions.html" title="http://www.catb.org/~esr/faqs/smart-questions.html">Don't forget about the <em>netiquette</em>...</a></span></p>
-        <br>
-        <h2 class="Related_Topics" id="Related_Topics" name="Related_Topics">Related topics</h2>
-        <ul>
-          <li><a href="/en-US/docs/Mobile" title="en-US/docs/Mobile">Mobile</a></li>
-          <li><a href="/en-US/docs/Security" title="/en-US/docs/Security">Security</a></li>
-        </ul>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<p> </p>
-<div id="cke_pastebin" style="position: absolute; top: 483px; width: 1px; height: 1px; overflow: hidden; left: -1000px;">
-  <br>
-  Firefox OS</div>
diff --git a/files/hu/archive/b2g_os/firefox_os_telepítése/index.html b/files/hu/archive/b2g_os/firefox_os_telepítése/index.html
deleted file mode 100644
index 49ffd2f528..0000000000
--- a/files/hu/archive/b2g_os/firefox_os_telepítése/index.html
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: A Firefox OS telepítése és
-slug: Archive/B2G_OS/Firefox_OS_telepítése
-translation_of: Archive/B2G_OS/Building_and_installing_B2G_OS
----
-<div class="summary">
- <p>Mivel a Firefox OS aktív fejlesztés alatt áll, az új verzió megjelenése előtt a legjobb módja a telepítésének egy olyan verzió, ami a jövőben frissíti magát az újabb változatra. Ez a cikk lépésről-lépésre leírja a Firefox OS (emulátorba, illetve kompatibilis eszközre) vagy a Gaia felhasználói felület (Firefox böngészőben) telepítését.</p>
-</div>
-<table class="topicpage-table">
- <tbody>
-  <tr>
-   <td>
-    <h2 class="Documentation" id="A_Firefox_OS_letöltése_és_konfigurálása">A Firefox OS letöltése és konfigurálása</h2>
-    <dl>
-     <dt>
-      <a href="/en-US/Firefox_OS/Building_and_installing_Firefox_OS/Firefox_OS_build_overview">Firefox OS konfigurációs áttekintés</a></dt>
-     <dd>
-      A Firefox OS telepítése és konfigurálása sok időt igényel, az internet sebességének és a számítási teljesítménynek függvényében. Ez az oldal körvonalazza a konfiguráció lépéseit és céljait, hogy segítse a felhasználókat a folyamat során.</dd>
-     <dt>
-      <a href="/en-US/docs/Mozilla/Firefox_OS/Firefox_OS_build_prerequisites" title="Mozilla/Firefox_OS/Firefox OS build prerequisites">Firefox OS konfigurálási előfeltételek</a></dt>
-     <dd>
-      Lépések mielőtt először konfigurálná a Firefox OS-t.</dd>
-     <dt>
-      <a href="/en-US/docs/Mozilla/Firefox_OS/Preparing_for_your_first_B2G_build" title="Mozilla/Firefox_OS/Preparing for your first B2G build">Felkészülés az első Firefox OS konfigurálására</a></dt>
-     <dd>
-      Mielőtt konfigurálja a Firefox OS-t, klónoznia kell a tárolót, és konfigurálni az ön telepítését. Ez a cikk elmagyarázza, hogyan kell csinálni.</dd>
-     <dt>
-      <a href="/en-US/docs/Mozilla/Firefox_OS/Building" title="Mozilla/Firefox_OS/Building">Firefox OS konfigurálása</a></dt>
-     <dd>
-      Hogyan konfiguráljuk a Firefox OS-t.</dd>
-     <dt>
-      <a href="/en-US/docs/Mozilla/Firefox_OS/Porting" title="/en-US/docs/Mozilla/Firefox_OS/Porting">Firefox OS áthelyezése</a></dt>
-     <dd>
-      Információk arról, hogyan helyezzük át a Firefox OS-t új eszközre.</dd>
-    </dl>
-    <p><span class="alllinks"><a href="/en-US/docs/tag/B2G" title="tag/B2G">View All...</a></span></p>
-   </td>
-   <td>
-    <h2 class="Community" id="A_Firefox_OS_ésvagy_Gaia_telepítése">A Firefox OS  és/vagy Gaia telepítése</h2>
-    <dl>
-     <dt>
-      <a href="/en-US/docs/Mozilla/Firefox_OS/Choosing_how_to_run_Gaia_or_B2G" title="Mozilla/Firefox_OS/Choosing how to run Gaia or B2G">A Firefox OS vagy Gaia futtatási módjának kiválasztása</a></dt>
-     <dd>
-      Használhatja a Gaia-t Firefox-ban, vagy a Firefox OS-t egy mobileszközön illetve PC-alapú szimulátorban. Ez az útmutató segít eldönteni, hogy melyik felel meg a legjobban az Ön igényeinek.</dd>
-     <dt>
-      <strong><a href="/en-US/docs/Mozilla/Firefox_OS/Using_Gaia_in_Firefox" title="Mozilla/Firefox_OS/Using Gaia in Firefox">A Gaia használata Firefox-ban</a></strong></dt>
-     <dd>
-      Gaia használatának módja egy asztali Firefox böngészőben.</dd>
-     <dt>
-      <a href="/en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_desktop_client" title="Mozilla/Firefox_OS/Using the B2G desktop client">A Firefox OS asztali kliens használata</a></dt>
-     <dd>
-      Útmutató Firefox OS asztali kliens futtatásához és használatához; ez szimulálja a Gaia környezetet egy asztali alkalmazáson keresztül. Ez pontosabb, mint a Gaia futtatása a Firefoxban, de nem olyan pontos, mint az emulátor.</dd>
-     <dt>
-      <a href="/en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_emulators" title="Mozilla/Firefox_OS/Using the B2G emulators">Firefox OS emulátorok használata</a></dt>
-     <dd>
-      Egy útmutatás a Firefox OS emulátorok konfigurálásához és használatához, és hogy mikor melyik emulátort kell használni.</dd>
-     <dt>
-      <a href="/en-US/docs/Mozilla/Firefox_OS/Installing_on_a_mobile_device" title="Mozilla/Firefox_OS/Installing on a mobile device">Firefox OS telepítése mobileszközre</a></dt>
-     <dd>
-      Hogyan telepítsük a Firefox OS-t  egy valódi mobileszközre.</dd>
-     <dt>
-      <a href="/en-US/docs/Mozilla/Firefox_OS/Dual_boot_of_B2G_and_Android_on_SGS2" title="Mozilla/Firefox_OS/Dual boot of B2G and Android on SGS2">Firefox OS és Android használata egyszerre (egy SamsungGalaxyS2-n)</a></dt>
-     <dd>
-      Hogyan használjuk a Firefox OS-t és az Androidot egyszerre (egy Samsung Galaxy S2-n)</dd>
-    </dl>
-   </td>
-  </tr>
- </tbody>
-</table>
-<p> </p>
diff --git a/files/hu/archive/b2g_os/index.html b/files/hu/archive/b2g_os/index.html
deleted file mode 100644
index ff622156a2..0000000000
--- a/files/hu/archive/b2g_os/index.html
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: B2G OS
-slug: Archive/B2G_OS
-translation_of: Archive/B2G_OS
----
-<p><strong>Firefox OS</strong> (rövidítve <strong>FxOS</strong>) egy új mobil operációs rendszer amit a Mozilla fejleszt. A Linux kernelen alapuló rendszer egy Gecko alapú futtató környezetet töltbe be, ami lehetővé teszi olyan alkalmazások futtatását amik teljes egészében <a href="/hu/docs/HTML" title="hu/docs/HTML">HTML</a>, <a href="/hu/docs/JavaScript" title="hu/docs/JavaScript">JavaScript</a>, és egyéb webes alkalmazás API-k segítségével íródtak.</p>
-
-<p>A Firefox OS jelenleg számos fejlesztés alatt áll; Folyamatosan azon dolgozunk hogy ön számára könnyebbé váljon a Gaia (alapértelmezett app csomag) használata, és elkészíthesse saját applikációit. Ehhez azonban sok ismeretre van szüksége a Firefox OS működéséről. Alább találhat hasznos leírásokat a Firefox OS-ra való fejlesztésről, tesztelésről, testreszabásról.</p>
-
-<table class="topicpage-table">
- <tbody>
-  <tr>
-   <td>
-    <h2 class="Documentation" id="Documentation" name="Documentation">A Firefox OS platform</h2>
-
-    <dl>
-     <dt><a href="/en-US/docs/Mozilla/Firefox_OS/Introduction" title="en-US/docs/Mozilla/Firefox_OS/Introduction">Bevezetés a Firefox OS-be</a></dt>
-     <dd>Bevezető információk a Firefox OS mivoltáról és működéséről.</dd>
-     <dt><a href="/en-US/docs/Mozilla/Firefox_OS/Firefox_OS_usage_tips" title="/en-US/docs/Mozilla/Firefox_OS/Firefox_OS_usage_tips">Hasznos tippek</a></dt>
-     <dd>Rövid tippek melyek megkönnyítik a Firefox OS használatát és fejlesztését.</dd>
-     <dt><a href="/en-US/docs/Mozilla/Firefox_OS/Platform" title="/en-US/docs/Mozilla/Firefox_OS/Platform">Firefox OS platform kézikönyv</a></dt>
-     <dd>Teljes dokumentáció a Firefox OS platformról, magába foglalva a Gonk, Gaia, és egyébcsomagok használatát.</dd>
-     <dt><a href="/en-US/docs/Mozilla/Firefox_OS/Building_and_installing_Firefox_OS" title="/en-US/docs/Mozilla/Firefox_OS/Building_and_installing_Firefox_OS">Build and install Firefox OS</a></dt>
-     <dd>This includes documentation for building and installing the platform onto devices, as well as building the simulator and emulators.</dd>
-     <dt><a href="/en-US/docs/Mozilla/Firefox_OS/Hacking_Firefox_OS" title="/en-US/docs/Mozilla/Firefox_OS/Hacking_Firefox_OS">Hacking Firefox OS</a></dt>
-     <dd>Once you're used to the basic Firefox OS process, it's time to start hacking the OS, customizing your builds, getting things the way you think they should be! This section shows you how to get ahead.</dd>
-     <dt><a href="/en-US/docs/Mozilla/Firefox_OS/Troubleshooting" title="/en-US/docs/Mozilla/Firefox_OS/Troubleshooting">Troubleshooting</a></dt>
-     <dd>A guide to resolving common problems with Firefox OS.</dd>
-     <dt><a href="/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide" title="/en-US/docs/Mozilla/Firefox_OS/Boot to Gecko developer phone guide">Firefox OS developer phone guide</a></dt>
-     <dd>A guide to the Firefox OS developer phones Mozilla provides to some developers. This guide also applies if someone installed Firefox OS on your phone for you.</dd>
-    </dl>
-
-    <h2 class="Documentation" id="Documentation" name="Documentation">Firefox OS Alkalmazás Tervezés és fejlesztés</h2>
-
-    <p>For up-to-date information on Firefox OS App design and development, you should consult our <a href="/en-US/docs/Web/Apps" title="/en-US/docs/Web/Apps">Open Web Apps documentation center</a>. Some other resources are listed below, but probably won't be for long, as they will be integrated into the main apps docs.</p>
-
-    <dl>
-     <dt><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Apps/Tips_and_techniques">Tips and techniques</a></dt>
-     <dd>An assortment of tips and tricks (as well as workarounds for problems) that our developers have suggested for you!</dd>
-     <dt><a href="https://marketplace.firefox.com/developers/" title="https://marketplace.firefox.com/developers/">Developer Hub</a></dt>
-     <dd>A collection of tools, tutorials, and services for Firefox OS app developers.</dd>
-    </dl>
-
-    <dl>
-     <dt><a href="/en-US/docs/Mozilla/Firefox_OS/Debugging" title="en-US/docs/Mozilla/Firefox_OS/Debugging">Debugging on Firefox OS</a></dt>
-     <dd>A guide to debugging both your mobile apps and Firefox OS itself.</dd>
-     <dt><a href="/en-US/docs/Mozilla/Firefox_OS/Performance" title="/en-US/docs/Mozilla/Firefox_OS/Performance">Performance</a></dt>
-     <dd>Articles about optimizing Firefox OS applications.</dd>
-    </dl>
-
-    <p><span class="alllinks"><a href="/en-US/docs/tag/B2G" title="/en-US/docs/tag/B2G">View All...</a></span></p>
-   </td>
-   <td>
-    <h2 class="Community" id="Community" name="Community">Segítség kérése a közösségtől</h2>
-
-    <p>If you're working with Firefox OS, or developing applications you'd like to run on Firefox OS devices, there are community resources to help you!</p>
-
-    <ul>
-     <li>Ask your question on Mozilla's Boot to Gecko IRC channel: <a class="link-irc" href="irc://irc.mozilla.org/b2g" title="irc://irc.mozilla.org/b2g">#b2g</a></li>
-    </ul>
-
-    <p><span class="alllinks"><a class="external" href="http://www.catb.org/~esr/faqs/smart-questions.html" title="http://www.catb.org/~esr/faqs/smart-questions.html">Don't forget about the <em>netiquette</em>...</a></span></p>
-
-
-    <h2 class="Related_Topics" id="Related_Topics" name="Related_Topics">Kapcsolódó TÉmák</h2>
-
-    <ul>
-     <li><a href="/en-US/docs/Mobile" title="en-US/docs/Mobile">Mobile</a></li>
-     <li><a href="/en-US/docs/HTML" title="en-US/docs/HTML">HTML</a></li>
-     <li><a href="/en-US/docs/CSS" title="en-US/docs/CSS">CSS</a></li>
-     <li><a href="/en-US/docs/JavaScript" title="en-US/docs/JavaScript">JavaScript</a></li>
-    </ul>
-
-    <h2 class="Tools" id="Források">Források</h2>
-
-    <ul>
-     <li><a class="link-https" href="https://wiki.mozilla.org/B2G/FAQ" title="B2G/FAQ">Mozilla wiki FAQ</a></li>
-     <li><a class="link-https" href="https://wiki.mozilla.org/B2G/Schedule_Roadmap" title="https://wiki.mozilla.org/B2G/Schedule_Roadmap">Roadmap</a></li>
-     <li><a href="/en-US/docs/Mozilla/Firefox_OS/Feature_support_chart" title="/en-US/docs/Mozilla/Firefox_OS/Feature_support_chart">Feature support chart</a></li>
-     <li><a href="/en-US/docs/Mozilla/Firefox_OS/Geeksphone_FAQ" title="/en-US/docs/Mozilla/Firefox_OS/Geeksphone_FAQ">Geeksphone FAQ</a></li>
-    </ul>
-   </td>
-  </tr>
- </tbody>
-</table>
diff --git a/files/hu/archive/b2g_os/quickstart/az_elsö_appod/index.html b/files/hu/archive/b2g_os/quickstart/az_elsö_appod/index.html
deleted file mode 100644
index 92b5c36e72..0000000000
--- a/files/hu/archive/b2g_os/quickstart/az_elsö_appod/index.html
+++ /dev/null
@@ -1,261 +0,0 @@
----
-title: Az első appod
-slug: Archive/B2G_OS/Quickstart/Az_elsö_appod
-translation_of: Archive/B2G_OS/Quickstart/Your_first_app
----
-<article class="brush: js">
-<div class="summary">
-<p>A nyílt webes alkalmazások pontosan azt nyújtják a fejlesztőknek, amire évek óta vágynak: különböző kezelőfelületek egységes környezetét, amit kizárólag HTML, CSS és JavaScript alkalmazásoknak szántak — mindezt az első, nyílt webes felülettel, a Firefox OS-szel. Ez az útmutató egy gyors, alapszintű programozási és alkalmazásépítői instrukciót tartalmaz, hogy létrehozhasd a következő nagyszerű appot.</p>
-</div>
-
-<p>Ha szeretnél minket és ezt az útmutatót követni, letöltheted a <a href="https://github.com/chrisdavidmills/mdn-app-template">gyors applikációkezdő mintánkat</a>. Tudj meg többet ennek tartalmáról, és olvasd el az <a href="/en-US/docs/Project:MDN/Style_guide/Sample_app_coding_guidelines#Apps_template">Alkalmazásminták</a> útmutatót (a programozói felületek és programnyelvek angol nyelvtudást igényelnek)</p>
-
-<h2 id="Az_alkalmazás_felépítése">Az alkalmazás felépítése</h2>
-
-<h3 id="Csomagolt_vs._Hostolt_alkalmazások">Csomagolt vs. Hostolt alkalmazások</h3>
-
-<p>A nyílt webes alkalmazásoknak két formájuk van: <code>csomagolt</code> and <code>hostolt</code>. A csomagolt appok alapvetően <code>zip</code> file-ok, melyek minden alkalmazáskiegészítőt tartalmaznak: HTML, CSS, JavaScript, képek, tanúsítványok, stb. A hostolt alkalmazások szerverről futnak, egy megadott domainen, akárcsak egy weboldal. Mindkét alkalmazástípus érvényes tanúsítványt igényel. Mikor eljön a pillanat, hogy feltöltsd az alkalmazásodat a Firefox Piactérre, akkor vagy ezt a zip file-t töltöd fel, vagy a hostolt applikációhoz mutató linket fogod megadni</p>
-
-<div style="width: 480px; margin: 0 auto;">
-<p>{{EmbedYouTube("Q7x-B13y33Q")}}</p>
-
-<div class="video-caption">
-<p>Készült a Treehouse társulás jóvoltából: <a class="button" href="http://teamtreehouse.com/?cid=1154">Lesd meg őket!</a></p>
-</div>
-</div>
-
-<p>Ezen útmutatón keresztül el fogod készíteni a hostolt alkalmazásodat, amely a te <code>localhost</code> címeden lesz elérhető. Amint az appod készen áll arra, hogy megoszthasd a Firefox Piactéren, eldöntheted, hogy csomagolva, vagy hostolva osztod meg.</p>
-
-<h3 id="App_Tanúsítványok">App Tanúsítványok</h3>
-
-<p>Minden Firefox appnak szüksége van egy manifest.webapp file-ra az alkalmazáson belül. A <a href="/en-US/docs/Web/Apps/Manifest"><code>manifest.webapp</code></a> file biztosítja a létszükségletű információkat az appról, úgy, mint verzó, név, leírás, ikon, hely, helyszíni láncolatok, domain, ahonnan az app telepíthető, és még sokminden. Csak a név és verziószám kötelező. A legegyszerűbb tanúsítvány (az alkalmazásmintán belül) a következőképpen néz ki:</p>
-
-<pre class="brush: js">{
-  "version": "0.1",
-  "name": "Open Web App",
-  "description": "Your new awesome Open Web App",
-  "launch_path": "/app-template/index.html",
-  "icons": {
-    "16": "/app-template/app-icons/icon-16.png",
-    "48": "/app-template/app-icons/icon-48.png",
-    "128": "/app-template/app-icons/icon-128.png"
-  },
-  "developer": {
-    "name": "Your Name",
-    "url": "http://yourawesomeapp.com"
-  },
-  "locales": {
-    "es": {
-      "description": "Su nueva aplicación impresionante Open Web",
-      "developer": {
-        "url": "http://yourawesomeapp.com"
-      }
-    },
-    "it": {
-      "description": "La tua nuova fantastica Open Web App",
-      "developer": {
-        "url": "http://yourawesomeapp.com"
-      }
-    }
-  },
-  "default_locale": "en"
-}</pre>
-
-<div style="width: 480px; margin: 0 auto;">
-<p>{{EmbedYouTube("dgAUgHQOm8M")}}</p>
-
-<div class="video-caption">
-<p>Készült a Treehouse társulás jóvoltából: <a class="button" href="http://teamtreehouse.com/?cid=1154">lESD MEG ŐKET!</a></p>
-</div>
-</div>
-
-<p> </p>
-
-<p>A kezdéshez egy alap tanúsítványra van szükséged. További részletekért olvasd el az  <a href="/en-US/docs/Web/Apps/Manifest">Alkalmazástanúsítványt</a>.</p>
-
-<h2 id="App_Tervezés_Design">App Tervezés &amp; Design</h2>
-
-<p>Az appok kinézete kiemelkedően fontossá vált, ahogy a képernyők felbontása egyre jobb színvonalat ért el. Noha az appok fő célterülete a telefonplatformokban van, mint például a Firefox OS, egyéb eszközöknek is lehet hozzáférésük. A <a href="//developer.mozilla.org/docs/CSS/Media_queries">CSS médium lista</a> lehetővé teszi, hogy különböző eszközök megjelenítéséhez igazodj, ahogy azt alábbi CSS példaváz mutatja:</p>
-
-<pre class="brush: css">/* The following are examples of different CSS media queries */
-
-/* Basic desktop/screen width sniff */
-@media only screen and (min-width : 1224px) {
-  /* styles */
-}
-
-/* Traditional iPhone width */
-@media
-  only screen and (-webkit-min-device-pixel-ratio : 1.5),
-  only screen and (min-device-pixel-ratio : 1.5) {
-  /* styles */
-}
-
-/* Device settings at different orientations */
-@media screen and (orientation:portrait) {
-  /* styles */
-}
-@media screen and (orientation:landscape) {
-  /* styles */
-}</pre>
-
-<p>Számos JavaScript és CSS keretrendszer elérhető, hogy segítsen a tervezésben és mobil app fejlesztésben (<a href="http://twitter.github.com/bootstrap">Bootstrap</a>, stb.) Válaszd azt, amelyik a legjobban illik a stílusodhoz.</p>
-
-<h2 id="Web_API-k">Web API-k</h2>
-
-<p>A JavaScript API-k (alkalmazásprogramozási felületek) legalább olyan gyorsan fejlődnek, mint maguk a készülékek. A Mozilla <a href="https://wiki.mozilla.org/WebAPI">WebAPI</a> kezdeményezés temérdek szabvány mobilvázlatot integrál a JavaScript API-kba. A támogatott eszközök listája elérhető a <a href="https://wiki.mozilla.org/WebAPI">WebAPI</a> oldalon. A legjobb gyakorlást a JavaScript eszközérzékelő biztosítja, ahogy azt itt mutatjuk:</p>
-
-<pre class="brush: js">// If this device supports the vibrate API...
-if('vibrate' in navigator) {
-    // ... vibrate for a second
-    navigator.vibrate(1000);
-}</pre>
-
-<p>A következő példában a <code>&lt;div&gt; </code>megjelenítését módosítottuk a készülék töltöttségének függvényében:</p>
-
-<pre class="brush: java">// Create the battery indicator listeners
-(function() {
-  var battery = navigator.battery || navigator.mozBattery || navigator.webkitBattery,
-      indicator, indicatorPercentage;
-
-  if(battery) {
-    indicator = document.getElementById('indicator'),
-    indicatorPercentage = document.getElementById('indicator-percentage');
-
-    // Set listeners for changes
-    battery.addEventListener('chargingchange', updateBattery);
-    battery.addEventListener('levelchange', updateBattery);
-
-    // Update immediately
-    updateBattery();
-  }
-
-  function updateBattery() {
-    // Update percentage width and text
-    var level = (battery.level * 100) + '%';
-    indicatorPercentage.style.width = level;
-    indicatorPercentage.innerHTML = 'Battery: ' + level;
-    // Update charging status
-    indicator.className = battery.charging ? 'charging' : '';
-  }
-})();</pre>
-
-<p>A fenti kódmintában, amint megerősíted a <a href="https://developer.mozilla.org/en-US/docs/DOM/window.navigator.battery">Battery API</a> támogatottságot, további eseményfigyelőket adhatsz a <code>chargingchange</code> és a <code>levelchange</code> kódhoz, hogy frissíthesd az elemek megjelenítése. Próbáld meg hozzáadni a mintádhoz, és nézd meg magad a működését.</p>
-
-<p>Rendszeresen ellenőrizd a <a href="https://wiki.mozilla.org/WebAPI">WebAPI</a> oldalt, hogy naprakész legyél az API készülékstátuszokkal.</p>
-
-<h3 id="API_funkcionálisság_telepítése">API funkcionálisság telepítése</h3>
-
-<p>Az app kezdőmintánkban elhelyeztünk egy telepítőkapcsolót, amivel megtekintheted az appodat, mint egy mintaweboldalt, mintha az egy telepített alkalmazás lenne a Firefox OS-en. A gomb megjelenésében nincs semmi különös:</p>
-
-<pre class="brush: html">&lt;button id="install-btn"&gt;Install app&lt;/button&gt;</pre>
-
-<p>A kapcsoló az API telepítő használatával is működtethető (lásd install.js):</p>
-
-<pre class="brush: js">var manifest_url = location.href + 'manifest.webapp';
-
-function install(ev) {
-  ev.preventDefault();
-  // define the manifest URL
-  // install the app
-  var installLocFind = navigator.mozApps.install(manifest_url);
-  installLocFind.onsuccess = function(data) {
-    // App is installed, do something
-  };
-  installLocFind.onerror = function() {
-    // App wasn't installed, info is in
-    // installapp.error.name
-    alert(installLocFind.error.name);
-  };
-};
-
-// get a reference to the button and call install() on click if the app isn't already installed. If it is, hide the button.
-var button = document.getElementById('install-btn');
-
-var installCheck = navigator.mozApps.checkInstalled(manifest_url);
-
-installCheck.onsuccess = function() {
-  if(installCheck.result) {
-    button.style.display = "none";
-  } else {
-    button.addEventListener('click', install, false);
-  };
-};
-</pre>
-
-<p>Összegezzük, mi is történik:</p>
-
-<ol>
- <li>Kapunk egy hivatkozást a telepítőkapcsolóra, amit a  <code>button </code>változó alatt tárolunk.</li>
- <li>Eztuán a <code>navigator.mozApps.checkInstalled</code> kódot használjuk, hogy ellenőrizzük a tanúsítványban foglalt app (helyileg: <code>http://people.mozilla.com/~cmills/location-finder/manifest.webapp)</code> telepítve van-e az eszközön. Ezt a teszt az <code>installCheck</code> változóban tárolódik.</li>
- <li>Miután a teszt sikeresen lefut, létrehoz egy sikeres eseményt, ezáltal az <code>installCheck.onsuccess = function() { ... }</code> fut tovább.</li>
- <li>Eztuán tesztet futtatunk az <code>installCheck.result</code> létezésére egy egyszerű <code>if</code> állítás használatával. Ha létezik, ezzel alátámasztva, hogy az app telepítve van, elrejtjük a kapcsolót, mivel ezután erre már nincs szükség.</li>
- <li>Ha az app nincs telepítve, egy kattintásfigyelőt adunk a kapcsolóhoz, így az <code>install()</code> funkció fut, amikor arra kattintunk.</li>
- <li>Mikor a gombra kattintunk, és az <code>install()</code> funkció fut, eltároljuk a tanúsítvány fájlt egy <code>manifest_url </code>változóban tároljuk, ezután telepítjük az appot a <code>navigator.mozApps.install(manifest_url) </code>használatával, eltárolva ezzel egy hivatkozást az <code>installLocFind</code> változóban. Észrevehetjük, hogy ez a telepítés sikeres és sikertelen eseményeket is létrehoz, így annak függvényében tudsz parancsokat futtatni, hogy a telepítés sikerült-e, vagy sem.</li>
-</ol>
-
-<p>Feltehetőleg igazolni szeretnéd a <a href="/en-US/docs/Web/Apps/JavaScript_API">API teljesítési állapot</a>-ot, mikor először jutsz a telepíthető webalkalmazásokhoz.</p>
-
-<div class="note">
-<p>Megjegyzés: a telepíthető webalkalmazásokra az "egy app/egy eredet" szabály vonatkozik. Magyarul egy hostolt alkalmazás csak egy helyről származtatható. Ez a tesztelést kissé bonyolítja, de ez megkerülhető, például különbözü sub-domaineken keresztül, Firefox OS szimulátorral, vagy a telepítő működésének Firefox Aurora/Nightly-n keresztüli tesztelésével, amiken keresztül a webalkalmazásokat az asztalodra telepítheted. Olvasd el az <a href="/en-US/docs/Web/Apps/FAQs/About_app_manifests">app tanúsítványok GYIK-et</a> további információért.</p>
-</div>
-
-<h2 id="WebRT_API-k_(Engedély-alapú_API-k)">WebRT API-k (Engedély-alapú API-k)</h2>
-
-<p>Sok  WebAPI létezik, amelyek ugyan elérhetők, de külön engedély kell egy-egy speciális tartalom eléréséhez. Az appok az engedélykérelmet a <code>manifest.webapp</code> file-ba regisztrálják, a következőképpen:</p>
-
-<pre class="brush: js">// New key in the manifest: "permissions"
-// Request access to any number of APIs
-// Here we request permissions to the systemXHR API
-"permissions": {
-    "systemXHR": {}
-}</pre>
-
-<p>Az engedély három szintje a következők:</p>
-
-<ul>
- <li>Normál — API-k, melyek nem ígényelnek különleges elérési engedélyt.</li>
- <li>Privilegizált — Ezek elérhetők a fejlesztőknek, hogy használják a saját appjukban, amíg feltüntetik az elérési hozzájárulást a tanúsítványban, és megbízható forráson keresztül terjesztik.</li>
- <li>Igazolt — Azok az API-k, amik kritikus eszközfunkciókat használnak, legyen az például tárcsázó, vagy üzenetküldő szolgáltatás. Ezeket általában kívülálló fejlesztők nem használhatják</li>
-</ul>
-
-<p>Az engedélyekről bővebben a <a href="https://developer.mozilla.org/en-US/docs/Web/Apps/Packaged_apps#Types_of_packaged_apps" title="/en-US/docs/Web/Apps/Packaged_apps#Types_of_packaged_apps">Csomagolt apptípusok</a> alatt olvashatsz. Itt többet megtudhatsz az engedélyköteles API-król, és hogy milyen engedélyre van szükséged, nézd meg az <a href="/en-US/docs/Web/Apps/App_permissions">App engedélyek </a>tájékoztatót.</p>
-
-<div class="note">
-<p>Fontos megjegyezni, hogy nem minden web API-t valósítottunk meg a Firefox OS szimulátoron belül.</p>
-</div>
-
-<h2 id="Eszközök_és_tesztelés">Eszközök és tesztelés</h2>
-
-<p>A tesztelés rendkívül fontos, amikor az eszköztámogatásról van szó. Számos opció áll rendelkezésre a telepíthető webalkalmazások tesztelésére.</p>
-
-<h3 id="Firefox_OS_Szimulátor">Firefox OS Szimulátor</h3>
-
-<p>Installing and using the <a href="https://marketplace.firefox.com/developers/docs/firefox_os_simulator">Firefox OS Simulator</a> is the easiest way to get up and running with your app. After you install the simulator, it is accessible from the Tools -&gt; Web Developer -&gt; Firefox OS Simulator menu. The simulator launches with a JavaScript console so you can debug your application from within the simulator.</p>
-
-<h3 id="App_Manager">App Manager</h3>
-
-<p>The new kid on the block with regards to testing tools is called the <a href="/en-US/docs/Mozilla/Firefox_OS/Using_the_App_Manager">App Manager</a>. This tool allows you to connect desktop Firefox to a compatible device via USB (or a Firefox OS simulator), push apps straight to the device, validate apps, and debug them as they run on the device.</p>
-
-<h3 id="Unit_Testing">Unit Testing</h3>
-
-<p>Unit tests are extremely valuable when testing on different devices and builds. jQuery's <a href="http://qunitjs.com">QUnit</a> is a popular client-side testing utility, but you can use any set of testing tools you'd like.</p>
-
-<h3 id="Installing_Firefox_OS_on_a_Device">Installing Firefox OS on a Device</h3>
-
-<p>Since Firefox OS is an open source platform, code and tools are available to build and install Firefox OS on your own device. Build and installation instructions, as well as notes on what devices it can be installed on, can be found on <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Platform">MDN</a>.</p>
-
-<p>Dedicated Firefox OS developer preview devices are also available: read our <a href="https://marketplace.firefox.com/developers/dev_phone">Developer preview phone page</a> for more information.</p>
-
-<h2 id="App_benyújtása_és_terjesztése">App benyújtása és terjesztése</h2>
-
-<p>Once your app is complete, you can host it yourself like a standard web site or app (read <a href="/en-US/docs/Web/Apps/Publishing/Self-publishing_Apps">Self-publishing apps</a> for more information), or it can be <a href="https://marketplace.firefox.com/developers/submit/app/manifest">submitted</a> to the <a href="https://marketplace.firefox.com">Firefox Marketplace</a>. Your app's manifest will be validated and you may choose which devices your app will support (e.g. Firefox OS, Desktop Firefox, Firefox Mobile, Firefox Tablet). Once validated, you can add additional details about your app (screenshots, descriptions, price, etc.) and officially submit the app for listing within the Marketplace. Once approved, your app is available to the world for purchase and installation.</p>
-
-<h3 id="More_Marketplace_Listing_Information">More Marketplace &amp; Listing Information</h3>
-
-<ol>
- <li><a href="/en-US/docs/Web/Apps/Publishing/Submitting_an_app">Submitting an App to the Firefox OS Marketplace </a></li>
- <li><a href="/en-US/docs/Web/Apps/Publishing/Marketplace_review_criteria">Marketplace Review Criteria </a></li>
- <li><a href="http://s.vid.ly/embeded.html?link=8k2n4w&amp;autoplay=false">App Submission Video Walkthrough </a></li>
-</ol>
-</article>
diff --git a/files/hu/archive/b2g_os/quickstart/index.html b/files/hu/archive/b2g_os/quickstart/index.html
deleted file mode 100644
index ebe1f7c220..0000000000
--- a/files/hu/archive/b2g_os/quickstart/index.html
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Build
-slug: Archive/B2G_OS/Quickstart
-tags:
-  - NeedsTranslation
-  - TopicStub
-translation_of: Archive/B2G_OS/Quickstart
----
-<div class="summary">
-  <p>Quickstart information on coding open web apps.</p>
-</div>
-<dl>
-  <dt>
-    <a href="/en-US/docs/Web/Apps/Quickstart/Build/Intro_to_open_web_apps">Introduction to open web apps</a></dt>
-  <dd>
-    What are open web apps? How they differ from regular web pages? Why is this significant? This article aims to answer these questions and more.</dd>
-  <dt>
-    <a href="/en-US/docs/Web/Apps/Quickstart/Build/Your_first_app">Your first app</a></dt>
-  <dd>
-    This article takes you through the basic steps and additional knowledge on top of regular web development required to create installable open web apps.</dd>
-  <dt>
-    <a href="/en-US/docs/Web/Apps/Quickstart/Build/Intro_to_Firefox_OS">Introduction to Firefox OS</a></dt>
-  <dd>
-    An introduction to Firefox OS, Mozilla's new open web app-based mobile platform.</dd>
-  <dt>
-    <a href="/en-US/docs/Web/Apps/Quickstart/Build/Intro_to_manifests">Introduction to manifests</a></dt>
-  <dd>
-    An FAQ designed to answer any questions you may have about manifests, hosting apps, origins, and other such topics.</dd>
-  <dt>
-    <a href="/en-US/docs/Web/Apps/Quickstart/Build/For_Web_developers">App development for web developers</a></dt>
-  <dd>
-    If you're a web developer, how do open web apps differ from what you're used to? This article explains all.</dd>
-  <dt>
-    <a href="/en-US/docs/Web/Apps/Quickstart/Build/For_mobile_developers">App development for mobile developers</a></dt>
-  <dd>
-    If you're a native mobile application developer, what advantages can open web apps bring to you, and how do they differ from what you are used to? Here are some ideas.</dd>
-  <dt>
-    <a href="/en-US/docs/Web/Apps/Quickstart/Build/Developing_app_functionality">Developing app functionality</a></dt>
-  <dd>
-    This page talks about the kinds of different functionality that you might want to build into your apps, with links to further information.</dd>
-  <dt>
-    <a href="/en-US/docs/Web/Apps/Quickstart/Build/Payments">Payments</a></dt>
-  <dd>
-    How do you build functionality to make people pay for installing your open web apps? Here is the lowdown.</dd>
-  <dt>
-    <a href="/en-US/docs/Web/Apps/Quickstart/Build/App_tools">App tools</a></dt>
-  <dd>
-    Last for this section, we provide some links to more information on the tools available to help you develop great open web apps.</dd>
-</dl>
diff --git a/files/hu/archive/b2g_os/releases/2.0/index.html b/files/hu/archive/b2g_os/releases/2.0/index.html
deleted file mode 100644
index 752d0cb316..0000000000
--- a/files/hu/archive/b2g_os/releases/2.0/index.html
+++ /dev/null
@@ -1,112 +0,0 @@
----
-title: Firefox OS 2.0 for developers
-slug: Archive/B2G_OS/Releases/2.0
-translation_of: Archive/B2G_OS/Releases/2.0
----
-<div class="summary">
-<p>This page details the developer features newly implemented in Gecko that are specific to Firefox OS 2.0.</p>
-</div>
-
-<div class="note">
-<p>Firefox OS 2.0's Gecko component is based on Firefox 31/32.</p>
-</div>
-
-<h2 id="New_product_features">New product features</h2>
-
-<p>This section provides a summary of the new features available in Firefox OS 2.0. For more details on specific platform changes (API additions, etc.), see the <a href="#Platform_additions_in_detail">Platform additions in detail</a> section.</p>
-
-<dl>
- <dt>NFC</dt>
- <dd><span class="author-g-x59co88jbi1y2uah b i">This release includes support for device-to-device content sharing support with NFC <span class="author-g-x59co88jbi1y2uah b i">(Near Field Communication)</span>. You can pair your device with another, then <a href="/en-US/docs/Web/API/NFC_API/Using_the_NFC_API#The_P2P_Sharing_UI">swipe to share</a> your contacts, media, or favorite URLs with others.</span></dd>
- <dt>Telephony</dt>
- <dd><span class="author-g-x59co88jbi1y2uah b i">Firefox OS now supports both IPv4 and IPv6 addresses</span> in the network manager.</dd>
- <dt>Find My Device</dt>
- <dd><span class="author-g-9k649z122zgh819oqmty">If you’ve lost your Firefox OS smartphone, Find My Device can help you find it (see the <span class="author-g-9k649z122zgh819oqmty url"><a href="http://find.firefox.com">http://find.firefox.com</a> website</span>). You can see it on a map, make it play a sound and have it display a message. You can also remotely lock it or delete your personal info.</span><span class="author-g-9k649z122zgh819oqmty"> To get started, create a Firefox Account (<em>Settings &gt; Firefox Accounts</em> on your device) and enable Find My Device (<span class="author-g-9k649z122zgh819oqmty"><em>Settings &gt; Find My Device</em></span>).</span></dd>
- <dt>Media</dt>
- <dd><span class="author-g-4iwx7wjdkbf2wjjv b">You can now create your own ringtones using your own music collection, or songs you download from the Web.</span></dd>
- <dt>Camera</dt>
- <dd><span class="author-g-4iwx7wjdkbf2wjjv b">The Camera app now supports various focus modes: Touch, Continuous Auto and Face tracking</span>.</dd>
- <dt>Productivity</dt>
- <dd>We've done a visual refresh of the Email, Calender, and Clock apps.</dd>
- <dt>Homescreen</dt>
- <dd><span class="author-g-4f4wmtjtu8s4fjq7 b i">Firefox OS 2.0 introduces a simpler vertical-scrolling homescreen with larger icons.</span></dd>
- <dt>Edge-gesture app switching</dt>
- <dd><span class="author-g-4f4wmtjtu8s4fjq7 b i">Edge gestures are now available for switching between apps (swipe your thumb from the left edge of the screen to the right and vice versa, to switch between multiple open apps.)</span></dd>
-</dl>
-
-<h2 id="New_partner_features">New partner features</h2>
-
-<dl>
- <dt>E.ME integration</dt>
- <dd>E.ME integration provides direct access to web apps while configurable search providers can search the web at the same time.</dd>
-</dl>
-
-<h2 id="New_DevTools_features">New DevTools features</h2>
-
-<p>The Firefox <a href="/en-US/docs/Tools">Developer Tools</a> have had a large number of features added in Firefox versions 31 and 32; these aren't Firefox OS-specific, but you can take advantage of them when debugging your Firefox OS apps through <a href="/en-US/docs/Tools/WebIDE">WebIDE</a>. To find out more, read:</p>
-
-<ul>
- <li><a href="https://hacks.mozilla.org/2014/05/editable-box-model-multiple-selection-sublime-text-keys-much-more-firefox-developer-tools-episode-31/">Firefox Developer Tools Episode 31</a></li>
- <li><a href="https://hacks.mozilla.org/2014/06/toolbox-inspector-scratchpad-improvements-firefox-developer-tools-episode-32/">Firefox Developer Tools Episode 32</a></li>
-</ul>
-
-<h2 id="Platform_additions_in_detail">Platform additions in detail</h2>
-
-<div class="note">
-<p><strong>Note</strong>: Our list here includes features most important to Firefox OS. For an expanded list of general Gecko feature additions (which are generally also present in Firefox OS 2.0), consult the <a href="/en-US/docs/Mozilla/Firefox/Releases/31" title="/en-US/docs/Mozilla/Firefox/Releases/31">Firefox 31 release notes for developers</a> and <a href="/en-US/docs/Mozilla/Firefox/Releases/32" title="/en-US/docs/Mozilla/Firefox/Releases/32">Firefox 32 release notes for developers</a>.</p>
-</div>
-
-<h3 id="Web_API">Web API</h3>
-
-<ul>
- <li>The parameters of the <a href="/hu/docs/Web/API/MozMobileNetworkInfo" title="The documentation about this has not yet been written; please consider contributing!"><code>MozMobileNetworkInfo</code></a> constructor have been made nullable (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1026727" title="FIXED: Unknown state is displayed instead of Connected during manual network selection">bug 1026727</a>).</li>
- <li>WebRTC: <span class="author-g-41mtsa1hor7b107c i"><a href="/hu/docs/Web/API/MozGetUserMedia" title="The documentation about this has not yet been written; please consider contributing!"><code>mozGetUserMedia</code></a>, <a href="/hu/docs/Web/API/MozRTCPeerConnection" title="The documentation about this has not yet been written; please consider contributing!"><code>mozRTCPeerConnection</code></a>, and <a href="/hu/docs/Web/API/DataChannels" title="The documentation about this has not yet been written; please consider contributing!"><code>DataChannels</code></a> are supported by default</span>.</li>
- <li>New constraints for <a href="https://developer.mozilla.org/en-US/docs/Glossary/WebRTC">WebRTC</a>'s <a class="new" href="https://developer.mozilla.org/en-US/docs/Web/API/NavigatorUserMedia.getUserMedia" title="The documentation about this has not yet been written; please consider contributing!"><code>getUserMedia()</code></a>, <code>width</code>, <code>height</code>, and <code>framerate</code>,  have been added, to limit stream dimensions and frame rate (<a class="external external-icon" href="https://bugzilla.mozilla.org/show_bug.cgi?id=907352" title="FIXED: Implement width/height/framerate gUM constraints">bug 907352</a>):
-  <pre class="brush: json  language-json"><code class="language-json"><span class="token punctuation">{</span>
-  mandatory<span class="token punctuation">:</span> <span class="token punctuation">{</span>
-    width<span class="token punctuation">:</span> <span class="token punctuation">{</span> min<span class="token punctuation">:</span> <span class="token number">640</span> <span class="token punctuation">}</span><span class="token punctuation">,</span>
-    height<span class="token punctuation">:</span> <span class="token punctuation">{</span> min<span class="token punctuation">:</span> <span class="token number">480</span> <span class="token punctuation">}</span>
-  <span class="token punctuation">}</span><span class="token punctuation">,</span>
-  optional<span class="token punctuation">:</span> <span class="token punctuation">[</span>
-    <span class="token punctuation">{</span> width<span class="token punctuation">:</span> <span class="token number">650</span> <span class="token punctuation">}</span><span class="token punctuation">,</span>
-    <span class="token punctuation">{</span> width<span class="token punctuation">:</span> <span class="token punctuation">{</span> min<span class="token punctuation">:</span> <span class="token number">650</span> <span class="token punctuation">}</span><span class="token punctuation">}</span><span class="token punctuation">,</span>
-    <span class="token punctuation">{</span> frameRate<span class="token punctuation">:</span> <span class="token number">60</span> <span class="token punctuation">}</span><span class="token punctuation">,</span>
-    <span class="token punctuation">{</span> width<span class="token punctuation">:</span> <span class="token punctuation">{</span> max<span class="token punctuation">:</span> <span class="token number">800</span> <span class="token punctuation">}</span><span class="token punctuation">}</span><span class="token punctuation">,</span>
-  <span class="token punctuation">]</span>
-<span class="token punctuation">}</span></code></pre>
- </li>
- <li>RTSP streaming support is now available (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=929372" title="FIXED: [RTSP][User Story]Support basic RTSP streaming function.">bug 929372</a>).</li>
- <li>The Resource Statistics API is implemented (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=951976" title="FIXED: API for Resource Statistics">bug 951976</a>).</li>
- <li>The Resource Timing API is implemented (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=822480" title="FIXED: Add in the Resource Timing API">bug 822480</a>).</li>
- <li>fastSeek API is now available for media elements (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=778077" title="FIXED: Implement fastSeek API on media elements (and switch the built-in controls over to it)">bug 778077</a>).</li>
- <li><span class="author-g-41mtsa1hor7b107c i">The <a href="/en-US/docs/Web/API/Network_Information_API">Network Information API</a> is now exposed to Firefox OS (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=960426" title="FIXED: Support Network Information API in Firefox OS">bug 960426</a>).</span></li>
- <li><span class="author-g-41mtsa1hor7b107c i"><span class="author-g-41mtsa1hor7b107c i">The Wifi capabilities of the device can now be returned using <code>WifiManager.getCapabilities()</code> (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1002314" title="FIXED: [B2G]To have a webapi providing WIFI capabilities of device">bug 1002314</a>).</span></span></li>
- <li>The <a href="https://developer.mozilla.org/en-US/docs/Web/API/Navigator.vibrate" title="The Navigator.vibrate() method pulses the vibration hardware on the device, if such hardware exists. If the device doesn't support vibration, this method has no effect. If a vibration pattern is already in progress when this method is called, the previous pattern is halted and the new one begins instead."><code>Navigator.vibrate()</code></a> method behavior has been adapted to the latest specification: too long vibrations are now truncated (<a class="external external-icon" href="https://bugzilla.mozilla.org/show_bug.cgi?id=1014581" title="FIXED: Update Vibration API to conform to latest W3C spec">bug 1014581</a>).</li>
- <li><span class="author-g-41mtsa1hor7b107c i">The <a href="/en-US/docs/Web/API/Device_Storage_API">Device Storage API</a> now has mount and unmount capabilities (privileged) (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=971612" title='FIXED: Implement "mount", "unmount" API for device storage'>bug 971612</a>).</span></li>
- <li><span class="author-g-41mtsa1hor7b107c i"><span class="author-g-41mtsa1hor7b107c i">The Feature Detection API is now available (privileged) (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=983502" title="FIXED: Implement and expose the feature detection API to privileged apps">bug 983502</a>).</span></span></li>
- <li> The <a class="new" href="https://developer.mozilla.org/en-US/docs/Web/API/MSISDN_Verification_API">MSISDN Verification API</a> has been added (privileged) (<a class="external external-icon" href="https://bugzilla.mozilla.org/show_bug.cgi?id=988469" title="FIXED: MSISDN verification API for privileged apps">bug 988469</a>).</li>
- <li>A new CameraControl API is now available (privileged) (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=909542" title="FIXED: Camera Control API clean-up/streamline">bug 909542</a>).</li>
- <li>The <a href="https://developer.mozilla.org/en-US/docs/Web/API/Data_Store_API">Data Store API</a> has been made available to <a href="https://developer.mozilla.org/en-US/docs/Web/Guide/Performance/Using_web_workers">Web Workers</a> (certified) (<a class="external external-icon" href="https://bugzilla.mozilla.org/show_bug.cgi?id=949325" title="FIXED: C++ wrapper to support DataStore API on the worker">bug 949325</a>).</li>
- <li>The <a href="/en-US/docs/Web/API/Device_Storage_API">Device Storage API</a> now uses the File System API spec (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=910412" title="FIXED: Change DeviceStorage API to use FileSystem API spec">bug 910412</a>).</li>
- <li><span class="author-g-41mtsa1hor7b107c i">The deprecated Audio Data API has been removed</span> (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=927245" title="FIXED: Remove deprecated Audio Data API implementation">bug 927245</a>).</li>
-</ul>
-
-<h3 id="CSS">CSS</h3>
-
-<ul>
- <li><code>position:sticky</code> is now supported, and used in Gaia app layout (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=886646" title="FIXED: implement position:sticky">bug 886646</a>).</li>
- <li><a href="https://developer.mozilla.org/en-US/docs/Web/CSS/flex-grow" title="The CSS flex-grow property specifies the flex grow factor of a flex item."><code>flex-grow</code></a> and  <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/flex-shrink" title="The CSS flex-shrink property specifies the flex shrink factor of a flex item."><code>flex-shrink</code></a> can now to transition between zero and non-zero values (<a class="external external-icon" href="https://bugzilla.mozilla.org/show_bug.cgi?id=996945" title="FIXED: Allow flex-grow / flex-shrink to transition between zero and nonzero values">bug 996945</a>).</li>
-</ul>
-
-<h3 id="Technology_support_improvements">Technology support improvements</h3>
-
-<ul>
- <li>Firefox OS 2.0 now supports H.264 video hardware, allowing you to create and playback video encoded using this codec much more efficiently. See <a href="https://developer.mozilla.org/en-US/Firefox_OS/Media_support">Media support on Firefox OS</a> for details.</li>
-</ul>
-
-<h2 id="Older_versions">Older versions</h2>
-
-<p></p><div class="multiColumnList">
-<ul>
-<li><a href="/en-US/docs/Mozilla/Firefox_OS/Releases/1.4">Firefox OS 1.4 for developers</a></li><li><a href="/en-US/docs/Mozilla/Firefox_OS/Releases/1.3">Firefox OS 1.3 for developers</a></li><li><a href="/en-US/docs/Mozilla/Firefox_OS/Releases/1.2">Firefox OS 1.2 for developers</a></li><li><a href="/en-US/docs/Mozilla/Firefox_OS/Releases/1.1">Firefox OS 1.1 for developers</a></li><li><a href="/en-US/docs/Mozilla/Firefox_OS/Releases/1.0.1">Firefox OS 1.0.1 for developers</a></li></ul>
-</div><p></p>
diff --git a/files/hu/archive/b2g_os/releases/index.html b/files/hu/archive/b2g_os/releases/index.html
deleted file mode 100644
index 3edbcd4c75..0000000000
--- a/files/hu/archive/b2g_os/releases/index.html
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Firefox OS developer release notes
-slug: Archive/B2G_OS/Releases
-tags:
-  - Firefox OS
-  - NeedsTranslation
-  - TopicStub
-translation_of: Archive/B2G_OS/Releases
----
-<h2 id="Firefox_OS_release_notes_by_version">Firefox OS release notes by version</h2>
-<p>This section provides articles covering each new release of Gaia and Gecko for Firefox OS, explaining what features were added and bugs eliminated in each update. There is also a linked summary table showing what APIs are supported by each version of Firefox OS.</p>
-<div class="multiColumnList">
- {{ListSubpages("",1,0,1)}}</div>
-<h2 id="Other_supporting_information">Other supporting information</h2>
-<dl>
- <dt>
-  <a href="/en-US/docs/Mozilla/Firefox_OS/API_support_table">Firefox OS API support table</a></dt>
- <dd>
-  Lists the different APIs available, and what versions of Firefox have support for them.</dd>
- <dt>
-  <a href="/en-US/docs/Web/Apps/App_permissions">App permissions</a></dt>
- <dd>
-  Lists hosted, privileged and certified APIs, along with information on the permissions they need to have set in the App Manifest of your installable apps, such as the manifest permission name, app type required, description, access property, and default permission.</dd>
-</dl>
diff --git a/files/hu/archive/b2g_os/simulator/index.html b/files/hu/archive/b2g_os/simulator/index.html
deleted file mode 100644
index 96c17a6033..0000000000
--- a/files/hu/archive/b2g_os/simulator/index.html
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: Firefox OS Simulator
-slug: Archive/B2G_OS/Simulator
-translation_of: Archive/B2G_OS/Simulator
----
-<div class="note">
-<p>This page describes the Firefox OS Simulator for developers targeting Firefox OS 1.2 or later. If you're developing apps for Firefox OS 1.1, then you should check out the documentation for the <a href="/en-US/docs/Tools/Firefox_OS_1.1_Simulator">Firefox OS 1.1 Simulator</a> instead.</p>
-</div>
-
-<p><span style="line-height: 1.5;">The Firefox OS Simulator is <span style="line-height: 1.5;">a version of the higher layers of Firefox OS</span> that simulates a Firefox OS device, but runs on the desktop</span><span style="line-height: 1.5;">. This means that in many cases, you don't need a real device to test and debug your app. </span><span style="line-height: 1.5;">It runs in a window the same size as a Firefox OS device, includes the Firefox OS user interface and built-in apps, and simulates many of the Firefox OS device APIs.</span></p>
-
-<p><span style="line-height: 1.5;">The Simulator is packaged and distributed as a Firefox add-on. Once you've downloaded it and installed it in Firefox, you can run it, push apps to it, and attach the developer tools to it using the <a href="/en-US/Firefox_OS/Using_the_App_Manager">App Manager</a> tool or </span><a href="/docs/Tools/WebIDE"><span style="line-height: 1.5;">WebIDE</span></a><span style="line-height: 1.5;">.</span></p>
-
-<h2 id="Installation"><span style="line-height: 1.5;">Installation</span></h2>
-
-<p><span style="line-height: 1.5;">To install the simulator, use <a href="/docs/Tools/WebIDE#Adding_a_Simulator">WebIDE's Manage Simulators pane</a> (available as part of Firefox 33 and onwards). Multiple versions are available, and you are advised to install them all, for maximum flexibility.</span></p>
-
-<p>To start the Simulator, you choose it from WebIDE's runtime list. For more details, see the <a href="/docs/Tools/WebIDE#Selecting_a_runtime" style="font-size: 14px; font-weight: normal; line-height: 1.5;">instructions in the WebIDE documentation</a>. Once the Simulator's running, you can push apps to it and debug them using the WebIDE, just as you can with a real device.</p>
-
-<p>If you are using the <a href="/Firefox_OS/Using_the_App_Manager">App Manager</a> (an older tool available prior to the WebIDE), you can install a simulator via the following button:</p>
-
-<p><a href="https://ftp.mozilla.org/pub/mozilla.org/labs/fxos-simulator/" style="margin-bottom: 20px; padding: 10px; color: white; text-align: center; border-top-left-radius: 4px; border-top-right-radius: 4px; border-bottom-right-radius: 4px; border-bottom-left-radius: 4px; display: inline-block; background-color: rgb(129, 188, 46); white-space: nowrap; text-shadow: rgba(0, 0, 0, 0.247059) 0px 1px 0px; box-shadow: rgba(0, 0, 0, 0.2) 0px 1px 0px 0px, rgba(0, 0, 0, 0.298039) 0px -1px 0px 0px inset;">Install Simulator</a></p>
-
-<h2 id="The_Simulator_UI" style="line-height: 30px;">The Simulator UI</h2>
-
-<p><span style="line-height: 22.00800132751465px;">The Simulator appears as a separate window, sized so the simulated screen area is 320x480 pixels. </span><span style="line-height: 22.00800132751465px;">To simulate touch events you can click the mouse button and drag while holding the button down. So by clicking and dragging right-to-left from the Home Screen, you'll see the built-in apps, as well as any apps you have added:</span></p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/7173/simulator-1.2.png" style="width: 810px; height: 623px; display: block; margin: 0px auto;"></p>
-
-<p>The Simulator has two buttons in a toolbar at the bottom:</p>
-
-<ul>
- <li>the button on the left takes you to the Home screen, or switches the Simulator off if you hold it down</li>
- <li>the button on the right switches the Simulator between portrait and landscape orientation. This will generate the <a href="https://developer.mozilla.org/en-US/docs/WebAPI/Managing_screen_orientation#Listening_orientation_change" title="/en-US/docs/WebAPI/Detecting_device_orientation">orientationchange</a> event.</li>
-</ul>
-
-<h2 id="Limitations_of_the_Simulator">Limitations of the Simulator</h2>
-
-<p>Note that the Firefox OS Simulator isn't a perfect simulation.</p>
-
-<h3 id="Hardware_limitations">Hardware limitations</h3>
-
-<p>Apart from screen size, the Simulator does not simulate the hardware limitations of a Firefox OS device such as available memory or CPU speed.</p>
-
-<h3 id="Audiovideo_codecs">Audio/video codecs</h3>
-
-<p>The following codecs depend on hardware-accelerated decoding and are therefore not yet supported:</p>
-
-<ul>
- <li>MP3</li>
- <li>AAC</li>
- <li>H.264 (MP4)</li>
- <li>WebM</li>
-</ul>
-
-<p>This means it isn't possible to use the Simulator to test video playback in apps and on websites like Youtube that rely on these codecs.</p>
-
-<h3 id="Unsupported_APIs"><a name="Unsupported-APIs">Unsupported APIs</a></h3>
-
-<p>Certain APIs that work on the device won't work on the Simulator, generally because the supporting hardware is not available on the desktop. We've implemented simulations for some APIs such as geolocation, and expect to add more in future releases. However, at the moment the following APIs are not supported. Using them might throw errors or just return incorrect results:</p>
-
-<ul>
- <li><a href="/en-US/WebAPI/WebTelephony" title="/en-US/WebAPI/WebTelephony">Telephony</a></li>
- <li><a href="/en-US/docs/WebAPI/WebSMS" title="/en-US/docs/WebAPI/WebSMS">WebSMS</a></li>
- <li><a href="/en-US/docs/WebAPI/WebBluetooth" title="/en-US/docs/WebAPI/WebBluetooth">WebBluetooth</a></li>
- <li><a href="/en-US/docs/WebAPI/Using_Light_Events" title="/en-US/docs/WebAPI/Using_Light_Events">Ambient Light</a></li>
- <li><a href="/en-US/docs/WebAPI/Proximity" title="/en-US/docs/WebAPI/Proximity">Proximity</a></li>
- <li><a href="/en-US/docs/WebAPI/Network_Information" title="/en-US/docs/WebAPI/Network_Information">Network Information</a></li>
- <li><a href="/en-US/docs/Online_and_offline_events" title="/en-US/docs/Online_and_offline_events">navigator.onLine and offline events</a></li>
- <li><a href="/en-US/docs/WebAPI/Vibration" title="/en-US/docs/WebAPI/Vibration">Vibration</a></li>
-</ul>
-
-<h2 id="Getting_help"><a name="Simulator-help"></a>Getting help</h2>
-
-<p><span style="line-height: 1.5;">If you have a question, try asking us on the </span><a href="https://lists.mozilla.org/listinfo/dev-developer-tools" style="line-height: 1.5;">dev-developer-tools mailing list</a><span style="line-height: 1.5;"> or on </span><a href="irc://irc.mozilla.org/#devtools" style="line-height: 1.5;">#devtools on irc.mozilla.org</a><span style="line-height: 1.5;">.</span></p>
-
-<h3 id="How_to_enable_verbose_logging"><a name="Simulator-verbose-logging"></a>How to enable verbose logging</h3>
-
-<p>You can see messages logged from your app in the <a href="/en-US/docs/Tools/Web_Console">Web Console</a>, which you can attach to your app using the <a href="/docs/Tools/WebIDE/Troubleshooting">WebIDE</a>. If you want to catch early messages happening during app startup, before the console gets connected and working, you can enable verbose logging in the Simulator.</p>
-
-<p>Visit about:config and <strong>create</strong> a new preference. The preference name is different for each version of the Simulator:</p>
-
-<ul>
- <li>extensions.fxos_1_3_simulator@mozilla.org.sdk.console.logLevel for Firefox OS 1.3</li>
- <li>extensions.fxos_1_2_simulator@mozilla.org.sdk.console.logLevel for Firefox OS 1.2</li>
-</ul>
-
-<p>Set it to the string value "all", and disable, then reenable, the add-on in the Add-on Manager. Now extra messages about the Simulator's operation will appear in the <a href="/en-US/docs/Tools/Browser_Console">Browser Console</a>.</p>
diff --git a/files/hu/archive/b2g_os/teljesítmény/index.html b/files/hu/archive/b2g_os/teljesítmény/index.html
deleted file mode 100644
index 843627ac3c..0000000000
--- a/files/hu/archive/b2g_os/teljesítmény/index.html
+++ /dev/null
@@ -1,146 +0,0 @@
----
-title: Teljesítmény
-slug: Archive/B2G_OS/Teljesítmény
-translation_of: Web/Performance/Fundamentals
----
-<p>Performance is a broad topic. This document gives a brief overview of what Firefox OS was designed and optimized for. It also introduces tools and processes developers can use to improve the performance of their code.</p>
-<h2 id="What_is_performance">What is performance?</h2>
-<p>Performance is entirely what is perceived by users. Users provide inputs to the system through touch, movement, and speech. In return, they perceive outputs in the form of visual, tactile, and auditory feedback. Performance is the quality of outputs in response to these inputs.</p>
-<p>Code that is optimized for a target other than user-perceived performance (hereafter UPP) will lose in competition against code that is, all other things being equal. Users will prefer an application that's responsive and smooth while only processing, say, 1,000 database transactions a second, over another that processes 100,000,000 a second but is choppy and unresponsive.</p>
-<p>Of course, that's not to say it's pointless to optimize metrics like the number of database transactions processed per second; it almost always is. The point is that these metrics are secondary, proximate to real UPP targets.</p>
-<p>There are a few key performance metrics. The first is "responsiveness". Responsiveness is simply the speed with which the system provides outputs (possibly multiple ones) in response to user inputs. For example, when a user taps the screen, they expect the pixels to change in a certain way. The time elapsed between the "tap" gesture and the change in pixels is the responsiveness metric for that interaction.</p>
-<p>Responsiveness sometimes involves multiple stages of feedback. Application launch is one particularly important case, which is discussed in more detail below.</p>
-<p>Responsiveness is important for the simple reason that no one wants to be ignored. Every millisecond that elapses between the user providing input to the system and the system finally responding with output is a millisecond that the user is being ignored. Being ignored engenders frustration and anger.</p>
-<p>The next key metric is "framerate": the rate at which the system changes pixels displayed to the user. This is a familiar concept; everyone prefers, say, games that display 60 frames per second over ones that display 10 frames per second, even if they can't explain why.</p>
-<p>Framerate is important as a "quality of service" metric. Computer displays are designed to "fool" user's eyes, by delivering photons to them that mimic reality. For example, document readers display text by creating arrangements of display pixels that are designed to create photons that strike users' retinas in the same patterns as photons reflected off crisply-struck text on physical paper.</p>
-<p>In reality, motion is "continuous" (as inferred by our brains anyway); it's not jerky and discrete, but rather "updates" smoothly. (Strobe lights are fun because they turn that upside down, starving our brains of inputs to create the illusion of discrete reality.) On a computer display, a higher framerate simply allows the display to imitate reality more faithfully.</p>
-<p>(An interesting aside is that humans are generally not able to perceive differences in framerate above 60Hz. That's why most modern electronic displays are designed to refresh at that rate. A television probably looks choppy and unrealistic to a hummingbird, for example.)</p>
-<p>Memory usage is another key metric. Unlike responsiveness and framerate, users don't directly perceive memory usage. However, memory usage is a close approximation to "user state". An ideal system would maintain 100% of user state at all times: all applications in the system would run simultaneously, and all applications would retain the state created by the user the last time the user interacted with the application. (Application state is stored in computer memory, which is why the approximation is close.)</p>
-<p>An important corollary of this is contrary to popular belief: a well-designed system should not be optimized to maximize the amount of <strong>free</strong> memory. Memory is a resource, and free memory is a unused resource. Rather, a well-designed system should be optimized to <strong>use</strong> as much memory as possible in service of maintaining user state, while meeting other UPP goals.</p>
-<p>Optimizing a system to use memory doesn't mean it should <strong>waste</strong> memory. Using more memory than is required to maintain some particular user state is wasting a resource that could be used to retain some other user state.</p>
-<p>In reality, no system can maintain all user state. Intelligently allocating memory to user state is an important concern that's discussed in more detail below.</p>
-<p>The final metric discussed here is power usage. Like memory usage, users don't directly perceive power usage. Users perceive power usage indirectly by their devices being able to maintain all other UPP goals for a longer duration. In service of meeting UPP goals, the system must use only the minimum amount of power required.</p>
-<p>The remainder of this document will discuss performance in terms of these metrics.</p>
-<h2 id="Platform_performance">Platform performance</h2>
-<p>This section provides a brief overview of how Firefox OS contributes to performance generally, below the level of all applications. From a developer's or user's perspective, this answers the question, what does the platform do for you?</p>
-<p>This section assumes the reader is familiar with the basic conceptual design of Firefox OS.</p>
-<p>Firefox OS is optimized for applications built with web technologies, HTML/CSS/JavaScript and so on. Except for a handful of basic system services, all the code that runs in Firefox OS is web applications and the Gecko engine. Even the operating system window manager is written in HTML/CSS/JS.</p>
-<p>Because the core operating system is built with the same web technologies that applications are built with, the performance of those technologies is critical. There's no "escape hatch". This greatly benefits developers because all the optimizations that enable a performant OS window manager, for example, are available to third-party applications as well. There's no "magic performance sauce" available only to preinstalled code.</p>
-<p>The web platform provides many tools, some better suited for particular jobs than others. All application logic is written in JavaScript. For displaying graphics, developers can choose between the high-level declarative languages of HTML/CSS, or use low-level imperative interfaces offered by the canvas element.</p>
-<p>HTML/CSS greatly increase productivity, sometimes at the cost of pixel-level control over rendering or a few frames per second. Text and images are reflowed automatically, the system theme is applied to UI elements by default, and "built-in" support is provided for some use cases developers may not think about initially, like different-resolution displays or right-to-left languages.</p>
-<p>The canvas element offers a pixel buffer directly to developers to draw on. This gives pixel-level control over rendering and precise control of framerate to developers. But it comes at the expense of extra work needed to deal with multiple resolutions and orientations, right-to-left languages, and so forth. Developers draw to canvases using either a familiar 2D drawing API, or WebGL, a "close to the metal" binding that mostly follows OpenGL ES 2.0.</p>
-<p>(Somewhere "in between" HTML/CSS and canvas is SVG, which is beyond the scope of this document.)</p>
-<p>The Gecko JavaScript engine supports just-in-time (JIT) compilation. This enables application logic to perform comparably to other virtual machines, such as Java virtual machines, and in some cases close to "native code".</p>
-<p>The graphics pipeline in Gecko underlying HTML/CSS and canvas is optimized in several ways. The HTML/CSS layout and graphics code in Gecko minimizes invalidation and repainting for common cases likes scrolling; developers get this support "for free". Pixel buffers painted by both Gecko "automatically" and applications to canvas "manually" minimize copies when being drawn to the display framebuffer. This is done by avoiding intermediate surfaces where they would create overhead (such as per-application "back buffers" in many other operating systems), and by using special memory for graphics buffers that can be directly accessed by the compositor hardware. Complex scenes are rendered using the device's GPU for maximum performance. To improve power usage, simple scenes are rendered using special dedicated composition hardware, while the GPU idles or turns off.</p>
-<p>Fully static content is the exception rather than the rule for rich applications. Rich applications use dynamic content with animations, transitions, and other effects. Transitions and animations are particularly important to applications. Developers can use CSS to declare even complicated transitions and animations with a simple, high-level syntax. In turn, Gecko's graphics pipeline is highly optimized to render common animations efficiently. Common-case animations are "offloaded" to the system compositor, which can render them both performantly and power efficiently.</p>
-<p>The runtime performance of applications is important, but just as important is their startup performance. Firefox OS improves startup experience in several ways.</p>
-<p>Gecko is optimized to load a wide variety of content efficiently: the entire Web! Many years of improvements targeting this content, like parallel HTML parsing, intelligent scheduling of reflows and image decoding, clever layout algorithms, etc, translate just as well to improving web applications on Firefox OS. The content is written using the same technologies.</p>
-<p>Each web application has its own instance of the Gecko rendering engine. Starting up this large, complicated engine is not free, and because of that, Firefox OS keeps around a preallocated copy of the engine in memory. When an app starts up, it takes over this preallocated copy and can immediately begin loading its application resources.</p>
-<p>Applications "start" most quickly when they're already running. To this end, Firefox OS tries to keep as many applications running in the background as possible, while not regressing the user experience in foreground applications. This is implemented by intelligently prioritizing applications, and discarding background applications according to their priorities when memory is low. For example, it's more disruptive to a user if their currently-playing music player is discarded in the background, while their background calculator application keeps running. So, the music player is prioritized above the calculator automatically by Firefox OS and the calculator is discarded first when memory is low.</p>
-<p>Firefox OS prevents applications that are running in the background from impacting the user experience of foreground applications through two mechanisms. First, timers created by background apps are "throttled" to run at a low frequency. Second, background applications are given a low CPU priority, so that foreground applications can get CPU time when they need it.</p>
-<p>In addition to the above, Firefox OS includes several features designed to improve power usage that are common to mobile operating systems. The Firefox OS kernel will eagerly suspend the device for minimal power usage when the device is idle. Relatedly, ICs like the GPU, cellular radio, and Wifi radio are powered down when not being actively used. Firefox OS also takes advantage of hardware support for media decoding.</p>
-<h2 id="Application_performance">Application performance</h2>
-<p>This section is intended for developers asking the question: "how can I make my app fast"?</p>
-<h3 id="Startup_performance">Startup performance</h3>
-<p>Application startup is punctuated by three user-perceived events, generally speaking. The first is the application "first paint": the point at which sufficient application resources have been loaded to paint an initial frame. Second is when the application becomes interactive; for example, users are able to tap a button and the application responds. The final event is "full load", for example when all the user's albums have been listed in a music player.</p>
-<p>The key to fast startup is to keep two things in mind: UPP is all that matters, and there's a "critical path" to each user-perceived event above. The critical path is exactly and only the code that must run to produce the event.</p>
-<p>For example, to paint an application's first frame that comprises visually some HTML and CSS to style that HTML, (i) the HTML must be parsed; (ii) the DOM for that HTML must be constructed; (iii) resources like images in that part of the DOM have to be loaded and decoded; (iv) the CSS styles must be applied to that DOM; (v) the styled document has to be reflowed. Nowhere in that list is "load the JS file needed for an uncommon menu"; "fetch and decode the image for the High Scores list"; etc. Those work items are not on the critical path to painting the first frame.</p>
-<p>It seems obvious, but to reach a user-perceived startup event more quickly, the main "trick" is to just not run code that's off the critical path. Alternatively, shorten the critical path by simplifying the scene.</p>
-<p>The web platform is highly dynamic. JavaScript is a dynamically-typed language, and the web platform allows loading code, HTML, CSS, images, and other resources dynamically. These features can be used to defer work at startup that's off the critical path, by loading the unnecessary content "lazily" some time after startup.</p>
-<p>Another problem that can delay startup is idle time, caused by waiting on responses to requests like database loads. To avoid this problem, applications can "front load" the work by issuing requests as early as possible in startup. Then when the data is needed later, it's hopefully already been fetched and the application doesn't need to wait.</p>
-<p>Relatedly, it's important to separate network requests for dynamic data from static content that can be cached locally. Locally-cached resources can be loaded much more quickly than they can be fetched over high-latency and lower-bandwidth mobile networks. Network requests should never be on the critical path to early application startup. Caching resources locally is also the only way applications can be used when "offline". Firefox OS allows applications to cache resources by either being "packaged" in a compressed ZIP file or "hosted" through HTML5 appcache. How to choose between these options for a particular type of application is beyond the scope of this document, but in general application packages provide optimal load performance; appcache is slower.</p>
-<p>A few other hints are listed below:</p>
-<ul>
-  <li>
-    <p>Don't include scripts or stylesheets that don't participate in the critical path in your startup HTML file. Load them when needed.</p>
-  </li>
-  <li>
-    <p>Use the "defer" or "async" attribute on script tags needed at startup. This allows HTML parsers to process documents more efficiently.</p>
-  </li>
-  <li>
-    <p>Don't force the web engine to construct more DOM than is needed. A "hack" to do this simply is to leave your HTML in the document, but commented out.</p>
-    <pre>&lt;div id="foo"&gt;&lt;!--
-  &lt;div&gt; ...
---&gt;&lt;/div&gt;</pre>
-  </li>
-  <li>
-    <p>When that part of the document needs to be rendered, load the commented HTML.</p>
-    <pre>foo.innerHTML = foo.firstChild.nodeValue;</pre>
-  </li>
-  <li>
-    <p>Use Web Worker Threads for background processing. Only the application "main thread" can process user events and render primary UI. But a common use case is to fetch some data, process it, then update the UI. Use Worker Threads for this work and keep the main thread free for interacting with the user.</p>
-  </li>
-</ul>
-<h3 id="Framerate">Framerate</h3>
-<p>The first important consideration for achieving high framerate is to select the right tool for the job. Mostly static content that's scrolled and infrequently animated is usually best implemented with HTML/CSS. Highly dynamic content like games that need tight control over rendering, and don't need theming, is often best implemented with canvas.</p>
-<p>For content drawn using canvas, it's up to the developer to hit framerate targets: they have direct control over what's drawn.</p>
-<p>For HTML/CSS content, the path to high framerate is to use the right primitives. Firefox OS is highly optimized to scroll arbitrary content; this is usually not a concern. But often trading some generality and quality for speed, such as using a static rendering instead of a CSS radial gradient, can push scrolling framerate over a target. CSS media queries allow these compromises to be restricted only to devices that need them.</p>
-<p>Many applications use transitions or animations through "pages", or "panels". For example, the user taps a "Settings" button to transition into an application configuration screen, or a settings menu "pops up". Firefox OS is highly optimized to transition and animate scenes that</p>
-<ul>
-  <li>Use pages/panels that are approximately the size of the device screen or smaller</li>
-  <li>Transition/animate the CSS transform and opacity properties</li>
-</ul>
-<p>Transitions and animations that adhere to these guidelines can be offloaded to the system compositor and run maximally efficiently.</p>
-<p>To help diagnose low framerates, see the section below.</p>
-<h3 id="Memory_and_power_usage">Memory and power usage</h3>
-<p>Improving memory and power usage is a similar problem to speeding up startup: don't do unnecessary work; use efficient data structures; lazily load uncommonly-used UI resources; ensure resources like images are optimized well.</p>
-<p>Modern CPUs can enter a lower-power mode when mostly idle. Applications that constantly fire timers or keep unnecessary animations running prevent CPUs from entering low-power mode. Power-efficient applications don't do that.</p>
-<p>When applications are sent to the background, a visibilitychange event is fired on their documents. This event is a developer's friend; applications should listen for it. As mentioned above, Firefox OS tries to keep as many applications running simultaneously as it can, but does have to discard applications sometimes. Applications that drop as many loaded resources as possible when sent to the background will use less memory and be less likely to be discarded. This in turn means they will "start up" faster (by virtue of already being running) and have better UPP.</p>
-<p>Similarly, applications should prepare for the case when they
-  <i>
-    are</i>
-  discarded. To improve user-perceived memory usage, that is to say, making the user feel that more of their state is being preserved, applications should save the state needed to return the current view if discarded. If the user is editing an entry, for example, the state of the edit should be saved when entering the background.</p>
-<h2 id="Measuring_performance_and_diagnosing_problems">Measuring performance and diagnosing problems</h2>
-<p>Before beginning to measure and diagnose performance problems, remember this:</p>
-<div class="geckoVersionNote">
-  <blockquote>
-     </blockquote>
-  <blockquote>
-    Must. Test. On. Device.</blockquote>
-  <blockquote>
-     </blockquote>
-</div>
-<p>A great strength of the web platform is that the same code written for "desktop" web browsers runs on Firefox OS on mobile devices. Developers should use this to improve productivity: develop on "desktops", in comfortable and productive environments, as much as possible.</p>
-<p>But when it comes time to test performance, mobile devices must be used. Modern desktops can be more than 100x more powerful than mobile hardware. The lower-end the mobile hardware tested on, the better.</p>
-<p>With that caveat, the sections below describe tools and processes for measuring and diagnosing performance issues.</p>
-<h3 id="Measuring_performance">Measuring performance</h3>
-<p>Firefox OS comes built-in with some convenient and easy-to-use tools that, when used properly, can be used to quickly measure performance. The first tool is the "framerate monitor". This can be enabled in the Firefox OS Settings application.</p>
-<p>The framerate monitor continuously reports two numbers. The values reported are an average of recent results within a sliding window, meant to be "instantaneous" but fairly accurate. As such, both numbers are "guesses". The left number is the "composition rate": the estimated number of times per second Firefox OS is drawing frames to the hardware framebuffer. This is an estimate of the user-perceived framerate, and only an estimate. For example, the counter may report 60 compositions per second even if the screen is not changing. In that case the user-perceived framerate would be 0. However, when used with this caveat in mind and corroborated with other measurements, the monitor can be a useful and simple tool.</p>
-<p><img alt="Screenshot of fps counter" src="http://people.mozilla.com/~cjones/mdn/enable-fps-counter.png" style="width: 320px; height: 480px;"></p>
-<p>The rightmost number is the "layer transaction rate", the estimated number of times per second processes are repainting and notifying the compositor. This number is mostly useful for Gecko platform engineers, but it should be less than or equal to the composition rate number on the left.</p>
-<p>Firefox OS also has a tool that can help measure startup time, specifically the "first paint" time described above. This "time-to-load" tool can be enabled using the Settings application. The value shown by the tool is the elapsed time between when the most recent application was launched, and an estimate of the first time that application painted its UI. This number only approximates the real "first paint" time, and in particular underestimates it. However, lowering this number almost always correlates to improvements in real startup time, so it can be useful to quickly measure optimization ideas.</p>
-<p><img alt="Screenshot of enabling ttl" src="http://people.mozilla.com/~cjones/mdn/enable-ttl.png" style="width: 320px; height: 480px;"></p>
-<p>For accurately measuring both startup times and responsiveness, a high-speed camera is indispensable. "High-speed" means that the camera can record 120 frames per second or above. The higher the capture rate, the more accurate the measurements that can be made. This may sound like exotic technology, but consumer models can be purchased for a few hundred US dollars.</p>
-<p><a href="http://people.mozilla.com/~cjones/mdn/hs-example.webm" title="http://people.mozilla.com/~cjones/mdn/hs-example.webm">Link to example video of high-speed capture that I can't upload</a></p>
-<p>The measuring process with these cameras is simple: record the action to be studied, and then play back the capture and count the number of frames that elapse between the input (say, a tap gesture) and the desired output (pixels changing in some way). Divide the number of counted frames by the capture rate, and the resulting number is the measured duration.</p>
-<p>Mozilla built an automated tool called Eideticker which operates on the same principle as described above. The difference is that Eideticker uses synthetic user input events and HDMI capture to measure durations. The code is available and can be used with any device with an HDMI output.</p>
-<p>Measuring power can be more difficult. It's possible to jury-rig measurement apparatus with a soldering iron, but a good approximation of power usage can be gathered by observing CPU load. Simple command-line tools like |top| allow monitoring CPU usage continuously.</p>
-<p>In general, when measuring performance, don't be proud! "Primitive technology" like a stopwatch or logging, when used effectively, can provide eminently usable data.</p>
-<h3 id="Diagnosing_performance_problems">Diagnosing performance problems</h3>
-<p>If performance measurements show an application is below its targets, how can the underlying problem be diagnosed?</p>
-<p>The first step of any performance work is to create a reproducible workload and reproducible measurement steps. Then gather baseline measurements, before any code changes are made. It seems obvious, but this is required to determine whether code changes actually improve performance! The measurement process selected isn't too important; what's important is that the process be (i) reproducible; (ii) realistic, in that it measures what users will perceive as closely as possible; (iii) precise as possible; (iv) accurate as possible. Even stopwatch timings can fit this spec.</p>
-<p>Firefox OS includes two built-in tools for quickly diagnosing some performance issues. The first is a render mode called "paint flashing". In this mode, every time a region of the screen is painted by Gecko, Gecko blits a random translucent color over the painted region. Ideally, only parts of the screen that visually change between frames will "flash" with a new color. But sometimes more area than is needed is repainted, causing large areas to "flash". This symptom may indicate that application code is forcing too much of its scene to update. It may also indicate bugs in Gecko itself.</p>
-<p><img alt="Enable paint flashing" src="http://people.mozilla.com/~cjones/mdn/enable-paint-flashing.png" style="width: 320px; height: 480px;"></p>
-<p><img alt="Paint flashing after scrolling down from previous image" src="http://people.mozilla.com/~cjones/mdn/enable-paint-flashing-scroll-down.png" style="width: 320px; height: 480px;"></p>
-<p>The second tool is called "animation logging", and can also be enabled in Settings. This tool tries to help developers understand why animations are not offloaded to the compositor to be run efficiently as possible. It reports "bugs" like trying to animate elements that are too large, or trying to animate CSS properties that can't be offloaded.</p>
-<p><img alt="Enable animation logging" src="http://people.mozilla.com/~cjones/mdn/enable-log-animations.png" style="width: 320px; height: 480px;"></p>
-<p><img alt="Start of animation not offloaded" src="http://people.mozilla.com/~cjones/mdn/enable-log-animations-1.png" style="width: 320px; height: 480px;"></p>
-<pre>I/Gecko   ( 5644): Performance warning: Async animation disabled because frame size (1280, 410) is bigger than the viewport (360, 518) [div with id 'views']
-</pre>
-<p><img alt="End of animation not offloaded" src="http://people.mozilla.com/~cjones/mdn/enable-log-animations-2.png" style="width: 320px; height: 480px;"></p>
-<div class="note">
-  <p>A common pitfall is to animate left/top/right/bottom properties instead of using CSS transforms to achieve the same effect. For a variety of reasons, the semantics of transforms make them easier to offload, but left/top/right/bottom are much more difficult. Animation logging will report this.</p>
-</div>
-<p>These tools can help quickly assess a performance problem, but they often show only what developers should be "looking for": hints at deeper problems. When more information is required, the Gecko Profiler can be used. A full description of the profiler is beyond the scope of this document; see <a href="/en-US/docs/Performance/Profiling_with_the_Built-in_Profiler" title="/en-US/docs/Performance/Profiling_with_the_Built-in_Profiler">[here]</a>. Briefly, the profiler shows mixed JavaScript/C++ "samples" of what all Firefox OS processes are doing over a rolling time interval. Developers can use these profiles to see what their code and Gecko itself are doing. Warnings are built into the profiler UI for many common pitfalls like excessive garbage collection (caused by creating too many JS objects), and forcing "synchronous reflows". Sync reflows are bad because Gecko is optimized to do expensive work like reflows in big batches, when needed. Forced reflows throw off this "schedule", and can cause more work to be done than necessary.</p>
-<p>Similarly, advanced users may wish to use a whole-system profiler like the linux |perf| tool. This is mostly useful for platform engineers, though.</p>
-<p>As with measuring performance, don't be proud about tools used to diagnose it! A few well-placed Date.now() calls with logging can often provide a quick and accurate answer.</p>
-<p>Finally, the only way to keep improving performance is to not regress it. The only way to not regress performance is to test it, preferably with automated tests. A full discussion of that topic is beyond the scope of this document, though.</p>
-<h2 id="Paris_Firefox_OS_Performance_Optimization_Workshop_March_4_-_8_2013">Paris Firefox OS Performance &amp; Optimization Workshop, March 4 - 8, 2013</h2>
-<p>To illustrate these concepts here are some videos and slides from the Paris Workshop dedicated to performances and optimizations.</p>
-<p>Part 1: Technical basics and more (Gabriele &amp; Thomas)</p>
-<ul>
-  <li>Video : <a href="https://docs.google.com/file/d/0ByB4v6HDNT-ZdHAtam5IdWpWWkE/edit?usp=sharing" title="https://docs.google.com/file/d/0ByB4v6HDNT-ZdHAtam5IdWpWWkE/edit?usp=sharing">Technical considerations</a></li>
-  <li>Slides : <a href="https://docs.google.com/file/d/0ByB4v6HDNT-ZNGRxS3A1X21tMjQ/edit?usp=sharing" title="https://docs.google.com/file/d/0ByB4v6HDNT-ZNGRxS3A1X21tMjQ/edit?usp=sharing">Presentation</a></li>
-</ul>
-<p>Part 2: <a href="https://docs.google.com/file/d/0ByB4v6HDNT-ZWFNkRGtyTHd5TUU/edit?usp=sharing" title="https://docs.google.com/file/d/0ByB4v6HDNT-ZWFNkRGtyTHd5TUU/edit?usp=sharing">Performances in a UX point of view</a> (Josh)</p>
-<p>Part 3: <a href="https://docs.google.com/file/d/0ByB4v6HDNT-ZdUVadVBmeDlXaW8/edit?usp=sharing" title="https://docs.google.com/file/d/0ByB4v6HDNT-ZdUVadVBmeDlXaW8/edit?usp=sharing">Performances measurement &amp; automation</a> (Julien &amp; Anthony)</p>
diff --git a/files/hu/archive/b2g_os/using_the_app_manager/index.html b/files/hu/archive/b2g_os/using_the_app_manager/index.html
deleted file mode 100644
index b18aa26621..0000000000
--- a/files/hu/archive/b2g_os/using_the_app_manager/index.html
+++ /dev/null
@@ -1,281 +0,0 @@
----
-title: Using the App Manager
-slug: Archive/B2G_OS/Using_the_App_Manager
-translation_of: Archive/B2G_OS/Using_the_App_Manager
----
-<div class="summary">
-<p><span class="seoSummary">The App Manager is a tool for Firefox Desktop which provides a number of useful tools to help developers test, deploy and debug HTML5 web apps on Firefox OS phones &amp; Simulator, directly from Firefox browser. This page documents how to use the App Manager.</span></p>
-
-<p>App Manager is available for Firefox OS 1.2 or later, lower versions are supported in <a href="/en-US/docs/Tools/Firefox_OS_1.1_Simulator">Firefox OS 1.1 Simulator</a>. The App Manager is being replaced by the <a href="/en-US/docs/Tools/WebIDE">WebIDE</a>, starting from Firefox 33. The WebIDE provides all the features of the App Manager and also features an editing environment to create and develop Firefox OS apps.</p>
-</div>
-
-<p>{{EmbedYouTube("z1Bxg1UJVf0")}}</p>
-
-<p>The App Manager is composed of:</p>
-
-<ul>
- <li>An <a href="#Apps_panel"><em>Apps panel</em></a>, which manages local apps (app source code located on your computer) and apps hosted externally, allowing you to package and install them on your device or simulator, and debug them using Toolboxes</li>
- <li>A <a href="#Device_panel"><em>Device panel</em></a>, which displays information about the connected device including Firefox OS version installed, permissions required for using device APIs on the device, and apps installed</li>
- <li><a href="/en-US/docs/Tools_Toolbox"><em>Toolboxes</em></a>, which are are sets of developer tools (web console, inspector, debugger, etc.) that can be connected to a running app via the Apps panel to perform debugging operations</li>
-</ul>
-
-<h2 id="Quick_setup"><a name="Configuring_device">Quick setup</a></h2>
-
-<p>This section is designed to get you up and running as soon as possible; if you need some more detail please skip forward to the {{ anch("Device and system configuration") }} section and start reading from there.  Also see the {{ anch("Troubleshooting") }} section for help if you are having trouble.</p>
-
-<ol>
- <li>Make sure you have Firefox Desktop 26+ installed</li>
- <li>Open the App Manager (in the URL bar, type <code>about:app-manager</code>, or go to <em>Tools &gt; Web Developer &gt; App Manager</em> in your Firefox menu.) This should appear in a new browser tab.</li>
- <li>If you don't have a real device:
-  <ol>
-   <li><a href="https://ftp.mozilla.org/pub/mozilla.org/labs/fxos-simulator/">Install the Firefox OS Simulator</a> add-on, then go back to the App Manager tab of your browser.</li>
-   <li>In App Manager's bottom toolbar, click on <em>Start Simulator</em>, then click on the name of the installed simulator, which should appear there.</li>
-  </ol>
- </li>
- <li>If you have a real device:
-  <ol>
-   <li>Make sure your device is running Firefox OS 1.2+</li>
-   <li>On Windows, make sure to install the drivers provided by your phone manufacturer</li>
-   <li>In the Settings of your device, disable Screen Lock (<code>Settings &gt; Phone lock &gt; <code>Lock Screen</code></code>) and enable Remote Debugging (<code>Settings &gt; Device information &gt; More information &gt; Developer</code>)</li>
-   <li><a href="https://ftp.mozilla.org/pub/mozilla.org/labs/fxos-simulator/">Install the ADB Helper</a> add-on in Firefox Desktop</li>
-   <li>Connect your device to your machine via a USB cable</li>
-   <li>You should see the name of your device in the App Manager's bottom bar. Click on it.</li>
-  </ol>
- </li>
- <li>The bottom bar should show "Connected to: xxx"</li>
- <li>Click on the <em>Apps</em> panel and add an app (packaged or hosted)</li>
- <li>The <em>Refresh</em> button validates your app and installs it on the Simulator/Device</li>
- <li>The <em>Debug</em> button connects the developer tools to the running app</li>
- <li><strong>See the {{ anch("Troubleshooting") }} section for help if you are having trouble</strong></li>
-</ol>
-
-<h2 id="Device_and_system_configuration">Device and system configuration</h2>
-
-<p>The first thing you'll need to do when using the App Manager is make sure your system and phone are set up correctly. This section will run through all the steps required.</p>
-
-<h3 id="Firefox_OS_1.2_required">Firefox OS 1.2+ required</h3>
-
-<p>Make sure your device is running Firefox OS 1.2/Boot2Gecko 1.2 or higher. To check which version of Firefox OS the device is runing, go to <code>Settings &gt; Device Information &gt; Software</code>.</p>
-
-<p>If you don't have a high enough version installed, depending on what phone you have you will need to either install an available nightly build of Firefox 1.2+, or configure and build it yourself from source.</p>
-
-<p>Builds available:</p>
-
-<ul>
- <li><a href="http://downloads.geeksphone.com/">Geeksphone Keon/Peak builds</a> (to find out more about using these, read <a href="/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/Updating_and_Tweaking_Geeksphone">Updating and Tweaking your Firefox OS Developer Preview phone/Geeksphone</a>)</li>
- <li>More to follow</li>
-</ul>
-
-<div class="note">
-<p><strong>Note</strong>: To build your own Firefox OS 1.2+ distribution, follow the instructions located at <a href="/en-US/docs/Mozilla/Firefox_OS/Building_and_installing_Firefox_OS">Building and installing Firefox OS</a>, starting with <a href="/en-US/docs/Mozilla/Firefox_OS/Firefox_OS_build_prerequisites">Firefox OS build prerequisites</a>.</p>
-</div>
-
-<h3 id="Remote_debugging">Remote debugging</h3>
-
-<p>Next, you need to enable remote debugging in Firefox OS. To do so, go to <code>Settings &gt; Device information &gt; More information &gt; Developer</code> and check the Remote Debugging checkbox.</p>
-
-<h3 id="Adb_Helper_Add-on" name="Adb_Helper_Add-on">ADB or ADB helper</h3>
-
-<p>The process uses the Android Debug Bridge (ADB) to handle the device-computer connection and communication. There are two options for running ADB:</p>
-
-<ul>
- <li>
-  <p>Let Firefox handle ADB (recommended). <a href="https://ftp.mozilla.org/pub/mozilla.org/labs/fxos-simulator/">Install the ADB Helper add-on</a>, which makes the process easier. With this installed, there's no need to install the ADB, and no need to type the <code>adb forward</code> command: everything is handled by the add-on.</p>
-  <a href="https://ftp.mozilla.org/pub/mozilla.org/labs/fxos-simulator/" style="margin-bottom: 20px; padding: 10px; text-align: center; border-radius: 4px; display: inline-block; 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;" title="https://addons.mozilla.org">Download ADB Helper Add-on</a></li>
- <li>Use ADB manually. You need to have it installed on your computer: download and install <code>adb</code> as explained in <a href="/en-US/Firefox_OS/Debugging/Installing_ADB">Installing ADB</a>. You'll need to enable port forwarding by entering the following command into your terminal:
-  <pre>adb forward tcp:6000 localfilesystem:/data/local/debugger-socket</pre>
-  Note that you'll need to do this every time the phone is restarted or unplugged then re-plugged.</li>
-</ul>
-
-<div class="note">
-<p><strong>Note</strong>: There's no need to run this command if you installed the ADB Helper Add-on.</p>
-</div>
-
-<h2 id="Connecting_your_device_to_the_App_Manager">Connecting your device to the App Manager</h2>
-
-<p>With all your configuration done, it's now time to plug your device into your computer and start the App Manager:</p>
-
-<ol>
- <li>Plug the device into your computer via USB.</li>
- <li>Disable Screen lock on your device by going to <code>Settings &gt; Screen Lock</code> and unchecking the <code>Lock Screen</code> checkbox. This is a good idea because when the screen gets locked, the phone connection gets lost, meaning it is no longer available for debugging.</li>
- <li>Start the App Manager — In Firefox Desktop select the <code>Tools &gt; Web Developer &gt; App Manager</code> menu option, or type <code>about:app-manager</code> in the URL bar.</li>
- <li>At the bottom of the App Manager tab, you will see a connection status bar (see screenshot below). You should be able to connect your device by clicking the "Connect to localhost:6000" button.</li>
- <li>If this works successfully, a prompt should appear on your device: "An incoming request to permit remote debugging connection was detected. Allow connection?". Tap the OK button (You may also have to press the power button on the phone so you can see the prompt.) The connection status bar should update to say "Connected to B2G", with a Disconnect button available to press if you want to cancel the connection.</li>
-</ol>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/6263/connection-status.png" style="display: block; height: 30px; margin: 0px auto; width: 600px;"></p>
-
-<div class="note">
-<p><strong>Note</strong>: The other controls in the connection status bar allow you to connect a simulator to the App Manager, which we cover in the next section, below, and change the port that the connection happens on. If you change the port, you'll also need to enable port forwarding for this port as well, as instructed in the {{anch("Enable port forwarding")}} section, above.</p>
-</div>
-
-<h2 id="Using_a_Firefox_OS_Simulator_Add-on"><a name="Simulator">Using a Firefox OS Simulator Add-on</a></h2>
-
-<p>If you haven't got a real device available to use with App Manager, you can still try it out using a <a href="/en-US/docs/Tools/Firefox_OS_Simulator">Firefox OS Simulator</a> Add-on. To start off, install the simulator with the following button (multiple versions are available; you are advised to install them all, for maximum flexibility):</p>
-
-<p><a class="download-button external ignore-external" href="https://ftp.mozilla.org/pub/mozilla.org/labs/fxos-simulator/" rel="noopener">Install Simulator</a></p>
-
-
-<p>Once you've installed the simulator(s), you need to go to about:app-manager to see the connection status bar at the bottom of the App Manager tab, and click the "Start simulator" button. At least three buttons will appear:</p>
-
-<ul>
- <li>"Firefox OS 1.3", "Firefox OS 1.2" ... etc. (or something similar): the left-most buttons contain the names of the simulator versions you have installed. Click one to start a connection to a simulator.</li>
- <li>"Add": the middle button navigates to the simulator install links in this article, so you can add more Simulators (Firefox OS 1.3, Firefox OS 1.4, etc.)</li>
- <li>"Cancel": the right hand button cancels the connection.</li>
-</ul>
-
-<div class="note">
-<p><strong>Note</strong>: The Firefox OS 1.5 Simulator has been removed, as 1.5 was changed to 2.0. If you have the Firefox OS 1.5 Simulator installed, it won't automatically update to 2.0, so you should uninstall 1.5 and install 2.0 instead. The Firefox OS 2.0 simulator will then automatically update.</p>
-</div>
-
-<div class="note">
-<p><strong>Note</strong>: The Firefox OS 1.2 Simulator has been removed, as no phones are likely to be released with version 1.2 installed — this version is therefore of limited value, and it makes more sense to spend your time debugging on other versions.</p>
-</div>
-
-<h2 id="Running_custom_builds_in_the_App_Manager">Running custom builds in the App Manager</h2>
-
-<p>Note that you can run custom B2G Desktop and Gaia/Gecko builds in the App Manager via the simulator. Read <a href="/en-US/Firefox_OS/Running_custom_builds_in_the_App_Manager">Running custom Firefox OS/Gaia builds in the App Manager</a> for instructions on how to do this.</p>
-
-<h2 id="Apps_panel_Test_and_debug_Firefox_OS_apps"><a name="Apps_panel">Apps panel</a>: Test and debug Firefox OS apps</h2>
-
-<p>Now that everything is working, let's review the functionality available inside the App Manager, starting with the Apps panel. From here, you can import an existing app to push onto your device, for testing and debugging:</p>
-
-<ul>
- <li>To install a locally stored app, click on the plus next to the "Add Packaged App" label and use the resulting file chooser dialog to select the directory your app is contained inside.</li>
- <li>To install an externally hosted app, enter the absolute URL of the app's manifest file into the text field inside the "Add Hosted App" box, then press the plus button.</li>
-</ul>
-
-<p>Information about your app should appear on the right hand side of the window, as seen below:</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/6261/apps-panel.png" style="display: block; height: 375px; margin: 0px auto; width: 600px;"></p>
-
-<h3 id="Manifest_editor">Manifest editor</h3>
-
-<p>From Firefox 28 onwards, the Apps Panel includes an editor for the app manifest:</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/6613/apps-panel-fx-28.png" style="display: block; margin: 0px auto; width: 600px;"></p>
-
-<h3 id="Debugging">Debugging</h3>
-
-<p>Clicking on <em>"Update"</em> will update (install) the app on the device. Clicking on <em>"debug"</em> will connect a toolbox to the app, allowing you to debug its code directly:</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/6265/debug.png" style="display: block; height: 375px; margin: 0px auto; width: 600px;"></p>
-
-<div class="note">
-<p>You'll enjoy playing around with the toolbox — try altering the DOM, CSS etc. and you'll see the updates reflected on the device in realtime. Such updates will be saved on the installed app code; you'll see them next time you open the app on the device.</p>
-</div>
-
-<p>Before Firefox 28, the tools are launched in a separate window. From Firefox 28 onwards, the tools are launched in a separate tab in the App Manager itself, alongside the Apps and Device tabs. The tab is given your app's icon so it's easy to find:</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/6615/toolbox-fx-28.png" style="display: block; height: 375px; margin: 0px auto; width: 600px;"></p>
-
-<h3 id="Errors">Errors</h3>
-
-<p>If an app was not added successfully — for example if the URL was incorrect, or you selected a packaged app folder — an entry will be added to the page for this app, but this will include error information.</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/6259/apps-error.png" style="display: block; height: 375px; margin: 0px auto; width: 600px;"></p>
-
-<p>You can also delete an app from this view, by hovering over the App name/description on the left of the window, and pressing the "X" button that appears in each case. This however doesn't remove the app from the device. To do that you need to manually remove the app using the device itself.</p>
-
-<h2 id="Device_panel_2"><a name="Device_panel">Device panel</a></h2>
-
-<p>The <em>Device</em> tab displays information about the connected device. From the <em>"</em>Installed Apps<em>"</em> window, apps on the device can be started and debugged.</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/6267/device-tab.png" style="display: block; height: 375px; margin: 0px auto; width: 600px;"></p>
-
-<div class="note">
-<p>Note: Certified Apps are not listed by default. <a href="#Debugging_Certified_Apps">See how to debug certified apps</a>.</p>
-</div>
-
-<p><a name="permissions"></a>The "Permissions" window shows the required privileges for different <a href="/en-US/docs/WebAPI">Web APIs</a> on the current device:</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/6269/permissions.png" style="display: block; height: 375px; margin: 0px auto; width: 600px;"></p>
-
-<p>Finally, you can take a screenshot of the current device display by clicking the "Screenshot" button. The screenshot appears in a new tab on Firefox, and from there you can save or discard it as you wish.</p>
-
-<h2 id="Debugging_Certified_Apps_2"><a name="Debugging_Certified_Apps">Debugging Certified Apps</a></h2>
-
-<p>Currently only devices running a development build of Firefox OS 1.2+ are capable of debugging certified apps. If you have a development build, you can enable certified app debugging by changing the pref <code>devtools.debugger.forbid-certified-apps</code> to <code>false</code> in your profile. To do this, follow the steps below:</p>
-
-<h3 id="Using_a_real_device">Using a real device</h3>
-
-<ol>
- <li>
-  <p>On your computer, enter the following command in Terminal/console to enter your device's filesystem via the shell:</p>
-
-  <pre class="brush: bash">adb shell</pre>
-
-  <p>Your prompt should change to <code>root@android</code>.</p>
- </li>
- <li>
-  <p>Next, stop B2G running using the following command:</p>
-
-  <pre class="brush: bash">stop b2g</pre>
- </li>
- <li>
-  <p>Navigate to the following directory:</p>
-
-  <pre>cd /data/b2g/mozilla/*.default/</pre>
- </li>
- <li>
-  <p>Here, update the prefs.js file with the following line:</p>
-
-  <pre class="brush: js">echo 'user_pref("devtools.debugger.forbid-certified-apps", false);' &gt;&gt; prefs.js</pre>
- </li>
- <li>
-  <p>After you've finished editing and saving the file, start B2G again using the following command:</p>
-
-  <pre class="brush: bash">start b2g</pre>
- </li>
- <li>
-  <p>Exit the android filesystem using the <code>exit</code> command; this will return you to your normal terminal prompt.</p>
- </li>
- <li>
-  <p>Next, reconnect to the App Manager and you should see certified apps appear for debugging.</p>
- </li>
-</ol>
-
-<h3 id="Using_the_B2G_desktop_client">Using the B2G desktop client</h3>
-
-<p class="brush: js">With the B2G desktop client, the preference is already defined in your profile in <code>greprefs.js</code>, located at the root of your B2G desktop client folder. Stop your B2G desktop client and edit the file to turn the <code>devtools.debugger.forbid-certified-apps</code> preference to <code>false</code>. Then restart the B2G client and connect the App Manager. You should now see all applications.</p>
-
-<div class="note">
-<p>Note: If you want to add this preference to your Gaia build you can run <code>make DEVICE_DEBUG=1 reset-gaia</code>.</p>
-</div>
-
-<h2 id="Troubleshooting_2"><a name="Troubleshooting">Troubleshooting</a></h2>
-
-<p id="My_device_is_not_recognized">If the device is not recognized:</p>
-
-<ul>
- <li>If clicking the button corresponding to your Firefox OS phone doesn't do anything, make sure you haven't connected an Android phone at the same time as the Firefox OS phone to your computer.</li>
- <li>Read the <a href="#Configuring_device">Device and system configuration</a> section thoroughly, and make sure all the steps are followed:</li>
- <li>Is your device running at least Firefox OS 1.2?</li>
- <li>Don't see all the apps? Do you need to enable <a href="#Debugging_Certified_Apps">Certified Apps debugging</a>?</li>
- <li>Did you enable "Remote Debugging" in the settings of your phone?</li>
- <li>If you are not using the <a href="#Adb_Helper_Add-on">ADB Helper add-on</a>:
-  <ul>
-   <li>Did you successfully run the <code>adb forward</code> command?</li>
-  </ul>
- </li>
- <li>If you are using the <a href="#Adb_Helper_Add-on">ADB Helper add-on</a> and your device is not listed in the bottom toolbar:
-  <ul>
-   <li>If you use Linux, <a href="http://developer.android.com/tools/device.html#setting-up">make sure to setup udev correctly</a></li>
-   <li>If you use Windows, <a href="http://developer.android.com/tools/device.html#setting-up">make sure to install the appropriate drivers</a></li>
-   <li>You can also enable verbose logging to gather diagnostics:
-    <ul>
-     <li>Use about:config to set the pref "<span class="message"><span class="content"><span class="email">extensions.adbhelper@mozilla.org.sdk</span>.console.logLevel"</span></span> to the string value "all"</li>
-     <li>Disable and re-enable the ADB Helper add-on from the add-ons manager, or restart Firefox</li>
-     <li>Open the App Manager again</li>
-     <li>In the <a href="/docs/Tools/Browser_Console">Browser Console</a>, you should now see additional output lines that mention "adbhelper"</li>
-     <li>If you see them but aren't sure what they mean, stop by the <a href="https://wiki.mozilla.org/DevTools/GetInvolved#Communication">#devtools room on IRC</a> or <a href="https://bugzilla.mozilla.org/enter_bug.cgi?alias=&amp;assigned_to=nobody%40mozilla.org&amp;attach_text=&amp;blocked=&amp;bug_file_loc=http%3A%2F%2F&amp;bug_ignored=0&amp;bug_severity=normal&amp;bug_status=NEW&amp;cf_blocking_b2g=---&amp;cf_crash_signature=&amp;cf_status_b2g18=---&amp;cf_status_b2g_1_1_hd=---&amp;cf_status_b2g_1_2=---&amp;cf_status_firefox24=---&amp;cf_status_firefox25=---&amp;cf_status_firefox26=---&amp;cf_status_firefox27=---&amp;cf_status_firefox_esr17=---&amp;cf_status_firefox_esr24=---&amp;cf_tracking_b2g18=---&amp;cf_tracking_firefox24=---&amp;cf_tracking_firefox25=---&amp;cf_tracking_firefox26=---&amp;cf_tracking_firefox27=---&amp;cf_tracking_firefox_esr17=---&amp;cf_tracking_firefox_esr24=---&amp;cf_tracking_firefox_relnote=---&amp;cf_tracking_relnote_b2g=---&amp;comment=&amp;component=Developer%20Tools%3A%20App%20Manager&amp;contenttypeentry=&amp;contenttypemethod=autodetect&amp;contenttypeselection=text%2Fplain&amp;data=&amp;defined_groups=1&amp;dependson=&amp;description=&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-720=X&amp;flag_type-721=X&amp;flag_type-737=X&amp;flag_type-748=X&amp;flag_type-781=X&amp;flag_type-787=X&amp;flag_type-791=X&amp;flag_type-799=X&amp;flag_type-800=X&amp;flag_type-802=X&amp;flag_type-803=X&amp;flag_type-809=X&amp;flag_type-825=X&amp;form_name=enter_bug&amp;keywords=&amp;maketemplate=Remember%20values%20as%20bookmarkable%20template&amp;op_sys=All&amp;priority=--&amp;product=Firefox&amp;qa_contact=developer.tools%40firefox.bugs&amp;rep_platform=x86&amp;requestee_type-203=&amp;requestee_type-41=&amp;requestee_type-5=&amp;requestee_type-607=&amp;requestee_type-748=&amp;requestee_type-781=&amp;requestee_type-787=&amp;requestee_type-791=&amp;requestee_type-800=&amp;short_desc=&amp;status_whiteboard=&amp;target_milestone=---&amp;version=Trunk">file a bug</a> with the log output</li>
-    </ul>
-   </li>
-  </ul>
- </li>
- <li>See <strong>"???????"</strong> instead of the device name on Linux? You have permissions issues. <a href="http://developer.android.com/tools/device.html#setting-up">Make sure to setup udev correctly</a>.</li>
- <li>Is your phone screen unlocked?</li>
- <li>If the command "adb devices" shows no entries even though the phone is connected and unlocked, you may have to <a href="http://blog.fh-kaernten.at/wehr/?p=1182">edit adb_usb.ini</a>.</li>
-</ul>
-
-<p>Can't connect your device to the App Manager or start the simulator? <a href="https://wiki.mozilla.org/DevTools/GetInvolved#Communication">Let us know</a> or <a href="https://bugzilla.mozilla.org/enter_bug.cgi?alias=&amp;assigned_to=nobody%40mozilla.org&amp;attach_text=&amp;blocked=&amp;bug_file_loc=http%3A%2F%2F&amp;bug_ignored=0&amp;bug_severity=normal&amp;bug_status=NEW&amp;cf_blocking_b2g=---&amp;cf_crash_signature=&amp;cf_status_b2g18=---&amp;cf_status_b2g_1_1_hd=---&amp;cf_status_b2g_1_2=---&amp;cf_status_firefox24=---&amp;cf_status_firefox25=---&amp;cf_status_firefox26=---&amp;cf_status_firefox27=---&amp;cf_status_firefox_esr17=---&amp;cf_status_firefox_esr24=---&amp;cf_tracking_b2g18=---&amp;cf_tracking_firefox24=---&amp;cf_tracking_firefox25=---&amp;cf_tracking_firefox26=---&amp;cf_tracking_firefox27=---&amp;cf_tracking_firefox_esr17=---&amp;cf_tracking_firefox_esr24=---&amp;cf_tracking_firefox_relnote=---&amp;cf_tracking_relnote_b2g=---&amp;comment=&amp;component=Developer%20Tools%3A%20App%20Manager&amp;contenttypeentry=&amp;contenttypemethod=autodetect&amp;contenttypeselection=text%2Fplain&amp;data=&amp;defined_groups=1&amp;dependson=&amp;description=&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-720=X&amp;flag_type-721=X&amp;flag_type-737=X&amp;flag_type-748=X&amp;flag_type-781=X&amp;flag_type-787=X&amp;flag_type-791=X&amp;flag_type-799=X&amp;flag_type-800=X&amp;flag_type-802=X&amp;flag_type-803=X&amp;flag_type-809=X&amp;flag_type-825=X&amp;form_name=enter_bug&amp;keywords=&amp;maketemplate=Remember%20values%20as%20bookmarkable%20template&amp;op_sys=All&amp;priority=--&amp;product=Firefox&amp;qa_contact=developer.tools%40firefox.bugs&amp;rep_platform=x86&amp;requestee_type-203=&amp;requestee_type-41=&amp;requestee_type-5=&amp;requestee_type-607=&amp;requestee_type-748=&amp;requestee_type-781=&amp;requestee_type-787=&amp;requestee_type-791=&amp;requestee_type-800=&amp;short_desc=&amp;status_whiteboard=&amp;target_milestone=---&amp;version=Trunk">file a bug</a>. and</p>
diff --git a/files/hu/archive/index.html b/files/hu/archive/index.html
deleted file mode 100644
index 0b020071da..0000000000
--- a/files/hu/archive/index.html
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Archive of obsolete content
-slug: Archive
-translation_of: Archive
----
-<p>(hu translation)</p>
-
-<p>Here at MDN, we try to avoid outright deleting content that might be useful to people targeting legacy platforms, operating systems, and browsers. Perhaps your target audience is people that are using older hardware, for example, and can't upgrade to the latest and greatest browsers. Or for "reasons," your company is required to use very old software and you need to build Web content that runs on that software. Or perhaps you're just curious about the history of an obsolete feature or API, and how it worked.</p>
-
-<p>There are many reasons older documentation can be useful. So, we've established this area into which we can archive older documentation. Material in this Archived content zone should <strong>not</strong> be used for building new Web sites or apps for modern browsers. It's here for historical reference only.</p>
-
-<div class="note">
-<p><strong>Note to writers:</strong> We need to try to keep the subpages here organized instead of all dumped into one large folder. Try to create subtrees for categories of material. Also, only move pages here that are <strong>extremely</strong> obsolete. If anyone might realistically need the information in a living product, it may not be appropriate to move it here. In general, it may be best to discuss it in the <a href="https://chat.mozilla.org/#/room/#mdn:mozilla.org">MDN Web Docs chat room</a> before moving content here.</p>
-</div>
-
-<p>{{SubpagesWithSummaries}}</p>
-
-<h2 id="Subnav">Subnav</h2>
-
-<p>{{ListSubpages("/en-US/docs/Archive", 2, 0, 1)}}</p>
diff --git a/files/hu/kozossegi_api/index.html b/files/hu/kozossegi_api/index.html
deleted file mode 100644
index 7ad4528f11..0000000000
--- a/files/hu/kozossegi_api/index.html
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Közösségi API
-slug: Kozossegi_API
-translation_of: Archive/Social_API
----
-<p>A Közösségi API egy új API, hogy a webböngészőknek könnyebb legyen integrálni a közösségi média szolgáltatásokat. Amint egy közösségi szolgáltató bevezetésre kerül a Firefoxban, lehetővé válik a böngésző számára 'in-chrome' felhasználói vezérlők és a szolgáltatáshoz kapcsolodó információk megjelenítése. A következő cikkek leírják, hogyan vezessen be közösségi szolgáltatást.</p>
-<div class="note">
-  <p><strong>Megjegyzés:</strong> Az aloldalakon lévő tartalom többsége kidolgozott de még nincs átmigrálva ebbe a fastruktúrába; <a href="/en-US/docs/User:Sheppy/Social_API_temp" title="/en-US/docs/User:Sheppy/Social_API_temp">átmenetileg itt találhatja meg</a>.</p>
-</div>
-<div class="row topic-page">
-  <div class="section">
-    <h2 class="Documentation" id="Közösségi_API_dokumentáció">Közösségi API dokumentáció</h2>
-    <p>Ajánlás a közösségi szolgáltatás munkás API-hoz</p>
-    <p><a href="/en-US/docs/DOM/navigator.mozSocial" title="/en-US/docs/DOM/navigator.mozSocial">Közösségi szolgáltatás tartalom API: MozSocial</a></p>
-    <p>Ajánlás a közösségi szolgáltatás tartalom API-hoz, amelyet a  {{domxref("navigator.MozSocial")}} objektum nyújt.</p>
-    <p><a href="/en-US/docs/Social_API/Widgets" title="/en-US/docs/Social_API/Widgets">Közösségi szolgáltatás widgetek</a></p>
-    <p>Útmutató a közösségi szolgáltatás által nyújtott widgetekhez.</p>
-    <p><a href="/en-US/docs/Social_API/Implementing_chat_functionality" title="/en-US/docs/Social_API/Implementing_chat_functionality">Chat funkció megvalósítása</a></p>
-    <p>Útmutató a chat jellemzők megvalósításához a Közösségi API használatával</p>
-    <dl>
-      <dt>
-        <a href="/en-US/docs/Social_API/Glossary" title="/en-US/docs/Social_API/Glossary"><span id="cke_bm_71S" style="display: none;"> </span>Közösségi API szójegyzék</a><span id="cke_bm_71E" style="display: none;"> </span></dt>
-      <dd>
-        Provides definitions of key terms you'll need to understand when using the Social API.</dd>
-      <dt>
-        <a href="/en-US/docs/Social_API/Guide" title="/en-US/docs/Social_API/Guide">Közösségi API és közösségi szolgáltatás útmutató</a></dt>
-      <dd>
-        Bevezetés és útmutató a Közösségi API-hoz és a kapcsolodó szolgálgatásokhoz.</dd>
-      <dt>
-        <a href="/en-US/docs/Social_API/Manifest" title="/en-US/docs/Social_API/Manifest">Közösségi szolgáltatás jegyzék</a></dt>
-      <dd>
-        A jegyzék—(TBD: és útmutató az építéshez)—leírása szükséges.</dd>
-      <dt>
-        <a href="/en-US/docs/Social_API/Service_worker_API_reference" title="/en-US/docs/Social_API/Service_worker_reference">Közösségi szolgáltatás munkás API ajánlás</a></dt>
-    </dl>
-    <p><span class="alllinks"><a href="/en-US/docs/tag/Social" title="/en-US/docs/tag/CSS">Összes megtekintése....</a></span></p>
-  </div>
-  <div class="section">
-    <p class="Community">Segítség kérése a közösségtől</p>
-    <p>Segítségre van szüksége a Közösségi API-val összefüggő problémában és nem találja a megoldást a dokumentációban?</p>
-    <ul>
-      <li>
-        <p>Kérdezzen a Mozilla IRC csatornáján<br>
-          <a href="irc://irc.mozilla.org/socialdev" title="irc://irc.mozilla.org/socialdev">#socialdev</a></p>
-      </li>
-    </ul>
-    <p><span class="alllinks"><a class="external" href="http://www.catb.org/~esr/faqs/smart-questions.html" title="http://www.catb.org/~esr/faqs/smart-questions.html">Ne felejtse a netikettet...</a></span></p>
-    <p class="Tools"><strong>Eszközök és demók</strong></p>
-    <p><a href="https://github.com/mixedpuppy/socialapi-demo" title="https://github.com/mixedpuppy/socialapi-demo">Egy minta közösségi szolgáltatás a github</a>on.<br>
-      <a href="/en-US/docs/social_API_Devtools" title="/en-US/">Hogy használja a Firefox Fejlesztői Eszközeit a Közösségi API-val.</a></p>
-    <p><span class="alllinks"><a href="/en-US/docs/tag/Social" title="/en-US/docs/tag/CSS:Tools">Összes megtekintése...</a></span></p>
-    <h2 class="Related_Topics" id="Related_Topics" name="Related_Topics">Kapcsolodó témakörök</h2>
-    <p><a href="/en-US/docs/Apps" title="/en-US/docs/Apps">Webes alkalmazások megnyitása</a></p>
-  </div>
-</div>
-<p> </p>
diff --git a/files/hu/mozilla/bugzilla/index.html b/files/hu/mozilla/bugzilla/index.html
deleted file mode 100644
index f9a6703385..0000000000
--- a/files/hu/mozilla/bugzilla/index.html
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Bugzilla
-slug: Mozilla/Bugzilla
-tags:
-  - Bugzilla
-  - Developing Mozilla
-  - 'Developing_Mozilla:Tools'
-  - NeedsTranslation
-  - QA
-  - Tools
-  - TopicStub
-translation_of: Mozilla/Bugzilla
----
-<p><a class="link-https" href="https://bugzilla.mozilla.org/"><font><font>A</font></font></a><font><font> bugzilla.mozilla.org (gyakran rövidítve a bmo) a Mozilla.org hibakövetési rendszere, egy adatbázis a hibák rögzítésére és a Firefox, Thunderbird, SeaMonkey, Camino és más mozilla.org projektek fejlesztési kérelmeire.</font></font></p>
-
-<div class="row topicpage-table">
-<div class="section">
-<h2 class="Documentation" id="Documentation" name="Documentation"><font><font>Dokumentáció a Bmo-ról</font></font></h2>
-
-<dl>
- <dt><a href="/en-US/docs/What_to_do_and_what_not_to_do_in_Bugzilla" title="hu / What_to_do_and_what_not_to_do_in_Bugzilla"><font><font>Mit kell csinálni, és mit nem csinálni Bugzilában</font></font></a></dt>
- <dd><font><font>Tippek a Bugzilla használatához, valamint a kerülendő dolgok.</font></font></dd>
- <dt><a class="link-https" href="https://bugzilla.mozilla.org/page.cgi?id=etiquette.html"><font><font>Bugzilla-etikett</font></font></a></dt>
- <dd><font><font>Útmutató az etiketthez; </font><font>Ez az útmutató segít megérteni, hogyan lehet a legjobban viselkedni a bmo-n, és hogy a megfelelő viselkedés és az udvariasság használata elősegíti, hogy a problémád mielőbb, se később megoldódjon.</font></font></dd>
- <dt><a href="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html" title="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"><font><font>Hogyan tudom megtudni, ha hibát már jelentettek</font></font></a></dt>
- <dd><font><font>Hasznos (de nem kötelező), ha ellenőrizni szeretné, hogy a jelentett probléma már nyomon volt-e. </font><font>Ez az útmutató segít abban.</font></font></dd>
- <dt><a href="/en-US/docs/Mozilla/QA" title="/en-US/docs/Mozilla/QA"><font><font>Minőségbiztosítás</font></font></a></dt>
- <dd><font><font>Dokumentáció a Mozilla minőségbiztosításáról.</font></font></dd>
- <dt><a href="/en-US/docs/Mozilla/QA/Bug_writing_guidelines" title="/ En-US / docs / Mozilla / QA / Bug_writing_guidelines"><font><font>Hibaírási útmutató</font></font></a></dt>
- <dd><font><font>Útmutató egy jó, érthető hiba elkészítéséhez, amelyet a fejlesztői csapat könnyen követ.</font></font></dd>
- <dt><a href="/en-US/docs/Developer_Guide/How_to_Submit_a_Patch" title="/ En-US / docs / Developer_Guide / How_to_Submit_a_Patch"><font><font>Hogyan kell beküldeni a javítást</font></font></a></dt>
- <dd><font><font>Ha kijavított egy hibát, vagy új funkciót hajtott végre, akkor be kell helyeznie a javítást a fába, hogy ez a termék részévé váljon. </font><font>Ez az útmutató megtanítja, hogyan!</font></font></dd>
-</dl>
-
-<p><span class="alllinks"><a href="/en-US/docs/tag/Bugzilla" title="/ hu-Egyesült Államok / docs / tag / CSS"><font><font>Összes megtekintése...</font></font></a></span></p>
-</div>
-
-<div class="section">
-<h2 class="Community" id="Community" name="Community"><font><font>Segítség a közösségtől</font></font></h2>
-
-<p><font><font>Segítségre van szüksége egy CSS-rel kapcsolatos problémában, és nem talál megoldást a dokumentációban?</font></font></p>
-
-<ul>
- <li><font><font>Látogasson el a </font></font><a href="https://wiki.mozilla.org/BMO/Support" title="https://wiki.mozilla.org/BMO/Support"><font><font>bmo támogatási oldalra</font></font></a><font><font> .</font></font></li>
- <li><font><font>Tegye fel kérdését a Mozilla IRC csatornán: </font></font><a class="link-irc" href="irc://irc.mozilla.org/qa"><font><font>#qa</font></font></a></li>
-</ul>
-
-<p><span class="alllinks"><a class="external" href="http://www.catb.org/~esr/faqs/smart-questions.html" title="http://www.catb.org/~esr/faqs/smart-questions.html"><font><font>Ne felejtsd el a </font></font><em><font><font>nettikettet</font></font></em><font><font> ...</font></font></a></span></p>
-
-<h2 class="Related_Topics" id="Related_Topics" name="Related_Topics"><font><font>Más anyagok</font></font></h2>
-
-<ul>
- <li><a class="external" href="http://www.bugzilla.org/about/"><font><font>Bevezetés a Bugzillába</font></font></a></li>
- <li><a class="external" href="http://blog.johnath.com/2010/02/04/bugzilla-for-humans"><font><font>Bugzilla ember számára</font></font></a></li>
- <li><a class="external" href="http://www.squarefree.com/bugzilla/quicksearch-help.html"><font><font>A Bugzilla QuickSearch súgó oldala</font></font></a><font><font> . </font><font>A QuickSearch gyors, egyszerű és nagyon hatékony módszer a bugzilla gyors lekérdezésére.</font></font></li>
- <li><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Bugzilla/Testopia" title="https://developer.mozilla.org/en-US/docs/Mozilla/Bugzilla/Testopia"><font><font>Testopia</font></font></a><font><font> - teszt esetkezelési kiterjesztés</font></font></li>
- <li><a class="external" href="http://www.bugzilla.org"><font><font>bugzilla.org</font></font></a><font><font> - a projekt oldala</font></font></li>
- <li><font><font>{{interwiki ('wikipedia', 'Bugzilla', 'wikipedia: Bugzilla')}} - a Bugzilla általános leírása (nem vonatkozik a Mozilla projektekre)</font></font></li>
-</ul>
-
-<h2 class="Tools" id="Tools" name="Tools"><font><font>Eszközök</font></font></h2>
-
-<ul>
- <li><a href="http://harthur.github.io/bugzilla-todos/" title="http://harthur.github.io/bugzilla-todos/"><font><font>A Bugzilla Todos</font></font></a><font><font> felsorolja az áttekintési és megjelölési kérelmeket, a bejelentkezési javításokat, a másoktól nem teljesített kéréseket és a hozzárendelt hibákat.</font></font></li>
-</ul>
-</div>
-</div>
diff --git a/files/hu/mozilla/gecko/index.html b/files/hu/mozilla/gecko/index.html
deleted file mode 100644
index fee760a09e..0000000000
--- a/files/hu/mozilla/gecko/index.html
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Gecko
-slug: Mozilla/Gecko
-tags:
-  - Gecko
-  - Mozilla
-translation_of: Mozilla/Gecko
----
-<div>{{FirefoxSidebar}}</div>
-
-<p class="summary"><span class="seoSummary">A <strong>Gecko</strong> a Mozilla Projekt keretében fejlesztett böngészőmotor. Az eredeti neve NGLayout volt. A Gecko feladata a webes tartalom (például <a href="/hu/docs/HTML">HTML</a>, <a href="/hu/docs/CSS">CSS</a>, <a href="/hu/docs/XUL">XUL</a> és <a href="/hu/docs/JavaScript">JavaScript</a>) feldolgozása és megjelenítése a felhasználó képernyőjén vagy nyomtatásban. A XUL-alapú alkalmazásokban a Gecko felel az alkalmazás felhasználói felületének megjelenítéséért is.</span></p>
-
-<p>A Geckót számos alkalmazásban használják, többek között néhány böngészőben, pl. a Firefox és a SeaMonkeyban is (teljesebb listát lásd a <a class="external" href="https://hu.wikipedia.org/wiki/Gecko#Webb%C3%B6ng%C3%A9sz%C5%91k" rel="external">Wikipédia Geckóról szóló szócikkében</a>). A Gecko azonos verzióját használó termékek azonos mértékben támogatják a webes sztenderdeket.</p>
-
-<table class="topicpage-table">
- <tbody>
-  <tr>
-   <td>
-    <h2 id="Dokumentáció">Dokumentáció</h2>
-
-    <dl>
-     <dt><a href="/hu/docs/Mozilla/Gecko/Chrome">Chrome</a></dt>
-     <dd>This page contains information specific to browser chrome (not Google Chrome) code running in Gecko.</dd>
-     <dt><a href="/hu/docs/Gecko_FAQ">Gecko GYIK</a></dt>
-     <dd>Gyakran ismételt kérdések a Geckóról.</dd>
-     <dt><a href="/hu/docs/Gecko_DOM_Reference">Gecko DOM referencia</a></dt>
-     <dd>A DOM referenciaszintű leírása.</dd>
-     <dt><a href="/hu/docs/Gecko-Specific_DOM_Events">Gecko-esemény-referencia</a></dt>
-     <dd>Referencia a Geckóban és Mozilla-alkalmazásokban használt eseményekről; a webes sztenderdek által meghatározott DOM-eseményekhez lásd a <a href="/hu/docs/DOM/DOM_event_reference">DOM-esemény-referenciát</a>.</dd>
-     <dt><a href="/hu/docs/Gecko/Versions">Gecko- és alkalmazásverziók</a></dt>
-     <dd>A Gecko verziói és az azokat használó alkalmazások.</dd>
-     <dt><a href="/hu/docs/Introduction_to_Layout_in_Mozilla">Bevezetés a megjelenésbe a Mozillában</a></dt>
-     <dd>Tech Talk on layout.</dd>
-     <dt><a href="/hu/docs/Embedding_Mozilla">Mozilla beágyazása</a></dt>
-     <dd>A Gecko használata saját alkalmazásban.</dd>
-     <dt><a href="/hu/docs/Character_Sets_Supported_by_Gecko">A Gecko által támogatott karakterkészletek</a></dt>
-     <dd>A Gecko által támogatott karakterkészletek listája.</dd>
-     <dt><a href="/hu/docs/Gecko/HTML_parser_threading" title="Gecko/HTML_parser_threading">Többszálú HTML-feldolgozás</a></dt>
-     <dd>A HTML-feldolgozó többszálú működésének leírása.</dd>
-     <dt>{{interwiki('wikimo', 'Gecko:Home_Page', 'Gecko-kezdőlap a MozillaWikiben')}}</dt>
-     <dd>Home for the active developers. Roadmaps and more up-to-date resources.</dd>
-    </dl>
-
-    <p><span class="alllinks"><a href="/hu/docs/tag/Gecko">Minden kapcsolódó dokumentáció megjelenítése</a></span></p>
-   </td>
-   <td>
-    <h2 id="Közösség">Közösség</h2>
-
-    <ul>
-     <li>Mozilla-fórumok: {{DiscussionList("dev-tech-layout", "mozilla.dev.tech.layout")}}</li>
-    </ul>
-
-    <h2 id="Kapcsolódó_témák">Kapcsolódó témák</h2>
-
-    <ul>
-     <li><a href="/hu/docs/Web_Standards">Webes sztenderdek</a></li>
-     <li><a href="/hu/docs/XUL">XUL</a></li>
-     <li><a href="/hu/docs/Embedding_Mozilla">Mozilla beágyazása</a></li>
-     <li><a href="/hu/docs/Developer_Guide">Mozilla-fejlesztés</a></li>
-    </ul>
-   </td>
-  </tr>
- </tbody>
-</table>
diff --git a/files/hu/zones/index.html b/files/hu/zones/index.html
deleted file mode 100644
index 4fb47ab48c..0000000000
--- a/files/hu/zones/index.html
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Zones
-slug: Zones
-translation_of: Zones
----
-<p><font><font>MDN zónák az Ön egyablakos információkhoz való hozzáférést meghatározott témakörökben vagy termékeket. </font><font>Itt egy lista az összes zóna áll az Ön rendelkezésére.</font></font></p>
-<div class="row topicpage-table">
- <div class="section">
-  <h2 id="Web_és_alkalmazás_fejlesztés"><font><font>Web és alkalmazás fejlesztés</font></font></h2>
-  <dl>
-   <dt>
-    <a href="/en-US/Apps"><font><font>App Center</font></font></a></dt>
-   <dd>
-    <font><font>Megtanulják, hogyan kell létrehozni a nyílt webes alkalmazások gazdag tapasztalatokat, hogy halad át több eszköz és forma tényező, ugyanazt a webes szabványok és a nyílt technológiák már tudod.</font></font></dd>
-   <dt>
-    <a href="/en-US/docs/Tools"><font><font>Fejlesztői eszközök</font></font></a></dt>
-   <dd>
-    <font><font>Ismerje meg, hogyan kell használni a Firefox fejlesztői eszközöket, hogy hibakeresés, teszt, és optimalizálja a webes alkalmazások és a webhelyek.</font></font></dd>
-   <dt>
-    <a href="/en-US/Marketplace"><font><font>Firefox Marketplace</font></font></a></dt>
-   <dd>
-    <font><font>Egy nyílt, nem védett internetes piactér webes alkalmazások HTML, CSS, JavaScript és. </font><font>Küldje el az alkalmazások számára, a Firefox Marketplace, vagy használja a kódot, hogy a saját piacán.</font></font></dd>
-   <dt>
-    <a href="/en-US/docs/Games"><font><font>Játék fejlesztés</font></font></a></dt>
-   <dd>
-    <font><font>Ismerje meg, hogyan lehet fejleszteni játékok az interneten, hogyan lehet a meglévő kikötő játékok webes technológiákat, és hogyan kapcsolja be a játék a webes alkalmazások.</font></font></dd>
-   <dt>
-    <a href="/en-US/docs/Mozilla/Developer_Program"><font><font>Mozilla Developer Program</font></font></a></dt>
-   <dd>
-    <font><font>Tudjon meg többet a Mozilla Developer Program, ahol akkor iratkozzon fel a tagság a programban, iratkozzon fel hírlevelünkre, és elérheti a növekvő sor z webfejlesztőknek.</font></font></dd>
-  </dl>
- </div>
- <div class="section">
-  <h2 id="Products" name="Products"><font><font>Termékek és projektek</font></font></h2>
-  <dl>
-   <dt>
-    <a href="/en-US/docs/Emscripten"><font><font>Emscripten</font></font></a></dt>
-   <dd>
-    <font><font>Egy LLVM JavaScript fordító; </font><font>ez lehetővé teszi, hogy lefordítani, például a C ++ kódot JavaScript kódot, amely lehet futtatni bármely webböngészőben.</font></font></dd>
-   <dt>
-    <a href="/en-US/docs/L20n"><font><font>L20n</font></font></a></dt>
-   <dd>
-    <font><font>A JavaScript lokalizáció keretrendszer kibontakoztatásához a természetes nyelv erejét egyszerű kódot.</font></font></dd>
-   <dt>
-    <a href="/en-US/docs/Project:MDN"><font><font>A projekt MDN</font></font></a></dt>
-   <dd>
-    <font><font>A Mozilla Developer Network (ezen az oldalon) támaszkodik közössége az olvasók és a közreműködők növekedni és fejlődni. </font><font>Meg lehet tanulni, hogyan kell segíteni itt, használat, hozzájárulnak, és épít a kód mögött MDN! 1</font></font></dd>
-   <dt>
-    <a href="/en-US/Persona"><font><font>Személy</font></font></a></dt>
-   <dd>
-    <font><font>Egy új, egyszerű, magánjellegű single-megjelölés által kifejlesztett Mozilla amely lehetővé teszi a felhasználók jelentkezzen be a webhely használatával az e-mail címét, megkímélve a felhasználót jelszó kezelése.</font></font></dd>
-  </dl>
-  <h2 id="Mozilla_technológiák"><font><font>Mozilla technológiák</font></font></h2>
-  <dl>
-   <dt>
-    <a href="/en-US/Add-ons"><font><font>Kiegészítőket</font></font></a></dt>
-   <dd>
-    <font><font>Megtanulják, hogyan kell építeni és telepíteni bővítményeket, témákat, és plug-inek Mozilla-alapú szoftver, köztük a népszerű Firefox böngésző.</font></font></dd>
-   <dt>
-    <a href="/en-US/Firefox"><font><font>Firefox</font></font></a></dt>
-   <dd>
-    <font><font>Tudjon meg mindent a Firefox, a hogyan építeni, és felülvizsgálja, hogyan kell építeni kiegészítőket kifejezetten azt.</font></font></dd>
-   <dt>
-    <a href="/en-US/Firefox_OS"><font><font>Firefox OS</font></font></a></dt>
-   <dd>
-    <font><font>Az új mobil operációs rendszer által kifejlesztett Mozilla amely lehetővé teszi a felhasználók telepíteni és futtatni a nyílt webes alkalmazások segítségével létrehozott HTML, CSS, JavaScript és.</font></font></dd>
-  </dl>
- </div>
-</div>
-<p> </p>