diff options
Diffstat (limited to 'files/vi/mdn/contribute')
| -rw-r--r-- | files/vi/mdn/contribute/feedback/index.html | 62 | ||||
| -rw-r--r-- | files/vi/mdn/contribute/howto/create_and_edit_pages/index.html | 179 | ||||
| -rw-r--r-- | files/vi/mdn/contribute/howto/index.html | 15 | ||||
| -rw-r--r-- | files/vi/mdn/contribute/howto/tag/index.html | 376 | ||||
| -rw-r--r-- | files/vi/mdn/contribute/index.html | 77 |
5 files changed, 0 insertions, 709 deletions
diff --git a/files/vi/mdn/contribute/feedback/index.html b/files/vi/mdn/contribute/feedback/index.html deleted file mode 100644 index 688130e9c2..0000000000 --- a/files/vi/mdn/contribute/feedback/index.html +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Gửi phản hồi về MDN -slug: MDN/Contribute/Feedback -translation_of: MDN/Contribute/Feedback ---- -<div>{{MDNSidebar}}</div> - -<div>{{IncludeSubnav ("/en-US/docs/MDN")}}</div> - -<p>Chào mừng bạn đến với MDN! <span class="seoSummary">Nếu bạn có gợi ý, hoặc đang gặp vấn đề sử dụng MDN, đây là nơi thích hợp để được. Thực tế rằng bạn đang quan tâm trong việc cung cấp thông tin phản hồi làm cho bạn nhiều hơn một phần của cộng đồng Mozilla, và chúng tôi cảm ơn trước sự quan tâm của bạn.</span></p> - -<p><span class="seoSummary">Bạn có nhiều lựa chọn để cung cấp góc nhìn sâu sắc của bạn; bài viết này sẽ giúp bạn làm như vậy.</span></p> - -<h2 id="Cập_nhật_các_tài_liệu_hướng_dẫn">Cập nhật các tài liệu hướng dẫn</h2> - -<p>Trước hết, nếu bạn đã nhìn thấy một vấn đề với các tài liệu, bạn nên luôn luôn cảm thấy miễn phí để sửa chữa nó cho mình.</p> - -<ol> - <li><a href="/en-US/docs/MDN/Contribute/Howto/Create_an_MDN_account">Đăng nhập</a> bằng <a href="https://github.com/">Github</a>.</li> - <li>Nhấp vào nút<a href="https://github.com/"> </a><strong>Chỉnh sửa</strong> màu xanh để mở <a href="/en-US/docs/MDN/Contribute/Editor">trình biên tập</a>.</li> - <li>Nhấn vào nút <strong>Xuất bản</strong> sau khi hoàn thiện chỉnh sửa.</li> -</ol> - -<p>Các tài liệu ở đây như là ở trong một trang wiki, và được giám tuyển bởi một nhóm các tình nguyện viên và nhân viên được trả tiền, do đó, đừng ngần ngại - ngữ pháp của bạn không phải là hoàn hảo. Chúng tôi sẽ làm sạch nó nếu bạn phạm phải một sai lầm; không gây hại chút nào!</p> - -<p>Để biết thêm thông tin về đóng góp cho tài liệu MDN, xem:</p> - -<ul> - <li><a href="/en-US/docs/Project:Getting_started">Bắt đầu</a></li> - <li><a href="/en-US/docs/MDN/Contribute">Đóng góp cho MDN</a></li> - <li><a href="/en-US/docs/MDN/Contribute/Editor">Giao diện chỉnh sửa MDN</a></li> -</ul> - -<h2 id="Tham_gia_vào_cuộc_trò_chuyện">Tham gia vào cuộc trò chuyện</h2> - -<p>Nói với chúng tôi! Có một vài cách để liên lạc với những người khác, những người làm việc về nội dung MDN.</p> - -<h3 id="Đồng_bộ_hoá_Chat">(Đồng bộ hoá) Chat</h3> - -<p> - </p><h3 id="Bất_đồng_bộ_Thảo_luận"><span class="short_text" id="result_box" lang="vi"><span>(Bất đồng bộ) Thảo luận</span></span></h3> - - -<p><span id="result_box" lang="vi"><span>Các cuộc thảo luận dài hạn diễn ra trên <a href="https://discourse.mozilla-community.org/c/mdn">diễn đàn thảo luận MDN</a> của chúng tôi.</span> <span>Bạn có thể đăng lên diễn đàn qua email tới <a href="mailto://mdn@mozilla-community.org">mdn@mozilla-community.org</a>.</span> <span>Nếu bạn tham gia diễn đàn, bạn cũng có thể chọn để có thông báo về các cuộc thảo luận gửi tới bạn qua email.</span></span></p> - -<h2 id="Báo_cáo_một_vấn_đề">Báo cáo một vấn đề</h2> - -<h3 id="Vấn_đề_tài_liệu">Vấn đề tài liệu</h3> - -<p>Nếu bạn nhìn thấy một vấn đề trong các tài liệu hướng dẫn và không thể sửa chữa nó do có bất cứ lý do nào, bạn có thể <a href="https://github.com/mdn/sprints/issues/new?template=issue-template.md&projects=mdn/sprints/2&labels=user-report">báo cáo vấn đề</a>! Bạn có thể sử dụng mẫu này cho bất kỳ vấn đề liên quan đến tài liệu nào, chẳng hạn:</p> - -<ul> - <li>một sự điều chỉnh đơn giản</li> - <li>một yêu cầu cho một mảng nội dung hoàn toàn mới</li> - <li>báo cáo nội dung không phù hợp (bao gồm cả spam và dịch thuật sai chỗ)</li> -</ul> - -<p>Như đã đề cập trước đó, chúng tôi mời các bạn đóng góp những thay đổi của chính mình, nhưng tùy chọn này cũng có sẵn cho bạn luôn.</p> - -<h3 id="Vấn_đề_trang_web">Vấn đề trang web</h3> - -<p>Nếu bạn gặp vấn đề với các trang web MDN, hay có những ý tưởng cho các tính năng mới cho trang web, bạn có thể <a href="https://bugzilla.mozilla.org/form.mdn">gửi một phiếu cho nhóm phát triển MDN</a>.</p> diff --git a/files/vi/mdn/contribute/howto/create_and_edit_pages/index.html b/files/vi/mdn/contribute/howto/create_and_edit_pages/index.html deleted file mode 100644 index b0dc76e311..0000000000 --- a/files/vi/mdn/contribute/howto/create_and_edit_pages/index.html +++ /dev/null @@ -1,179 +0,0 @@ ---- -title: Cách tạo và chỉnh sửa trang -slug: MDN/Contribute/Howto/Create_and_edit_pages -translation_of: MDN/Contribute/Howto/Create_and_edit_pages ---- -<div>{{MDNSidebar}}</div> - -<p><span class="seoSummary">Bài viết này giới thiệu những người đóng góp mới vào quá trình chỉnh sửa các trang hiện có và tạo những trang mới.</span></p> - -<h2 id="Chỉnh_sửa_một_trang_hiện_có">Chỉnh sửa một trang hiện có</h2> - -<p>Để chỉnh sửa một trang:</p> - -<ol> - <li>Nếu bạn đang sử dụng phiên bản read-only của MDN Web Docs (https://developer.mozilla.org), click <strong>Edit in wiki</strong> trong tiêu đề bài viết. Điều này đưa bạn đến phần có thể chỉnh sửa, phiên bản wiki của trang (https://wiki.developer.mozilla.org), nhưng không thực sự mở giao diện chỉnh sửa.</li> - <li>Bấm vào nút <strong>Chỉnh sửa</strong> trong tiêu đề bài viết của trang wiki.</li> - <li>The page then reloads, with an editing interface where you can add or delete information directly.</li> - <li>Add paragraphs, delete text, insert headings, and perform more of the basic functions involved in writing and editing.</li> -</ol> - -<p>See the guide to <a href="/en-US/docs/MDN/Contribute/Editor/Basics">Editor UI elements</a> in the <a href="/en-US/docs/MDN/Contribute/Editor">MDN Editor guide</a> for more information on using <strong>MDN</strong>'s built-in editor.</p> - -<h3 id="Preview_changes">Preview changes</h3> - -<p>To see what your changes look like:</p> - -<ul> - <li>Click the <strong>Preview</strong> button, within the editing function at the top or bottom of the page.</li> - <li>This opens the preview page, showing your revisions in a new window, or tab.</li> - <li>Each time you click this button, it refreshes your preview page with the latest changes.</li> -</ul> - -<p>Be careful! Previewing a page <strong>does not</strong> save your progress. Don't close the editing tab until you've saved your work.</p> - -<h3 id="Revision_comment">Revision comment</h3> - -<p>After previewing your changes, you will want to <em>save your revision</em>. Before you <strong>save</strong>, look for the revision comment box, below the editing box, leaving a comment to inform other contributors why you made changes. For example, you might have added a new section, changed some words to make the terminology more consistent, rewritten a paragraph to clarify the language, or removed information because it was redundant.</p> - -<h3 id="Table_of_Contents">Table of Contents</h3> - -<p>The 'On this Page' section of an article, is an auto-generated list of links to the headings on the page. The wording of these can be edited via the headings. It's also possible to remove a table of contents or decrease its number of links, by selecting 'Edit Page Title and Properties', changing the value of the "TOC" drop down.</p> - -<h3 id="Tags">Tags</h3> - -<p>You can add or remove tags, which describe the page content and purpose, below the editing section. See <a href="/en-US/docs/MDN/Contribute/Tagging">How to properly tag pages</a>, for information on which tags to apply.</p> - -<h3 id="Review_needed">Review needed?</h3> - -<p>If an expert or experienced contributor should review your edits, please request a technical review (for code, API's, or technologies), and/or an editorial review (for prose, grammar, and content), making sure the appropriate box is checked before you save.</p> - -<h3 id="Attach_files">Attach files</h3> - -<p>Attaching files requires a special user privilege. See <a href="/en-US/docs/MDN/Contribute/Editor/Basics/Attachments">Attachments in the MDN editor</a> for details, including how to request the upload privilege.</p> - -<h3 id="Publish_Discard_or_Keep_editing">Publish, Discard, or Keep editing</h3> - -<p>When you finish editing and are happy with your preview, publish your work and comments by clicking the <em>green</em> <strong>Publish</strong> button, to the <strong>right of the page title</strong>, or towards the <strong>bottom of the page</strong>. If you wish to continue working, click <strong>Publish and keep editing</strong>, which publishes your changes and keeps the edit interface open.</p> - -<p>If you change your mind, you can discard edits, by clicking the <em>red</em> <strong>Discard</strong> button. Note that discarding changes <em>permanently</em> discards them.</p> - -<p>Pressing <strong>Enter</strong> in the Revision Comment field is equivalent to clicking <strong>Publish and Keep Editing</strong>.</p> - -<div class="note"> -<p>Note: If attempting to save, but changes are rejected as invalid, and you feel the content is appropriate for MDN, <a href="mailto:mdn-admins@mozilla.com?subject=MDN%3A%20Content%20Rejection%20Appeal&body=%3CDescribe%20the%20content%20you%20were%20trying%20to%20save%20and%20where%20you%20were%20trying%20to%20place%20it.%3E">email the MDN admin team</a> for assistance.</p> -</div> - -<h2 id="Getting_page-creation_permissions">Getting page-creation permissions</h2> - -<p>For security reasons, newly-created accounts don't have the ability to create new pages. If you try to do so, you'll see a page instructing you how to get the page created. There are two options:</p> - -<ul> - <li><strong>Ask for the page to be created for you.</strong> To do this, <a href="https://github.com/mdn/sprints/issues/new?template=issue-template.md&projects=mdn/sprints/2&labels=user-report">file a documentation request issue</a>, with the title "Create page: <page title>". Fill out the URL field of the template with the location on MDN where you'd like the page to go if you know where to place it. In the comment text, include information on why this page needs creating.</li> - <li><strong>Request page creation privileges.</strong> If you request page creation privileges, and they're granted to you, you'll be able to add new pages by following the instructions here. To request these privileges, <a href="mailto:mdn-admins@mozilla.org">email the MDN admin</a> team with your request. Include your username, why you would like to have the ability to create new pages. For instance, you're documenting a new API which involves many new pages, or you'd like to add new terms to the glossary. You should also have made useful contributions to this site's content, and been a contributor for some time. This length of time, and the other factors are collectively considered.</li> -</ul> - -<h2 id="Creating_a_new_page">Creating a new page</h2> - -<p>Once you have page-creation permission, you can begin creating pages.</p> - -<p>If you do not know where to place a new article, <strong>do not worry.</strong> Put it anywhere, we will find it, move to where it belongs, or merge it into existing content. Whatever makes the most sense. Do not worry about making it perfect. We have happy helper gnomes who help to make your content clean and rather luscious.</p> - -<p>There are a few ways to create a new page:</p> - -<ul> - <li><a href="#Missing_page_link">'Missing page' link.</a></li> - <li><a href="#New_page_without_link">New page without a link.</a></li> - <li><a href="#Subpage_of_an_existing_page">A subpage of an existing page.</a></li> - <li><a href="#Clone_of_an_existing_page">Clone of an existing page.</a></li> - <li><a href="#Link_from_an_existing_page">Link from an existing page.</a></li> -</ul> - -<h3 id="Missing_page_link">'Missing page' link</h3> - -<p>As with most wikis, it is possible to create a link to a page that is yet to exist. For example, an author might create a list of all the members of an API, before creating the pages for those members. On MDN, links to non-existent pages are typically displayed in red.</p> - -<p>To create a page from a 'missing page' link:</p> - -<ol> - <li>Log into MDN, and have page-creation permission. If not logged in, clicking a 'missing page' link results in a 404 (page not found) error.</li> - <li>Click the 'missing page' link. If you have page creation permission, the <a href="/en-US/docs/MDN/Contribute/Editor">MDN Editor UI</a> opens, ready for you to create the missing page.</li> - <li>Write the content of the page, and save it.</li> -</ol> - -<h3 id="New_page_without_link">New page without link</h3> - -<p><em>To create a new page without linking from another page</em>, enter a unique page name in the URL field of your browser. For example, if you enter:</p> - -<pre class="language-html notranslate">https://wiki.developer.mozilla.org/en-US/docs/FooBar</pre> - -<p>MDN Creates a new page, with the title "FooBar", opening the editor for you to add new content. Refer to the <a href="#Editing_an_existing_page">Editing an existing page</a> section of this article, for information on how to use the editor mode.</p> - -<p><em>To create a new page without linking from another page</em>:</p> - -<ol> - <li>Log in, and have page-creation permission.</li> - <li>Enter the following in the URL field of your browser:</li> -</ol> - -<pre class="language-html notranslate">https://wiki.developer.mozilla.org/en-US/docs/new</pre> - -<p>MDN Creates a new page, with a place for a title, opening the editor to add new content to this page. Refer to <a href="#Editing_an_existing_page">Editing an existing page</a>, for information on using editor mode.</p> - -<h3 id="Subpage_of_an_existing_page">Subpage of an existing page</h3> - -<p>To create a page you want to be below an existing page, in the page hierarchy:</p> - -<ol> - <li>If needed, navigate to the wiki site by clicking <strong>Edit in wiki</strong> in the article header.</li> - <li>On the 'parent' page, click the <strong>Advanced</strong> menu (the gear icon in the toolbar), then click <strong>New sub-page</strong>.</li> - <li>An editor view opens for creating a new document.</li> - <li>Add a title for this document, in the <strong>Title</strong> field.</li> - <li>Change the <strong>Slug</strong> field, if needed. For example, if the title is long, and a shorter URL seems appropriate. This field is automatically filled by the editor, substituting underscores for spaces found in the title, changing only the last part of the URL.</li> - <li>In the <strong>TOC</strong> field, select heading levels you want to be displayed in the table of contents for the page. Or select 'No table of contents', if one is not needed.</li> - <li>Write content of the page in the editor pane, saving your changes. Refer to <a href="#Editing_an_existing_page">Editing an existing page</a>, for further information on using editor mode.</li> -</ol> - -<h3 id="Clone_of_an_existing_page">Clone of an existing page</h3> - -<p>If there is an existing page, whose format you wish to use as a base for your new page, you can 'clone' that page, and then change its content.</p> - -<ol> - <li>If needed, navigate to the wiki site by clicking <strong>Edit in wiki</strong> in the article header.</li> - <li>On the original page, click the <strong>Advanced</strong> menu (the gear icon in the toolbar), and click <strong>Clone this page</strong>. An editor view opens, for creating a new document.</li> - <li>Change the <strong>Title</strong> of the page, as appropriate for the new content. The <strong>Slug</strong> field is updated automatically as you change the <strong>Title</strong> field.</li> - <li>Change the path portion of the <strong>Slug</strong> field, as needed, to put the new document in a different location in the document hierarchy. In most cases, this is not needed. A cloned page often has similar content to its original, and need to be in a similar location.</li> - <li>In the <strong>TOC</strong> field, select the heading levels you want to be automatically displayed in the table of contents for this page. Or select 'No table of contents', if one is not needed.</li> - <li>Write your content in the editor pane, saving your changes. Refer to <a href="#Editing_an_existing_page">Editing an existing page</a>, for more information on using editor mode.</li> -</ol> - -<h3 id="Link_from_an_existing_page">Link from an existing page</h3> - -<p>This is a bit of a hybrid. You can create a link on another page, then click the link you just inserted, to create the new page:</p> - -<ol> - <li>Enter the name of your new page, anywhere that makes sense in the text of an existing page.</li> - <li>Highlight this new name, and <strong>click the Link icon (<img alt="" src="https://developer.mozilla.org/files/3810/link-icon.png" style="height: 28px; width: 29px;">) </strong>in the editor's toolbar. The <strong>'Update Link'</strong> dialog opens, with the highlighted text in the <strong>'Link To'</strong> field.</li> - <li><strong>"/en-US/docs/"</strong> is inserted by default, to the beginning of the URL field.<em> Enter the name </em>of the page after "/en-US/docs/". The page name does not have to be the same as the link text.</li> - <li>Click <strong>OK</strong>, to create and insert the link.</li> -</ol> - -<p>If the page does not yet exist, the link is displayed in red. If the page <em>does</em> exist, the link is displayed blue. If you want to create a new page, but the page title you desire is already taken, check if it makes sense helping edit and improve the page already there. Otherwise, think of a unique title for your new page, and create a link for it. Refer to <a href="https://developer.mozilla.org/Project:en/Page_Naming_Guide" title="Project:en/Page_Naming_Guide">page naming guide</a> for guidelines.</p> - -<p>To add content to your new page, click on the red link you just created, after saving and closing the editor. The new page opens in editor mode, enabling you to start writing. Refer to <a href="#Editing_an_existing_page">Editing an existing page</a>, for further information on using editor mode.</p> - -<h2 id="Refreshing_page_content">Refreshing page content</h2> - -<p>MDN support of KumaScript macros, and integration of content from other pages can sometimes be hampered by the need for caching of pages, for performance reasons. Pages are built from their source, and this output is cached for future requests. From that moment on, any macros (templates), or integrations (using the macro<span class="templateLink"><code><a href="https://developer.mozilla.org/en-US/docs/Template:Page">Page</a></code></span>), will not reflect later changes made to the macro, its output, or the contents of the integrated material.</p> - -<ul> - <li>To manually update a page, force-refresh your Web browser. MDN detects this, triggering a page rebuild, pulling in updated macro output, and integrating page content.</li> - <li>You can also configure pages to periodically rebuild, automatically. This should not be done unless you expect the page to update frequently. See <a href="/en-US/docs/MDN/Contribute/Tools/Page_regeneration">Page regeneration</a>, for detailed information.</li> -</ul> - -<h2 id="See_also">See also</h2> - -<ul> - <li><a href="/en-US/docs/MDN/Contribute/Editor">MDN editor guide</a></li> - <li><a href="/en-US/docs/MDN/Contribute/Content/Style_guide">MDN style guide</a></li> -</ul> diff --git a/files/vi/mdn/contribute/howto/index.html b/files/vi/mdn/contribute/howto/index.html deleted file mode 100644 index 08734f5092..0000000000 --- a/files/vi/mdn/contribute/howto/index.html +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: How-to guides -slug: MDN/Contribute/Howto -tags: - - Landing - - MDN Meta - - NeedsTranslation - - TopicStub -translation_of: MDN/Contribute/Howto ---- -<div>{{MDNSidebar}}</div><div>{{IncludeSubnav("/en-US/docs/MDN")}}</div> - -<p>These articles provide step-by-step guides to accomplishing specific goals when contributing to MDN.</p> - -<p>{{LandingPageListSubpages}}</p> diff --git a/files/vi/mdn/contribute/howto/tag/index.html b/files/vi/mdn/contribute/howto/tag/index.html deleted file mode 100644 index a766f40b5c..0000000000 --- a/files/vi/mdn/contribute/howto/tag/index.html +++ /dev/null @@ -1,376 +0,0 @@ ---- -title: How to properly tag pages -slug: MDN/Contribute/Howto/Tag -translation_of: MDN/Contribute/Howto/Tag ---- -<div>{{MDNSidebar}}</div> - -<p class="summary"><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>{{anch("Document category", "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>{{anch("Topic", "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>{{anch("API identification")}}</dt> - <dd>Reference pages about an API need to identify the specific component of the API being documented (that is, what interface it's a part of, and what property or method the page covers, if applicable).</dd> - <dt>{{anch("Technology status")}}</dt> - <dd>What's the status of the technology? Is it non-standard? Obsolete or deprecated? Experimental?</dd> - <dt>{{anch("Skill level")}}</dt> - <dd>For tutorials and guides, how advanced is the material covered by the article?</dd> - <dt>{{anch("Document metadata")}}</dt> - <dd>The writing community uses 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("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 API's overview, 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("SVG")}}</code></li> - <li><code>{{Tag("WebGL")}}</code></li> - <li><code>{{Tag("Tools")}}</code></li> - <li><code>{{Tag("Web")}}</code></li> - <li><code>{{Tag("Element")}}</code></li> - <li><code>{{Tag("Extensions")}}</code> and <code>{{Tag("WebExtensions")}}</code> for WebExtension documentation.</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">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> - -<h4 id="Mozilla-specific_content">Mozilla-specific content</h4> - -<p>These tags are used in Mozilla-specific content only:</p> - -<ul> - <li><code>{{Tag("Mozilla")}}</code></li> - <li><code>{{Tag("Firefox")}}</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> -</ul> - -<h3 id="API_identification">API identification</h3> - -<p>Within the API reference, each article should identify which part of the API it covers:</p> - -<dl> - <dt><code>{{tag("Interface")}}</code></dt> - <dd>The main article for an interface should have this tag. For example, {{DOMxRef("RTCPeerConnection")}}.</dd> - <dt><code>{{tag("Constructor")}}</code></dt> - <dd>Each interface may have up to one page tagged "Constructor"; this is the interface's constructor. The page should have the same name as the interface, like {{DOMxRef("RTCPeerConnection.RTCPeerConnection()", "RTCPeerConnection()")}}.</dd> - <dt><code>{{tag("Property")}}</code></dt> - <dd>Every article describing a particular property within an interface needs this tag. See {{DOMxRef("RTCPeerConnection.connectionState")}}, for example.</dd> - <dt><code>{{tag("Method")}}</code></dt> - <dd>Each article documenting an interface method needs this tag. See {{DOMxRef("RTCPeerConnection.createOffer()")}} for example.</dd> -</dl> - -<p>In addition, the reference pages need to include interface, property, and method names among their tags. Some examples:</p> - -<dl> - <dt>The interface {{DOMxRef("RTCPeerConnection")}}</dt> - <dd>Include the tag <code>{{Tag("RTCPeerConnection")}}</code> along with the other relevant tags (<code>{{Tag("Interface")}}</code>, <code>{{Tag("WebRTC")}}</code>, <code>{{Tag("WebRTC API")}}</code>, <code>{{Tag("API")}}</code>, <code>{{Tag("Reference")}}</code>, and so forth).</dd> - <dt>The method {{DOMxRef("RTCPeerConnection.createOffer()")}}</dt> - <dd>Include the tags <code>{{Tag("RTCPeerConnection")}}</code> and <code>{{Tag("createOffer")}}</code> (note <em>no</em> parentheses in tag names!) along with the other relevant tags, including <code>{{Tag("Method")}}</code>, <code>{{Tag("WebRTC")}}</code>, <code>{{Tag("WebRTC API")}}</code>, <code>{{Tag("API")}}</code>, <code>{{Tag("Reference")}}</code>, and so forth. Consider including things like <code>{{Tag("Offer")}}</code> and <code>{{Tag("SDP")}}</code>, which are also relevant here.</dd> - <dt>The property {{DOMxRef("RTCPeerConnection.iceConnectionState")}}</dt> - <dd>Include the tags <code>{{Tag("RTCPeerConnection")}}</code> and <code>{{Tag("iceConnectionState")}}</code> along with the other relevant tags, including <code>{{Tag("Property")}}</code>, <code>{{Tag("WebRTC")}}</code>, <code>{{Tag("WebRTC API")}}</code>, <code>{{Tag("API")}}</code> and <code>{{Tag("Reference")}}</code>. Also consider including <code>{{Tag("ICE")}}</code>.</dd> -</dl> - -<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("Read-only")}}</code></dt> - <dd>Apply this tag to reference pages which describe a property or attribute which is read-only.</dd> - <dt><code>{{Tag("Non-standard")}}</code></dt> - <dd>Indicates that the technology or API described on the page is not part of a standard, whether it's stable or not in any browsers which implement it (if it's not stable, it should also be {{Tag("Experimental")}}). 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 is 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. If the technology isn't part of any specification (even in draft form), it should also have the {{tag("Non-standard")}} tag.</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">compatibility table</a> in your article! That should always be present.</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("Draft")}}</code></dt> - <dd>The article is not complete, and is at least in theory still actively being updated (although it's also possible it's been forgotten about). Try to check with the most recent contributors before making changes, in order to avoid potential content collisions.</dd> - <dt><code>{{Tag("NeedsCompatTable")}}</code></dt> - <dd>The article needs a table to specify compatibility of a feature across browsers. <a href="/en-US/docs/MDN/Contribute/Structures/Compatibility_tables">See here</a> for a guide on contributing to browser compatibility.</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">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">live sample system</a>.</dd> - <dt><code>{{Tag("NeedsMarkupWork")}}</code></dt> - <dd>The article needs improvement to the page markup (usually because the page content consists mostly or entirely of {{HTMLElement("p")}} tags).</dd> - <dt><code>{{Tag("NeedsSpecTable")}}</code></dt> - <dd>The article needs a table to indicate on which specification document(s) the feature was defined.</dd> - <dt><code>{{Tag("NeedsUpdate")}}</code></dt> - <dd>The content is out of date and needs to be updated.</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> - -<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>{{Tag("WebGL")}}, {{Tag("Graphics")}}, {{Tag("Guide")}}, {{Tag("Beginner")}}</dd> - <dt>Reference page for {{HTMLElement("canvas")}}</dt> - <dd>{{Tag("Canvas")}}, {{Tag("HTML")}}, {{Tag("Element")}}, {{Tag("Graphics")}}, {{Tag("Reference")}}</dd> - <dt>A landing page for Firefox OS developer tools</dt> - <dd>{{Tag("Tools")}}, {{Tag("Firefox OS")}}, {{Tag("Landing")}}</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="blockIndicator 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> - -<div class="blockIndicator todo"> -<p><strong>FIXME:</strong> Filter topics have been changed since this was last updated.</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 rowspan="23" scope="row" style="vertical-align: baseline;">Topic</th> - <td>APIs and DOM</td> - <td>{{Tag("API")}} || {{Tag("DOM")}} {{Deprecated_Inline}}</td> - </tr> - <tr> - <td>Add-ons & Extensions {{Deprecated_Inline}}</td> - <td>{{Tag("Add-ons")}} || {{Tag("Extensions")}} || {{Tag("Plugins")}} || {{Tag("Themes")}} || {{Tag("WebExtensions")}}</td> - </tr> - <tr> - <td>CSS</td> - <td>{{Tag("CSS")}}</td> - </tr> - <tr> - <td>Canvas</td> - <td>{{Tag("Canvas")}}</td> - </tr> - <tr> - <td>Firefox</td> - <td>{{Tag("Firefox")}}</td> - </tr> - <tr> - <td>Firefox for Android {{Obsolete_Inline}}</td> - <td>{{Tag("Firefox Mobile")}}</td> - </tr> - <tr> - <td>Firefox for Desktop {{Obsolete_Inline}}</td> - <td>{{Tag("Firefox Desktop")}}</td> - </tr> - <tr> - <td>Firefox OS</td> - <td>{{Tag("Firefox OS")}}</td> - </tr> - <tr> - <td>Games</td> - <td>{{Tag("Games")}}</td> - </tr> - <tr> - <td>HTML</td> - <td>{{Tag("HTML")}}</td> - </tr> - <tr> - <td>HTTP</td> - <td>{{Tag("HTTP")}}</td> - </tr> - <tr> - <td>JavaScript</td> - <td>{{Tag("JavaScript")}}</td> - </tr> - <tr> - <td>Marketplace {{Non-standard_Inline}}</td> - <td>{{Tag("Marketplace")}}</td> - </tr> - <tr> - <td>MathML</td> - <td>{{Tag("MathML")}}</td> - </tr> - <tr> - <td>Mobile</td> - <td>{{Tag("Mobile")}}</td> - </tr> - <tr> - <td>Open Web Apps {{Non-standard_Inline}}</td> - <td>{{Tag("Apps")}}</td> - </tr> - <tr> - <td>SVG</td> - <td>{{Tag("SVG")}}</td> - </tr> - <tr> - <td>Web Development</td> - <td>{{Tag("Web Development")}}</td> - </tr> - <tr> - <td>Web Standards</td> - <td>{{Tag("Web")}}</td> - </tr> - <tr> - <td>WebExtensions</td> - <td>{{Tag("WebExtensions")}}</td> - </tr> - <tr> - <td>WebGL</td> - <td>{{Tag("WebGL")}}</td> - </tr> - <tr> - <td>XPCOM {{Non-standard_Inline}}</td> - <td>{{Tag("XPCOM")}}</td> - </tr> - <tr> - <td>XUL {{Non-standard_Inline}}</td> - <td>{{Tag("XUL")}}</td> - </tr> - <tr> - <th rowspan="3" scope="row" style="vertical-align: baseline; white-space: nowrap;">{{anch("Skill level")}}</th> - <td>I'm an Expert</td> - <td>{{Tag("Advanced")}}</td> - </tr> - <tr> - <td>Intermediate</td> - <td>{{Tag("Intermediate")}}</td> - </tr> - <tr> - <td>I'm Learning</td> - <td>{{Tag("Beginner")}}</td> - </tr> - <tr> - <th rowspan="7" scope="row" style="vertical-align: baseline; white-space: nowrap;">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> - <td>Demos</td> - <td><em>This includes Demo Studio content in the search results.</em></td> - </tr> - <tr> - <td>Tools</td> - <td>{{Tag("Tools")}}</td> - </tr> - <tr> - <td>Code Samples</td> - <td>{{Tag("Example")}}</td> - </tr> - <tr> - <td>How-To & Tutorial</td> - <td>{{Tag("Guide")}}</td> - </tr> - <tr> - <td>Developer Profiles</td> - <td><em>This includes developer profiles from the MDN site in the search results.</em></td> - </tr> - <tr> - <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 "{{anch("Document category", "category")}}" tag and a "{{anch("Topic", "topic")}}" 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 you may occasionally see some localized tags (such as <code>Référence</code>) showing up on some English pages. This was due to a <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=776048">bug in Kuma</a>, which caused the tags to reappear even if they were deleted. That bug has <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=776048#c37">since been fixed</a>, so any remaining localized tags can be cleaned up if they're spotted.</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" or {{anch("Document category", "another category tag")}} 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! They're ugly, they're hard to manage if they're allowed to linger too long, and they're terrible for {{Glossary("SEO")}}.</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">The tags box</a>" in the <a href="/en-US/docs/Project:MDN/Contributing/Editor_guide">MDN editor guide</a>.</p> diff --git a/files/vi/mdn/contribute/index.html b/files/vi/mdn/contribute/index.html deleted file mode 100644 index d0f126c32e..0000000000 --- a/files/vi/mdn/contribute/index.html +++ /dev/null @@ -1,77 +0,0 @@ ---- -title: Contributing to MDN -slug: MDN/Contribute -tags: - - Documentation - - Guide - - Landing - - MDN - - NeedsTranslation - - TopicStub -translation_of: MDN/Contribute ---- -<div>{{MDNSidebar}}</div> - -<p><font><font>Chào mừng bạn! </font><font>Bằng cách truy cập vào trang này, bạn đã thực hiện bước đầu tiên để trở thành người đóng góp cho MDN. </font></font></p> - -<p><span class="seoSummary"><font><font>Hướng dẫn được liệt kê ở đây bao gồm tất cả các khía cạnh đóng góp cho MDN, bao gồm hướng dẫn về phong cách, hướng dẫn sử dụng trình biên tập và công cụ của chúng tôi và hơn thế nữa. </font><font>Vui lòng đảm bảo bạn đã đọc (và tuân thủ) </font></font><a href="https://www.mozilla.org/en-US/about/legal/terms/mozilla/"><font><font>Điều khoản của Mozilla</font></font></a><font><font> trước khi chỉnh sửa hoặc tạo bất kỳ trang nào. </font></font></span></p> - -<p>Nếu bạn chưa từng đóng góp cho MDN trước đây, bài viết <a href="/vi/docs/MDN/Getting_started">Bắt Đầu</a> sẽ hướng dẫn bạn chọn một nhiệm vụ để có thể bắt đầu đóng góp ngay.</p> - -<div class="row topicpage-table"> -<div class="section"> -<h2 id="Hướng_dẫn_của_cộng_tác_viên"><font><font>Hướng dẫn của cộng tác viên</font></font></h2> - -<dl> - <dt><a href="/en-US/docs/MDN/Getting_started"><font><font>Bắt đầu</font></font></a></dt> - <dd><font><font>Hướng dẫn bắt đầu nhanh để thiết lập và đóng góp đầu tiên của bạn.</font></font></dd> - <dt><a href="/en-US/docs/MDN/Contribute/Style_guide"><font><font>Hướng dẫn về nội dung và phong cách</font></font></a></dt> - <dd><font><font>Hướng dẫn về nội dung và hướng dẫn phong cách MDN cung cấp chi tiết về cách viết phong cách, bố cục trang và kiểu nội dung để nội dung bạn viết phù hợp với phần nội dung còn lại của MDN.</font></font></dd> - <dt><a href="/en-US/docs/MDN/Contribute/Editor"><font><font>Hướng dẫn biên tập</font></font></a></dt> - <dd><font><font>Hướng dẫn đầy đủ để sử dụng trình soạn thảo của MDN.</font></font></dd> - <dt><a href="/en-US/docs/MDN/Contribute/Reviewing_articles"><font><font>Bài đánh giá</font></font></a></dt> - <dd><font><font>Hướng dẫn thực hiện các bài đánh giá kỹ thuật và biên tập nội dung bài viết, để giúp chúng tôi đảm bảo rằng tất cả nội dung trên MDN là hữu ích và dễ đọc nhất có thể!</font></font></dd> - <dt><a href="/en-US/docs/MDN/Contribute/Conventions"><font><font>Thuật ngữ và công ước</font></font></a></dt> - <dd><font><font>Thuật ngữ của chúng tôi và hướng dẫn công ước cung cấp thông tin bạn có thể sử dụng để đảm bảo rằng bạn sử dụng thuật ngữ chính xác để mô tả mọi thứ.</font></font></dd> - <dt><a href="/en-US/docs/MDN/Contribute/Community"><font><font>Làm việc với cộng đồng MDN</font></font></a></dt> - <dd><font><font>Hướng dẫn làm việc với cộng đồng của chúng tôi, tìm kiếm sự trợ giúp, và kết nối với những người có câu trả lời cho những câu hỏi phát sinh trong khi bạn đóng góp cho MDN.</font></font></dd> - <dt><a href="/en-US/docs/MDN/Contribute/FAQ"><font><font>Các câu hỏi thường gặp</font></font></a></dt> - <dd><font><font>Các mẹo và câu trả lời cho những câu hỏi phổ biến nhất về đóng góp cho MDN.</font></font></dd> -</dl> - -<dl> - <dt><a href="/en-US/docs/MDN/Kuma/Contributing"><font><font>Đóng góp cho Kuma</font></font></a></dt> - <dd><font><font>Hướng dẫn đóng góp cho dự án Kuma. </font><font>Kuma là nền tảng hỗ trợ trang web MDN.</font></font></dd> -</dl> -</div> - -<div class="section"> -<h2 id="Làm_thế_nào_để..."><font><font>Làm thế nào để...</font></font></h2> - -<p><font><font>Chúng tôi </font></font><a href="/en-US/docs/MDN/Contribute/Howto"><font><font>làm thế nào để hướng dẫn</font></font></a><font><font> cung cấp từng bước hướng dẫn để giúp bạn hoàn thành nhiệm vụ cụ thể khi góp phần MDN.</font></font></p> - -<dl> - <dt><a href="/en-US/docs/MDN/Contribute/Howto/Document_a_CSS_property"><font><font>Làm thế nào để tài liệu một tài sản CSS</font></font></a></dt> - <dd><font><font>Hướng dẫn viết tài liệu về thuộc tính CSS. </font><font>Tất cả tài liệu thuộc tính CSS phải khớp với kiểu và bố cục được mô tả trong bài viết này.</font></font></dd> - <dt><font><font>Làm thế nào để tài liệu một phần tử HTML</font></font></dt> - <dd><font><font>Hướng dẫn này để ghi lại các phần tử HTML sẽ đảm bảo rằng các tài liệu mà bạn viết khớp với những người khác trên MDN.</font></font></dd> - <dt><a href="/en-US/docs/MDN/Contribute/Howto/Tag"><font><font>Cách gắn thẻ trang đúng cách</font></font></a></dt> - <dd><font><font>Hướng dẫn để gắn thẻ trang cung cấp thông tin về các tiêu chuẩn của chúng tôi về gắn thẻ, bao gồm các danh sách các thẻ có ý nghĩa chuẩn trên MDN. </font><font>Theo hướng dẫn này sẽ đảm bảo rằng nội dung của bạn được phân loại đúng, tìm kiếm dễ dàng hơn và cơ chế lọc tìm kiếm hoạt động đúng với các bài viết của bạn.</font></font></dd> - <dt><a href="/en-US/docs/MDN/Contribute/Howto/Interpret_specifications"><font><font>Làm thế nào để giải thích chi tiết kỹ thuật</font></font></a></dt> - <dd><font><font>Hướng dẫn này sẽ giúp bạn giải thích đúng các tiêu chuẩn Web chuẩn; </font><font>có thể đọc được những điều này có thể là một hình thức nghệ thuật, và biết làm thế nào để làm điều đó sẽ giúp bạn tạo ra các tài liệu tốt hơn.</font></font></dd> -</dl> - -<h2 id="Nội_địa_hoá"><font><font>Nội địa hoá</font></font></h2> - -<dl> - <dt><a href="/en-US/docs/MDN/Contribute/Localize/Tour"><font><font>Tour hướng dẫn bằng tiếng địa phương</font></font></a></dt> - <dd><font><font>Hướng dẫn này sẽ hướng dẫn bạn cách định vị nội dung trên MDN.</font></font></dd> - <dt><a href="/en-US/docs/MDN/Contribute/Localize/Guide"><font><font>Hướng dẫn bản địa hoá</font></font></a></dt> - <dd><font><font>Hướng dẫn này cung cấp chi tiết về quy trình nội địa hóa cho nội dung MDN.</font></font></dd> - <dt><a href="/en-US/docs/MDN/Contribute/Localize/Localization_projects"><font><font>Dự án bản địa hoá</font></font></a></dt> - <dd><font><font>Tìm dự án bản địa hoá cho ngôn ngữ của bạn - hoặc, nếu không có, hãy tìm hiểu cách bắt đầu một ngôn ngữ mới!</font></font></dd> -</dl> -</div> -</div> - -<p> </p> |