React Glossary
Every technical field runs on acronyms that lock out anyone who has not already been in the room. A glossary is the cheapest way to widen your audience — and each definition is a landing page for a search someone genuinely makes.
A
- AEADAuthenticated Encryption with Associated DataCryptography
- A cipher mode that provides confidentiality and integrity in one pass, and additionally authenticates a header that is transmitted in the clear. GCM is the common instantiation.See GCM
- AttestationSecurity
- A signed statement from a device about its own configuration — firmware measurements, boot state, key provenance — that a remote party can verify before trusting it.See Root of Trust
D
- DOMDomain-Oriented MaskingSecurity
- A side-channel countermeasure that splits every secret into randomised shares processed in separate domains, so power consumption no longer correlates with the key.See SCA
E
- EOLEnd of LifeSupply
- The point at which a part stops being manufactured. A last-time-buy date is normally published alongside it, after which no further orders are accepted.
G
- GCMGalois/Counter ModeCryptography
- An AEAD mode combining counter-mode encryption with a Galois-field authenticator. Parallelisable, which is why it dominates line-rate link encryption.See AEAD
M
- ML-KEMModule-Lattice Key Encapsulation MechanismCryptography
- The post-quantum key establishment scheme standardised as FIPS 203, derived from CRYSTALS-Kyber. Replaces Diffie-Hellman key exchange against a quantum adversary.See PQC
- MOQMinimum Order QuantitySupply
- The smallest quantity a supplier will accept on an order line. Often set by reel or tray size rather than by policy.
P
- PQCPost-Quantum CryptographyCryptography
- Algorithms believed to resist attack by a large-scale quantum computer. Relevant today because of harvest-now-decrypt-later: traffic captured now can be decrypted once such a machine exists.See ML-KEM
R
- Root of TrustSecurity
- The minimal hardware component that is trusted implicitly because nothing else can vouch for it. Everything else in the security architecture derives its trust from this anchor.See Attestation
S
- SCASide-Channel AttackSecurity
- Recovering a secret from a physical measurement of the device — power draw, electromagnetic emission, or timing — rather than from a mathematical weakness in the algorithm.See DOM
T
- TRNGTrue Random Number GeneratorCryptography
- An entropy source derived from a physical process rather than an algorithm. SP 800-90B specifies how the raw entropy must be assessed and conditioned before use.
X
- XTSXEX-based Tweaked-codebook with ciphertext StealingCryptography
- A block cipher mode designed for storage, where each sector is encrypted under a tweak derived from its address. Provides confidentiality but no authentication.
Installation
npx shadcn@latest add "https://kelvinui.com/registry/glossary.json"
Props
| Prop | Type | Description |
|---|---|---|
| terms | GlossaryTerm[] | { id, term, expansion?, definition, category?, seeAlso?, href? } |
| title | string | Optional heading |
| showCategories | boolean | Category filter chips (default true) |
Terms sort and group alphabetically on their own — pass them in any order. Each entry gets its id as a DOM id, so /glossary#pqc links straight to a definition, which is what you want from inline links elsewhere in your docs. seeAlso ids that do not resolve are skipped rather than rendered as dead links.
Writing definitions people finish
- Lead with what it is, not what it stands for. The expansion goes in
expansion; the first sentence ofdefinitionshould be the meaning. - Two sentences. One for the definition, one for why the reader should care. The ML-KEM and PQC entries above follow this shape.
- Cross-reference in both directions. If PQC mentions ML-KEM, ML-KEM should point back. Readers arrive at whichever term they searched for.
- Define what you actually use. A glossary padded with terms you never mention reads as SEO filler, and it is — search engines have been discounting that pattern for a long time. Definitions that match your own documentation are the ones that earn traffic.
New components every week
Get the week's new Kelvin UI components and templates in one short email. No spam, unsubscribe anytime.