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

6 files changed, 0 insertions, 566 deletions

diff --git a/files/ja/mdn/contribute/howto/link_a_github_account/index.html b/files/ja/mdn/contribute/howto/link_a_github_account/index.html
deleted file mode 100644
index 4f7443b7f0..0000000000
--- a/files/ja/mdn/contribute/howto/link_a_github_account/index.html
+++ /dev/null
@@ -1,111 +0,0 @@
----
-title: GitHub アカウントを MDN プロフィールに結びつける方法
-slug: MDN/Contribute/Howto/Link_a_GitHub_account
-tags:
-  - Documentation
-  - MDN
-  - MDN Meta
-  - MDN Project
-translation_of: Archive/MDN/Howto_Link_a_Github_account
----
-<div>{{MDNSidebar}}</div>
-
-<div>{{IncludeSubnav("/en-US/docs/MDN")}}</div>
-
-<div class="note">
-<p><strong>Note: </strong>Support for Persona logins on MDN was disabled on November 1, 2016. The method for adding a Github account to your profile therefore no longer works. If you didn't add a GitHub login to your MDN account before we disabled Persona logins, please <strong>file an <a class="external external-icon" href="https://mzl.la/accounthelp">"Account Help" bug</a> </strong>on Bugzilla. For further reading about the end of life of Persona, see: <a href="https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers">Persona shutdown guidelines</a>.</p>
-</div>
-
-<p><span class="seoSummary">Mozilla の <a href="https://login.persona.org/">Persona</a> 認証システムは終了しつつあるため、MDN に貢献したいすべてのユーザーは、2016年11月1日までにMDN にサインインする別の方法を持っておく必要が出てきます。現在は、唯一サポートしている代替品が GitHub なので、その日以降に MDN にサインイン・編集するには <a href="https://github.com/">GitHub</a> アカウントが必要になります。この記事ではあなたの MDN プロフィールに GitHub 認証を追加する方法を述べます。</span></p>
-
-<div class="warning">
-<p>2016年11月1日までにこれを行わないとなりません、さもないと、MDNにサインインする方法がもうなくなってしまうでしょう!</p>
-</div>
-
-<h2 id="概要">概要</h2>
-
-<p>GitHub 認証をアカウントに追加するのは難しくありません。少し後に詳細に入りますが、まず最初に、ステップの一覧がこちらです:</p>
-
-<ol>
- <li>Persona で <a href="/docs/MDN/Signing_in">MDN アカウントにサインインする</a></li>
- <li><a href="https://developer.mozilla.org/ja/users/account/connections">アカウント接続</a> ページに移動する</li>
- <li>GitHub 認証を追加する</li>
-</ol>
-
-<h2 id="詳細な手順">詳細な手順</h2>
-
-<p>こちらが、知っておくべきこと全てのやり方を詳しく説明したステップバイステップガイドです。</p>
-
-<h3 id="MDN_アカウントにサインインする">MDN アカウントにサインインする</h3>
-
-<ol>
- <li>MDN ページの上部で、 <strong>サインイン</strong> ボックスにマウスを重ねるかタップします。利用できる認証ボックス、つまり <strong>Persona</strong> か <strong>GitHub</strong> が表示されます<br>
-  <img alt="Sign in box on MDN, showing Persona and Github." src="https://mdn.mozillademos.org/files/13426/Mozilla_Developer_Network_-__Private_Browsing_.png" style="border-style: solid; border-width: 1px; height: 140px; width: 425px;"></li>
- <li><strong>Persona</strong> を選択し、機密情報を使ってサインインします。認識されないエラーが出た場合、今使っているeメールアドレスが何であろうと、MDNにPersonaをリンクした時のeメールアドレスを使っているか確認してください。問題が続く場合、 {{anch("Persona doesn't remember me")}}を見てください。</li>
-</ol>
-
-<h3 id="アカウント接続_ページに移動する">"アカウント接続" ページに移動する</h3>
-
-<p>アカウント接続ページにたどり着くには2つの方法があります。</p>
-
-<p>最初は、単に下記のリンクをクリックします。</p>
-
-<p>あるいは、下記を行います:</p>
-
-<ol>
- <li>MDN ページ上部にあるユーザ名をクリックします。(ログイン前に <strong>サインイン</strong> ボックスがあった場所にあります) これでプロフィールページに移ります。</li>
- <li>"歯車" メニューを開き、<strong>アカウント接続</strong> をクリックします。<img alt='Gear menu in profile, showing the "Account connections" option' src="https://mdn.mozillademos.org/files/13428/SheppyWork___MDN_-__Private_Browsing_.png" style="height: 217px; width: 219px;"></li>
-</ol>
-
-<h3 id="GitHub_認証を追加する">GitHub 認証を追加する</h3>
-
-<p>あなたは "アカウント接続" ページにいます。ここにはすでにあなたの MDN プロフィールと結ばられている外部アカウントが一覧になっています。GitHub が既に載っていたら、おめでとうございます! もう出発できます! ただし、確実にパスワードを覚えているようにするために、MDN からサインアウトしてからまた GitHub の秘密情報でサインインするのを試してみます。</p>
-
-<p>GitHub が載っていない場合、ページの下部付近にて、既にリンクされた外部アカウントを見ます。そこで <strong>新しいアカウントを接続する</strong> という節が見えて、MDN プロフィールに接続できるアカウントの種類が一覧されています。それはこのような感じです:</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/13430/Account_Connections___MDN_-__Private_Browsing_.png" style="height: 79px; width: 476px;"></p>
-
-<p>GitHub を追加するには:</p>
-
-<ol>
- <li><strong>GitHub と接続</strong>をクリックします。 MDN は GitHub に連絡してアカウントをリンクする権限を要求します。GitHub にまだサインインしていない場合、それを求められます:<br>
-  <img alt="Screenshot of GitHub sign in window." src="https://mdn.mozillademos.org/files/13444/GitHub_Sign_In.png" style="height: 447px; width: 356px;"></li>
- <li>GitHub アカウントで2要素認証を有効化している場合、認証コードの入力を求められます:<img alt="Screenshot of GitHub's Two-factor authentication window." src="https://mdn.mozillademos.org/files/13460/GitHub_-_Where_software_is_built.png" style="height: 448px; width: 361px;"></li>
- <li>GitHub アカウントにサインインしており、GitHub と MDN とのリンクの承認を求められるでしょう(すでに何らかの理由により、承認済みでない場合)。このページは下記に出ています。<br>
-  <img alt='Screenshot of GitHub "Authorize application" window.' src="https://mdn.mozillademos.org/files/13456/Authorize_Mozilla_Developer_Network.png" style="height: 420px; width: 766px;"><br>
-  緑の <strong>Authorize application</strong> ボタンをクリックして、MDN アカウントが GitHub アカウントにアクセスできる権限を与えます。GitHub アカウントがうまく MDN プロフィールと結びつけられたら、下記のメッセージが見えます:<br>
-  <img alt="Account successfully created." src="https://mdn.mozillademos.org/files/13454/Edit_Your_Profile___MDN.png" style="height: 57px; width: 646px;"></li>
-</ol>
-
-<p>MDN のサインインに GitHub を使えるだけでなく、実際すでに GitHub 認証を使ってサインインしています! いまやあなたは Persona の終了に対する準備ができています。パスワードマネージャをインストールしていれば、必要に応じて更新してください。</p>
-
-<h2 id="トラブルシューティング">トラブルシューティング</h2>
-
-<p>プロフィールに GitHub アカウントを追加しようとする時に問題に入った場合、下記のトラブルシューティング tips が役立つでしょう。</p>
-
-<h3 id="Error_Could_not_find_profile_matching_account">Error: Could not find profile matching account</h3>
-
-<p>あなたのプロフィールに GitHub アカウントを追加しようとして "Could not find profile matching account," というエラーが出た場合、いくつか異なる事を意味します。GitHubアカウントに複数のアカウントを持っている場合、いくらか混乱があります; GitHub は MDN が期待するeメールアドレスに報告せず、その結果エラーとなります。他の処理中のグリッチでも同じメッセージが出る事もあります。</p>
-
-<p>この問題の回避策は: ブラウザのプライベートウィンドウを開きます; たとえば Firefox ではファイルメニューで "新しいプライベートウィンドウ" を選びます (または <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> [Mac では<kbd>Cmd</kbd>-<kbd>Shift</kbd>-<kbd>P</kbd>])。そこでMDNへ移動し、<a href="/en-US/docs/MDN/Signing_in">MDN アカウントにサインインして</a> 上記に説明したように、あなたのプロフィールに GitHub アカウントを再度追加してみてください。</p>
-
-<h3 id="アカウント接続のページで_GitHub_認証が表示されない">アカウント接続のページで GitHub 認証が表示されない</h3>
-
-<p>それはキャッシュの問題かもしれません。ページをリロードするかログアウトして再びログインすれば問題は解決するでしょう。</p>
-
-<h3 id="Persona_に私の情報が記憶されていない">Persona に私の情報が記憶されていない</h3>
-
-<p>Persona にログインを試みてMDNアカウントに GitHub ログインしようとした時に、 "Your email address is new to us,(あなたのeメールアドレスを我々は知りません)" と告げられた場合、Personaに最終ログインしてから長い時間が経ったためシステムがあなたのeメールアドレスを削除してしまった可能性が高いです。これはいくらかの期間の後に起こります; つまりPersonaのログインウィンドウはこの状況でこのようになります:</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/13765/unknown-to-persona.png" style="height: 533px; width: 800px;"></p>
-
-<p>If this happens, you need to simply follow Persona's instructions to create a new password for that email address. MDN doesn't care about this process; the fact that your email address matches up is all that matters. A confirmation email will be sent to verify that you own the email address, probably from <code>no-reply@persona.org</code>. If you have spam filtering, it may be sent to your spam folder.</p>
-
-<p>Once you've finished the process of setting the password for the email address you used to log into MDN, your access to MDN will be restored. Then you can follow the steps in {{anch("Detailed instructions")}} above to add your GitHub login to your MDN account.</p>
-
-<h2 id="こちらも見てください">こちらも見てください</h2>
-
-<ul>
- <li><a href="/docs/MDN/Contribute/Howto/Create_an_MDN_account">MDN アカウントを作成する方法</a></li>
- <li><a href="/docs/MDN/Getting_started">MDN を始めるには</a></li>
-</ul>
diff --git a/files/ja/mdn/contribute/persona_sign-in/index.html b/files/ja/mdn/contribute/persona_sign-in/index.html
deleted file mode 100644
index 94a28d3e88..0000000000
--- a/files/ja/mdn/contribute/persona_sign-in/index.html
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: MDNへのPersonaでのサインインについて
-slug: MDN/Contribute/Persona_sign-in
-tags:
-  - Documentation
-  - MDN
-  - MDN Meta
-  - Mozilla
-  - Persona
-translation_of: Archive/MDN/Persona_sign-ins
----
-<div>{{MDNSidebar}}</div><div class="warning">
-<p>MDNへのサインインを継続できるように、<a href="/docs/MDN/Contribute/Howto/Link_a_GitHub_account">今すぐあなたのMDNプロフィールとGitHubを紐付けてください</a>。</p>
-</div>
-
-<p>現在、貢献者は、MozillaのPersonaとGitHubという、異なる2つの認証方法でMDNにサインインできます。しかし、2016年11月1日からは、ログインのための選択肢からPersonaが除外されます。従って、MDNへログインできなくなるのを防ぐために、あなたのアカウントでGitHubでの認証を有効化していただく必要があります。</p>
-
-<p>ご不便をおかけして申し訳ありませんが、仕方のないことなのです。</p>
-
-<h2 id="なぜPersonaは除外されるのか">なぜPersonaは除外されるのか</h2>
-
-<p>MozillaはPersonaプロジェクトを終了しており、サーバが2016年11月1日に無効化されるためです。Mozilla Wikiで、Personaを廃止するという<a href="https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers#FAQs">Mozillaのこの決定についてより詳しく知る</a>ことができます。</p>
-
-<h2 id="Personaはいつ除外されるのか">Personaはいつ除外されるのか</h2>
-
-<p>私たちは、2016年11月1日に、認証方法としてのPersonaの利用を無効化します。言い換えれば、Personaを使ってMDNにサインインできるであろう最後の日は、2016年10月31日となるでしょう。 私たちは今後、<a href="/docs/MDN/Contribute/Howto/Link_a_GitHub_account">MDNプロフィールにGitHubアカウントを加える</a>ためのお知らせを、頻度を上げながら、かつ緊急性の度合いを増しながら発行していきます。MDNアカウントへのアクセスを失うようなあらゆるリスクを防ぐために、なるべく早く紐付けを行ってください。</p>
-
-<h2 id="MDNが他の認証方法を採用する予定はありますか">MDNが他の認証方法を採用する予定はありますか?</h2>
-
-<p>とてもそうしたいところですが、私たちの要求を満たすような他の認証方法をまだ見つけられていません。さらに、他の認証方法を採用するのに必要な開発者資源を現在私たちは持っていません。当面、貢献者としてのMDNへのアクセスを保つための<em>唯一の</em>選択肢は、<a href="/docs/MDN/Contribute/Howto/Link_a_GitHub_account">MDNプロフィールにGitHubアカウントを紐付ける</a>ことのみとなります。</p>
-
-<p>もちろん、私たちのコンテンツを読むだけの場合、MDNにサインインする必要はありません。しかし、貢献のためのアカウントを持っていてかつ、今後も貢献できるようにしておきたいと思っているなら、2016年10月31日になる前に、<em><strong>なるべく早くあなたのプロフィールにGitHubアカウントを追加</strong></em>してください。</p>
diff --git a/files/ja/mdn/contribute/processes/trello/index.html b/files/ja/mdn/contribute/processes/trello/index.html
deleted file mode 100644
index 6404404c6e..0000000000
--- a/files/ja/mdn/contribute/processes/trello/index.html
+++ /dev/null
@@ -1,94 +0,0 @@
----
-title: Trello
-slug: MDN/Contribute/Processes/Trello
-translation_of: Archive/Meta_docs/Trello
----
-<div>{{MDNSidebar}}</div>
-
-<p><span class="seoSummary">MDN コミュニティは <a href="https://trello.com/b/HAhl54zz/mdn-content-team-status">Trello 掲示板</a> を使用して改善する必要のあるもの、更新する必要のあるもの、そしてコンテンツに追加する必要のあるものを組織化し、その進行を管理しています。このガイドは　Trello が何なのか、どのように使うのかを知る助けになるでしょう。</span></p>
-
-<p>Having a tool like this to maintain a public task list lets our entire community participate in planning, and helps everyone understand what we're working on. That way, both MDN staff writers and our amazing community of volunteer contributors can know what's going on at a glance. Our board is public, meaning that <a href="https://trello.com/b/HAhl54zz/mdn-content-team-status">everyone can see it</a>. If you already have an account on Trello, you can star (favorite/bookmark) the board so that you can get to it quickly whenever you connect to Trello.</p>
-
-<h2 id="Trello_の紹介">Trello の紹介</h2>
-
-<p>The Trello software is a Web application (created by Trello, Inc.) which you can access using your Web browser or an <a href="https://trello.com/platforms">app on your mobile device</a> (Android, iOS, Kindle Fire, and Windows 8 are among the supported platforms). This lets you check or update the Trello board at your convenience. For more information, you can read their <a href="https://trello.com/about">"about" page</a>.</p>
-
-<h3 id="Trello_掲示板">Trello 掲示板</h3>
-
-<p>A board is composed of <strong>lists</strong>, and each list is composed of <strong>cards</strong>. Every card represents an "action item", which is a task that needs to be accomplished. You can add comments, due dates, detailed lists of sub-tasks, etc. on every card. But most importantly, you can drag and drop a card from a list to another, which means the task has changed status; for instance, you might drag a card from the "Doing" column to the "Review needed" column, which indicates that you've finished the task and would like for someone to review your work.</p>
-
-<p><img alt="Screenshot of the MDN content Trello board." src="https://mdn.mozillademos.org/files/10351/mdn_board.JPG" style="border-style: solid; border-width: 1px; height: 460px; width: 968px;"></p>
-
-<h4 id="Lists">Lists</h4>
-
-<p>A list is a set of cards; while you can assign whatever meaning you wish to each column, the MDN team uses each column to represent the status of the task. The farther to the right the column is, the closer to complete the task is. This is similar to the <a href="http://hamberg.no/gtd/">GTD method</a> or the <a href="https://en.wikipedia.org/wiki/Kanban#Kanban_cards">Kanban methodology</a>.</p>
-
-<p>We have the following primary lists (other lists may crop up temporarily from time to time):</p>
-
-<dl>
- <dt>On Hold</dt>
- <dd>The tasks here have been accepted as something that need to be done, but are not currently being actively worked on. When work begins on a task, it should advance to the next column.</dd>
- <dt>Doing</dt>
- <dd>The tasks in this column are actively being worked on.</dd>
- <dt>Review Needed</dt>
- <dd>The tasks in this list have been completed but the writer(s) would like someone to review the work to ensure that it's accurate and/or stylistically/grammatically.</dd>
- <dt>No Update in the last 14 days</dt>
- <dd>Bugs in this list have been languishing with no new information for more than two weeks. These bugs are in danger of being moved back into the On Hold list unless their status is updated soon.</dd>
- <dt>Completed in...</dt>
- <dd>We create lists of bugs created in specific months to help us track our rate of progress and to be able to provide achievement lists</dd>
-</dl>
-
-<p>Lists are simply are a collection of cards with a title, used to organize cards.</p>
-
-<h4 id="Cards">Cards</h4>
-
-<p>A card has much more content in it. As mentioned earlier, a card corresponds to a specific task or project. The card is described by its title which is displayed on the "front" of the card when you're looking at the board. Clicking on a card "flips" the card, showing you a panel with additional details. The detail view looks something like this:</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/10353/screenshot-trello%20com%202015-04-02%2013-20-54.png" style="height: 603px; width: 510px;"></p>
-
-<p>A card's detail view has these sections:</p>
-
-<dl>
- <dt>1. Members</dt>
- <dd>The members of the board that are assigned to this task/card. These are the Trello users that are working on the task in some way. Here, we can see that four people are involved with this task.</dd>
- <dt>2. Labels</dt>
- <dd>You can think of labels as themes or categories that can apply to more than one list. Here, we can see that this card is related to "Open Web Docs" (a category), "Q1 Delivery" (a planning tag), "Learning Area" (a tag indicating a<a href="/en-US/Learn"> section of MDN</a>), etc. These labels are used for organizational purposes, but are also helpful for filtering; see {{anch("Filters")}} below.</dd>
- <dt>3. Due date</dt>
- <dd>You can add a due date for a card to help with planning. This date can also be used for sorting and filtering. Trello can also be configured to display a calendar showing items that are due in a given time period, but this feature is not currently enabled on the MDN Content Team Status board.</dd>
- <dt>4. Content</dt>
- <dd>In this example, the card has a checklist to detail the precise actions that are needed to complete the task. You might also find comments and attachments inside a card. So if someone wants to put a note for this card, one can add a comment and so on. Usually, checklists are used to break down a task in smaller units which do not need to be displayed for everyone on the board.</dd>
-</dl>
-
-<h4 id="Filters">Filters</h4>
-
-<p>If you look back at the <a href="https://mdn.mozillademos.org/files/10351/mdn_board.JPG">first screenshot</a>, you can see that there are a lot of cards. While working on some project, you might want to focus on specific ones (such as those associated with a particular technology or project). To make the board clearer and to find the right cards more efficiently, you can use filters.</p>
-
-<p>For example, if you only want to see the cards representing tasks or projects that are first quarter goals, you can turn on the corresponding filter on the label "Q1 Deliverables" and get this as a result:</p>
-
-<p><img alt="" src="https://mdn.mozillademos.org/files/10355/screenshot-trello%20com%202015-04-02%2013-43-10.png" style="border-style: solid; border-width: 1px; height: 349px; width: 753px;"></p>
-
-<p>Experiment with filters! You can filter on members (to find work being done by specific people), due dates, and more.</p>
-
-<h2 id="Trello_の使い方">Trello の使い方</h2>
-
-<p>Every member of the writing staff is a member of this board. In addition, volunteers can easily get access too. See {{anch("Getting involved")}} to learn how.</p>
-
-<p>Once you have access, you can either create cards representing proposed or ongoing projects, and you can add yourself to a card to indicate that you intend to work on that task. You can then update cards with new details such as new comments, attachments, or changes to to-do lists on the cards.</p>
-
-<h2 id="参加するには">参加するには</h2>
-
-<p>We encourage you to join us and <a href="/en-US/docs/MDN/Contribute">contribute</a> to these tasks! Pick a task that is described on one of the cards and <a href="/en-US/docs/MDN/Getting_started">start working on it</a>. Once you are working on it, you'll need to be able to edit the corresponding card. For this you'll need to have a Trello account, which is free. Then you will need an administrator of the board to add you to the board. To contact an administrator, you can:</p>
-
-<ul>
- <li><a href="mailto:mdn-admins@mozilla.org?subject=MDN%20Content%20Trello%20board%20write%20access%20request&amp;body=I%20would%20like%20write%20access%20for%20the%20MDN%20Content%20Trello%20board.%0A%0AI%20plan%20to%20work%20on%3A%20%3Cadd%20details%20here%3E%0A%0AMy%20Trello%20username%20is%3A%20%3Cadd%20username%20here%3E" title="Email the MDN administration team">Email the MDN administration team</a></li>
- <li>Or just drop into the <a href="https://chat.mozilla.org/#/room/#mdn:mozilla.org">MDN Web Docs chat room</a> any time and politely ask if an admin is around. Typically there will be at least one around between around 5 AM and 5 PM Pacific time.</li>
-</ul>
-
-<h2 id="こちらもご覧ください">こちらもご覧ください</h2>
-
-<ul>
- <li><a href="https://trello.com/b/p56Gwq46/mdndev-rocks">MDN 開発チームの Trello 掲示板</a></li>
- <li><a href="https://trello.com/b/LDggrYSV/learning-area-glossary">The Learning Area Trello board</a></li>
- <li><a href="https://trello.com/guide">The Trello Guide</a></li>
- <li><a href="/en-US/docs/MDN/Community/Whats_happening">Following what is happening on MDN</a></li>
-</ul>
diff --git a/files/ja/mdn/tools/content_kits/index.html b/files/ja/mdn/tools/content_kits/index.html
deleted file mode 100644
index b10f0bb06d..0000000000
--- a/files/ja/mdn/tools/content_kits/index.html
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: コンテンツキット
-slug: MDN/Tools/Content_kits
-translation_of: Archive/MDN/Content_kits
----
-<div>{{MDNSidebar}}</div><div class="summary">
-<p><span class="seoSummary">MDN コンテンツキットはある題材について技術リソースを集めたもので、 地域の技術者の会合を開いたり、 イベント、会議、ワークショップなどで技術的なプレゼンテーションを行う時に役に立ちます。</span></p>
-</div>
-
-<p>Each MDN Content Kit offers relevant, up-to-date technical information for presenters and teachers on a particular topic related to web development or web app development, such as Web APIs, useful libraries, or developer tools. Content Kits may also be focused on Mozilla products, tools, or technologies such as Firefox Developer Tools or <a href="https://www.mozilla.org/en-US/research/">Mozilla Research</a> projects. Resources may include slides, demos, code samples, screencasts, video, exercises, etc.</p>
-
-<p>By providing MDN Content Kits, MDN aims to grow developer engagement with Mozilla in regional communities, and increase standards-based web development globally.</p>
-
-<h2 id="MDN_コンテンツキットを作成する_または_寄贈する">MDN コンテンツキットを作成する または 寄贈する</h2>
-
-<p>Kits can be built by anyone, and we encourage people to suggest and build kits! Individuals may also contribute to existing content kits by submitting a pull request on Github.  Get started with the <a href="https://github.com/mdn/content-kit-template">MDN Content Kit Template</a> on Github or read about the project on the <a href="https://wiki.mozilla.org/MDN/Projects/Content/MDN_Content_Kits">MDN wiki</a>.</p>
-
-<div class="note">
-<p><strong>Note</strong>: There is also a <a href="http://chrisdavidmills.github.io/content-kit-guide/">Content Kit Guide</a> available, to give you more guidance in creating content kits.</p>
-</div>
-
-<h2 id="現在のコンテンツキット">現在のコンテンツキット</h2>
-
-<ul>
- <li><a href="http://mdn.github.io/beginning-programming-content-kit/">Beginners Programming</a>. This kit contains resources you can use to learn and teach general programming principles and the JavaScript language. The teacher will need to know HTML and JavaScript. The students will not need any previous web development knowledge but knowing how the web works and what web pages are will help. The Beginners Programming kit has 8 sections, each of which takes 1-1.5 hours to teach.</li>
- <li><a href="http://end3r.github.io/Gamedev-Canvas-Content-Kit/">Beginners Game development with HTML5 Canvas</a>. In this kit you can learn the basics of game development using <a href="/en-US/docs/Web/JavaScript">JavaScript</a> and <a href="/en-US/docs/Web/API/Canvas_API">HTML5 Canvas</a>. All you need is a little prior experience with JavaScript basics.</li>
- <li><a href="http://end3r.github.io/Gamedev-Phaser-Content-Kit/">Beginners Game development with Phaser</a>. In this kit you can learn the basics of game development using Phaser, a popular HTML5 game development framework. This differs from the above kit because it doesn't teach you any pure JavaScript, instead giving you expeience of working with a framework. All you need is a little prior experience with JavaScript basics.</li>
- <li><a href="https://gist.github.com/callahad/1d0885dd70b157c3978e#file-valence-content-kit-md">Valence</a>.  Valence is the public-facing name for the Firefox Developer Tools Adapters, which extend the Firefox WebIDE to allow for remotely debugging pages in Chrome or Safari from within the Firefox Developer Tools. Valence is still in development and is experimental. Valence is distributed as an add-on, which is automatically downloaded and installed by Firefox Developer Edition, though the raw .xpi file is available on <a href="http://archive.mozilla.org/pub/labs/valence/">archive.mozilla.org</a> and its source code is on GitHub.  The Valance Content Kit is for an experienced web developer to give a presentation to a group of experienced web developers.</li>
- <li><a href="https://github.com/sole/ck-node-firefox">node-firefox</a>. Node-firefox is a series of node.js modules for interacting with Firefox runtimes via the Developer Tools remote debugging protocol. The node-firefox Content Kit is for an experienced web developer to give a presentation to a group of experienced web developers.</li>
- <li><a href="https://github.com/chrisdavidmills/html5-captions-and-subtitles-content-kit">Working with HTML5 Video: Adding captions and subtitles</a>. This kit contains everything you might need to present a one hour presentation on HTML5 video captions and subtitles. This includes using the {{htmlelement("track")}} element, WebVTT syntax, CSS extensions, and the difference between captions and subtitles.</li>
- <li><a href="http://codingfree.github.io/l10n-content-kit">l10n.js</a>. JavaScript library that enables localization through the native JavaScript method intended for it. There is already a placeholder method for all API calls as specified in the ECMAScript specification and is present in all JavaScript engines.</li>
- <li><a href="https://github.com/TatumCreative/mdn-matrix-math">Matrix Math for the Web</a>. This content kit is brief overview of manipulating 3d objects with matrices (a concept from linear algebra.) Matrix math is used heavily in WebGL, but web developers are more familiar with DOM manipulations. This intro divorces the explanation of matrices from the WebGL APIs by using the CSS3 matrix3d transform. It demonstrates translation, scale, and rotation transformations, as well as exploring how to compose a single matrix transform from multiple transforms through matrix multiplication.</li>
- <li><a href="https://github.com/TatumCreative/mdn-model-view-projection">WebGL Model View Projection</a>. This content kit explores how to take data within a WebGL project, and project it into the proper spaces to display it on the screen. It assumes a knowledge of basic matrix math using translation, scale, and rotation matrices. It explains the three core matrices that are typically used to represent a 3d object: the model, view and projection matrices.</li>
- <li><a href="https://github.com/TatumCreative/mdn-lighting-models">WebGL Lighting Models</a>. Getting a model projected onto the screen using WebGL is only the first step for working in 3d. The next is applying a shading or lighting model to it. This content kit walks through the steps on how to build the classic Lambertian lighting model and the Blinn Phong lighting model.</li>
-</ul>
-
-<h2 id="MDN_コンテンツキットを利用する">MDN コンテンツキットを利用する</h2>
-
-<p>Hints on using Content Kits before, during, and after a meetup. Note that these points are representative of a general Content Kit — not all points will necessarily apply to all kits.</p>
-
-<h3 id="会合の前に"><span class="mw-headline" id="Prior_to_a_meetup">会合の前に</span></h3>
-
-<ol>
- <li>Review the content kit and all supporting materials, including relevant MDN articles.</li>
- <li>Download the demo project and play with it until you feel comfortable demoing it.</li>
- <li>Download the video, so you can play it locally if all else fails.</li>
-</ol>
-
-<h3 id="会合の中で"><span class="mw-headline" id="During_the_meetup">会合の中で</span></h3>
-
-<ol>
- <li>Present the topic, including a live demo (or recorded, if necessary.)</li>
- <li>Lead the group in a discussion of the topic, or an activity with the demo project.</li>
-</ol>
-
-<h3 id="会合の後で"><span class="mw-headline" id="After_the_meetup">会合の後で</span></h3>
-
-<ol>
- <li>Submit issues for any problems you encountered with the kit.</li>
- <li>Submit pull requests for any changes you made to the kit.</li>
-</ol>
-
-<h2 id="新しい_MDN_コンテンツキットを提案する">新しい MDN コンテンツキットを提案する</h2>
-
-<p>If you would like to propose a new topic for an MDN Content Kit, please add your topic to <a href="https://devengage.etherpad.mozilla.org/DevMeetupTopics">this etherpad</a> as well as on the <a href="https://lists.mozilla.org/listinfo/mdn">MDN mailing list</a>.</p>
-
-<p>If you propose a new Content Kit topic, please let us know how you will use the new MDN Content Kit and whether you will provide us feedback. We are looking for proposals for topics that will be used by groups that can provide us with feedback so that we can continue to improve and grow the collection of MDN Content Kits.</p>
diff --git a/files/ja/mdn/tools/zones/index.html b/files/ja/mdn/tools/zones/index.html
deleted file mode 100644
index 2bb4599e2d..0000000000
--- a/files/ja/mdn/tools/zones/index.html
+++ /dev/null
@@ -1,203 +0,0 @@
----
-title: ゾーン
-slug: MDN/Tools/Zones
-tags:
-  - Deprecated
-  - Guide
-  - MDN Meta
-  - Site-wide
-  - Tools
-translation_of: Archive/MDN/Zones
----
-<div>{{MDNSidebar}}</div><p><span class="seoSummary"><strong>ゾーン</strong>は MDN の特別なエリアで、そのコンテンツは特別ゾーンナビゲーションボックス、ページのヘッダにおける強調された視覚要素のような追加ユーザインタフェースと共に提供されます。</span> このガイドはゾーンの構築と維持について取り扱います。</p>
-
-<div class="warning">
-<p><strong>ゾーンの使用は廃止されました</strong><br>
- Due to an unsatisfactory user experience and the performance costs of its implementation, we are in the process of deprecating zones. <em>Please only create a new zone if you absolutely must</em>; generally, this should only be done to fix problems related to content which is a zone in English but not in other locales.  Please drop into #mdn on IRC to ask questions about anything you read here, especially if you're considering creating a zone or turning any existing material into a zone.</p>
-</div>
-
-<h2 id="ゾーンの特徴">ゾーンの特徴</h2>
-
-<p>Once you've created a zone, as covered below, you have various special features and abilities that you can, and should, take advantage of:</p>
-
-<ul>
- <li>A colored header area with a color that uniquely identifies your zone.</li>
- <li>A "hero image" representing the zone in the header area.</li>
- <li>A zone landing page, at the base of the zone's navigation hierarchy, which presents a larger than usual banner area with the hero image in a large size and space for a short blurb describing the zone.</li>
- <li>A special navigation sidebar; zones may include content from anywhere on MDN in this navigation, even if they're not actually contained within the zone's direct hierarchy.</li>
- <li>Subpages of the zone's landing page — that is, pages actually physically located beneath the landing page — inherit the zone's color and hero image, with a smaller banner area at the top of the page.</li>
-</ul>
-
-<p>There are basically two types of zone: the <strong>in-wiki zone</strong>, and the <strong>mini-site zone</strong>.</p>
-
-<h3 id="Wiki_内のゾーン">Wiki 内のゾーン</h3>
-
-<p>An <strong>in-wiki zone</strong> is a zone which takes advantage of zone functionality while remaining part of the main flow of MDN's documentation content.  These are sort of semi-zones, in that they generally don't include content from outside their own hierarchy.</p>
-
-<p>An in-wiki zone allows a segment of MDN to add the additional visuals and, probably more importantly, the zone navigation sidebar, without removing the user from the main flow of MDN content.</p>
-
-<div class="note">
-<p><strong>Note:</strong> In-wiki zones do not typically appear in the "Zones" list on the MDN home page, since they're treated as part of the main body of MDN's documentation content.</p>
-</div>
-
-<h3 id="ミニサイト_ゾーン">ミニサイト ゾーン</h3>
-
-<p>A <strong>mini-site zone</strong> is a zone which, while edited and managed using the same interface as any wiki page on MDN, is presented outside the main flow of documentation content. In all functional respects, it supports all the standard wiki functionality provided by the <a href="/en-US/docs/MDN/Kuma">Kuma</a> platform on which MDN is built. A good example is the <a href="/en-US/Apps">App Center</a>.</p>
-
-<p>When a mini-site zone is created, it is given a new URL outside the "/docs/" tree on MDN, typically at the URL <code>https://developer.mozilla.org/<em>&lt;locale&gt;</em>/zone/<em>&lt;your_zone_name&gt;</em></code>.</p>
-
-<div class="note">
-<p><strong>Note:</strong> In general, only very high-profile, special-purpose content should be moved out of the wiki hierarchy; these zones are intended primarily for setting up special-purpose promotional and/or program-related content.</p>
-</div>
-
-<h2 id="何をゾーンにするべきか">何をゾーンにするべきか?</h2>
-
-<p>This is an interesting question, and to be honest, the answer is likely to change over time. Zones are a new concept for MDN, and we're still learning exactly how we'll use them.</p>
-
-<p>There are basically two reasons to create a zone:</p>
-
-<ol>
- <li>You need to set up a <strong>mini-site</strong> for a promotional campaign or a specific product.</li>
- <li>You want to create a one-stop shop, so to speak, for a topic that spans multiple technology areas.</li>
-</ol>
-
-<h2 id="ゾーンを作成する">ゾーンを作成する</h2>
-
-<p>The first step is to create the content. At a minimum, you need to create the initial landing page that will become the root page for your zone. Once you have at least the root page, and possibly even your sub-content, you can then have the pages turned into a zone.</p>
-
-<p>In order to turn a section of MDN into a zone requires MDN administrator privileges, so you'll need to ask an MDN administrator to do it for you. There are a few things you'll need to provide to the admin as part of your request:</p>
-
-<ul>
- <li>What page on MDN should be turned into the root page for the new zone. Keep in mind that all pages below it in the site's hierarchy will become part of the zone.</li>
- <li>Is your zone an {{anch("In-wiki zones", "in-wiki zone")}} or a {{anch("Mini-site zones", "mini-site zone")}}?</li>
- <li>You'll need to provide style information and artwork for the customization of the header area in the new zone. See {{anch("Customizing the appearance")}} for details.</li>
-</ul>
-
-<div class="note">
-<p><strong>Note:</strong> Because zones are a special-purpose construct, you will likely be asked to justify why the content should be a zone at all. Refer to {{anch("What should be a zone.3F", "What should be a zone?")}} for insight.</p>
-</div>
-
-<h2 id="ゾーンのアクセスポリシーを変更する">ゾーンのアクセスポリシーを変更する</h2>
-
-<p>At this time, there's no functional support for access control for zones. This functionality is coming in the future. If you need access control for your zone, please let us know, so we can adjust the priority of that work.</p>
-
-<h2 id="表示をカスタマイズする">表示をカスタマイズする</h2>
-
-<p>Part of what makes a zone a zone is the ability to customize its visual identity. Minimally, this means a special color and image used as the background in the header area of the zone's pages to help the user know that they're in a specific zone. It's also possible to make other basic adjustments to the appearance of the page, as long as the overall feeling of being on MDN is retained.</p>
-
-<div class="note">
-<p><strong>Note:</strong> It's important to keep in mind that the instructions below are <strong>suggestions</strong>. You can try to tinker further with the CSS for your zone. Just keep in mind that your changes may be reviewed by our UX and/or design teams, and will be expected to blend in well with the rest of MDN.</p>
-</div>
-
-<h3 id="基本的なカスタマイズ">基本的なカスタマイズ</h3>
-
-<p>The basic, required customizations for each zone are the background color and image for the header area of the pages in the zone. When requesting that a zone be created, you'll be asked to provide these. Here are basic guidelines to what you need to provide.</p>
-
-<ul>
- <li>The background color should be reasonably distinctive from other zones' backgrounds, while being relevant to the topic area covered by the zone. You should specify this to the MDN administrator setting up your zone as a {{cssxref("&lt;color&gt;")}}.</li>
- <li>The background image is, by default, presented near the right side of the header area (or the left side in a right-to-left locale). This image may be in any Web-compatible format, although PNG is generally best. It should either blend into your specified background color or (preferably) have a transparent background. As a general rule, the background image should be about 468 pixels wide and 400 pixels tall, although the CSS on the page can be set to use {{cssxref("overflow")}} to crop it if necessary. That said, making the image too large increases page size, so that should be avoided.</li>
- <li>The image may be sent to the MDN admin with your zone creation request, or may be one that's already been uploaded to MDN as an attachment to an appropriate page.</li>
-</ul>
-
-<p>With this information, the MDN admin team can set up the basic CSS for your zone for you. If you'd like, however, you can go a step farther and provide the CSS yourself. By following the guidelines in {{anch("Additional customizations")}}, you can experiment with other changes to the appearance of your zone.</p>
-
-<h3 id="さらなるカスタマイズ">さらなるカスタマイズ</h3>
-
-<p>If you'd like to investigate additional customization options, take a look at the CSS/stylus template located <a href="https://github.com/mozilla/kuma/blob/master/media/redesign/stylus/zones.styl">in github</a>. This lists all the Stylus CSS for the styles you're allowed to alter using your zone's custom CSS.</p>
-
-<p>If you wish to perform additional customizations, you may do so, with one major caveat: your customizations must not be so drastic that they make the pages in the zone no longer "feel" like part of MDN.</p>
-
-<p>When customizing the zone's stylesheet, it's your job to sort out from the template which styles you want to alter and to put together the CSS to do so. Once you've done so, provide that CSS to the MDN admin team, and they'll install it for you.</p>
-
-<p>All zone-related content has the class <code>zone</code> on it.</p>
-
-<div class="note">
-<p><strong>Note:</strong> Please note that because the site is actively undergoing development, anything about specific classes and styles discussed here is subject to change without notice.</p>
-</div>
-
-<h4 id="背景色">背景色</h4>
-
-<p>As mentioned previously, the first thing you're likely to customize is the background color for your zone's header area. The CSS looks something like this:</p>
-
-<pre class="brush: css notranslate">.zone #main-header, .zone .zone-article-header, .zone .zone-landing-header {
-    background-color: <strong><em>zone-color</em></strong>;
-}
-</pre>
-
-<p>The ID <code>main-header</code> refers to the site navigation area at the very top of the page. This includes the "Mozilla" cross-site navigation tab, search box, and other global navigation functionality.</p>
-
-<p>The class <code>zone-article-header</code> represents the appearance of the header area on article pages within the zone. That is, all pages other than the base landing page within the zone will have this class on their heading area.</p>
-
-<p>The class <code>zone-landing-header</code> is used for the header area on the zone's landing page. This is the taller heading area on the landing page, with the larger image in it.</p>
-
-<p>As a general rule, you want all of these areas to have the same color; indeed, the article and landing page header colors should be the same. The only reason you might configure them differently is if they were gradients and you wanted to adjust them to have the same overall "average" color despite the different height of the space.</p>
-
-<p><strong>In short:</strong> Replace <strong><em>zone-color</em></strong> in the CSS snippet above with the {{cssxref("&lt;color&gt;")}} you've selected for your zone color.</p>
-
-<h4 id="ランディングページのヘッダ画像">ランディングページのヘッダ画像</h4>
-
-<p>You will also want to change the image that represents your zone on the zone's landing page. This page has a larger header box to accomodate a larger image to represent your zone. The CSS looks like this:</p>
-
-<pre class="brush: css notranslate">.zone .zone-landing-header .zone-image {
-    background-image: url(<strong><em>zone-image-url</em></strong>);
-}
-</pre>
-
-<p>The <code>zone-image</code> class is used to specify and style the image for your zone's landing page header. This image should be no wider than 468 pixels, although you can override this by using additional CSS here. Simply replace <em><strong>zone-image-url</strong></em> with the URL of the image to use.</p>
-
-<div class="note">
-<p><strong>Note:</strong> The easiest way to provide the image is to simply attach it to an appropriate page on MDN and use the resulting URL.</p>
-</div>
-
-<h4 id="記事ページのヘッダ画像">記事ページのヘッダ画像</h4>
-
-<p>Additionally, you should set the image that represents your zone on its subpages. By default, this image is constrained to 200 pixels wide by 400 pixels tall, but, again, that can be overridden.</p>
-
-<pre class="brush: css notranslate">.zone .zone-article-header .zone-image {
-    background-image: url(<strong><em>zone-image-url</em></strong>);
-}
-</pre>
-
-<p>Just replace <em><strong>zone-image-url</strong></em> with the URL of the image to use.</p>
-
-<div class="note">
-<p><strong>Note:</strong> The easiest way to provide the image is to simply attach it to an appropriate page on MDN and use the resulting URL. You can choose to use the same image as you do for the landing page header image, with some scaling or cropping applied, or you can use a different image.</p>
-</div>
-
-<h4 id="ヘッダボタンの下の境界">ヘッダボタンの下の境界</h4>
-
-<p>The last thing you're generally advised to change is the appearance of the bottom border of the buttons in the zone header area. This is the CSS:</p>
-
-<pre class="brush: css notranslate">.zone .zone-landing-header a.button {
-    box-shadow: inset 0 -1px <strong><em>color</em></strong>;
-}
-</pre>
-
-<p>Here, replace <strong><em>color</em></strong> with a {{cssxref("&lt;color&gt;")}} that is very similar to your background color, but slightly darker.</p>
-
-<h2 id="ゾーンナビゲーション">ゾーンナビゲーション</h2>
-
-<h3 id="ゾーンナビゲーションサイドバー">ゾーンナビゲーションサイドバー</h3>
-
-<p>The sidebar appearing on every page in a zone is defined in the zone's landing page content, in a section called "Subnav" (visible only when editing the page). This section may contain a manually curated list of pages or use a macro, such as {{TemplateLink("ListSubpages")}}. In the latter case you will need to <a href="/en-US/docs/MDN/Kuma/Introduction_to_KumaScript#Caching">force-reload</a> (shift+refresh) the zone's landing page in order to update the sidebar.</p>
-
-<h3 id="クイックリンク">クイックリンク</h3>
-
-<p>As is the case with any page on MDN, pages within zones may use the <a href="/en-US/docs/MDN/Contribute/Content/Quicklinks">quicklinks</a> feature. Quicklinks are a navigation box, presented in the left sidebar area, offering links the user may follow to related material. These links may be within MDN or off-site, and may be nested up to two total levels deep, using folders.</p>
-
-<p>To aid in generating common types of quicklinks for zones, we have some macros you can use.</p>
-
-<h4 id="QuickLinksWithSubpages">QuickLinksWithSubpages</h4>
-
-<p>The {{TemplateLink("QuickLinksWithSubpages")}} macro generates all of the HTML required to present a quicklinks box on the page with the links corresponding to the pages in a specified hierarchy. You can also use it with no parameters at all to present quicklinks of subpages of the current page, although this is not commonly as useful in a zone since the zone navigation will generally present this for you.</p>
-
-<h2 id="ゾーンのスタイルガイド">ゾーンのスタイルガイド</h2>
-
-<h2 id="注記">注記</h2>
-
-<p>This section offers some notes that are worth keeping in mind when creating, working with, and using zones.</p>
-
-<ul>
- <li>Every page in a zone automatically inherits the navigation sidebar provided on their zone's root page.</li>
- <li>If a page in a zone has a quicklinks section, the quicklinks are displayed below the zone's navigation in the sidebar. Toggling off the quicklinks makes both the quicklinks and the navigation bar disappear, allowing more room for the page content.</li>
-</ul>
diff --git a/files/ja/mdn/user_guide/writing/index.html b/files/ja/mdn/user_guide/writing/index.html
deleted file mode 100644
index 7fa04b601b..0000000000
--- a/files/ja/mdn/user_guide/writing/index.html
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: コンテンツの作成
-slug: MDN/User_guide/Writing
-tags:
-  - MDN
-  - MDN Project
-translation_of: Archive/Meta_docs/Writing_content
----
-<p>MDN には、いつもたくさんのページの追加やアップデートがあります。たとえば、真新しいAPI のドキュメントや若干の変更がある古いAPIのページがあり、あなたの翻訳はいつでも役立ちます。</p>
-
-<h2 id="既存のページを編集する">既存のページを編集する</h2>
-
-<p>訂正したいページを見つけたら、右上の「編集」ボタンをクリックしてください。すると、該当ページが編集可能になったWYSIWYGエディタが開きます。どのように編集するかは、<a href="/docs/Project:MDN/Contributing/Editor_guide">MDN のエディタガイド</a>を読んでください。コンテンツの構築とレイアウトを自動的に手助けするマクロシステムなどの説明もあります。</p>
-
-<p>次のような場合に、既存ページの編集が必要です。</p>
-
-<ul>
- <li>誤字脱字</li>
- <li>わかりにくい表現</li>
- <li>レイアウトや形式が乱雑</li>
- <li>API ドキュメントの更新と、API のアップデートに合わせた更新</li>
- <li>複数のブラウザの異なる振る舞いに関する情報</li>
- <li>サンプルコードの追加と改善. 詳細は、{{anch("Add a code sample")}} を参照</li>
- <li>仮ページ、または重要な情報の不足</li>
-</ul>
-
-<h2 id="新しいページを作成する">新しいページを作成する</h2>
-
-<p>これは大きな出来事です！MDN に新しいページを追加すると、Webがあなたを愛しあなたを抱きしめてくれるでしょう。まだドキュメント化されていない API や新しい話題のチュートリアル・解説記事というように、新しいページの作成は、とても役に立ちます。</p>
-
-<p>MDN には、次のように新しいページの作成を始める方法があります。<a href="/docs/Project:MDN/Contributing/Getting_started#Logging_into_MDN">ログイン</a>してから始めてください:</p>
-
-<dl>
- <dt>存在しないページのリンクをクリック</dt>
- <dd>MDN をブラウズしていると、存在しないページへのリンクが見つかることがあるでしょう。リンク先のページを作らずに、記事を書くことがあるからです。これは、最終的にページ構成がどうなるか理解する手助けになるのですが、そこに取りかかるまでに、時間がかかる場合もあります。そんなところを見つけたら、自由に作業してみてください。リンクをクリックして、新規ページを編集すればいいのです。</dd>
- <dt>サブページの作成</dt>
- <dd>右上あたりの歯車マークから、<strong>"サブページを作成"</strong> を呼び出すことができます。この項目を選ぶと、そのとき表示していたページを親にした、新しいページの編集画面が開きます。タイトルとスラッグを設定したら、記事を書き始めましょう。</dd>
- <dt>このページを複製</dt>
- <dd>歯車マークの<strong>"このページを複製"</strong> オプションで、現在のページのコピーを作ることができます。この項目を選ぶと、そのとき表示していたページを複写した、新しいページの編集画面が開くので、タイトルとスラッグを設定しましょう。新しいページを作る場合、これはわりといい方法です。なぜなら、元と同じようなレイアウトで簡単にページを作れるからです。</dd>
- <dt>存在しないページへのリンクを作成してクリック</dt>
- <dd>これは、いくつかの方法の組み合わせです。どのページもどこからかリンクされている必要があるので、現在存在しているページから、新しいページにリンクを貼ってしまうのです。それから、元のページをいったん保存して、今挿入したリンクをクリックすれば、新しい記事の編集画面が開きます。</dd>
-</dl>
-
-<div class="note">
-<p><strong>注記:</strong> ログインしていない場合、新しいページを編集するかわりに、404エラーが出るかもしれません。</p>
-</div>
-
-<h2 id="関連情報">関連情報</h2>
-
-<p>ここでは、コンテンツ作成を始めるためのいくつかのヒントや確実に役立つ注意すべき情報を紹介しています。</p>
-
-<dl>
- <dt><a href="https://wiki.mozilla.org/Modules">モジュールオーナー一覧 (Module owner lists)</a></dt>
- <dd>Mozilla プロジェクトは、モジュールオーナーベースで活動しており、主要なコンポーネントは、オーナーまたは責任者がいます。このオーナーたちは、あなたが何かするときの最適な情報源です。あるいは、誰と話をすればいいか見つける一番の方法です。</dd>
- <dt><a href="http://mxr.mozilla.org/">Mozilla ソースのクロスリファレンス (Mozilla source cross-reference)</a></dt>
- <dd>MXR (Mozilla クロスリファレンス、Mozilla cross-reference) は、Mozilla プロジェクトのすべてのソースコードにアクセスできる場所です (一部の例外を除きます。例えば、Firefox OS のソースコードは GitHub 上にあります)。コードとそこに書かれたコメントは、とても役に立つ情報源です。</dd>
- <dt><a href="http://wiki.mozilla.org/">Mozilla wiki</a></dt>
- <dd>The Mozilla wiki — "wikimo" とも呼ばれます — は、プロセスやデザインノート・ドラフト・計画・暫定の仕様などが保存されています。雑然と混乱していますが、多くの場合、貴重な情報の宝庫になっています。</dd>
-</dl>