Logseq - A Roam Research Alternative for Notes / PKM / To Do / Journal

Logseq positions itself as a Roam Research-style personal knowledge management tool that keeps notes in a local outliner while also syncing them to GitHub for backup. The pitch is straightforward: avoid losing work to siloed folders or fragile workflows, and instead build a network of linked notes that can be navigated like a wiki.

Setup starts with connecting Logseq to GitHub. After authorizing access, Logseq requests a GitHub personal access token. The transcript walks through generating that token in GitHub’s developer settings, emphasizing that the token value must be copied immediately because it can’t be viewed again. With the token in place, Logseq asks which repository should store the notes. A new private repository can be created (no README needed), and the repository link is used so Logseq can clone and begin syncing. Once connected, a green indicator confirms that all notes are syncing to GitHub, and the journal-style pages appear by date.

In day-to-day use, Logseq’s core interface behaves like an outliner: typing creates notes, indentation creates structure, and sections can be focused on by collapsing or selecting a specific “knot” (a note block). As new entries are added to today’s page, they appear immediately, and the system supports expanding and collapsing at multiple levels.

The standout feature is backlinking and transclusions—mechanisms that create relationships between notes without forcing everything into a strict hierarchy. Instead of burying ideas inside nested folders, users can link concepts together so reviewing one page leads to related pages. The transcript demonstrates this with a “fitness” example: typing a bracketed link (e.g., [[fitness]]) turns a term into a clickable page, and subsequent text can populate that page. Clicking the link navigates to the linked note, while shift-click opens it in a side view for editing alongside the current page. This reduces the friction of jumping back and forth to find the right place to write.

Transclusions add another layer: using an embed block (via a slash command) can insert a referenced section—such as “my goals are”—directly into another page. Editing the embedded content updates the source page, letting users reuse structured snippets without duplicating work.

Logseq also supports practical workflows: a “to-do list for a now and later” pattern where unfinished items roll forward to the next day, plus date-based navigation using commands for yesterday and tomorrow. Pages can be created on demand through search (e.g., creating a “how to take notes” page when it doesn’t exist yet), and search can surface all references to a term across existing notes.

Finally, the transcript highlights safety and visibility. Notes are exported in a markdown-style format into the GitHub repository, and the interface provides tools like recent pages, a page graph showing which pages link to which, theme switching, and command help. The overall takeaway is that linking and transclusions keep information findable over time, while GitHub syncing provides a durable backup for the growing network of notes.