Agent-readable docs index: /llms.txt. Download /docs.zip to grep all markdown files locally.

Components

This section follows the same broad structure as Mintlify's component docs, but the examples render through Holocron's actual MDX component map.

Browse by use case

Structure content
Columns, cards, steps, tiles, and tree layouts.
Draw attention
Callouts, badges, banner config, tooltips, and updates.
Show hidden content
Accordions, expandables, tabs, and views.
Document APIs
Fields, responses, request examples, response examples, and panel layouts.
Visual helpers
Icons, color tokens, frames, mermaid diagrams, and previews.
AI-oriented UI
Prompt cards and examples useful for agent-facing docs.

Importing components in .tsx files

All MDX components are available from @holocron.so/vite/mdx. This is useful when you build custom components that compose Holocron primitives:
import { Card, CardGroup, Callout, Steps, Step } from '@holocron.so/vite/mdx'

export function FeatureGrid({ features }) {
  return (
    <CardGroup cols={3}>
      {features.map((f) => (
        <Card key={f.title} title={f.title} icon={f.icon}>
          {f.description}
        </Card>
      ))}
    </CardGroup>
  )
}
You only need this import when writing .tsx component files. In MDX pages, all components are available globally without imports.

What to expect on each page

  • A short explanation of the Mintlify component concept
  • Holocron examples that actually render in this repo
  • A Holocron differences section when parity is incomplete or behavior differs
Some Mintlify docs describe behaviors that are broader than Holocron's current implementation. Those differences are called out explicitly instead of being hidden.
Powered byHolocron