I write notes in Logseq, which uses a block structure and supports links and backlinks between notes.

Logseq

The compromise here is to create a public post with my daily journal note in Logseq, and when I find I have some thoughts, put them in that post and publish it on my website directly.

it also requires using my fork of Logseq

Uses existing block hierarchy structure already core to Logseq

Logseq has the goal to build a world knowledge graph

These notes are written in Logseq and published using my custom built system for converting Logseq notes to a Hugo website. It’s an experimental system and it has some bugs. But it’s a good space to publish notes exactly the way I write them locally on my system, and experiment with Building a knowledge graph in Logseq.

LATER fix current need to wait for Logseq to reindex before Logseq Export works

This has some similarities to the already richly supported properties in Logseq. I would suggest that making it possible to create rich relationships in line in one’s writing makes a huge difference (when I tried to use properties to do this, I ended up writing a lot of my notes in the properties, making my notes look more like a database table than an outliner or writing tool). I’m happy to discuss this more as I think the difference between this proposed functionality and properties is a subtle but important one.

Finally finishing bringing over my old Obsidian posts over to Logseq. The formatting is still funky, and there’s a fair amount of duplication. But it feels good to have everything in one place now. I think I’ll be able to slowly clean this up.

I suggest continuing to use the existing simple syntax convention for relationships to add any grammar. This feels more in line with the outliner DNA of Logseq, as it uses the block hierarchies to encode information, and keeps everything visible in the markdown (rather than in an extra layer of data that only exists within the plugin).

I extract the public pages and blocks from Logseq and publish them using hugo. For more details on how this flow works, you can read about how I publish this website.

Some nice things this system currently supports and brings over from Logseq

In reality, the Logseq/Publish interface is suboptimal, and requires more work (see https://notes.denizay.org)

Logseq’s own json export doesn’t have enough information, so I have to essentially copy the whole edn database and convert that to json

Logseq has a stated goal to build a World Knowledge Graph. Here’s what I think they should build:

I’m not sure how Logseq is planning to build their stated World Knowledge Graph, but this seems like a reasonable way to begin letting users add structure to their personal knowledge graphs that could eventually be integrated with other knowledge graphs.