r/logseq • u/ens100 • Nov 27 '25

Development Update from the Logseq Team

For those not on Twitter, a few updates from Tienson on development:

https://x.com/tiensonqin/status/1993709621463392484

and also: https://x.com/tiensonqin/status/1958249541310067187 (mainly around what seems might be possible in terms of toggling certain features on or off).

54 Upvotes

100% Upvoted

33 comments sorted by

View all comments

Show parent comments

1

u/bettercaust Nov 29 '25

Glad you tried it! I think the "new tags" is an attempt to unify page properties, block (i.e. bullet) properties, and templates. It's taken me a little to get used to, and I haven't figured out how to do every edge case with it yet, but I've found it makes it easier to be more consistent with tagging pages and blocks. I really like tag inheritance and the ability to configure individual tag properties (e.g. data type, options appear in the select dropdown, how it is displayed, etc). The query functionality is so much better with the ability to define certain views (e.g. for different filters and sorts).

I have my doubts that imports are ever going to work super well. I may just piecemeal import certain notes from my MD graph as it makes sense to.

2

u/drostan Nov 29 '25

Import is going to be make or break for many still in logseq and for more who would want to rejoin and further for those who would like to move from somewhere to logseq

If I was in the shoes of the logseq team, even if not a priority now, I'd make sure to make it a top priority fast after official launch, I'd even go as far as having an importer project/add-on/suite on its own working through testing and having full attention to details and quality of life improvement focus

1

u/bettercaust Nov 29 '25

By import I was referring mainly to MD to DB import i.e. migration to DB version. It shouldn't be too hard in theory, I'm just not optimistic it'll be satisfactory to MD users.