Logseq Onboarding | Learn the fundamentals of Logseq in 70 minutes

Logseq’s core pitch is that notes become more useful when they’re treated as a network of small, linkable blocks—especially when those blocks live in a time-anchored journal and can be retrieved instantly with queries. Instead of forcing every idea into a single “home” like a traditional document or folder, Logseq keeps the smallest unit of meaning as a block (often one idea per bullet) and lets relationships—links and references—carry the real value. That shift matters because it reduces cognitive overload: working memory is limited, and large linear notes make people reread and mentally juggle too much at once.

The onboarding walkthrough starts with outliner fundamentals because Logseq’s structure is hierarchical even when it feels “graph-like.” Each bullet is a block, indentation creates parent/child relationships, and nesting enables quick zooming between a high-level overview and detailed views via expand/collapse. Clicking into a block provides focus, while the sidebar lets multiple pages or branches stay open in parallel—useful for research workflows where notes are collected in one place and drafts are written in another. Quick entry is tied to the Journals page: new thoughts can be captured immediately without deciding where they belong, since journal entries automatically receive an “anchor in time.” The presenter emphasizes that newcomers should default to writing on the journal page and only later create pages for grouping and distilling related material.

From there comes “network thinking,” framed through analogies like a crime-show wall of connected clues and Wikipedia-style linking. In this model, the location of an idea matters less than the relationships between ideas. Logseq is described as an outliner built on a graph database, so the relationships between blocks become the primary asset. The workflow is built around atomic blocks (one idea each) so links stay precise and don’t require loading multiple concepts at once. Traditional note apps often mimic paper—one note, one location—whereas Logseq allows a note or block to be referenced from many places.

The session then drills into how links work in practice. Page links (wiki/bracket links and hashtag-style links) create bidirectional connections and populate “linked references” at the destination. Tags are treated as a categorization layer with different matching behavior than page links. For precision, block references point to a specific block via unique IDs and show all instances where that block is referenced. Block embeds and page embeds act like “portals”: embeds can display children and can be edited in-place while updating the original source. The walkthrough also highlights Logseq’s local-first approach for privacy—notes and assets live on the user’s computer, with sync described as optional.

Finally, the most operational part arrives with tasks and queries. Tasks support multiple modes (to-dos, priorities, time tracking, and org-mode-style schedule/deadline). Queries are presented as saved searches that filter blocks using conditions like linked pages, page properties, priorities, and date ranges (e.g., “journals between January 1st and January 4th”). Queries can also power task views by dynamically updating when a block’s status changes. The takeaway is a practical 80/20: start with journals for capture, write in blocks, link to pages, and use queries to retrieve and manage both knowledge and tasks without duplicating content.