Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Glossary Enhancements #43

Open
3 tasks
stijn-dejongh opened this issue Oct 23, 2023 · 2 comments
Open
3 tasks

Glossary Enhancements #43

stijn-dejongh opened this issue Oct 23, 2023 · 2 comments
Labels
good first issue Good for newcomers status: pinned Issues and PRs that should not be labeled as stale or closed if they remain inactive. type: automation About actions workflows and automation. type: enhancement New feature or request.

Comments

@stijn-dejongh
Copy link
Member

stijn-dejongh commented Oct 23, 2023

Similar to docsify, adding links from content pages towards the glossary would make the reading experience more enjoyable.

Context

We want to encourage underatanding and clarity. To do so, jargon used in the knowledge base should eiher be explained in it's immediate context, or be added to the glossary.

For potential future integrations, it would make sense to include alternate content access methods for the glossary terms, such as XML, or JSON. This would encourage re-use by other people.

Acceptance criteria

  • terminology used in text refers to glossary definition
  • the glossary page itself is exempt from this logic
  • add an XML rendering of the glossary terms, including an XSD schema file

Implementation Caveats

  • avoid client-side scripting if possible
  • consider writing a custom Hugo preprocessor to add links to textual pages
  • make sure the links to glossary definitions is subtle, but readable (e.g. a thin, dashed line, and a cursor change to the info pointer). Will require a custom terminology link css class.
@stijn-dejongh stijn-dejongh added type: enhancement New feature or request. type: automation About actions workflows and automation. labels Oct 23, 2023
@stijn-dejongh
Copy link
Member Author

Update:
As a first iteration, consider porting the docsify-glossary javascript utility to the knowledge base. While it implies client-side processing, it would get the implementation done much quicker.

To be checked: page render time impact (especially on slow internet connections).

@stijn-dejongh stijn-dejongh added the good first issue Good for newcomers label Nov 30, 2023
@stijn-dejongh
Copy link
Member Author

Update: possible implementation

We can rework the generation of content pages by adapting the way HTML pages are generated.
Concretely, the ReplaceRe and RelRef functions in HUGO can be used to create a custom content pipe, similar to markdownify. This can then be applied to selected sections, and replace occurrences of Glossary-included terminology and abbreviations with links to the glossary.

Update: Additional feature

Include permalinks to each of the glossary's elements.
Consider adding a UUID to each element, to make sure the links act as true permalinks and do not break when the content/name of entries is modified.

References

@stijn-dejongh stijn-dejongh added the status: pinned Issues and PRs that should not be labeled as stale or closed if they remain inactive. label Jul 13, 2024
@stijn-dejongh stijn-dejongh pinned this issue Aug 16, 2024
@stijn-dejongh stijn-dejongh unpinned this issue Sep 20, 2024
@stijn-dejongh stijn-dejongh pinned this issue Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers status: pinned Issues and PRs that should not be labeled as stale or closed if they remain inactive. type: automation About actions workflows and automation. type: enhancement New feature or request.
Projects
None yet
Development

No branches or pull requests

1 participant