# Table of Contents - [Unofficial Logseq Documentation | Logseq Documentation](#unofficial-logseq-documentation-logseq-documentation) - [Blog | Logseq Documentation](#blog-logseq-documentation) - [Tags | Logseq Documentation](#tags-logseq-documentation) - [Posts tagged "docusaurus" | Logseq Documentation](#posts-tagged-docusaurus-logseq-documentation) - [Posts tagged "logseq" | Logseq Documentation](#posts-tagged-logseq-logseq-documentation) - [Why I suggest to use docusaurus | Logseq Documentation](#why-i-suggest-to-use-docusaurus-logseq-documentation) - [Hello from Logseq Documentation | Logseq Documentation](#hello-from-logseq-documentation-logseq-documentation) - [Blocks and Pages | Logseq Documentation](#blocks-and-pages-logseq-documentation) - [Understanding-Oriented Docs | Logseq Documentation](#understanding-oriented-docs-logseq-documentation) - [Contents Page | Logseq Documentation](#contents-page-logseq-documentation) - [Problem-Oriented Docs | Logseq Documentation](#problem-oriented-docs-logseq-documentation) - [Search entry | Logseq Documentation](#search-entry-logseq-documentation) - [Introduction | Logseq Documentation](#introduction-logseq-documentation) - [Information-Oriented Docs | Logseq Documentation](#information-oriented-docs-logseq-documentation) - [Shortcuts | Logseq Documentation](#shortcuts-logseq-documentation) - [Learning-Oriented Docs | Logseq Documentation](#learning-oriented-docs-logseq-documentation) - [Quickstart | Logseq Documentation](#quickstart-logseq-documentation) --- # Unofficial Logseq Documentation | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/#main) Welcome[#](https://chrislasar.github.io/logseq-doc/#welcome "Direct link to heading") -------------------------------------------------------------------------------------- Welcome to an attempt to support user-driven documentation creation for Logseq. This documentation is by now totally unofficial and incomplete. Visit the [repository](https://github.com/ChrisLasar/logseq-doc) to see how to contribute. * [Welcome](https://chrislasar.github.io/logseq-doc/#welcome) --- # Blog | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/blog#main) ### Recent posts * [Why I suggest to use docusaurus](https://chrislasar.github.io/logseq-doc/blog/why-docusaurus) I guess some people are wondering why this site uses Docusaurus instead of Logseq for documentation? Basically there are the following reasons. Logseq is not yet prepared for parallel writing of documentation by multiple users. Docusaurus already hosts large documentations created by a large number of users. Integration with standard development processes is excellent (GitOps). And the complexity of Docusaurus is so low that anyone can contribute within minutes. Docusaurus therefore seems to be a good candidate for creating initial documentation. The user community is international. The majority of developers are from China. Discord already has an español speaking subcommunity. My native language is German, unfortunately English is the only foreign language I do speak. Sooner or later the project might need a multilingual documentation. The energy of an international team of authors can only be used if the documentation is not created in independent parallel worlds. This requires a defined exchange between the language areas in the documentation. [Docusaurus is prepared](https://docusaurus.io/docs/i18n/introduction) to create multilingual documentation in the upcoming V2 - which we are already using today. --- # Tags | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/blog/tags#main) ### Recent posts * [Why I suggest to use docusaurus](https://chrislasar.github.io/logseq-doc/blog/why-docusaurus) Tags ==== ### D [docusaurus (1)](https://chrislasar.github.io/logseq-doc/blog/tags/docusaurus) * * * ### L [logseq (1)](https://chrislasar.github.io/logseq-doc/blog/tags/logseq) * * * --- # Posts tagged "docusaurus" | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/blog/tags/docusaurus#main) ### Recent posts * [Why I suggest to use docusaurus](https://chrislasar.github.io/logseq-doc/blog/why-docusaurus) One post tagged with "docusaurus" ================================= [View All Tags](https://chrislasar.github.io/logseq-doc/blog/tags) I guess some people are wondering why this site uses Docusaurus instead of Logseq for documentation? Basically there are the following reasons. Logseq is not yet prepared for parallel writing of documentation by multiple users. Docusaurus already hosts large documentations created by a large number of users. Integration with standard development processes is excellent (GitOps). And the complexity of Docusaurus is so low that anyone can contribute within minutes. Docusaurus therefore seems to be a good candidate for creating initial documentation. The user community is international. The majority of developers are from China. Discord already has an español speaking subcommunity. My native language is German, unfortunately English is the only foreign language I do speak. Sooner or later the project might need a multilingual documentation. The energy of an international team of authors can only be used if the documentation is not created in independent parallel worlds. This requires a defined exchange between the language areas in the documentation. [Docusaurus is prepared](https://docusaurus.io/docs/i18n/introduction) to create multilingual documentation in the upcoming V2 - which we are already using today. --- # Posts tagged "logseq" | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/blog/tags/logseq#main) ### Recent posts * [Why I suggest to use docusaurus](https://chrislasar.github.io/logseq-doc/blog/why-docusaurus) One post tagged with "logseq" ============================= [View All Tags](https://chrislasar.github.io/logseq-doc/blog/tags) I guess some people are wondering why this site uses Docusaurus instead of Logseq for documentation? Basically there are the following reasons. Logseq is not yet prepared for parallel writing of documentation by multiple users. Docusaurus already hosts large documentations created by a large number of users. Integration with standard development processes is excellent (GitOps). And the complexity of Docusaurus is so low that anyone can contribute within minutes. Docusaurus therefore seems to be a good candidate for creating initial documentation. The user community is international. The majority of developers are from China. Discord already has an español speaking subcommunity. My native language is German, unfortunately English is the only foreign language I do speak. Sooner or later the project might need a multilingual documentation. The energy of an international team of authors can only be used if the documentation is not created in independent parallel worlds. This requires a defined exchange between the language areas in the documentation. [Docusaurus is prepared](https://docusaurus.io/docs/i18n/introduction) to create multilingual documentation in the upcoming V2 - which we are already using today. --- # Why I suggest to use docusaurus | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/blog/why-docusaurus#main) ### Recent posts * [Why I suggest to use docusaurus](https://chrislasar.github.io/logseq-doc/blog/why-docusaurus) I guess some people are wondering why this site uses Docusaurus instead of Logseq for documentation? Basically there are the following reasons. Logseq is not yet prepared for parallel writing of documentation by multiple users. Docusaurus already hosts large documentations created by a large number of users. Integration with standard development processes is excellent (GitOps). And the complexity of Docusaurus is so low that anyone can contribute within minutes. Docusaurus therefore seems to be a good candidate for creating initial documentation. The user community is international. The majority of developers are from China. Discord already has an español speaking subcommunity. My native language is German, unfortunately English is the only foreign language I do speak. Sooner or later the project might need a multilingual documentation. The energy of an international team of authors can only be used if the documentation is not created in independent parallel worlds. This requires a defined exchange between the language areas in the documentation. [Docusaurus is prepared](https://docusaurus.io/docs/i18n/introduction) to create multilingual documentation in the upcoming V2 - which we are already using today. [Edit this page](https://github.com/ChrisLasar/logseq-doc/edit/main/blog/2021-05-12-why-docusaurus.md) --- # Hello from Logseq Documentation | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/old_index#main) ### Easy to Use Docusaurus was designed from the ground up to be easily installed and used to get your website up and running quickly. ### Focus on What Matters Docusaurus lets you focus on your docs, and we'll do the chores. Go ahead and move your docs into the `docs` directory. ### Powered by React Extend or customize your website layout by reusing React. Docusaurus can be extended while reusing the same header and footer. --- # Blocks and Pages | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/docs/explanation/blocks-and-pages#main) Blocks[#](https://chrislasar.github.io/logseq-doc/docs/explanation/blocks-and-pages#blocks "Direct link to heading") --------------------------------------------------------------------------------------------------------------------- Blocks are the smallest addressable and thus linkable unit in Loqseq. Each page is automatically created with the first block, which the user can fill with content. If the user closes a block, the program automatically appends another block for further information. Pressing the `Enter` key closes a block. A simple line break within the same block is achieved by pressing the `Shift-Enter` key combination. A block can have any number of sub-blocks. Each block is implicitly linked to its sub-blocks in the knowledge graph. Pages[#](https://chrislasar.github.io/logseq-doc/docs/explanation/blocks-and-pages#pages "Direct link to heading") ------------------------------------------------------------------------------------------------------------------- Pages are a special form of blocks. Pages are characterized by the following properties: * When saved, pages create a separate file in the file system. * While blocks can contain only sub-blocks, pages can contain multiple blocks at the upper level. * The user can only mark pages for export, but not individual blocks. * By default, the knowledge graph represents only the link between pages. [Edit this page](https://github.com/ChrisLasar/logseq-doc/edit/main/docs/explanation/blocks-and-pages.md) * [Blocks](https://chrislasar.github.io/logseq-doc/docs/explanation/blocks-and-pages#blocks) * [Pages](https://chrislasar.github.io/logseq-doc/docs/explanation/blocks-and-pages#pages) --- # Understanding-Oriented Docs | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/docs/explanation/intro#main) According to the ["Grand Unified Theory of Documentation"](https://documentation.divio.com/) : > [Explanation](https://documentation.divio.com/explanation/#) > , or discussions, clarify and illuminate a particular topic. They broaden the documentation’s coverage of a topic. Backlog[#](https://chrislasar.github.io/logseq-doc/docs/explanation/intro#backlog "Direct link to heading") ------------------------------------------------------------------------------------------------------------ Feel free to contribute or to extend this list: * Explain the usage of properties * Explain the different kinds of installations (app, online, self-hosted, ...) * Backlinks [Edit this page](https://github.com/ChrisLasar/logseq-doc/edit/main/docs/explanation/intro.md) * [Backlog](https://chrislasar.github.io/logseq-doc/docs/explanation/intro#backlog) --- # Contents Page | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/docs/how-to/content-page#main) The contents page allows the user to quickly access his pages similar to a table of contents. The contents page is located in the right sidebar. To open the sidebar, the user presses the burger icon in the upper right corner. The first tab contains the contents page. The contents page is a normal Loqseq page with the title "Contents. The user can design this page any way he wants. Usually it is a list of blocks with links to the important pages in the graph. To customize the table of contents, the user [searches for the page](https://chrislasar.github.io/logseq-doc/docs/how-to/content-page/search-entry) with the title "Contents" and customizes this page to his needs. Raw "Contents" page example \- \[\[GTD\]\] \- \[\[GTD - weekly\]\] \- Meetings \- \[\[Project A - Standup\]\] \- \[\[1-on-1\]\] Copy [Edit this page](https://github.com/ChrisLasar/logseq-doc/edit/main/docs/how-to/content-page.md) --- # Problem-Oriented Docs | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/docs/how-to/intro#main) According to the ["Grand Unified Theory of Documentation"](https://documentation.divio.com/) : > [How-to guides](https://documentation.divio.com/how-to-guides/) > take the reader through the steps required to solve a real-world problem. This might be the right place to explain workflows. Backlog[#](https://chrislasar.github.io/logseq-doc/docs/how-to/intro#backlog "Direct link to heading") ------------------------------------------------------------------------------------------------------- Feel free to contribute or to extend this list: * Page alias * Create a slide show * Getting things done * Content page [Edit this page](https://github.com/ChrisLasar/logseq-doc/edit/main/docs/how-to/intro.md) * [Backlog](https://chrislasar.github.io/logseq-doc/docs/how-to/intro#backlog) --- # Search entry | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/docs/how-to/search-entry#main) The user can search for an entry using the magnifying glass icon at the top left of the main window. The search can also be accessed via a keyboard shortcut. By default this shortcut is `CTRL/CMD-U`. Logseq searches the page titles and block contents for the entered string. The results appear directly below the search field as you type. A page is marked with a P, a block with a B. With the cursor keys up/down the user selects the desired entry and changes to this page or block by pressing the Enter key. If Loqseq does not find an entry and the user completes his input with the Enter key, Loqseq creates a new page with this title. [Edit this page](https://github.com/ChrisLasar/logseq-doc/edit/main/docs/how-to/search-entry.md) --- # Introduction | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/docs/intro#main) This documentation follows the ["Grand Unified Theory of Documentation"](https://documentation.divio.com/) . Therefore it consists of * [learning-oriented tutorials](https://chrislasar.github.io/logseq-doc/docs/intro/tutorial/intro) , * [problem-oriented how-to guides](https://chrislasar.github.io/logseq-doc/docs/intro/how-to/intro) , * [understanding-oriented explanations](https://chrislasar.github.io/logseq-doc/docs/intro/explanation/intro) and * [information-oriented references](https://chrislasar.github.io/logseq-doc/docs/intro/reference/intro) . [Edit this page](https://github.com/ChrisLasar/logseq-doc/edit/main/docs/intro.md) --- # Information-Oriented Docs | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/docs/reference/intro#main) According to the ["Grand Unified Theory of Documentation"](https://documentation.divio.com/) : > [Reference guides](https://documentation.divio.com/reference/#) > are technical descriptions of the machinery and how to operate it. Backlog[#](https://chrislasar.github.io/logseq-doc/docs/reference/intro#backlog "Direct link to heading") ---------------------------------------------------------------------------------------------------------- Feel free to contribute or to extend this list: * List of frequently used queries (?) * References for plugin implementation [Edit this page](https://github.com/ChrisLasar/logseq-doc/edit/main/docs/reference/intro.md) * [Backlog](https://chrislasar.github.io/logseq-doc/docs/reference/intro#backlog) --- # Shortcuts | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/docs/reference/shortcuts#main) To see the most important keyboard shortcuts, press the ? in the lower right corner of the screen. For your first steps the following keyboard shortcuts will help: * Click to edit any block. * Type `Enter` to start a new block. * Type `Shift+Enter` to create a new line in the current block. * Type `/` to show all the commands. * for example type `/Draw` for free drawing. * Type `[[` to reference or create a new page.\ * Type `((` to reference a block on any page.\ * Type `Tab` to indent and `Shift+Tab` to unindent a block.\ * Type `<` for more formatting commands (like quotes and tips!)\ \ [Edit this page](https://github.com/ChrisLasar/logseq-doc/edit/main/docs/reference/shortcuts.md) --- # Learning-Oriented Docs | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/docs/tutorial/intro#main) According to the ["Grand Unified Theory of Documentation"](https://documentation.divio.com/) : > [Tutorials](https://documentation.divio.com/tutorials/) > are lessons that take the reader by the hand through a series of steps to complete a project of some kind. They are what your project needs in order to show a beginner that they can achieve something with it. Backlog[#](https://chrislasar.github.io/logseq-doc/docs/tutorial/intro#backlog "Direct link to heading") --------------------------------------------------------------------------------------------------------- Feel free to contribute or to extend this list: * Installation * Usage of queries * Add an use properties [Edit this page](https://github.com/ChrisLasar/logseq-doc/edit/main/docs/tutorial/intro.md) * [Backlog](https://chrislasar.github.io/logseq-doc/docs/tutorial/intro#backlog) --- # Quickstart | Logseq Documentation [Skip to main content](https://chrislasar.github.io/logseq-doc/docs/tutorial/quickstart#main) First start[#](https://chrislasar.github.io/logseq-doc/docs/tutorial/quickstart#first-start "Direct link to heading") ---------------------------------------------------------------------------------------------------------------------- When you start the program for the first time, you are in the diary view. The top section shows the current date. The cursor is ready for your first input. Enter a text and press `Enter`. Congratulations, you have created your first page with the first block in it. [Edit this page](https://github.com/ChrisLasar/logseq-doc/edit/main/docs/tutorial/quickstart.md) * [First start](https://chrislasar.github.io/logseq-doc/docs/tutorial/quickstart#first-start) ---