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

Marvin Baumann

Joined Nov 3, 2023 Last seen Jan 5, 2024
Posts 5 Comments 3

⁨Marvin Baumann⁩'s Posts

Newest Top
Newest Top
Marvin Baumann Marvin Baumann Jan 5, 2024

New Setting: Tight Margins around nodes/fields to enable more content per space

Actions

Explain the problem as you see it

Tana sets nice margins left and right of nodes and right of field names, which look "clean" but are not strictly necessary and take up space. Also they lead to line breaks earlier than strictly necessary, see second picture where the field values would easily have fitted in a single line still, but because of these enforced margins the line breaks and vertical content volume is cut in half.

image.png
image.png

Why is this a problem for you?

The more we multitask in tana, to quickly jump between different views and locations of the knowledge graph (which might be connect in our minds but tana isn't as far yet in UX design to show it the way our brains do), the more we'd like to maximize what we can view in the windows. Some users might prefer less margins or actually find them cleaner to enable them to take up more content in a single monitor.

Suggest a solution

Add a new setting: Normal, Tight and Extremly Tight margins.

0 ⁨0⁩ ⁨comments⁩
Marvin Baumann Marvin Baumann Jan 3, 2024

Collapsing of collapsed node should collapse parent-node

Actions

Explain the problem as you see it

When viewing a list of lists, I usually "expand all" children of a certain node, read the children and their children, and in the end I want to collapse it all again, to remove visual clutter and get to the next parent node which I want to expand all, read, collapse all.

Currently for this I have to scroll up all the way to the expanded parent node and collapse it.

Why is this a problem for you?

Friction, takes time, unnecessary because fixable via this solution.

Suggest a solution

Executing command "Collapse All" on an already collapsed node (in this case a child node of the parent node I want to re-collapse) should collapse the parent node instead of doing nothing as is currently the case.

0 ⁨0⁩ ⁨comments⁩
Marvin Baumann Marvin Baumann Dec 29, 2023

View Tana in Firefox Sidebar

Actions

Explain the problem as you see it

I use firefox and when reading an article it would be great to pull up the firefox sidebar (which is capable of housing extensions) and have my daily node there and just paste and supertag the content there.

Why is this a problem for you?

It's not immersive enough to go back and forth between applications or tabs.

Suggest a solution

Add at the very least the ability to embed the tana daily node in an extension (currently blocked from embedding) so that I can hack something for myself, but optimally publish a simple addon to the firefox extension store.

1 ⁨1⁩ ⁨comment⁩
Marvin Baumann Marvin Baumann Dec 11, 2023

Quick Add from anywhere on macOS

Actions

Explain the problem as you see it

On macOS I am used to the cmd+space shortcut for spotlight (or I'm using Alfred), which helps me get information, data or jump somewhere, from where ever I am currently.

Tana's quick add feature is great, but only accessible inside tana.

Why is this a problem for you?

A global quick add would be great to further reduce context switching.

Suggest a solution

Some global shortcut that brings up a single line, similar to spotlight on mac, where I can add a single node (to my today node let's say), like:

  • call Alex later #todo[supertag fields: #person:Alex]

This could be done using the mac app, such that the workspace context is immediately available as long as tana app is open somewhere.

6 ⁨6⁩ ⁨comments⁩
Marvin Baumann Marvin Baumann Nov 3, 2023

Improve navigation speed: When cmd+. into a node, move cursor to first child

Actions

Explain the problem as you see it

With focus/cursor inline on some node, cmd+. let's me open that node up as a full page (or "zoom in"). If I want to keep zooming, I now have to use the arrows to move downwards, skipping subtitle and view options, to the children of the node.

Why is this a problem for you?

This is unnecessarily cumbersome.

If I zoom into a node, what are the odds I want to edit the "title" or node itself, rather than work on the children or keep zooming into some child?

Suggest a solution

It makes more sense to me, to have to focus on the first child-node after cmd+. which then allows to navigate to some child-node via arrows and the keep zooming with cmd+.

With a couple of cmd+, I can zoom back out, no need for change here.

0 ⁨0⁩ ⁨comments⁩