Part of the problem is Obisidian treats anything with a tab indentation as a source block, there’s a fix you can make in logseq to change how indentation behaves by swapping it from tabs to number of spaces. Drop this into your config.edn, and then try creating a new document with indented bullet-points and you should see them render correctly in Obsidian.
:export/bullet-indentation :two-spaces
Thank you! I have been trying to figure out how to replace the indentation for a while!
This is not an issue with obsidian, as it is the default behavior for markdown standards.
4 spaces are used to define a codeblock
voted. like logseq, but I really want a outline/TOC, which is a must-have feature for a md editor, not to mention a wiki system.
I was about to suggest something similar. I’d love to see such a feature. All my pages have a certain structure at the macro level:
I’d keep the outline of the page open in the sidebar at all times to quickly navigate it.
There’s a toc plugin here: GitHub - mschmidtkorth/logseq-msk-toc: A table of contents generator for Logseq
We just added support for plugins’ floating windows. @Charlie Should we make a PR on the logseq-msk-toc plugin?
I think the possibility of collapsing all the blocks with a single click or a keyboard stroke would be a good solution, the document would become an outline of itself.
Glad to know there’s a plugin, will give it a try. Any chance it gets merged into the main repo?
It could be! Would like to collect more feedback first.
Having this ability in the right sidebar would be really convenient and useful
Chanced upon this FR. I’ve built a TOC plugin in the marketplace that can be opened in the right sidebar to facilitate easy navigation. Can take a look!
This is awesome!! I’ve been wanting a TOC/Outline view myself 
Maybe I am missing something. But in a large page, when you click outside the content and the CMD-UP a few time all blocks are folded till the main level, effectively the H1 level.
When I CMD-DOWN 1 time it opens the H1/H2 level.
And sometimes I even go further down but most of the time from this level I enter a Block by hitting the bullet and I can edit (also the sub-bullets for that H3 level).
And using the breadcrumbs at the top of the page I can quickly see where I am and navigate to a higher level … to deep dive in another place in the document.
So I guess an outline overview is already in the document.
@Miro — the Zettlekasten method recommends zettles remain small. So one way to avoid the massive pages requiring a table of contents is to avoid massive pages. And one way to achieve some division in large bodies is to use the hierarchies feature. You could for example, write a book where every chapter existed as part of a hierarchy.
I’m not disagreeing with the feature request, I’m just offering suggestions for effectively dealing with it in its absence. When I find a page that’s oversized, I generally feel it needs split apart.
This TOC plugin allows a TOC in the sidebar.
The doc may be a bit confusing, but to use it in the sidebar showing the TOC for whatever page is selected:
Any new progress and future plan about this feature?
I’d like to use Obsidian to do more longform writing inside the same system as my existing outline-based notes, but have a similar worry that my structure will be flattened when I return to my outline in Logseq.
Would a community plugin that told Logseq to parse Markdown heading levels (#, ## etc) as levels of an outliner hierarchy solve this problem? I guess you’d also have to work out how to tell it to deal with plain text blocks in between hierarchy levels (maybe always as children of the most recent header?).
Does a plugin like that exist, and if not how hard would it be to make one?
I’ve tried a few TOC plugins mentioned here, but I didn’t find them quite satisfactory for my flow.
However, I’ve recently discovered this sticky headers plugin and I’ve been really enjoying it. I think it’s a nice alternative to having a dedicated Contents panel: GitHub - yoyurec/logseq-sticky-headers: 📌 H1-H5 headers stick on content scroll. Logseq pligin
If you like that plugin, then it also goes very nicely with this plugin to easily modify heading levels: GitHub - vipzhicheng/logseq-plugin-heading-level-shortcuts: A very tiny plugin for Logseq to bind shortcuts to change heading levels
You can also use GitHub - stdword/logseq13-missing-commands: Logseq plugin with missing but really helpful commands 🪚 and it’s 🔪 Toggle auto headingplugin.logseq13-missing-commands to select blocks and it’ll assign them headings automatically
