Checkout this workflow:
Over email, I had to exchange a number of important financial documents regarding a real-world topic, which has aspects that go beyond digital life, but also I tend to excerpt an unreasonable amount of control over these types of document exchange. For instance, one of the imperatives for me is that files must be grouped in one place. Cause at the end of the day, you know that tools come and go. Although I think Logseq and I are married for life, but still it’s that conservative way of thinking in specific situations that ask you to not overthink it. Make a folder, put them there.
And this is the twist of this workflow. HEY.com people have understood this nuance very well. As an email client, IMHO they represent the state of the art in their category.
- Now, imagine I already have a folder in Dropbox or a backed up file system node [^1].
- The name of this folder usually corresponds to a well-known topic that is well-documented.
- The odds are good that the topic in Logseq was even created before the file exchange.
- Or not. Either way,
- Cmd+K and BAM, I’m on the topic. I just drop the files and start typing.
- I as the artist of my knowledge graph will make sure that when I find my topic, that I land under:
~ws/2022/Budget Forecast 2023
and this is mapped to
/Users/skh/ws/2022/Budget Forecast 2023
on the filesystem
Here’s the twist, this can only happen if Logseq follows subdirs. Because I need to be connected to the filesystem context so the files land, exactly where I want them to, rather than all in assets.
And in fact, it’s the disconnect between the filesystem context of the assets and that of the topic page, that is the key to understanding my argument here. For real world topics, some want control, some want files grouped in classical directories. In fact, Logseq does present filesystem parity as one of its main features and rightly so. You guys are gods in what you do. But this breaks that imperative.
[^1]: Backed up of course because these are things I intend to keep for 7 years (at least) (required by Belgian law)
cc @Didac