I suggest that the Obsidian team natively supports Markdoc syntax to enhance the application’s functionality. Although implementing Markdoc support through a plugin seems like a viable solution, native integration avoids potential compatibility or update issues associated with relying on plugins, thereby providing a more stable and consistent experience for all users.
If you are trying to win folks over to your side, I’d include links to what Markdoc is, and why it would be a good core feature.
I did a web search for it, but I reckon most folks won’t.
Yeah, if you don’t explain the value of the request, it’s unlikely to be implemented.
I removed the “editor-legacy” tag since this isn’t about the legacy editor, which was recently removed anyway.
I understand, and I will elaborate on my remarks next time.