Difference between revisions of "Glossary"

From Freephile Wiki
Jump to navigation Jump to search
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{Feature
 
{{Feature
|explains    = Terminology
+
|image=Blue flat directory icon.svg
|description = You use jargon at work; you're wiki should know that jargon.
+
|imgdesc=Automatic glossary of terms
|notes        =[[mw:Extension:Lingo]] first added here in January 2016
+
|title=
|tests          = [[Terminology]] page where you can add/edit glossary terms.
 
|examples  =GPL
 
 
}}
 
}}
 +
{{#set:feature description = You use jargon at work; you're wiki should know that jargon. }}
 +
{{#set:feature notes = [[mw:Extension:Lingo]] first added here in January 2016 }}
 +
{{#set:feature tests = [[Terminology]] page where you can add/edit glossary terms. }}
 +
{{#set:feature examples = GPL }}
  
 
== What's It Good For? ==
 
== What's It Good For? ==
 
Every profession and/or group uses specific jargon.  The TLA is everywhere.  ATM, BMW, XML.  Does everyone in your organization even know what your acronyms stand for?  With this feature, every document in your wiki becomes instantly self-aware as TLAs are defined automatically by the glossary page.
 
Every profession and/or group uses specific jargon.  The TLA is everywhere.  ATM, BMW, XML.  Does everyone in your organization even know what your acronyms stand for?  With this feature, every document in your wiki becomes instantly self-aware as TLAs are defined automatically by the glossary page.
  
This wiki has a [[explainsFeature::Terminology]] page where you can add/edit glossary terms.  Thanks to the [[mw:Extension:Lingo]], these terms are then visually expanded by 'tooltips' '''wherever they occur''' in the content.  For example, the acronyms API and GNHLUG used in this sentence are decorated by the Lingo extension due to their definitions in the Terminology page.  
+
This wiki has a [[Terminology]] page where you can add/edit glossary terms.  Thanks to the [[mw:Extension:Lingo]], these terms are then visually expanded by 'tooltips' '''wherever they occur''' in the content.  For example, the acronyms API and GNHLUG used in this sentence are decorated by the Lingo extension due to their definitions in the Terminology page.  
  
 
If you see an acronym on this wiki, and it doesn't have a tooltip, then fix it by adding it to the [[Terminology]] page.   
 
If you see an acronym on this wiki, and it doesn't have a tooltip, then fix it by adding it to the [[Terminology]] page.   
  
There can actually be multiple such pages in case your organization or content structure would work better with multiple glossaries.  
+
There can actually be multiple such pages in case your organization or content structure would work better with multiple glossaries.
  
 
[[Category:Feature]]
 
[[Category:Feature]]

Latest revision as of 16:57, 14 May 2020

Glossary Dialog-information.svg
Automatic glossary of terms
Image shows: Automatic glossary of terms
Summary
Description: You use jargon at work; you're wiki should know that jargon.
More
Notes: mw:Extension:Lingo first added here in January 2016
Test: Terminology page where you can add/edit glossary terms.
Example: GPL




What's It Good For?[edit | edit source]

Every profession and/or group uses specific jargon. The TLA is everywhere. ATM, BMW, XML. Does everyone in your organization even know what your acronyms stand for? With this feature, every document in your wiki becomes instantly self-aware as TLAs are defined automatically by the glossary page.

This wiki has a Terminology page where you can add/edit glossary terms. Thanks to the mw:Extension:Lingo, these terms are then visually expanded by 'tooltips' wherever they occur in the content. For example, the acronyms API and GNHLUG used in this sentence are decorated by the Lingo extension due to their definitions in the Terminology page.

If you see an acronym on this wiki, and it doesn't have a tooltip, then fix it by adding it to the Terminology page.

There can actually be multiple such pages in case your organization or content structure would work better with multiple glossaries.