vitessio / vitessio/website

Add a glossary

Open
#1,982 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation help wanted
Dominant language
Java
Stars
70
Forks
236
Avg merge
5h 41m
Merged PRs (30d)
9

Description

Overview

Add a glossary of terms to the documentation site.

Audience: All

Type: Reference

Context

This issue tracks recommended changes resulting from an analysis of the Vitess
documentation commissioned by CNCF. The analysis and supporting documents are
here: https://github.com/cncf/techdocs/tree/main/analyses/0014-vitess under
0014-Vitess.

See the umbrella issue
listing all issues identified in the analysis.

Possible Implementation

Related material in the current doc:

Suggested changes:

Add a glossary. This is different from the "Concepts" page – the explanations
of terms is less in-depth. The glossary contains not just key terms but any word
or phrase that the reader might not know: abbreviations and acronyms,
definitions of Vitess-specific terms, and explanations of jargon used in Vitess
("topo", for example).

You can locate the glossary in the main doc table of contents (TOC), or in the
Reference section of the doc website.

See these other CNCF projects for examples of glossaries:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the CNCF analysis 0014-Vitess, the umbrella issue, and the existing Concepts page. Compare the linked etcd and KEDA glossaries to define the glossary’s scope and terminology. Done means a glossary covering unfamiliar Vitess terms, abbreviations, acronyms, and jargon is added to the documentation site and linked from the main TOC or Reference section.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.