Manage map versions
This feature requires the Team capability tier (the Team or Business ). During the beta, every project is on the free Solo tier, so this feature is locked by default: go to Settings ▸ Billing and request Team access to unlock it.
Create versions of a map to maintain separate documentation structures (for example, v1 and v2 of your product) while sharing the same underlying topics.
How versioning works
A map version duplicates the map's structure (which topics, in what order, with what nesting) but shares the same topics. Editing a topic updates it across all versions. Each version can have its own publication targets with different condition profiles and variable sets.
Map versions share topics, not copy them. When you edit a topic in one version, the change appears in every version that includes that topic. To serve version-specific content within a shared topic, use conditions on content blocks and assign different condition profiles to each version's publication targets.
Anyone can see a map's version list, but creating, renaming, and deleting versions requires the Team plan.
Create a version
Open a map in the editor.
Click the branch icon in the right icon rail to open the Versions panel.
Click New version.
In the Create new version dialog, enter an optional label (for example, "v2.0" or "Q4 2026"). Labels can be up to 100 characters.
Click Create version.
Topicary duplicates the map structure and opens the new version in the editor. The new version gets an auto-incremented version number.
Rename a version
Open the Versions panel.
Click the pencil icon next to any version.
Edit the label inline. Changes save automatically.
If no label is set, versions display as "v1," "v2," and so on. The first map in a version group displays as "Original."
Switch between versions
The Versions panel lists all versions in the group with their item count and target count. Click any version to open it in the editor.
Publish versioned documentation
Each version can have its own publication targets. When you publish multiple versions, readers see a version selector dropdown in the published site header. Selecting a version navigates to the same page slug in that version's site.
The version selector only appears when 2 or more versions of the same map have published targets.
Delete a version
Open the Versions panel.
Click the trash icon next to a non-root version.
Confirm the deletion.
Deleting a version permanently removes its map structure and all associated publication targets, including any published sites tied to those targets. This action cannot be undone. The original (root) version cannot be deleted.
What is shared and what is separate
Shared across versions | Separate for each version |
|---|---|
Topics and their content | Map structure (item order and nesting) |
Components | Publication targets |
Conditions and variables | Version label |
Because topics are shared, an edit to a topic in one version appears in all versions. To serve different content for each version, use conditions on content blocks and assign different condition profiles to each version's publication targets.
Use version labels that match your product's release naming convention (for example, "v2.1", "2026.1", "Enterprise"). Readers see these labels in the version selector dropdown on the published site, so clear labels reduce confusion.
See also
Create and organize a map: Build and structure the maps that versioning applies to
Publish a web site: Publish versioned maps with a version selector dropdown for readers
The topic-map-publication model: Understand how maps and publication targets relate in Topicary's architecture
Conditions versus variables: Use conditions to serve version-specific content within shared topics