Looks nice. However I don't like custom extensions like [[BackLinks]] or ((Block Reference)), because they translate badly to other markdown tools. I like my markdown files to be independent of the applications I use to edit them.
[[BackLinks]] seem to be common in the md-knowledge-base space, less so (()) and {{}}. I'd prefer standard markdown links with support from the editor to insert them faster and add backlinks and stuff like that.
I understand this objection. For me this is an acceptable compromise. I'm using logseg where links to pages [[]] and blocks (()) are noted the same way. In contrast to standard markdown links []() where displayed text and path is separated it fits better in typing flow if there is only the handle of page / tag required in brackets. Furthermore, at least Logseq is rendering those internal links diferently.
Another non-standard-markdown markup which Logseq allows is ^^highlighting text^^. However, this is something I miss at pure markdown.
The compromise is perfected as Logseq allows to remove those special markup for exporting content and using it elsewhere (e.g. as Pandoc input).
Comments
Looks nice. However I don't like custom extensions like [[BackLinks]] or ((Block Reference)), because they translate badly to other markdown tools. I like my markdown files to be independent of the applications I use to edit them.
[[BackLinks]] seem to be common in the md-knowledge-base space, less so (()) and {{}}. I'd prefer standard markdown links with support from the editor to insert them faster and add backlinks and stuff like that.
I understand this objection. For me this is an acceptable compromise. I'm using logseg where links to pages [[]] and blocks (()) are noted the same way. In contrast to standard markdown links []() where displayed text and path is separated it fits better in typing flow if there is only the handle of page / tag required in brackets. Furthermore, at least Logseq is rendering those internal links diferently.
Another non-standard-markdown markup which Logseq allows is ^^highlighting text^^. However, this is something I miss at pure markdown.
The compromise is perfected as Logseq allows to remove those special markup for exporting content and using it elsewhere (e.g. as Pandoc input).
Don't know how MdSilo will handle this.