Zero to Terminal

From “I’ve never used a terminal” to “I deployed a website using nothing but the command line”

---

Who Is This Track For?

This track is for absolute beginners. No IT or coding background is assumed; use each module’s platform guidance and setup notes as you go.

Maybe you’re:

• A student curious about technology
• Someone switching careers into tech
• A non-technical person who wants to understand what developers do
• Someone who’s been told “just open a terminal” and felt lost

You are welcome here. Every expert was once a beginner.

---

What You’ll Learn

By the end of this track, you’ll be able to:

• Understand what’s happening inside your computer (and why it matters)
• Use the terminal (command line) to navigate, create, and manage files
• Edit files using a text editor right in the terminal
• Understand networking, servers, and how to connect to them remotely
• Know what “the cloud” actually means (spoiler: it’s not magic)
• Deploy a real website using nothing but the terminal

This track leads into the main prerequisites route — Cloud Native 101 and then Kubernetes Basics — with Linux Deep Dive as an optional systems-internals fork you can take anytime.

Optional first-terminal preview

Before starting the ordered route, you may preview the existing terminal opening and prompt guide and first safe-command exercise. Use Module 0.2’s own platform guidance. Then return to Module 0.1 and complete the modules in order; the preview does not replace the track.

---

The Restaurant Kitchen Analogy

Throughout these modules, we use a restaurant kitchen as our running analogy:

Computer Concept	Kitchen Equivalent
CPU	The chef (does the work)
RAM	Counter space (temporary workspace)
Disk/SSD	The pantry (permanent storage)
Operating System	The restaurant manager
Programs	Recipes
Terminal	Talking directly to the kitchen staff
Server	A restaurant kitchen (serves many customers)
Cloud	Renting a commercial kitchen instead of building your own

Use the kitchen table as an optional orientation aid for the terms listed above. It does not replace the technical explanations, platform notes, or exercises; skip the analogy if it obscures the terms.

---

Modules

Module	Title	Time	What You’ll Learn
0.1	What is a Computer?	90–120 min	CPU, RAM, disk, OS — the kitchen hardware
0.2	What is a Terminal?	90–120 min	Opening and understanding the terminal
0.3	First Terminal Commands	80–100 min	Navigate, create, move, and delete files
0.4	Files and Directories	90–120 min	Paths, file types, organizing your filesystem
0.5	Editing Files	80–100 min	Edit files with nano, write your first script
0.6	Git Basics — Track Your Work	90–120 min	Track your work with Git — init, add, commit, log
0.7	What is Networking?	90–120 min	IPs, ports, DNS — how computers talk to each other
0.8	Servers and SSH	80–100 min	What servers are, how to connect remotely
0.9	Software and Packages	80–100 min	Installing and managing software from the terminal
0.10	What is the Cloud?	80–100 min	Cloud computing, AWS/Azure/GCP, where K8s fits
0.11	Your First Server — Putting It All Together	90–120 min	Capstone: deploy a real website using everything you’ve learned

These are planning estimates copied from the eleven module headers, not measured learner completion times. Their arithmetic gives an aggregate range of 940–1220 minutes (about 15 hours 40 minutes–20 hours 20 minutes); individual setup, reading, and practice time will vary.

---

How to Use This Track

1. Go in order. Each module builds on the last.
2. Do the exercises. Read the explanation, try the task, and compare your result with the success criteria.
3. It’s okay to be slow. Speed comes with practice, not pressure.
4. Re-read if needed. Professional engineers re-read documentation constantly.
5. Take breaks. Your brain needs time to absorb new concepts.

---

What’s Next?

On the suggested prerequisites route, continue straight into Cloud Native 101 and then Kubernetes Basics—the linear spine from terminal skills to hands-on cluster work.

Default next step: Cloud Native 101 — containers, Docker, and the cloud-native ecosystem.

Optional fork: Linux Fundamentals if you want deeper operating-system knowledge before operations-heavy work. Linux is not required for the main route; you can return to it anytime.

If you are unsure where to go, start with Cloud Native 101 and keep the Linux path as an optional parallel route.

               Zero to Terminal
                     |
              Module 0.11 (Capstone)
                     |
          Cloud Native 101  (default — suggested route)
                     |
            Kubernetes Basics
                     |
                     ...

          Linux Deep Dive  (optional fork — anytime)

---

Time Investment

The module-header planning range is about 15 hours 40 minutes–20 hours 20 minutes. It is an unmeasured estimate, not a completion promise; setup, reading, and practice can take longer.

---

Start with one action. Try it, check what happened, and ask questions before moving on. You do not need to master the whole track in one sitting.