I have a use-case where I am using Obsidian to write the content that will be presented via mkdocs which has caused some ‘interesting’ problems due to differences in how they both interpret the files. Tags are one of those areas.
The problem is that mkdocs doesnt have any support whatsoever for hashtags. You cant even search for them in the site. It does however have a plugin which supports them when in this format:
--- tags: - tag1 - tag2 - tagN ---
In messing around, I found that Obsidian kinda sorta understands this because it will suggest these names when typing a hashtag. They however do not show in Obsidian’s tag list or work as a tag search.
I did however find that while hashtags in the YAML frontmatter also dont appear in the tag list, they are searchable. That has lead me to using this less than ideal but workable model:
--- tags: #some_tag_not_shown_in_mkdocs #some_other_tag_not_shown_in_mkdocs - tag1 #tag1 - tag2 #tag2 - tagN #tagN ---
#some_tag_not_shown_in_mkdocs: Ive found that there are times its kinda useful to have tags that are usable only in Obsidian that dont appear in the mkdocs generated page.
Within the YAML frontmatter, at some point would it be possible for Obsidian to fully support:
- hashtags, and
- YAML lists of tags?
This combo would permit a cleaner page render via mkdocs, eliminate duplicate data, and provide full tag support in Obsidian (inc Tag Wrangler which I find immensely helpful).