logseq-flavored-markdown

Formatting Logseq-Flavored Markdown (LFM)

Note: these markdown rules are not itself in LFM (though it does contain examples of valid LFM)

⚠️ CRITICAL: DO NOT MODIFY FRONTMATTER TAGS ⚠️

• NEVER modify, add, or remove the tags:: frontmatter item specifically
• The tags:: frontmatter (e.g., tags:: [[MyTagHere]], [[MySecondTagHere]]) is strictly protected
• Even if you think a tag is missing or incorrect, DO NOT change the tags:: frontmatter
• This restriction applies ONLY to the tags:: frontmatter item, not to other page attributes
• Other page-level attributes may be modified when explicitly instructed to do so
• Do not confuse this instruction with inline tags in the document body (e.g., #MyTag)
• This is a strict requirement - modifying frontmatter tags will disrupt the user's categorization system

Basic Structure

• Logseq uses a hierarchical bullet-point structure.
• TAB Indentation determines the relationship between parent and child blocks.
• IMPORTANT: All content, including headings, must be prefixed with bullet points (-)
• IMPORTANT: Indentations should use the TAB character.
• Headings are created using #, with more # indicating deeper nesting
• Heading format: - # Heading Text (note the bullet point before the #)
• Content should be nested logically under the appropriate headings
  • H2 (##) should be "under" H1 (#)
  • H3 (###) should be "under" H2 (##)
  • ...
  • H should be "under H
• DO NOT blank newlines in the document. Each line in the whole file should have content. At the very least, a line should contain a -.

Example

<CORRECT_✅>

- # Main Topic
  - ## Overview
    - ### Basic Idea
      - Sub-detail A
    - Detail 2
- # Next Topic
  - First point under next topic

<CORRECT_✅>

The following example is incorrect because it lacks indentation, unordered list items, and puts newlines between headings: <INCORRECT_❌>

# Main Topic

## Overview

### Basic Idea
- Sub-detail A
- Detail 2