Workspace-specific Foam functionality

[wetlandscapes]

Is your feature request related to a problem? Please describe.

First, thank you all so much for the amazing package. I'm just starting to play around with it, but there is a lot of potential here. And the vscode integration is just great.

This is related to #683. A lot was discussed in that pull request, but it looks like it stalled, so I just wanted to bump it, as some of the functionalities discussed would be extremely useful. Specifically, it looks like the contributors were a bit overwhelmed by all the possible options that might need to be implemented for both primary and edge cases. So, I'm just providing my use case to highlight some core functionality that might be valuable to the majority of folks, and encouraging the contributors to worry about edge cases later (perhaps the suggestion is naive, but sometimes perfect can be the enemy of good enough -- and I mean that with the best of intentions, as I think this project is already great).

Describe the solution you'd like

My use case is that I have a "main" second brain for personal use, so the core functionalities already provided work great. But I also have "satellite" second brains for specific projects with collaborators. For my satellite projects I would like to be able to store all my Foam notes in a subdirectory to the main project, as there are other concerns that need to be placed in the main directory of my workspace (e.g., website functionalities). I also don't want Foam to think all my other folders need to be mapped/connected (e.g., via the graph), but don't want to have to add every single folder to the exceptions in the settings.json file (which I think I would need to do if using Foam from the project root).

In that context, it would useful to just be able to change the location of the ${projectRoot} to something else. I only every plan to use Foam in the context of a workspace, if that helps simplify things (I think that's probably most other users, as well).

Describe alternatives you've considered

For my satellite projects, I'm hosting Foam notes in a notes/ subdirectory. When I create new linked notes using [[]] they are automatically generated in this directory, which is nice, but if I create new notes from the command palette, they are created in the workspace's root, so I have to manually move them, which is not terrible, but does become a hassle on particularly prolific note taking days.

Screenshots or Videos

No response

[riccardoferretti]

hi @wetlandscapes thanks for sharing your workflow, I had never come across one like this, it's pretty interesting.

The discussion in the PR with @movermeyer has been very helpful, even though in the end didn't reach a conclusion. I agree we should try to simplify our approach there, and probably the key is accepting edge cases to be handled in an ad hoc matter (basically what we were converging to in the PR discussion).

IIUC your workflow, it would be supported by the solution we were drafting there right? For any other point regarding to the approach to take it would be useful to continue the conversation on the PR.