Explain the problem as you see it
When defining supertag templates in Tana, currently, users must create a node with child nodes visualizable as Tabs, a common practice in dashboard creation (i.e., setting >Attribute == PARENT).
This method, however, contributes to a problematic 'nesting hell' phenomenon in the existing Tana UI/UX flow. The issue manifests particularly with tags like #day and #person, where opening the node is required to see related tasks, projects, or notes tied to the day or individual.
Why is this a problem for you?
This node-based structure produces an excessive and often frustrating level of nesting in Tana's UX/UI. Directly anchoring nodes to generated node titles (e.g., "Today, Tue, Aug 01") would offer a more intuitive, dashboard-like feel. Such a setup would present the main elements for review immediately upon opening, reducing the need for additional layers of navigation. Regardless of the ability to recall which nodes should be open, anchoring nodes directly under the node title would greatly enhance UX by creating a more natural, entity-specific dashboard.
Suggest a solution
Permit users to establish a "view as" setting on chosen nodes within the supertag template.