Before computers had graphical desktops, the home directory was the desktop. Everything that mattered lived there. Documents, programs, configuration, mail, scripts, and even your identity on the machine were organized beneath a single directory tree.

Modern desktop environments have made this less obvious. We are encouraged to think in terms of “Documents”, “Downloads”, and “Pictures”, while the directories that actually make the system ours remain hidden behind a leading period. Yet for a textsmith—someone who thinks in plain text and treats the computer as a workshop rather than an appliance—these hidden places are every bit as important as the visible ones.

Today I’d like to take a small tour of the workshop.

A carpenter knows where every tool hangs.

A mechanic knows which drawer holds the right spanner.

Likewise, a textsmith gradually learns that productivity comes not from owning the latest software but from understanding where things live. Once you know the layout of your workshop, maintaining your system becomes easier, backups become meaningful, and moving to another machine becomes almost routine.

These five locations form the heart of my own Linux workspace.

1. ~/Documents — Your Library

This is the obvious one.

For many people it is simply where Word documents accumulate. For a textsmith, however, it becomes something richer.

Inside might live:

• Markdown manuscripts
• Quarto projects
• Typst documents
• LaTeX papers
• notes
• shell scripts
• source code
• CSV data
• plain text journals

The important observation is that nearly all of these are simply text.

A 200-page book may occupy only a few hundred kilobytes because it consists mostly of words rather than formatting instructions.

The result is a library that is easy to search with grep, version with Git, synchronize with rsync, or archive for decades.

Your documents are not just files.

They are knowledge.

2. ~/Downloads — Your Receiving Dock

Every workshop needs somewhere to unload deliveries.

Downloads is intentionally temporary.

Packages arrive here.

PDF manuals.

Compressed archives.

Software releases.

Datasets.

Installation images.

Many users allow this directory to become a museum of forgotten files. Mine rarely survives a month without a cleanup.

Think of Downloads as the loading bay rather than permanent storage.

Once something proves useful, move it to its proper home.

A tidy workshop saves time.

3. ~/.config — The Workshop Settings

If Documents stores your work, .config stores how you work.

This directory quietly remembers thousands of decisions you’ve made.

Perhaps it contains:

~/.config/

vim/
git/
kitty/
alacritty/
bat/
fd/
ripgrep/
mpv/

Open one of these files and you’ll discover something delightful:

They’re almost all plain text.

A font size.

A color scheme.

A keyboard shortcut.

A default directory.

A startup command.

Every setting represents a conversation between you and your software.

Unlike the Windows Registry—which inspired much of my own appreciation for configuration files—these settings are transparent, editable, searchable, and easy to version-control.

The computer begins to explain itself.

4. ~/.ssh — Your Identity

One of the most overlooked directories on Linux is also one of the most important.

~/.ssh

To many people it looks mysterious.

To a system administrator it is home.

This directory commonly stores:

• SSH keys
• known hosts
• configuration files
• agent settings

In a sense, this directory contains your passport.

When you log into a remote server…

ssh server.example.com

…your machine proves who you are using the credentials stored here.

GitHub repositories.

Personal servers.

Cloud machines.

Virtual private servers.

All of these become far easier once SSH is understood.

Protect this directory carefully.

Back it up wisely.

Never publish its private keys.

5. ~/.local — Your Personal Workshop

Linux separates software installed for the whole system from software installed just for you.

That personal world often lives beneath:

~/.local/

Depending on your system you might find:

~/.local/bin
~/.local/share
~/.local/state

This is where user-installed applications, scripts, fonts, icons, caches, and local data often reside.

I particularly appreciate:

~/.local/bin

because it allows me to install my own helper scripts without needing administrator privileges.

Need a small script that converts Markdown?

Place it here.

Need a wrapper around rg?

Place it here.

Need a quick backup command?

Again, this is an excellent home.

As your collection grows, your personal toolbox grows with it.

Do Not Forget $HOME

Curiously, some of the most important files aren’t inside any directory at all.

They sit directly in your home directory.

For example:

~/.vimrc
~/.bashrc
~/.profile
~/.gitconfig
~/.mbsyncrc

Each one teaches another program how to behave.

These files are wonderfully ordinary.

Open them in Vim.

Read them.

Search them.

Edit them.

Over time they become a written record of your computing habits.

When people ask why my editor behaves differently or why certain commands seem so natural on my machine, the answer is usually hidden inside one of these files.

The computer is behaving exactly as it was instructed.

Your Home Directory Is More Than Storage

One of the pleasant surprises awaiting anyone who moves from merely using Linux to understanding Linux is the realization that the home directory is not just somewhere to keep files.

It is your workshop.

Your identity lives here.

Your tools live here.

Your preferences live here.

Your projects grow here.

Your automation begins here.

For a system administrator, learning these directories means understanding how a machine is assembled.

For a textsmith, it means understanding how ideas flow from keyboard to document, from document to publication, and from one computer to the next.

The more familiar you become with your home directory, the more reproducible your environment becomes. A carefully maintained $HOME can often be backed up, placed under version control, or restored onto a new machine with remarkably little effort. That is one of the quiet powers of plain text: your workspace becomes something you can understand, preserve, and rebuild.

The Unix tradition has always encouraged us to think of the computer as a collection of understandable pieces rather than a sealed appliance. Learning these five directories is a small step in that tradition. Like learning where the chisels, planes, and measuring tapes belong on a workbench, it may seem mundane at first—but it pays dividends every day thereafter.

Because every good craft begins with an organized workshop, and every good workshop begins at $HOME.

• The Workshop

• Reproducible Computer
• System Administration
• Configuration Files