Why are users forced to outline everything?

Feedback Feature Requests
2

Welcome.

  • A few of the past discussions for reference:
  • Some points concerning note-taking software:
    • It is about notes, which are meant to be relatively short, even atomic.
      • Paragraphs are not notes.
      • This is by far the strongest argument.
    • Logseq is not a markdown editor.
      • This is a separate issue from forcing outlining.
      • Good markdown support would be great.
        • Nobody opposes that, but apparently it has not been a priority.
      • Standards are great.
        • They are also limited.
          • Markdown is definitely very limited for Logseq’s needs.
        • They also have limited support in the real world anyway.
          • Markdown is not particularly standardized.
          • Different software supports different standards.
          • Converters are more realistic than direct support.
            • Especially when they are open-source.
    • Logseq is not a document editor.
      • For using documents in Logseq, they need to be in PDF format.
        • Exporting in PDF is at least as useful as saving in markdown.
      • For editing documents, there is nothing wrong in using a dedicated document editor.
      • The right tool for each job.
        • It is doubtful whether a good document editor could be also a good note-taker.
          • Even if existed, maintaining its quality would be very hard.
    • Outliners are part of the real world.
      • Many people don’t write longform at all.
        • LLMs don’t count as people.
      • The world changes.
        • Longform will always be a thing, but gradually less important than in the past.
          • Transitions are always painful.
5 Likes