Should you use blocks or pages in LogSeq?

TL;DR

This video explains the difference between pages and blocks in Logseq and provides a personal system for deciding when to use each one.

Transcript

so if you're using lockseek then you might have noticed that you can link to both pages and individual blocks and this raises the question should i make pages or just put everything into blocks with sub blocks now in this video i'm going to dive into the difference between two and my personal system to help me decide where to use what now if you're... Read More

Key Insights

• 🔐 The difference between pages and blocks in logseq: Pages are top-level blocks in their own file with unique abilities like easier search and multiple top-level blocks on a single page. The knowledge graph is made of pages.
• 🖊️ Adding information to blocks is easier and keeps the flow, while adding information to pages requires a workflow break. Blocks allow for outlining related data and shaping structured formats.
• 🔍 To tackle the question of when to use pages or blocks, topics that will be added to over time become pages, while blocks are used to refer to those topics. Journal entries, meeting notes, emails, and chat messages are examples of blocks that reference pages.
• 📚 Pages are the foundation of the system, and blocks that refer to those pages add value. Pages without references should be evaluated to determine if they should be kept as blocks.
• ✒️ Changing things from pages to blocks or vice versa is possible but may be harder than desired. Future self usability is important when considering how to organize data in logseq.
• 🎥 Proposed logseq video topics: Transitioning workflows to logseq, advanced queries, and a getting started guide. Viewer feedback is requested to prioritize the video releases.
• 👍 Remember to subscribe to receive notifications of video releases.

Questions & Answers

Q: What are the advantages of using pages in Logseq?

Pages in Logseq have several advantages, including easier searching, quick access, and the ability to be marked as favorites. Additionally, pages are part of the knowledge graph in Logseq, making them a foundational element of the system.

Q: Why would one choose to store information in blocks instead of pages?

Storing information in blocks can be more convenient for adding information within a specific context without interrupting the workflow. Blocks also allow for structured outlining and the ability to reshape data later on.

Q: How does the speaker decide when to use pages or blocks in their personal system?

The speaker's personal system involves using pages for topics that require continuous updates, such as projects, people, books, movies, and software applications. Blocks are then used to reference these topics and organize related data.

Q: Can pages be converted back into blocks or vice versa in Logseq?

Pages can be merged to create one big topic, effectively converting multiple pages into a single block. Similarly, blocks can be updated to point towards a fresh page, allowing for flexibility in organizing and restructuring the linked network of information.

Summary & Key Takeaways

• Pages in Logseq are top-level blocks that have unique abilities such as easier searching, quick access, and the ability to be marked as favorites.

• Blocks, on the other hand, are useful for adding information within a specific context and allowing for structured outlining.

• The speaker's personal system involves using pages for topics that require continuous updates, while using blocks to reference those topics and organize related data.