About 15,700 results
Open links in new tab
  1. Logseq: A privacy-first, open-source knowledge base

    Think faster, think better! By thinking and writing with Logseq, you'll gain confidence in what you know and stop worrying about forgetting anything.

  2. How to Set Up and Use Logseq Sync

    Aug 31, 2024 · Trust no one with your data! Learn step-by-step how to setup and securely sync your notes using Logseq Sync.

  3. Logseq: A privacy-first platform for knowledge management and …

    A privacy-first, open-source platform for knowledge management and collaboration.

  4. About Logseq and this blog

    This blog provides a platform for content creators who use Logseq for their daily activities. No matter if you're an academic, project manager, or just have a curious mind, you'll find content …

  5. Logseq - Logseq forum

    The official Logseq forum to request features, report bugs, and have in-depth discussions about workflows

  6. New to Logseq? Start here - Documentation - Logseq

    Jun 30, 2022 · By using Logseq as a daily log, you quickly collect notes on a variety of topics. Most users start out by taking notes during meetings, to track tasks, or even manage entire …

  7. Logseq Blog

    Jul 4, 2022 · How-to Citation Needed: How to Use Logseq's Zotero Integration Learn how to set up Zotero in combination with Logseq, and get access to powerful document annotation and …

  8. How to Get Started With Networked Thinking and Logseq

    Apr 18, 2022 · This is log in the name Logseq. By using Logseq as a logbook first and foremost, you greatly reduce cognitive load. Whereas in many other note-taking tools you first need to …

  9. Whiteboards and Live Queries for Everybody! [0.9.1 Update]

    Mar 29, 2023 · Logseq is an open source project, made by a community of personal knowledge enthusiasts, for enthusiasts. If you have suggestions to make Logseq a better tool for thinking …

  10. How advanced queries work - step-by-step explainer - Queries

    Dec 20, 2024 · Technically there is a 4th value, transaction-id, but this is usually ignored for Logseq use-cases (it can be excluded from the vectors). So practically, all Logseq data …