Also not OP, but personally I have a few gripes with Logseq:
- No export to PDF. There's a community plugin, but it's not great. The workaround is to export to HTML and print to PDF, but there's no real iOS option there.
- Managing images and other attachments are a mess. Using the "upload an asset" method gives it a random filename that if the app fails to save the page correctly, you either dig through the folder structure to find the random file name to link manually or you re-"upload an asset" creating a duplicate with a new random name. This could be alleviated if it was more stable or with a file picker with thumbnails to find previously "uploaded" files
- Pages fail to save correctly more than I'd like. I have no idea what the cause is, but it happens frequently on every platform I've tried.
- Page title changes don't propagate correctly sometimes, causing orphaned pages where it's a coin flip whether the page with the older title holds the content or the new one, leaving the other empty.
- Each page needs a unique title. I like how Notion allows multiple pages with the same title and are organized based on which parent page they're embedded or created in. I imagine Notion randomizes the actual file name similar to how Logseq already does for "uploaded" assets, so this could be alleviated if Logseq did the same. It could potentially alleviate the previously mentioned issue and it seems to me like the most logical method of handling this particular type of non-directory organizational structure.
- Their E2EE sync service is not yet ready, so no real mobile sync outside of iCloud (I use DropBox).
- Their documentation is terrible. There's tons of undocumented features, like admonitions, and the existing documentation is horribly structured, which is ironic since the documentation uses Logseq itself and the whole point of the app is to structure content.
----
Side note, since we're on the topic of personal knowledge bases and note taking, my personal dream app is Obsidian with Asciidoc support instead of Markdown. A lot of the extra features they add to markdown are part of the Asciidoc standard, like admonitions and document-to-document cross-references, it would potentially make the backend easier and the content more portable with page attributes like specifying an attachment directory, and some features are simply more flexible/powerful like tables.
I still use AsciiDoc to create PDF documents that require more flexibility, like table spans and nested ordered lists (Obsidian's markdown uses just 1,2,... instead of changing to e.g., a,b,... for a nested level). My current workflow is typing it up in VS Code, converting to DocBook with asciidoctor, then converting that to a LaTeX PDF using pandoc. The result is a professional, academic-like PDF, but the workflow is a bit of a hassle and I'd prefer to do all of my document typing in Obsidian since it's so nice to use.
If I had more free time outside of my CS master's program and thesis work, I'd learn JS/TS to attempt to create a community extension that added AsciiDoc support to it and support for exporting to HTML and DocBook (and basic PDF since I'm pretty sure Obsidian uses an HTML-based PDF export anyway because CSS themes affect the look of the export), even if I still needed to use pandoc to convert to a more professional LaTeX PDF. I'm sure the VS Code AsciiDoc extension as reference and asciidoctor.js could get one pretty far.
Sorry for the rant. I've just been itching for a AsciiDoc-based note-taking/PKB for a long time.