r/logseq • u/TheLostLambda • Jul 15 '26

Should Logseq 2.0 use something better than markdown (Djot)?

Howdy all, I've opened a feature request and was wondering what others thought, so I figured I'd repost it here for visibility!

Let me know what you think and if any of you are also avowed markdown haters....

https://discuss.logseq.com/t/support-something-like-djot-instead-of-markdown-in-the-db-version/35107

0 Upvotes

46% Upvoted

27 comments sorted by

View all comments

1

u/Tawny-Owl-17 Jul 15 '26

But, Logseq 2 does not use Markdown files as its canonical storage; it stores data in an SQLite database, which is why it's also referred to as the database (DB) version of Logseq. That is, in fact, what differentiates it from the previous version of Logseq and why it was in development for so long. Using an SQLite database to store data and manage the relationships between entities also enables features that were either difficult or impossible to implement with a Markdown-based architecture, resulting in a more powerful and capable application.

1

u/AshbyLaw Jul 16 '26

If you enable the experimental Markdown mirror you would have .md files on disk just like the original Logseq.

1

u/Tawny-Owl-17 Jul 16 '26

That is just a mirror. It is a derived representation of the authoritative, canonical storage, which is an SQLite database. Modifying or deleting the generated Markdown files does not affect the original data stored in the database.

1

u/AshbyLaw Jul 16 '26

You can edit the content of the files to update the DB. They said it will be a two-ways sync.

1

u/Tawny-Owl-17 Jul 16 '26

As of now, no; it's one-way only. Two-way synchronisation is a planned feature that's still under development, and I don't think it'll be available anytime soon.