I’m a heavy-duty Logseq user; I use it all day, every day as Product Manager at a fintech company in the UK. It’s used to capture my ideas, record notes from interviews and conversations, correlate concepts and topics, document research notes, prepare product roadmaps, perform competitor analyses, plan my day ahead etc. The back/cross linking functionality works exactly like my mind works. Logseq is the only app that’s done this for me, and I’ve tried many over the decades.
It’s literally the only app I have open all the time. Everything of importance is recorded in Logseq (if it’s not in Logseq it didn’t happen 
)
I came across this thread because I subscribe to the Logseq Weekly RSS feed (thanks @Ed_Nico ) and it struck a chord with me.
I have all these notes, with all the rich context provided through linked references, embedded blocks etc. but I then have to dick about getting that info into something that can be easily summarised and circulated to colleagues for comment, review etc.
I’ve tried workarounds like working with quote blocks, but that breaks really easily.
If Logseq were to go for an MVP in this area, I’d suggest
- the ability to create a page where you can set Outliner-Mode-Off, which means I could write paragraphs of text that aren’t prefixed or automatically indented
- retain the ability to embed blocks so that I can, for example, write my paragraphs of long form text at the top of the page and include embedded blocks of related content further down the page which only serve as transient notes/reminders of what needs to be included in the non-outlined text I’m writing about.
If I had the above, I’d be able to:
- Set up a new page to compose a document that summarises my thoughts and research on a specific topic
- have access to all the notes that I need to write the long form text about
- copy and paste the final output of the long form text to whatever corporate system/app I need to use to share the information
- … without breaking the integrity and linkages of my source material
@Luhmann Thanks for posting your suggestion, and your rationale. It inspired me to write this.