Oh… Yeah. You’re correct that MediaWiki-style [] links don’t work or convert to GHPages or an SSG (like 11ty, Hugo, etc…)
I don’t use [] links in Obsidian. I use standard Markdown [text](link) format which works perfectly in Obsidian. And allows me to “lable” the link anything I want instead of whatever the File Name is.
I also have TextExpander quick keys that generate an entire set of FrontMatter Keys and Values at the top of each file. Again, I’m working mostly in VSCode and only use Obsidian for viewing the Graph or backlinks…and with FOAM there’s less round-tripping between VSCode and Obsidian.
For me, I’m really not concerned about the Graph or backlinks when I’m working/writing.
My thinking/process is basically:
- In order to maintain as much open format and interoperability in the future, stick to content and file format standards.
- For the few internal/external links in each document, it’s not that much of an inconvenience (especially with quick keys) to use standard [text](link) syntax. This ensures I can serve any .MD file I have with any SSG and/or use any standard Markdown converter now and in the future. And when I’ve finished the document, I do have to manually at Tags to the Frontmatter “tags” array. Adds 2-3 seconds per tag, but guarantees I’ll have taxonomy connections between files when published through an SSG.
- Placing Frontmatter at the top of each file also guarantees future interoperability, conversion, and hosting via SSG. Using TextExpander makes this super easy and fast.
It’s that old tradeoff of simply changing a few workflow elements (using [text](link) instead of [] for example) to benefit from exponentially more interoperability.