Glossary

Last updated Jun 18, 2026 View as Markdown Agent setup

The Glossary component is used 25 times on 25 pages.

See all examples of pages that use Glossary

Used 25 times.

Pages

/ai-crawl-control/reference/glossary/ - Source
/ai-gateway/glossary/ - Source
/api-shield/glossary/ - Source
/bots/glossary/ - Source
/byoip/glossary/ - Source
/cache/glossary/ - Source
/cloudflare-one/glossary/ - Source
/cloudflare-wan/glossary/ - Source
/d1/reference/glossary/ - Source
/dns/glossary/ - Source
/durable-objects/reference/glossary/ - Source
/email-security/glossary/ - Source
/fundamentals/reference/glossary/ - Source
/kv/glossary/ - Source
/logs/glossary/ - Source
/magic-transit/glossary/ - Source
/network-flow/glossary/ - Source
/queues/glossary/ - Source
/spectrum/glossary/ - Source
/speed/glossary/ - Source
/waf/glossary/ - Source
/waiting-room/glossary/ - Source
/workers-ai/platform/glossary/ - Source
/workers/glossary/ - Source
/workflows/reference/glossary/ - Source

Partials

Use the glossary definition shortcode to render the defined glossary definition. Additionally, you can include a prepend value to add words to the start of the definition.

Create the glossary entries in a file dedicated to your product. These YAML files live in /src/content/glossary/<YOUR-PRODUCT>.yaml

Component

import { Glossary } from "~/components"

<Glossary />

Glossary

productName: Style Guide
entries:
  - term: example
    general_definition: |-
      Hello, world! You can use **Markdown** features inside of your `tooltips`.

Was this helpful?