Then the words only have to be defined once. When using the wiki template, we’d have to use the template whenever we want to use an abbreviation. But with a glossary, 1 configuration line would suffice to make the underlines word + abbreviation explanation tooltip appear wiki wide.
I think the Glossary template would be better overall, since the Wiki page I am partially responsible for has multiple unfamiliar acronyms:
Using the Glossary template would allow me to define these unfamiliar acronyms in a concise manner using definitions. Here is an example code block:
{{glossary}}
{{term|1=MWEB}}
{{defn|1=Mimblewimble Extension Block is an optional transaction feature that enhances privacy by concealing wallet addresses and transaction amounts between the sender and recipient. It operates on a parallel private blockchain, ensuring that these sensitive details remain confidential.}}
{{glossary end}}
This may potentially lead to informing Whonix users about each cryptocurrencies’ benefits and drawbacks from an anonymity and/or privacy perspective.
However, the Lingo extension is only viable if the acronym definition alone is sufficient. Here is an example code block:
;MWEB:Mimblewimble Extension Block
Otherwise, the Glossary template is more comprehensive, but it requires placing the glossary itself somewhere on the same page, typically near the footer, so the choice depends on how much information you want to provide along with its presentation.