Revision 912363 of Glossary documentation status

<div>{{DocStatusQuickLinks()}}</div>

<p>This page tries to track ongoing documentation work in the MDN <a href="/en-US/docs/Glossary">Glossary</a>. Feel free to contribute! Planning and actual work in progress is tracked on the on <a class="external external-icon" href="https://trello.com/b/LDggrYSV">the community trello board</a>.</p>

<h2 id="Summary">Summary</h2>

<p>{{DocStatus('Glossary','[]', 'March 1, 2014', '', '', '', '["Navigation", "WebMechanics", "Search", "Credibility", "Security", "Composing", "Remixing", "Design","Accessibility", "CodingScripting", "Infrastructure", "Sharing", "Collaborating", "Community", "Privacy", "OpenPractices","Disambiguation"]')}}</p>

<h2 id="Current_priorities">Current priorities</h2>

<h3 id="Technical_Review">Technical Review</h3>

<p>There are a lot of articles flagged for technical review. You can check if they are technically correct and correct them and/or remove the flag as appropriate.</p>

<h3 id="Editorial_Review">Editorial Review</h3>

<p>Articles need to be correctly formatted and spell-checked. <a href="/en-US/docs/Glossary/Class">Here</a> is an example of a well-formatted entry.</p>

<h3 id="Cut_longer_articles">Cut longer articles</h3>

<p>If an article is too long, it needs to be reduced as per guidelines <a href="/en-US/docs/MDN/Contribute/Howto/Write_a_new_entry_in_the_Glossary">here</a>. If you think a long article is particularly well written and deserves to be preserved, discuss it with us, on the dev-mdc mailing list. It can be moved to the appropriate area of MDN if it's deserving of it's own place on the site.</p>

<h3 id="General_check_of_completeness">General check of completeness</h3>

<p>There are a lot of articles. We should check to see if they need content and tag them appropriately. Coordination for this work is done on our <a href="https://trello.com/b/LDggrYSV">Trello board</a>.</p>

<h3 id="Use_the_Glossary_macro">Use the Glossary macro</h3>

<p>Articles in the Glossary Area, the Learning Area and MDN in general should use the Glossary macro (where appropriate). You can learn more about the glossary macro <a href="https://developer.mozilla.org/en-US/docs/MDN/Contribute/Howto/Write_a_new_entry_in_the_Glossary#How_to_use_the_.7B.7BGlossary.7D.7D_macro">here</a>.</p>

<h2 id="How_to_improve_the_content">How to improve the content</h2>

<h3 id="Tagging_standard">Tagging standard</h3>

<ul>
 <li>Each page should be tagged with at least one <a href="/en-US/docs/MDN/Contribute/Howto/Tag#Web_Literacy_Map">tag from the web literacy map</a>.</li>
 <li>If pages are related to a given technology, they should be tagged with that <a href="/en-US/docs/MDN/Contribute/Howto/Tag#Topic">technology name</a>.</li>
 <li>If pages need any type of work, a "<strong>Need*</strong>" tag should be added.</li>
</ul>

<h3 id="Link_the_glossary">Link the glossary</h3>

<p>While browsing and editing MDN, you can easly link any term to the glossary by using the <a href="/en-US/docs/Template:Glossary">Glossary</a> macro.</p>

<p>It takes up to three&nbsp;possible parameters:</p>

<ol>
 <li>The term to link to (note that terms are case insensitive)</li>
 <li>An alternate text to display (an expression identical to the term, a plural version, etc.)</li>
 <li>A flag indicating if the link must be displayed as a regular link (<code>1</code>) or as a soft link (<code>0</code>, the default)</li>
</ol>

<table class="standard-table">
 <thead>
  <tr>
   <th scope="col">Macro</th>
   <th scope="col">Result</th>
  </tr>
 </thead>
 <tbody>
  <tr>
   <td>\{{Glossary("Browser")}}</td>
   <td>{{Glossary("Browser")}}</td>
  </tr>
  <tr>
   <td>\{{Glossary("Browser", "Web browser")}}</td>
   <td>{{Glossary("Browser","Web browser")}}</td>
  </tr>
  <tr>
   <td>\{{Glossary("Browser", "Web browser", 1)}}</td>
   <td>{{Glossary("Browser","Web browser",1)}}</td>
  </tr>
 </tbody>
</table>

<h3 id="Writing_a_term_definition">Writing a term definition</h3>

<p>A term definition page must have three clear sections:</p>

<ol>
 <li>A summary that shortly defines the term (one to two sentences at most)</li>
 <li>An in-depth definition that provides all the necessary details to understand what the term covers</li>
 <li>A "Learn more" section that provides various links to dig deeper in the area covered by this term</li>
</ol>

<p>The content of a term definition must be written assuming the reader has no specific knowledge about the term and its usage. Use&nbsp;simple&nbsp;and straightforward English. Try to avoid as many technicalities as possible (it's not always possible but try to simplify).</p>

<p>Please remember that while gathering information from other sites is a good thing, it isn't good practice to copy and paste passages (or even entire articles) from them (otherwise we could just link to them).</p>

<p>For more detailed information check out the "<a href="/en-US/docs/Project:MDN/Contributing/How_to/Write_a_new_entry_in_the_Glossary">how to write a new entry in the glossary</a>" article.</p>

<h2 id="Learning_area_meeting">Learning area meeting</h2>

<p>The Learning Area weekly meeting takes place in the <a class="text external external-icon" href="irc://irc.mozilla.org/mdn" rel="nofollow">#mdn</a> channel on irc.mozilla.org at 10 AM PDT (17:00 UTC, 19:00 CET). <a class="text external external-icon" href="https://arewemeetingyet.com/UTC/2014-10-06/17:00/w/Learning%20Area%20Weekly%20Meeting" rel="nofollow">See the meeting time in your time zone.</a> It's open to anyone that would like to participate, so please feel free to join in!</p>

<p>{{CommunityBox("Glossary", "dev-mdc", "mozilla.dev.mdc", "mdn", "Meetings|https://wiki.mozilla.org/MDN/Projects/Content/Learning_Area/Weekly_meetings|Every Monday in IRC||Glossary mentors|/profiles/klez|klez++/profiles/Biraj|Biraj")}}</p>