diff options
Diffstat (limited to 'files/id/mdn/contribute')
| -rw-r--r-- | files/id/mdn/contribute/feedback/index.html | 56 | ||||
| -rw-r--r-- | files/id/mdn/contribute/getting_started/index.html | 126 | ||||
| -rw-r--r-- | files/id/mdn/contribute/howto/index.html | 16 | ||||
| -rw-r--r-- | files/id/mdn/contribute/howto/tag/index.html | 373 | ||||
| -rw-r--r-- | files/id/mdn/contribute/index.html | 23 | ||||
| -rw-r--r-- | files/id/mdn/contribute/processes/index.html | 23 |
6 files changed, 0 insertions, 617 deletions
diff --git a/files/id/mdn/contribute/feedback/index.html b/files/id/mdn/contribute/feedback/index.html deleted file mode 100644 index fc2958dc4f..0000000000 --- a/files/id/mdn/contribute/feedback/index.html +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: 'Project:Tanggapan' -slug: MDN/Contribute/Feedback -tags: - - Dokumentasi - - MDN - - MDN Meta - - Panduan -translation_of: MDN/Contribute/Feedback ---- -<div>{{MDNSidebar}}</div> - -<p>Selamat datang di Mozilla Developer Network! Jika kamu mempunyai masalah, atau ingin meminta saran, ini tempat yang tepat. Kenyataannya kamu tertarik mengirimkan tanggapan membuat anda semakin menjadi bagian dari komunitas Mozilla, dan kami berterima kasih atas ketertarikan kamu.</p> - -<p>Kamu memiliki beberapa pilihan untuk menawarkan wawasan, artikel ini akan membantumu melakukannya.</p> - -<h2 id="Memperbarui_dokumentasi">Memperbarui dokumentasi</h2> - -<p>Pertama-tama, jika kamu melihat masalah dalam dokumentasi, kamu boleh mengkoreksinya sendiri. Masuk dengan <a href="https://www.persona.org/">Persona</a>, tekan tombol biru Edit sehingga membuka editor dan masukan kata untuk berkontribusi pada dokumentasi MDN. Dokumentasi di sini adalah pengetahuan, dan dikumpulkan oleh team relawan dan staff yang dibayar, jadi jangan malu -- tata bahasa kamu tidak harus sempurna. Kami akan membersihkan jika kamu membuat kesalahan; tak ada salahnya untuk dilakukan!</p> - -<p>Untuk informasi lebih lanjut tentang kontribusi untuk dokumentasi MDN, lihat:</p> - -<ul> - <li><a href="/en-US/docs/Project:Getting_started">Awal mula</a></li> - <li><a href="/en-US/docs/Project:How_to_Help">Cara membantu</a></li> - <li><a href="/en-US/docs/Project:MDN_editing_interface">Merubah tampilan MDN</a></li> -</ul> - -<h2 id="Gabung_dalam_percakapan">Gabung dalam percakapan</h2> - -<p>Bicara pada kami! Ada beberapa cara untuk terhubung dengan orang lain yang bekerja dalam konten MDN.</p> - -<h3 id="Obrolan">Obrolan</h3> - -<p>Kami menggunakan Internet Relay Chat (<a href="https://wiki.mozilla.org/IRC">IRC</a>) untuk mendiskusikan MDN dan kontennya. Kamu dapat bergabung dalam percakapan! Kami mempunyai beberapa saluran, tergantung pada minat kamu:</p> - -<dl> - <dt><a href="irc://irc.mozilla.org/mdn">Situs MDN (#mdn)</a></dt> - <dd>Saluran ini untuk diskusi umum MDN. Bila kamu tidak yakin dimana mendapatkan bantuan, atau masalah yang melibatakan kamu, kamu dapat bertanya di sini!</dd> - <dt><a href="irc://irc.mozilla.org/mdndev">Situs dokumentasi pengembang (#mdndev)</a></dt> - <dd>Di saluran #mdndev ini kita membahas tentang pekerjaan pengembang platform yang berjalan pada situs MDN. Bila kamu memiliki masalah tentang fungsionalitas website, atau ide tentang fitur, kamu dapat bergabung dalam pembahasan ini.</dd> -</dl> - -<h3 id="Asinkron_Diskusi">(Asinkron) Diskusi</h3> - -<p>Diskusi jangka panjang terjadi di <a href="https://discourse.mozilla-community.org/c/mdn">forum diskusi MDN</a> kita. Kamu bisa posting ke forum via email ke <a href="mailto:mdn@mozilla-community.org">mdn@mozilla-community.org</a>. Jika kamu bergabung dengan forum, kamu dapat memilih untuk memiliki pemberitahuan tentang diskusi yang dikirimkan kepada kamu melalui email juga.</p> - -<h2 id="Laporkan_masalah">Laporkan masalah</h2> - -<h3 id="Masalah_dokumentasi">Masalah dokumentasi</h3> - -<p>Bila kamu melihat masalah dalam dokumentasi dan tidak bisa memperbaikinya sendiri karena berbagai alasan, kamu dapat <a href="https://github.com/mdn/sprints/issues/new?template=issue-template.md&projects=mdn/sprints/2&labels=user-report">melaporkan masalah</a>! Kamu dapat menggunakan formulir ini untuk semua masalah dokumentasi, apakah itu koreksi sederhana atau permintaan untuk sepotong konten yang sama sekali baru. Seperti disebutkan sebelumnya, kami mengundang anda untuk berkontribusi dengan melakukan perubahan sendiri, tetapi opsi pelaporan ini tersedia untuk kamu juga.</p> - -<h3 id="Masalah_situs">Masalah situs</h3> - -<p>Bila kamu mengalami masalah dengan situs web MDN, atau memiliki ide untuk fitur baru dalam situs ini, anda dapat <a href="https://bugzilla.mozilla.org/form.mdn">mengajukan permintaan</a> dalam sistem Bugzilla juga.</p> diff --git a/files/id/mdn/contribute/getting_started/index.html b/files/id/mdn/contribute/getting_started/index.html deleted file mode 100644 index 04dd189549..0000000000 --- a/files/id/mdn/contribute/getting_started/index.html +++ /dev/null @@ -1,126 +0,0 @@ ---- -title: Langkah Awal Di MDN -slug: MDN/Contribute/Getting_started -tags: - - Dokumentasi - - Langkah Awal - - MDN - - Panduan - - Proyek MDN -translation_of: MDN/Contribute/Getting_started ---- -<div>{{MDNSidebar}}</div><div>{{IncludeSubnav("/id/docs/MDN")}}</div> - -<p id="What_is_MDN.3F"><span class="seoSummary">Kami adalah komunitas terbuka yang terdiri dari pengembang dan penulis sumber daya untuk Web yang lebih baik, terlepas dari merek, browser, atau perangkat. Siapa saja dapat memberikan kontribusinya dan mereka yang membuat kami semakin kuat. Bersama kita bisa melanjutkan untuk menggerakkan inovasi di Web untuk memberikan pelayanan yang lebih baik. Dimulai disini, dengan Anda. </span></p> - -<p><span>Setiap bagian dari MDN (dokumen, demonstrasi, dan situs itu sendiri) dibuat oleh komunitas terbuka para pengembang sumber daya. Bergabunglah bersama kami!</span></p> - -<h2 id="3_langkah_mudah_untuk_MDN"><span>3 langkah mudah untuk MDN</span></h2> - -<p>MDN adalah sebuah ensiklopedia, dimana <strong>semua orang</strong> bisa menambah dan mengedit konten. Anda tidak perlu menjadi seorang pemrogram atau mengetahui banyak hal mengenai teknologi. Ada beberapa tugas yang harus diselesaikan, mulai dari yang termudah (Mengoreksi bacaan and mengoreksi kesalahan penulisan) <span id="result_box" lang="id"><span class="hps">hingga yang kompleks</span></span> (menulis dokumentasi Program aplikasi antarmuka, <em>API</em>).</p> - -<p>Ikut berkontribusi sangatlah mudah dan aman. Bahkan jika Anda melakukan kesalahan, itu mudah diperbaiki. Bahkan jika Anda tidak mengetahui dengan tepat bagaimana suatu hal yang seharusnya benar, atau tata bahasa Anda tidak sepenuhnya bagus, jangan khawatir akan hal tersebut! Kami memiliki tim yang terdiri dari orang-orang yang bekerja untuk memastikan bahwa konten di MDN bisa lebih baik sebisa mungkin. Seseorang akan ikut serta untuk memastikan bahwa pekerjaan Anda rapih dan ditulis dengan benar.</p> - -<h3 id="Langkah_1_Membuat_akun_di_MDN">Langkah 1: Membuat akun di MDN</h3> - -<p>Untuk memulai kontribusi Anda di MDN, Anda memerlukan sebuah akun di MDN. Untuk keterangan lanjut, silahkan lihat <a href="/en-US/docs/MDN/Contribute/Howto/Create_an_MDN_account">bagaimana membuat sebuah akun</a>.</p> - -<h3 id="Langkah_2_Ambil_sebuah_tugas_untuk_diselesaikan">Langkah 2: Ambil sebuah tugas untuk diselesaikan</h3> - -<p>Setelah Anda selesai login, bacalah deskripsi mengenai perbedaan tipe tugas pada daftar dibawah ini, dan tentukan mana yang menjadi daya tarik bagi Anda. Anda bisa mengambil tugas manapun yang Anda sukai sebagai kontribusi yang Anda berikan.</p> - -<h3 id="Langkah_3_Kerjakan_tugas">Langkah 3: Kerjakan tugas</h3> - -<p>Setelah Anda menentukan tugas seperti apa yang Anda ingin kerjakan, temukan halaman yang spesifik, misalnya kode, atau yang lainnya untuk dikerjakan, dan lakukanlah!</p> - -<p>Jangan khawatir mengenai kesempurnaan dalam mengerjakan; kontributor MDN lainnya ada disini untuk membantu memperbaiki kesalahan yang terjadi. Jika Anda ingin melakukan percobaan sebelum melakukan sesuatu "yang nyata", Anda bisa mengedit halaman <a href="/en-US/docs/Sandbox">Kotakpasir</a>. Jika Anda memiliki pertanyaan selama melakukan pekerjaan, kunjungi halaman <a href="/en-US/docs/MDN/Community">Komunitas</a> untuk informasi di daftar surat menyurat (<em>mailing lists</em>) dan saluran bercakap (<em>Chat Channels</em>) dimana Anda bisa mendapatkan jawaban.</p> - -<p>Ketika Anda selesai, silahkan ambil item lainnya, atau lihat lagi <a href="#Other_things_you_can_do_on_MDN">Hal lain yang Anda bisa lakukan di MDN</a>.</p> - -<h2 id="Jenis-jenis_tugas_yang_memungkinkan">Jenis-jenis tugas yang memungkinkan</h2> - -<p>Ada banyak jalan yang dapat Anda ambil untuk berkontribusi untuk MDN tergantung keahlian yang Anda persiapkan dan sukai. Walaupun beberapa tugas bisa menghilangkan semangat, kami juga memiliki banyak kegiatan mudah yang tersedia. Kegiatan tersebut setidaknya hanya membutuhkan lima menit (atau kurang!) dari waktu Anda. Bersama dengan tugas dan dengan deskripsi yang pendek, Anda akan mengetahui <span id="result_box" lang="id"><span class="hps">berapa waktu</span> <span class="hps">perkiraan</span> <span class="hps">setiap</span> <span class="hps">jenis tugas</span> biasanya akan diselesaikan<span>.</span></span></p> - -<h3 id="Opsi_1_Saya_menyukai_kata-kata">Opsi 1: Saya menyukai kata-kata</h3> - -<p>Anda bisa membantu kami meninjau atau mengedit dokumen yang ada, dan menerapkan label yang benar.</p> - -<ul> - <li><a href="/en-US/docs/MDN/Contribute/Howto/Set_the_summary_for_a_page">Mengatur ringkasan untuk halaman</a> (5-15 menit)</li> - <li><a href="/en-US/docs/Project:MDN/Contributing/How_to/Do_an_editorial_review">Tinjauan tajuk rencana</a> (5–30 menit)</li> - <li><a href="/en-US/docs/MDN/User_guide/Writing#Editing_an_existing_page">Memperbaharui artikel yang ada dengan informasi baru</a> (5 menit-1 jam)</li> - <li><a href="/en-US/docs/MDN/User_guide/Writing#Adding_a_new_page">Tulis sebuah artikel tentang teknologi baru atau <em>API </em></a>(30 menit-2 jam)</li> -</ul> - -<div class="note"><strong>Catatan:</strong> Jika Anda sedang meninjau artikel atau menulis artikel yang baru, kami berharap Anda meninjau <a href="/en-US/docs/Project:MDN/Style_guide">Panduan Gaya</a>. Ini akan membantu untuk meyakinkan bahwa artikel tersebut sesuai.</div> - -<h3 id="Opsi_2_Saya_menyukai_kode">Opsi 2: Saya menyukai kode</h3> - -<p>Kami membutuhkan lebih banyak sampel kode! Anda juga dapat membantu membangun perangkat halaman kami, <a href="https://developer.mozilla.org/en-US/docs/Project:MDN/Kuma">Kuma</a>!</p> - -<ul> - <li><a href="/en-US/docs/Project:MDN/Contributing/How_to/Convert_code_samples_to_be_live_">Konversi sampel kode menjadi "aktif"</a> (30 menit)</li> - <li><a href="https://kuma.readthedocs.org/en/latest/installation-vagrant.html">Menyusun lingkungan membangun Kuma</a> (1 jam)</li> - <li><a href="https://github.com/mozilla/kuma#readme">Kirim kode tambalan Anda ke pusat kode Kuma</a> (1 jam)</li> - <li><a href="https://developer.mozilla.org/en-US/demos/submit">Mengajukan demonstrasi baru </a>(1 jam)</li> -</ul> - -<h3 id="Opsi_3_Saya_menyukai_kata-kata_dan_kode">Opsi 3: Saya menyukai kata-kata dan kode</h3> - -<p>Kami memiliki tugas-tugas yang membutuhkan teknis dan kemampuan bahasa bersama, seperti menulis artikel baru, meninjau keakurasian teknis, atau mengadapsikan dokumen-dokumen.</p> - -<ul> - <li><a href="/en-US/docs/Project:MDN/Contributing/How_to/Tag_JavaScript_pages">Halaman label JavaScript</a> (5 menit)</li> - <li><a href="/en-US/docs/MDN/Promote">Promosikan MDN di situs web Anda</a> (5 menit)</li> - <li><a href="/en-US/docs/Project:MDN/Contributing/How_to/Do_a_technical_review">Tinjauan teknis</a> (30 menit)</li> - <li><a href="/en-US/docs/Project:MDN/Contributing/How_to/Update_API_page_layout">Perbaharui tata ruang halaman API</a> (30 menit)</li> - <li><a href="/en-US/docs/MDN/Contribute/Creating_and_editing_pages#Creating_a_new_page">Tulis sebuah artikel baru yang akrab bagi Anda</a> (1 jam atau lebih)</li> -</ul> - -<h3 id="Opsi_4_Saya_ingin_MDN_ada_di_bahasa_saya">Opsi 4: Saya ingin MDN ada di bahasa saya</h3> - -<p>Semua lokalisasi and terjemahan selesai dikerjakan di MDN oleh komunitas sukarelawan kami yang mengagumkan.</p> - -<ul> - <li><a href="/en-US/docs/MDN/Contribute/Localize/Translating_pages">Menerjemahkan halaman</a> (2 jam)</li> - <li>Menghubungkan dengan lokalisir lainnya yang terdaftar di <a href="/en-US/docs/Project:MDN/Localizing/Localization_projects">Proyek lokalisasi</a> (30 menit)</li> -</ul> - -<h3 id="Opsi_5_Saya_menemukan_beberapa_kesalahan_informasi_tapi_saya_tidak_tahu_bagaimana_memperbaikinya">Opsi 5: Saya menemukan beberapa kesalahan informasi tapi saya tidak tahu bagaimana memperbaikinya</h3> - -<p>Anda dapat melaporkan masalah tersebut dengan <a class="external" href="https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Developer%20Network">mengisi dokumentasi kesalahan</a>. (5 menit)</p> - -<p>Gunakan nilai bidang ini:</p> - -<table class="standard-table"> - <tbody> - <tr> - <td><strong>Bidang Bugzilla</strong></td> - <td><strong>Nilai</strong></td> - </tr> - <tr> - <td><code>produk</code></td> - <td><a href="https://bugzilla.mozilla.org/enter_bug.cgi?product=Developer+Documentation">Dokumentasi Pengembang</a></td> - </tr> - <tr> - <td><code>komponen</code></td> - <td>[<span id="result_box" lang="id"><span class="hps">memilih</span> <span class="hps">daerah yang sesuai</span> <span class="hps">dengan topik</span><span>,</span> <span class="hps">atau</span> <span class="atn hps">"</span><span>Umum</span><span>"</span> <span class="hps">jika Anda tidak</span> <span class="hps">yakin</span> <span class="hps">atau</span> <span class="hps">Anda tidak melihat</span> mana <span class="hps">yang benar</span></span>]</td> - </tr> - <tr> - <td><code>URL</code></td> - <td>Halaman dimana Anda menemukan masalah</td> - </tr> - <tr> - <td><code>Deskripsi</code></td> - <td>Sebanyak yang Anda ketahui atau memiliki waktu untuk mengutarakan masalah tersebut dan dimana menemukan informasi yang benar. Ini dapat berisi orang-orang yang ("berbicara jadi-dan-jadi") sebaik mungkin seperti tautan Web.</td> - </tr> - </tbody> -</table> - -<h2 id="Hal-hal_lai_yang_bisa_Anda_lakukan_di_MDN">Hal-hal lai yang bisa Anda lakukan di MDN</h2> - -<ul> - <li><a href="/en-US/docs/Project:Community">Bergabung dengan komunitas MDN</a>.</li> - <li><a href="/en-US/profile">Isi profil Anda</a> jadi yang lain dapat mengetahui lebih tentangmu.</li> - <li>Belajar lebih lanjut tentang <a href="/en-US/docs/MDN/Contribute">berkontribusi untuk MDN</a>.</li> -</ul> diff --git a/files/id/mdn/contribute/howto/index.html b/files/id/mdn/contribute/howto/index.html deleted file mode 100644 index 1ac1697957..0000000000 --- a/files/id/mdn/contribute/howto/index.html +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: How-to guides -slug: MDN/Contribute/Howto -tags: - - Documentation - - Landing - - MDN - - NeedsTranslation - - TopicStub -translation_of: MDN/Contribute/Howto ---- -<div>{{MDNSidebar}}</div><div>{{IncludeSubnav("/id/docs/MDN")}}</div> - -<p>Artikel berikut menyediakan pedoman langkah - langkah untuk mencapai tujuan tertentu ketika berkontribusi di MDN.</p> - -<p>{{LandingPageListSubpages}}</p> diff --git a/files/id/mdn/contribute/howto/tag/index.html b/files/id/mdn/contribute/howto/tag/index.html deleted file mode 100644 index 8b0d868f78..0000000000 --- a/files/id/mdn/contribute/howto/tag/index.html +++ /dev/null @@ -1,373 +0,0 @@ ---- -title: How to properly tag pages -slug: MDN/Contribute/Howto/Tag -translation_of: MDN/Contribute/Howto/Tag ---- -<div>{{MDNSidebar}}</div><p dir="rtl">One important feature of MDN that helps users find content is the <strong>article tag</strong>. Each page can be tagged with zero or more tags <span style="line-height: 1.572;">(preferably at least one)</span><span style="line-height: 1.572;"> to help categorize the content. <span class="seoSummary">There are many ways tags are used to help organize information on MDN; this page will help you learn how to best tag pages to help information be organized, sorted, and located by readers.</span></span></p> - -<p>For a guide to the user interface for editing tags on pages, see the <a href="/en-US/docs/MDN/Contribute/Editor/Basics#The_tags_box">tagging section</a> in our editor guide.</p> - -<p>Note that proper use of tags is important; we are increasingly using automation to generate lists of content, landing pages, and cross-linking of articles. Failure to properly tag articles as indicated below can prevent articles from being listed correctly.</p> - -<h2 id="Ways_tags_are_used_on_MDN">Ways tags are used on MDN</h2> - -<p>There are several ways tags get used on MDN:</p> - -<dl> - <dt>Categorization</dt> - <dd>What type of document is it? Is it a reference? A tutorial? A landing page? These can be used when filtering searches, so they're really important!</dd> - <dt>Topic identification</dt> - <dd>What topic does the article cover? Is it about an API? The DOM? Graphics? These, too, are important, because they can be used as filters on searches.</dd> - <dt>Technology status</dt> - <dd>What's the status of the technology? Is it non-standard? Obsolete or deprecated? Experimental?</dd> - <dt>Skill level</dt> - <dd>For tutorials and guides, how advanced is the material covered by the article?</dd> - <dt>Document metadata</dt> - <dd>The writing community often needs a way to track information about pages in need of specific kinds of work. This is done using tags.</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="Category">Category</h3> - -<p>Tagging an article with one of these categories will help automatically constructed landing pages, table of contents pages, and the like be more accurately built. These terms will also be used by our new search system, eventually, to let the user locate reference or guide information by their choice.</p> - -<p>The following category names are standard tagging terms used on MDN.</p> - -<dl> - <dt><code>{{Tag("Intro")}}</code></dt> - <dd>The article provides introductory material about a topic. In theory there should be only one of these per technology area.</dd> - <dt><code>{{Tag("Featured")}}</code></dt> - <dd>The article is a high-importance article that should be featured in a special way on landing pages; this must be used sparingly. Only three or fewer of these should exist in any documentation area.</dd> - <dt><code>{{Tag("Reference")}}</code></dt> - <dd>The article contains reference material about an API, element, attribute, property, or the like.</dd> - <dt><code>{{Tag("Landing")}}</code></dt> - <dd>The page is a landing page.</dd> - <dt><code>{{Tag("Guide")}}</code></dt> - <dd>The article is a how-to or guide page.</dd> - <dt><code>{{Tag("Example")}}</code></dt> - <dd>The article is a code sample page, or has code samples. This shouldn't be used for very one-liner "syntax examples" but actual snippets of useful code, or for full usable samples.</dd> -</dl> - -<h3 id="Topic">Topic</h3> - -<p>By identifying the article's topic area, you can also help to generate better search results as well as landing pages and other navigational aids.</p> - -<p>While there's some room for flexibility here as new topic areas are identified, we try to keep these to the names of APIs or technologies. Some useful examples:</p> - -<ul> - <li><code>{{Tag("HTML")}}</code></li> - <li><code>{{Tag("CSS")}}</code></li> - <li><code>{{Tag("JavaScript")}}</code> (notice the capital "S"!)</li> - <li><code>{{Tag("Document")}}</code></li> - <li><code>{{Tag("DOM")}}</code></li> - <li><code>{{Tag("API")}}</code> for each interface, method and property.</li> - <li><code>{{Tag("Method")}}</code> for each method of an API</li> - <li><code>{{Tag("Property")}}</code> for each property of an API</li> - <li><code>{{Tag("Graphics")}}</code></li> - <li><code>{{Tag("Firefox OS")}}</code></li> - <li><code>{{Tag("Gecko")}}</code></li> - <li><code>{{Tag("XUL")}}</code></li> - <li><code>{{Tag("XPCOM")}}</code></li> - <li><code>{{Tag("SVG")}}</code></li> - <li><code>{{Tag("WebGL")}}</code></li> - <li><code>{{Tag("Element")}}</code></li> - <li><code>{{Tag("Node")}}</code></li> - <li><code>{{Tag("Tools")}}</code></li> - <li><code>{{Tag("Web")}}</code></li> -</ul> - -<p>In general, the name of an interface that has a number of related pages, such as <a href="/en-US/docs/Web/API/Node" title="/en-US/docs/Web/API/Node">Node</a> (which has many pages for its various properties and methods) makes a good topic identification tag, as does the name of an overall technology or technology type. A page about WebGL might be tagged with <code>Graphics</code> and <code>WebGL</code>, for example, while a page about the {{HTMLElement("canvas")}} element might be tagged <code>HTML</code>, <code>Element</code>, <code>Canvas</code>, and <code>Graphics</code>.</p> - -<h3 id="Technology_status">Technology status</h3> - -<p>To help the reader understand how viable a technology is, we use tags to label pages as to what the status of the technology's specification is. This isn't as detailed as actually explaining what the spec is and where in the specification process the technology is (that's what the Specifications table is for), but it will help the reader judge, at a glance, whether using the technology described in the article is a good idea or not.</p> - -<p>Here are possible values for these tags:</p> - -<dl> - <dt><code>{{Tag("Non-standard")}}</code></dt> - <dd>Indicates that the technology or API described on the page is not part of a standard, but is considered stable in the browser or browsers that do implement it. If you don't use this tag, the assumption is made that the article covers something that's 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 has been marked as deprecated in the specification, and is expected 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 in the process of 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.</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>Regardless of the use of these tags, you should be sure to include a <a href="/en-US/docs/Project:Compatibility_tables" title="/en-US/docs/Project:Compatibility_tables">compatibility table</a> in your article!</p> - -<h3 id="Skill_level">Skill level</h3> - -<p>The skill level tag type is only used for guides and tutorials (that is, pages tagged <code>Guide</code>). It's used to help users whittle down tutorials based on their familiarity level with a technology, for example. 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 that have gotten started with the technology but aren't experts.</dd> - <dt><code>{{Tag("Advanced")}}</code></dt> - <dd>Articles about stretching the capabilities of a technology and of the reader.</dd> -</dl> - -<h3 id="Document_metadata">Document metadata</h3> - -<p>The writing community uses tags to label articles as requiring specific types of work. Here's a list of the ones we use most:</p> - -<dl> - <dt><code>{{Tag("junk")}}</code></dt> - <dd>The article needs to be deleted.</dd> - <dt><code>{{Tag("NeedsContent")}}</code></dt> - <dd>The article is a stub, or is otherwise lacking information. This tag means that someone should review the content and add more details and/or finish writing the article.</dd> - <dt><code>{{Tag("NeedsExample")}}</code></dt> - <dd>The article needs one or more examples created to help illustrate the article's point. These examples should use the <a href="/en-US/docs/Project:MDN/Contributing/How_to_help/Code_samples" title="/en-US/docs/Project:MDN/Contributing/How_to_help/Code_samples">live sample system</a>.</dd> - <dt><code>{{Tag("NeedsLiveSamples")}}</code></dt> - <dd>The article has one or more examples that need to be updated to use the <a href="/en-US/docs/Project:MDN/Contributing/How_to_help/Code_samples" title="/en-US/docs/Project:MDN/Contributing/How_to_help/Code_samples">live sample system</a>.</dd> - <dt><code>{{Tag("NeedsUpdate")}}</code></dt> - <dd>The content is out of date and needs to 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> - -<h3 id="Web_Literacy_Map">Web Literacy Map</h3> - -<p>The <a href="https://webmaker.org" rel="external">WebMaker</a> project, through the <a href="https://webmaker.org/literacy" rel="external">Web Literacy Map</a>, has defined a set of tags to qualify the various competencies and skills recommended to get better at reading, writing and participating on the Web. We use them on MDN to help our users to find the best resources to suit their needs:</p> - -<dl> - <dt>{{Tag("Navigation")}}</dt> - <dd>The articles provides information on how to browse the web.</dd> - <dt>{{Tag("WebMechanics")}}</dt> - <dd>The article provides information on how the web is organized and how it's working.</dd> - <dt>{{Tag("Search")}}</dt> - <dd>The article provides information on how to locate information, people and resources via the web.</dd> - <dt>{{Tag("Credibility")}}</dt> - <dd>The article provides information on how to critically evaluate information found on the web.</dd> - <dt>{{Tag("Security")}}</dt> - <dd>The article provides information on how to keep systems, identities, and content safe.</dd> - <dt>{{Tag("Composing")}}</dt> - <dd>The article provides information on how to create and curate content for the web.</dd> - <dt>{{Tag("Remixing")}}</dt> - <dd>The article provides information on how to modify existing web resources to create something new.</dd> - <dt>{{Tag("DesignAccessibility")}}</dt> - <dd>The article provides information on how to create universally effective communications through web resources.</dd> - <dt>{{Tag("CodingScripting")}}</dt> - <dd>The article provides information on how to code and/or create interactive experiences on the web.</dd> - <dt>{{Tag("infrastructure")}}</dt> - <dd>The article provides information which help understanding the Internet technical stack.</dd> - <dt>{{Tag("Sharing")}}</dt> - <dd>The article provides information on how to create resources with others.</dd> - <dt>{{Tag("Collaborating")}}</dt> - <dd>The article provides information on how to work with each other.</dd> - <dt>{{Tag("Community")}}</dt> - <dd>The article provides information on how to get involved in web communities and understanding their practices.</dd> - <dt>{{Tag("Privacy")}}</dt> - <dd>The article provides information on how to examine the consequences of sharing data online.</dd> - <dt>{{Tag("OpenPractices")}}</dt> - <dd>The article provides information on how to help keep the web universally accessible.</dd> -</dl> - -<h2 id="Putting_it_all_together">Putting it all together</h2> - -<p>So, with these different types of tags, you assemble them together to get the full set of tags for a page. A few examples:</p> - -<dl> - <dt>A tutorial about WebGL for beginners</dt> - <dd>Appropriate tags would be: <code>WebGL</code>, <code>Graphics</code>, <code>Guide</code>, <code>Beginner</code></dd> - <dt>Reference page for the {{HTMLElement("canvas")}} element</dt> - <dd>This should be tagged with <code>Canvas</code>, <code>HTML</code>, <code>Element</code>, <code>Graphics</code> <code>Reference</code></dd> - <dt>A landing page for Firefox OS developer tools</dt> - <dd>This should be tagged with <code>Tools</code>, <code>Firefox OS</code>, <code>Landing</code></dd> -</dl> - -<h2 id="Tagging_and_search_filters">Tagging and search filters</h2> - -<p>The upcoming search filter implementation, which will let users restrict the results of their searches based on criteria they specify, will rely on proper tagging of pages on MDN. Here's a table of the various search filters and which tags they look for.</p> - -<div class="note"> -<p><strong>Note:</strong> If multiple tags are listed under "Tag name," that means any one or more of those tags need to be present for the article to match.</p> -</div> - -<table class="standard-table"> - <thead> - <tr> - <th scope="col">Filter group</th> - <th scope="col">Search filter name</th> - <th scope="col">Tag name</th> - </tr> - </thead> - <tbody> - <tr> - <th>Topic</th> - <td>Open Web Apps</td> - <td>{{Tag("Apps")}}</td> - </tr> - <tr> - <th> </th> - <td>HTML</td> - <td>{{Tag("HTML")}}</td> - </tr> - <tr> - <th> </th> - <td>CSS</td> - <td>{{Tag("CSS")}}</td> - </tr> - <tr> - <th> </th> - <td>JavaScript</td> - <td>{{Tag("JavaScript")}}</td> - </tr> - <tr> - <th> </th> - <td>APIs and DOM</td> - <td>{{Tag("API")}}</td> - </tr> - <tr> - <th> </th> - <td>Canvas</td> - <td>{{Tag("Canvas")}}</td> - </tr> - <tr> - <th> </th> - <td>SVG</td> - <td>{{Tag("SVG")}}</td> - </tr> - <tr> - <th> </th> - <td>MathML</td> - <td>{{Tag("MathML")}}</td> - </tr> - <tr> - <th> </th> - <td>WebGL</td> - <td>{{Tag("WebGL")}}</td> - </tr> - <tr> - <th> </th> - <td>XUL</td> - <td>{{Tag("XUL")}}</td> - </tr> - <tr> - <th> </th> - <td>Marketplace</td> - <td>{{Tag("Marketplace")}}</td> - </tr> - <tr> - <th> </th> - <td>Firefox</td> - <td>{{Tag("Firefox")}}</td> - </tr> - <tr> - <th> </th> - <td>Firefox for Android</td> - <td>{{Tag("Firefox Mobile")}}</td> - </tr> - <tr> - <th> </th> - <td>Firefox for Desktop</td> - <td>{{Tag("Firefox Desktop")}}</td> - </tr> - <tr> - <th> </th> - <td>Firefox OS</td> - <td>{{Tag("Firefox OS")}}</td> - </tr> - <tr> - <th> </th> - <td>Mobile</td> - <td>{{Tag("Mobile")}}</td> - </tr> - <tr> - <th> </th> - <td>Web Development</td> - <td>{{Tag("Web Development")}}</td> - </tr> - <tr> - <th> </th> - <td>Add-ons & Extensions</td> - <td>{{Tag("Add-ons ")}}|| {{Tag("Extensions")}} || {{Tag("Plugins")}} || {{Tag("Themes")}}</td> - </tr> - <tr> - <th> </th> - <td>Games</td> - <td>{{Tag("Games")}}</td> - </tr> - <tr> - <th>Skill level</th> - <td>I'm an Expert</td> - <td>{{Tag("Advanced")}}</td> - </tr> - <tr> - <th> </th> - <td>Intermediate</td> - <td>{{Tag("Intermediate")}}</td> - </tr> - <tr> - <th> </th> - <td>I'm Learning</td> - <td>{{Tag("Beginner")}}</td> - </tr> - <tr> - <th>Document type</th> - <td>Docs</td> - <td><em>This will restrict the search to docs content, leaving out Hacks and other MDN content.</em></td> - </tr> - <tr> - <th> </th> - <td>Demos</td> - <td><em>This will include Demo Studio content in the search results.</em></td> - </tr> - <tr> - <th> </th> - <td>Tools</td> - <td>{{Tag("Tools")}}</td> - </tr> - <tr> - <th> </th> - <td>Code Samples</td> - <td>{{Tag("Example")}}</td> - </tr> - <tr> - <th> </th> - <td>How-To & Tutorial</td> - <td>{{Tag("Guide")}}</td> - </tr> - <tr> - <th> </th> - <td>Developer Profiles</td> - <td><em>This will include developer profiles from the MDN site in the search results.</em></td> - </tr> - <tr> - <th> </th> - <td>External Resources</td> - <td><em>This is something the dev team will need to figure out.</em></td> - </tr> - </tbody> -</table> - -<h2 id="Tagging_problems_you_can_fix">Tagging problems you can fix</h2> - -<p>There are several types of problems with tags you can help fix:</p> - -<dl> - <dt>No tags</dt> - <dd>All articles should have at least one tag, and usually more than one. Generally, at a minimum, articles should have at least a "<a href="/en-US/docs/Project:MDN/Contributing/Tagging_standards#Category" title="/en-US/docs/Project:MDN/Contributing/Tagging_standards#Categories">category</a>" tag and a "<a href="/en-US/docs/Project:MDN/Contributing/Tagging_standards#Topic" title="/en-US/docs/Project:MDN/Contributing/Tagging_standards#Topic">topic</a>" tag. Often other tags are appropriate as well, but if you can help us ensure that at least these are present, you'll be a documentation hero!</dd> - <dt>Tags that don't follow our tagging standards</dt> - <dd>We have a <a href="/en-US/docs/Project:MDN/Contributing/Tagging_standards" title="/en-US/docs/Project:MDN/Contributing/Tagging_standards">Tagging standards</a> guide that explains how we use tags, including lists of appropriate tags to use on various types of documentation. Ideally, all articles should follow these standards, so if you see a page whose tags don't do so, please fix it!</dd> - <dt>Incorrect tags</dt> - <dd>If you're looking at an article about HTML and it's got the "JavaScript" tag on it, that's probably wrong! Similarly, if an article is about Mozilla internals but has the "Web" tag on it, that's probably wrong too. Remove these tags (and, if missing, add the right ones). This type of problem includes misspelled tags. "JavaScript" or "Javascript" for example (the latter actually will match, since tags are case-insensitive, but it's just not right!).</dd> - <dt>Missing tags</dt> - <dd>If an article has some tags, but not all of the appropriate ones, feel free to add more. Maybe you're looking at a page in the JavaScript reference, which is correctly tagged with "JavaScript" but has no other tags. Since it's a reference page, this should also have the "Reference" tag. You're invited to add it!</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 tags for a page, leaving a page with 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". These need to be deleted posthaste!</dd> -</dl> - -<p>If you see one (or more) of these problems, you can help by <a href="/en-US/docs/Project:MDN/Contributing/Getting_started#Logging_into_MDN">logging into MDN</a>, then clicking the Edit button at the top right of the MDN window. Once the editor loads up, scroll down to the bottom of the page, where you'll see the tag box. For more details on the tagging interface, see "<a href="/en-US/docs/Project:MDN/Contributing/Editor_guide#The_tags_box" title="/en-US/docs/Project:MDN/Contributing/Editor_guide#The_tags_box">The tags box</a>" in the <a href="/en-US/docs/Project:MDN/Contributing/Editor_guide" title="/en-US/docs/Project:MDN/Contributing/Editor_guide">MDN editor guide</a>.</p> diff --git a/files/id/mdn/contribute/index.html b/files/id/mdn/contribute/index.html deleted file mode 100644 index 4d76fd020d..0000000000 --- a/files/id/mdn/contribute/index.html +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Contributing to MDN -slug: MDN/Contribute -tags: - - Documentation - - Guide - - Landing - - MDN - - NeedsTranslation - - TopicStub -translation_of: MDN/Contribute ---- -<div>{{MDNSidebar}}</div><div>{{IncludeSubnav("/en-US/docs/MDN")}}</div> - -<p>Selamat Datang! Dengan mengunjungi halaman ini, anda telah mengambil satu langkah menjadi kontributor di MDN!</p> - -<p><span class="seoSummary">Daftar paduan disini memuat semua aspek kontribusi ke MDN, diantaranya paduan style, paduan menggunakan alat dan editor kami, dan banyak lagi. Pastikan anda membaca (dan aduan tentang) <a href="https://www.mozilla.org/en-US/about/legal/terms/mozilla/">Mozilla Terms</a> sebelum mengedit atau membuat halaman. </span></p> - -<p>Jika anda belum pernah berkontribusi di MDN, Paduan <a href="/en-US/docs/MDN/Getting_started">Memulai</a> bisa membantu anda memulai.</p> - -<div class="row topicpage-table"> </div> - -<p>{{LandingPageListSubPages()}}</p> diff --git a/files/id/mdn/contribute/processes/index.html b/files/id/mdn/contribute/processes/index.html deleted file mode 100644 index d01213c69f..0000000000 --- a/files/id/mdn/contribute/processes/index.html +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Proses dokumentasi -slug: MDN/Contribute/Processes -tags: - - ButuhPenerjemahan - - Landing - - MDN Meta - - Meta MDN - - NeedsTranslation - - Pendaratan - - Processes - - Proses - - RintisanTopik - - TopicStub -translation_of: MDN/Contribute/Processes ---- -<div>{{MDNSidebar}}</div> - -<div>{{IncludeSubnav("/en-US/docs/MDN")}}</div> - -<p>The MDN documentation project is enormous; there are a huge number of technologies to cover, and we have hundreds of contributors all over the world. To help bring order to chaos, we've got standard processes to follow when working on specific documentation-related tasks. Here you'll find guides to those processes.</p> - -<p>{{LandingPageListSubPages()}}</p> |