initial commit

25 files changed, 3643 insertions, 0 deletions

diff --git a/files/zh-tw/mdn/about/index.html b/files/zh-tw/mdn/about/index.html
new file mode 100644
index 0000000000..9f32937bb2
--- /dev/null
+++ b/files/zh-tw/mdn/about/index.html
@@ -0,0 +1,104 @@
+---
+title: 關於 MDN
+slug: MDN/About
+tags:
+  - 指引
+  - 文檔
+  - 版權
+  - 社群
+translation_of: MDN/About
+---
+<div>{{MDNSidebar}}</div>
+
+<div>{{IncludeSubNav("/zh-TW/docs/MDN")}}</div>
+
+<p>MDN Web Docs 是個針對網路技術和基於網路的軟體，持續發展的學習平台。它包含了：</p>
+
+<ul>
+ <li>諸如 <a href="/zh-TW/docs/CSS" title="/zh-TW/docs/CSS">CSS</a>、<a href="/zh-TW/docs/HTML" title="/zh-TW/docs/HTML">HTML</a>、<a href="/zh-TW/docs/JavaScript" title="/zh-TW/docs/JavaScript">JavaScript</a> 的網路標準</li>
+ <li><a href="/zh-TW/docs/Apps" title="/zh-TW/docs/Apps">Open Web app 開發</a></li>
+ <li><a href="/zh-TW/docs/Add-ons" title="/zh-TW/docs/Add-ons">Firefox 附加元件開發</a></li>
+</ul>
+
+<h2 id="我們的使命">我們的使命</h2>
+
+<p>MDN 的使命非常簡單：提供開發者在<a href="/zh-TW/docs/Web">開放網站</a>上輕鬆地建立各種專案所需的資訊。只要有一個網路上開放的技術，我們就希望把它寫成文件。</p>
+
+<p>除此之外，我們提供有關 <a href="/zh-TW/docs/Mozilla">Mozilla 產品</a>和如何<a href="/zh-TW/docs/Mozilla">建置與貢獻 Mozilla 專案</a>的方法。另外也涵蓋了 <a href="/zh-TW/docs/Mozilla/B2G_OS">B2G OS</a>（以前叫做 Firefox OS）的文件。</p>
+
+<p>如果你不知道一個特定的主題適不適合出現在 MDN 上，請參閱：<a href="/zh-TW/docs/Project:MDN/Contributing/Does_this_belong">Does this belong on MDN?</a>。</p>
+
+<h2 id="如何幫忙">如何幫忙</h2>
+
+<p>想要幫忙 MDN 更加完善，你不需要寫得一手很好的程式碼！你可以透過很多種方式幫忙我們，從檢查文件是否合理、到隨手增添一些文字或是範例程式碼都行。根據你的興趣和時間，你可以到<a href="/zh-TW/docs/MDN/Getting_started">開始入門 MDN</a> 頁面看看有幾種方法可以幫忙我們。</p>
+
+<p>你也可以在你自己的部落格或網站上<a href="/zh-TW/docs/MDN/About/Promote">推廣 MDN</a>。</p>
+
+<h2 id="MDN_社群">MDN 社群</h2>
+
+<p>我們的社群是個地球村！我們傑出的貢獻者遍布全世界、涵蓋各種語言。如果你想更認識我們、或是需要任何幫忙，隨時歡迎你到我們的<a href="https://discourse.mozilla-community.org/c/mdn">討論區</a>或 <a href="irc://irc.mozilla.org#mdn">IRC 頻道</a>！你也可以追蹤我們的 Twitter 帳號「<a href="http://twitter.com/MozDevNet">@MozDevNet</a>」獲得最新消息。如果你發現任何錯誤、或是你有任何話想跟我們說，都歡迎你發送推文給我們的作者和貢獻者！</p>
+
+<h2 id="使用_MDN_的內容">使用 MDN 的內容</h2>
+
+<h3 id="著作權授權">著作權授權</h3>
+
+<p><strong>MDN wiki 文件</strong> 是許多 Mozilla 基金會內外作者的心血結晶。除另有註明，所有內容皆採用<a class="external text" href="http://creativecommons.org/licenses/by-sa/2.5/" rel="nofollow" title="http://creativecommons.org/licenses/by-sa/2.5/">創用CC 姓名標示-相同方式分享</a>授權條款（CC BY-SA）的第 2.5 版或任何更新的版本釋出。在引用內容時請務必標示作者為「Mozilla Contributors」、並附上該篇 wiki 的超連結或印出網址。你可以標示如下：</p>
+
+<blockquote><a href="https://developer.mozilla.org/zh-TW/docs/MDN/About">關於 MDN</a> 由 <a href="https://developer.mozilla.org/zh-TW/docs/MDN/About$history">Mozilla Contributors</a> 製作，以 <a href="http://creativecommons.org/licenses/by-sa/2.5/">CC-BY-SA 2.5</a> 釋出。</blockquote>
+
+<p>請注意在以上範例中，「Mozilla Contributors」連結到該頁面的編輯歷史。參閱 <a href="http://wiki.creativecommons.org/Marking/Users">Best practices for attribution</a> 獲得更多資訊。</p>
+
+<div class="note">
+<p>參閱 <a href="/zh-TW/docs/MDN_content_on_WebPlatform.org" title="/zh-TW/docs/MDN_content_on_WebPlatform.org">MDN content on WebPlatform.org</a> 了解更多有關如何在網站上使用和標註 MDN 內容的資訊。</p>
+</div>
+
+<p>在 2010 年 8 月 20 日以前新增到這個 wiki 的範例程式碼，是採用 <a class="external" href="http://www.opensource.org/licenses/mit-license.php" title="http://www.opensource.org/licenses/mit-license.php">MIT 授權條款</a>釋出。你應該在 MIT 模板中增加這些作者資訊：「© &lt;最新的 wiki 更新日期&gt; &lt;寫下這段程式碼的人&gt;」</p>
+
+<p>在 2010 年 8 月 20 日（含）以後新增到這個 wiki 的範例程式碼，是採用 <a class="external" href="http://creativecommons.org/publicdomain/zero/1.0/" title="http://wiki.creativecommons.org/Public_domain">公有領域</a>授權。你不需要註明任何授權文字。不過你要的話，可以註明：「Any copyright is dedicated to the Public Domain. http://creativecommons.org/publicdomain/zero/1.0/」</p>
+
+<p>如果你希望貢獻到這個 wiki，你必須讓你的文件採用姓名標示-相同方式分享（或是你正在編輯的頁面上已經指定好的其他替代授權），同時你的程式碼必須採用<a href="http://creativecommons.org/publicdomain/zero/1.0/" title="http://creativecommons.org/publicdomain/zero/1.0/">Creative Commons CC-0</a>（公有領域）授權。在你編輯這個 wiki 的同時即表示你同意採用這些授權。</p>
+
+<p>有些比較舊的內容可能會採用和上述不同的授權條款。這些授權條款都會在每個頁面最下方透過 <a class="internal" href="/Archive/Meta_docs/Examples/Alternate_License_Block" title="Project:En/Examples/Alternate License Block">Alternate License Block</a> 列明。</p>
+
+<div class="warning">
+<p>新建立的頁面不得使用替代的授權條款。</p>
+</div>
+
+<p><strong>除非作者另有聲明，否則所有貢獻素材的版權皆歸屬其作者所有</strong>。</p>
+
+<p>如果你對這裡提到的內容有任何問題或疑慮，請聯絡 <a class="external" href="mailto:eshepherd@mozilla.com" rel="nofollow" title="mailto:eshepherd@mozilla.com">Eric Shepherd</a>。</p>
+
+<hr>
+<p>Mozilla 基金會的商標、Logo、服務標誌，以及這個網站的風格外觀，皆不屬於創用 CC 授權的範圍。它們是其原作者的作品（例如 Logo 和圖形設計），不包含在上述的授權條款中。如果你使用文件中的文字、並同時希望使用以上任一權利，或者你對於遵守我們的授權條款有任何的問題，你應該聯絡 Moziila 基金會：<a class="external text" href="mailto:licensing@mozilla.org" rel="nofollow" title="mailto:licensing@mozilla.org">licensing@mozilla.org</a>。</p>
+
+<h3 id="下載內容">下載內容</h3>
+
+<p>你可以下載 <a href="/media/developer.mozilla.org.tar.gz">MDN 的完整鏡像檔案</a>（2016-11-30 時約為 2.5GB）。</p>
+
+<h4 id="單一頁面">單一頁面</h4>
+
+<p>你可以透過在網址增加<a href="/zh-TW/docs/MDN/Kuma/API#Document_parameters">文件參數</a>指定想要的格式，取得單一頁面的內容。</p>
+
+<h4 id="第三方工具">第三方工具</h4>
+
+<p>你可以透過第三方工具來閱覽 MDN，例如 <a href="http://kapeli.com/dash">Dash</a>（Mac OS 用）和 <a href="http://zealdocs.org/">Zeal</a>（Linux 和 Windows用）。</p>
+
+<p><a href="https://kapeli.com/">Kapeli</a> 也發布了<a href="https://kapeli.com/mdn_offline">離線 MDN docs</a> 涵蓋 HTML、CSS、JavaScript、SVG 和 XSLT。</p>
+
+<h3 id="連結到_MDN">連結到 MDN</h3>
+
+<p>請參閱 <a href="/zh-TW/docs/MDN/About/Linking_to_MDN">linking to MDN</a> 文內的指導，了解連結文件的最佳做法。</p>
+
+<h2 id="向_MDN_報告問題">向 MDN 報告問題</h2>
+
+<p>請參閱 <a href="/zh-TW/docs/MDN/Contribute/Howto/Report_a_problem">How to report a problem on MDN</a>。</p>
+
+<h2 id="MDN_網頁文檔歷史">MDN 網頁文檔歷史</h2>
+
+<p>MDN Web Docs（前身為<em>Mozilla Developer Network (MDN)</em>，更前身為 Mozilla Developer Center (MDC) 或 <em>Devmo</em>）專案始於 2005 年初，<a class="external" href="http://www.mozillafoundation.org">Mozilla 基金會</a>從 AOL 得到了原始的 Netscape <a href="https://web.archive.org/web/*/devedge.netscape.com" title="Project:en/DevEdge">DevEdge</a> 授權。DevEdge 內容仍被視為可用，之後由志願者合併到今天的這個 wiki 以便日後的更新與維護。</p>
+
+<p>你可以從我們的<a href="/zh-TW/docs/MDN_at_ten">十週年慶祝</a>頁面看到更多 MDN 的歷史，包含一些參與者的口述歷史。</p>
+
+<h2 id="關於_Mozilla">關於 Mozilla</h2>
+
+<p>無論你是想更認識我們、了解如何成為 <em>Mozilla</em> 的一份子，又或是單純想找我們聊天，那你都來對地方了。想知道是什麼驅使我們、讓我們更加與眾不同，請造訪我們的<a href="http://www.mozilla.org/zh-TW/mission/">使命</a>一頁。</p>
diff --git a/files/zh-tw/mdn/community/index.html b/files/zh-tw/mdn/community/index.html
new file mode 100644
index 0000000000..3c6fcda1a2
--- /dev/null
+++ b/files/zh-tw/mdn/community/index.html
@@ -0,0 +1,52 @@
+---
+title: 加入 MDN 社群
+slug: MDN/Community
+tags:
+  - 教學
+  - 社群
+translation_of: MDN/Community
+---
+<div>{{MDNSidebar}}</div>
+
+<div>{{IncludeSubnav("/zh-TW/docs/MDN")}}</div>
+
+<div class="summary">
+<p>MDN (Mozilla Developer Network 的縮寫) 比 wiki 更強大： 它是一個屬於開發者們的社群，致力於讓 MDN 這個龐大資源更加傑出。</p>
+</div>
+
+<p>我們非常感謝您對 MDN 的貢獻，但是我們更希望您加入我們的社群，這裡有三個加入我們社群的方法：</p>
+
+<ol>
+ <li><a href="/zh-TW/docs/MDN/Contribute/Howto/Create_an_MDN_account">建立 MDN 帳戶</a></li>
+ <li><a href="/zh-TW/docs/MDN/Community/論壇">加入會談</a></li>
+ <li><a href="/zh-TW/docs/MDN/Community/Whats_happening">追蹤新資訊</a></li>
+</ol>
+
+<h2 id="社群如何運作">社群如何運作</h2>
+
+<p>以下更多文章關於更多 MDN 的社群。</p>
+
+<div class="row topicpage-table">
+<div class="section">
+<dl>
+ <dt class="landingPageList"><a href="/zh-TW/docs/MDN/Community/Roles">社群角色</a></dt>
+ <dd class="landingPageList">在MDN社群中，有著許多負責不同部分的角色。</dd>
+ <dt class="landingPageList"><a href="/zh-TW/docs/MDN/Community/Doc_sprints">文件生成聚會</a></dt>
+ <dd class="landingPageList">這是一個文件生成聚會的指南。它包含了過去人們舉辦文件生成聚會所提供的一些建議與訣竅，以幫助你也舉辦一個。</dd>
+ <dt class="landingPageList"><a href="/zh-TW/docs/MDN/Community/Whats_happening">追蹤新資訊</a></dt>
+ <dd class="landingPageList">MDN 是由 <a class="external" href="https://wiki.mozilla.org/MDN">Mozilla Developer Network community</a> 所維護。 這裡有一些我們分享我們在做什麼的資訊管道。</dd>
+</dl>
+
+<dl>
+</dl>
+</div>
+
+<div class="section">
+<dl>
+ <dt class="landingPageList"><a href="/zh-TW/docs/MDN/Community/Conversations">MDN社群會議</a></dt>
+ <dd class="landingPageList">許多的社群工作都發生在MDN上，然而社群工作也同時發生在一些 討論(非即時性) 與 線上聊天或會議(即時性)中。</dd>
+ <dt class="landingPageList"><a href="/zh-TW/docs/MDN/Community/Working_in_community">與社群一同工作</a></dt>
+ <dd class="landingPageList">絕大部分相當程度對於MDN文件的貢獻來自於了解如何與社群一同工作。這份文章提供一些訣竅以幫助你與其他文件生成者及開發團隊交流。</dd>
+</dl>
+</div>
+</div>
diff --git a/files/zh-tw/mdn/community/論壇/index.html b/files/zh-tw/mdn/community/論壇/index.html
new file mode 100644
index 0000000000..955d241ece
--- /dev/null
+++ b/files/zh-tw/mdn/community/論壇/index.html
@@ -0,0 +1,53 @@
+---
+title: MDN的社群論壇
+slug: MDN/Community/論壇
+tags:
+  - MDN 資料
+  - 指南
+  - 社群論壇
+translation_of: MDN/Community/Conversations
+---
+<div>{{MDNSidebar}}</div>
+
+<div>MDN的『 工作 』通常在MDN的網頁上，但『社群』也會透過異步討論(Asynchronous discussions)，及同步線上討論或會議(Synchronous chat)進行。</div>
+
+<h2 id="異步討論_Asynchronous_discussions">異步討論 Asynchronous discussions</h2>
+
+<p>為了分享資訊及持續的溝通，MDN在Mozilla論壇中有獨立的類別(<a href="https://discourse.mozilla.org/c/mdn/zh-TW/docs/">"MDN"</a>)，這個類別連結所有與MDN相關的主題，包括文檔內容的創建，翻譯和維護； MDN平台開發；以及計劃，目標設定和進度跟踪。</p>
+
+<ul>
+ <li>為了加入To join Mozilla's Discourse, see <a href="https://discourse.mozilla-community.org/t/signing-up-and-logging-in/16017">Signing up and logging in</a>; if you have a Mozilla LDAP account, you can use that instead of "Login with email".</li>
+ <li>To subscribe to the MDN category, see <a href="https://discourse.mozilla-community.org/t/subscribing-to-categories-and-topics/16024">Subscribing to categories and topics</a>.</li>
+ <li>(Optional) If you prefer to interact with Discourse primarily by email, see <a href="https://discourse.mozilla-community.org/t/mailman-mode/15279">Set up a mailing list experience for yourself</a>. You can start a discussion in Discourse by sending an email message to: <a href="mailto://mdn@mozilla-community.org">mdn@mozilla-community.org</a>. If you use Discourse via email, you can reply to a message by replying to the notification email that you receive. If you want to intersperse comments inline within a reply, please put two carriage-returns before and after your inline chunks, so that Discourse parses them correctly.</li>
+</ul>
+
+<h3 id="歷史檔案館"><a href="https://www.books.com.tw/products/0010621631">歷史檔案館</a></h3>
+
+<p>Prior to June 2017, MDN-related discussions took place in mailings lists that were gatewayed and archived with Google groups. If you want to search these past discussions, you can look at the Google groups corresponding to the old mailing lists. (Yes, we know these names are overlapping and confusing. Historical accident. Sorry about that.)</p>
+
+<dl>
+ <dt><a href="https://groups.google.com/forum/#!forum/mozilla.dev.mdc">mozilla.dev.mdc</a> a.k.a. <strong>dev-mdc</strong></dt>
+ <dd>This list was for discussions about documentation content on MDN.</dd>
+ <dt><a href="https://groups.google.com/forum/#!forum/mozilla.dev.mdn">mozilla.dev.mdn </a>a.k.a. <strong>dev-mdn</strong></dt>
+ <dd>This list was about the development work on MDN's underlying <a href="/en-US/docs/Project:MDN/Kuma">Kuma</a> platform.</dd>
+ <dt><a href="https://groups.google.com/forum/#!forum/mozilla.mdn">mozilla.mdn </a>a.k.a. <strong>mdn@</strong></dt>
+ <dd>This forum was for high-level planning and prioritization discussions, for the MDN website and other related initiatives.</dd>
+</dl>
+
+<h2 id="同步討論（Synchronous_chat）">同步討論（Synchronous chat）</h2>
+
+<p>Mozilla's platform for real-time discussions is <a href="https://matrix.org/">Matrix</a>, a chat protocol for which <a href="https://chat.mozilla.org/">Mozilla has its own server</a>.</p>
+
+<p>The <a href="https://chat.mozilla.org/#/room/#mdn:mozilla.org">MDN Web docs chat room</a> is a major channel for discussing the content of MDN. We talk about writing, organization of content, and so on. We also have "water cooler" conversations here—it's a way our community can keep in touch and just hang out. This room is most likely to be active during weekdays in North America and Europe.</p>
+
+<p>You might want to learn more about using <a href="https://wiki.mozilla.org/Matrix">Matrix with Mozilla</a>, and, if you're really into it, install a stand-alone Matrix application such as <a href="https://about.riot.im/">Riot.im</a>.</p>
+
+<h3 id="IRC？"> IRC？</h3>
+
+<p>For many years, Mozilla used Internet Relay Chat (IRC) for real-time discussions. As of early 2020, IRC has been deprecated in favor of Matrix. You may see references to IRC channels in many places, including on MDN. You can help by updating links to IRC channels that you find on MDN to point to the corresponding Matrix rooms instead. If you're not sure what the Matrix room is for a topic, ask in the <a href="https://chat.mozilla.org/#/room/#general:mozilla.org">General</a> room. Projects or topics that are no longer active might not have a Matrix room; in such cases, just delete the link.</p>
+
+<h2 id="參與我們的會議_或其他活動">參與我們的會議 (或其他活動)</h2>
+
+<p>MDN團隊舉辦了許多對MDN社群開放的常規會議，請參閱Mozilla wiki上的<a href="https://wiki.mozilla.org/MDN/Meetings">MDN Meetings</a>頁面，可以獲取日程、議程、註釋相關以及如何加入的訊息。</p>
+
+<p>有關這些會議及其他會議，當地聚會和其他活動，可參閱<a href="https://www.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530%40resource.calendar.google.com">MDN 活動日曆</a>。定期會議會呈現在<a href="https://wiki.mozilla.org/MDN/Meetings">MDN Meetings wiki page</a>。</p>
diff --git a/files/zh-tw/mdn/contribute/getting_started/index.html b/files/zh-tw/mdn/contribute/getting_started/index.html
new file mode 100644
index 0000000000..4218ba895c
--- /dev/null
+++ b/files/zh-tw/mdn/contribute/getting_started/index.html
@@ -0,0 +1,105 @@
+---
+title: 開始入門 MDN
+slug: MDN/Contribute/Getting_started
+tags:
+  - Beginner
+  - Getting Started
+  - Guide
+  - MDN Meta
+  - 入門
+translation_of: MDN/Contribute/Getting_started
+---
+<div>{{MDNSidebar}}{{IncludeSubnav("/zh-TW/docs/MDN")}}</div>
+
+<p>這是一個開放的開發者和作家社區，不分品牌、瀏覽器、平台，為更好的 Web 構建提供更多資源。每個人都能做出貢獻，而每個貢獻者的付出都讓我們變得更為壯大。<span class="ordinary-span-edit">要想持續推動 Web 創新、成就更為偉大的事物？就讓我們和您一起，從這裡開始。</span></p>
+
+<p>MDN 上的每一個部分（網站本身的程式、文件、程式範例、效果展示等等）都是由一群開發者及文案編輯組成的社群完成。術業有專攻，您也一定有些妙招可以分享，請加入我們！</p>
+
+<h2 id="MDN_三步驟快速上手"><span>MDN 三步驟快速上手</span></h2>
+
+<p><span class="seoSummary">MDN 是一個 wiki，<strong>每個人</strong>都可以添加、編撰內容。您不必得是個了解許多技術的程式設計師才能加入，畢竟總有各種事情需要完成，從簡單如校對與糾正拼寫，到複雜如撰寫 API 文件都有。這個導向將引導您開始和幫助您找到可以幫助提升 MDN 内容的方法。</span></p>
+
+<p>加入貢獻非常容易，且即使您不慎犯了錯誤，也很容易修正。就算您不知道文件該怎麼編排，或者不太了解語法，也不用煩惱：我們有一群人就是專門努力巡視四周、盡力確保 MDN 上的內容優質依舊；有人會盡力編輯您的貢獻確保文件格式正確。放膽分享您的所學吧，並相信整個社群能幫您做得更好。</p>
+
+<h3 id="步驟_1：建立_MDN_帳號">步驟 1：建立 MDN 帳號</h3>
+
+<p>加入貢獻的第一步是要有 MDN 帳號，請參考<a href="/docs/MDN/Contribute/Howto/Create_an_MDN_account">建立帳號說明</a>。注意，在建立 MDN 帳號之前，您需要有一個 <a href="https://github.com/join">GitHub帳號</a>，因為我們已經使用 GitHub 作為登入驗證。</p>
+
+<p>如果你想創建一個新的頁面，請參考{{SectionOnPage("/zh-TW/docs/MDN/Contribute/Howto/Create_and_edit_pages", "新增一個新頁面")}}，這裏有關於如何獲得創建新頁面許可的重要信息；出於安全考慮，新賬戶默認沒有此功能。</p>
+
+<h3 id="步驟_2：找件事來完成">步驟 2：找件事來完成</h3>
+
+<p>現在您已經登入完畢，請閱讀{{anch("各種工作內容", "下面列表")}}中不同工作的描述，找出最吸引您的一個。您可以任選一個喜歡的工作作為第一步。</p>
+
+<h3 id="步驟_3：動手">步驟 3：動手</h3>
+
+<p>一旦決定了想做什麼事，就找個特定的頁面、程式碼範例之類的，然後開工吧！</p>
+
+<p>別擔心您無法做到完美，會有 MDN 成員來幫忙修復問題與錯誤。有任何疑問，都歡迎到<a href="/docs/MDN/Community">社群網頁</a>上查詢郵件群組、聊天頻道等資訊，協助您找尋答案。</p>
+
+<div class="note">
+<p>如果您想要在編輯 MDN 之前做些實際的試驗，那麽我們有提供一個沙盒(<strong><a href="/zh-TW/docs/Sandbox">Sandbox</a>)</strong>給您體驗。請將您的試驗限制在這個頁面。請不要為了看看會發生什麽而在内容頁做不必要的變動，這會弄得一團糟讓其他人搞不清楚，更糟糕的是，會讓一些衹是想學點或看點什麽的讀者混亂。</p>
+</div>
+
+<p>完成這項工作以後，歡迎再挑另一件事情做，或者看看{{anch("其他可以在 MDN 上做的事", "其他可以在 MDN 上做的事")}}。</p>
+
+<h2 id="各種工作內容">各種工作內容</h2>
+
+<p>貢獻 MDN 的方法很多，要選哪種就端看您的技能和興趣來決定。儘管有些工作可能很難，但我們也真的有好多比較單純的事情可以做。很多工作大概只需要花您五分鐘時間（甚至不到！）。在每項工作的簡短說明後方，您可以看到各類型工作所需的推估時間。</p>
+
+<h3 id="選項_1_給熱愛文字的人">選項 1: 給熱愛文字的人</h3>
+
+<p>您可以幫我們審查或編輯現有的文件，並為其加上正確的標籤。</p>
+
+<ul>
+ <li><a href="/zh-TW/docs/MDN/Contribute/Howto/Set_the_summary_for_a_page">撰寫文件摘要</a> （5-15 分鐘）</li>
+ <li><a href="/zh-TW/docs/MDN/Contribute/Howto/Do_an_editorial_review">編輯審查</a>（5–30 分鐘）</li>
+ <li><a href="/zh-TW/docs/MDN/Contribute/Howto/Write_a_new_entry_in_the_Glossary">在詞彙表中加上新的詞彙</a>（15 分鐘-1 小時）</li>
+ <li><a href="/zh-TW/docs/MDN/Contribute/Howto/Write_an_article_to_help_learn_about_the_Web">撰寫幫助大眾了解 Web 的文章</a>（1 小時-3 小時）</li>
+</ul>
+
+<div class="note">如果您要審查或撰寫新文章，建議先看一下<a href="/zh-TW/docs/MDN/Contribute/Guidelines/Style_guide">文件體例</a>。這樣能確保文章的一貫性。</div>
+
+<h3 id="選項_2_給熱愛程式碼的人">選項 2: 給熱愛程式碼的人</h3>
+
+<p>我們需要更多的代碼示例！你也可以幫助建立我們的網站平臺，<a href="https://developer.mozilla.org/zh-TW/docs/MDN/Kuma">Kuma</a>！</p>
+
+<ul>
+ <li><a href="/zh-TW/docs/MDN/Contribute/Howto/Convert_code_samples_to_be_live">轉換示例代碼是「可用的」</a>（30分鐘）</li>
+ <li><a href="https://wiki.mozilla.org/Webdev/GetInvolved/developer.mozilla.org">閱讀參與的指引</a>（30分鐘）</li>
+ <li><a href="http://kuma.readthedocs.org/en/latest/installation.html">設定 Kuma 的組建環境</a>（1 小時）</li>
+ <li><a href="https://github.com/mozilla/kuma#readme">把你的程式更新到 Kuma 程式庫</a> （1 小時）</li>
+</ul>
+
+<h3 id="選項_3_我喜歡文字和代碼">選項 3: 我喜歡文字和代碼</h3>
+
+<p>我們有需要的技術和語言技能的任務，像寫新文章，審查技術的準確性，或調整文檔。</p>
+
+<ul>
+ <li><a href="/zh-TW/docs/MDN/About/Promote">在你的網站推廣 MDN</a>（5 分鐘）</li>
+ <li><a href="/zh-TW/docs/MDN/Contribute/Howto/Do_a_technical_review">技術評論</a>（30 分鐘）</li>
+ <li><a href="/zh-TW/docs/Contribute_to_docs_that_are_currently_needed">撰寫當前主題所需要的文章</a>（1 小時以上）</li>
+ <li><a href="/zh-TW/docs/MDN/Contribute/Howto/Create_an_interactive_exercise_to_help_learning_the_web">撰寫能幫人理解 web 的互動示範</a>（1 小時以上）</li>
+ <li>從<a href="http://www.joshmatthews.net/bugsahoy/?mdn=1">MDN category in Bugs Ahoy</a>修復<a href="/zh-TW/docs/MDN/Contribute/Howto/Resolve_a_mentored_developer_doc_request">文件錯誤</a>（1 小時以上）</li>
+</ul>
+
+<h3 id="選項_4_我希望MDN有我的語言">選項 4: 我希望MDN有我的語言</h3>
+
+<p>所有的本地化和翻譯的工作，都是由我們的驚豔地 MDN 社區志願者所完成。</p>
+
+<ul>
+ <li><a href="/zh-TW/docs/MDN/Contribute/Localize/Translating_pages">翻譯頁面</a>（2 小時）（參見 <a href="/zh-TW/docs/MDN/Doc_status/l10nPriority">top priorities</a>）</li>
+ <li>與其他列在<a href="/zh-TW/docs/MDN/Contribute/Localize/Localization_projects">本地化專案</a>裡面的朋友聯繫（30 分鐘）</li>
+</ul>
+
+<h3 id="選項_5_我發現了一些錯誤的資訊，但我不知道該怎樣修復它">選項 5: 我發現了一些錯誤的資訊，但我不知道該怎樣修復它</h3>
+
+<p>你可以在 <a href="https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Developer%20Network">Bugzilla 上提交 bug</a>。（5分鐘）</p>
+
+<h2 id="其他可以在_MDN_上做的事">其他可以在 MDN 上做的事</h2>
+
+<ul>
+ <li><a href="/zh-TW/docs/MDN/Community">加入 MDN 社群</a></li>
+ <li><a href="/zh-TW/profile">填寫你的個人資料</a>以便其他人能更瞭解你</li>
+ <li>多理解如何<a href="/zh-TW/docs/MDN/Contribute">貢獻 MDN</a></li>
+</ul>
diff --git a/files/zh-tw/mdn/contribute/howto/create_an_mdn_account/index.html b/files/zh-tw/mdn/contribute/howto/create_an_mdn_account/index.html
new file mode 100644
index 0000000000..6f3f294e88
--- /dev/null
+++ b/files/zh-tw/mdn/contribute/howto/create_an_mdn_account/index.html
@@ -0,0 +1,34 @@
+---
+title: 如何創建 MDN 帳戶
+slug: MDN/Contribute/Howto/Create_an_MDN_account
+translation_of: MDN/Contribute/Howto/Create_an_MDN_account
+---
+<div>{{MDNSidebar}}</div><p><span class="seoSummary">要針對 MDN 做出任何改變，你需要一個 MDN 帳戶。不要擔心，如果你只是想閱讀和搜索 MDN，你並不需要帳戶！這個簡單的指南幫助你設置 MDN 帳戶。</span></p>
+
+<div class="pull-aside">
+<div class="moreinfo"><strong>為什麼 MDN 需要我的電子郵件地址？</strong><br><br>
+
+<p>你的電子郵件地址用於帳戶恢復，MDN 管理員也會在必要時，用它來和你討論你的帳戶或你在網站上的活動。</p>
+<p>此外，你可以選擇註冊的通知（例如<a href="/zh-TW/docs/MDN/Contribute/Howto/Watch_a_page">特定頁面被更改時</a>）和信息（例如，如果你選擇加入我們的 beta 測試團隊，你可能會收到需要測試的新功能）的電子郵件。</p>
+<p>你的電子郵件地址永遠不會在 MDN 顯示，而且只會在符合我們的<a href="https://www.mozilla.org/privacy/websites/">隱私權政策</a>下使用。</p>
+
+<div class="note">如果你透過 Github 登入 MDN，而且在 Github 使用了 noreply 的電子郵件地址，你<em>不會</em>收到來自 MDN 的訊息（包含你訂閱頁面的訊息）。</div>
+</div>
+</div>
+
+<ol>
+ <li>在 MDN 每一頁的最上方，你會發現有一個<strong>登入</strong>的按鈕。滑鼠滑到那邊後點一下（如果是移動設備就輕按）以表列 MDN 支持的驗證服務列表。</li>
+ <li>選擇要登入的服務。目前只支持 GitHub。請注意如果選了 GitHub，你的 MDN 公開用戶頁會包含一個指向你 GitHub 頁面的連結。</li>
+ <li>按照 GitHub 的提示把您的帳戶連接到 MDN。</li>
+ <li>一旦認證服務把你帶回 MDN 以後，MDN 就會提示你輸入一個用戶名和電子郵件地址。<em><strong>您的用戶名會被公開顯示以表彰你所做的工作。不要使用您的電子郵件地址作為用戶名。</strong></em>。</li>
+ <li>點擊「創建我的 MDN 配置文件」按鈕。</li>
+ <li>如果您在步驟四指定的電子郵件地址，與認證服務使用的不一樣，你需要檢查這個電子郵件地址，並點擊確認電子郵件中的鏈接。</li>
+</ol>
+
+<p>就是這樣！你有一個MDN帳戶，並可以立即編輯或標籤頁，或者提交演示！</p>
+
+<p>您可以在任何 MDN 頁面的頂部點擊你的名字，看看你的公開檔案。從那裡，你可以點擊「編輯」按鈕，進行更改或添加到您的個人資料，所以你可以分享更多關於您的利益，把鏈接添加到你的推特帳戶或部落格等等。</p>
+
+<div class="note">
+<p>用戶名新不能包含空格或“@”字符。請記住，你的用戶名會被公開顯示，以確定你所做的工作！</p>
+</div>
diff --git a/files/zh-tw/mdn/contribute/howto/create_and_edit_pages/index.html b/files/zh-tw/mdn/contribute/howto/create_and_edit_pages/index.html
new file mode 100644
index 0000000000..7e4813e5a8
--- /dev/null
+++ b/files/zh-tw/mdn/contribute/howto/create_and_edit_pages/index.html
@@ -0,0 +1,144 @@
+---
+title: 編輯以及新增頁面
+slug: MDN/Contribute/Howto/Create_and_edit_pages
+tags:
+  - MDN
+  - 初學者
+  - 新頁面
+  - 編輯
+translation_of: MDN/Contribute/Howto/Create_and_edit_pages
+---
+<div>{{MDNSidebar}}</div><p>幾乎每位MDN的貢獻者在MDN中都會做的兩件基本工作，即為編輯一個已存在的頁面或者是新增一個頁面。這篇文章將介紹如何編輯文件的基本技能。</p>
+
+<h2 id="編輯一個已存在的頁面">編輯一個已存在的頁面</h2>
+
+<p>想要編輯十分的簡單：</p>
+
+<ul>
+ <li>只要按下畫面右上角的 <strong>Edit</strong> 按鈕。</li>
+ <li>頁面會重新載入各種選項，這樣一來你就能直接在頁面新增或刪除資訊。</li>
+ <li>你可以增加文件段落、刪除文字、插入標題、以及做各式各樣的基本撰寫與編輯。</li>
+</ul>
+
+<h2 id="預覽修改">預覽修改</h2>
+
+<p>若是要檢視您所做出的變更:</p>
+
+<ul>
+ <li>點選「預覽修改」按鈕（在編輯模式之中）位於文章標題上方。</li>
+ <li>會以開啟一個新分頁或是新視窗來顯示一個您所做的所有變更。</li>
+ <li>每當您按下此按鈕，此預覽頁會顯示您最新的更動狀態</li>
+</ul>
+
+<p>請注意！預覽變更<strong>並不等同</strong>儲存您的修改，請小心不要太快關閉您的文章編輯頁面。</p>
+
+<h2 id="版本註解">版本註解</h2>
+
+<p>在您預覽您的編輯過後，您總會希望送出您的修訂版本。在您<strong>送出</strong>之前，請在頁面文章下方找版本註解的輸入框，並且留下您於此次所做的變更註解以讓其他貢獻者能了解您做了那些變更<span style="line-height: 1.572;">。 舉例來說，您可能新增了一個段落，改變一些詞彙使其更符合原意，重新編寫段落以更在地化，或是移除了一些多餘的資訊。</span></p>
+
+<h2 id="Tags">Tags</h2>
+
+<p>您可以於文章編輯區塊下增加或移除用以描述文章內容以及用途的 tags。請詳見 <a href="/en-US/docs/MDN/Contribute/Tagging">How to properly tag pages</a> 以了解 tags 如何來提供資訊。</p>
+
+<h2 id="審核是必要的嗎">審核是必要的嗎?</h2>
+
+<p>在您送出您的變更之前，您可以藉由勾選技術審核（針對 code、APIs或是技術內容），編輯審查（針對篇章結構、文法或內容），或是模板審查（針對 KumaScript code ），來讓專家或是經驗豐富的貢獻者審核您的變更。</p>
+
+<h2 id="附件">附件</h2>
+
+<p>若您想要讓文章更易於理解或是加上插圖，而希望在頁面上<strong>夾帶檔案</strong>，您可在文章編輯頁面下方找到此功能。{OptimizeImagesNote(1)}}</p>
+
+<h2 id="儲存、放棄、以及繼續修改">儲存、放棄、以及繼續修改</h2>
+
+<p>當您修改完成，以及滿懷希望的預覽修改之後，您可以填寫註解並且透過點擊於文章標題右手邊的「<strong>儲存修改</strong>」綠色按鈕。若您改變您的心意，您可以透過點擊於文章標題右手邊的「<strong>放棄修改</strong>」紅色按鈕。</p>
+
+<p>於版本註解輸入 <strong>Enter </strong>和點選「儲存並繼續修改」具有同等的效果。</p>
+
+<h2 id="新增一個新頁面">新增一個新頁面</h2>
+
+<p>若您不知道能夠在哪裡新增文章，<strong>別擔心！</strong>您可以隨意存放，我們會找到文章並且移到文章到它所屬的地方，或者與現有內容合併比較合理。您可以不需要為了使其完美而花費太多心力。 我們有快樂的地精幫手可以來為您的內容保持乾淨以及充滿價值。</p>
+
+<p>以下是一些創造新頁面的方法：</p>
+
+<ul>
+ <li><a href="#「缺失頁面」連結">「缺失頁面」連結</a></li>
+ <li><a href="#非基於連結而建立的新頁面">非基於連結而建立的新頁面</a></li>
+ <li><a href="#從現有的頁面新增子頁面">從現有的頁面新增子頁面</a></li>
+ <li><a href="#複製現有的頁面">複製現有的頁面</a></li>
+ <li><a href="#從現有頁面連結">從現有頁面連結</a></li>
+</ul>
+
+<h2 id="「缺失頁面」連結">「缺失頁面」連結</h2>
+
+<p>就像大部分的wiki，在MDN上當然可能在頁面上新增還未存在的頁面連結。舉例來說，作者可以在新增API所屬頁面前，新增所有API的成員清單。在MDN上，連結至還未存在的頁面會顯示為紅色。</p>
+
+<p>要在頁面新增「缺失頁面」連結：</p>
+
+<ol>
+ <li>請先確認您已經登入MDN（如果您還未登入，點繫「缺失頁」連結會出現404（找不到頁面）錯誤）。</li>
+ <li>點擊「缺失頁面」連結，將開啟<a href="https://developer.mozilla.org/en-US/docs/MDN/Contribute/Editor">MDN Editor UI</a>，讓您新增缺失頁面。</li>
+ <li>撰寫頁面內容，並且儲存。</li>
+</ol>
+
+<h2 id="非基於連結而建立的新頁面">非基於連結而建立的新頁面</h2>
+
+<p>為了建立一個非基於連結而建立的新頁面，您需要於 URL 區塊後輸入一個獨一無二的頁面名稱。舉例來說，若您輸入:</p>
+
+<pre class="language-html">https://developer.mozilla.org/en-US/docs/FooBar</pre>
+
+<p>MDN 會心建立一個標題為「FooBar」而且會於開啟編輯器讓您能夠編輯此新頁面。請參考 <a href="#Editing_an_existing_page">Editing an existing page</a> section of this article for how to use the editor mode.</p>
+
+<h2 id="從現有的頁面新增子頁面">從現有的頁面新增子頁面</h2>
+
+<p>為您在現有的頁面架構下新增一個子頁面:</p>
+
+<ol>
+ <li>在「父」頁面，點選<strong>進階目錄</strong> ( 於列表上呈現齒輪圖樣 )，並點選<strong>新增子頁面</strong>。接著便會出現一個可以編輯新頁面的模式。</li>
+ <li>於 <strong>Title</strong> 欄位輸入文章標題。</li>
+ <li>若有必要，改變 <strong>Slug</strong> 欄位 ( 舉例來說，若文章標題非常長而您又希望有個較短的 URL）。此欄位會由編輯器自動地來填入， by substituting underscores for spaces in the title. 在此種狀況下，您只能改變 URL 的最後一部分。</li>
+ <li>在<strong>TOC</strong>欄位，選擇您想要自動生成顯示在目錄的標題層級，或者這一頁不需要目錄也可以選擇「不需要目錄」選項。</li>
+ <li>於編輯器中增添內容並且儲存，請參考 <a href="#Editing_an_existing_page">Editing an existing page</a> 文章來了解如何運用編輯模式。</li>
+</ol>
+
+<h2 id="複製現有的頁面">複製現有的頁面</h2>
+
+<p>若您想於您的新頁面上套用某個現存頁面的格式，您可以點選「複製此頁」並於稍後改變該複製頁的內容。</p>
+
+<ol>
+ <li>於原始的頁面上，點選<strong>進階目錄</strong> ( 於列表上呈現齒輪圖樣 )，並且點選<strong>複製此頁</strong>。接著便可編輯一個以該原始文件為樣本的複製頁面。</li>
+ <li>您可根據您文章的內容適當地訂下<strong>標題</strong>。<strong>Slug</strong> 會根據您文章<strong>標題</strong>如何訂定而自動變換。</li>
+ <li>如有必要，可以改變 <strong>Slug </strong>的部分內容以呈現出新文件於原始架構下的不同。（在大多數的狀況下，此舉是多餘的。因為複製後的頁面對於原始頁面具有相似的內容，因此就必須放在相似的架構之下。）</li>
+ <li>在<strong>TOC</strong>欄位，選擇您想要自動生成顯示在目錄的標題層級，或者這一頁不需要目錄也可以選擇「不需要目錄」選項。</li>
+ <li>在頁面編輯欄位編寫內容，並且儲存您的變更。請參考 <a href="#Editing_an_existing_page">Editing an existing page</a> 文章來了解如何運用編輯模式。</li>
+</ol>
+
+<h2 id="從現有頁面連結">從現有頁面連結</h2>
+
+<p>這種方法算是混合形式，您可以在其他頁面產生連結，接著點擊剛加上去的連結，就會產生新的頁面了。</p>
+
+<ol>
+ <li>從現有頁面任何地方輸入新頁面的名稱（需合理）。</li>
+ <li>反白該名子並且於編輯器中點選連結圖樣（<img alt="" src="https://developer.mozilla.org/files/3810/link-icon.png" style="height: 28px; width: 29px;">）。「連結」的訊息框會出現並且詢問該段反白文字需要被導向哪個頁面</li>
+ <li>「/zh-TW/docs/」 是預設的 URL 欄位內容。您可於「/zh-TW/docs/」之後輸入新頁面的名子（該頁面的名字並不需要和被連結的文字內容相同）。</li>
+ <li>點擊「確定」來創造和插入新的連結。</li>
+</ol>
+
+<p>當連結呈現紅色時，代表著該頁面尚未存在。當連結呈現藍色時，代表著該頁面已經存在。若您想要建立一個新頁面但他的編題已經存在時，首先去檢查並改善現存的頁面，否則為您的新頁面想個不同的標題名稱並以此產生連結。請參考 <a href="https://developer.mozilla.org/Project:en/Page_Naming_Guide" title="Project:en/Page_Naming_Guide">page naming guide</a> 以幫助您命名。</p>
+
+<p>您可點擊您新建立的紅色連結（在您儲存以及關閉編輯器之後），來為您的新頁面增添內容。新頁面將在編輯模式下開啟，此時您就可以編寫內容了。請參考 <a href="#Editing_an_existing_page">Editing an existing page</a> 文章來了解如何運用編輯模式。</p>
+
+<h2 id="重新整理頁面內容">重新整理頁面內容</h2>
+
+<p>MDN支援KumaScript巨集和嵌入其他頁面內容插入頁面，有時候因效能因素需要為生成的頁面用快取，而略為延遲內容更新。頁面從原始碼生成，產生的頁面會先產生快取以便未來存取使用。從現在起，所有的巨集（模版）或是嵌入（在該頁使用<span class="templateLink"><code><a href="https://developer.mozilla.org/en-US/docs/Template:Page">Page</a></code></span>巨集）並不會馬上就會反應更動後的巨集變動，巨集生成頁面，或者嵌入頁面的內容。</p>
+
+<ul>
+ <li>要手動更新頁面，您可以在您的瀏覽器強制更新。MDN偵測到強制更新，將會重新生成頁面，更新的巨集生成頁面，以及嵌入頁面內容。</li>
+ <li>您可以週期性設定自動重新生成頁面。不過除非該頁面常常更新，不然請不要這麼做。請參考 <a href="https://developer.mozilla.org/en-US/docs/MDN/Contribute/Tools/Page_regeneration">Page regeneration </a>一文獲得更多資訊。</li>
+</ul>
+
+<h2 id="參見">參見</h2>
+
+<ul>
+ <li><a href="/en-US/docs/MDN/Contribute/Editor">MDN 編輯器指南</a></li>
+ <li><a href="/zh-TW/docs/MDN/Contribute/Content/Style_guide">MDN 風格指南</a></li>
+</ul>
diff --git a/files/zh-tw/mdn/contribute/howto/do_a_technical_review/index.html b/files/zh-tw/mdn/contribute/howto/do_a_technical_review/index.html
new file mode 100644
index 0000000000..ecb35fe0be
--- /dev/null
+++ b/files/zh-tw/mdn/contribute/howto/do_a_technical_review/index.html
@@ -0,0 +1,50 @@
+---
+title: 如何進行技術審查
+slug: MDN/Contribute/Howto/Do_a_technical_review
+translation_of: MDN/Contribute/Howto/Do_a_technical_review
+---
+<div>{{MDNSidebar}}</div><div>{{IncludeSubnav("/zh-TW/docs/MDN")}}</div>
+
+<p class="summary"><strong>技術審查</strong>包含檢查文章的正確與完整性，並在需要時進行修正。若文章作者需要其他人來檢查文章的技術性內容，可以在編輯時勾選「技術審查」（Technical review）。通常由作者連絡特定工程師來進行技術審查，但具備該主題技術專長者亦可參與。</p>
+
+<p><span class="seoSummary">本文描述如何執行技術審查，以協助確保 MDN 的內容是正確的。</span></p>
+
+<dl>
+ <dt>要做什麼？</dt>
+ <dd>審查並修正文章在技術上的正確與完整性。</dd>
+ <dt>要審查的文章在哪？</dt>
+ <dd>找被標記為「<a href="/zh-TW/docs/needs-review/technical">技術審查</a>」（technical review）的特定文章。</dd>
+ <dt>要知道些什麼？</dt>
+ <dd>
+ <ul>
+  <li>針對文章主題的專業知識。若閱讀該文章並沒有對你傳授非常新的東西，那就視你自己為專家。</li>
+  <li>編輯 MDN 上維基文章的方法。</li>
+ </ul>
+ </dd>
+ <dt>有哪些步驟？</dt>
+ <dd>
+ <ol>
+  <li>選擇要審查的文章
+   <ol>
+    <li>前往<a href="/zh-TW/docs/needs-review/technical">技術審查</a>（technical reviews）清單頁面。這裡列出所有請求技術審查的頁面。</li>
+    <li>選擇一個頁面，而你對該主題非常熟練。</li>
+    <li>點擊文章連結以載入頁面。</li>
+   </ol>
+  </li>
+  <li><a id="core-steps" name="core-steps"></a>閱讀文章並密切關注技術性細節：這篇文章正確嗎？有沒有漏掉什麼？若初次選擇的頁面並不適合由你來審查，不要猶豫，選擇其他頁面。</li>
+  <li>若沒有錯誤，你不需要透過編輯將文章標記為已審查。找到頁面左方側邊攔的「快速回顧」（quick review），黃色框框會列出任何等待中的審查，並讓你清除審查請求的標記。若有審查請求會顯示如下：<br>
+   <img alt="Screenshot of the sidebar's box listing reviews that have been requested and allowing the flags to be changed." src="https://mdn.mozillademos.org/files/13016/SidebarTechReviewRequested.png"></li>
+  <li>取消選取「<strong>技術</strong>」（<strong>Technical</strong>），然後點擊「<strong>儲存</strong>」（<strong>Save</strong>）。</li>
+  <li>若發現有錯誤需要修正，亦可在編輯器中改變審查請求的狀態。操作過程如下：
+   <ol>
+    <li>點擊靠近頁面頂端的「<strong>編輯</strong>」（<strong>Edit</strong>）按鈕以編輯頁面，這會帶你到 <a href="/en-US/docs/MDN/Contribute/Editor">MDN editor</a>。</li>
+    <li>修正任何錯誤的技術資訊，並且（或者）增加任何重要但被遺漏的訊息。</li>
+    <li>在文章底部填寫<strong>版本註解</strong>（<strong>Revision Comment</strong>）。這是用來描述你做了什麼事的簡短訊息，如：「技術審查完成」。當你做了些修正，將相關資訊納入你的註解，如：「技術審查並修正參數描述」。這會幫助其他貢獻者和網站編輯知道你變更的內容和理由。你也可提出（若有的話）自認不夠資格審查的部分。</li>
+    <li>在 「<strong>需要審核嗎？</strong>」（<strong>Review Needed?</strong>） 下方，取消選取「<strong>技術</strong>」（<strong>Technical</strong>），就在頁面底部版本註解區塊附近。</li>
+    <li>點擊「<strong>發布</strong>」（<strong>PUBLISH</strong>）按鈕。</li>
+   </ol>
+  </li>
+ </ol>
+ <p>恭喜！你已經完成你的第一份技術審查！感謝你的幫助！</p>
+ </dd>
+</dl>
diff --git a/files/zh-tw/mdn/contribute/howto/do_an_editorial_review/index.html b/files/zh-tw/mdn/contribute/howto/do_an_editorial_review/index.html
new file mode 100644
index 0000000000..8ef91de87d
--- /dev/null
+++ b/files/zh-tw/mdn/contribute/howto/do_an_editorial_review/index.html
@@ -0,0 +1,55 @@
+---
+title: 如何進行編輯審查
+slug: MDN/Contribute/Howto/Do_an_editorial_review
+tags:
+  - 如何
+  - 指南
+  - 文件
+  - 編輯審查
+translation_of: MDN/Contribute/Howto/Do_an_editorial_review
+---
+<div>{{MDNSidebar}}</div>
+
+<div>{{IncludeSubnav("/zh-TW/docs/MDN")}}</div>
+
+<p class="summary">一個主題的編輯審查包含錯字、拼字、文法、語法或其他文字錯誤。並非所有貢獻者都是語言專家，但他們的知識可以提供極為有用的資訊，因此需要審稿和校對。這就是編輯審查在做的事。</p>
+
+<p><span class="seoSummary">這個主題將會介紹如何進行編輯審查，以幫助確保在 MDN 的資訊是正確的。</span></p>
+
+<dl>
+ <dt>有哪些任務？</dt>
+ <dd>必要的有審稿和校對。</dd>
+ <dt>有哪些東西需要編輯審查？</dt>
+ <dd>那些被標記需要審查的主題。</dd>
+ <dt>進行編輯審查需要知道什麼？</dt>
+ <dd>你需要具有良好的英文文法和拼字能力（即能準確翻譯英文成中文的能力）。編輯審查在於確保文法、拼字和語法的正確和意義，並遵守 <a href="/zh-TW/docs/MDN/Contribute/Guidelines/Writing_style_guide">MDN 編輯指南</a>。</dd>
+ <dt>有哪些步驟？</dt>
+ <dd>
+ <ol>
+  <li>選擇一個主題：
+   <ol>
+    <li>前往<a href="/zh-TW/docs/needs-review/editorial">待審查清單</a>。這個表列出了要求審查的主題。</li>
+    <li>選擇一個中文標題且不帶有 <code>Template:</code> (<code>Template:</code> 包含 MDN 功能碼) 的主題。</li>
+    <li>點擊該主題的連結。</li>
+   </ol>
+  </li>
+  <li>閱讀主題，注意錯字、拼字、文法、語法或其他錯誤。如果你覺得無法應付，請找下一個主題。</li>
+  <li>如果沒有錯誤，你不需要編輯主題來標記為已審查。在左方導覽列尋找「快速審查」方塊：<br>
+   <img alt="快速審查" src="http://i.imgur.com/3T2JKns.jpg" style="height: 104px; width: 321px;"></li>
+  <li>取消選取 <strong>編輯 </strong>方塊並點擊 <strong>儲存。</strong></li>
+  <li>如果有錯誤需要被糾正：
+   <ol>
+    <li>點擊在頁面頂端附近的 <strong>編輯</strong> 按鈕，接著會轉到 <a href="/zh-TW/docs/MDN/Contribute/Editor">MDN 編輯器</a>。</li>
+    <li>修正你找到的錯字、拼字、文法、語法或其他錯誤。你並不需要修正所有錯誤，但若你不確定你已經完整的審查主題，請留下編輯審查請求。</li>
+    <li>在主題尾端留下 <strong>版本註解</strong> 。像是「編輯審查：修正錯字、文法和拼字」。這能讓其他貢獻者和網站編輯者知道你改了什麼和為什麼。</li>
+    <li>取消選取在 <strong>需要審查嗎？</strong> 中的 <strong>編輯 </strong>方塊。他在版本註解下面。</li>
+    <li>按下 <strong>發布</strong>。</li>
+   </ol>
+  </li>
+ </ol>
+
+ <div class="note">
+ <p>你的變更不一定會立刻出現，他可能會因送出和儲存延遲一會。</p>
+ </div>
+ </dd>
+</dl>
diff --git a/files/zh-tw/mdn/contribute/howto/index.html b/files/zh-tw/mdn/contribute/howto/index.html
new file mode 100644
index 0000000000..e33524d58b
--- /dev/null
+++ b/files/zh-tw/mdn/contribute/howto/index.html
@@ -0,0 +1,14 @@
+---
+title: How-to guides
+slug: MDN/Contribute/Howto
+tags:
+  - Documentation
+  - Landing
+  - MDN
+  - NeedsTranslation
+  - TopicStub
+translation_of: MDN/Contribute/Howto
+---
+<div>{{MDNSidebar}}</div><p>這些文章將會帶領你一步步完成貢獻 MDN 專案所需完成的目標</p>
+
+<p>{{LandingPageListSubpages}}</p>
diff --git a/files/zh-tw/mdn/contribute/howto/set_the_summary_for_a_page/index.html b/files/zh-tw/mdn/contribute/howto/set_the_summary_for_a_page/index.html
new file mode 100644
index 0000000000..e44a6fb7ce
--- /dev/null
+++ b/files/zh-tw/mdn/contribute/howto/set_the_summary_for_a_page/index.html
@@ -0,0 +1,50 @@
+---
+title: 如何撰寫文章摘要？
+slug: MDN/Contribute/Howto/Set_the_summary_for_a_page
+tags:
+  - 摘要
+translation_of: MDN/Contribute/Howto/Set_the_summary_for_a_page
+---
+<div>{{MDNSidebar}}</div><p> </p>
+
+<p><span class="seoSummary">你可以在MDN用各式各樣的方式來定義一個頁面的摘要，像是搜尋引擎結果，在其他的MDN網頁如某些到達頁(<a href="https://cola.workxplay.net/what-is-an-landing-page/">Landing Pages</a>)，以及提示中。他應該是在頁面的上下文中有意義的文本，並且在上下文中顯示時，沒有其餘的頁面內容。</span></p>
+
+<p>在頁面中摘要是明確定義的。如果沒有被明確定義的話，通成會拿第一句來當摘要，但並不總是最適合的。</p>
+
+<dl>
+ <dt>
+ <h3 id="任務是什麼？"><strong>任務是什麼？</strong></h3>
+ </dt>
+ <dd>在頁面中找出可以當成摘要的文字，且用別種文字說明寫成適當的摘要。</dd>
+ <dt>
+ <h3 id="哪些地方需要撰寫摘要？"><strong>哪些地方需要撰寫摘要？</strong></h3>
+ </dt>
+ <dd>缺少摘要的頁面，或是摘要不足的頁面。</dd>
+ <dt>
+ <h3 id="撰寫摘要之前，你需要具備知道什麼？"><strong>撰寫摘要之前，你需要具備/知道什麼？</strong></h3>
+ </dt>
+ <dd>會使用MDN編輯器、擅長寫英文作文以及對於該頁面要有足夠的了解，才能寫出好的摘要。</dd>
+ <dt>
+ <h3 id="撰寫摘要的步驟："><strong>撰寫摘要的步驟：</strong></h3>
+ </dt>
+ <dd>
+ <ol>
+  <li>選一個頁面：
+   <ol>
+    <li>在 <a href="/en-US/docs/MDN/Doc_status">MDN documentation status</a> 頁面中, 在<strong>Sections(章節)</strong>下方，點選任何一個你熟悉或是對其有所了解的標題連結（ex：HTML）：<br>
+     <img alt="" src="https://mdn.mozillademos.org/files/8681/sections.png" style="height: 130px; width: 504px;"></li>
+    <li>在此文件狀態頁面上方的摘要表格內，點選<strong>Pages(頁面)。</strong>點選後會導向關於這個標題(ex:HTML)的全部頁面的索引頁。左邊欄位顯示這個頁面的連結，右邊則是顯示tags(標籤)以及該頁面的摘要。<img alt="" src="https://mdn.mozillademos.org/files/8675/pages.png" style="height: 82px; width: 361px;"></li>
+    <li>挑選一個沒有摘要的頁面，或是摘要太少的頁面：<br>
+     <img alt="" src="https://mdn.mozillademos.org/files/8677/summary.png" style="height: 38px; width: 296px;"></li>
+    <li>點選該頁面的連結。</li>
+   </ol>
+  </li>
+  <li>點選<strong>編輯</strong>打開MDN編輯器。</li>
+  <li>找出一句或是兩句可以總結上下文的摘要。如果需要的話，編輯現有的內容以創造或是修改成好的摘要。</li>
+  <li>選擇要當成摘要的文字。</li>
+  <li>點選在編輯器工具列中的格式化樣式，選擇<strong>SEO Summary</strong>. （在原始碼中，這會在被選起來的文字旁，產生一個HTML元素： {{HTMLElement("span")}} element with <code>class="seoSummary"</code> ）<br>
+   <img alt="" src="https://mdn.mozillademos.org/files/8679/styles.png" style="height: 231px; width: 403px;"></li>
+  <li>使用修訂評論保存您的更改。評論為非必填項目，但我們鼓勵您填寫。能使其他人更容易追蹤文章的變化。</li>
+ </ol>
+ </dd>
+</dl>
diff --git a/files/zh-tw/mdn/contribute/howto/tag/index.html b/files/zh-tw/mdn/contribute/howto/tag/index.html
new file mode 100644
index 0000000000..515ad7f6ef
--- /dev/null
+++ b/files/zh-tw/mdn/contribute/howto/tag/index.html
@@ -0,0 +1,374 @@
+---
+title: How to properly tag pages
+slug: MDN/Contribute/Howto/Tag
+translation_of: MDN/Contribute/Howto/Tag
+---
+<div>{{MDNSidebar}}</div><p><strong>Article tags</strong> are an important way to put visitors in touch with helpful content. Each page should normally have several tags to help keep content organized. <span class="seoSummary">This page explains the best way to tag pages so that our readers can find information and we can keep ourselves organized.</span></p>
+
+<p>For a help with the user interface for editing tags, see the <a href="/en-US/docs/MDN/Contribute/Editor/Basics#The_tags_box">tagging section</a> in our editor guide.</p>
+
+<p>Please use tags properly as explained below. If you don't, our automated tools will not correctly generate lists of content, landing pages, and cross-linking of articles.</p>
+
+<h2 id="How_MDN_uses_tags">How MDN uses tags</h2>
+
+<p>Tags get used on MDN several ways:</p>
+
+<dl>
+ <dt>Document categorization</dt>
+ <dd>What type of document is it? Is it a reference? A tutorial? A landing page? Our visitors can use these tags to filter searches, so they're really important!</dd>
+ <dt>Topic identification</dt>
+ <dd>What is the article about? Is it about an API? The DOM? Graphics? Again, these tags are important because they can filter searches.</dd>
+ <dt>Technology status</dt>
+ <dd>What's the status of the technology? Is it non-standard? Obsolete or deprecated? Experimental?</dd>
+ <dt>Skill level</dt>
+ <dd>For tutorials and guides, how advanced is the material covered by the article?</dd>
+ <dt>Document metadata</dt>
+ <dd>The writing community needs tags to keep track of which pages need what kind of work.</dd>
+</dl>
+
+<h2 id="Tag_type_guide">Tag type guide</h2>
+
+<p>Here's a quick guide to the types of tags and possible values for them.</p>
+
+<h3 id="Document_category">Document category</h3>
+
+<p>When you tag an article with one of these categories, you help the automated tools more accurately generate landing pages, tables of contents, and so on. Our new search system will also use these terms so that our visitors can locate reference or guide information at will.</p>
+
+<p>We use the following category names as standard tagging terms:</p>
+
+<dl>
+ <dt><code>{{Tag("Intro")}}</code></dt>
+ <dd>The article provides introductory material about a topic. Ideally each technology area should have only one "Intro".</dd>
+ <dt><code>{{Tag("Featured")}}</code></dt>
+ <dd>The article is critical and will display prominently on landing pages. Use this tag sparingly (never more than three documents in each documentation area).</dd>
+ <dt><code>{{Tag("Reference")}}</code></dt>
+ <dd>The article contains reference material about an API, element, attribute, property, or the like.</dd>
+ <dt><code>{{Tag("Landing")}}</code></dt>
+ <dd>The page is a landing page.</dd>
+ <dt><code>{{Tag("Guide")}}</code></dt>
+ <dd>The article is a how-to or guide page.</dd>
+ <dt><code>{{Tag("Example")}}</code></dt>
+ <dd>The article is a code sample page, or has code samples (that is, actual snippets of useful code, not one-line "syntax examples").</dd>
+</dl>
+
+<h3 id="Topic">Topic</h3>
+
+<p>By identifying the article's topic area, you are helping generate better search results (and landing pages and navigation as well).</p>
+
+<p>While there's some room for flexibility here as we identify new topic areas, we try to limit ourselves to the names of APIs or technologies. Some useful examples:</p>
+
+<ul>
+ <li><code>{{Tag("HTML")}}</code></li>
+ <li><code>{{Tag("CSS")}}</code></li>
+ <li><code>{{Tag("JavaScript")}}</code> (notice the capital "S"!)</li>
+ <li><code>{{Tag("Document")}}</code></li>
+ <li><code>{{Tag("DOM")}}</code></li>
+ <li><code>{{Tag("API")}}</code> for each interface, method and property.</li>
+ <li><code>{{Tag("Method")}}</code> for each method of an API</li>
+ <li><code>{{Tag("Property")}}</code> for each property of an API</li>
+ <li><code>{{Tag("Graphics")}}</code></li>
+ <li><code>{{Tag("Firefox OS")}}</code></li>
+ <li><code>{{Tag("Gecko")}}</code></li>
+ <li><code>{{Tag("XUL")}}</code></li>
+ <li><code>{{Tag("XPCOM")}}</code></li>
+ <li><code>{{Tag("SVG")}}</code></li>
+ <li><code>{{Tag("WebGL")}}</code></li>
+ <li><code>{{Tag("Element")}}</code></li>
+ <li><code>{{Tag("Node")}}</code></li>
+ <li><code>{{Tag("Tools")}}</code></li>
+ <li><code>{{Tag("Web")}}</code></li>
+</ul>
+
+<p>In general, your topic identification tag should be the name of an interface with a number of related pages (like <a href="/en-US/docs/Web/API/Node" title="/en-US/docs/Web/API/Node">Node</a>, which has many pages for its various properties and methods), or the name of an overall technology type. You might tag a page about WebGL with <code>Graphics</code> and <code>WebGL</code>, for example, but a page about {{HTMLElement("canvas")}} with <code>HTML</code>, <code>Element</code>, <code>Canvas</code>, and <code>Graphics</code>.</p>
+
+<h3 id="Technology_status">Technology status</h3>
+
+<p>To help the reader understand how viable a technology is, we use tags to label pages as to the status of the technology's specification. This isn't as detailed as actually explaining what the spec is and how far the technology has come in the specification process (that's what the Specifications table is for), but it helps the reader judge, at a glance, whether it's a good idea to use the technology described in the article.</p>
+
+<p>Here are possible values for these tags:</p>
+
+<dl>
+ <dt><code>{{Tag("Non-standard")}}</code></dt>
+ <dd>Indicates that the technology or API described on the page is not part of a standard, but is considered stable in any implementing browser(s). If you don't use this tag, your readers will assume the technology is standard. The compatibility table on the page should clarify which browser(s) support this technology or API.</dd>
+ <dt><code>{{Tag("Deprecated")}}</code></dt>
+ <dd>The technology or API covered on the page is marked as deprecated in the specification, and is likely to eventually be removed, but is generally still available in current versions of browsers.</dd>
+ <dt><code>{{Tag("Obsolete")}}</code></dt>
+ <dd>The technology or API has been deemed obsolete and has been removed (or actively being removed) from all or most current browsers.</dd>
+ <dt><code>{{Tag("Experimental")}}</code></dt>
+ <dd>The technology is not standardized, and is an experimental technology or API that may or may not ever become part of a standard. It is also subject to change in the browser engine (typically only one) that implements it.</dd>
+ <dt><code>{{Tag("Needs Privileges")}}</code></dt>
+ <dd>The API requires privileged access to the device on which the code is running.</dd>
+ <dt><code>{{Tag("Certified Only")}}</code></dt>
+ <dd>The API only works in certified code.</dd>
+</dl>
+
+<p>These tags are no excuse to leave out the <a href="/en-US/docs/Project:Compatibility_tables" title="/en-US/docs/Project:Compatibility_tables">compatibility table</a> in your article!</p>
+
+<h3 id="Skill_level">Skill level</h3>
+
+<p>Use the skill-level tag type only for guides and tutorials (that is, pages tagged <code>Guide</code>) to help users choose tutorials based on how familiar they are with a technology. There are three values for this:</p>
+
+<dl>
+ <dt><code>{{Tag("Beginner")}}</code></dt>
+ <dd>Articles designed to introduce the reader to a technology they've never used or have only a passing familiarity with.</dd>
+ <dt><code>{{Tag("Intermediate")}}</code></dt>
+ <dd>Articles for users who have gotten started with the technology but aren't experts.</dd>
+ <dt><code>{{Tag("Advanced")}}</code></dt>
+ <dd>Articles about stretching the capabilities of a technology and of the reader.</dd>
+</dl>
+
+<h3 id="Document_metadata">Document metadata</h3>
+
+<p>The writing community uses tags to label articles as requiring specific types of work. Here's a list of the ones we use most:</p>
+
+<dl>
+ <dt><code>{{Tag("junk")}}</code></dt>
+ <dd>The article needs to be deleted.</dd>
+ <dt><code>{{Tag("NeedsContent")}}</code></dt>
+ <dd>The article is a stub, or is otherwise lacking information. This tag means that someone should review the content and add more details and/or finish writing the article.</dd>
+ <dt><code>{{Tag("NeedsExample")}}</code></dt>
+ <dd>The article needs one or more examples created to help illustrate the article's point. These examples should use the <a href="/en-US/docs/Project:MDN/Contributing/How_to_help/Code_samples" title="/en-US/docs/Project:MDN/Contributing/How_to_help/Code_samples">live sample system</a>.</dd>
+ <dt><code>{{Tag("NeedsLiveSamples")}}</code></dt>
+ <dd>The article has one or more examples that need to be updated to use the <a href="/en-US/docs/Project:MDN/Contributing/How_to_help/Code_samples" title="/en-US/docs/Project:MDN/Contributing/How_to_help/Code_samples">live sample system</a>.</dd>
+ <dt><code>{{Tag("NeedsUpdate")}}</code></dt>
+ <dd>The content is out of date and needs to updating.</dd>
+ <dt><code>{{Tag("l10n:exclude")}}</code></dt>
+ <dd>The content is not really worth localizing and will not appear on localization status pages.</dd>
+ <dt><code>{{Tag("l10n:priority")}}</code></dt>
+ <dd>The content is important and should be marked as a priority for MDN translators. Shows up in an extra priority table on localization status pages.</dd>
+</dl>
+
+<h3 id="Web_Literacy_Map">Web Literacy Map</h3>
+
+<p>The <a href="https://webmaker.org" rel="external">WebMaker</a> project, through the <a href="https://webmaker.org/literacy" rel="external">Web Literacy Map</a>, has defined skills needed to optimally read, write, and participate on the Web. We use Web literacy skills as tags on MDN to help our users find the resources that best suit their needs:</p>
+
+<dl>
+ <dt>{{Tag("Navigation")}}</dt>
+ <dd>how to browse the Web</dd>
+ <dt>{{Tag("WebMechanics")}}</dt>
+ <dd>how the Web is organized and how it works</dd>
+ <dt>{{Tag("Search")}}</dt>
+ <dd>how to find information, people, and resources on the Web</dd>
+ <dt>{{Tag("Credibility")}}</dt>
+ <dd>how to critically evaluate information you find on the Web</dd>
+ <dt>{{Tag("Security")}}</dt>
+ <dd>how to keep systems, identities, and content safe</dd>
+ <dt>{{Tag("Composing")}}</dt>
+ <dd>how to create and curate content for the Web</dd>
+ <dt>{{Tag("Remixing")}}</dt>
+ <dd>how to modify existing Web resources to create something new</dd>
+ <dt>{{Tag("DesignAccessibility")}}</dt>
+ <dd>how to create universally effective communications through Web resources</dd>
+ <dt>{{Tag("CodingScripting")}}</dt>
+ <dd>how to code and/or create interactive experiences on the Web</dd>
+ <dt>{{Tag("infrastructure")}}</dt>
+ <dd>how the Internet's technical stack works</dd>
+ <dt>{{Tag("Sharing")}}</dt>
+ <dd>how to create resources with others</dd>
+ <dt>{{Tag("Collaborating")}}</dt>
+ <dd>how to work with other people</dd>
+ <dt>{{Tag("Community")}}</dt>
+ <dd>how to get involved in Web communities and understand how they work</dd>
+ <dt>{{Tag("Privacy")}}</dt>
+ <dd>how to examine the consequences of sharing data online</dd>
+ <dt>{{Tag("OpenPractices")}}</dt>
+ <dd>how to help keep the Web accessible to everybody</dd>
+</dl>
+
+<h2 id="Putting_it_all_together">Putting it all together</h2>
+
+<p>So to each page you assign tags from several tag types, for example</p>
+
+<dl>
+ <dt>A tutorial about WebGL for beginners</dt>
+ <dd><code>WebGL</code>, <code>Graphics</code>, <code>Guide</code>, <code>Beginner</code></dd>
+ <dt>Reference page for {{HTMLElement("canvas")}}</dt>
+ <dd><code>Canvas</code>, <code>HTML</code>, <code>Element</code>, <code>Graphics,</code> <code>Reference</code></dd>
+ <dt>A landing page for Firefox OS developer tools</dt>
+ <dd><code>Tools</code>, <code>Firefox OS</code>, <code>Landing</code></dd>
+</dl>
+
+<h2 id="Tagging_and_search_filters">Tagging and search filters</h2>
+
+<p>Search filters won't work properly unless we tag MDN pages properly. Here's a table of search filters and which tags they look for.</p>
+
+<div class="note">
+<p><strong>Note:</strong> If multiple tags are listed under "Tag name," that means any one or more of these tags must be present for the article to match.</p>
+</div>
+
+<table class="standard-table">
+ <thead>
+  <tr>
+   <th scope="col">Filter group</th>
+   <th scope="col">Search filter name</th>
+   <th scope="col">Tag name</th>
+  </tr>
+ </thead>
+ <tbody>
+  <tr>
+   <th>Topic</th>
+   <td>Open Web Apps</td>
+   <td>{{Tag("Apps")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>HTML</td>
+   <td>{{Tag("HTML")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>CSS</td>
+   <td>{{Tag("CSS")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>JavaScript</td>
+   <td>{{Tag("JavaScript")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>APIs and DOM</td>
+   <td>{{Tag("API")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>Canvas</td>
+   <td>{{Tag("Canvas")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>SVG</td>
+   <td>{{Tag("SVG")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>MathML</td>
+   <td>{{Tag("MathML")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>WebGL</td>
+   <td>{{Tag("WebGL")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>XUL</td>
+   <td>{{Tag("XUL")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>Marketplace</td>
+   <td>{{Tag("Marketplace")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>Firefox</td>
+   <td>{{Tag("Firefox")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>Firefox for Android</td>
+   <td>{{Tag("Firefox Mobile")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>Firefox for Desktop</td>
+   <td>{{Tag("Firefox Desktop")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>Firefox OS</td>
+   <td>{{Tag("Firefox OS")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>Mobile</td>
+   <td>{{Tag("Mobile")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>Web Development</td>
+   <td>{{Tag("Web Development")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>Add-ons &amp; Extensions</td>
+   <td>{{Tag("Add-ons ")}}|| {{Tag("Extensions")}} || {{Tag("Plugins")}} || {{Tag("Themes")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>Games</td>
+   <td>{{Tag("Games")}}</td>
+  </tr>
+  <tr>
+   <th>Skill level</th>
+   <td>I'm an Expert</td>
+   <td>{{Tag("Advanced")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>Intermediate</td>
+   <td>{{Tag("Intermediate")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>I'm Learning</td>
+   <td>{{Tag("Beginner")}}</td>
+  </tr>
+  <tr>
+   <th>Document type</th>
+   <td>Docs</td>
+   <td><em>This restricts the search to docs content, leaving out Hacks and other MDN content.</em></td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>Demos</td>
+   <td><em>This includes Demo Studio content in the search results.</em></td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>Tools</td>
+   <td>{{Tag("Tools")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>Code Samples</td>
+   <td>{{Tag("Example")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>How-To &amp; Tutorial</td>
+   <td>{{Tag("Guide")}}</td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>Developer Profiles</td>
+   <td><em>This includes developer profiles from the MDN site in the search results.</em></td>
+  </tr>
+  <tr>
+   <th> </th>
+   <td>External Resources</td>
+   <td><em>The dev team is still figuring this out...</em></td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Tagging_problems_you_can_fix">Tagging problems you can fix</h2>
+
+<p>There are several kinds of tag problems you can help fix:</p>
+
+<dl>
+ <dt>No tags</dt>
+ <dd>Generally articles should have at <em>least</em> a "<a href="/en-US/docs/Project:MDN/Contributing/Tagging_standards#Category" title="/en-US/docs/Project:MDN/Contributing/Tagging_standards#Categories">category</a>" tag and a "<a href="/en-US/docs/Project:MDN/Contributing/Tagging_standards#Topic" title="/en-US/docs/Project:MDN/Contributing/Tagging_standards#Topic">topic</a>" tag. Usually other tags are appropriate as well, but if you can help us ensure that the minimum tags are present, you'll be a documentation hero!</dd>
+ <dt>Tags that don't follow our tagging standards</dt>
+ <dd>Please fix any documents whose tags don't follow the standards on this page.<br>
+ Note that due to a <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=776048">bug in Kuma</a>, some localized tags (such as <code>Référence</code>) may show up on some English pages. These tags are likely to reappear even if you delete them; don't bother trying to fix them until the Kuma bug is fixed.</dd>
+ <dt>Incorrect tags</dt>
+ <dd>If you're looking at an article about HTML and it's tagged "JavaScript", that's probably wrong! Likewise, if an article discusses Mozilla internals but has a "Web" tag, that's probably wrong too. Remove these tags and add the right tags if they aren't already there. Please also correct misspelled tags (e.g., "Javascript" will still match, since tags are case-insensitive, but let's not be sloppy!).</dd>
+ <dt>Missing tags</dt>
+ <dd>If an article has some but not all of the tags it needs, feel free to add more. For example, if a page in JavaScript reference is (correctly) tagged "JavaScript" but nothing else, you're invited to tag the page "Reference" as well!</dd>
+ <dt>Tag spam</dt>
+ <dd>This insidious beast is the most revolting tag problem of all: some Web vermin has deposited its droppings in the page tags (like "Free warez!" or "Hey I was browsing your site and wanted to ask you if you could help me solve this problem I'm having with Flash crashing all the time"). We've got to delete these right away!</dd>
+</dl>
+
+<p>If you see one (or more) of these problems, please <a href="/en-US/docs/Project:MDN/Contributing/Getting_started#Logging_into_MDN">log into MDN</a> and click EDIT at the top right of the MDN window. Once the editor loads up, scroll down to the bottom of the page, where you'll see the tag box. For more details on the tagging interface, see "<a href="/en-US/docs/Project:MDN/Contributing/Editor_guide#The_tags_box" title="/en-US/docs/Project:MDN/Contributing/Editor_guide#The_tags_box">The tags box</a>" in the <a href="/en-US/docs/Project:MDN/Contributing/Editor_guide" title="/en-US/docs/Project:MDN/Contributing/Editor_guide">MDN editor guide</a>.</p>
diff --git a/files/zh-tw/mdn/contribute/index.html b/files/zh-tw/mdn/contribute/index.html
new file mode 100644
index 0000000000..817ac06f4f
--- /dev/null
+++ b/files/zh-tw/mdn/contribute/index.html
@@ -0,0 +1,20 @@
+---
+title: 貢獻 MDN
+slug: MDN/Contribute
+tags:
+  - Documentation
+  - Guide
+  - Landing
+  - MCD PROJECT
+  - MDN
+translation_of: MDN/Contribute
+---
+<div>{{MDNSidebar}}</div><div>{{IncludeSubnav("/zh-TW/docs/MDN")}}</div>
+
+<p>歡迎！當你在看這個頁面時，就已經邁向成為 MDN 貢獻者的第一步！</p>
+
+<p><span class="seoSummary">這份指南涵蓋貢獻 MDN 的各個面向，包括風格指引、使用編輯器和工具的引導……等等。在編輯或建立任何頁面前，請先閱讀並確認同意 <a href="https://www.mozilla.org/zh-TW/about/legal/terms/mozilla/">Mozilla 網站與通訊使用條款</a>。</span></p>
+
+<p>如果之前你並沒有貢獻過 MDN 的話，<a href="/zh-TW/docs/MDN/Getting_started">開始入門</a>指南能幫你決定要投入的任務。</p>
+
+<p>{{LandingPageListSubPages()}}</p>
diff --git a/files/zh-tw/mdn/contribute/localize/index.html b/files/zh-tw/mdn/contribute/localize/index.html
new file mode 100644
index 0000000000..4d18dde8a4
--- /dev/null
+++ b/files/zh-tw/mdn/contribute/localize/index.html
@@ -0,0 +1,33 @@
+---
+title: Localizing MDN
+slug: MDN/Contribute/Localize
+tags:
+  - Documentation
+  - Localization
+  - MDN
+  - NeedsTranslation
+  - TopicStub
+translation_of: MDN/Contribute/Localize
+---
+<div>{{MDNSidebar}}</div><p><span style="">MDN 被全世界的人用來作為 Web 技術的參考和指南，甚至是 Firefox 開發團隊內部的人也使用 MDN。 我們的在地化社群是 Mozilla 社群的關鍵部分；他們將文件翻譯，並有助於世界各地進行 Web 開發的人們，使用他們自己的語言參考文件 如果您想了解有關在地化社群的更多資訊，請加入其中一個團隊，或者甚至開始翻譯新的文件。</span></p>
+
+<p>{{LandingPageListSubpages}}</p>
+
+<h2 id="在地化工具">在地化工具</h2>
+
+<p><span style="">你可以使用許多有用的工具來幫助你進行將文件在地化的工作：</span></p>
+
+<dl>
+ <dt><a href="/zh-TW/docs/Mozilla/Localization/Localizing_with_Pontoon">Pontoon</a></dt>
+ <dd>
+ <p style="margin: 0.5rem 0px; width: inherit; position: relative;" class="md-focus"><span style="" class="md-expand">是一個基於web網頁的、所見即所得（WYSIWYG）的在地化（l10n即localization）工具。</span></p>
+ </dd>
+ <dt><a href="http://transvision.mozfr.org/" title="http://transvision.mozfr.org/">Transvision</a></dt>
+ <dd><span style="">一個由 Mozilla 法國社群提供的工具。讓你可以搜尋某個英文單字出現的次數，並且可以找尋出所有翻譯該英文單字的該國語言文字。很適合用在，當你不知道某個單字或片語如何翻譯時。</span></dd>
+</dl>
+
+<h2 id="另可參閱">另可參閱</h2>
+
+<ul>
+ <li><a href="/en-US/docs/Mozilla/Localization" title="/en-US/docs/Mozilla/Localization">Localization at Mozilla</a></li>
+</ul>
diff --git a/files/zh-tw/mdn/contribute/localize/localization_projects/index.html b/files/zh-tw/mdn/contribute/localize/localization_projects/index.html
new file mode 100644
index 0000000000..026d2a7479
--- /dev/null
+++ b/files/zh-tw/mdn/contribute/localize/localization_projects/index.html
@@ -0,0 +1,1085 @@
+---
+title: 在地化專案
+slug: MDN/Contribute/Localize/Localization_projects
+translation_of: MDN/Contribute/Localize/Localization_projects
+---
+<div>{{MDNSidebar}}</div>
+
+<p><span class="seoSummary">所有在 MDN 上的在地化跟翻譯工作都是由一群志願者所完成的。這篇文章列出了在地化的專案以及積極貢獻這些專案的人們和一些細節。</span></p>
+
+<p>如果您想要開始貢獻翻譯，請參見 <a href="/en-US/docs/MDN/Contribute/Localize/Translating_pages">Translating MDN pages</a>.</p>
+
+<div class="note">
+<p><strong>備註:</strong> 如果你有意願接受其他貢獻者關於某個特定區域的在地化的聯繫，歡迎把你的名字加入本頁面。請確認你的 MDN 個人檔案頁面有聯繫你的方式，例如：推特 (Twitter) 或其他社群網站。如果頁面上的名字在過去 12 個月沒有任何貢獻，該名字會從頁面中被移除。</p>
+</div>
+
+<details><summary>
+<h2 id="af_Afrikaans">af: Afrikaans</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/af/dashboards/revisions?locale=af">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:af">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="ar_العربية_Arabic">ar: العربية [Arabic]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ar/dashboards/revisions?locale=ar">Latest changes</a></li>
+ <li><a href="/ar/docs/MDN/Doc_status/Overview">Status overview</a></li>
+ <li>Discussions</li>
+ <li><a href="https://pontoon.mozilla.org/ar/contributors/">Current contributors</a></li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:ar">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/ar/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="az_Azərbaycanca_Azerbaijani">az: Azərbaycanca [Azerbaijani]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/az/dashboards/revisions?locale=az">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors:</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:az">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/az/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="bg_Български_Bulgarian">bg: Български [Bulgarian]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/bg/dashboards/revisions?locale=bg">Latest changes</a></li>
+ <li>Status overview</li>
+ <li><a href="https://pontoon.mozilla.org/bg/contributors/">Current contributors</a></li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:bg">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/bg/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="bm_Bamanankan_Bambara">bm: Bamanankan [Bambara]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/bm/dashboards/revisions?locale=bm">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:bm">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="bn-BD_বাংলা_(বাংলাদেশ)_Bengali_Bangladesh">bn-BD: বাংলা (বাংলাদেশ) [Bengali, Bangladesh]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/bn-BD/dashboards/revisions?locale=bn-BD">Latest changes</a></li>
+ <li><a href="https://developer.mozilla.org/bn-BD/docs/MDN/Doc_status/Overview">Status overview</a></li>
+ <li>Discussions</li>
+ <li>Current contributors:</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:bn-BD">Mozilla localization project</a></li>
+ <li><a href="https://developer.mozilla.org/bn-BD/docs/Project:MDN/%E0%A6%85%E0%A6%AC%E0%A6%A6%E0%A6%BE%E0%A6%A8/mozillabd-l10n-team">MDN team page</a></li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/bn_BD/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="bn-IN_বাংলা_(ভারত)_Bengali_India">bn-IN: বাংলা (ভারত) [Bengali, India]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/bn-IN/dashboards/revisions?locale=bn-IN">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:bn-IN">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="ca_Català_Catalan">ca: Català [Catalan]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ca/dashboards/revisions?locale=ca">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:ca">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/ca/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="cs_Čeština_Czech">cs: Čeština [Czech]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/cs/dashboards/revisions?locale=cs">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:cs">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/cs/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="de_Deutsch_German">de: Deutsch [German]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/de/dashboards/revisions?locale=de">Latest changes</a></li>
+ <li><a href="https://developer.mozilla.org/de/docs/MDN/Doc_status/Overview">Status overview</a></li>
+ <li>Current contributors: {{userlink("fscholz")}}{{ref('*')}}, {{userlink("SebastianZ","Sebastian Zartner")}}, {{userlink("Shidigital")}}</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:de">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/de/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="ee_Eʋe_Ewe">ee: Eʋe [Ewe]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ee/dashboards/revisions?locale=ee">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Current contributors</li>
+ <li>Mozilla localization project</li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="el_Ελληνικά_Greek">el: Ελληνικά [Greek]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/el/dashboards/revisions?locale=el">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:el">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/el/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="es_Español_Spanish">es: Español [Spanish]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/es/dashboards/revisions?locale=es">Latest changes</a></li>
+ <li><a href="https://developer.mozilla.org/es/docs/MDN/Doc_status/Overview">Status overview</a></li>
+ <li>Current contributors: {{userlink("maedca","Manuel Camacho")}}{{ref('*')}}, {{userlink("StripTM")}}, {{userlink("Jorge.villalobos")}}</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:es">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li><a href="https://developer.mozilla.org/es/docs/Project%3AGu%C3%ADa_de_estilo">Conventions</a></li>
+ <li><a href="https://pontoon.mozilla.org/es/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="fa_فارسی_Persian">fa: فارسی [Persian]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/fa/dashboards/revisions?locale=fa">Latest changes</a></li>
+ <li><a href="https://developer.mozilla.org/fa/docs/MDN/Doc_status/Overview">Status overview</a></li>
+ <li>Current contributors:</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:fa">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/fa/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="ff_Pulaar-Fulfulde_Fulah">ff: Pulaar-Fulfulde [Fulah]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ff/dashboards/revisions?locale=ff">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:ff">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="fi_suomi_Finnish">fi: suomi [Finnish]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/fi/dashboards/revisions?locale=fi">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:fi">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details open><summary>
+<h2 id="fr_Français_French">fr: Français [French]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/fr/dashboards/revisions?locale=fr">Latest changes / Dernières éditions</a></li>
+ <li><a href="https://developer.mozilla.org/fr/docs/MDN/Doc_status/Overview">Status overview / Statut de la localisation</a></li>
+ <li><a href="http://mozfr.org/mailman/listinfo/moz-fr/">Discussions (moz-fr mailiing list)</a></li>
+ <li>Current contributors: {{userlink("Jeremie","Jeremie Patonnier")}}{{ref('*')}}, {{userlink("SphinxKnight", "Sphinx")}}{{ref('*')}}, {{userlink("BenoitL","Benoit Leseul")}}, {{userlink("tregagnon","Thierry Régagnon (tregagnon)")}}, {{userlink("Goofy")}}, {{userlink("Delapouite")}}</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:fr">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/fr/mdn/">Translate the MDN interface / Traduire l'interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="fy-NL_Frysk_(Netherlands)_Frisian">fy-NL: Frysk (Netherlands) [Frisian]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/fy-NL/dashboards/revisions?locale=fy-NL">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:fy-NL">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/fy-NL/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="ga-IE_Gaelige_(Ireland)_Gaelic">ga-IE: Gaelige (Ireland) [Gaelic]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ga-IE/dashboards/revisions?locale=ga-IE">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:ga-IE">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/ga-IE/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="ha_Hausa">ha: Hausa</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ha/dashboards/revisions?locale=ha">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:ha">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="he_עברית_Hebrew">he: עברית [Hebrew]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/he/dashboards/revisions?locale=he">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors:</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:he">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="hi-IN_हिन्दी_(भारत)_Hindi">hi-IN: हिन्दी (भारत) [Hindi]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/hi-IN/dashboards/revisions?locale=hi-IN">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors:</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:hi-IN">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="hr_Hrvatski_Croatian">hr: Hrvatski [Croatian]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/hr/dashboards/revisions?locale=hr">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:hr">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/hr/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="hu_magyar_Hungarian">hu: magyar [Hungarian]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/hu/dashboards/revisions?locale=hu">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:hu">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/hu/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="id_Bahasa_Indonesia_Indonesian">id: Bahasa Indonesia [Indonesian]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/id/dashboards/revisions?locale=id">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors:</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:id">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/id/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="ig_Igbo">ig: Igbo</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ig/dashboards/revisions?locale=ig">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:ig">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="it_Italiano_Italian">it: Italiano [Italian]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ig/dashboards/revisions?locale=it">Latest changes</a></li>
+ <li><a href="https://developer.mozilla.org/it/MDN/Doc_status/Overview">Status overview</a></li>
+ <li>Discussions: <a href="https://translate.googleusercontent.com/translate_c?depth=1&amp;hl=en&amp;rurl=translate.google.com&amp;sl=auto&amp;tl=en&amp;u=http://forum.mozillaitalia.org/&amp;usg=ALkJrhhzVkkb--9tarnQhoYRv6OonR79Tg">Mozilla Italia</a></li>
+ <li>Current contributors:</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:it">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li><a href="/it/MDN/Contribute/Localize/GuidaItaliano">How to help</a></li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/it/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="ja_日本語_Japanese">ja: 日本語 [Japanese]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ja/dashboards/revisions?locale=ja">Latest changes</a></li>
+ <li><a href="https://developer.mozilla.org/ja/docs/MDN/Doc_status/Overview">Status overview</a></li>
+ <li>Discussions: <a href="https://groups.google.com/forum/#!forum/mozilla-translations-ja">Mozilla.translations.ja</a></li>
+ <li>Current contributors: {{userlink("myakura","myakura (Masataka Yakura)")}}, {{userlink("yyss")}}, {{userlink("Marsf","Marsf (Masahiko Imanaka)")}}, {{userlink("Masayuki")}},  {{userlink("dynamis","dynamis (Tomoya Asai)")}}, {{userlink("mantaroh")}}, {{userlink("hamasaki")}}, {{userlink("mfuji09")}}</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:ja">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help: We are taking a bit long time in transition from old resources, <a href="https://developer.mozilla.org/ja/docs/Project:%E6%97%A5%E6%9C%AC%E8%AA%9E%E7%89%88">MDC Japan Project</a> (-2009), those include some useful information.</li>
+ <li><a href="/ja/docs/MDN/Contribute/Content/Writing_style_guide">Conventions</a></li>
+ <li><a href="https://pontoon.mozilla.org/ja/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="ka_ქართული_Georgian">ka: ქართული [Georgian]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ka/dashboards/revisions?locale=ka">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:ka">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="kab_Taqbaylit_Kabyle">kab: Taqbaylit [Kabyle]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://l10n.mozilla-community.org/webdashboard/?locale=kab">Mozilla localization Status Overview</a></li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:kab">Mozilla Kabyle localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+ <li><a href="https://www.mozilla.org/kab/">Mozilla.org Kabyle</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="ko_한국어_Korean">ko: 한국어 [Korean]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ko/dashboards/revisions?locale=ko">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions: <a href="https://groups.google.com/forum/#!forum/mdckorea">mdckorea</a></li>
+ <li>Current contributors:</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:ko">Mozilla localization project</a></li>
+ <li><a href="/ko/docs/Project:Korean_Contributors">MDN team page</a></li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/ko/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="ln_Lingála">ln: Lingála</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ln/dashboards/revisions?locale=ln">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li>Mozilla localization project</li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="mg_Malagasy">mg: Malagasy</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/mg/dashboards/revisions?locale=mg">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:mg">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="ml_മലയാളം_Malayalam">ml: മലയാളം [<span class="mw-headline" id="Malayalam_.28ml.2C_ml_IN.29">Malayalam]</span></h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ml/dashboards/revisions?locale=ml">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors:</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:ml">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="ms_Melayu_Malay">ms: Melayu [Malay]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ms/dashboards/revisions?locale=ms">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:ms">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="my_မြန်မာဘာသာ_Myanmar">my: မြန်မာဘာသာ [Myanmar]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/my/dashboards/revisions?locale=my">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors:</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:my">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="nl_Nederlands_Dutch">nl: Nederlands [Dutch]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/nl/dashboards/revisions?locale=nl">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:nl">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/nl/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="pl_Polski_Polish">pl: Polski [Polish]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/pl/dashboards/revisions?locale=pl">Latest changes</a></li>
+ <li><a href="https://developer.mozilla.org/pl/docs/MDN/Doc_status/Overview">Status overview</a></li>
+ <li>Discussions</li>
+ <li>Current contributors:</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:pl">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/pl/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="pt-BR_Português_(do_Brasil)_Portuguese_Brazil">pt-BR: Português (do Brasil) [Portuguese, Brazil]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/pt-BR/dashboards/revisions?locale=pt-BR">Latest changes</a></li>
+ <li><a href="https://developer.mozilla.org/pt-BR/docs/MDN/Doc_status/Overview">Status overview</a></li>
+ <li>Discussions</li>
+ <li>Current contributors:</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:pt-BR">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li><a href="http://mzl.la/Odmaq9">Como ajudar a MDN</a></li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/pt-BR/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="pt-PT_Português_(Europeu)_Portuguese_Portugal">pt-PT: Português (Europeu) [Portuguese, Portugal]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/pt-PT/dashboards/revisions?locale=pt-PT">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:pt-PT">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/pt-PT/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="ro_română_Romanian">ro: română [Romanian]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ro/dashboards/revisions?locale=ro">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors:</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:ro">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/ro/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details open><summary>
+<h2 id="ru_Русский_Russian">ru: Русский [Russian]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ru/dashboards/revisions?locale=ru">Latest changes</a></li>
+ <li><a href="https://developer.mozilla.org/ru/docs/MDN/Doc_status/Overview">Status overview</a></li>
+ <li>Discussions</li>
+ <li>Current contributors: {{userlink("bychekRU","Victor Bychek")}}</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:ru">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li><a href="/ru/docs/Project%3AWriter's_guide">Conventions</a></li>
+ <li><a href="https://pontoon.mozilla.org/ru/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="son_Soŋay_Songhay">son: Soŋay [Songhay]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/son/dashboards/revisions?locale=son">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:son">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="sr_Српски_Serbian">sr: Српски [Serbian]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/sr/dashboards/revisions?locale=sr">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors:</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:sr">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/sr/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="sq_Shqip_Albanian">sq: Shqip [Albanian]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/sq/dashboards/revisions?locale=sq">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:sq">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/sq/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="sv-SE_Svenska_Swedish">sv-SE: Svenska [Swedish]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/sv-SE/dashboards/revisions?locale=sv-SE">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:sv-SE">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/sv-SE/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="sw_Kiswahili_Swahili">sw: Kiswahili [Swahili]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/sw/dashboards/revisions?locale=sw">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:sw">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="ta_தமிழ்_Tamil">ta: தமிழ் [Tamil]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ta/dashboards/revisions?locale=ta">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:ta">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="te_తెలుగు_Telugu">te: తెలుగు [Telugu]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/ta/dashboards/revisions?locale=te">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:te">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/te/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="th_ไทย_Thai">th: ไทย [Thai]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/th/dashboards/revisions?locale=th">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:th">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/th/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="tl_Tagalog">tl: Tagalog</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/tl/dashboards/revisions?locale=tl">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:tl">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="tn_Setswana_Tswana">tn: Setswana [Tswana]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/tn/dashboards/revisions?locale=tn">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:tn">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="tr_Türkçe_Turkish">tr: Türkçe [Turkish]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/tr/dashboards/revisions?locale=tr">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:tr">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details open><summary>
+<h2 id="uk_Українська_Ukrainian">uk: Українська [Ukrainian]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/uk/dashboards/revisions?locale=uk">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors: {{userlink("asmforce", "asmforce (Крутько Віталій)")}}</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:uk">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/uk/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details open><summary>
+<h2 id="vi_Tiếng_Việt_Vietnamese">vi: Tiếng Việt [Vietnamese]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/vi/dashboards/revisions?locale=vi">Latest changes</a></li>
+ <li><a href="/vi/docs/MDN/Doc_status/Overview">Status overview</a></li>
+ <li>Discussions: <a href="https://gitter.im/mdn-vi-l10n">group chat on Gitter</a></li>
+ <li>Current contributors: see <a href="https://mdn-top-vi-contributors.netlify.com/">top vi contributors minisite</a> (created by {{userlink("trongthanh")}})</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:vi">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li><a href="https://developer.mozilla.org/vi/docs/MDN/Contribute/Localize/dich_trang">How to help</a></li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/vi/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="wo_Wolof">wo: Wolof</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/wo/dashboards/revisions?locale=wo">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:wo">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="xh_isiXhosa_Xhosa">xh: isiXhosa [Xhosa]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/xh/dashboards/revisions?locale=xh">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:xh">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="yo_Yorùbá">yo: Yorùbá</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/yo/dashboards/revisions?locale=yo">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:yo">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li>Translate the MDN interface</li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="zh-CN_中文_(简体)_Chinese_simplified">zh-CN: 中文 (简体) [Chinese, simplified]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/zh-CN/dashboards/revisions?locale=zh-CN">Latest changes</a></li>
+ <li><a href="https://developer.mozilla.org/zh-CN/docs/MDN/Doc_status/Overview">Status overview</a></li>
+ <li>Discussions: {{page("/zh-CN/docs/MDN/Contribute/Localize/Localization_projects", "notes")}}</li>
+ <li>Current contributors: {{page("/zh-CN/docs/MDN/Contribute/Localize/Localization_projects", "leader")}}{{ref('*')}}; see the team page for other contributors.</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:zh-CN">Mozilla localization project</a></li>
+ <li><a href="https://developer.mozilla.org/zh-CN/docs/MDN/Contribute/Localize/Localization_projects">MDN team page</a></li>
+ <li>How to help</li>
+ <li><a href="/zh-CN/docs/MDN/Contribute/Content/Style_guide">Conventions</a></li>
+ <li><a href="https://pontoon.mozilla.org/zh-CN/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details open><summary>
+<h2 id="zh-TW_中文_(繁體)_Chinese_traditional">zh-TW: 中文 (繁體) [Chinese, traditional]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/zh-TW/dashboards/revisions?locale=zh-TW">Latest changes</a></li>
+ <li><a href="https://developer.mozilla.org/zh-TW/docs/MDN/Doc_status/Overview">Status overview</a></li>
+ <li>Discussions: 我們需要更多貢獻者，請到 <a href="https://groups.google.com/group/moztw-general">MozTW-general 郵件群組</a>與我們聯繫！</li>
+ <li>Current contributors: {{userlink("irvinfly")}}{{ref('*')}}, {{userlink("BobChao")}}, {{userlink("petercpg")}}</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:zh-TW">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li><a href="/zh-TW/docs/MDN/Contribute/Content/Style_guide">Conventions</a></li>
+ <li><a href="https://pontoon.mozilla.org/zh-TW/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<details><summary>
+<h2 id="zu_isiZulu_Zulu">zu: isiZulu [Zulu]</h2>
+</summary>
+
+<ul>
+ <li><a href="https://developer.mozilla.org/zu/dashboards/revisions?locale=zu">Latest changes</a></li>
+ <li>Status overview</li>
+ <li>Discussions</li>
+ <li>Current contributors</li>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:zu">Mozilla localization project</a></li>
+ <li>MDN team page</li>
+ <li>How to help</li>
+ <li>Conventions</li>
+ <li><a href="https://pontoon.mozilla.org/zu/mdn/">Translate the MDN interface</a></li>
+</ul>
+</details>
+
+<p>The <a href="/en-US/docs/MDN/Community/Roles/Localization_driver_role">localization lead</a> is marked by {{ref('*')}}. This is the person who <span class="ZmSearchResult" id="DWT15474"><span class="ZmSearchResult" id="DWT15476"><span class="ZmSearchResult" id="DWT15515">leads</span></span></span> a localization community on MDN, guiding their work in localizing content for a specific locale or topic.</p>
+
+<h2 id="其他區域">其他區域</h2>
+
+<p>以下這些區域的在地化還沒有在 MDN 上，但可能有人想要貢獻這些區域。如果你對新增一個區域的在地化有興趣，請參見 <a href="/en-US/docs/MDN/Contribute/Localize/Starting_a_localization">Starting a new MDN localization</a> 。</p>
+
+<h3 id="gu_ગુજરાતી_Gujarati">gu: ગુજરાતી [Gujarati]</h3>
+
+<ul>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:gu-IN">Mozilla localization project</a></li>
+ <li>Interested users: {{userlink("prafull_satasiya")}}</li>
+</ul>
+
+<h3 id="lo_ພາສາລາວ_Lao">lo: ພາສາລາວ [Lao]</h3>
+
+<ul>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:lo">Mozilla localization project</a></li>
+ <li>Interested users: {{userlink("rcampbelllaos","Robert M Campbell")}}</li>
+</ul>
+
+<h3 id="si_සිංහල_Sinhalese">si: <strong>සිංහල [Sinhalese]</strong></h3>
+
+<ul>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:si">Mozilla localization project</a></li>
+ <li>Interested users: {{userlink("pkavinda")}}</li>
+</ul>
+
+<h3 id="ur_اردو_Urdu">ur: اردو [Urdu]</h3>
+
+<ul>
+ <li><a href="https://wiki.mozilla.org/L10n:Teams:ur">Mozilla localization project</a></li>
+ <li>Interested users:</li>
+</ul>
+
+<section id="Quick_Links">
+<ul>
+ <li><a href="/en-US/docs/MDN/Contribute/Localize/Translating_pages">Translating MDN pages</a></li>
+ <li><a href="/en-US/docs/MDN/Contribute/Localize/Starting_a_localization">Starting a new MDN localization</a></li>
+ <li><a href="/en-US/docs/Mozilla/Localization">Localizating Mozilla software and websites</a></li>
+ <li><a href="/en-US/docs/Mozilla/Localization/Localizing_with_Pontoon">Localizing with Pontoon</a></li>
+</ul>
+</section>
diff --git a/files/zh-tw/mdn/contribute/localize/translating_pages/index.html b/files/zh-tw/mdn/contribute/localize/translating_pages/index.html
new file mode 100644
index 0000000000..8b36f33fbd
--- /dev/null
+++ b/files/zh-tw/mdn/contribute/localize/translating_pages/index.html
@@ -0,0 +1,52 @@
+---
+title: 翻譯 MDN 頁面
+slug: MDN/Contribute/Localize/Translating_pages
+tags:
+  - 在地化
+  - 指南
+  - 頁面翻譯
+translation_of: MDN/Contribute/Localize/Translating_pages
+---
+<div>{{MDNSidebar}}</div>
+
+<p>本文為翻譯 MDN 內容提供基本指南，包括翻譯的運作機制及正確處理各種類型內容的訣竅。</p>
+
+<h2 id="開始翻譯新的頁面">開始翻譯新的頁面</h2>
+
+<p>當你來到一個欲翻譯成你的語言的頁面時，請按照下述步驟進行：</p>
+
+<ol>
+ <li>點選語言圖示（{{FontAwesomeIcon("icon-language")}}）以開啟<strong>語言</strong>選單，接著點選 <strong>Add a Translation</strong>，選擇語言頁面將會出現。</li>
+ <li>點選你想翻譯的語言，開啟翻譯文章介面。原文會顯示於畫面左側。</li>
+ <li>在<strong>翻譯描述</strong>裡，你可以翻譯標題並（選擇性的）翻譯「條目連結代碼」（slug）。條目連結代碼就是頁面網址的最末段（例如本文網址中的「Translating_pages」）。在某些語言社群中並不翻譯條目名稱，而會保持與英文一致。比較你語言中的其它文章，以了解習慣作法（編按：正體中文版本不翻譯 slug）。當你完成這部份時，你可以點選<strong>翻譯描述</strong>旁的減號將其隱藏，以讓出更多空間給<strong>內容翻譯</strong>的部份。</li>
+ <li>在<strong>翻譯內容</strong>裡翻譯頁面的內容。</li>
+ <li>為該頁面填至少一個<strong>標籤</strong>。</li>
+ <li>當你完成時點選<strong>儲存修改</strong>。</li>
+</ol>
+
+<div class="note"><strong>注意：</strong> 翻譯新文章的使用者介面會以英文顯示。 更新文章時，如果 MDN 的介面有被在地化，則會以適當的語言顯示翻譯介面。 MDN 的使用者介面可以在 <a href="https://pontoon.mozilla.org/projects/mdn/" title="https://pontoon.mozilla.org/projects/mdn/">Pontoon</a> 上進行在地化。請參見<a href="/zh-TW/docs/Mozilla/Localization/Localizing_with_Pontoon" title="/zh-TW/docs/Mozilla/Localization/Localizing_with_Pontoon">使用 Pontoon 來在地化</a>以詳細了解如何使用該工具。</div>
+
+<h2 id="編輯已翻譯的頁面">編輯已翻譯的頁面</h2>
+
+<ul>
+ <li>在已翻譯的頁面，點選 <strong>Edit</strong> 按鈕（有時會以目標語系呈現），即會開啟文章翻譯界面。</li>
+</ul>
+
+<p>如果英文原文在前次譯文更新之後有所變動，文章翻譯介面會以程式碼的風格，顯示英文版的「前後差異比對」，幫助你找到需要更新的部份。</p>
+
+<h2 id="翻譯標籤">翻譯標籤</h2>
+
+<p>幫每個頁面都標上至少一個標籤非常重要，即使這是譯文。</p>
+
+<p>某些標籤用於搜尋篩選、或是貢獻者之間的約定用法，它們不應該被翻譯。 想要知道有哪些標籤，請閱讀<a href="/en-US/docs/Project:MDN/Contributing/Tagging_standards">標籤準則</a>一文。如果文章還沒有被任何標準的標籤標記，你可以自由的建立翻譯過的標籤以將內容分組。</p>
+
+<h2 id="針對新譯者的指引">針對新譯者的指引</h2>
+
+<p>如果你是 MDN 的新譯者，這裡有些指引：</p>
+
+<ul>
+ <li>在 <a href="/zh-TW/docs/Glossary">Glossary</a> 的文章很適合新譯者翻譯，因為它們很簡短。</li>
+ <li><a href="/en-US/docs/tag/l10n%3Apriority">被標示為 "l10n:priority" </a> 的文章被認定是高優先翻譯。另外，教學與概念性文章的優先度，通常比參考頁面高，這是因為讀者在理解新觀念的時候，最需要翻譯的東西。</li>
+ <li>如果你看到兩個大括號的文字，例如 <code>\{{some-text("more text")}}</code>，讓它在文章內保持原樣、不要改動標點符號。這是 <a href="/zh-TW/docs/MDN/Contribute/Structures/Macros">Macro</a>，它可能用於創建頁面的架構、或其他的用途。你可能看到一些由 macro 產生的原文，在你從 MDN 得到更多經驗以前，不用操心這個（改變那邊的文字需要<a href="/zh-TW/docs/MDN/Contribute/Tools/Template_editing">特殊權限</a>，這是因為 macro 有著十分強大的效果）如果你感到好奇，可以看看 <a href="/zh-TW/docs/MDN/Contribute/Structures/Macros/Commonly-used_macros">Commonly-used macros</a> 來了解各種 macro 如何做動。</li>
+ <li>查看 <a href="/zh-TW/docs/MDN/Contribute/Localize/Localization_projects">Localization projects page</a> 以找出更多你語言的在地化。</li>
+</ul>
diff --git a/files/zh-tw/mdn/editor/basics/index.html b/files/zh-tw/mdn/editor/basics/index.html
new file mode 100644
index 0000000000..d33daf9aeb
--- /dev/null
+++ b/files/zh-tw/mdn/editor/basics/index.html
@@ -0,0 +1,55 @@
+---
+title: Editor UI elements
+slug: MDN/Editor/Basics
+translation_of: MDN/Editor/Basics
+---
+<div>{{MDNSidebar}}</div><p><span class="seoSummary">The built-in WYSIWYG editor on MDN is designed to make it as easy as possible to create, edit, and improve articles and other pages almost anywhere on the site.</span> The editor window, shown below, consists of eight key area. This guide provides information about each section so you know how to use our entire editing environment.</p>
+
+<div class="note">
+<p>We're constantly working on improvements to MDN, so there will be times when this documentation or the screen shots below may be slightly out-of-date. We'll periodically update this documentation, though, to avoid it being unusably behind.</p>
+</div>
+
+<p><img alt="Screenshot of the editor UI (August 2017) with each section labeled" src="https://mdn.mozillademos.org/files/15261/edit-page-with-labels.png" style="border-style: solid; border-width: 2px; height: 723px; width: 808px;"></p>
+
+<p>The editor UI contains the following sections, as shown above. Click a link below to read about that section of the editor.</p>
+
+<ul>
+ <li><a href="/en-US/docs/MDN/Contribute/Editor/Basics/Page_info">Page info</a></li>
+ <li><a href="/en-US/docs/MDN/Contribute/Editor/Basics/Page_controls">Page controls</a></li>
+ <li><a href="/en-US/docs/MDN/Contribute/Editor/Basics/Toolbar">Toolbar</a></li>
+ <li><a href="/en-US/docs/MDN/Contribute/Editor/Edit_box">Edit box</a></li>
+ <li><a href="/en-US/docs/MDN/Contribute/Editor/Basics/Tags">Tags</a></li>
+ <li><a href="#Revision_comment">Revision comment</a></li>
+ <li><a href="#Review_requests">Review requests</a></li>
+ <li><a href="/en-US/docs/MDN/Contribute/Editor/Basics/Attachments">Attachments</a></li>
+</ul>
+
+<h2 id="Revision_comment">Revision comment</h2>
+
+<p>After you've made your changes, it's strongly recommended you add a comment to your revision. This is displayed in the revision history for the page, as well as on the <a href="/en-US/dashboards/revisions" title="/en-US/dashboards/revisions">Revision Dashboard</a>. It helps to explain or justify your changes to others that may review your work later. To add a revision comment, simply type the note into the revision comment box before clicking either of the <strong>Publish</strong> buttons at the top or bottom of the page.</p>
+
+<p>There are a few reasons this is helpful:</p>
+
+<ul>
+ <li>If the reason for your change isn't obvious, your note can explain the reasoning to others.</li>
+ <li>If your change is technically complex, it can explain to editors the logic behind it; this can include a bug number, for example, that editors can refer to for more information.</li>
+ <li>If your edit involves deleting a large amount of content, you can justify the deletion (for example, "I moved this content to article X").</li>
+</ul>
+
+<h2 id="Review_requests">Review requests</h2>
+
+<p>The MDN community uses <strong>reviews</strong> to try to monitor and improve the quality of MDN's content. This works by setting a flag on an article indicating that a review is needed. You can learn more about <a href="/en-US/docs/MDN/Contribute/Howto/Do_a_technical_review" title="/en-US/docs/Project:MDN/Contributing/How_to_help#Content_reviews">technical reviews</a> and <a href="/en-US/docs/MDN/Contribute/Howto/Do_an_editorial_review">editorial review</a> in the <a href="/en-US/docs/MDN/Contribute/Howto" title="/en-US/docs/Project:MDN/Contributing/How_to_help">How to</a> guides.</p>
+
+<p>To request a review on the article you've worked on, toggle on the checkbox next to the type of review that's needed. Technical reviews should be requested any time you make changes to the explanation of how something technical works, while editorial reviews are a good idea when you've made changes and would like someone to review your writing and style choices.</p>
+
+<p>While selecting a review checkbox adds the article to the lists of those <a href="/en-US/docs/needs-review/technical">needing technical review</a> or <a href="/en-US/docs/needs-review/editorial">needing editorial review</a>, it does not guarantee that anyone will immediately review the article. For technical reviews, it's a good idea to directly contact a <a href="/en-US/docs/MDN/Community/Roles/Subject-matter_experts">subject-matter expert</a> in the relevant technical area. For editorial reviews, you can post in the <a href="/https://discourse.mozilla.org/c/mdn">MDN discussion forum</a> to request that someone review your changes.</p>
+
+<p>Be sure to click one of the <strong>Publish</strong> buttons after making your selections, to commit your review request.</p>
+
+<h2 id="See_also">See also</h2>
+
+<ul>
+ <li><a href="http://docs.cksource.com/CKEditor_3.x/Users_Guide">CKEditor User's Guide</a></li>
+</ul>
+
+<h6 id="EditorGuideQuicklinks">{{EditorGuideQuicklinks}}<span id="cke_bm_73C" style="display: none;"> </span></h6>
diff --git a/files/zh-tw/mdn/editor/edit_box/index.html b/files/zh-tw/mdn/editor/edit_box/index.html
new file mode 100644
index 0000000000..3c691a124b
--- /dev/null
+++ b/files/zh-tw/mdn/editor/edit_box/index.html
@@ -0,0 +1,134 @@
+---
+title: Edit box of the MDN editor
+slug: MDN/Editor/Edit_box
+translation_of: MDN/Editor/Keyboard_shortcuts
+---
+<div>{{MDNSidebar}}</div><p>The edit box is, of course, where you actually do your writing. Right-clicking in the editor box offers appropriate additional options depending on the context of your click: right-clicking in a table offers table-related options and right-clicking in a list offers list-related options, for example.</p>
+
+<p>By default, the editor uses its own contextual menu when you right-click on the editor. To access your browser's default contextual menu (such as to access the Firefox spell checker's list of suggested corrections), hold down the <kbd>Shift</kbd> or <kbd>Control</kbd> key (the <kbd>Command</kbd> key on Mac OS X) while clicking.</p>
+
+<h2 id="鍵盤快捷鍵">鍵盤快捷鍵</h2>
+
+<p>There are a number of convenient keyboard shortcuts available to help you avoid taking your hands off the keyboard while you work. The shortcuts are listed for Windows and Linux; on Mac, instead of using the <kbd>Control</kbd> key, you can use the <kbd>Command</kbd> key.</p>
+
+<table class="standard-table">
+ <colgroup>
+  <col style="width: 15em;">
+ </colgroup>
+ <tbody>
+  <tr>
+   <th>快捷鍵</th>
+   <th>說明</th>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>A</kbd></td>
+   <td>全選</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>C</kbd></td>
+   <td>複製到剪貼簿</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>V</kbd></td>
+   <td>從剪貼簿貼上</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>X</kbd></td>
+   <td>剪下</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>Z</kbd></td>
+   <td>回到上一步</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>Y</kbd></td>
+   <td>重置</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>K</kbd></td>
+   <td>開啟連結編輯器／新增連結</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>K</kbd></td>
+   <td>移除連結游標位置。</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>B</kbd></td>
+   <td>粗體</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>I</kbd></td>
+   <td>斜體</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>O</kbd></td>
+   <td>切換 <code>&lt;code&gt;</code> 樣式。</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>O</kbd></td>
+   <td>
+    <p>切換原始碼顯示模式。</p>
+
+    <div class="note">在原始碼模式下編輯時請小心，您需要遵守我們的內容標準。更多細節關於如何使用原始碼模式與使用之優缺點請參照<a href="/en-US/docs/MDN/Contribute/Editor/Source_mode">原始碼模式編輯教學</a>。</div>
+   </td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>P</kbd></td>
+   <td>切換 <code>&lt;pre&gt;</code> 樣式在當前區塊中的開啟與關閉。</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>U</kbd></td>
+   <td>底線。</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>S</kbd></td>
+   <td>儲存修改並關閉編輯器。</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>S</kbd></td>
+   <td>儲存修改但不要關閉編輯器。</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>0</kbd></td>
+   <td>Remove formatting from the selected area (That's a zero, not the letter "O").</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>2</kbd> through <kbd>Ctrl</kbd> + <kbd>6</kbd></td>
+   <td>Select heading level 2 through 6. Heading level 1 is reserved for the page title displayed at the top of the article.</td>
+  </tr>
+  <tr>
+   <td><kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>L</kbd></td>
+   <td>Toggle from bulleted list to numbered list to and paragraph format</td>
+  </tr>
+  <tr>
+   <td><kbd>Tab</kbd></td>
+   <td>Increase indent level if in indent mode, otherwise inserts two spaces as a tab. Inside tables, this moves the cursor to the next cell, or inserts a new row if there is no next cell. If the cursor is currently in the page title or in a heading, the cursor jumps to the next paragraph.</td>
+  </tr>
+  <tr>
+   <td><kbd>Shift</kbd> + <kbd>Tab</kbd></td>
+   <td>Decrease indent level if in indent mode. Inside tables, this jumps to the previous cell, or inserts a new row if there is no previous cell. If the cursor is currently in the page title or in a heading, the cursor jumps to the next paragraph.</td>
+  </tr>
+  <tr>
+   <td><kbd>Shift</kbd> + <kbd>Space</kbd></td>
+   <td>Insert a non-breaking space (<code>&amp;nbsp;</code>)</td>
+  </tr>
+  <tr>
+   <td><kbd>Shift</kbd> + <kbd>Enter</kbd></td>
+   <td>
+    <p>Exits out of the current block. For example, if you're currently editing a <code>&lt;pre&gt;</code> block, <kbd>Shift</kbd> + <kbd>Enter</kbd> exits the block, putting you back in the body of the article.</p>
+
+    <div class="note style-wrap">
+    <p>Not currently implemented; see {{bug(780055)}}.</p>
+    </div>
+   </td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="See_also">See also</h2>
+
+<ul>
+ <li><a href="/en-US/docs/MDN/Contribute/Editor/Basics">Editor UI elements</a></li>
+ <li><a href="/en-US/docs/MDN/Contribute">Contributing to MDN</a></li>
+ <li><a href="/en-US/docs/MDN/Getting_started">Getting started on MDN</a></li>
+</ul>
diff --git a/files/zh-tw/mdn/editor/index.html b/files/zh-tw/mdn/editor/index.html
new file mode 100644
index 0000000000..5cf0ac0a43
--- /dev/null
+++ b/files/zh-tw/mdn/editor/index.html
@@ -0,0 +1,23 @@
+---
+title: Guide to the MDN editor UI
+slug: MDN/Editor
+tags:
+  - Documentation
+  - Guide
+  - Landing
+  - MDN
+  - MDN Meta
+  - 指南
+translation_of: MDN/Editor
+---
+<div>{{MDNSidebar}}</div><div>{{IncludeSubnav("/zh-TW/docs/MDN")}}</div>
+
+<p><span class="seoSummary">MDN線上文件百科的WYSIWYG (what-you-see-is-what-you-get) 所見即所得編輯器讓人可以輕鬆地對新內容做出貢獻。</span></p>
+
+<p><span class="seoSummary">這個指南將教會您如何使用編輯器以及提升你的生產力，在您開始編輯或創造新頁面前，請先閱讀並同意遵守<a href="https://www.mozilla.org/en-US/about/legal/terms/mozilla/">Mozilla Terms</a> 。</span></p>
+
+<p><a href="/en-US/docs/MDN/Contribute/Content/Style_guide" title="Read the MDN style guide">MDN style guide</a> 提供了內容的編排方法與風格，其中包含了我們建議的文法與拼字規則。</p>
+
+<p>{{LandingPageListSubpages}}</p>
+
+<p>{{EditorGuideQuicklinks}}</p>
diff --git a/files/zh-tw/mdn/guidelines/index.html b/files/zh-tw/mdn/guidelines/index.html
new file mode 100644
index 0000000000..da94b5a289
--- /dev/null
+++ b/files/zh-tw/mdn/guidelines/index.html
@@ -0,0 +1,13 @@
+---
+title: MDN 內容與風格指南
+slug: MDN/Guidelines
+tags:
+  - Documentation
+  - Landing
+  - MDC Project
+  - MDN
+translation_of: MDN/Guidelines
+---
+<div>{{MDNSidebar}}</div><p><span class="seoSummary">這些指南說明 MDN 文件該如何撰寫及格式化，及我們的範例程式與其他內容該如何呈現。</span> 跟著這些指南進行，你就可以確保你的產出既乾淨又便於使用。</p>
+
+<p>{{LandingPageListSubpages}}</p>
diff --git a/files/zh-tw/mdn/guidelines/writing_style_guide/index.html b/files/zh-tw/mdn/guidelines/writing_style_guide/index.html
new file mode 100644
index 0000000000..39d4d22e9a
--- /dev/null
+++ b/files/zh-tw/mdn/guidelines/writing_style_guide/index.html
@@ -0,0 +1,567 @@
+---
+title: MDN 風格指南
+slug: MDN/Guidelines/Writing_style_guide
+translation_of: MDN/Guidelines/Writing_style_guide
+---
+<div>{{MDNSidebar}}</div>
+
+<p><span class="seoSummary">為了讓文檔更加組織化、標準化而易於閱讀，MDN 風格指南描述了文本的組織方式、拼寫和格式等問題。</span>這些規則只是指導方針而非強制規定。與格式相比，我們對內容更感興趣，因此在你做貢獻之前，大可不必因為沒有學習本指南而感到驚訝或沮喪，只管放手去做便是。勤勞的志願者們會編輯你的工作以符合本指南。</p>
+
+<p>如果你在尋找頁面應當如何結構化的具體方式，參見 <a href="/zh-CN/docs/MDN/Contribute/Content/Layout" style="line-height: 1.5;">MDN 頁面配置指南</a>。</p>
+
+<p>在語言方面，本指南主要適用於英語文檔，其它語言可擁有（且歡迎創建）自己的風格指南。它們應作為當地語系化團隊頁面的子頁面發佈。</p>
+
+<p>有關 MDN 以外網站內容的風格標準，請參考 <a href="http://www.mozilla.org/zh-CN/styleguide/" title="http://www.mozilla.org/en-US/styleguide/">Mozilla 風格指南</a>。</p>
+
+<h2 id="Page_name_and_heading_capitalization" name="Page_name_and_heading_capitalization">基礎</h2>
+
+<p>維持整份文件的一致性是各大文件發表風格指南的基礎。以下段落將會列出這些基礎概念來協助您。</p>
+
+<h3 id="頁面標題">頁面標題</h3>
+
+<p>頁面標題會展示於搜索結果中，也可用於在頂部的麵包屑導航列中的層次結構以建構頁面。頁面標題可以與頁面“縮略名”不同。縮略名會出現在“<em>&lt;locale&gt;/docs/”後，是頁面URL的一部分。</em></p>
+
+<h4 id="標題與頁首的大小寫">標題與頁首的大小寫</h4>
+
+<p>頁面標題與章節標題應使用一般句子的大小寫形式（只大寫句首字母和專有名詞）， 而非新聞式標題。</p>
+
+<ul>
+ <li><span class="correct"><strong>正確</strong></span>：“A new method for creating JavaScript rollovers”</li>
+ <li><span class="incorrect"><strong>錯誤</strong></span>：“A New Method for Creating JavaScript Rollovers”</li>
+</ul>
+
+<p>有些舊的頁面編寫於本樣式規則定版之前。若你願意，可隨時更新它們。我們會逐漸完善它們。</p>
+
+<h4 id="選擇標題與簡述">選擇標題與簡述</h4>
+
+<p>頁面縮略名應保持簡短；當創建新的層級時， 該層次的縮略名通常應只由一兩個單詞組成。</p>
+
+<p>至於頁面標題，只要在合理範圍內，長度可以隨意，不過它應當是描述性的。</p>
+
+<h4 id="創建新子樹">創建新子樹</h4>
+
+<p>當你需要添加關於某個主題或主題範圍的文章時，一般可以創建一個登陸頁面，然後為這些文章分別添加子頁面。登陸頁面應當以一兩段對該主題或技術的描述開頭，接著提供一個子頁面的清單，並對每個子頁面做簡短的描述。你可以用一些我們創建的巨集來將頁面自動插入到該清單中。</p>
+
+<p>以 <a href="/zh-TW/docs/Web/JavaScript">JavaScript</a> 指南為例，它的結構如下：</p>
+
+<ul>
+ <li><a href="/zh-TW/docs/Web/JavaScript/Guide" title="JavaScript/Guide">JavaScript/指南</a> - 主內容表頁面</li>
+ <li><a href="/zh-TW/docs/Web/JavaScript/Guide/JavaScript_Overview" title="JavaScript/Guide/JavaScript_Overview">JavaScript/指南/JavaScript 概述</a></li>
+ <li><a href="/zh-TW/docs/JavaScript/Guide/Functions" title="JavaScript/Guide/Functions">JavaScript/指南/函數</a></li>
+ <li><a href="/zh-TW/docs/JavaScript/Guide/Details_of_the_Object_Model" title="JavaScript/Guide/Details_of_the_Object_Model">JavaScript/指南/物件模型細節</a></li>
+</ul>
+
+<p>請儘量避免將你的文章放在頂層，不然會拖慢網站的下載速度，降低網站導航和搜索的效率。</p>
+
+<h3 id="Sections.2C_Paragraphs.2C_Newlines" name="Sections.2C_Paragraphs.2C_Newlines">章節、段落與換行</h3>
+
+<p>請按照遞增順序使用標題級別：首先是 {{HTMLElement("h2")}}，其次是{{HTMLElement("h3")}}，接著是 {{HTMLElement("h4")}}，不要跳過級別。H2 是允許的最高級別，因為 H1 要留給頁面標題。若你需要超過四、五個級別的標題，請考慮將該文章拆分為幾篇更小的文章並創建登陸頁面，然後用巨集 {{TemplateLink("Next")}}、{{TemplateLink("Previous")}} 和 {{TemplateLink("PreviousNext")}} 將他們連結起來。</p>
+
+<p>在你鍵盤上的 Enter (或 return) 鍵會開一個新的段落。如果希望插入新的一行中間沒有空白，就同時按下 Shift 和 Enter 鍵。</p>
+
+<p>Don't create single subsections -- you don't subdivide a topic into one. It's either two subheadings or more or none at all. </p>
+
+<p>Don't have bumping heads, which are headings followed immediately by headings. Aside from looking horrible, it's helpful to readers if every heading has at least a brief intro after it to introduce the subsections beneath.</p>
+
+<h3 id="Text_Formatting" name="Text_Formatting">文本格式與樣式</h3>
+
+<p>請使用“樣式”下拉清單來為選中的內容應用預定義的樣式。</p>
+
+<div class="note"><strong>注意： </strong>“注意” 樣式用於重要的注意事項，就像這樣。</div>
+
+<div class="warning"><strong>警告：</strong>同樣，“警告”樣式用於創建警告框，就像這樣。</div>
+
+<p>除非有明確指令，否則<strong>請勿</strong>使用 HTML 的 <code>style</code> 屬性來手動更改內容的風格。如果你無法使用預先定義的 class 來達成目的，就將他丟到 {{IRCLink("mdn")}} 以尋求協助。</p>
+
+<h3 id="範例程式的樣式與格式">範例程式的樣式與格式</h3>
+
+<h4 id="縮排與換行">縮排與換行</h4>
+
+<p>所有的程式碼範例，一個縮排使用兩個空白鍵。程式碼縮排要整潔、左大括號（ { ）和開展一段區域的宣稱同行。例如：</p>
+
+<pre class="brush: js notranslate">if (condition) {
+  /* handle the condition */
+} else {
+  /* handle the "else" case */
+}
+</pre>
+
+<p>一行不能長到要橫向滾動才能閱讀，應當於自然斷點處換行。例如：</p>
+
+<pre class="brush: js notranslate">if (class.CONDITION || class.OTHER_CONDITION || class.SOME_OTHER_CONDITION
+       || class.YET_ANOTHER_CONDITION ) {
+  /* something */
+}
+
+var toolkitProfileService = Components.classes["@mozilla.org/toolkit/profile-service;1"]
+                           .createInstance(Components.interfaces.nsIToolkitProfileService);
+</pre>
+
+<h4 id="行內程式碼樣式">行內程式碼樣式</h4>
+
+<p>按下 Code 按鈕（標示為一對尖括號 &lt;&gt; ）套用到函式、變數、以及方法名稱的行內程式碼（這用到了 {{HTMLElement("code")}} 元素），例如 <code class="js plain">frenchText()</code> 函式。</p>
+
+<p>方法名稱要跟著一對小括號：<code>doSomethingUseful()</code>，這能讓該方法與其他程式碼術語做出辨別。</p>
+
+<h4 id="語法高亮">語法高亮</h4>
+
+<p><img alt='Screenshot of the "syntax highlighting" menu.' src="https://mdn.mozillademos.org/files/7857/syntax-highlighting-menu.png" style="border-style: solid; border-width: 1px; float: right; height: 315px; margin: 2px 4px; width: 183px;">Entire lines (or multiple lines) of code should be formatted using syntax highlighting rather than the {{HTMLElement("code")}} element. Click the "pre" button in the toolbar to create the preformatted content box in which you'll then write your code. Then, with the text entry cursor inside the code box, select the appropriate language from the language list button to the right of the "pre" button, as seen in the screenshot to the right. The following example shows text with JavaScript formatting:</p>
+
+<div class="line number2 index1 alt1">
+<pre class="brush: js notranslate">for (var i = 0, j = 9; i &lt;= 9; i++, j--)
+  document.writeln("a[" + i + "][" + j + "]= " + a[i][j]);</pre>
+</div>
+
+<p>If no appropriate transformation is available, use the <code>pre</code> tag without specifying a language ("No Highlight" in the language menu).</p>
+
+<pre class="notranslate">x = 42;</pre>
+
+<h4 id="HTML_元素風格參考">HTML 元素風格參考</h4>
+
+<p>There are various specific rules to follow when writing about HTML elements, in order to consistently describe the various components of elements, and to ensure that they're properly linked to detailed documentation.</p>
+
+<dl>
+ <dt>元素名</dt>
+ <dd>請使用 {{TemplateLink("HTMLElement")}} macro，它可以導向該元素的網頁連結。例如說，寫 \{{HTMLElement("title")}} 就會產生 {{HTMLElement("title")}}。如果不想要有連結，<strong>使用尖括號把名字包起來</strong> ，然後套用 Code (inline) 樣式（例如 <code>&lt;title&gt;</code>）。</dd>
+ <dt>屬性名</dt>
+ <dd>請使用 <strong>粗體</strong></dd>
+ <dt>屬性定義</dt>
+ <dd>針對 definition term，請使用 {{TemplateLink("htmlattrdef")}} macro（例如 <span class="nowiki">\{{htmlattrdef("type")}}</span>）so that it can be linked to from other pages, then use the {{TemplateLink("htmlattrxref")}} macro (e.g., <span class="nowiki">\{{htmlattrxref("attr","element")}}</span>) to reference attribute definitions.</dd>
+ <dt>屬性值</dt>
+ <dd>Use "Code (inline)" style, and do not use quotation marks around strings, unless needed by the syntax of a code sample. E.g.: When the <strong>type</strong> attribute of an <code>&lt;input&gt;</code> element is set to <code>email</code> or <code>tel</code> ...</dd>
+ <dt>Labeling attributes</dt>
+ <dd>Use labels like {{HTMLVersionInline(5)}} thoughtfully. For example, use them next to the bold attribute name but not for every occurrence in your body text.</dd>
+</dl>
+
+<h3 id="Latin_abbreviations" name="Latin_abbreviations">拉丁語縮寫</h3>
+
+<h4 id="In_notes_and_parentheses" name="In_notes_and_parentheses">在注記與括弧中</h4>
+
+<ul>
+ <li>常見的拉丁縮寫（etc.、i.e.、e.g.）可以在括號表達、或注記內使用。這些縮寫都要用半形句點（.）。
+  <ul>
+   <li><span class="correct"><strong>正確</strong></span>：Web browsers (e.g. Firefox) can be used ...</li>
+   <li><span class="incorrect"><strong>錯誤</strong></span>：Web browsers e.g. Firefox can be used ...</li>
+   <li><span class="incorrect"><strong>錯誤</strong></span>：Web browsers, e.g. Firefox, can be used ...</li>
+   <li><span class="incorrect"><strong>錯誤</strong></span>：Web browsers, (eg: Firefox) can be used ...</li>
+  </ul>
+ </li>
+</ul>
+
+<h4 id="In_running_text" name="In_running_text">在行文中</h4>
+
+<ul>
+ <li>在普通行文中（也就是注記與括號以外的文字）請使用與該縮寫相等的文字表達。
+  <ul>
+   <li><span class="correct"><strong>正確</strong></span>: ... web browsers, and so on.</li>
+   <li><span class="incorrect"><strong>錯誤</strong></span>: ... web browsers, etc.</li>
+   <li><span class="correct"><strong>正確</strong></span>: Web browsers such as Firefox can be used ...</li>
+   <li><span class="incorrect"><strong>錯誤</strong></span>: Web browsers e.g. Firefox can be used ...</li>
+  </ul>
+ </li>
+</ul>
+
+<h4 id="Meanings_and_English_equivalents_of_Latin_abbreviations" name="Meanings_and_English_equivalents_of_Latin_abbreviations">與拉丁文意義相同的中/英文</h4>
+
+<table class="fullwidth-table">
+ <tbody>
+  <tr>
+   <th>縮寫</th>
+   <th>拉丁文</th>
+   <th>英文</th>
+   <th>中文</th>
+  </tr>
+  <tr>
+   <td>cf.</td>
+   <td><em>confer</em></td>
+   <td>compare</td>
+   <td>對比，比較</td>
+  </tr>
+  <tr>
+   <td>e.g.</td>
+   <td><em>exempli gratia</em></td>
+   <td>for example</td>
+   <td>例如</td>
+  </tr>
+  <tr>
+   <td>et al.</td>
+   <td><em>et alii</em></td>
+   <td>and others</td>
+   <td>什麼的，以及其他</td>
+  </tr>
+  <tr>
+   <td>etc.</td>
+   <td><em>et cetera</em></td>
+   <td>and so forth, and so on</td>
+   <td>等等，諸如此類</td>
+  </tr>
+  <tr>
+   <td>i.e.</td>
+   <td><em>id est</em></td>
+   <td>that is, in other words</td>
+   <td>即，換言之</td>
+  </tr>
+  <tr>
+   <td>N.B.</td>
+   <td><em>nota bene</em></td>
+   <td>note well</td>
+   <td>注意</td>
+  </tr>
+  <tr>
+   <td>P.S.</td>
+   <td><em>post scriptum</em></td>
+   <td>postscript</td>
+   <td>注，附言</td>
+  </tr>
+ </tbody>
+</table>
+
+<div class="note">
+<p><strong>注意：</strong>永遠考慮使用拉丁語縮寫的收益。有些縮寫很少用到、多數讀者並不明白其意義，或常常與其他縮寫搞混。如果你要用，也請確定<strong>你</strong>用對了，像常見的錯誤是把「e.g.」與「i.e.」搞混。</p>
+</div>
+
+<h3 id="Acronyms_and_abbreviations" name="Acronyms_and_abbreviations">縮寫與簡稱</h3>
+
+<h4 id="Capitalization_and_periods" name="Capitalization_and_periods">大小寫與點號</h4>
+
+<p>所有的縮寫與簡稱都要大寫、並把半形句點刪除，就算是「US」與「UN」之類的組織也一樣。</p>
+
+<ul>
+ <li><span class="correct"><strong>正確</strong></span>：XUL</li>
+ <li><span class="incorrect"><strong>錯誤</strong></span>：X.U.L.</li>
+ <li><span class="incorrect"><strong>錯誤</strong></span>：Xul</li>
+</ul>
+
+<h4 id="Expansion" name="Expansion">全名</h4>
+
+<p>On the first mention of a term on a page, expand acronyms likely to be unfamiliar to users. When in doubt, expand it, or, better, link it to the article or <a href="/en-US/docs/Glossary">glossary</a> entry describing the technology.</p>
+
+<ul>
+ <li><span class="correct"><strong>Correct</strong></span>: "XUL (XML User Interface Language) is Mozilla's XML-based language..."</li>
+ <li><span class="incorrect"><strong>Incorrect</strong></span>: "XUL is Mozilla's XML-based language..."</li>
+</ul>
+
+<h4 id="Plurals_of_acronyms_and_abbreviations" name="Plurals_of_acronyms_and_abbreviations">縮寫與簡寫的複數形式</h4>
+
+<p>For plurals of acronyms or abbreviations, add <em>s</em>. Don't use an apostrophe. Ever. Please.</p>
+
+<ul>
+ <li><span class="correct"><strong>Correct</strong></span>: CD-ROMs</li>
+ <li><span class="incorrect"><strong>Incorrect</strong></span>: CD-ROM's</li>
+</ul>
+
+<h3 id="Contractions" name="Contractions">大小寫</h3>
+
+<p>Use standard English capitalization rules in body text, and capitalize "World Wide Web" and "Web".</p>
+
+<p>Keyboard keys should use sentence-style capitalization, not all-caps capitalization. For example, "Enter" not "ENTER."</p>
+
+<h3 id="Contractions" name="Contractions">縮寫</h3>
+
+<p>Use contractions (e.g. "don't", "can't", "shouldn't") if you prefer. We're not that formal!</p>
+
+<h3 id="Pluralization" name="Pluralization">複數形式</h3>
+
+<p>Use English-style plurals, not the Latin- or Greek-influenced forms.</p>
+
+<ul>
+ <li><span class="correct"><strong>Correct</strong></span>: syllabuses, octopuses</li>
+ <li><span class="incorrect"><strong>Incorrect</strong></span>: syllabi, octopi</li>
+</ul>
+
+<h3 id="Hyphenation" name="Hyphenation">連字號</h3>
+
+<p>Hyphenate compounds when the last letter of the prefix is a vowel and is the same as the first letter of the root.</p>
+
+<ul>
+ <li><font color="green"><strong>Correct</strong></font>: email, re-elect, co-op</li>
+ <li><font color="red"><strong>Incorrect</strong></font>: e-mail, reelect, coop</li>
+</ul>
+
+<h3 id="性別中立的用語">性別中立的用語</h3>
+
+<p>It is a good idea to use gender-neutral language in any kind of writing where gender is irrelevant to the subject matter, to make the text as inclusive as possible. So for example, if you are talking about the actions of a specific man, usage of he/his would be fine, but if the subject is a person of either gender, he/his isn't really appropriate.<br>
+ <br>
+ Let's take the following example:</p>
+
+<blockquote>
+<p>A confirmation dialog appears, asking the user if he allows the web page to make use of his web cam.</p>
+</blockquote>
+
+<blockquote>
+<p>A confirmation dialog appears, asking the user if she allows the web page to make use of her web cam.</p>
+</blockquote>
+
+<p>Both versions in this case are gender-specific. This could be fixed by using gender-neutral pronouns:</p>
+
+<blockquote>
+<p>A confirmation dialog appears, asking the user if they allow the web page to make use of their web cam.</p>
+</blockquote>
+
+<div class="note">
+<p><strong>Note:</strong> MDN allows the use of this very common syntax (which is controversial among usage authorities), in order to make up for the lack of a neutral gender in English. The use of the third-person plural as a neutral gender pronoun (that is, using "they," them", "their," and "theirs") is an accepted practice, commonly known as "<a href="http://en.wikipedia.org/wiki/Singular_they">singular 'they.'</a>"</p>
+</div>
+
+<p>You can use both genders:</p>
+
+<blockquote>
+<p>A confirmation dialog appears, asking the user if he or she allows the web page to make use of his/her web cam.</p>
+</blockquote>
+
+<p>making the users plural:</p>
+
+<blockquote>
+<p>A confirmation dialog appears, asking the users if they allow the web page to make use of their web cams.</p>
+</blockquote>
+
+<p>The best solution, of course, is to rewrite and eliminate the pronouns completely:</p>
+
+<blockquote>
+<p>A confirmation dialog appears, requesting the user's permission for web cam access.</p>
+</blockquote>
+
+<blockquote>
+<p>A confirmation dialog box appears, which asks the user for permission to use the web cam.</p>
+</blockquote>
+
+<p>The last way of dealing with the problem is arguably better, as it is not only grammatically more correct but removes some of the complexity associated with dealing with genders across different languages that may have wildly varying gender rules. This can make translation easier, both for readers reading English, then translating it into their own language as they read, and for localizers translating articles into their own language.</p>
+
+<h3 id="Numbers_and_numerals" name="Numbers_and_numerals">數字與數詞</h3>
+
+<h4 id="日期">日期</h4>
+
+<p>For dates (not including dates in code samples) use the format "January 1, 1990".</p>
+
+<ul>
+ <li><span class="correct"><strong>Correct</strong></span>: February 24, 2006</li>
+ <li><span class="incorrect"><strong>Incorrect</strong></span>: February 24th, 2006; 24 February, 2006; 24/02/2006</li>
+</ul>
+
+<p>Alternately, you can use the YYYY/MM/DD format.</p>
+
+<ul>
+ <li><span class="correct"><strong>Correct</strong></span>: 2006/02/24</li>
+ <li><span class="incorrect"><strong>Incorrect</strong></span>: 02/24/2006; 24/02/2006; 02/24/06</li>
+</ul>
+
+<h4 id="Decades" name="Decades">年代</h4>
+
+<p>For decades, use the format "1990s". Don't use an apostrophe.</p>
+
+<ul>
+ <li><span class="correct"><strong>Correct</strong></span>: 1990s</li>
+ <li><span class="incorrect"><strong>Incorrect</strong></span>: 1990's</li>
+</ul>
+
+<h4 id="Plurals_of_numerals" name="Plurals_of_numerals">數詞的複數</h4>
+
+<p>For plurals of numerals add <em>"s"</em>. Don't use an apostrophe.</p>
+
+<ul>
+ <li><span class="correct"><strong>Correct</strong></span>: 486s</li>
+ <li><span class="incorrect"><strong>Incorrect</strong></span>: 486's</li>
+</ul>
+
+<h4 id="Commas" name="Commas">逗號</h4>
+
+<p>In running text, use commas only in five-digit and larger numbers.</p>
+
+<ul>
+ <li><span class="correct"><strong>Correct</strong></span>: 4000; 54,000</li>
+ <li><span class="incorrect"><strong>Incorrect</strong></span>: 4,000; 54000</li>
+</ul>
+
+<h3 id="Punctuation" name="Punctuation">標點符號</h3>
+
+<h4 id="Serial_comma" name="Serial_comma">連續逗號</h4>
+
+<p><strong>Use the serial comma</strong>. The serial (also known as "Oxford") comma is the comma that appears before the conjunction in a series of three or more items.</p>
+
+<ul>
+ <li><span class="correct"><strong>Correct</strong></span>: I will travel on trains, planes, and automobiles.</li>
+ <li><span class="incorrect"><strong>Incorrect</strong></span>: I will travel on trains, planes and automobiles.</li>
+</ul>
+
+<div class="note">
+<p><strong>Note:</strong> This is in contrast to the <a href="http://www.mozilla.org/en-US/styleguide/" title="http://www.mozilla.org/en-US/styleguide/">One Mozilla style guide</a>, which specifies that the serial comma is not to be used. MDN is an exception to this rule.</p>
+</div>
+
+<h3 id="Spelling" name="Spelling">拼字</h3>
+
+<p>For words with variant spellings, always use the first entry at <a href="http://www.answers.com/library/Dictionary">Answers.com</a>. Do not use variant spellings.</p>
+
+<ul>
+ <li><span class="correct"><strong>Correct</strong></span>: localize, honor</li>
+ <li><span class="incorrect"><strong>Incorrect</strong></span>: localise, honour</li>
+</ul>
+
+<h3 id="術語">術語</h3>
+
+<h4 id="棄用_vs._過時">棄用 vs. 過時</h4>
+
+<p>It's important to be clear on the difference between the terms <strong>obsolete</strong> and <strong>deprecated</strong>.</p>
+
+<dl>
+ <dt>棄用：</dt>
+ <dd>On MDN, the term <strong>obsolete</strong> marks an API or technology that is not only no longer recommended, but also no longer implemented in the browser. For Mozilla-specific technologies, the API is no longer implemented in Mozilla code; for Web standard technology, the API or feature is no longer supported by current, commonly-used browsers.</dd>
+ <dt>過時：</dt>
+ <dd>On MDN, the term <strong>deprecated</strong> marks an API or technology that is no longer recommended, but is still implemented and may still work. These technologies will in theory eventually become <em>obsolete</em> and be removed, so you should stop using them. For Mozilla-specific technologies, the API is still supported in Mozilla code; for Web standard technology, the API or feature has been removed or replaced in a recent version of the defining standard.</dd>
+</dl>
+
+<h4 id="HTML_元素">HTML 元素</h4>
+
+<p>Use "elements" to refer to HTML and XML elements, rather than "tags". In addition, they should almost always be wrapped in "&lt;&gt;", and should be in the {{HTMLElement("code")}} style. Also, at least the first time you reference a given element in a section should use the {{TemplateLink("HTMLElement")}} macro, to create a link to the documentation for the element (unless you're writing within that element's reference document page).</p>
+
+<ul>
+ <li><span class="correct"><strong>Correct</strong></span>: the {{HTMLElement("span")}} element</li>
+ <li><span class="incorrect"><strong>Incorrect</strong></span>: the span tag</li>
+</ul>
+
+<h4 id="使用者介面動作">使用者介面動作</h4>
+
+<p>In task sequences, describe user interface actions using the imperative mood. Identify the user interface element by its label and type.</p>
+
+<ul>
+ <li><span class="correct"><strong>Correct</strong></span>: Click the Edit button.</li>
+ <li><span class="incorrect"><strong>Incorrect</strong></span>: Click Edit.</li>
+</ul>
+
+<h3 id="語態">語態</h3>
+
+<p>While the active voice is generally preferred, the passive voice is also acceptable, given the informal feel of our content. Try to be consistent, though.</p>
+
+<h2 id="Wiki_語法與用處">Wiki 語法與用處</h2>
+
+<h3 id="外部連結">外部連結</h3>
+
+<p>To automatically create a link to a Bugzilla bug, use this template:</p>
+
+<pre class="notranslate">\{{Bug(322603)}}
+</pre>
+
+<p>This results in:</p>
+
+<p>{{Bug(322603)}}</p>
+
+<p>For WebKit bugs, you can use this template:</p>
+
+<pre class="notranslate">\{{Webkitbug("322603")}}
+</pre>
+
+<p>This results in:</p>
+
+<p>{{Webkitbug("322603")}}</p>
+
+<h3 id="頁面標籤">頁面標籤</h3>
+
+<p>Tags provide meta information about a page and/or indicate that a page has specific improvements needed to its content. Every page in the wiki should have tags. You can find details on tagging in our <a href="/en-US/docs/MDN/Contribute/Howto/Tag">How to properly tag pages</a> guide.</p>
+
+<p>The tagging interface lives at the bottom of a page while you're in edit mode, and looks something like this:</p>
+
+<p><img alt="Screenshot of the UX for adding and removing tags on MDN" src="https://mdn.mozillademos.org/files/7859/tag-interface.png" style="border-style: solid; border-width: 1px; height: 167px; width: 863px;"></p>
+
+<p>To add a tag, click in the edit box at the end of the tag list and type the tag name you wish to add. Tags will autocomplete as you type. Press enter (or return) to submit the new tag. Each article may have as many tags as needed. For example, an article about using JavaScript in AJAX programming might have both "JavaScript" and "AJAX" as tags.</p>
+
+<p>To remove a tag, simply click the little "X" icon in the tag.</p>
+
+<h4 id="標記需要加工的頁面">標記需要加工的頁面</h4>
+
+<p>In addition to using tags to track information about the documentation's quality and content, we also use them to mark articles as needing specific types of work.</p>
+
+<h4 id="標記棄用的頁面">標記棄用的頁面</h4>
+
+<p>Use the following tags for pages that are not current:</p>
+
+<ul>
+ <li><em>Junk</em>: Use for spam, pages created by mistake, or content that is so bad that it should be deleted. Pages with this tag are deleted from time to time.</li>
+ <li><em>Obsolete</em>: Use for content that is technically superceded, but still valid in context. For example an HTML element that is obsolete in HTML5 is still valid in HTML 4.01. You can also use the <span class="nowiki">{{TemplateLink("obsolete_header")}}</span> macro to put a prominent banner on the topic.</li>
+ <li><em>Archive</em>: Use for content that is technically superceded and no longer useful. If possible, add a note to the topic referring readers to a more current topic. For example, a page that describes how to use the Mozilla CVS repository should refer readers to a current topic on using Mercurial repos. (If no corresponding current topic exists, use the <em>NeedsUpdate</em> tag, and add an explanation on the Talk page.) Pages with the Archive tag are eventually moved from the main content of MDN to the <a href="/en-US/docs/Archive">Archive</a> section.</li>
+</ul>
+
+<h3 id="SEO_摘要">SEO 摘要</h3>
+
+<p>The SEO summary is a very short summary of the page. It will be reported as a summary of the article to robots crawling the site, and will then appear in search results for the page. It is also used by macros that automate the construction of landing pages inside MDN itself.</p>
+
+<p>By default, the first pagragraph of the page is used as the SEO summary. However you can override this behavior by marking a section with the <a href="/en-US/docs/Project:MDN/Contributing/Editor_guide/Editing#Formatting_styles">"SEO summary" style in the WYSIWYG editor</a>.</p>
+
+<h3 id="導航頁面">導航頁面</h3>
+
+<p><strong>Landing pages</strong> are pages at the root of a topic area of the site, such as the main <a href="/en-US/docs/CSS" title="CSS">CSS</a> or <a href="/en-US/docs/HTML" title="HTML">HTML</a> pages. They have a standard format that consists of three areas:</p>
+
+<ol>
+ <li>A brief (typically one paragraph) overview of what the technology is and what it's used for. See {{anch("Writing a landing page overview")}} for tips.</li>
+ <li>A two-column list of links with appropriate headings. See {{anch("Creating a page link list")}} for guidelines.</li>
+ <li>An <strong>optional</strong> "Browser compatibility" section at the bottom of the page.</li>
+</ol>
+
+<h4 id="創建頁面連結清單">創建頁面連結清單</h4>
+
+<p>The link list section of an MDN landing page consists of two columns. These are created using the following HTML:</p>
+
+<pre class="brush: html notranslate">&lt;div class="row topicpage-table"&gt;
+  &lt;div class="section"&gt;
+    ... left column contents ...
+  &lt;/div&gt;
+  &lt;div class="section"&gt;
+    ... right column contents ...
+  &lt;/div&gt;
+&lt;/div&gt;</pre>
+
+<p>The left-hand column should be a list of articles, with an <code>&lt;h2&gt;</code> header at the top of the left column explaining that it's a list of articles about the topic (for example "Documentation and tutorials about foo"); this header should use the CSS class "Documentation". Below that is a <code>&lt;dl&gt;</code> list of articles, with each article's link in a <code>&lt;dt&gt;</code> block and a brief one-or-two sentence summary of the article in the corresponding <code>&lt;dd&gt;</code> block.</p>
+
+<p>The right-hand column should contain one or more of the following sections, in order:</p>
+
+<dl>
+ <dt>從社群尋求協助</dt>
+ <dd>This should provide information on Matrix rooms and mailing lists available about the topic. The heading should use the class "Community".</dd>
+ <dt>工具</dt>
+ <dd>A list of tools the user can look at to help with the use of the technology described in this section of MDN. The heading should use the class "Tools".</dd>
+ <dt>相關主題</dt>
+ <dd>A list of links to landing pages for other, related, technologies of relevance. The heading should use the class "Related_Topics".</dd>
+</dl>
+
+<p><strong>&lt;&lt;&lt;finish this once we finalize the landing page standards&gt;&gt;&gt;</strong></p>
+
+<h2 id="插入、使用圖片">插入、使用圖片</h2>
+
+<p>It's sometimes helpful to provide an image in an article you create or modify, especially if the article is very technical. To include an image:</p>
+
+<ol>
+ <li>Attach the desired image file to the article (at the bottom of every article in edit mode)</li>
+ <li>Create an image in the WYSIWYG editor</li>
+ <li>In the WYSIWYG editor in the drop-down list listing attachments, select the newly created attachment which is your image</li>
+ <li>Press OK.</li>
+</ol>
+
+<h2 id="其它參考">其它參考</h2>
+
+<h3 id="Preferred_style_guides" name="Preferred_style_guides">首選風格指南</h3>
+
+<p>If you have questions about usage and style not covered here, we recommend referring to the <a href="http://www.economist.com/research/StyleGuide/">Economist style guide</a> or, failing that, the <a href="http://www.amazon.com/gp/product/0226104036/">Chicago Manual of Style</a>.</p>
+
+<h3 id="Preferred_dictionary" name="Preferred_dictionary">首選詞典</h3>
+
+<p>For questions of spelling, please refer to <a href="http://www.answers.com/library/Dictionary">Answers.com</a>. The spell-checker for this site uses American English. Please do not use variant spellings (e.g., use <em>honor</em> rather than <em>honour</em>).</p>
+
+<p>We will be expanding the guide over time, so if you have specific questions that aren't covered in this document, please send them to the <a href="/en-US/docs/Project:Community" title="Project:en/Community">MDC mailing list</a> or <a href="/User:Sheppy" title="User:Sheppy">project lead</a> so we know what should be added.</p>
+
+<h3 id="MDC-specific" name="MDC-specific">MDN 特定資訊</h3>
+
+<ul>
+ <li><a href="/en-US/docs/Project:Custom_CSS_Classes" title="Project:en/Custom_CSS_Classes">Custom CSS classes</a> defined for all MDC pages.</li>
+ <li><a href="/en-US/docs/Project:Custom_Templates" title="Project:en/Custom_Templates">Custom templates</a> created for use on MDC, with explanations.</li>
+</ul>
+
+<h3 id="Other_resources" name="Other_resources">語言、文法和拼字</h3>
+
+<p>If you're interested in improving your writing and editing skills, you may find the following resources to be helpful.</p>
+
+<ul>
+ <li><a href="http://www.amazon.com/Writing-Well-30th-Anniversary-Nonfiction/dp/0060891548">On Writing Well</a>, by William Zinsser (Amazon link)</li>
+ <li><a href="http://www.amazon.com/Style-Basics-Clarity-Grace-4th/dp/0205830765/" title="http://www.amazon.com/Style-Lessons-Clarity-Grace-Edition/dp/0321898680">Style: The Basics of Clarity and Grace</a>, by Joseph Williams and Gregory Colomb (Amazon link)</li>
+ <li><a href="http://www.bartleby.com/64/">American Heritage Book of English Usage</a></li>
+ <li><a href="http://www.wsu.edu/~brians/errors/">Common Errors in English</a></li>
+ <li><a href="http://www-personal.umich.edu/~jlawler/aue.html">English Grammar FAQ</a> (alt.usage.english)</li>
+ <li><a href="http://www.angryflower.com/bobsqu.gif">Bob's quick guide to the apostrophe, you idiots</a> (funny)</li>
+ <li><a href="http://www.amazon.com/Merriam-Websters-Concise-Dictionary-English-Usage/dp/B004L2KNI2" title="http://www.amazon.com/Merriam-Websters-Concise-Dictionary-English-Usage/dp/B004L2KNI2">Merriam-Webster's Concise Dictionary of English Usage</a> (Amazon link): Scholarly but user-friendly, evidence-based advice; very good for non-native speakers, especially for preposition usage.</li>
+</ul>
diff --git a/files/zh-tw/mdn/index.html b/files/zh-tw/mdn/index.html
new file mode 100644
index 0000000000..c335002f11
--- /dev/null
+++ b/files/zh-tw/mdn/index.html
@@ -0,0 +1,32 @@
+---
+title: MDN 專案
+slug: MDN
+tags:
+  - Documentation
+  - MDN
+translation_of: MDN
+---
+<div>{{MDNSidebar}}</div>
+
+<p><strong>MDN Web Docs</strong> 是我們為開放網路、Mozilla 技術、Firefox 與其他開發者相關專題建立文件的 Wiki 系統。歡迎任何人新增與編輯內容。你不需要是程式設計師或非常了解技術；這邊有各種需要協助的工作，從最簡單（閱讀文件、改錯字）到最複雜（撰寫 API 文件）都有。</p>
+
+<div class="summary">
+<p>MDN Web Docs 的使命是提供<em>開發者</em>在<em>網站平台</em>上<em>輕鬆</em>建立專案所需的資訊。歡迎加入！</p>
+</div>
+
+<p>我們歡迎你的直接協助，非常容易！也不需要擔心「要不要獲得許可」之類的問題。在此同時，請試著了解並融入 <a href="/zh-TW/docs/MDN/Community">MDN 社群</a>；我們都在這裡協助你！以下文件能作為起步的指引。</p>
+
+
+
+<ul class="card-grid">
+ <li><span><a href="/zh-TW/docs/MDN/Getting_started">新手起手式</a></span>
+
+  <p>你是 MDN 新人，想要學習該如何開始嗎？就從這起步吧！</p>
+ </li>
+ <li><span><a href="/zh-TW/docs/MDN/Contribute">我是進階用戶</a></span>
+  <p>當你覺得適當之時，閱讀我們的完整、深入 MDN 貢獻指引以學習更多</p>
+ </li>
+ <li><span><a class="new" href="/zh-TW/docs/MDN/Promote" rel="nofollow">向世界宣傳</a></span>
+  <p>如果你愛 MDN，幫助我們傳達給全世界！找尋圖片、工具與 MDN 宣傳指引。</p>
+ </li>
+</ul>
diff --git a/files/zh-tw/mdn/kuma/index.html b/files/zh-tw/mdn/kuma/index.html
new file mode 100644
index 0000000000..1a4263acad
--- /dev/null
+++ b/files/zh-tw/mdn/kuma/index.html
@@ -0,0 +1,26 @@
+---
+title: 'Kuma: MDN 的維基平台'
+slug: MDN/Kuma
+tags:
+  - Kuma
+  - Landing
+  - MDN Meta
+translation_of: MDN/Kuma
+---
+<div>{{MDNSidebar}}</div>
+
+<div>{{IncludeSubnav("/zh-TW/docs/MDN")}}</div>
+
+<p>Kuma 是由 MDN Web Docs 維護的 Django 程式碼。</p>
+
+<p>{{SubpagesWithSummaries}}</p>
+
+<h2 id="參與_Kuma">參與 Kuma</h2>
+
+<p>要參與 Kuma:</p>
+
+<ul>
+ <li>訪問一下 <a href="https://github.com/mozilla/kuma">Github 的 Kuma 專案</a>。</li>
+ <li>去看一下<a href="https://github.com/mozilla/kuma/blob/master/CONTRIBUTING.md">貢獻指引</a>。</li>
+ <li>需要的話，深入探索<a href="http://kuma.readthedocs.org/en/latest/">Kuma 的完整文件</a>。</li>
+</ul>
diff --git a/files/zh-tw/mdn/tools/index.html b/files/zh-tw/mdn/tools/index.html
new file mode 100644
index 0000000000..a7ac474b98
--- /dev/null
+++ b/files/zh-tw/mdn/tools/index.html
@@ -0,0 +1,15 @@
+---
+title: MDN tools
+slug: MDN/Tools
+tags:
+  - Landing
+  - MDN Meta
+translation_of: MDN/Tools
+---
+<div>{{MDNSidebar}}</div>
+
+<div>{{IncludeSubnav("/en-US/docs/MDN")}}</div>
+
+<p>MDN 提供了許多功能來簡化追蹤進度、管理內容，並跟上網站最新的修改。</p>
+
+<p>{{LandingPageListSubpages}}</p>
diff --git a/files/zh-tw/mdn/tools/kumascript/index.html b/files/zh-tw/mdn/tools/kumascript/index.html
new file mode 100644
index 0000000000..9404ced57b
--- /dev/null
+++ b/files/zh-tw/mdn/tools/kumascript/index.html
@@ -0,0 +1,490 @@
+---
+title: KumaScript
+slug: MDN/Tools/KumaScript
+translation_of: MDN/Tools/KumaScript
+---
+<div>{{MDNSidebar}}</div><h2 id="概要">概要</h2>
+
+<p><span class="seoSummary">On the <a href="/en-US/docs/MDN/Kuma">Kuma</a> platform that powers MDN, the template system for automating aspects of content on the wiki is called <a class="link-https" href="https://github.com/mdn/kumascript" title="https://github.com/mdn/kumascript">KumaScript</a>. KumaScript is powered by server-side JavaScript, implemented using <a class="external" href="https://nodejs.org/en/" title="https://nodejs.org/en/">Node.js</a>.</span> This article provides basic information on how to use KumaScript.</p>
+
+<p>For a detailed overview and Q&amp;A of KumaScript, watch the MDN dev team's <a href="https://vreplay.mozilla.com/replay/showRecordDetails.html?sortBy=date&amp;viewCount=1&amp;currentPage=1&amp;groupBy=combo&amp;roomFilter=&amp;usernameFilter=&amp;searchFilter=&amp;usernameFullFilter=&amp;myManager=-1&amp;adminManager=0&amp;webCast=0&amp;command=&amp;recId=1082&amp;auxMessage=&amp;auxMessage1=&amp;lang=en&amp;langChanged=&amp;tenantFilter=&amp;securityTab=">KumaScript Fireside Chat</a> (the meeting starts at 10 minutes into the video). KumaScript replaced DekiScript, which was the template language for MindTouch, the previous platform used by MDN.</p>
+
+<h3 id="What_is_KumaScript">What is KumaScript?</h3>
+
+<ul>
+ <li>A way to reuse and localize content that appears repeatedly between documents (e.g., compatibility labels, section navigation, warning banners).</li>
+ <li>A way to build documents out of content pulled from other documents.</li>
+ <li>A way to fetch and include content from other web sites and services (e.g., Bugzilla).</li>
+</ul>
+
+<h3 id="What_KumaScript_is_not">What KumaScript is not</h3>
+
+<ul>
+ <li>KumaScript does not support interactive scripting of the kind that can accept form submissions.</li>
+ <li>KumaScript does not have access to a database, files, or any other way to store information persistently.</li>
+ <li>KumaScript does not support site personalization based on the user currently logged in.</li>
+ <li>KumaScript does not have access to user information, only to the content and metadata of a wiki page being viewed.</li>
+</ul>
+
+<h2 id="基礎">基礎</h2>
+
+<p>KumaScript is used on MDN in <a class="link-https" href="https://github.com/visionmedia/ejs" title="https://github.com/visionmedia/ejs">embedded JavaScript templates</a>. These templates can be invoked in document content by any MDN author, through the use of macros.</p>
+
+<p>A script in KumaScript is a <em>template</em>, and each template is a file in <a href="https://github.com/mdn/kumascript/tree/master/macros">the macros directory of the KumaScript repository</a> on Github. A  <a class="link-https" href="https://github.com/mdn/kumascript/blob/master/macros/hello.ejs" title="hello.ejs">template</a> looks like this:</p>
+
+<pre class="notranslate">&lt;% for (var i = 0; i &lt; $0; i++) { %&gt;
+Hello #&lt;%= i %&gt;
+&lt;% } %&gt;</pre>
+
+<p>Invoking a template is done with a <em>macro</em>, which can be used anywhere in any wiki content. A macro looks like this:</p>
+
+<pre class="notranslate">\{{ hello("3") }}</pre>
+
+<p>The output of the macro looks like this:</p>
+
+<pre class="notranslate">Hello #0
+Hello #1
+Hello #2</pre>
+
+<h3 id="Macro_syntax">Macro syntax</h3>
+
+<p>KumaScript templates are invoked in document content with macros, like this:</p>
+
+<pre class="notranslate">\{{ templateName("arg0", "arg1", ..., "argN") }}
+</pre>
+
+<p>Macro syntax consists of these rules:</p>
+
+<ul>
+ <li>Macros start and end with <code>\{{</code> and <code>\}}</code> characters.</li>
+ <li>The first part of the macro is the name of a template. The lowercase value of this name should match the lowercase value of one of the filenames under <a href="https://github.com/mdn/kumascript/tree/master/macros">the macros directory of KumaScript</a>.</li>
+ <li>A template can accept parameters, and this parameter list starts and ends with parentheses.</li>
+ <li>All non-numeric parameters must be in quotes. Numbers can be left unquoted.</li>
+</ul>
+
+<h4 id="Using_JSON_as_a_macro_parameter">Using JSON as a macro parameter</h4>
+
+<p>As a semi-experimental feature (not guaranteed to work), you can supply a JSON object for the first and only parameter, like so:</p>
+
+<pre class="notranslate">\{{ templateName({ "Alpha":"one", "Beta":["a","b","c"], "Foo":"http:\/\/mozilla.org\/" }) }}
+</pre>
+
+<p>The data from this macro is available in template code as an object in the <code>$0</code> argument (e.g., <code>$0.Alpha</code>, <code>$0.Beta</code>, <code>$0.Foo</code>). This also allows you to express complex data structures in macro parameters that are hard or impossible to do with a simple list of parameters.</p>
+
+<p>Note that this parameter style is very picky — it must adhere to <a href="http://json.org/" title="http://json.org/">JSON syntax</a> exactly, which has some requirements about escaping characters that are easy to miss (e.g., all forward slashes are escaped). When in doubt, <a href="http://jsonlint.com/" title="http://jsonlint.com/">try running your JSON through a validator</a>.</p>
+
+<h4 id="How_to_write_in_text">How to write "\{{" in text</h4>
+
+<p>Since the character sequence "<code>\{{</code>" is used to indicate the start of a macro, this can be troublesome if you actually just want to use "<code>\{{</code>" and "<code>}}</code>" in a page. It will probably produce <code>DocumentParsingError</code> messages.</p>
+
+<p>In this case, you can escape the first brace with a backslash, like so: <code>\\{</code></p>
+
+<h3 id="Template_syntax">Template syntax</h3>
+
+<p>Each KumaScript template is a file under <a href="https://github.com/mdn/kumascript/tree/master/macros">the macros directory of KumaScript</a>. You create and edit these files as you would the files of any open-source project on GitHub (see <a href="https://github.com/mdn/kumascript">the KumaScript README</a> for more information).</p>
+
+<p>KumaScript templates are processed by an <a class="link-https" href="https://github.com/visionmedia/ejs" title="https://github.com/visionmedia/ejs">embedded JavaScript template engine</a> with a few simple rules:</p>
+
+<ul>
+ <li>Within a template, the parameters passed in from the macro are available as the variables <code>$0</code>, <code>$1</code>, <code>$2</code>, and so on. The entire list of parameters is also available in a template as the variable <code>arguments</code>.</li>
+ <li>Most text is treated as output and included in the output stream.</li>
+ <li>JavaScript variables and expressions can be inserted into the output stream with these blocks:
+  <ul>
+   <li><code>&lt;%= expr %&gt;</code> — the value of a JavaScript expression is escaped for HTML before being included in output (e.g., characters like <code>&lt;</code> and <code>&gt;</code> are turned into <code>&amp;lt;</code> and <code>&amp;gt;</code>).</li>
+   <li><code>&lt;%- expr %&gt;</code> — the value of a JavaScript expression is included in output without any escaping. (Use this if you want to dynamically build markup or use the results of another template that may include markup.)</li>
+   <li>It is an error to include semicolons inside these blocks.</li>
+  </ul>
+ </li>
+ <li>Anything inside a <code>&lt;% %&gt;</code> block is interpreted as JavaScript. This can include loops, conditionals, etc.</li>
+ <li>Nothing inside a <code>&lt;% %&gt;</code> block can ever contribute to the output stream. But, you can transition from JS mode to output mode using <code>&lt;% %&gt;</code>—for example:
+  <pre class="notranslate">&lt;% for (var i = 0; i &lt; $0; i++) { %&gt;
+Hello #&lt;%= i %&gt;
+&lt;% } %&gt;
+</pre>
+
+  <p>Note how the JavaScript code is contained in <code>&lt;% ... %&gt;</code>, and output happens in the space between <code>%&gt; ... &lt;%</code>. The <code>for</code> loop in JS can begin with one <code>&lt;% %&gt;</code> block, transition to output mode, and finish up in a second <code>&lt;% %&gt;</code> JS block.</p>
+ </li>
+ <li>For more details on EJS syntax, <a class="link-https" href="https://github.com/visionmedia/ejs" title="https://github.com/visionmedia/ejs">check out the upstream module documentation</a>.</li>
+</ul>
+
+<h3 id="Tips">Tips</h3>
+
+<p>You can see a list of macros and how they are used on MDN on the <a href="/en-US/dashboards/macros">macros dashboard</a>.</p>
+
+<h2 id="進階功能">進階功能</h2>
+
+<p>Beyond the basics, the KumaScript system offers some advanced features.</p>
+
+<h3 id="Environment_variables">Environment variables</h3>
+
+<p>When the wiki makes a call to the KumaScript service, it passes along some context on the current document that KumaScript makes available to templates as variables:</p>
+
+<dl>
+ <dt><code>env.path</code></dt>
+ <dd>The path to the current wiki document</dd>
+ <dt><code>env.url</code></dt>
+ <dd>The full URL to the current wiki document</dd>
+ <dt><code>env.id</code></dt>
+ <dd>A short, unique ID for the current wiki document</dd>
+ <dt><code>env.files</code></dt>
+ <dd>An array of the files attached to the current wiki document; each object in the array is as described under {{ anch("File objects") }} below</dd>
+ <dt><code>env.review_tags</code></dt>
+ <dd>An array of the review tags on the article ("technical", "editorial", etc.)</dd>
+ <dt><code>env.locale</code></dt>
+ <dd>The locale of the current wiki document</dd>
+ <dt><code>env.title</code></dt>
+ <dd>The title of the current wiki document</dd>
+ <dt><code>env.slug</code></dt>
+ <dd>The URL slug of the current wiki document</dd>
+ <dt><code>env.tags</code></dt>
+ <dd>An array list of tag names for the current wiki document</dd>
+ <dt><code>env.modified</code></dt>
+ <dd>Last modified timestamp for the current wiki document</dd>
+ <dt><code>env.cache_control</code></dt>
+ <dd><code>Cache-Control</code> header sent in the request for the current wiki document, useful in deciding whether to invalidate caches</dd>
+</dl>
+
+<h4 id="File_objects">File objects</h4>
+
+<p>Each file object has the following fields:</p>
+
+<dl>
+ <dt><code>title</code></dt>
+ <dd>The attachment's title</dd>
+ <dt><code>description</code></dt>
+ <dd>A textual description of the current revision of the file</dd>
+ <dt><code>filename</code></dt>
+ <dd>The file's name</dd>
+ <dt><code>size</code></dt>
+ <dd>The size of the file in bytes</dd>
+ <dt><code>author</code></dt>
+ <dd>The username of the person who uploaded the file</dd>
+ <dt><code>mime</code></dt>
+ <dd>The MIME type of the file</dd>
+ <dt><code>url</code></dt>
+ <dd>The URL at which the file can be found</dd>
+</dl>
+
+<h4 id="Working_with_tag_lists">Working with tag lists</h4>
+
+<p>The <code>env.tags</code> and <code>env.review_tags</code> variables return arrays of tags. You can work with these in many ways, of course, but here are a couple of suggestions.</p>
+
+<h5 id="Looking_to_see_if_a_specific_tag_is_set">Looking to see if a specific tag is set</h5>
+
+<p>You can look to see if a specific tag exists on a page like this:</p>
+
+<pre class="brush: js notranslate">if (env.tags.indexOf("tag") != −1) {
+  // The page has the tag "tag"
+}
+</pre>
+
+<h5 id="Iterating_over_all_the_tags_on_a_page">Iterating over all the tags on a page</h5>
+
+<p>You can also iterate over all the tags on a page, like this:</p>
+
+<pre class="brush: js notranslate">env.tag.forEach(function(tag) {
+  // do whatever you need to do, such as:
+  if (tag.indexOf("a") == 0) {
+    // this tag starts with "a" - woohoo!
+  }
+});</pre>
+
+<h3 id="APIs_and_Modules">APIs and Modules</h3>
+
+<p>KumaScript offers some built-in methods and APIs for KumaScript macros.  Macros can also use <code>module.exports</code> to export new API methods.</p>
+
+<p>API changes require updating the KumaScript engine or macros via a pull request to the <a href="https://github.com/mdn/kumascript">KumaScript repository</a>.</p>
+
+<h4 id="Built-in_methods">Built-in methods</h4>
+
+<p>This manually-maintained documentation is likely to fall out of date with the code. With that in mind, <a class="link-https" href="https://github.com/mdn/kumascript/blob/master/lib/kumascript/api.js#L175" title="https://github.com/mdn/kumascript/blob/master/lib/kumascript/api.js#L208">you can always check out the latest state of built-in APIs in the KumaScript source</a>. But here is a selection of useful methods exposed to templates:</p>
+
+<dl>
+ <dt><code>md5(string)</code></dt>
+ <dd>Returns an MD5 hex digest of the given string.</dd>
+ <dt><code>template("name", ["arg0", "arg1", ..., "argN"])</code></dt>
+ <dd>Executes and returns the result of the named template with the given list of parameters.</dd>
+ <dd>Example: <code>&lt;%- template("warning", ["foo", "bar", "baz"]) %&gt;</code>.</dd>
+ <dd>Example using the <code>domxref</code> macro: <code>&lt;%- template("domxref", ["Event.bubbles", "bubbles"]) %&gt;</code>.</dd>
+ <dd>This is a JavaScript function. So, if one of the parameters is an arg variable like $2, do not put it in quotes. Like this: <code>&lt;%- template("warning", [$1, $2, "baz"]) %&gt;</code>. If you need to call another template from within a block of code, do not use <code>&lt;%</code> ... <code>%&gt;</code>. Example: <code>myvar = "&lt;li&gt;" + template("LXRSearch", ["ident", "i", $1]) + "&lt;/li&gt;";</code></dd>
+ <dt><code>require(name)</code></dt>
+ <dd>Loads another template as a module; any output is ignored. Anything assigned to <code>module.exports</code> in the template is returned.</dd>
+ <dd>Used in templates like so: <code>&lt;% var my_module = require('MyModule'); %&gt;</code>.</dd>
+ <dt><code>cacheFn(key, timeout, function_to_cache)</code></dt>
+ <dd>Using the given key and cache entry lifetime, cache the results of the given function. Honors the value of <code>env.cache_control</code> to invalidate cache on <code>no-cache</code>, which can be sent by a logged-in user hitting shift-refresh.</dd>
+ <dt><code>request</code></dt>
+ <dd>Access to <a class="link-https" href="https://github.com/mikeal/request" title="https://github.com/mikeal/request"><code>mikeal/request</code></a>, a library for making HTTP requests. Using this module in KumaScript templates is not yet very friendly, so you may want to wrap usage in module APIs that simplify things.</dd>
+ <dt><code>log.debug(string)</code></dt>
+ <dd>Outputs a debug message into the script log on the page (i.e. the big red box that usually displays errors).</dd>
+</dl>
+
+<h4 id="Built-in_API_modules">Built-in API modules</h4>
+
+<p>There's only one API built in at the moment, in the <code>kuma</code> namespace. You can see the most up to date list of methods under <code>kuma</code> from <a href="https://github.com/mdn/kumascript/blob/master/lib/kumascript/api.js#L74">the KumaScript source code</a>, but here are a few:</p>
+
+<dl>
+ <dt><code>kuma.inspect(object)</code></dt>
+ <dd>Renders any JS object as a string, handy for use with <code>log.debug()</code>. See also: <a href="http://nodejs.org/api/util.html#util_util_inspect_object_options">node.js <code>util.inspect()</code></a>.</dd>
+</dl>
+
+<dl>
+ <dt><code>kuma.htmlEscape(string)</code></dt>
+ <dd>Escapes the characters <code>&amp;, &lt;, &gt;, "</code> to <code>&amp;amp, &amp;lt;, &amp;gt;, &amp;quot;</code>, respectively.</dd>
+ <dt><code>kuma.url</code></dt>
+ <dd>See also: <a href="http://nodejs.org/api/url.html">node.js <code>url</code> module</a>.</dd>
+ <dt><code>kuma.fetchFeed(url)</code></dt>
+ <dd>Fetch an RSS feed and parse it into a JS object. See also: <a href="https://github.com/mdn/kumascript/blob/master/macros/InsertFeedLinkList.ejs"><code>InsertFeedLinkList</code></a></dd>
+</dl>
+
+<h4 id="Creating_modules">Creating modules</h4>
+
+<p>Using the built-in <code>require()</code> method, you can load a template as a module to share common variables and methods between templates. A module can be defined in a template like this:</p>
+
+<pre class="notranslate">&lt;%
+module.exports = {
+    add: function (a, b) {
+        return a + b;
+    }
+}
+%&gt;
+</pre>
+
+<p>Assuming this template is saved under <a href="https://github.com/mdn/kumascript/tree/master/macros">https://github.com/mdn/kumascript/tree/master/macros</a> as <code>MathLib.ejs</code>, you can use it in another template like so:</p>
+
+<pre class="notranslate">&lt;%
+var math_lib = require("MathLib");
+%&gt;
+The result of 2 + 2 = &lt;%= math_lib.add(2, 2) %&gt;
+</pre>
+
+<p>And, the output of this template will be:</p>
+
+<pre class="notranslate">The result of 2 + 2 = 4
+</pre>
+
+<h4 id="Auto-loaded_modules">Auto-loaded modules</h4>
+
+<p>There are a set of modules editable as wiki templates that are automatically loaded and made available to every template. This set is defined in the configuration file for the KumaScript service - any changes to this requires an IT bug to edit configuration and a restart of the service.</p>
+
+<p>For the most part, these attempt to provide stand-ins for legacy DekiScript features to ease template migration. But, going forward, these can be used to share common variables and methods between templates:</p>
+
+<ul>
+ <li><code>mdn.*</code> - <a class="link-https" href="https://github.com/mdn/kumascript/blob/master/macros/MDN-Common.ejs" title="MDN:Common">MDN-Common</a></li>
+ <li><code>Page.*</code> - <a class="link-https" href="https://github.com/mdn/kumascript/blob/master/macros/DekiScript-Page.ejs" title="DekiScript:Page">DekiScript-Page</a></li>
+ <li><code>String.*</code> - <a class="link-https" href="https://github.com/mdn/kumascript/blob/master/macros/DekiScript-String.ejs" title="DekiScript:String">DekiScript-String</a></li>
+ <li><code>Uri.*</code> - <a class="link-https" href="https://github.com/mdn/kumascript/blob/master/macros/DekiScript-Uri.ejs" title="DekiScript:Uri">DekiScript-Uri</a></li>
+ <li><code>Web.*</code> - <a class="link-https" href="https://github.com/mdn/kumascript/blob/master/macros/DekiScript-Web.ejs" title="DekiScript:Web">DekiScript-Web</a></li>
+ <li><code>Wiki.*</code> - <a class="link-https" href="https://github.com/mdn/kumascript/blob/master/macros/DekiScript-Wiki.ejs" title="DekiScript:Wiki">DekiScript-Wiki</a></li>
+</ul>
+
+<p><strong>Note:</strong> You might notice that the DekiScript modules use a built-in method named <code>buildAPI()</code>, like so:</p>
+
+<pre class="notranslate">&lt;% module.exports = buildAPI({
+    StartsWith: function (str, sub_str) {
+        return (''+str).indexOf(sub_str) === 0;
+    }
+}); %&gt;
+</pre>
+
+<p>The reason for this is because DekiScript is case-insensitive when it comes to references to API methods, whereas JavaScript is strict about uppercase and lowercase in references. So, <code>buildAPI()</code> is a hack to try to cover common case variations in DekiScript calls found in legacy templates.</p>
+
+<div class="note">
+<p>With that in mind, please do not use <code>buildAPI()</code> in new modules.</p>
+</div>
+
+<h2 id="Tips_and_caveats">Tips and caveats</h2>
+
+<h3 id="Debugging">Debugging</h3>
+
+<p>A useful tip when debugging. You can use the <code>log.debug()</code> method to output text to the scripting messages area at the top of the page that's running your template. Note that you need to be really sure to remove these when you're done debugging, as they're visible to all users! To use it, just do something like this:</p>
+
+<pre class="notranslate">&lt;%- log.debug("Some text goes here"); %&gt;
+</pre>
+
+<p>You can, of course, create more complex output using script code if it's helpful.</p>
+
+<h3 id="Caching">Caching</h3>
+
+<p>KumaScript templates are heavily cached to improve performance. For the most part, this works great to serve up content that doesn't change very often. But, as a logged-in user, you have two options to force a page to be regenerated, in case you notice issues with scripting:</p>
+
+<ul>
+ <li>Hit Refresh in your browser. This causes KumaScript to invalidate its cache for the content on the current page by issuing a request with a <code>Cache-Control: max-age=0</code> header.</li>
+ <li>Hit Shift-Refresh in your browser. This causes KumaScript to invalidate cache for the current page, as well as for any templates or content used by the current page by issuing a request with a <code>Cache-Control: no-cache</code> header.</li>
+</ul>
+
+<h3 id="Using_search_keywords_to_open_template_pages">Using search keywords to open template pages</h3>
+
+<p>When using templates, it's common to open the template's code in a browser window to review the comments at the top, which are used to document the template, its parameters, and how to use it properly. To quickly access templates, you can create a Firefox <a href="http://kb.mozillazine.org/Using_keyword_searches">search keyword</a>, which gives you a shortcut you can type in the URL box to get to a template more easily.</p>
+
+<p>To create a search keyword, open the bookmarks window by choosing "Show all bookmarks" in the Bookmarks menu, or by pressing <kbd>Control</kbd>-<kbd>Shift</kbd>-<kbd>B</kbd> (<kbd>Command</kbd>-<kbd>Shift</kbd>-<kbd>B</kbd> on Mac). Then from the utility ("Gear") menu in the Library window that appears, choose "New Bookmark...".</p>
+
+<p>This causes the bookmark editing dialog to appear. Fill that out as follows:</p>
+
+<dl>
+ <dt>Name</dt>
+ <dd>A suitable name for your search keyword; "Open MDN Template" is a good one.</dd>
+ <dt>Location</dt>
+ <dd><kbd>https://github.com/mdn/kumascript/blob/master/macros/%s</kbd></dd>
+ <dt>Tags {{optional_inline}}</dt>
+ <dd>A list of tags used to organize your bookmarks; these are entirely optional and what (if any) tags you use is up to you.</dd>
+ <dt>Keyword</dt>
+ <dd>The shortcut text you wish to use to access the template. Ideally, this should be something short and quick to type, such as simply "t" or "mdnt".</dd>
+ <dt>Description {{optional_inline}}</dt>
+ <dd>A suitable description explaining what the search keyword does.</dd>
+</dl>
+
+<p>The resulting dialog looks something like this:</p>
+
+<p><img alt="" src="https://mdn.mozillademos.org/files/14432/Screen%20Shot%202016-11-28%20at%203.08.39%20PM.png" style="height: 289px; width: 500px;"></p>
+
+<p>Then click the "Add" button to save your new search keyword. From then on, typing your keyword, then a space, then the name of a macro will open that macro in your current tab. So if you used "t" as the keyword, typing <kbd>t ListSubpages</kbd> will show you the page at {{TemplateLink("ListSubpages")}}.</p>
+
+<h2 id="Cookbook">Cookbook</h2>
+
+<p>This section will list examples of common patterns for templates used on MDN, including samples of legacy DekiScript templates and their new KumaScript equivalents.</p>
+
+<h3 id="Force_templates_used_on_a_page_to_be_reloaded">Force templates used on a page to be reloaded</h3>
+
+<p>It bears repeating: To force templates used on a page to be reloaded after editing, hit Shift-Reload. Just using Reload by itself will cause the page contents to be regenerated, but using cached templates and included content. A Shift-Reload is necessary to invalidate caches beyond just the content of the page itself.</p>
+
+<h3 id="Recovering_from_Unknown_Error">Recovering from "Unknown Error"</h3>
+
+<p>Sometimes, you'll see a scripting message like this when you load a page:</p>
+
+<pre class="notranslate">Kumascript service failed unexpectedly: &lt;class 'httplib.BadStatusLine'&gt;</pre>
+
+<p>This is probably a temporary failure of the KumaScript service. If you Refresh the page, the error may disappear. If that doesn't work, try a Shift-Refresh. If, after a few tries, the error persists - <a class="link-https" href="https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&amp;format=itrequest">file an IT bug</a> for Mozilla Developer Network to ask for an investigation.</p>
+
+<h3 id="Broken_wiki.languages_macros">Broken wiki.languages() macros</h3>
+
+<p>On some pages, you'll see a scripting error like this:</p>
+
+<pre class="notranslate">Syntax error at line 436, column 461: Expected valid JSON object as the parameter of the preceding macro but...
+</pre>
+
+<p>If you edit the page, you'll probably see a macro like this at the bottom of the page:</p>
+
+<pre class="notranslate">\{{ wiki.languages({ "zh-tw": "zh_tw/Core_JavaScript_1.5_教學/JavaScript_概要", ... }) }}
+</pre>
+
+<p>To fix the problem, just delete the macro. Or, replace the curly braces on either side with HTML comments <code>&lt;!-- --&gt;</code> to preserve the information, like so:</p>
+
+<pre class="notranslate">&lt;!-- wiki.languages({ "zh-tw": "zh_tw/Core_JavaScript_1.5_教學/JavaScript_概要", ... }) --&gt;
+</pre>
+
+<p>Because Kuma supports localization differently, these macros aren't actually needed any more. But, they've been left intact in case we need to revisit the relationships between localized pages. Unfortunately, it seems like migration has failed to convert some of them properly.</p>
+
+<h3 id="Finding_the_Current_Pages_Language">Finding the Current Page's Language</h3>
+
+<p>In KumaScript, the locale of the current document is exposed as an environment variable:</p>
+
+<pre class="notranslate">var lang = env.locale;
+</pre>
+
+<p>The <code>env.locale</code> variable should be reliable and defined for every document.</p>
+
+<h3 id="Reading_the_contents_of_a_page_attachment">Reading the contents of a page attachment</h3>
+
+<p>You can read the contents of an attached file by using the <code>mdn.getFileContent()</code> function, like this:</p>
+
+<pre class="notranslate">&lt;%
+  var contents = mdn.getFileContent(fileUrl);
+  ... do stuff with the contents ...
+%&gt;
+</pre>
+
+<p>or</p>
+
+<pre class="notranslate">&lt;%-mdn.getFileContent(fileObject)%&gt;
+</pre>
+
+<p>In other words, you may specify either the URL of the file to read or as a file object. The file objects for a page can be accessed through the array <code>env.files</code>. So, for example, to embed the contents of the first file attached to the article, you can do this:</p>
+
+<pre class="notranslate">&lt;%-mdn.getFileContent(env.files[0])%&gt;
+</pre>
+
+<div class="note"><strong>Note:</strong> You probably don't want to try to embed the contents of a non-text file this way, as the raw contents would be injected as text. This is meant to let you access the contents of text attachments.</div>
+
+<p>If the file isn't found, an empty string is returned. There is currently no way to tell the difference between an empty file and a nonexistent one. But if you're putting empty files on the wiki, you're doing it wrong.</p>
+
+<h3 id="Localizing_template_content">Localizing template content</h3>
+
+<p>Templates are not translated like wiki pages, rather any single template might be used for any number of locales.</p>
+
+<p>So the main way to output content tailored to the current document locale is to pivot on the value of <code>env.locale</code>. There are many ways to do this, but a few patterns are common in the conversion of legacy DekiScript templates:</p>
+
+<h4 id="Ifelse_blocks_in_KumaScript">If/else blocks in KumaScript</h4>
+
+<p>The KumaScript equivalent of this can be achieved with simple if/else blocks, like so:</p>
+
+<pre class="notranslate">&lt;% if ("fr" == env.locale) { %&gt;
+&lt;%- template("CSSRef") %&gt; « &lt;a title="Référence_CSS/Extensions_Mozilla" href="/fr/docs/Référence_CSS/Extensions_Mozilla"&gt;Référence CSS:Extensions Mozilla&lt;/a&gt;
+&lt;% } else if ("ja" == env.locale) { %&gt;
+&lt;%- template("CSSRef") %&gt; « &lt;a title="CSS_Reference/Mozilla_Extensions" href="/ja/docs/CSS_Reference/Mozilla_Extensions"&gt;CSS リファレンス:Mozilla 拡張仕様&lt;/a&gt;
+&lt;% } else if ("pl" == env.locale) { %&gt;
+&lt;%- template("CSSRef") %&gt; « &lt;a title="Dokumentacja_CSS/Rozszerzenia_Mozilli" href="/pl/docs/Dokumentacja_CSS/Rozszerzenia_Mozilli"&gt;Dokumentacja CSS:Rozszerzenia Mozilli&lt;/a&gt;
+&lt;% } else if ("de" == env.locale) { %&gt;
+&lt;%- template("CSSRef") %&gt; « &lt;a title="CSS_Referenz/Mozilla_CSS_Erweiterungen" href="/de/docs/CSS_Referenz/Mozilla_CSS_Erweiterungen"&gt;CSS Referenz: Mozilla Erweiterungen&lt;/a&gt;
+&lt;% } else { %&gt;
+&lt;%- template("CSSRef") %&gt; « &lt;a title="CSS_Reference/Mozilla_Extensions" href="/en-US/docs/CSS_Reference/Mozilla_Extensions"&gt;CSS Reference:Mozilla Extensions&lt;/a&gt;
+&lt;% } %&gt;
+</pre>
+
+<p>Depending on what text editor is your favorite, you may be able to copy &amp; paste from the browser-based editor and attack this pattern with a series of search/replace regexes to get you most of the way there.</p>
+
+<p>My favorite editor is MacVim, and a series of regexes like this does the bulk of the work with just a little manual clean up following:</p>
+
+<pre class="notranslate">%s#&lt;span#^M&lt;span#g
+%s#&lt;span lang="\(.*\)" .*&gt;#&lt;% } else if ("\1" == env.locale) { %&gt;#g
+%s#&lt;span class="script"&gt;template.Cssxref(#&lt;%- template("Cssxref", [#
+%s#)&lt;/span&gt; &lt;/span&gt;#]) %&gt;
+</pre>
+
+<p>Your mileage may vary, and patterns change slightly from template to template. That's why the migration script was unable to just handle this automatically, after all.</p>
+
+<h4 id="String_variables_and_switch">String variables and switch</h4>
+
+<p>Rather than switch between full chunks of markup, you can define a set of strings, switch them based on locale, and then use them to fill in placeholders in a single chunk of markup:</p>
+
+<pre class="notranslate">&lt;%
+var s_title = 'Firefox for Developers';
+switch (env.locale) {
+    case 'de':
+        s_title = "Firefox für Entwickler";
+        break;
+    case 'fr':
+        s_title = "Firefox pour les développeurs";
+        break;
+    case 'es':
+        s_title = "Firefox para desarrolladores";
+        break;
+};
+%&gt;
+&lt;span class="title"&gt;&lt;%= s_title %&gt;&lt;/span&gt;
+</pre>
+
+<h4 id="Use_mdn.localString">Use <code>mdn.localString()</code></h4>
+
+<p>A recent addition to the <code>MDN:Common</code> module is <code>mdn.localString()</code>, used like this:</p>
+
+<pre class="notranslate">&lt;%
+var s_title = mdn.localString({
+  "en-US": "Firefox for Developers",
+  "de": "Firefox für Entwickler",
+  "es": "Firefox para desarrolladores"
+});
+%&gt;
+&lt;span class="title"&gt;&lt;%= s_title %&gt;&lt;/span&gt;
+</pre>
+
+<p>This is more concise than the switch statement, and may be a better choice where a single string is concerned. However, if many strings need to be translated (e.g., as in <a class="link-https" href="https://github.com/mdn/kumascript/blob/master/macros/CSSRef.ejs" title="CSSRef">CSSRef</a>), a switch statement might help keep all the strings grouped by locale and more easily translated that way.</p>
+
+<p>When the object does not have the appropriate locale, the value of "en-US" is used as the initial value.</p>
+
+<h2 id="參見">參見</h2>
+
+<ul>
+ <li><a href="http://kuma.readthedocs.io/en/latest/" title="Getting started with Kuma">Getting started with Kuma</a></li>
+ <li><a href="https://github.com/mdn/kumascript" title="Project:en/KumaScript reference">KumaScript reference</a></li>
+ <li><a class="link-https" href="https://wiki.mozilla.org/MDN/Kuma" title="https://wiki.mozilla.org/MDN/Kuma">Kuma wiki</a></li>
+</ul>
diff --git a/files/zh-tw/mdn/tools/kumascript/troubleshooting/index.html b/files/zh-tw/mdn/tools/kumascript/troubleshooting/index.html
new file mode 100644
index 0000000000..e3dcd998d5
--- /dev/null
+++ b/files/zh-tw/mdn/tools/kumascript/troubleshooting/index.html
@@ -0,0 +1,63 @@
+---
+title: 修復 KumaScript 錯誤
+slug: MDN/Tools/KumaScript/Troubleshooting
+translation_of: MDN/Tools/KumaScript/Troubleshooting
+---
+<div>{{MDNSidebar}}</div><div class="summary">
+<p>網頁上出現一塊又大又醜的 <a href="/en-US/docs/MDN/Kuma/Introduction_to_KumaScript">KumaScript</a> 錯誤會惹惱讀者，好險任何擁有 MDN 帳號的人，可以編輯文件來修復錯誤。當一個頁面出現錯誤的時候，該面會被列在<a href="/zh-TW/docs/with-errors">有錯誤的文件</a>裡面。網站編輯者會透過這份清單，找出並修復錯誤。這篇文章列出 KumaScript 錯誤的四種類型，還有解決他們的步驟。</p>
+</div>
+
+<h2 id="文件解析錯誤">文件解析錯誤</h2>
+
+<p><code>DocumentParsingError</code> errors appear when KumaScript has trouble understanding something in the document itself. The most common cause is a syntax error in a <a href="/en-US/docs/MDN/Contribute/Content/Macros">macro</a>.</p>
+
+<p>Check for:</p>
+
+<dl>
+ <dt>Use of curly braces without intending to call a macro.</dt>
+ <dd>If you need to write  \{ in a document without calling a macro you can escape it with a \ like this: <code>\\{</code></dd>
+ <dt>Use of a special character in a macro parameter.</dt>
+ <dd>If you need to use a " or a \  inside of a macro parameter they can be escaped with a \ like this: <code>\\</code> or <code>\"</code></dd>
+ <dt>Missing commas between macro parameters.</dt>
+ <dd>Macro parameters need to be delimited by a comma (,) but not at the end of the list of parameters; for example <code>\{\{anch("top", "Back to top")}}</code>.</dd>
+ <dt>HTML tags appearing inside a macro call</dt>
+ <dd>If you apply styling to a macro, it will often break because, for example, a <code>&lt;/code&gt;</code> tag may have appeared inside the macro code in the source code. Check the source view to see what's there, and remove any unnecessary styling.</dd>
+</dl>
+
+<ul>
+</ul>
+
+<h2 id="TemplateLoadingError">TemplateLoadingError</h2>
+
+<p><code>TemplateLoadingError</code> errors appear when KumaScript has trouble finding which <a href="/en-US/docs/MDN/Contribute/Content/Macros">macro</a> to include on a page.</p>
+
+<p>Check for:</p>
+
+<dl>
+ <dt>Misspelling of macro names or renamed macros.</dt>
+ <dd>You can try visiting the template page for the macro to see if it's named correctly. The URL for the template page can be constructed by adding the template name to the end of the URL <code>https://developer.mozilla.org/en-US/docs/Template: — </code>for example the template page for <code>\{\{anch("top", "Back to top")}}</code>  is <a href="https://developer.mozilla.org/en-US/docs/Template:anch">https://developer.mozilla.org/en-US/docs/Template:anch</a>.<br>
+ <br>
+ There is a partial list of <a href="https://developer.mozilla.org/en-US/docs/MDN/Contribute/Content/Custom_macros">macros for the MDN</a>, which may include the existing macro you are looking at, or its correct/new spelling.</dd>
+</dl>
+
+<div class="note">
+<p><strong>Tip:</strong> You can make it quick and easy to jump to a specific macro by adding a <a href="http://kb.mozillazine.org/Using_keyword_searches">search keyword</a> to Firefox. &lt;&lt;&lt;MORE SOON&gt;&gt;</p>
+</div>
+
+<h2 id="TemplateExecutionError">TemplateExecutionError</h2>
+
+<p><code>TemplateExecutionError</code> errors appear when KumaScript encounters an error in the macro. These errors can only be fixed by admin users and need to be reported as bugs.</p>
+
+<p>Before reporting an error check to see that it hasn't already been fixed. You can do this by forcing KumaScript to give you a fresh copy of the page by holding down <kbd>Shift</kbd> while you refresh the page (<kbd>Shift</kbd> + <kbd>Ctrl</kbd> + <kbd>R</kbd> on Windows/Linux, <kbd>Shift</kbd> + <kbd>Cmd</kbd> + <kbd>R</kbd> on Mac).</p>
+
+<p>If the error persists, <a href="https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla_Developer_Network&amp;component=General#h=detail|bug">report a bug</a>, including the URL of the page and the text of the error.</p>
+
+<h2 id="未知和錯誤">未知和錯誤</h2>
+
+<p>如果錯誤並不屬於上述任何一項時，將被歸類為未知．</p>
+
+<p>Check for fixes and report persistent bugs like described under <a href="#TemplateExecutionError">TemplateExecutionError</a>.</p>
+
+<p> </p>
+
+<p> </p>