However, every line in the frontmatter is now a page?
That’s odd; and annoying, as now all pages have a connection to several pages:
id
old_title (I modifies the script to preserve the old titles)
desc
updated
created
traitIds
Logseq thinks that all of those are pages.
Fixing Links
How can I port the Dendron-specific link syntax?
It supports a way off linking to a specific part of other pages, anywhere in the text.
How can I replicate this in Logseq?
Porting Jourals
Logseq is focused on daily journals, as is Dendron.
How can I port the “special” pages to be “special” journal pages in Logseq too?
Any help is off course always appreciated,
Friendly greetings,
Tanja
If I use a named Dendron link like this: [[yesterday|2024-02-25]], I need to convert it like so: [yesterday]([[2024-02-25]])
It thinks every line in frontmatter is a page title
Dendron has note references, which ca anchor to any part of the page by inserting spacial anchors
Solutions
I used VS Code to find & replace:
From \[\[(.+?)\|(.+?)\]\] to [$1]([[$2]]) to port the named Dendron links
From (---\nid: (.|\n)+?---\n) to <!--\n$1-->\n\n to comment out the frontmatter
Unsolved problems
The syntax for block references in Logseq is ((65dbe6ca-f417-45d4-8a0e-3c4e66e9e053)) where the UUID between the braces is the UUID of the logseq block.
For now, I’ll simply discard the special Dendron anchors:
Workaround for problem 3
I once again used VS code to search & replace:
From \^[a-z0-9]{12}$ (note the leading space before the backslash, it isn’t rendered) to “” (empty string) to get rid of the special Dendron anchors within the contnet
From #\^[a-z0-9]{12}(:#\^[a-z0-9]{12})? to “” (empty string) to remove the special Dendron anchors from the links
Note that this is a lossy conversion, as I do not know a way of calculating the UUID a block would get in Logseq to put it between double braces: ((uuid-unknown))