Related content

Overview

Related content is a handy feature for displaying content that is related to a node, placed adjacent to its main content. Like the reference section, it is meant to be a way to provide easy access to contextually-relevant information without taking up space in the main content area of a node.

They show up as floating boxes to the bottom or to the right of the main content. You can simply plug in a reference as static content, or a search node to make it dynamic.

Say for example, you want to start your day by triaging bugs. In your day tag, you could create a related content area that contains a search for all new #bugs filed on that day. This is a search you might have had as part of your supertag template. Now, it can live in the Related content section instead, removing clutter from the main content of the node.

Basics

• Related content can be configured on any node, and in a supertag so it appears on any tagged node.
• Related content can contain search nodes and references. Plain nodes will not render in Related content.
• Related content can appear either to the right of or on the bottom of the node content. Default is to the right.

Detail

To get to related content setup

On a supertag

Right-click on a tag > Configure tag > Advanced options > Related content

On a node

• Run the command Configure node on the node
• Go to the field Related content where you can set it up and add content

To add content

Related content only accepts search nodes and references. Plain nodes will not be rendered.

Content type: Search nodes

Useful for adding content that changes based on search conditions or is specific to the instance.

To add a search node, use any method:

• slash / -> Search node,
• ? -> Create search node, or
• command line Find nodes

Search nodes that live in the node/supertag config are expanded by default.

—Ideas for configuring your search node:

Note on PARENT: When setting up searches, if you want to reference the instance of the supertag you are on (for example, the #day node), you need to add the searches on the top level in the Related content and use PARENT where you want to use the instance as a field value. GRANDPARENT won't work because that means your search node is nested within a plain node, which won't render in Related content.

• Meetings of the day: This search is on the #day tag. If you're configuring a supertag, use PARENT as a field value to refer to the instance. In the example below, PARENT is used in the Date field to refer to the day node. This will show meetings happening only on that day ("FT" is the workspace node):

• Alternative Reference section: With related content, you can for instance create a custom reference section that displays references to a page, but with the flexibility offered through searches and view options to tailor it to your needs. Use this to search: LINKS TO:: PARENT (doesn't include unlinked mentions). See the image here for a visual example of the search query.
• Other search ideas: Bugs related to a feature, thoughts related to a topic, tasks related to a project

Content type: References

Useful for adding dashboard-type content.

To add a reference, use any method:

• @-mention any reference
• Copy-paste a reference
• Write a plain node → move it to Library (or elsewhere) and leave a reference in its place

References are collapsed by default, even if it is a reference to a search node. If you turn on heading on the reference, it should expand by default.

To change the placement of related content

The easy way

When you have added nodes to the related content section, they appear to the right of the node by default. Hover over the related content, and you'll see a button with three dots/ellipsis appear on the top right corner (1). Click it and go to Prefer area to change its default position (2).

The difficult way

The area configuration is a contextual content node with a system field in it ("Preferred related content area") with options to change the position there.

Other changes

If related content is set up on the supertag level and you change it on the instance level, it will save to the supertag level and appear like this on all instances.

To move related content from one context to another

If you want to move a related content node from one config to another, copy a reference of it to the new location and use the command Bring referenced node here

To remove related content

Hover over the related content, and you'll see a button with three dots/ellipsis appear on the top right corner (1). Click it and select Remove from <tag>/node to remove it (2).

Alternatively, go to the Supertag advanced options/Configure node and delete the nodes in the configuration.

Deep dive into related content

Brage is here to share some tips on cool stuff you can do with related content:

Related content in Tana Core

If you upgraded to Tana Core and synced your calendar, your daily notes will show a related content area called Agenda. This gives you easy access to all the calendar events you have for the day.

If you already had a related content area called Agenda, the existing one will be called "Agenda (old)" with the new one installed underneath. You can choose which one to keep and remove the other.

For more on the calendar sync, see Calendar integration