fix(content): add the leading slash to 164 quest preview paths by bamr87 · Pull Request #792 · bamr87/it-journey

bamr87 · 2026-10-04T15:54:06Z

Problem

164 quests set preview: images/previews/<file> without a leading slash. The theme glues that onto its assets_prefix, so every one of those pages points its hero background and og:image / twitter:image at:

/assetsimages/previews/<file>     ← 404

Evidence (QA scan, Oct 2026): quest pages on it-journey.dev request /assetsimages/previews/*.png and get 404. Social shares of those quests have no image.

In a local build of main, 164 pages contain assetsimages, and 169 of the 180 unique preview URLs on /quests/ are missing.

Fix

Front matter only: preview: images/… → preview: /images/… in the 164 quest files. This matches the 17 quests that already use /images/. Only the first front-matter block is touched; no body text, other fields or generated data change.
TODO/templates/SEO_FRONTMATTER_TEMPLATE.md uses the slashed form, so new pages start out correct.
CHANGELOG [Unreleased] → Fixed entry.

The theme is also being hardened to accept the slashless form (bamr87/zer0-mistakes#509), but this repo should be correct on its own.

Verification

Local CI-parity build (_config.yml,_config_dev.yml,_config_ci.yml, remote theme):
- Pages containing assetsimages: 164 → 0.
- Unique preview URLs on /quests/ that resolve to a missing file: 169 → 71.
make quest-audit: AUDIT PASSED, including "all generated data in sync". Previews are not part of the generated quest data, so make quest-data has nothing to regenerate.
None of the touched files carry source_repo / source_url, so no vendored file is rewritten.

Follow-up (not in this PR)

The remaining 71 preview URLs now resolve correctly, but the image files were never generated. Every one is a .png under assets/images/previews/, for example:

agentic-autonomy-levels-matrix.png
agentic-behavior-tuning.png
agentic-codex-capstone-exam-trial.png

Running the preview generator (bundle exec jekyll preview-images, zer0-image-generator) should fill them in. That generates images, so it is left to the preview lane.

preview: images/previews/x.png was joined onto /assets as /assetsimages/previews/x.png (404 for the hero background and og:image). Use /images/previews/... like the other 17 quests, and fix the SEO frontmatter template so new pages start correct.

github-actions · 2026-10-04T15:54:20Z

🕸️ Quest Network Validation

⚠️ Warnings (first 10)

pages/_quests/1010/analytics-mcp-setup.md: carries retired field(s) ['quest_relationships', 'quest_mapping', 'learning_paths', 'snippet'] — run make quest-normalize
pages/_quests/1010/automate-traffic-report.md: carries retired field(s) ['quest_relationships', 'quest_mapping', 'learning_paths', 'snippet'] — run make quest-normalize
pages/_quests/1010/query-traffic-with-mcp.md: carries retired field(s) ['quest_relationships', 'quest_mapping', 'learning_paths', 'snippet'] — run make quest-normalize
Orphaned quest (not referenced): /quests/0001/barodybroject-stack-analysis/
Orphaned quest (not referenced): /quests/0001/git-init-testing/
Orphaned quest (not referenced): /quests/0001/it-journey-stack-analysis/
Orphaned quest (not referenced): /quests/0001/kaizen-continuous-improvement/
Orphaned quest (not referenced): /quests/0001/stack-attack/
Orphaned quest (not referenced): /quests/0010/jekyll-mermaid-integration/
Orphaned quest (not referenced): /quests/0010/oh-my-zsh-mastery/

github-actions · 2026-10-04T15:54:26Z

✒️ Content quality — brand gate

brand_lint: scanned 164 file(s)
On-brand — no glossary drift. ✔

github-actions · 2026-10-04T15:54:44Z

🎯 Quest Validation Results

Status	Quest	Score

Summary: 140 passed, 0 failed

ℹ️ About Quest Validation

This check validates quest files against IT-Journey standards:

Required frontmatter fields (16 fields)
Quest hierarchy metadata (8 fields)
Content structure (objectives, prerequisites, platform sections)
Code block language specifications
Interactive checkboxes
Fantasy theme integration
Accessibility (image alt text)
Citations/references

Run locally: python3 test/quest-validator/quest_validator.py <file.md> --summary

github-actions · 2026-10-04T16:08:50Z

🤖 Agentic Quest Review

4 quests evaluated · ✅ 1 pass · ⚠️ 3 warn · ❌ 0 fail · avg 73.8% · ~$1.9474

	Score	Quest	Snippets run	Summary
⚠️	65	bashcrawl and Beyond: Extending a Terminal Dungeon Adventure	3/15 (3✗)	A well-themed, generally accurate bashcrawl-extension quest whose individual Bash snippets are idiomatic and correct, but which is undermined by two real execution defects: an unreconciled working-directory switch (Steps 4–6 use absolute-from-root paths while the learner is left inside armoury) and a wrong relative path in the hidden-room reveal (`mv ../.study`) that silently prevents the secret room from appearing. It also promises `read`/`case` encounters it never has the learner build. Fixing the path bugs and aligning content with the stated objectives would raise this from adequate to strong.
⚠️	75	Character Building: Forge Your IT Hero Identity	0/3	A clear, well-organized conceptual foundation quest that successfully guides a beginner through IT self-assessment, specialization, and goal-setting with coherent validation criteria and zero safety risks. Its main defects are editorial/structural: a large duplicated section appended after the conclusion, and 'toolkit' code blocks that contain only comments instead of runnable install commands, plus a couple of outdated tool recommendations (Atom, Adobe XD).
✅	83	Git Basics: Version Control Introduction	0/33	A well-structured, accurate, and safe Git foundation quest: install steps, core git/gh commands, undo operations, and verification scripts are correct and clearly sequenced, with destructive commands properly warned. The one significant flaw is the Boss Battle's merge-conflict phase, which edits non-overlapping lines and therefore never produces the promised conflict — breaking the capstone's `git add index.html`/`git commit` step for a literal follower; fixing the conflict setup (as Challenge 2 already does correctly) would make this an excellent quest.
⚠️	72	Markdown Mastery: Content Formatting Fundamentals	no	A well-structured, safe, and pedagogically strong Level 0000 Markdown quest whose syntax is almost entirely accurate. Its one significant flaw is self-undermining for the topic: the fenced-code example closes blocks with `text instead of` , which would teach learners to produce broken Markdown. Fixing that and reconciling the 'abbreviations/definition lists' objective with the actual content would make this excellent.

Recommendations for flagged quests

bashcrawl and Beyond: Extending a Terminal Dungeon Adventure (pages/_quests/0000/bash-run.md) — 65%

high · Step 4 & Step 5 working directory: Make paths consistent: either add an explicit cd back to the bashcrawl root before the absolute paths in Steps 4–6, or keep using relative paths (e.g. mkdir library/.study, cat > library/guardian) consistent with Step 3's cd entrance/cellar/armoury.
high · Step 4 hidden-room reveal: Fix the reveal path: since .study is in library/ (same dir as treasure), change mv ../.study ../study 2>/dev/null to mv .study study 2>/dev/null. As written the hidden room is never revealed and the error is hidden.
medium · Objectives vs. content (read/case): Either add a case-based (and read-based) interactive encounter to the build steps, or revise the objective/validation text so it no longer promises read and case that the learner never actually writes.
medium · Step 4 'Add this line inside library/treasure': Show the full, final library/treasure with the reveal lines in place (inside the then branch, after the heredoc) rather than a free-floating snippet, so beginners know exactly where the lines go.
medium · Fork-specific commands/flags: Verify and, if needed, qualify ./setup.sh --verify, make web-build, make web-test, and the mode table against the actual bamr87 fork; drop or mark as fork-specific any flag/target that doesn't exist.
low · Step 6 save file: Note that .bashcrawl_save.json only exists after the game has been launched/played, so cat .bashcrawl_save.json may error on a fresh clone.

Character Building: Forge Your IT Hero Identity (pages/_quests/0000/character-building.md) — 75%

high · Structure — duplicated trailing content (lines 348-408): Remove the duplicated OS/dev-environment numbered list and the stray repeated sentence at line 348 (a copy of line 98). This appended block duplicates Chapters 2 and 4 and sits after the conclusion, making the quest read like two merged drafts.
high · Chapter 4 — specialization toolkit bash blocks: Replace the comment-only placeholders with real, copy-pasteable install commands (e.g. Frontend: Node.js via nvm plus npm install -g vite), or relabel the blocks clearly as 'checklists of tools to research/install' so learners don't expect them to execute.
medium · Technical accuracy — editor/tool recommendations: Drop 'Atom' (archived by GitHub in Dec 2022) and reconsider 'Adobe XD' (no longer actively developed). Recommend current tools (e.g. VS Code, Zed, Figma).
low · Data Science Toolkit categorization: Separate visualization tools by ecosystem: Matplotlib/Seaborn/Plotly as Python libraries, Tableau/Power BI as BI applications, and D3.js as a JS library, rather than grouping them as one.

Markdown Mastery: Content Formatting Fundamentals (pages/_quests/0000/markdown-mastery.md) — 72%

high · Chapter 2 — Fenced code blocks example (lines 151-164): Replace every text closing fence with a bare so the python/bash/javascript examples close correctly. As written, the quest teaches an invalid way to end a code block in a tutorial whose purpose is correct Markdown.
medium · Secondary objective vs. content (line 14 vs. Chapter 3): Either add brief sections on abbreviations and definition lists, or edit the objective to 'Footnotes and HTML embedding' so the promise matches what is taught.
low · Chapter 3 — HTML
Details
(lines 249-256 vs. Quick Win 261): Make the example and Quick Win consistent: show
and note it is needed for Jekyll/kramdown to render Markdown inside, matching the IT-Journey platform context.
low · Blockquote preview (lines 177-178): Include the nested blockquote in the 'rendered' preview so learners see the > > result they were just shown.

ℹ️ Advisory read-only review — does not block this PR. Add the agentic-review label for a sandboxed execute run.
♻️ Convergence: automatic pass 3/3 for this PR; quests last scoring ≥ 85 are exempt from re-review on later pushes. Add the agentic-review label to force a full pass.

github-actions · 2026-10-07T04:07:45Z

✒️ Content quality — brand gate

brand_lint: scanned 164 file(s)
On-brand — no glossary drift. ✔

github-actions · 2026-10-07T04:18:54Z

✒️ Content quality — brand gate

brand_lint: scanned 164 file(s)
On-brand — no glossary drift. ✔

Merge branch 'main' into fix/content-preview-leading-slash

c459d7d

Merge branch 'main' into fix/content-preview-leading-slash

302eea4

bamr87 merged commit aaee338 into main Oct 7, 2026
19 checks passed

bamr87 deleted the fix/content-preview-leading-slash branch October 7, 2026 04:30

Navigation Menu

Repository navigation

fix(content): add the leading slash to 164 quest preview paths - #792

fix(content): add the leading slash to 164 quest preview paths#792
bamr87 merged 3 commits into
mainfrom
fix/content-preview-leading-slash

bamr87 commented Oct 4, 2026

Uh oh!

github-actions Bot commented Oct 4, 2026

Uh oh!

github-actions Bot commented Oct 4, 2026

Uh oh!

github-actions Bot commented Oct 4, 2026

Uh oh!

github-actions Bot commented Oct 4, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 7, 2026

Uh oh!

github-actions Bot commented Oct 7, 2026

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

bamr87 commented Oct 4, 2026

Problem

Fix

Verification

Follow-up (not in this PR)

Uh oh!

github-actions Bot commented Oct 4, 2026

🕸️ Quest Network Validation

⚠️ Warnings (first 10)

Uh oh!

github-actions Bot commented Oct 4, 2026

✒️ Content quality — brand gate

Uh oh!

github-actions Bot commented Oct 4, 2026

🎯 Quest Validation Results

Uh oh!

github-actions Bot commented Oct 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🤖 Agentic Quest Review

Uh oh!

github-actions Bot commented Oct 7, 2026

✒️ Content quality — brand gate

Uh oh!

github-actions Bot commented Oct 7, 2026

✒️ Content quality — brand gate

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

github-actions Bot commented Oct 4, 2026 •

edited

Loading