Merge pull request #2810 from annietllnd/main

Add review-guidelines.md

Author: jasonrandrews

.github/review-guidelines.md

@@ -0,0 +1,45 @@
+### Maintenance checks for Learning Paths and Install Guides
+ 
+Please review the content in the specified content path and support my manual review by:
+ 
+1. **Summarizing what this guide does**
+   - What the end goal is
+   - What platform(s) and environments it targets
+   - Any key assumptions the reader must meet
+ 
+2. **Identifying dependencies and moving parts**
+   - OS, architecture, toolchains, frameworks, SDKs
+   - External repositories, models, downloads, or services
+   - Commands or workflows that are central to the guide
+ 
+3. **Flagging potential risk areas**
+   - References to old OS versions, runtimes, or toolchains
+   - Dependencies that may be stale, deprecated, or fragile
+   - Links or resources that might require checking
+   - Steps that rely heavily on UI flows or screenshots
+ 
+4. **Calling out anything that may need a closer human look**
+   - Ambiguous or unclear instructions
+   - Areas where “latest” or unpinned versions are used
+   - Places where ecosystem changes could affect correctness
+ 
+---
+ 
+### How to behave
+ 
+- Be conservative and transparent — if something is uncertain, say so.
+- Prefer **flagging** over **fixing**.
+- Do not invent new commands, tools, or workflows.
+- If suggesting changes, keep them minimal and clearly optional.
+- Treat this as a *conversation starter* for the reviewer, not a final verdict.
+ 
+---
+ 
+### Output format (keep it lightweight)
+ 
+Please respond with:
+- A short summary of the guide
+- A bulleted list of dependencies
+- A bulleted list of review flags or questions to consider
+ 
+No code changes are required unless I explicitly ask for them.

content/learning-paths/cross-platform/_example-learning-path/appendix-4-maintain.md

@@ -0,0 +1,39 @@
+---
+# User change
+title: "Maintaining the content"
+
+weight: 10 # 1 is first, 2 is second, etc.
+
+# Do not modify these elements
+layout: "learningpathall"
+---
+## How to review a Learning Path
+
+Keeping Learning Paths and Install Guides up to date is an ongoing responsibility. The goal of content maintenance is to ensure that guides remain technically correct as tools, platforms, and dependencies constantly evolve.
+
+When reviewing content, focus on identifying risk, drift, and breakage that could impact a user’s ability to successfully follow the guide today. Look for issues such as:
+
+### Outdated dependencies or assumptions
+
+* Old OS versions, runtimes, or toolchains
+* Deprecated frameworks, libraries, or models
+* Hardware assumptions that may no longer hold
+
+
+### Ecosystem changes
+
+* Referenced repositories that are archived or inactive
+* Installation methods or CLIs that have changed
+* External services or downloads that no longer exist or have moved
+
+### Version drift and ambiguity
+
+* Use of “latest” without version context
+* Missing or unclear compatibility guidance
+* Mismatches between stated prerequisites and actual steps
+
+### Trust and usability signals
+
+* Broken or redirected links
+* UI instructions or screenshots that no longer match reality
+* Formatting or rendering issues that undermine confidence

content/learning-paths/cross-platform/_example-learning-path/questions.md

@@ -1,7 +1,7 @@
 ---
 title: "Common questions"
 
-weight: 10 
+weight: 11
 
 layout: "learningpathall"
 ---