Mindmap File Format
.mindmap files are standard markdown that Nimbalyst renders as an interactive mindmap. You can create and edit them directly -- no special tools needed.
Syntax
Tree structure
| Syntax | Mindmap level |
|---|---|
# Heading |
Root node (exactly one per file) |
## Heading |
Depth 1 branches |
### Heading |
Depth 2 branches |
- List item |
Deeper nodes (indentation = depth) |
- Nested item |
2 spaces per indent level |
Headings define the top 3 levels. Below that, indented list items handle arbitrary nesting.
Notes
Blockquotes immediately after a node become that node's note:
## Branch Name
> This note is attached to "Branch Name".
> It can span multiple lines.
Metadata
Inline {key: value} at the end of a node line:
- Task name {color: green, status: todo, tags: frontend, urgent}
Supported keys:
color: default, red, orange, yellow, green, blue, purple, pinkstatus: none, idea, question, todo, in-progress, donetags: comma-separated listlink: one related workspace document, URL, or tracker item; tracker items use a canonical link such asnimbalyst://NIM-123pinned:truewhen a manual canvas position should survive hybrid layoutx,y: pinned canvas coordinates (written automatically by the editor)
Frontmatter
YAML frontmatter stores the document title:
---
title: My Mindmap
---
Complete example
---
title: Project Plan
layout: balanced
---
# Project Plan
> High-level roadmap for Q2.
## Research {color: blue}
- User interviews {status: done}
- Competitive analysis {status: in-progress}
- Feature comparison
- Pricing analysis
## Design {color: purple}
### Wireframes
- Homepage {status: done}
- Dashboard {tags: priority}
### Prototypes
- Interactive prototype {status: todo}
## Engineering {color: green, link: nimbalyst://NIM-123}
- API design
> RESTful endpoints for the core product.
- Authentication
- Data models
- Frontend
- Component library
- State management
Rules
- Exactly one
#heading (the root node) ##and###for the top levels, then-lists for deeper nesting- 2 spaces per indent level for list items
- Metadata
{...}goes at the end of the node line, not on a separate line - Notes
> ...go on the line(s) immediately after the node they belong to - Blank lines between sections improve readability but are optional
- The file extension is
.mindmap(not.md) - Frontmatter
layoutmay bebalancedorright
