Logseq/Journal/Section/Friction

• Journal section — Friction

  • Parent registry: Logseq/Journal. One journal has carried this section, 2026-03-25 Wed.

  • Purpose

    • Capture where the day resisted you without turning the journal into a complaint log. Split useful friction (learning, practice) from frustration (blocked goals, bugs, rough edges).

  • Structure (default)

    • Under the day’s narrative, use a second-level block titled with the Friction topic link in the heading, then nest:
      • Useful friction — optional third level; fourth level when Learning (or similar) if you are separating practice notes.
      • Frustration — bugs, failed attempts, tooling fights; link out to Q, Bug, or How To pages instead of long procedural paste.

  • Do

    • Link concrete follow-ups: Filed sessions, bug pages, questions, or updated docs.
    • Keep one-sentence context on the same bullet when it clarifies emotion or stakes (still a snapshot, not a ticket dump).

  • Don’t

    • Replace the change log — operational page lists stay under Filed and Updated, and are not duplicated as paragraphs here. Journals up to 2026-05-12 Tue nested both under a garddiff heading; since then they are top-level blocks of their own.
    • Turn Friction into the only section of the journal; story and questions still deserve their own headings.