Feature request : Creation of Folders and subfolders, will make knowledge management more feasible

Feedback Feature Requests
1

The Problem

  • We can’t create sub-folders inside folders. Thus all pages are stored in pages folder only, which make clearing the clutter difficult. Deletion of unwanted files.
  • Pdf linking and highlighting creates extra files. If some file name is changed, it doesn’t update the links and reference is lost.
  • Crystallization of thought files not possible due to linkage updation problem, and no specific folders.
  • Though I have tried creating folders inside pages folders, but all the pdf highlights, other assets linked are suddenly not accessible.
  • is the path correct error is shown.
  • also due to no folder categorisation, I can’t keep related resources files together. Retrieving becomes difficult if link is lost.
2

I would love folders, and even better could we have it so namespaces are basically folders?

So in Logseq the page Books/Dune would be pages/Books/Dune.md rather than pages/Books.Dune.md

11 Likes
3

Agree - however I’d personally tweak the feature request to this:

  • We need the ability to easily rename files
  • Create the ability to query files/assets only, by file attributes: type (pdf, doc, wav, etc), modified time, etc

This will allow for a document library, organized/filtered by LogSeq tag and by file attribute, to be embedded on any page.

Personally I hate the folder schema (files can only be in one “folder” at a time) vs. a tag schema.

5 Likes
4

Another upside of a folder structure is being able to have different git repos for different spaces. This would make team collaboration easier.

8 Likes
5

This is almost a deal-breaker for me! It’s too bad because I thought I found the right tool. I need a rich folder structure to sync with Obsidian.

8 Likes
6

Please see Proposal: Changing How Namespaces Function in Logseq.
It’s basically the same idea. Storing namespaces with folders.
It’s on the team radar, but it will take a while

1 Like
7

What do you think about moving Proposal: Changing How Namespaces Function in Logseq from #bug-reports to #feature-requests? It might be losing visibility for being in the wrong forum category.

8

See also [R] Move assets to dated subfolders for an example of how to move assets into subfolder based on creation date

9

I agree with you. But in my workflow, I work with imposed organisations with specifics folder structure (my clients, team), I work with OmniFocus, and need to work with the same structure of folders, everywhere, otherwise it would be a mess. It’s already happening, because i am creating my PKM in Logseq since a few days (newbie :smile: ).
It would be great to have that option too in Logseq. Because I could use folders (for external needs) but at the same time, using logic of Logseq PKM because I prefer. For the moment, I have separated the 2 worlds because that. It’s a labyrinth …

10

Based feature request.

I also need and am proposing something similar:

1 Like
11

Has this function been added? I still can’t create folders. I would like to have all my Raindrop imports in one folder, Readwise imports in one folder, all my notes in one folder, all my ToDos in one folder, etc.

1 Like