I’ve been refining a way to structure my folders and system drives that moves away from the legacy “filing cabinet” model (Documents, Downloads, Desktop) toward what I call an Intent-Based Filesystem.
Most modern workflows are action-oriented, but our folders are still organized by file type. I’ve consolidated my entire environment into three “mental zones” that dictate how I interact with data.
~/canvas
Replaces:~/Desktop and ~/Downloads
Philosophy:Active Workspace.
The Logic: “Desktop” is an outdated metaphor, and “Downloads” is a graveyard. By merging them into ~/canvas, everything that enters my system lands in a single, high-stakes “Inbox.”
The Benefit: It forces digital hygiene. If a file is in ~/canvas, I’m either working on it right now or I need to move it. It creates visual/mental pressure to either process or discard data.
~/archive
Contains: documents, music, pictures, videos, etc.
Philosophy:Cold Storage.
The Logic: I tucked the standard XDG directories away. I don’t need to see them every time I ls. They are for reference, not for work.
The Benefit: Reduces cognitive load and unnecessary clutter in $HOME. Everything that isn’t for configuration now lives in one of two semantically named folders.
/trunk
Purpose: Mount point for primary high-capacity data drive.
Philosophy:Infrastructure.
The Logic: It’s a double metaphor. In a tree, the “trunk” is the main branch off the root (/). In a home, a “trunk” is a place for storing things.
The Benefit: It’s a memorable, top-level path for games, VM images, and backups. cd /trunk/SteamLibrary is much more intuitive than hunting through /mnt or /run/media.
The “Why”:
Standard XDG layouts treat the computer like a fling cabinet in an office; my setup treats it like an art studio or workshop.
Reduced Decision Fatigue: I never wonder where a file goes. Is it active? ~/canvas. Is it a finished asset? ~/archive. Is it a 100GB game? /trunk.
Semantic Clarity: The names reflect the state of my work, not just the extension of the file.
Curious if anyone else has moved away from the standard ~/Documents / ~/Downloads sprawl in favor of something more “pragmatic”?
I haven’t moved away, but I do automate the movement of files, especially media (images and videos) to folders either for later sorting or based on file names.
I use simple bash scripts that use simple commands like mv and cp with a check for duplicate names to ensure I don’t replace files that are actually different but have the same name.
The Documents, Pictures, etc. folders haven’t been erased from any of my computers; instead, I have moved them all just one level deeper into ~/archive. So ~/Documents is now ~/archive/documents. I probably could have made a point to clarify that in my post.
The idea of something like ~/canvas makes no sense for my use case. I don’t process things like that in workflow fashion so it would just be extra work.
My data drive is actually linked into ~/Documents, ~/Music, etc so it is totally transparent and I don’t have to worry at all about what is on my data drive vs what is elsewhere.
Strictly discerning content by file type isn’t a productive layout. But overall it still works here.
Desktop is the short term scratchpad for my data. Is also synchronized between devices.
Downloads is for stuff that doesn’t originate from me. Can contain big files. Different mount point and excluded from short term snapshots.
Pictures or Music are still mostly self contained areas for me. Same for Movies with a different mount point.
Other stuff goes into Documents, and that has its own organization system. I don’t care if other file types live there.
I create other entries in ~/ as I see fit. But even for those file type is a good indicator. Ebooks are the ebooks. Source code is always source code, and I can e.g. exclude it from file indexing.
But every person has different workflows. So thanks for starting an interesting discussion.
While I understand the concern about portability, it’s worth noting that this layout relies on standard directory structures and mount points, so it should be compatible with virtually any Linux distribution. Of course, as others have mentioned, it ultimately boils down to what makes the most sense for your individual workflow—and that flexibility is really the beauty of Linux!
Yeah I can totally appreciate that it wouldn’t work perfectly for everyone. What you said is ultimately all I was hoping to do—start an interesting discussion.
