Nick video messaged me with a very helpful piece explaining the semantics of tags in Tana, and how this differs significantly from tags many of us have been used to in other PKMs and note-creating systems. My familiarity is mainly in Bear and Obsidian, both of which support layered #tags/subtags . By contrast I am understanding that Tana has re-imagined tagging outside the categories and frameworks — one of the most common is Tago Forte's PARA for Projects, Areas, Resources and Archive. This may be redundant in Tana, where shards of information can be allowed to be much more free-floating. Personally, I like to retain a little bit of structure. I'm not really an 'architect' type but there are times when you need to know where to look for the tag that will bring up the query! The hurdle for me now is just working on the 'Configure' screen which present two further layers of fields and values. I'm getting this bit by bit through trial and error, but I think it would be really helpful to have a short written + video resource to walk one through it. This isn't covered anywhere that I can find (noty everyone can afford a course). Maybe when I am a bit more expert I'll have a go at it but I think there are people in the Tana Community who would do it better!

I want to know what makes you ❤️ Tana, and especially what makes you 🤬 sometimes. Santi and I like Tana, but we didn't build it. So let the spice flow!! ;)

In today's twitter spaces @Nick Silhacek and I talked about Tana for long form writing. In Tana's features request, my request for long-from writing is in the top 3 here 👈 Tana already added the ability to create headings, which is definitely a step in the right direction. Would love to hear your take on this, and if this is important for your specific use case or not really?

Hi, I'm Ian Greig and I'm a writer in the UK. I discovered Tana largely through reading Ev Chapman's posts on Medium. She talks a lot about processing ideas that then morph into writing, and that piqued my interest — and she is a Tana user and coach with some good material. That has got me on a learning process withTana although for my main repository I rely on Obsidian with the help of Dataview. As many people know, Obsidian is powerful, reliable, flexible and a good writing environment but the weakness is that it isn't great for capture. It seems to me that Tana is a good fit with that need and worth the effort of another learning curve