Zorid fields are frontmatter values stored directly in Markdown files. Types are optional schemas that make a subset of those fields typed, visible, validated, and editor-enhanced.Documentation Index
Fetch the complete documentation index at: https://aidocs.zorid.app/llms.txt
Use this file to discover all available pages before exploring further.
Fields belong to the file. A Type controls which fields are active, grouped, typed, validated, and shown with richer editors.
Field syntax
v0 field syntax is YAML frontmatter:Primitive inference
Without a Type, Zorid still indexes fields and infers primitives from YAML:| YAML value | Inferred field type |
|---|---|
active | string |
12 | int |
4.5 | float |
true / false | boolean |
2026-06-01 | date |
2026-06-01T14:30:00+08:00 | datetime |
[a, b] | list |
| empty / null | null |
Types (.ztype)
Default location: .zorid/types/*.ztype.
string, int, float, boolean, date, datetime, select, multiselect.
Linking a file to a Type
zorid.type references the Type ID, not a path. The Type registry resolves IDs from .zorid/types/*.ztype and reports conflicts.
Notion-like preservation
If a file removes itszorid.type:
- Field values remain in frontmatter.
- The
Taskfield box disappears. - Fields become raw / ad-hoc metadata.
- Data Views can still query them.
zorid.type: task:
- The
Taskfield box reappears. - Previous field values are reused.
- Select / date / multiselect editors and validation resume.
UI shape
Source
Full Fields & Types spec on GitHub.