Repository URL to install this package:
|
Version:
2.0.0 ▾
|
| config |
| js |
| src |
| README.md |
| composer.json |
| melt_glossify.info.yml |
| melt_glossify.libraries.yml |
| melt_glossify.links.menu.yml |
| melt_glossify.module |
| melt_glossify.routing.yml |
| melt_glossify.tokens.inc |
Leverages Glossify module, its Glossify Taxonomy sub-module, Tippy.js for handling tooltips and the Token module.
melt_glossifyThe default functionality Glossify provides automatically chooses the first term or all instances of a term for you:
admin/config/content/formatsTooltips with taxonomy option and choose the taxonomy vocabulary to have terms glossifiedIf you open up a token browser window, you'll find a global melt Glossify token that can be used in places where you want more control over the placement of terms.
Basic
[meltglossify:<vocab_machine_name>:<termname/id>:?<label_override>]
Replace <vocab_machine_name> with the machine name of the vocabulary and <termname/id> with the term name or term id.
Custom label
[meltglossify:<vocab_machine_name>:<termname/id>:?<label_override>]
If you need to override the term name with a custom label.
Say we have a vocabulary called Glossary and it has a few terms like cat, dog, bird. If we wanted to use cat somewhere on our page, we would use [meltglossify:glossary:cat]. Drupal would then compile that token into <abbr title="Definition of a cat">cat</abbr>.
The title on the <abbr> tag gets pulled from the Description field from the taxonmy term. If no description is available, it just falls back to the term name without being wrapped in an abbr tag.
A settings page has been created at: admin/config/melt_glossify/settings.
You'll be able to:
tippy(options) instance.