Archive Guide

Syntactic protocols for the Grand Codex.

1. The Virtual File System (VFS)

The engine utilizes a dynamic Virtual File System. When organizing your scrolls, use the interactive sidebar to create infinite directories and documents. Behind the scenes, the Storage Adapter parses these structures seamlessly depending on your configured environment (Local vs Cloud).

2. Connecting Scrolls (MDX Linking)

To reference another entity within the codex, you must utilize precise directory paths. The editor intelligently intercepts relative markdown links that begin with a forward slash (/).

// Goal: Link to a file named 'protagonist.mdx' inside the 'characters' directory.

[The Outcast](/characters/protagonist)

// Goal: Link to a deeply nested lore entry.

[Ancient Treaty](/history/age-of-strife/treaty-of-iron)

CRITICAL RULE: You do NOT need to include the `.mdx` or `.md` extension in the path URL. The router automatically resolves the virtual node.

3. The Interactive Timeline

As a native MDX engine, you possess the ability to summon React components directly within your text. The most vital component is the <Timeline>. Use it to forge chronological sequences of events.

// Inject this block into any scroll to render a visual timeline.

<Timeline 
  events={[
    { 
      date: "3045 AE", 
      title: "The Siege of Atoria", 
      description: "The capital fell after a 40-day blockade." 
    },
    { 
      date: "3046 AE", 
      title: "The Signing", 
      description: "The [Treaty of Iron](/history/treaty) was drafted." 
    }
  ]} 
/>