Your writing may be organised in your head, but what about the hundreds of files accumulating on your computer? This guide explores how a few simple terminal commands can help bloggers organise, find, copy, and back up their work without becoming programmers.
The Quiet Power of the Terminal
A plain-language guide for writers, bloggers, and anyone who keeps files
Most of us meet our computers through pictures. We click a folder, drag a file, tap an icon, and trust the machine to understand. It usually does. But beneath that friendly surface lies an older and quieter way of speaking to a computer: plain, typed instruction.
It is called the terminal, and it has an undeserved reputation. Many people assume it belongs exclusively to programmers, system administrators, and the technically initiated. It does not. For anyone who writes regularly and accumulates files, the terminal is less a programming tool than a filing system that answers immediately.
What a Terminal Actually Is
A terminal is a text-based interface that lets you communicate directly with your computer’s operating system. You type a command; the computer carries it out. There are no menus, no icons, no windows to navigate. There is only an instruction and its result.
Instead of opening a file manager, clicking through to your Documents folder, and searching for the right place, you type:
| cd Documents |
And to create a new working folder:
| mkdir MyProject |
Every major operating system ships with one. On macOS and Linux, it is called Terminal. On Windows, you will find Command Prompt and PowerShell. The commands differ slightly between systems, but the core idea is identical.
In one sentence: the terminal is a text-based way to control your computer.
Why a Writer Should Care
Let me be clear at the outset: you do not need to become a programmer, and you should not use the terminal to write your posts. Your drafting tools—Notes, Pages, Word, WordPress—remain exactly where they are.
The terminal earns its place in a writer’s workflow for three tasks, each of which it performs faster and more reliably than clicking:
• Organising: Arranging drafts, images, research, and archives into a structure that holds up over years rather than weeks.
• Finding: Locating a single file among hundreds, by a fragment of its name, in a second or two.
• Backing up: Duplicating an entire body of work before you make a change you might regret.
Consider what accumulates after three years of steady writing: drafts, revisions, published versions, images, reflections, research notes, and SEO material. Hundreds of files, scattered across folders that made sense at the time. Graphical tools handle ten files gracefully; they handle a thousand badly.
There is also something quietly satisfying in the form itself. A terminal command is an instruction with no ambiguity in it. It states its subject and its object, it does precisely what it says, and it does nothing more. Anyone who has spent a career drafting clauses or precise prose will recognise the discipline.
Ten Commands Worth Knowing
You do not need hundreds of commands. Ten will cover almost everything a writer needs.
1. Find out where you are
| pwd |
Short for “print working directory”. It shows the folder you are currently working in—the terminal equivalent of looking up at a street sign.
2. See what is in front of you
| ls -l |
Lists the contents of the current folder. Adding the -l flag (lowercase L) gives complete details, including file sizes, permissions, and modification dates.
3. Enter a folder
| cd “Rise & Inspire” |
Quotation marks matter whenever a folder name contains spaces or symbols. Without them, the computer interprets the space as the start of a separate instruction.
4. Step back one level
| cd .. |
Two dots mean “the folder immediately above this one”. Note the space between cd and the dots. Typed completely alone, cd returns you directly to your home directory.
5. Create a folder
| mkdir “Sunday Series” |
Creates a single directory with the specified name.
6. Create several folders at once
| mkdir Drafts Published Images SEO Archive |
This single line builds an entire filing hierarchy in one stroke. It is usually the exact moment people understand why the terminal is worth learning.
7. Copy a file
| cp article.docx Archive/ |
The original file remains in place; an identical copy is placed inside the Archive folder.
8. Move or rename a file
To move a file into a folder:
| mv article.docx Archive/ |
To rename a file:
| mv old-name.docx new-name.docx |
The same command performs both operations. To a computer, moving and renaming are the exact same concept: assigning an item a new path address.
9. Search for a file
| find . -iname “*reflection*” |
Searches the current folder and every subfolder inside it for any file containing the word “reflection” (regardless of uppercase or lowercase). The full stop represents “start from here”; the asterisks stand for “any text on either side”. Once your archive reaches hundreds of documents, this single command repays the entire exercise.
10. Open the current folder in your visual file manager
| open . |
On macOS, typing open . (with a space before the dot) instantly opens your current terminal folder in Finder. On Windows PowerShell, the equivalent is explorer . and on Linux desktops, xdg-open . — serving as the direct bridge between the typed world and the visual one.
You can also open an individual file directly from the terminal:
| open reflection.docx |
A Folder Structure Worth Copying
Structure is the ultimate point of this discipline. Here is a clean, scalable layout adapted for a consistent publishing workflow:
| Rise & Inspire/ ├── Sunday Bible Series/ ├── Wake-Up Calls/ ├── Daily Prompts/ ├── Drafts/ ├── Images/ ├── SEO/ └── Archive/ |
The principle is simple: one folder for each recurring category of work, one for material in progress, one for what supports it, and one for what is finished. A structure you can predict is a structure you can search.
Backing Up Before You Change Anything
To duplicate an entire folder and everything inside it:
| cp -R “Rise & Inspire” “Rise & Inspire Backup” |
The -R flag stands for “recursive”, instructing the system to travel down through every subfolder rather than copying only top-level items. Run this command before any major reorganisation. It takes one line, executes in seconds, and protects against regrettable mistakes.
One Crucial Safety Rule
| Rule of Thumb: Do not use rm (the delete command) until you are entirely comfortable. Files removed through the terminal bypass the Trash and Recycle Bin entirely. They are purged immediately without confirmation. The terminal assumes you meant exactly what you typed—which is its great efficiency, but also its one real danger. Everything else in this guide is fully reversible. Deletion is not. Continue using the graphical Trash for deleting files, and reserve the terminal for creating, organising, finding, and copying. |
Where to Begin
Begin with five foundational commands, and only five:
| pwd | Locate yourself and see exactly where you are. |
| ls | Look around and view the contents of the current directory. |
| cd | Move between folders smoothly. |
| mkdir | Build a clean new folder. |
| open . | Return quickly to familiar ground in your visual file manager. |
Practice them for a week on practice folders that do not matter. Once the sequence feels natural, copying, moving, searching, and backing up will follow effortlessly.
There is a broader lesson buried in this small subject. The terminal rewards precision. It does not guess at intention, forgive a misplaced quotation mark, or soften a command it suspects you did not mean. You must say exactly what you want, in the right order, using the exact words.
That is not a bad discipline for a writer to keep company with. Most of our difficulties on the page come from the very same source: an instruction to the reader that was not quite clear enough to follow.
A few simple terminal commands turn scattered draft files into a reliable archive.
Over to You
What is the one file you have lost, searched for, and never found again—and would a folder structure you could actually predict have saved it?
Explore more at the Rise & Inspire archive | Tech Insights |
© 2026 Rise & Inspire.
Website: Home | Blog | About Us | Contact| Resources
Word Count:1353