Welcome.
About your “question”:
- There is currently no way to make any big restructuring at the file system.
- Thus what you have belongs to Feature Requests.
- There are already similar (not identical) requests (e.g. here), that you could vote for.
- Thus what you have belongs to Feature Requests.
- What you describe is a very specific folder structure that may fit your specific needs, but not the needs of many others.
- Logseq tries to be generic enough for serving many different needs.
- You may find better support asking instead for customization.
If you don’t mind, I would like to question your approach:
- Assets are not knowledge, so managing those is not exactly knowledge management.
- Knowledge is not about grouping things together, but about associating them with each other.
- This results in a graph (the scientific meaning of it).
- Parent-child relationships in Logseq are just a specific type of association, not meant to exist at the folder level.
- A hierarchical tree is just a type of graph.
- Knowledge is not about grouping things together, but about associating them with each other.
- If e.g. Minecraft is a topic full of “saves, screenshots, settings, videos etc.”, I would expect to dedicate not a single Logseq page (and thus a single
.md
file), but a full Logseq graph (and thus multiple.md
files) to Minecraft alone.- Within that graph there would still be a central page named
Minecraft
, but most of the assets would be in other pages, referencing this one.- They would still be visible in this one, not needing to navigate away.
- In Logseq a graph already has its own folder and subfolders.
- Again this structure is not currently customizable.
- There is currently no good way for inter-graph integration.
- This is another request.
- Within that graph there would still be a central page named