Thank you for contributing to this workshop. Follow these guidelines to maintain consistency across all labs.
- Fork this repository
- Create a feature branch:
git checkout -b feature/your-change - Make your changes following the style guide below
- Test locally with
bundle exec jekyll serve - Submit a pull request
- Use second-person voice ("you", "your")
- Use present tense and active voice
- Keep instructions direct and concise
- Avoid jargon without explanation
Every lab follows this structure:
---
permalink: /labs/lab-XX
title: "Lab XX: Title"
description: "Brief description"
---
# Lab XX: Title
| | |
|---|---|
| **Duration** | XX min |
| **Level** | Beginner / Intermediate / Advanced |
| **Prerequisites** | Lab NN |
## Learning Objectives
- Objective 1
- Objective 2
## Exercises
### Exercise X.1: Title
Step-by-step instructions...
## Verification Checkpoint
- [ ] Check 1
- [ ] Check 2
## Next Steps
Proceed to [Lab NN: Title](lab-NN.md).- Always specify the language:
powershell`,bash, ````json, etc. - Show expected output in separate blocks when relevant
- Use
> [!NOTE]for informational callouts - Use
> [!TIP]for helpful suggestions - Use
> [!WARNING]for caution notices
- Store in
images/lab-XX/directories - Name format:
lab-XX-descriptive-name.png - Reference format:
 - Every screenshot directory has a
README.mdinventory - Alt text must be descriptive for accessibility
- Use relative links between labs:
[Lab 01](lab-01.md) - Use relative links for images:
../images/lab-XX/filename.png
Mark exercises that require Azure with:
> [!NOTE]
> This exercise requires an Azure subscription (full-day tier only).