-
Adding a glossary to help with the technical jargon.
-
We want an index that links terms to the pages they occur on. From among those terms we pick the ones we want to give a definition, and this becomes the glossary.
rvosa updated
7 years ago
-
-
-
# ℹ️ Description
While reviewing the requirements, me and Melih noticed that we have not add the user tag that we have written in [Communication Features](https://github.com/bounswe/bounswe2024group1…
-
It would be nice to be able to configure that only the first match on a page gets a popup. The old `Products.PloneGlossary` had this option in the control panel.
I had a go at this last week, but …
-
See #488 for notes about how to go about this. Instead of specific pages, another strategy would be to translate all verbiages of a specific kind, so let's try to translate all headers.
Here's a…
-
# What should we add to our content collections?
A summary of terms used within Aiven that can be defined in one sentence.
Some examples:
- Service
- Account
- User
- Project
- Service Us…
-
As said by Andrew Hu on Facebook:
> also would like to add that Arg(page 16, question 21) should have a definition in the glossary
-
![image.png](https://raw.githubusercontent.com/marklowsk/pe/main/files/63f36e2a-a0d7-4615-9c58-42b1d123da6b.png)
Placeholder text still there.