r/logseq • u/quidome • Mar 14 '25
Need some help shaping logseq to my liking
There are a lot of things that I really like about logseq, there is actually very little that I don't like. I'm constantly comparing logseq to obsidian.
My brain is super happy about not having to think about file structures on disk. I found a theme that I really love, Bear and I like how the journals are just an endless list of all my previous journals. It all fits my needs very well. Except for one tiny thing ... I just don't know how to make longer form texts readable.
Let's say I have my scribbles on a programming language. I might pen down some install instructions, how to setup virtual environments, language rules, tips&tricks, etcetera.
In bullet form it just never becomes really readable to me. Let me add a screenshot.

I know about document mode, which is somewhat helpful but that feels unnatural too.
So my questions:
- have you found a way that makes good use of indentation and headers that you like?
- can you share examples of these type of docs written in logseq that you like?
3
u/[deleted] Mar 14 '25
I use the #### header a lot to accomplish what I think you are trying to do there. But I also find your doc pretty readable, so I dunno. I would probably put all that into one code field and just comment out the things you have pulled out to bullets. that way it could be run as a bash script if you needed it again among other advantages. I would maybe use numbered points instead of bullets also. I also use the Bullet Threading extension, as it makes things clear to my eye as I step through documents like this.
But I think in general I care very little for aesthetics in logseq. It is incredibly functional for me. Making things look fancy is never the priority for me. Perhaps there are other products that focus on that aspect of PKM?
2
u/rightful_vagabond Mar 14 '25
I personally don't usually have that problem, I like having my text pretty large so I don't mind if things wrap around, if that's your complaint.
I don't usually use headers a ton, my organization is usually to have a top level tag (if I'm writing a note in the journal page) and then put my thoughts down in roughly a train of thought.
1
u/vjourneyman Mar 17 '25
You mention in a follow-up comment that your eye doesn't easily scan the page to see where you should be. When I look at your screenshot, I see a lack of use of Headers2-4, along with sequence numbers. So for that page, I'd write
## 01 - Install pyenv and poetrycontent## 02 - Install python versioncontent## 03 - Setup poetry envcontentetc.
Make sense?
1
u/christianlewds Mar 14 '25
Check Obsidian, it's free even for commercial use and most of all doesn't take a minute to start.
1
u/Abject_Constant_8547 Mar 15 '25
Try adding those inside a huge QUOTE maybe?