| name | docusaurus-glossary |
| description | Use when working with docusaurus-plugin-glossary to configure, manage glossary terms, troubleshoot issues, and explain features |
Docusaurus Glossary
Quick Start
Configure the plugin in docusaurus.config.js and create a glossary JSON file:
// docusaurus.config.js - Using the preset (recommended)
module.exports = {
presets: [
[
'docusaurus-plugin-glossary/preset',
{
glossary: {
glossaryPath: 'glossary/glossary.json',
routePath: '/glossary',
},
docs: {
/* your docs config */
},
},
],
],
};
Core Principles
- Auto-linking: Terms in markdown are automatically detected and linked with tooltips (via preset)
- Glossary JSON: Single source of truth at
glossary/glossary.jsonwith terms array - Component-based: Use
<GlossaryTerm term="API" />for manual control in MDX - Preset approach: Use the preset to auto-configure the remark plugin for docs, blog, and pages
Common Patterns
Adding Glossary Terms
Create/update glossary/glossary.json with term objects containing term, definition, and optional abbreviation, relatedTerms
Troubleshooting Auto-linking
If terms aren't linking: verify glossaryPath exists, ensure using the preset (not just plugin), clear cache with npm run clear, restart dev server
Reference Files
For detailed documentation, see:
- configuration.md - Plugin options and setup
- usage.md - Using terms and components
- troubleshooting.md - Common issues and fixes
Notes
- Requires Docusaurus v3 and React 18
- Terms inside code blocks, links, or MDX components are not auto-linked
- Matching is case-insensitive but respects word boundaries
- Plugin includes GlossaryPage component and GlossaryTerm theme component