
What shipped
A lab can now carry its own guide. You write the guide in the portal, on the lab editor, and it travels with the lab from then on.
Learners on a Hosted Lab Page see the guide beside their environment. If you deliver labs through the API instead, the same guide comes back as structured content, so you can render it in your own pages.
Why we built it
Before this, the guide lived in your course and the lab lived with us. Two halves of one exercise, in two systems, maintained by two people.
That split costs you every time a lab changes. A renamed resource or a new step means editing lesson text in a platform that has no idea the lab moved on. Learners hit the mismatch before anyone else does.
Keeping the guide with the lab makes one person responsible for both, and one edit enough.
What a guide can hold
- Objectives, so the learner knows what the lab is for before they start.
- Step-by-step tasks, with knowledge-check questions along the way.
- Screenshots and images, uploaded in the editor or pasted straight into the text.
- Architecture diagrams, shown in their own tab and ordered the way learners should meet them.
- Downloads and reference links, listed next to the guide.
- A completion section for what to do after the lab.
Why this is only phase 1
Phase 1 covers authoring and delivery: getting guide content written in one place and out to learners.
Phase 2 is on the roadmap. It is about what happens while a learner works through the guide rather than what the guide says.
See everything else that shipped on the changelog, or what's coming next on the roadmap.
