I propose a feature I will refer to as “Views”.
This will solve specific problems that have been discussed in topics on this forum but in a flexible way. See Separate graphs for work and home? - Questions & Help - Logseq for background.
- Typical user starts off with the typical graph structure and everything at root level as normal:
- Logseq - assets - journals - logseq - pages - whiteboards
A new folder is introduced (this is to demonstrate the concept not the final UI)
The user can create a view of their graph by defining a filter query and giving it a name. It then shows up under “views”…
- views - My work stuff (this is expandable)
When you click on this query you don’t just see a page with the results of the query, rather it acts more like a node a parent node in the graph and projects all the matching items of the query as nodes in the subgraph i.e like a top level folder. So you can expand it and so your total structure now looks like:
- Logseq - assets - journals - logseq - pages - whiteboards - views - My work stuff - assets - journals - logseq - pages - whiteboards
However in this expanded view, the only nodes present are the nodes that satisfy the query for that “view”…
This could be made even more powerful in future, with things like:-
- The ability to publish, export, views.
This would solve the work / personal separation because, or even just situations in which you want to prepare for what can be seen at some presentation, talk or demo:-
- Those that want physical seperation can still use seperate graphs and ignore this feature.
- Alternatively those that want top level folder seperation can have seperate “parent” pages in the hierarcht for work vs personal, and can then define a seperate “View” for “Work” that just queries everything from the “Work” folder. This is less fragile than relying on metadata and only needs to be set up once. When in a work presentation, the user is able to switch to the “Work” view, and this constrains the graph that logseq is displaying in the app and that the current user can work with, until they switch out of this view, to the default view or another. So liss danger of work content being visible during that presentation.
- And for those that are comfortable purely with metadata and queries to distingush work / personal content, can forgo structuring there pages into top level /personal / work folders and can just rely on the metadata in their queries, and still leverage views to switch contexts if desired.