Explain the problem as you see it
Today there is no way to format text beyond bold, underline etc.
A simple ability to create headings - h1 h2 h3 would be welcome.
Why is this a problem for you?
I would like to improve the formatting and visual appeal of my notes as well as to make them easier to browse at a glance
Suggest a solution
Ability to create heading stills from the command menu (ctrl k) and keyboard shortcuts
6 Comments
I don’t mind the basic presentation of my notes. In fact this is the first tool where I have not wanted to apply formatting.
However, I want to improve the presentation of my exports and so I would like to see markdown support implemented so that when I export to HTML the basic formatting of the structure of the document is already there.
The outline structure also needs style and readability.
i miss the heading structure too.
I definitely support adding the concept of a "heading" as a special type of node. I don't think it is necessary to distinguish different types of heading (title, subtitle, h1, h2, h3, subheading, sub-subheading, etc.) as that would be determined by indent level and which node was currently top-level in the particular view.
I'm also in favor of formatting, but h1, h2, h3 are not formatting tag but structure tag, and the hierarchical structure is already given by the outliner format. If i have a cascade of 3 nodes, the first one can be displayed as h1, second h2, third h3... but if i zoom on the second node it becomes the new h1 on that view.
It might be useful to semantically mark a node as serving as a header, but leave to the outliner the choice on how to render or calculate that level header from the content. It also means that the body of a header becomes a sub-node of the header (and collapsable from the header) and not simply a node under as it would totally loose that semantic.
+1 for Markdown support. It's nearly ubiquitous in web apps. I'm pretty sure it's Obsidian, that solved a similar need, by referencing a new version of CodeMirror* that delivered Inline Markdown rendering (as opposed to rendering when you leave the node.)