The right side however has a built in "Contents" page - which tells you what it is for - only as far as I know one has to fill it out oneselves.
That said, my goal was not to convert you or anyone. I am a NetBeans user myself so I know a bit or two about others telling me why I should switch to "clearly superior alternatives" and I don't want to do that to others ;-)
Sounds like Obsidian fits me better than Logseq for now (for the inherent hierarchical organisation). Though one of these days I'll try running Logseq on the same files just for a different view and to try out journalling.
AFAIK Logseq docs encourage new users to put everything under Journal and just tag the relevant blocks. Multiple hierarchical tags are possible, as are aliases, which comes in handy, e.g. I have examples of good ux nested three steps down from root, but in practice I write [[Good UX]] and paste the screenshot and I am done, it shows up at the right place, but is a lot more readable in my journal. BTW, that alias could have been #GoodUX as well and I would have gotten away with hashtag notation.)
If Logseq can also do hierarchical organising/browsing with a simple sidebar interface, I think I'll give it a go. Does it work well for that use case? What's nice is that you can run both Logseq and Obsidian on the same Markdown files, since they're (mostly compatible) Markdown, so I'm not too worried about switching as needed or even using both.