I’m doing some non-critical work in Logseq, where it wouldn’t be detrimental to lose any notes I put into the platform. Additionally, I think the way the DB version handles tags and tag properties is far better than the plaintext version.
Having said that, I want to continue testing the DB version, but I’m not sure which “instance” is going to be updated more frequently as the team builds through updates to the Alpha. Should I use https://logseq-db-demo.pages.dev/ or https://test.logseq.com to be on the latest update?
I thought you had done some custom css to position and style the properties at the top. However turns out it’s all out of the box
At first I thought it’s a bit weird to have the habit checkboxes showing without labels (requiring hovering to know which is which). Though I guess it makes sense as the default for that position (end of block).
I was also a bit confused with what happens when a text property is made to be multi-value. It’s nice that it’s possible to add an arbitrary node hierarchy as a value in a property. But it’s confusing that this behaves differently from other multi-value properties.
Good job with the video btw. The db version is exciting, but it feels a bit too abstract. Seeing real world examples like that is very helpful.