initial commit

1 files changed, 56 insertions, 0 deletions

diff --git a/files/ja/mdn/structures/banners_and_notices/index.html b/files/ja/mdn/structures/banners_and_notices/index.html
new file mode 100644
index 0000000000..54cce6a78f
--- /dev/null
+++ b/files/ja/mdn/structures/banners_and_notices/index.html
@@ -0,0 +1,56 @@
+---
+title: バナーと通知
+slug: MDN/Structures/Banners_and_notices
+tags:
+  - MDN Meta
+  - ガイド
+  - 構造
+translation_of: MDN/Structures/Banners_and_notices
+---
+<div>{{MDNSidebar}}</div>
+
+<div>{{IncludeSubnav("/ja/docs/MDN")}}</div>
+
+<p><span class="seoSummary">場合によっては、記事に特別な通知が必要になることがあります。これは、プロダクションコードで使用すべきではない古い技術やその他の資料がページに含まれている場合に発生する可能性があります。この記事では最も一般的なケースについて説明します。</span></p>
+
+<h2 id="How_to_add_notice_boxes">How to add notice boxes</h2>
+
+<p>In most cases, you apply these notices by adding a macro call to inject an appropriate banner into the page content, and by adding a tag to the page's list of tags. Also, if the page includes a compatibility table (most API reference pages do, for example), you should update that table to reflect any compatibility changes.</p>
+
+<p>To do this, you open the editor, then insert the macro call at the top of the article, and change the browser <a href="/en-US/docs/Project:Compatibility_tables" title="/en-US/docs/Project:Compatibility_tables">compatibility table</a> (if any); the table should be near the end of the article. Once that's done, scroll to the bottom of the article to find the tag list, and add the new tag to the list. Once you've done that, click the Save Changes button near the top of the window to commit your updates. From then on, an appropriate banner will appear on the page, and any macros that reference page tags when looking for up-to-date articles will know that the page you've updated is obsolete.</p>
+
+<ul>
+ <li>To learn more about editing, see the <a href="/en-US/docs/Project:MDN/Contributing/Editor_guide" title="/en-US/docs/Project:MDN/Contributing/Editor_guide">MDN editor guide</a>.</li>
+ <li>For more information about tagging, see our <a href="/en-US/docs/Project:MDN/Contributing/Tagging_standards" title="/en-US/docs/Project:MDN/Contributing/Tagging_standards">Tagging standards</a> guide.</li>
+ <li>To discover more of our custom macros, see the article <a href="/en-US/docs/Project:MDN/Contributing/Custom_macros" title="/en-US/docs/Project:MDN/Contributing/Custom_macros">Custom macros for MDN</a>.</li>
+</ul>
+
+<p>Sometimes, you might want to flag just a single item in a list of items, or in a table, as obsolete, deprecated, or the like. There are special versions of each of the following macros for that; simply change "_header" to "_inline" to the end of the macro's name.</p>
+
+<h2 id="Obsolete_content">Obsolete content</h2>
+
+<p>If you come across an article whose content is obsolete -- meaning that everything on that page is out of date and shouldn't be used -- you can mark the page as such by adding the {{TemplateLink("obsolete_header")}} macro at the top of the article. Just open the page's editor and insert this at the top of the article:</p>
+
+<pre class="notranslate">\{{obsolete_header}}</pre>
+
+<p>You should also add the tag "Obsolete" to the tag list at the bottom of the page.</p>
+
+<div class="note">
+<p><strong>Note:</strong> If the article covers a Mozilla-specific technology, you can add the Gecko version in which the technology was removed from Gecko as a parameter to the {{TemplateLink("obsolete_header")}} macro, like this:</p>
+
+<pre class="notranslate">\{{obsolete_header(21)}}</pre>
+
+<p>This will make the banner specificy that the technology became obsolete in Gecko 21, with a link to the article <a href="/en-US/docs/Mozilla/Firefox/Releases/21" title="/en-US/docs/Mozilla/Firefox/Releases/21">Firefox 21 for developers</a>.</p>
+</div>
+
+<p>Eventually, once something is very, very obsolete (that is, it's so obsolete that reading the material might actually cause serious problems), we can move content into our <a href="/en-US/docs/Archive">Archive</a> section. If you see material that you think should be archived, <a href="mailto:mdn-admins@mozilla.org?subject=Archival%20of%20content&amp;body=%3C%3CPlease%20list%20the%20page%20to%20archive%20and%20why%20you%20think%20it%20should%20be%20archived%20here%3E%3E">contact an MDN administrator</a>.</p>
+
+<h2 id="Deprecated_content">Deprecated content</h2>
+
+<p>Deprecated content is content that covers a technology or idea that is in the process of becoming obsolete. It's no longer recommended, and is expected to be removed from browsers in the relatively near future. You can mark pages as deprecated using the {{TemplateLink("deprecated_header")}} macro. Just like with obsolete content, you can specify the Gecko version in which the technology was deprecated as a parameter, if the technology is Gecko-specific.</p>
+
+<p>You should also add the tag "Deprecated" to the page.</p>
+
+<h2 id="Non-standard_content">Non-standard content</h2>
+
+<p>Non-standard content is any content not yet part of a Web standard; this includes any technology that isn't even proposed as a draft specification, even if it's implemented by multiple browsers. You should use the {{TemplateLink("non-standard_header")}} macro on these pages, and tag the pages with "Non-standard".</p>