DavidJ

Given the reasons of the team to not put too much information into a single node I would appreciate a "long-form" node view. Basically the first node is the "title of the document" for example let's make a short post about an argument.

• Why 8 hours of sleep is important #long-form
  • Intro
  • Argument 1
  • Argument 2
  • Argument 3
  • Conclusion

The parent node containing the title gets a new "long-form" view which can be triggered via shortcut. Each paragraph below is a separate node but the bullets are removed so we get closer to the long-form format. Different types of nodes can then be inserted below such as code and formular one they make an appearance in Tana.

The long-form solution is just a different way to view an assortment of nodes rather than combining all information in a single node. This make referencing of i.e. the arguments somewhere else in Tana easier and allows the nodes to stay small and not harm the performance.

Given that the bullets contain some information about the nodes I would suggest shades of nodes to easily distinguish references etc.

Similar request for dropped state.
https://ideas.tana.inc/posts/101-markdroppedmark-checkbox-state

Table of Contents at the top of the page. So, the reader can easily jump to the specific section.

I would also like to see the integration of the Perplexity API.

Having the option to protect the page by a password would be nice. Having the emails of all my dinner guests publicly available is not the best solution.

I second that a robust Zotero integration is vital for all users in academia.