Learn one systems skill.
Document what runs.

Use Notion for the study path, lab notes and mistakes—not to pretend that a dashboard can run containers, clusters or infrastructure plans.

Choose one practical goal before collecting tools

Start with one goal: understand Linux command-line work, write a small systems program, run an application in a container, or describe infrastructure safely. Do not sign up for every track. C, C++, Rust and Go are language options, not mandatory prerequisites for learning Git or Docker.

Write a single outcome in your workspace, such as “Build and document one local containerized service.” Add a checklist for the concept, one reproducible lab and a note about the remaining limitations. Mark tutorials as references rather than evidence of working software.

If you are still learning programming basics, start with the beginner coding roadmap before choosing a systems or container lab.

Keep a terminal and Git field notebook

Create a Commands database with a purpose, shell or operating system, exact command, expected output, actual output, date tested and link to a trustworthy source. Use disposable paths and sample repositories in examples. Never paste passwords, secrets, production tokens or private keys into a publicly shared template.

The Terminal Commands template is a source-listed reference for Windows, macOS and Linux commands. Git Version Control is a separate reference for commits, branches and recovery workflows. Neither runs commands from within Notion; practice in a local shell and confirm any command against your environment.

Make a small Docker lab you can repeat

Before adding Kubernetes, build a small local application image, run it, examine logs and volumes, stop it cleanly and record how to reproduce the result. Keep a short file inventory, command sequence, chosen ports and an explanation of where data survives.

The Docker & Containers template can organize study notes, examples and follow-up questions. Your actual Docker installation and host configuration control whether a command succeeds. Treat template descriptions as source claims, not proof that this article executed any container.

Choose Kubernetes or Terraform only when the project needs it

Use Kubernetes when your learning goal involves workloads, deployments, services and cluster operations. Use Terraform when your goal involves declarative infrastructure configuration, state and plan review. They solve different problems and neither is required for every small application.

Keep a separate notes page for the selected track. Include the environment, version, smallest reversible change, expected result and a screenshot or log only after you genuinely test it. Never run a destructive infrastructure command from a copied tutorial without first reviewing the target and plan.

A simple workspace schema for technical learning

Create four sections: Current Project, Concepts, Labs and Mistakes. Each lab links to one concept, names the tool version and operating system, stores sanitized commands, and records an actual pass, failure or not-yet-tested state. Put source links beside any copied command.

Weekly review: pick one unfinished lab, reproduce it from a clean environment, repair outdated notes and archive examples that depend on unavailable services. Your Notion dashboard tracks learning artifacts; the compiler, terminal, container engine and cloud provider perform the work.

What this guide does not verify

The referenced source pages list technical learning templates; no live checkout, duplication, lesson-completeness audit, environment execution, provider uptime, compatibility or current template-language coverage was tested in this writing batch.

Template pages and prices may change. A source-listed free label is not confirmation of an authenticated acquisition. Verify product details, the actual download/duplicate flow and any licensing or version requirements before making a decision.

Pick the relevant reference, not an entire catalog

These links lead to current canonical source-owned product pages. Compare their descriptions, included resources and terms with your own chosen lab before taking the next step.

Common questions

Do I need to study Kubernetes and Terraform together?

No. Start with the problem you are trying to solve. Kubernetes organizes containerized workloads; Terraform describes infrastructure resources. Both are optional for a small introductory lab.

Will Notion execute my shell or Docker commands?

Not through this workflow. Keep sanitized commands and results in Notion, but run the commands in an environment you control and verify the actual output.

Are the listed templates a verified free training environment?

No. Product source pages describe reference materials. Checkout, duplication, hands-on lab execution and current availability need separate verification.