Capstone — Build and Share a Project Folder

Lesson 8 · taught by Pip

Here is the plain idea: you now know the whole everyday toolkit — find your spot, look around, move, make, copy, rename, and run. In this final stop you'll use all of it together to build something real: a tidy project folder, made entirely by typing, that you can screenshot and share to prove you did it.

Think of setting up a fresh workshop. You pick a spot, hang a sign with the workshop's name, then add labeled shelves — one for notes, one for drafts, one for finished work. By the end, anyone walking in can tell exactly what goes where. That clean, self-explaining space is what you're building, in folder form. 🔦

Step 1 — Pick your spot and make the project

Open your terminal and go somewhere comfortable, like your home folder. (pwd means "print working directory" — it tells you where you're standing.)

cd ~
pwd
mkdir my-first-project
cd my-first-project

Run pwd again — you should see my-first-project on the end. You're standing in your brand-new, empty workshop.

Step 2 — Build the shelves

Make three labeled folders, one for each kind of work. (mkdir means "make directory" — a directory is just another word for folder.)

mkdir notes
mkdir drafts
mkdir final

Run ls to list what's there and admire your three shelves.

Step 3 — Fill it with files

Add files in the right places. (touch makes a fresh, empty file.) First a readme at the top, then a file on the notes shelf:

touch readme.txt
cd notes
touch ideas.txt
cd ..

Notice the moves: cd notes steps onto the shelf, touch adds the file, and cd .. steps back up to the project. (.. means "the folder one level up.")

Step 4 — Copy and rename to tidy up

Make a rough draft, then promote a clean copy to the final shelf with a tidier name. (cp copies; pointing it at a new name renames the copy on the way.)

cd drafts
touch chapter-one-rough.txt
cp chapter-one-rough.txt ../final/chapter-one.txt
cd ..

The rough version stays safe in drafts; a clean copy now sits in final.

Step 5 — Print the tour

Now run a program to show off your work. There's a lovely one called tree that prints your whole folder as a neat diagram. Type tree and you'll see something like:

my-first-project
├── drafts
│   └── chapter-one-rough.txt
├── final
│   └── chapter-one.txt
├── notes
│   └── ideas.txt
└── readme.txt

Don't worry if your order looks a little different from mine — tree usually lists things alphabetically, not in the order you made them, so the lines may shuffle. What matters is that all the right files sit on the right shelves.

If tree isn't installed, no worry — use what you know: run ls at the top, then ls notes, ls drafts, and ls final to show each shelf in turn.

Your turn

Build the whole thing top to bottom, exactly as above, then run tree (or the ls tour). When the diagram appears, take a screenshot. That picture is your proof — a whole organized project, every folder and file placed by hand, by typing. Share it with a friend, or just keep it. You earned it.

You did it

Look back at what just happened. You opened the scary blank window, found your place, looked around, walked between folders, made new ones, filled them with files, copied and renamed, and ran programs to show your work. That's not a beginner peeking in — that's someone using the command line.

The terminal was never a hacker's lair. It's a calm counter where you order by name, and you now know enough words to be a regular. Whenever you forget one, you have the pattern: a program, maybe a flag, and the things to act on. The rest is just looking up local spellings.

Fair winds, keeper. The harbor's yours now. 🐙