A whiteboard for the main concepts in Logseq

Customization Look what I built
2

To give an example of how this diagram can help, consider the long-standing confusion between pages and blocks (an open conversation for years now). As a new user, reading the many threads on the matter didn’t provide me any confidence with how to use them. Here are just a few of those threads:

Picking between page and block in a given occasion can feel obvious, and both options may work at the moment, but this doesn’t exclude regretting the choice down the way:

  • Not everyone has the time or expertise to make a smooth conversion when they change their mind.
  • Even worse can be the feeling of unrest when both options look justifiable.

To gain the needed confidence, should shift the focus from the tangible to the conceptual. This is what the structure of the diagram clears up:

  • A page is a node in a graph (Logseq graph points down to Logseq page).
  • A page represents a concept within the managed knowledge (Logseq page points right to concept, which is under knowledge).
    • A concept is a conceived idea (concept points right to idea), meaningful enough to be given a unique title (not just an id).
      • as a soft rule, something that could be an article in a wiki
    • A concept is made up of a list of notes (concept points down to note).
      • The notes of a concept provide an outline for it.
      • A concept is the subject of all its notes.
  • A page is made up of a tree of blocks (Logseq page points down to Logseq block).
    • A block is a node in the tree of a page.
    • A block represents a note or a bullet point within a note (Logseq block points right to note).
      • A note associates some concepts (which it may reference with [[]]) (note points right to association).
      • A note belongs to the page of the concept which has the role of its subject.
        • A note in a journal is not in its final position.
3 Likes