Uh-oh... I'm going to answer this. n_n

99% just dirs in ~/. ( Does making new dirs in /bedrock/strata count when manually adding strata? That'll be about all there is in the other 1%. )

• ~/bin
• ~/gittings
• ~/gittings/Digit (where I keep my local copies of my own git repos)
• ~/images
• ~/images/scrots
• ~/images/ all the different things like dsktpbckgrnds, charts, memes, photos, gifs, etc & EDITS where I save most GIMP file artwork
• ~/sounds
• ~/.fonts (if the system does not create this already... so I can put my big tiny font collection "dbtfc" of otb and ttf fonts I made, in there, and have them "just work").

Oh, and this one's a little fun:

• ~/testdir in which i make a dir, a file, a media file, an executable, a fifo, a symlink, and a broken symlink, so I can ls that dir to see how everything looks in new themes.

And locations for my sshfs mounts and external drives (faster to type than putting them each in ~/mount or ~/media or ~/mnt).

• ~/bb
• ~/o
• ~/m or ~/t as symlinks to ~/mozart and ~/tyson depending on if on tyson or mozart. (I name my thinkpads after famous people born on the same day it arrives in the post).

And then on bb external hd, loads of dirs, some notable ones

• ./bkps
• ./software
• ./software/distros (where I store ISOs and system tarballs)
• ./software/configs/ ; crypto/ ; doc/ ; games/ ; langs/ ; other/ ; virtuals/
• ./cinema/
• ./cinema/library (hiding the library in cinema, so I see it more often ;D)
• ./cinema/_docu (for documentaries, lectures, interviews, etc)

And on the webserver

• ~/web
• ~/web/stuff
• ~/stuff (symlink to ^, that I use like my own personal pastebin) (... ~/o/stuff, from local machine).

~/git

Everything else is managed by Ansible or synced via Synthing (except ~/Downloads).

~/tmp

~/temp

~/temper

~/tempest

~/misc

/mnt/other (symlinked)

~/bin/ which I add to my $PATH

~/Repos (For all the github and other code repositories I work in)

~/Scripts (All my random Bash scripts, sometimes for testing out stuff)

~/Junk (Mostly used for testing programs or small project components that aren't mature enough to have their own repo)

$HOME/temp, $HOME/git, ln -s $HOME/git/scripts $HOME/scripts

Separate folders in the download one. One for each app. And a separate /home/sync folder with the same app separation folders to safekeep the backups of android apps and DCIM folder.

~/nixos/ for my NixOS config ~/repos/ for git repos ~/audio/ for my sound library and recordings

Code goes in the Developer folder

(I got used to that name on macOS, where it is the "canonical" name for it, because it automatically gets a special icon)

I make an ~/all/ directory as a catchall for things that don't fit elsewhere, since ~ is used by so many automatic softwares and config files, I like having a place that only I'll write to.

I also make ~/bin for general use and ~/all/GitHub/ for software I install from GitHub.

~/Scripts for any bash or python scripts
~/Gits for any repos I clone
~/Projects for any projects im working on (not organized by programming language, but I do have some dirs called zig, go, etc., for when im learning a new language and want to make some projects for learning purposes)

Most other files go into ~/Documents if they don’t have a home already, or don’t fit into the above directories

Public - for everything im seeding and sharing

Apps - for all app images

Games - for all lutris spam and random failed attempts at installing mods.

~/Projects which has everything I ever cloned or started. yes, it's getting kind of painful to backup :D

~/code for code

~/dots for git-backed nix configs

~/.rt for projects compiled locally ("runtime")

~/Screencast for recordings of my screen

I also create a ~/.shrc.bash symlink that points to ~/dots/bash/bashrc that reats ~/dots/bash/*.bash and sources the files

~/.shenv.bash where I keep environment (computer) specific settings

/datapool or whatever the array is called for zfs pools, I often do /mail on mail servers, and /www on web servers. Not sure why but it makes it super obvious what's going on when you login remotely

I don't, on most machines, which are servers of some sort. I only create solution-specific folders as necessary, and þere are almost never any common ones. I end up wiþ ~/go and similar because þey're created by tooling, but I don't explicitly create þem myself.

For my PCs, I've been carrying forward my ${HOME} for over a decade. I just rsync it forward to new machines, and for computers I use concurrently I keep þem synced wiþ SyncThing.

My homedir is an infernal hellhole of junk accumulated over the past 15 years and I wouldn't have it any other way

My home folders on any OS have a Development folder (which conveniently sits right next to Documents and Downloads) and in that folder, I’ve also got subfolders per programming language that have the respective projects in them.

The other folder I usually have is SyncThing with whatever synced folders are relevant for that machine.

Multiple people in this topic say they organise in directories for different programming languages, something I have never considered and I find it to be an odd way of organising for some reason I can't explain.

Where do you put a project with a Javascript frontend and a Python backend?

~/3D Objects

~/Homework (porn)

~/aaaaaaa (porn)

~/Stuff (memes, with a porn subfolder)

~/misc (work docs, study docs, forms, some porn)

At least two of these:
~/Stuff
~/Stuffs
~/Stuffz
~/Shits

I have /home/username/username/ and I sym link important dirs (like Downloads) to my new home. I strongly dislike all the dot files and dirs cluttering up my home dir.

• /ram - tmpfs filesystem
• ~/.local/bin - added to my path
• ~/.local/software - any user-local program more complicated than a binary gets a directory here. Generally a binary would be symlinked to ~/.local/bin
• ~/.local/venv - shared python venv to use for one liners and small scripts
• ~/repo - local filesystem backed package repository for which the host system is configured to install from
• ~/.local/repo - local filesystem backed package repository for which the host system is not configured to install from (used for mock, VMs, and external systems).
• /overflow - Used to point to a large secondary hard drive (back when having a small ssd was the economical thing to do. Nowadays, it is just where my large directories go cause I can't be bothered to get used to a more sane setup

~/Projects

Hardware folder (synced via sync thing). All hardware PDFs, notes images etc get subfolders by manufacturer. It is helpful for keeping track of use manuals, firmware or config settings for each piece of hardware.

~/proj
~/note
~/sync
~/docs (/book etc)
~/imgs ~/util ~/test ~/temp

Archive

Archive archive

Archive_11_2025

I am not good at organizing

~/dev for code
~/work for things I don't want to do, like taxes