Update studio config for training

.claude/README.md

@@ -208,7 +208,7 @@ Automatically runs heading validation when you submit a prompt:
 
 4. **Update Navigation**
 
-   - Manually edit mkdocs.yml to add new content
+   - Manually edit `docs/en/mkdocs.yml` to add new content
    - Or just ask Claude to update it
 
 5. **Preview Locally**
@@ -233,5 +233,6 @@ Consider also using:
 ## Additional Resources
 
 - **CONTRIBUTING.md** - Full contribution guidelines
+- **TRANSLATING.md** - Translation guide (all translations are AI-generated)
 - **Training Site** - https://training.nextflow.io
 - **Nextflow Docs** - https://www.nextflow.io/docs/latest/

.claude/commands/add-exercise.md → .claude/skills/add-exercise/SKILL.md

@@ -1,8 +1,13 @@
 ---
-description: Add an exercise with solution to an existing lesson
+name: add-exercise
+description: Add an interactive exercise with solution to an existing lesson. Creates properly formatted exercise and solution admonition blocks. Use when a lesson needs hands-on practice.
 ---
 
-Add an exercise with solution to an existing training lesson. Follow these steps:
+Add an exercise with solution to an existing training lesson.
+
+See [../shared/repo-conventions.md](../shared/repo-conventions.md) for directory structure and file conventions.
+
+Follow these steps:
 
 1. Ask the user:
 

.claude/skills/check-highlights/SKILL.md

@@ -7,6 +7,8 @@ description: Verify that hl_lines attributes in markdown code blocks correctly h
 
 Verify that `hl_lines` attributes in markdown code blocks are correctly set to highlight the intended lines.
 
+See [../shared/repo-conventions.md](../shared/repo-conventions.md) for file conventions.
+
 ## Critical Understanding
 
 **`hl_lines` is snippet-relative, NOT related to `linenums`**:
@@ -26,13 +28,6 @@ process FOO {      <- displayed as line 21 (snippet line 1)
 `
 ```
 
-## When to Use
-
-- After writing or editing code blocks with highlights
-- When reviewing Before/After comparison blocks
-- When a user reports highlights look wrong
-- As part of lesson review/validation
-
 ## How to Check
 
 For each code block with `hl_lines`:

.claude/skills/check-inline-code/SKILL.md

@@ -7,6 +7,8 @@ description: Review inline code in markdown files for proper formatting and synt
 
 Review inline code in markdown files for proper formatting and appropriate use of syntax highlighting.
 
+See [../shared/repo-conventions.md](../shared/repo-conventions.md) for file conventions.
+
 ## What to Check
 
 ### 1. Missing Backticks

.claude/skills/docker-setup/SKILL.md

@@ -200,7 +200,7 @@ docker stop nf-training && docker rm nf-training
 
 ## Notes
 
-- Always verify you're in the repository root before starting (check for `mkdocs.yml`)
+- Always verify you're in the repository root before starting (check for `docs/en/mkdocs.yml`)
 - The container uses `sleep infinity` so it persists across multiple command executions
 - Symlink must be recreated each time the container restarts
 - For long sessions, periodically check container is still running: `docker ps | grep nf-training`

.claude/skills/find-todos/SKILL.md

@@ -12,25 +12,21 @@ Execute from repository root. See [../shared/repo-conventions.md](../shared/repo
 ## Tasks to Perform
 
 1. **Search Markdown Files**
-
    - Use Grep to find TODO and FIXME in `docs/**/*.md`
    - Capture file path, line number, and full comment
    - Note context (which module/lesson)
 
 2. **Search Nextflow Scripts**
-
    - Find TODO/FIXME in `**/*.nf` files
    - Distinguish between training examples and solution code
    - Note if in core examples or side-quests
 
 3. **Search Configuration Files**
-
-   - Check `mkdocs.yml`
+   - Check `docs/en/mkdocs.yml`
    - Check `.github/**/*.yml` and `.github/**/*.py`
    - Check `CONTRIBUTING.md`
 
 4. **Categorize Results**
-
    - **High Priority**: Marked as FIXME, TODO(urgent), or blocking
    - **Documentation**: TODOs in markdown files
    - **Code**: TODOs in .nf or .py files
@@ -42,82 +38,32 @@ Execute from repository root. See [../shared/repo-conventions.md](../shared/repo
 
 ## Output Format
 
-Provide an organized report:
-
-````
+```
 # TODO/FIXME Report
 
 ## Summary
-- Total items: 23
-- High priority: 3
-- Documentation: 15
-- Code: 4
-- Configuration: 1
+Total items, High priority count, by category (Documentation/Code/Configuration)
 
 ## High Priority Items
-
-### docs/hello_nextflow/03_hello_workflow.md:156
-```markdown
-<!-- FIXME: Update this example for DSL2 syntax -->
-````
+[List FIXME and urgent items with file:line and context]
 
 ## Documentation TODOs
-
-### By File
-
-**docs/side_quests/debugging.md** (5 items)
-
-- Line 45: TODO: Add example of common error message
-- Line 89: TODO: Include screenshot of trace report
-- ...
-
-**docs/nf4_science/genomics/01_per_sample_variant_calling.md** (3 items)
-
-- Line 234: TODO: Verify this command works with latest GATK
-- ...
+[Group by file with line numbers]
 
 ## Code TODOs
-
-### hello-nextflow/hello-world.nf:23
-
-```groovy
-// TODO: Add error handling for missing files
-```
-
-## Configuration TODOs
-
-### CONTRIBUTING.md:204
-
-Known limitation documented - needs upstream fix in mkdocs plugin
+[Group by file with line numbers]
 
 ## Recommendations
-
-1. **Immediate attention** (3 items):
-
-   - Fix blocking issues in hello_nextflow
-   - Update genomics examples for latest tools
-
-2. **Next sprint** (8 items):
-
-   - Complete debugging module exercises
-   - Add missing screenshots
-
-3. **Low priority** (12 items):
-   - Style improvements
-   - Nice-to-have features
+1. Immediate attention: [blocking items]
+2. Next sprint: [significant items]
+3. Low priority: [nice-to-haves]
 
 ## Files with Most TODOs
-
-1. docs/side_quests/debugging.md (5)
-2. docs/nf4_science/genomics/01_per_sample_variant_calling.md (3)
-3. hello-nextflow/hello-world.nf (2)
-
+[Top 3-5 files]
 ```
 
 ## Notes
 
-- Use Grep tool with pattern `TODO|FIXME` (case insensitive)
-- Show enough context to understand what needs doing
+- Use Grep with pattern `TODO|FIXME` (case insensitive)
 - Distinguish between legitimate TODOs and example comments in training materials
 - Provide actionable priorities, not just a list
-```

.claude/commands/new-lesson.md → .claude/skills/new-lesson/SKILL.md

@@ -1,9 +1,12 @@
 ---
-description: Create a new lesson page within an existing training module
+name: new-lesson
+description: Create a new numbered lesson page within an existing training module. Use when adding a new topic like '05_error_handling.md' to an existing course.
 ---
 
 Create a new lesson page within an existing training module.
 
+See [../shared/repo-conventions.md](../shared/repo-conventions.md) for directory structure and file conventions.
+
 **Note**: A "module" is a complete training course (like "Hello Nextflow" or "Side Quests"), while a "lesson" is a single numbered page within that module (like "01_hello_world.md").
 
 Follow these steps:
@@ -99,10 +102,11 @@ process EXAMPLE {
    - Clear explanations for beginners
 
 5. Remind the user to:
-   - Add the lesson to `mkdocs.yml` nav section in the correct module
+   - Add the lesson to `docs/en/mkdocs.yml` nav section in the correct module
    - Create corresponding Nextflow example scripts if needed
    - Add solution files for any exercises in `[module]/solutions/`
    - Test any Nextflow examples before committing
    - Run heading validation: `uv run .github/check_headings.py --fix docs/**/*.md`
    - Preview locally with `mkdocs serve` or Docker to verify formatting
+   - Translations are handled automatically - when merged to master, the translation workflow will create PRs for each language
 ````

.claude/commands/new-module.md → .claude/skills/new-module/SKILL.md

@@ -1,8 +1,13 @@
 ---
-description: Scaffold a new complete training module with all standard files
+name: new-module
+description: Scaffold a complete new training module with standard directory structure, index, orientation, lessons, survey, and next-steps files. Use when creating a new course like 'Advanced Pipelines' or a new domain module.
 ---
 
-Create a new training module in this repository. Follow these steps:
+Create a new training module in this repository.
+
+See [../shared/repo-conventions.md](../shared/repo-conventions.md) for directory structure and file conventions.
+
+Follow these steps:
 
 1. Ask the user for:
 
@@ -30,11 +35,12 @@ Create a new training module in this repository. Follow these steps:
    - Appropriate use of admonitions
    - Code examples with proper formatting
 
-4. Add the module to mkdocs.yml navigation structure
+4. Add the module to `docs/en/mkdocs.yml` navigation structure
 
 5. Remind the user to:
    - Create any associated Nextflow example scripts in the root-level directory
    - Add Excalidraw diagrams if needed
    - Test all examples thoroughly
    - Run validation tools before committing
    - Preview the site locally
+   - Translations are handled automatically - when merged to master, the translation workflow will create PRs for each language

.claude/commands/preview.md → .claude/skills/preview/SKILL.md

@@ -1,9 +1,12 @@
 ---
-description: Start local preview server to view training materials
+name: preview
+description: Start local MkDocs preview server to view training material changes. Use when editing documentation, checking formatting, or testing how content renders before committing.
 ---
 
 Start the local MkDocs preview server to view changes to training materials.
 
+See [../shared/repo-conventions.md](../shared/repo-conventions.md) for directory structure.
+
 **First, check if a server is already running:**
 
 ```bash
@@ -16,27 +19,13 @@ docker ps --filter "ancestor=ghcr.io/nextflow-io/training-mkdocs:latest" --forma
 **Start the server using Docker (recommended):**
 
 ```bash
-docker run --rm -d -p 8000:8000 -v ${PWD}:/docs ghcr.io/nextflow-io/training-mkdocs:latest
-```
-
-**Alternative options:**
-
-If you encounter issues with social cards:
-
-```bash
-docker run --rm -p 8000:8000 -e 'CARDS=false' -v ${PWD}:/docs ghcr.io/nextflow-io/training-mkdocs:latest
+docker run --rm -d -p 8000:8000 -v ${PWD}:/docs -w /docs/docs/en ghcr.io/nextflow-io/training-mkdocs:latest
 ```
 
-If you have Python environment set up:
+**Alternative - using uv:**
 
 ```bash
-mkdocs serve
-```
-
-Or without social cards:
-
-```bash
-CARDS=false mkdocs serve
+uv run _scripts/docs.py serve
 ```
 
 **After starting the server:**
@@ -46,10 +35,7 @@ CARDS=false mkdocs serve
 - Check console for any build errors
 - Use `/stop-preview` command or Ctrl+C to stop the server
 
-**Note:** The initial build may take a few minutes as it builds documentation in multiple languages (en, pt, es, fr, it, ko). Wait for the "Serving on" message before accessing the site.
-
 **Common issues:**
 
-- If social cards fail, use CARDS=false option
 - If port 8000 is busy, use `/stop-preview` to stop other servers
 - If changes don't appear, check for markdown syntax errors in the console

.claude/skills/run-tutorial/SKILL.md

@@ -85,11 +85,11 @@ Use `TodoWrite` to track progress through phases and sections.
 Record any issues found. Do not proceed to Phase 2 until validation completes.
 ```
 
-### Phase 2: Progressive Execution (Core Unique Value)
+### Phase 2: Progressive Execution
 
-**CRITICAL**: Complete ALL steps (2.1-2.6) for EACH section before moving to the next section. Do NOT batch multiple sections together. The entire point of this skill is to catch issues that only appear when following the tutorial step-by-step.
+Complete steps 2.1-2.6 for each section before moving to the next. Do not batch sections together.
 
-For each numbered section in the lesson (0, 1, 2, 3...):
+For each numbered section in the lesson:
 
 #### 2.1 Read and Understand
 
@@ -99,13 +99,11 @@ For each numbered section in the lesson (0, 1, 2, 3...):
 
 #### 2.2 Verify Current State Matches "Before"
 
-**This is the key unique check**: Before applying any code change:
+Before applying any code change:
 
-1. Read the current file content using the `Read` tool
+1. Read the current file content
 2. Compare with the "Before" block in the documentation
-3. If they don't match, **STOP and report the discrepancy**
-   - This catches issues where earlier steps didn't work correctly
-   - This catches documentation that skipped steps
+3. If they don't match, stop and report the discrepancy
 
 #### 2.3 Apply Code Changes Progressively
 
@@ -125,16 +123,13 @@ For each numbered section in the lesson (0, 1, 2, 3...):
 - Compare console output with documented "Output" blocks
 - See [references/acceptable-differences.md](references/acceptable-differences.md) for what to flag vs. ignore
 
-#### 2.6 Confirm Section Complete Before Proceeding
+#### 2.6 Confirm Section Complete
 
-**MANDATORY**: Before moving to the next section:
+Before moving to the next section:
 
 1. Verify the workflow/script ran successfully (exit code 0)
 2. Confirm output matches documentation (within acceptable differences)
 3. Update `TodoWrite` to mark section complete
-4. Only then proceed to section N+1
-
-**Why this matters**: Skipping incremental testing defeats the purpose of this skill. A tutorial might work when you jump to the final solution but fail at intermediate steps - exactly the bugs learners encounter.
 
 ### Phase 3: Final Verification
 
@@ -207,8 +202,6 @@ Categorize as Critical / Warning / Minor
 Table with file, line, current, proposed, reason
 ```
 
-**IMPORTANT**: Always read actual section headings from the document. Do not guess.
-
 ---
 
 ## Special Cases