Labs & Content

Everything you learn on escbash — every roadmap, skill, topic, and step — is plain, versioned content: folders and YAML files in a git repository, loaded by the platform and served read-only. No CMS, no database of lessons. This page is the learner's view of how that content works.

What a topic is made of

A topic is an ordered list of steps, and each step has a kind:

• Concept — read or watch; explains before you do. Never graded.
• Guided task — the lesson shows you exactly what to run and decodes every line; Submit checks that it worked on your machine.
• Independent task — a goal and hints about the route, but the commands are yours to figure out. Same checks, less hand-holding.
• Challenge — a mission statement and nothing else: no hints, no walkthrough.
• Scenario — a judgment call ("you're about to push a key in a script — what's the right move?"). Every answer teaches; the best one is graded.
• Quiz — a quick recall check. Some quizzes grade against your live machine — "run nproc — how many cores?" — so the answer comes from your own session.

Why checks make it real

Every graded task follows one rule before it ships: its checks must fail on a fresh machine and pass after the work is done. A check that passes on an untouched VM verifies nothing and is treated as a bug. That discipline — verified against real sessions, not just reviewed — is why a green Submit actually means something.

Where content comes from

Content lives in its own repository and is written by the escbash team and content creators, in the open-friendly format described in the Creating content section (visible to creator accounts). If a lesson confused you or a check felt wrong, that's a content bug — report it and it gets fixed like code, because it is code.