-
Notifications
You must be signed in to change notification settings - Fork 441
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
Write a Glossary #1367
Labels
stale
All issues that are marked as stale due to inactivity
Comments
12 tasks
63 tasks
dwelsch-esi
added a commit
to dwelsch-esi/keda-docs
that referenced
this issue
May 10, 2024
- Moved some content from KEDA concept topics to Reference. - Added a glossary, issue kedacore#1367 - Removed non-inclusive language, issue kedacore#1373 kedacore#1366 kedacore#1367 kedacore#1373 Umbrella issue for CNCF tech docs recommendations: kedacore#1361 Signed-off-by: David Welsch <[email protected]>
1 task
nate-double-u
pushed a commit
to nate-double-u/kedacore-keda-docs
that referenced
this issue
May 30, 2024
- Moved some content from KEDA concept topics to Reference. - Added a glossary, issue kedacore#1367 - Removed non-inclusive language, issue kedacore#1373 kedacore#1366 kedacore#1367 kedacore#1373 Umbrella issue for CNCF tech docs recommendations: kedacore#1361 Signed-off-by: David Welsch <[email protected]>
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This is actively being worked on in #1389 |
This issue has been automatically closed due to inactivity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Create a glossary of terms specific to KEDA. Also include key Kubernetes terms that are vital to understanding KEDA. The glossary also spells out acronyms.
Add the glossary to the Reference section. Where a glossary term is used in the documentation, link to the definition in the glossary.
This issue tracks recommended changes resulting from an analysis of the KEDA documentation commissioned by CNCF. The analysis and supporting documents are here: https://github.com/cncf/techdocs/tree/main/assessments/0011-keda/
Use-Case
The primary purpose of a glossary is to define terms so that a reader can understand the documentation as they read it; without this information, either a reader's understanding is incomplete or they have to intrusively interrupt their reading to look up a term on the internet. Even better, if supported by the web framework, is if the term is available via mouse-over contextual help.
Specification
For an example from another CNCF project, see the glossary in the Backstage documentation.
Here is a partial list of terms to include:
The text was updated successfully, but these errors were encountered: