CynthiaS

This missing functionality exactly my issue.
I thought at first it was the issue captured here> https://ideas.tana.inc/posts/91-long-form-writing-in-tana
but really I just need the simple ability to have multi-line nodes.

It's driving me crazy that I can't write notes and tag an entire "paragraph" (or page).
Here is an example:
I have input from a user study. I wrote the note, but I can't write each separate input point in one giant run-on paragraph which is what Tana wants me to do to treat the information as one "node" of info. In reality, I need separate lines for each point I capture - but I don't want each point to be tagged individually. They make no sense unless they are part of the whole. So I want to create a note (not node) that has my list of input from my user study and treat that entire note as one entity to tag and reference.

I want to find the entire note with the intro paragraph and all the "points" (nodes). They are one whole and are meaningless if separated. But I can't do this with Tana.

Nodes are great and important. But, of course, we need to be able to look at, and act on, a set of nodes (i.e., a page) as one entire unit.

If Tana doesn't support this, then they are letting the backend data structure dictate how users think and use Tana. That would not be good for the long term.

This is exactly what is stopping me from using Tana as my repository.
Thanks for listening!
cheers,
c-

"I just felt the biggest reason why I would like to have an easier way for long form writing, strictly meaning multiline nodes."

This is exactly my issue.

While I would also like formatting of long form text per the OP, this is the most important issue for me.

It's driving me crazy that I can't write notes and tag the entire "paragraph" or "page" or list of nodes. Here is an example:
I have a input from a user study. I wrote the note, but I can't write each separate input point in one giant paragraph. Of course I need separate lines for each point. But, I don't want each input point to be tagged individually. They make no sense unless they are part of the whole.

I want to find the entire note with the intro paragraph and all the "points" (nodes). They are one whole. But I can't do this with Tana.

Nodes are great and important. But, of course, we need to be able to look at, and act on, a set of nodes (i.e., a page) as one entire unit.

If Tana doesn't support this, then they are letting the backend data structure dictate how users think and use Tana. That would not be good for the long term.

This is exactly what is stopping me from using Tana as my repository.
Thanks for listening!
cheers,
c-

This is how I currently save my thoughts on the go. Except I have to hack it by saving info to an Apple app and then later I need to move that info to the correct app. Yikes!

This is needed to make Tana THE app for content on the go.
Thanks!
c-

The content in my Tana KB is only useful if I can get to it whenever I need it. This includes when offline.

I see three distinct uses for offline access...

One distinct problem is needing to get answers from my Tana KB in all circumstances. I really do need this while traveling to places that have little or no internet access. Imagine working while on a plane with no internet, or commuting on a train, or being at a conference with spotty internet access, or a locale with no internet. The list is long...
I think offline read access of our Tana KB is the most important priority.

Second offline usage - I want to capture my data while on the go - and that includes when I'm offline. For me, this could be a specific method of capturing my content while offline. It does not need to include all the bells and whistles of Tana and doesn't require full edit access of my KB.

Finally, the third offline usage scenario is the ability to fully edit my Tana KB while offline. Personally, I do not need that level of offline access. But I can see why it would be a major use case for many people.

Thanks!
c-