Can I create aliases in Tana Outliner?

Yes. In Tana Outliner when you create an inline reference, you can change what is written and still retain the link. Click the inline reference and a toolbar will pop up that allows you to set the alias.

How do I delete nodes?

It depends what you are deleting, but almost always the cleanest way to delete nodes is using "hard delete" which clears the entire node at once. You can hard delete using the following methods:

Keyboard: Cmd/Ctrl+Shift+Backspace
Mouse: Right-click the node icon, then select Delete

If you delete a node, it goes to the trash. If you delete a node that is referenced one or more times in the graph, the node goes to the trash and the references will have a little trash icon next to them. If you want the node and all references deleted, use the command "Hard delete including references."

If deleting the node was a mistake, you can click on the trash icon and resurrect the node through one of the references. If you delete a reference, it goes to the trash and the node it referred to and other references will still exist and not be trashed.

How do I get the permalink to a node?

Bookmarking the URL in your browser of the form https://app.tana.inc?wsid=XXX (note the wsid) will break as it is a temporary ID for your window state.

To grab the permalink to a node, use one of the following ways:

Right-clicking on a node, then "Copy link"
Using the options menu on the node, then "Copy link"
Running the command "Copy link"

The link to a node never changes. They are URLs of the format https://app.tana.inc?nodeid=XXX (note the nodeid).

How do I remove the strikethrough on a node?

It is likely the legacy implementation of the checkbox node styling. Cycle through the Cmd/Ctrl+Enter checkbox states to see if that removes it.

Why are line breaks not supported?

Tana Outliner's speed is reliant on each node being a small packet of information. Larger nodes are slower to edit, slower to index, slower to update, and so on.

Line breaks, also known as multiline editing, would encourage longer entries of information, and would break many other situations where the contents of a node needs to be rendered as one line, such as inline references, option values, and title expressions just to name a few.

We do recognize that some want to store small pieces of information under one node, like a poem or quote. We are continuing to do research to explore ways to solve this, and also to solve for other issues related to long-form writing.

Owner vs Parent of a node

The Owner is the node's home (where it was created). A node has only one owner, but can have many parents.

PARENT/GRANDPARENT search operators are used to refer to one and two levels up in the outline, respectively.

How can I merge nodes, fields, or supertags?

Use the command "Merge node". It also works on references, meaning it will merge the nodes referenced to and all references will be updated accordingly.

To merge nodes: Select nodes, then run the command.

To merge fields: Get the field definitions in one place (copy/paste), select them and run the command.

To merge supertags: Get the supertag definitions in one place (copy/paste or @-mention), select them and run the command.

How to set up Unsplash banners on daily notes?

It is currently possible to plug in your own Unsplash API key which gives you access to their images for the banners of your daily notes page.

Note: This is an experimental feature; it might change in the future.

Convert text dates to Tana Outliner dates

Typically, to insert a date into a node, type @ followed by the date expression: today, tomorrow, friday, last monday. Tana Outliner understands natural language for dates, so you can say "in two weeks" and the app will understand.

If you want to convert text to a Tana Outliner date object:

Select text that contains the date
Press the @ key
Select desired option

Two Agendas on daily node, how to fix?

This can happen if you go through the calendar sync setup a second time. You can remove the extra/old one by clicking the ellipsis menu on the Related content section you want to remove, then selecting "Remove from #day".

Move node to Library when supertag is used

Goal: To move all nodes to a single place when they get tagged. This is useful if you want nodes of a certain type to live in a place that makes sense for breadcrumb navigation.

Instructions: For this example, we're going to build a command that moves all tagged nodes to the Library.

Build the command:

Create a new command called "Move to Library"
Add the command "Move node"
In the parameter "Move node target", pick the Library from the dropdown. There are other locations to choose from as well, and you can insert a reference to any node you want as the target
Add parameter "Remove references after moving node" and give it your desired setting. Most would want it unchecked so it leaves a reference of the node in the original location
Add parameter "Move original node" and check it. This ensures that even when you use the Add tag action on a reference, it moves the original node to the desired location and not the reference
Add the command to the config of the supertag in question. Go to AI and Commands, then "On added", and add a reference to the command here

Testing the command:

If used on a node, it should immediately send the original to the specified location and leave a reference behind
If used on a reference, it should send the original, wherever it is, to the specified location

Receive notification when someone uses a supertag

Goal: Get notified when a specific supertag has been added to a node. For example, you created a #feedback supertag to collect feedback from your team, and you want to receive a notification when someone applies the tag.

Instructions:

Build the command:

Create a new command called "Notify me"
Add the command "Run a command line command"
In the parameter "Commands", write Notify @[your Tana Outliner account email]. Example: Notify @fei@tana.inc
Go to the supertag config you want to be notified on, to the section "Trigger commands on events", and add a reference to the command to the "On added" section

Testing:

Test the command by adding the supertag. You should get a notification that a notification has been sent, and see a blue dot appear in your notifications. Clicking it shows you which node you were notified on.