A Zotero mind map plugin. Typed, named links between items and notes, organized into named mindmaps and rendered as a knowledge graph.
The documentation here follows Diataxis. Tutorials teach, how-tos solve one task, reference states what exists, and explanation says why the design is what it is.
| You want to | Read |
|---|---|
| Build a first mindmap | Getting started |
| Recover mindmaps that vanished | Plugin data recovery |
| Add a link type of your own | Editing link types |
| Report a bug you hit | Reporting a bug |
| Run the project locally | Development setup |
| Publish a version | Cutting a release |
| Debug a silent failure | Debugging a running Zotero |
| Change how mindmaps are stored | Storage design, then storage reference |
| Add a Zotero notifier observer | Notifiers and the storage queue first, it constrains what an observer may do |
| Change the graph's look | Rendering design |
The user guide covers the mindmap tab, the Mindmaps section, link types, grouping, cross-mindmap links, and what to do when the plugin's data ends up in the trash.
Contributing covers dev setup, the npm scripts, testing against a live Zotero instance, the MCP rig for debugging a running Zotero, and the configuration fields that fail silently when they're wrong.
Internals documents the storage layer, the document schema, graph rendering, and the plugin lifecycle, along with the Zotero constraints that shaped each one.
Version 0.2.0 is published. Download the .xpi from the latest release and install it through Tools, then Plugins, then the gear icon. Getting started covers the steps in order.
Building from source still works and is what you want if you're changing the plugin: see development setup.
One thing worth knowing before you start. The plugin stores its data in a library item called "Zotero Linked Mindmaps (plugin data)". Trash that item and every mindmap in the library disappears until you restore it. Nothing is lost, but it is alarming the first time. How to recover.