Yes, I have been talking about this in several places in the Slack channel in recent months.
For Tana to really retain the power and provide the speed entry-/organizing features of an outliner, this outliner mode needs to be available.
It could be a mode to switch on and off, but the ideal would be to be able to switch it for a particular node, and it would then apply to all the subnodes in that hierarchy.
I need it for several use cases.
The most obvious one is when planning tasks and breaking them down to subtasks. I do this daily. Whenever I "get closer" on a task at the work to be done, I break it down further.
The task is a super tag with various fields. Even if most of them are hidden, it is still cluttering.
A concept of how it could work - functionally - is already visible in the way the editor handles contextual subnodes. (You create it by using Ctrl-Shift down-arrow).
When a contextual subnode has been inserted, you can cycle between showing the fields or not - using Ctrl-down arrow.
(But the use cases are not solved by simply using contextual subnodes all the time. It does not facilitate the automatic populating of fields based on ancestors etc.).
An big reason for me originally taking my task system out of task apps and into an outliner (WorkFlowy / Dynalist / Roam Research before Tana) is because of the speed of entry and (re-)organizing.
You don't have permission to do this.
You're going a bit too fast! Take a break and try again in a moment.
Something went wrong! Please reload the page and try again.
Yes, I have been talking about this in several places in the Slack channel in recent months.
For Tana to really retain the power and provide the speed entry-/organizing features of an outliner, this outliner mode needs to be available.
It could be a mode to switch on and off, but the ideal would be to be able to switch it for a particular node, and it would then apply to all the subnodes in that hierarchy.
I need it for several use cases.
The most obvious one is when planning tasks and breaking them down to subtasks. I do this daily. Whenever I "get closer" on a task at the work to be done, I break it down further.
The task is a super tag with various fields. Even if most of them are hidden, it is still cluttering.
A concept of how it could work - functionally - is already visible in the way the editor handles contextual subnodes. (You create it by using Ctrl-Shift down-arrow).
When a contextual subnode has been inserted, you can cycle between showing the fields or not - using Ctrl-down arrow.
(But the use cases are not solved by simply using contextual subnodes all the time. It does not facilitate the automatic populating of fields based on ancestors etc.).
An big reason for me originally taking my task system out of task apps and into an outliner (WorkFlowy / Dynalist / Roam Research before Tana) is because of the speed of entry and (re-)organizing.