Basic concepts with glossary overrides#1954
Merged
jeremydesroches merged 2 commits intoNov 19, 2020
Merged
Conversation
12 tasks
Contributor
|
Thanks @rogermparent ! I'll use it in #1944 and let you know if any issues. |
Contributor
|
Many thanks, @rogermparent ! We'll continue the discussion in #1944 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is #1944 with a commit that adds the ability to override a glossary's tooltip entry with a new MD frontmatter field,
tooltip.When
tooltipis specified, it will be parsed at build-time and used as the content of the glossary tooltip- otherwise, the previous behavior is used and the MD body forms the tooltip.content/docs/user-guide/glossaryhas been changed to show this feature off: