For your first run, paste the supplied fictional outline into the official editor. Keep the Markdown as the editable source and compare the visual branches with the original notes.
In this guide
Prepare the outline before opening the renderer
Use one project heading, branch headings, and concise bullets. Source IDs help you return to the original notes. The example separates confirmed scope, actions, open questions, and suggestions.
Try the official editor
- Open the official Markmap editor and replace its sample text with project-map-example.md.
- Inspect each branch and its parent. A visual connection groups information; it does not establish a task dependency.
- Edit the Markdown if a branch is too long or wrongly grouped. Keep tentative dates and suggestions explicit.
- Save the reviewed Markdown and keep the source notes beside it.
Choose local tooling when that fits your work
The official CLI accepts Markdown input and creates HTML, with an offline-assets option. Follow its current instructions for your platform. Map rendering needs no AI model; an optional AI organizing step uses your own chosen account.
Fix structure in the source file
If the map is difficult to scan, shorten labels without losing conditions. If a hierarchy looks wrong, inspect headings and indentation. The official FAQ explains heading levels and nested lists.
Use fictional or permitted material in the online editor. Choose a setup your organization permits before processing private project notes.
References
Use it in a task
AI Mind Map Workflow for Project Leads: Organize Meeting Notes
Continue the task
A visual outline becomes more useful when its structure serves a real planning or presentation decision.