Please keep a Standard Markdown Link Syntax ("[descriptive-text"](URL "Title")) for Logseq Pages

Logseq would not lose anything if the [[som-page-name]] pages would be translated, in the back-end (in the markdown files), as [some-page-name]([[some-page-name]]) or, if Logseq would want to be 100% true to Standards, it would be translated to [some-page-name](../ "[[some-page-name]]"), which has the actual URL as the relative path to the file that the page is represented by in the filesystem and, inside the title syntax, the actual Logseq-Page-Name that the App would use to render the Link.

The Logseq user wouldn’t have to notice anything different. They would still type [[some-page-name]] in their in-app experience and everything would work the same as it is now. The only difference is that the backend would be Standard Markdown while Logseq is still being able to deliver features.

However, when the user wants a different text for the Link, he/she would use the Markdown Link sysntax: []() and, after he/she delivers the [text in between square brackets], inside the round brackets he/she would specify the Logseq Page Link [[some-page-name]] and this will not be translated, in the back-end, in the form I previously mentioned but will be kept as is.

So, to summarize:

  1. if user starts typing [[..., the backend will still be a Standard Markdown Link in the form of []() but with repeating the same Page Name as the one in between the square brackets: [some-page-name]([[some-page-name]]);
  2. if user starts with the actual Markdown Link Syntax ([]()), then he/she will deliver the descriptive text in between the square brackets and the [[page-name]] as a link, so the finished link will look like: [some-descriptive-text]([[some-page-name]]);

NOTE: My sincerest suggestion to Logseq is that they go even further and bridge the Logseq world and the Standard Markdown Syntax world by having, in the backend, a Page-Link that looks similar with this:

[descriptive-text OR some-page-name](../relatove-path-to-the-actual-page-file "[[page-name]]")

What would any downside be for this Standard-focused approach? Logseq would recognize the “Title” text “[[some-page-name]]” and render it accordingly in the app, while the markdown file will be standard markdown link in the form of "[descriptive-text](URL "Title")";