diff options
Diffstat (limited to 'files/ja/mdn/structures/banners_and_notices/index.html')
| -rw-r--r-- | files/ja/mdn/structures/banners_and_notices/index.html | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/files/ja/mdn/structures/banners_and_notices/index.html b/files/ja/mdn/structures/banners_and_notices/index.html index 54cce6a78f..e43794c9cd 100644 --- a/files/ja/mdn/structures/banners_and_notices/index.html +++ b/files/ja/mdn/structures/banners_and_notices/index.html @@ -17,12 +17,12 @@ translation_of: MDN/Structures/Banners_and_notices <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> +<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="/ja/docs/Project:Compatibility_tables" title="/ja/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> + <li>To learn more about editing, see the <a href="/ja/docs/Project:MDN/Contributing/Editor_guide" title="/ja/docs/Project:MDN/Contributing/Editor_guide">MDN editor guide</a>.</li> + <li>For more information about tagging, see our <a href="/ja/docs/Project:MDN/Contributing/Tagging_standards" title="/ja/docs/Project:MDN/Contributing/Tagging_standards">Tagging standards</a> guide.</li> + <li>To discover more of our custom macros, see the article <a href="/ja/docs/Project:MDN/Contributing/Custom_macros" title="/ja/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> @@ -40,10 +40,10 @@ translation_of: MDN/Structures/Banners_and_notices <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> +<p>This will make the banner specificy that the technology became obsolete in Gecko 21, with a link to the article <a href="/ja/docs/Mozilla/Firefox/Releases/21" title="/ja/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&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> +<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="/ja/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&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> |