3D mind maps: what the third dimension adds

What people mean by a 3D mind map

The phrase covers two different products. One is a scene you fly around, where every node floats in space and you turn the camera to hunt for a single one. The other is a map whose content is divided into layers, and the third dimension shows where those layers sit relative to each other. Canvasola builds the second kind, and the difference matters before you pick a tool.

A floating-node scene is a presentation device. It looks striking in a demo and is slow to work in, because a node in the middle of the scene is small, partly hidden and hard to read. The layered kind keeps every node on a flat plane, so the text stays legible and the depth carries a single piece of information: which layer a node belongs to.

If you are searching for a 3D mind map, the question worth asking is what the depth axis means. A depth axis that encodes nothing is decoration. A depth axis that separates data from product from interaction is a diagram you can argue with. The mind map fundamentals guide covers what a flat map does well, so read that first if the depth is a nice-to-have rather than the point.

• Two products get called a 3D mind map: a scene to fly around, and a layered map in perspective
• Canvasola's depth axis carries layer membership and nothing else
• Every node stays on a flat plane, so labels stay readable
• Ask what the third axis encodes before you compare tools

Depth as a second axis: layers, not floating nodes

In Canvasola the depth axis holds one thing: which layer a node sits on. A map can carry up to eight layers, and each layer gets its own layout on its own plane using the same tree or radial structure you already know. Nothing drifts in space and nothing hides behind a card, so the picture stays legible as the map grows.

These are the same layers the flat view uses. In 2D a tab scopes the map to a single layer, which is what you want while writing. In the stack, those layers spread along the depth axis, and the layer order becomes a sequence you can read, like pages standing on edge.

A cross-link between nodes on different layers is what makes the stack worth opening. Those links are drawn as tubes that sweep through the depth axis, so you watch a connection travel across planes instead of inferring it. The cross links guide covers how to add them and how many one map will hold.

• Depth encodes which layer a node belongs to
• Up to eight layers, each with its own 2D layout
• Cross-layer links are drawn as tubes that arc through depth
• The stack order is the same order as the layer tabs

Seeing the same map in 2D and 3D

Press 3 and the flat map becomes the stack. Press 2 and you are back in the flat editor, scoped to the layer you were last working in. Nothing is copied and nothing is converted: both views read the same nodes, the same links and the same layer assignments, so you can move between them while the thinking is still moving.

That round trip is the practical reason to care about the stack. Most of the writing happens in 2D, where editing is fast, and the 3D view is where you check the structure. The 3D layer stack guide walks through every control, and the layer tabs in the flat view tell you which plane you are in.

Editing in the stack is possible as well. You can add a child to a selected card with Tab, rename it with F2 or Enter, remove it with Delete, and drag cards around their own plane. Some people work faster that way, because they never leave the scene.

• 3 opens the stack, 2 opens the flat view again
• Both views read the same document
• Tab, F2, Enter and Delete edit the selected card
• The stack is for checking, the flat view is for writing

Note: The 3D view needs WebGL. On a machine without hardware acceleration it refuses to open and the app stays in the flat editor, with a message saying why. Nothing in the map is damaged when that happens, and the layer tabs keep working.

Why orbit and explode change what you understand

The camera has four presets: stack, front, side and free. Stack shows the planes as a pile, front looks straight at the first plane, side turns the stack edge-on so the gaps between planes are obvious, and free lets you orbit freely. Choosing side turns a flat list of layers into a picture of depth.

The explode slider pulls the planes apart along the depth axis, from zero, where the stack is compressed, to two, where the gaps are wide. A link that jumps from a data layer to an interaction layer looks different when the planes are far apart, because the distance you can see is the distance in the argument.

Use explode as a reviewing control rather than a picture control. Squeeze the layers together, look for the connections that vanish into the mess, then pull them apart and see which links are doing the work. The faint reference grid on each plane, toggled with G, gives the depth something to sit against.

• Stack, front, side and free are the four camera presets
• Side is the fastest way to read separation between layers
• The explode slider runs from 0 to 2
• G toggles the reference grid on each plane

Where a 3D map beats a flat one

The stack wins when the question is about relationships between groups. Which layer feeds which. Where a decision sits relative to the data it depends on. Whether one group of ideas is isolated from everything else. A flat map answers those questions badly, because it puts everything on one surface and lets distant items sit side by side.

It also wins in a review. A picture of the stack, exported as PNG, shows something a flat map cannot: the shape of the structure, the number of planes, the connections that cross them. For a group that has never seen your map, that single image often explains more than a tour of the flat view.

And it helps you find gaps. When one plane has no links to any other, that plane is disconnected from the argument, and you can see it in seconds from the side camera. The checks worth running first are simple: count the planes, look from the side, and ask whether a picture of the structure beats a page of notes.

• Cross-group relationships show up in a way a flat map hides
• One exported picture can explain the structure of a whole map
• Disconnected planes are obvious from the side view
• Useful in a review where the audience has never seen the map

Where a flat map is still better

Writing is faster in 2D. Adding a node, renaming it, restructuring a branch and fixing a label are all quicker in the flat editor, where the map is scaled to the screen and the keyboard does the work. The stack is for reading structure, and treating it as a writing tool slows you down.

Exporting and printing also favor the flat view. SVG and PNG exports capture what is on screen, so they capture one layer at a time. Markdown and OPML exports carry the whole structure, with a [layer:N] tag on each item, so a layered map round-trips through another tool with its planes intact.

And for a map with one or two layers, the depth axis has little to say. Most mind maps are a single layer, and for those the flat view with the layer tabs is the honest answer. The layers guide covers when splitting a map is worth the trouble.

• Editing, renaming and restructuring are faster in the flat view
• Picture exports capture the layer you are looking at
• Markdown and OPML keep the layer tags
• A one-layer map gains little from depth

What your device needs to run the stack

The 3D view needs WebGL, the browser's hardware-accelerated drawing layer. On a machine or browser where WebGL is missing or switched off, the stack will not open and Canvasola stays in the flat editor with a message explaining why. Everything else about layers, including the tabs and the outline exports, works without it.

The 3D code also loads on first use, so the very first time you open the stack the browser fetches it. After that it is cached, which is what makes the stack available on a train. If you plan to use it offline, open it once while you have a connection first, so the code is cached before you need it.

Older phones, and machines with graphics acceleration turned off in the browser settings, are the usual trouble spots. If the stack will not open on your device, the layers still work: build them in the flat view, use the tabs, and export each layer as a picture when you need one.

Note: There is no fallback renderer behind the stack. The layer tabs in the flat editor and the Markdown and OPML exports are the fallback, and they cover most working needs.

A checklist you can reuse

• You can say in one sentence what the depth axis encodes
• The map uses eight layers or fewer
• The stack was checked from the side camera before the review
• Explode was used to spot the links that jump between planes
• Every node is still readable, which means the content works in 2D too
• The PNG of the 3D view is genuinely the picture you needed
• You know the device has WebGL before you promise a 3D demo

Common mistakes to avoid

• Expecting nodes to float in space. The depth axis in Canvasola carries layer membership, not position in space. A tool that scatters nodes in 3D answers a different question, and you will judge this one against the wrong standard.
• Using the stack as a writing surface. Typing and restructuring are quicker in the flat view. Write in 2D, then open the stack to check the structure, and you will finish the map sooner.
• Reading depth from the front view. The front preset flattens the stack, so the gaps between planes disappear with it. Switch to the side camera whenever the distance between layers is the point.
• Promising 3D to an audience that cannot see it. The stack needs WebGL, and the first load pulls the 3D code over the network. Test the device in advance, or export a PNG from a machine that can render it.
• Treating depth as decoration. If the layers do not mean something, the third axis is noise. Give each layer a job you can name in a few words, and the depth starts to earn its place.

Frequently asked questions

Is a 3D mind map in Canvasola a scene with floating nodes?

No, and that difference is the whole point. Every node in the stack sits on a flat plane belonging to a layer, and the depth axis shows which layer that is. You get a layered map seen in perspective, with cross-layer links drawn as tubes, rather than a scene where you have to hunt for the node you want.

Can I edit nodes while the 3D stack is open?

Yes. Tab adds a child to the selected card, F2 or Enter renames it in place, and Delete removes it, and cards can be dragged around their own plane. For heavier text work, double-click a card and it opens that layer in the flat editor, where typing behaves the way it does everywhere else in the app.

Does the 3D view work offline?

After the first time, yes. The 3D code is fetched the first time you open the stack and cached from then on, so later opens work with no connection. If you plan to use the stack on a train, open it once while you are online, and note that a machine without WebGL never opens it at all.

How many layers does a Canvasola map allow?

Eight layers at most. Each one holds its own nodes, and both the flat layer tabs and the 3D stack work through the same list. The cap is a useful constraint, because a ninth plane usually means the branches need better labels rather than another depth level.

This guide is part of the 3d layer stack collection. For the wider product tour, read the complete Canvasola guide, and keep the keyboard shortcut cheat sheet open while you work.