#Teaching

These guides are for instructors and organization admins.

Start with Classrooms to create a class and enroll students. Then use The module library to author and release modules. Stacks groups modules into a shareable sequence, and Previewing a module lets you test one before assigning it.

Briefings covers the instructions students see. Roles and permissions explains who can do what.

For technical authoring, see Building VM images for manifests and Writing a rubric for grading.

Classrooms — A classroom is a group of students working through the same modules. Release a module to a classroom and every enrolled student can run it.
The Module Library — The library is where you prepare modules before releasing them to a classroom. Create, edit, share, and track builds here.
Stacks — A stack is a named, ordered list of modules. Use one when a set of modules is really a sequence: a networking unit taught over three weeks, a contest prep ladder, the labs that make up a semester. The stack keeps that order in the product instead of in a spreadsheet, and it shares as a single unit.
Previewing a module — A preview is your own private copy of a module, running the same image your students would get. It exists so you can walk through a module yourself before you put it in front of a class, and so module authors can check a build before promoting it.
Briefings — A briefing is the HTML prompt students read when they open a module. A clear briefing gives them a confident start and often prevents confusion before it begins.
Roles and Permissions — Rudder Virt has four roles, listed below from least to most privileged. Each role inherits everything the role beneath it can do.