Tiago Forte's PARA System in Tana
Based on CortexFutura Tools's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Tana templates bundle super tags and live searches into a shareable package that can be installed quickly instead of rebuilt manually.
Briefing
Tana’s new template feature lets users package connected “super tags” and live searches into a single shareable unit—so PARA-style second-brain setups can be installed in minutes instead of rebuilt from scratch. The walkthrough centers on a ready-made PARA template (based on Tiago Forte’s “Building a Second Brain”) and shows both how to install it and how to recreate the structure so others can reuse it.
Installation starts with opening the shared template link. Tana reloads to a template preview screen that lists how many super tags, fields, and search nodes it contains. Adding it to the home node places a pre-configured “welcome” view in the user’s workspace. From there, the setup is largely drag-and-drop: the template is designed so users only need to move the included live searches into their sidebar/home node, after which the system is ready to use.
A key dependency is enabling “semantic field functions” in Tana Labs. Without that setting, the template’s linking logic—how fields connect across areas, goals, projects, and resources—won’t work as intended. Once enabled, the PARA model is implemented through Tana’s connected data objects rather than a traditional folder hierarchy.
The template maps PARA components into Tana super tags and live searches: Areas represent ongoing spheres of activity (e.g., “CortexFutura” as an area), Goals sit inside each area, Projects serve a goal, and Tasks belong to projects. Resources represent topics/themes of ongoing interest (e.g., “Tana” as a resource). Instead of a strict “Archives” super tag, the system uses status-driven behavior: resources and areas have an active/inactive state (“Paris status” in the demo), which determines whether items appear in active live searches.
Live searches are embedded into the structure. For example, a live search can pull all goals connected to a specific area, and another can generate a project dashboard listing active projects linked to that area. The template also uses semantic “instance” and “part of” relationships so that dashboards and filtered views stay consistent as items are added.
Status handling is built into the interface. Projects and tasks include status fields (backlog, in progress, done, dropped, someday), and title expressions plus status icons provide at-a-glance cues. A practical interaction is demonstrated: switching a task’s status to “done” automatically updates the task’s check indicator, while moving it back to “in backlog” clears it.
Finally, the walkthrough explains how to share a custom template with the community. Publishing requires a dedicated published workspace set to read-only, and the template must be created under a node that “owns” every referenced super tag, field, and search node. If items are left as external references, the template won’t function for others. Updates don’t propagate automatically to existing installs, which prevents unexpected breakage when the template author changes something later.
Cornell Notes
The PARA template for Tana packages connected super tags and live searches into a shareable installable unit, letting users set up Areas → Goals → Projects → Tasks and Resources quickly. It relies on semantic field functions in Tana Labs so relationships like “part of” and instance fields can automatically drive dashboards and filtered views. Instead of a traditional Archives folder, the template uses active/inactive status to control what appears in live searches. Sharing a template requires a separate published, read-only workspace and careful ownership: all super tags, fields, and search nodes must live under the template’s shared node to avoid broken external references. Existing installs won’t auto-update, which helps prevent unexpected changes.
What does the PARA template implement inside Tana, and how do the objects relate?
Why is enabling “semantic field functions” in Tana Labs essential for this template?
How does the template handle “Archives” without an explicit archive super tag?
What role do live searches play in the template’s day-to-day usefulness?
How are status indicators implemented for projects and tasks?
What requirements must be met to share a working template with others?
Review Questions
- How do semantic “instance” and “part of” field settings enable the template’s dashboards to stay synchronized across Areas, Goals, and Projects?
- What mechanism replaces a traditional Archives folder in this PARA setup, and how does it affect which items appear in live searches?
- When publishing a template, what does “ownership” under the shared node mean, and why do external references cause failures for other users?
Key Points
- 1
Tana templates bundle super tags and live searches into a shareable package that can be installed quickly instead of rebuilt manually.
- 2
Installing the PARA template requires enabling semantic field functions for fields in Tana Labs; otherwise the relationship logic won’t link correctly.
- 3
The template implements PARA as connected objects: Areas → Goals → Projects → Tasks, with Resources as ongoing topics/themes.
- 4
“Archives” is handled via active/inactive status on areas and resources, controlling whether items appear in active live searches.
- 5
Live searches function as dynamic dashboards, pulling connected items into the sidebar for fast navigation.
- 6
Sharing a template requires a separate published, read-only workspace and strict ownership: all template components must live under the shared node to avoid external-reference breakage.
- 7
Template updates don’t automatically propagate to existing installs, reducing the risk of unexpected changes for users.