7 Levels of headings is quite an odd number and sometimes not enough.
Proposed solution
Suggestion:
10-20 Levels of headings,
the level of heading would not be accessable with multiple # hashtags behind eachother or a number followed by a 1 or 2 hashtags to define the syntax.
Examples:
Heading level 3 (### or 3# or 3##)
Heading level 6 (###### or 6# or 6##)
Why not a third symbol instead of a second hashtag?
Because its easier to type the same symbol twice.
“3#” could be already used syntax for some people wether it has a special function.
This is why i strongly suggest “3##” as syntax.
Optional:
They should use rainbow colors till heading 10, then the font changes to something obviosly different and the color sheme repeats till heading 20.
Rainbow headings is a theme i believe however it should be default. Vanilla obsidian is not a great experience unfortunately.
But this would make Obsidian incompatible with every other markdown editor. Markdown has six levels of headings; Word has nine; you need org-mode to go significantly further; or use an outlined.
I agree with @SomeDude, having discussions about syntax extension in Obsidian community is beneficial at least. We already have %% %% syntax for comments for example. In a sense Obsidian itself started discussion about syntax extension. Markdown files involving %% %% syntax are not rendered correctly in other markdown editors. Question is that how much incompatibilities Obsidian could introduce to other markdown editors before making Obsidian too incompatible with other markdown editors. It is clear that syntax extensions can impress some hearts resulting uplift to Obsidian’s future. In other words resources spent on syntax extensions can later come with positive returns.
It’s not rendered but is readable and doesn’t create an incompatibility. Easy enough to bulk change or remove.
Having too many headings is much more profound, because they’re used for a wide range of other functions.
The usual method with OPML, when there are too many levels to read on import into markdown is to make the extra headings into bullets. To an extent that can be set up to export back again into bullets. But outlines and bullets in markdown don’t work in the same way.
I really don’t see the developers ever implementing more heading levels than the standard, even if they might sometimes introduce a different extension. If you want a very large number of headings, you’d be better off with org (though few editors read it ) or go outliner - Logseq, Roam, Workflowy et al. Or develop a hybrid workflow using markdown files and an outliner. Database apps aren’t limited to any given number of headings but I’m not sure which, if any, might meet a need for more heading levels.
) or go outliner - Logseq, Roam, Workflowy et al. Or develop a hybrid workflow using markdown files and an outliner. Database apps aren’t limited to any given number of headings but I’m not sure which, if any, might meet a need for more heading levels.