I wrote an email to the Readwise developers. Here is part of it:
Right now I use the Readwise Community Plugin from obsidian. This works because I have followed these instructions for configuring Logseq and Obsidian to work together: Making Obsidian play nice with Logseq The Readwise community plugin also lets you modify the template, making the export work a bit better with Logseq, but I wanted even more customization so I went to the Readwise *beta) markdown exporter and tried editing things there, thinking that this would allow me more control. Unfortunately, I was only able to have limited success, prompting this email.
The big issue is that Logseq is an outliner, like Roam, but uses plain text files, like Obsidian. This means that the plain text files need to be formatted in a particular way. Each line should start with a - and rather than using markdown headers ###, it is best to indent the next line with four spaces. Unfortunately, it is not possible to edit this aspect of markdown export files in Readwise. The Obsidian Community Plugin is a bit better, but it has other limitations. For instance, I wanted to adjust the file name to conform to the Logseq page hierarchy structure. Logseq doesn’t use folders, but instead uses periods in page titles. I want pages to be something like this [[readwise/book/book title]] which would require a file named “readwise.book.book title.md” This is possible in the standard download, but not in the Obsidian plugin.
(Note that right now I cannot get “readwise.book.book title.md” to import as [[readwise/book/book title]] but I think that might be a bug…)