We have released a new update to Headings in Tana.
We are looking for feedback and first impressions. Please add any feedback on in the thread below.
This feedback will be considered by the product team for our first round of updates in the coming weeks.
Please note, this is not a place for submitting bugs. If you are encountering a bug, please file a report in app via 'submit a bug' in the bottom left settings menu in your Tana workspace.
8 Comments
Very cool! Just not sure how to toggle headers with the keyboard shortcut? Using "!" for headers doesn't do the same thing as "#" for supertags, as one would expect from the way shortcuts are displayed
! at the beginning of a node should do what you expect. (We don't allow multiple ! for different heading levels).
Ah, I see - it has to be at the beginning of the node
That works :)
Could you please add support for Tana Paste?
So sad. The size difference in the new header vs the normal text is not enough for my eyes to discern. My old CSS TAG for headings was much more effective for my low vision sight. But now I can't use those because it changes the children under the parent in which I used the CSS tag.
Great Job, I love Tana, but as a Research Student, Lacking Latex and Table support is holding a lot of potential back, Keep the hard work.
I understand Headings are always open by default because we should understand a heading's content as actually the heading's PARENT NODE content, right? The heading is only organizing the content. That is why (I think) you chose to always expand them, displaying their contents when you open the parent node.
Being consistent with this, shouldn't the References section of the PARENT NODE consider nodes under headings as if they were already mentioned in the PARENT NODE (and therefore exclude them from the References section)?
I sometimes find that I have a node that is a heading, but elsewhere it is not and retains the heading formatting out of context. I came to ask for a fix, but I also am open to hearing that I'm using the headings wrong. This is usually for nodes with supertags, but I also use headings as a way to organize a node (attaching no supertag, so they only persistently exist in the current context of that node). If that is the way you intend for us to use headings ALWAYS (or at least the intention, if not prescription) that would be helpful to know and experiment with.
And if it is, are headings included as operators in search? For example, I posted this question and if headings can be used in the way I'm imagining, it provides a secret third option that I didn't post in the thread.
Thanks! And feel free to reach out for more context, happy to explain/chat.