I am new to the Obsidian app, but I agree that showing Markdown headers alongside file names could be genuinely helpful. Especially in the Zettelkasten workflows.
Thanks to the former posts I found file-explorer-markdown-titles quite handy, and I modified it a bit to show both MD header (essentially, the first one in the document) aside with filename in the file explorer. And this is a preview (the detected header on the left, while the file name on the right, dimmed & italic).
The plugin is just a straightforward demo now. Since it is just about rendering the title, it will not affect document contents and could work well with other plugins. Open to any kind of comments & suggestions!
Here is the link to this tiny project obsidian-md-title-sidecar. I have not figured out how to upload it to the marketplace, so it could only be downloaded via Github Release and installed manually. I will do it when I got more time😌
I am curious about your suggestion though. If I have proper Zettelkasten IDs then they are already unique right? Can you elaborate please?
For my use-case, I have an existing Zettelkasten that I want to port to Obsidian. My Zettelkasten IDs are of the form YYYY-MM-DD-hhmmss with file names like YYYY-MM-DD-hhmmss.md.
This allows me to easily refer to notes from outside my Zettelkasten system like my TODO list manager, my Bullet Journal etc.
The most difficult part is autocomplete for wikilinks / internal links. Right now I have a simple python autokey (TextExpander like software) script that takes a title as input and spits out:
Note Title [[Zettelkasten ID]]
as output wherever my cursor is at.
I am not sure how big of a system this script can scale to. It would be nice for Obsidian to offer autocomplete wikilinks by searching H1 titles and not just the file names.
I have debated with myself over this, but in the end my requirements for portability stopped me:
I am not sure if the wikilinks alias syntax is portable. Seems like Zettlr doesn’t support them.
I want the source Markdown “look good” / be readable by itself too, in case the software I am using doesn’t have a nice live preview mode (like Obsidian has).
But I am not fully convinced with my own arguments I am kind of new to the networked note taking space, and have already had to switch 3 tools because of various deal breaking issues I encountered with them - and hence my emphasis on portability.
would also be useful if you’ve just arrived from evernote-land via an abalasko yarle conversion, then the option use the first h1 (which yarle adds to the top of the note and contains the evernote note title) is intuitive.
then presumably the ability to easily identify and edit the physical file name. dunno - maybe hover-show or append the filesystem name to the logical note title in file tree.
i personally like this suggestion because the evernote note titles were long-ish and descriptive and i find long and complex filenames visually offensive. b/c the evernote note titles contained a number of illegal characters wrt allowable windows filenames the yarle conversion also created some ugly filenames, in addition to being long.
but also i had an experience in the past with a different filesystem-based personal knowledge-base setup in which a restore from backup after ssd corruption resulted in plenty of headaches because getting a backup back into a (different) windows filesystem in a restore situation contains some surprises for noobs when the backed-up filesystem paths were long. the fact that you can backup your windows filesystem doesn’t mean you can easily restore it. i’d like to keep my obsidian filenames and paths crisp.
Much of the functionality described in this thread now works with plugins like Front Matter Title. However, the one missing piece is the ability to have the link text part of a Markdown URL: [Link Text](some-path.md) automatically updated when the title changes.
I am working on a plugin that supports this functionality, see: Title As Link Text plugin. I would appreciate some help testing it if anyone has time.
Please do not run it on your main Vault without a backup yet! I am new to Obsidian plugins (and Typescript) and expect many bugs.
I will submit it to Obsidian Community Plugins once I have tested it a bit more thoroughly.