Skip to main content
tana
Product Company Community App Get early access
Community
Search
Log In
Log In Sign Up
Guilherme Costa

Guilherme Costa

Joined Mar 13, 2023 Last seen May 22, 2025
Posts 10 Comments 15

⁨Guilherme Costa⁩'s Posts

Newest Top
Newest Top
Guilherme Costa Guilherme Costa Apr 18, 2024

Display options for "Tabs" and "Side Menu" views

Actions

Explain the problem as you see it

Sometimes I like to have a search node in Tabs/Side Menu view, so the results are more easily accessed (when I'm more interested in the insides of the result nodes than only the nodes itself).

For instance, this is useful for a "related meetings" live search inside a project supertag. I have each meeting showing up as a button in the side menu, so it's easily clickable to expand.

In these situations, I usually would like to tweak what the menu uses as a Display title (for instance, in these cases, I'd like the date to appear there in the title - I wouldn't want the date to appear next to a meeting everywhere, just in this view).

Why is this a problem for you?

Currently, we have either the option to set a Title Expression for everywhere or to use Display options to customize specific nodes's children appearance - except when the node is in Side Menu/Tabs view. No display option there.

Suggest a solution

Add display options for Side Menu/Tab views.

1 ⁨1⁩ ⁨comment⁩
Guilherme Costa Guilherme Costa Dec 9, 2023

Contextual commands

Actions

Explain the problem as you see it

Currently commands are hard-attached to nodes according to their current state/field values. There is no way to display a command button just in some views.

Why is this a problem for you?

There are views I build to process specific tasks (like chosing prospects I want to approach this week - and creating a task to do that), but each command I add to facilitate a task like this will hang onto the node wherever I see it - even out of the "weekly planning context".

Suggest a solution

It would be awesome if we could have a "node filter" for commands with rules about where the node is being referenced in that specific view, or what is the current zoomed-in node, etc (context-related criteria)

1 ⁨1⁩ ⁨comment⁩
Guilherme Costa Guilherme Costa Oct 19, 2023

Initialize fields based on context (where it's being referenced - zoomed-in page)

Actions

Explain the problem as you see it

Say you're on a class/meeting and you have a node zoomed-in to register what you're learning.

But what you're learning is related to a topic for which you have a node already in your library. So you reference that in the class/meeting node, expand it and start adding notes there.

Then you tag what you wrote as "#to revisit". You would probably want the fields of that node to be initialized with content from the class/meeting you're in, not only with content from the parent topic itself.

Why is this a problem for you?

This is a workflow I go through constantly, and would like it to be more fluid. Currently it's all solved by writing the fields manually, but we all know how that breaks the flow.

Suggest a solution

Add an option to initialize a field with content from the context (the currently zoomed-in page).

(While we're at it, why don't allow us to enable and prioritized the multiple initialization methods? - I know, I know, I'm just being lazy avoiding to write another idea page)

1 ⁨1⁩ ⁨comment⁩
Guilherme Costa Guilherme Costa Sep 22, 2023

Shortcut to expand the "reference counter" panel

Actions

Explain the problem as you see it

When we are building "knowledge nodes", we have at least two conceptual routes:
(1) open up the node and add children directly to it, or
(2) link related nodes to the "knowledge node" and leverage the "references" counter / section

(you can also have a mix, where after linking you go and write/curate the node's children)

when navigating through a list of knowledge nodes, it's useful to see the "full marker node" as a way to see there is more content if you expand the node. AND it's useful to see the reference counter as an indicator there is more content in the "reference section". BUT there isn't a keyboard shortcut to quicly expand the reference panel, you have to click the counter (or zoom in on the node).

Why is this a problem for you?

When navigating, keyboard shortcuts become second nature and allow you enter your flow.

Suggest a solution

A Command Line to "expand reference section" equivalent to clicking the reference counter in the node

0 ⁨0⁩ ⁨comments⁩
Guilherme Costa Guilherme Costa Sep 6, 2023

When using alias, show the original node's name as a tooltip

Actions

Explain the problem as you see it

Sometimes I use aliases to link a subjacent idea to a text, "below" a relevant word. But that word itself is not the link's name (it's just the alias), so when I'm reading again, some other time in the future, I often don't know what that link is about - a quick visual cue would be nice.

Why is this a problem for you?

Not a problem, just something to improve the flow.

Suggest a solution

It would be nice to see where the link will take me when just scanning through the text, hovering the link with the mouse and getting a tooltip with the node's "real" name.

0 ⁨0⁩ ⁨comments⁩
Guilherme Costa Guilherme Costa Aug 25, 2023

Set field as a live search

Actions

Explain the problem as you see it

I like to have live searches in attached to super tags to leverage the "PARENT" feature and quickly find related nodes.

I don't like the space search nodes take in my tagged content, so I usually hide them inside hidden fields.

But when I want to use them, I have to click two times: once in the field to be shown and then once to expand the search node.

Why is this a problem for you?

Too many clicks break my flow.

Suggest a solution

Allow us to create a live search as a field. This way, when you click to show the field, the live search expands immediatelly

0 ⁨0⁩ ⁨comments⁩
Guilherme Costa Guilherme Costa Aug 21, 2023

Archived nodes

Actions

Explain the problem as you see it

As you input information in Tana, your life goes through changes that diminish the importance of some of the dated content (like old projects, people from your old work, etc).

But whenever you want to fill in an instance field or search for nodes from a specific supertag, all your content gets surfaced (unless you create a specific way to remove unwanted content).

Why is this a problem for you?

I like the simplicity of instance fields (for example), but the only way to get rid of dated content is to untag the nodes or build your option field with search nodes.

Suggest a solution

We could have a configuration for nodes to mark them as "archived". By default, archived nodes wouldn't show up in searches, unless you explicitly search for them.

0 ⁨0⁩ ⁨comments⁩
Guilherme Costa Guilherme Costa Aug 15, 2023

Shortcut to toggle "allow content" from another workspace

Actions

Explain the problem as you see it

A large alternate workspace can make mentions take longer, so I usually keep workspace separate ("allow content" toggled off).

But sometimes I actively want to mention content from the other workspace.

Why is this a problem for you?

When I want to mention content from another workspace with the toggle "allow content" turned off, I have to break my flow, leave the page to find the unique spot where this toggle is located, activate it and come back. Then head there again to turn it off (so it doesn't slow down all my other frequent mentioning activities).

Suggest a solution

Hard way: make the mentions very fast no matter how many nodes you have in your graph

Workaround: create a command that we can activate with a custom shorcut to toggle "allow content" on/off easily

0 ⁨0⁩ ⁨comments⁩
Guilherme Costa Guilherme Costa May 10, 2023

Command to "send all" items in the view group to Daily node

Actions

Explain the problem as you see it

Daily, I have a routine when I sift through my tasks for the week, make sure I set the "When" field for all the ones I want to tackle today with the right value (eg Wednesday) and send them to my Daily node.

Why is this a problem for you?

Most of the time, I have several tasks in the view, and selecting them to operate a shortcut is not an easy task. As the screen starts to scroll, Tana loses the selection. It's not fluid.

Suggest a solution

Since I'm using a Cards view Grouped by When, I could make this field a instance of a tag #weekday and use a command for the tag "Remind me today". But the issue is there is no command that I would click on the Cards view that would run with all nodes in the view as context.

0 ⁨0⁩ ⁨comments⁩
Guilherme Costa Guilherme Costa Apr 3, 2023

"Next day"/"Previous day" command in the palette

Actions

Explain the problem as you see it

I'd like to have ability to navigate mouse-free through different day nodes.

Why is this a problem for you?

When trying to get "in the flow", navigation through the app should be second nature and having to let go from keyboard to reach the mouse disrupts that.

Suggest a solution

Add commands for "next day" and "previous day" in the command palette

0 ⁨0⁩ ⁨comments⁩