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.
You don't have permission to do this.
You're going a bit too fast! Take a break and try again in a moment.
Something went wrong! Please reload the page and try again.
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.