- There is no standard markdown, frontmatter etc.
- Logseq follows its own conventions, like everybody else does.
- The more the features the more the needed conventions.
- Logseq follows its own conventions, like everybody else does.
- In Logseq MD:
- graphs
- have a folder in the file system
- have connections that live in a local database
- recreated on every re-indexing
- have no concept of place or order
- pages
- are nodes in a graph
- are files inside a graph’s folder hierarchy
- unless they never had any content
- are very much like special blocks
- Especially in queries, they are just different entries in a mostly homogeneous database.
- are often treated differently by Logseq’s built-in functionalities
- are conceptually a different entity with a separate role
- But this is not strictly enforced.
- blocks
- belong to a page’s outline
- In outlines, everything has its own place in a strict hierarchical structure.
- have always a parent
- either their page or another block of the same page
- have potentially one or more siblings
- always ordered
- belong to a page’s outline
- frontmatter
- belongs to a page
- It is about that page’s meta-data.
- Typically its properties.
- They have their own order.
- But that order has no special meaning.
- It is about that page’s meta-data.
- is characterized by being:
- in the beginning of a file
- without dashes (
-
)
- is edited from within its page’s first bullet
- Sometimes this is mentioned as a block, while it is a mere bullet.
- All blocks correspond to a bullet, but this bullet corresponds to the page.
- While editing, sometimes this convention fails (aka a bug).
- i.e. the first bullet may or may not contain frontmatter
- Whenever this happens, it needs external editing of the markdown.
- Sometimes this is mentioned as a block, while it is a mere bullet.
- belongs to a page
- graphs
4 Likes