Logseq beginner's course (7/8) - Exploring Logseq menus and other user interface elements

Logseq’s interface is built around fast navigation between your databases, journals, and linked pages—so the practical goal is learning where key controls live and how they affect retrieval later. The left-side menu starts with a search bar and a shortcut for opening the menu, then a database/graph selector lets users switch between graphs, add new ones, and unlink graphs when needed. A refresh and “re-index” control pulls in changes from local files; re-indexing effectively rebuilds the graph, which can act like an “off and on again” fix when updates don’t appear. Because re-indexing can be risky if local changes haven’t actually been saved, the workflow includes checking the local directory first to confirm the new content exists before rebuilding the index.

From there, the menu organizes core workflows. Journals provide a direct jump back to journal pages, while Flashcards connect to spaced repetition: questions appear as cards, and users can reveal answers and move through them with shortcuts. “All pages” functions as a database-wide index, listing every page and showing link counts; sorting by number of links helps identify heavily used pages as well as pages that may be under-connected. It also displays creation and update times, and includes a cleanup tool to remove orphan pages—empty pages with no links—helping keep the knowledge base tidy.

Graph view is presented as a navigation and relationship map. Pages become nodes, and links become lines connecting related concepts. A page that isn’t linked to anything else may appear isolated except for its journal connection; once a user links it to another page (for example, linking “recipe”), the graph updates to reflect the new relationship. A separate “nodes” menu can be used to control what appears in the graph; one example avoids showing journal date pages in the graph because those built-in date entries can clutter the relationship view.

The right sidebar offers additional entry points for structuring and browsing information. Favorites and “contents” provide ways to organize access, while “page graph” shows all links made from a specific page in focus—useful when a page contains lots of connected notes. Help is positioned as a practical resource hub, pointing to keyboard shortcuts, documentation, unofficial community documentation, and the Discord community for troubleshooting. The emphasis is that open-source support often comes from detailed forum answers.

Finally, the settings area covers customization without overwhelming beginners. Developer mode can be enabled in advanced settings, which unlocks plugins and theme controls. Common beginner-friendly options include workflow preferences (such as changing the completion style), date format preferences, and tooltip previews for link pages. Shortcut customization is also available. The overall takeaway is that Logseq’s power comes from consistent structuring and retrieval: learning these interface elements early makes it easier to find and connect information as the database grows.