Introducing the Tana Pattern Library

Tana’s Pattern Library makes it possible to import complete workflow “packages”—including Super Tags, their Fields, and related collections—into a personal workspace with a few copy-and-paste steps. Instead of rebuilding a setup field-by-field, users can reference a shared pattern, then clone it into their own graph so it behaves like anything they created themselves. That shift matters because it turns experimentation into a low-risk process: patterns can be renamed, edited, and deleted without breaking other work.

The workflow starts with linking to a shared workspace. By right-clicking a workspace title and choosing “Link to node” (or copying the link), then pasting it into a user’s own workspace, the pattern library content appears as a normal reference. From there, specific patterns—such as a “micro and Nano cycles” setup—can be copied into the user’s graph. The key step is “Clone reference,” which converts the referenced pattern from a dotted-outline reference into actual nodes inside the user’s workspace. Once cloned, the Super Tags and their Fields become usable immediately; the user can run the Super Tag like any other, and can rename the cloned components (e.g., “TPL microcycle” becomes “demo microcycle”) to match personal conventions.

Editing and cleanup are treated as first-class features. If a cloned pattern doesn’t work as expected, the user can delete the node(s) directly from the graph. The transcript demonstrates that deleting the cloned Super Tag nodes removes them from the workspace, enabling rapid iteration. A tradeoff is made explicit: cloned patterns are a “hard copy” at the moment of cloning. They do not automatically update when the original library releases new versions (V2, V3, etc.), so users retain full control over what exists in their graph.

Beyond importing, the transcript also details how to share patterns with others. The approach is to create a new workspace and publish it read-only so anyone with the link can view its contents. Within that workspace, a user can build a workflow template—such as a “journal entry” workflow—by creating Fields (about, how to use it) and attaching the necessary Super Tags. The transcript emphasizes a structural requirement for sharing: the workflow’s Super Tag must be a direct child of the Super Tags field (not merely a reference), which is handled by “bring reference node here” to remove the dotted outline and place the node correctly in the hierarchy.

Finally, sharing can be done at two levels. Users can share the entire published workspace (letting others browse all patterns inside), or share individual patterns by copying a “get link to node,” pasting it into another workspace, and cloning the reference. In the demo, cloning an individual “journal entry” workflow into a personal workspace allows the user to run the Super Tag and generate journal entries using configured Field logic such as “date from ancestor day node” and “entry time.”