|
| 1 | +# Documentation Review Guide |
| 2 | + |
| 3 | +This file defines a repeatable review process for evaluating and improving |
| 4 | +the Mat3ra documentation. It is designed for AI coding agents but can also |
| 5 | +be used by human reviewers. |
| 6 | + |
| 7 | +Read [`WRITING-STYLE.md`](WRITING-STYLE.md) and [`AGENTS.md`](AGENTS.md) |
| 8 | +first — they are the canonical references for prose style and agent |
| 9 | +guidance respectively. This file builds on them. |
| 10 | + |
| 11 | +--- |
| 12 | + |
| 13 | +## Review Panel |
| 14 | + |
| 15 | +The review simulates a panel of three personas. Each brings a different |
| 16 | +lens to the documentation: |
| 17 | + |
| 18 | +| ID | Persona | Focus | |
| 19 | +|----|---------|-------| |
| 20 | +| R1 | Experienced computational materials scientist (5–10 yr) | Technical accuracy, depth, correctness of methods and parameters | |
| 21 | +| R2 | First-year postdoc in comp chem / AI for materials | Cross-linking, discoverability, ML workflow clarity | |
| 22 | +| R3 | Last-year PhD student in comp. mat. sci. | Clarity for newcomers, step-by-step completeness, visual aids | |
| 23 | + |
| 24 | +When scoring, consider how each persona would rate the page independently, |
| 25 | +then average. |
| 26 | + |
| 27 | +--- |
| 28 | + |
| 29 | +## Evaluation Criteria |
| 30 | + |
| 31 | +Score each page on a 0–10 scale across five criteria: |
| 32 | + |
| 33 | +### C1: Structural Consistency |
| 34 | + |
| 35 | +| Score | Description | |
| 36 | +|-------|-------------| |
| 37 | +| 9–10 | Numbered sections (`## 1.`, `### 1.1.`), imperative subheadings, no list directly under heading, proper H1/H2/H3 hierarchy | |
| 38 | +| 7–8 | Numbered sections but inconsistent subheading style, or one heading-level violation | |
| 39 | +| 5–6 | Unnumbered sections, gerund subheadings, lists under headings | |
| 40 | +| 0–4 | No structure, flat document, missing H1 | |
| 41 | + |
| 42 | +### C2: Voice & Style |
| 43 | + |
| 44 | +| Score | Description | |
| 45 | +|-------|-------------| |
| 46 | +| 9–10 | Third-person/passive throughout, no forbidden words, no "you/your/we/our", acronyms introduced on first use | |
| 47 | +| 7–8 | 1–2 isolated voice violations, otherwise clean | |
| 48 | +| 5–6 | Frequent "we"/"you" usage, some forbidden words | |
| 49 | +| 0–4 | Pervasive second-person, marketing tone | |
| 50 | + |
| 51 | +**Forbidden words** (from `WRITING-STYLE.md`): *Simply, Clearly, |
| 52 | +Obviously, In fact, Furthermore, Moreover, Complete, In particular, |
| 53 | +Really, Distinct, Various, Automatically, Finally*. |
| 54 | + |
| 55 | +### C3: Technical Depth |
| 56 | + |
| 57 | +| Score | Description | |
| 58 | +|-------|-------------| |
| 59 | +| 9–10 | Method explained with references, key parameters documented, expected results stated, comparison to experiment/literature where applicable | |
| 60 | +| 7–8 | Method referenced but not explained, parameters listed without rationale | |
| 61 | +| 5–6 | Procedural steps only, no "why" | |
| 62 | +| 0–4 | Incomplete procedure, missing steps | |
| 63 | + |
| 64 | +### C4: Navigability & Cross-Linking |
| 65 | + |
| 66 | +| Score | Description | |
| 67 | +|-------|-------------| |
| 68 | +| 9–10 | All related tutorials cross-linked, prerequisite tutorials referenced, same-site relative links, cross-site macro links | |
| 69 | +| 7–8 | Most links present, one or two missing cross-references | |
| 70 | +| 5–6 | Minimal linking, isolated page | |
| 71 | +| 0–4 | Broken links or no links at all | |
| 72 | + |
| 73 | +### C5: Media & Visuals |
| 74 | + |
| 75 | +| Score | Description | |
| 76 | +|-------|-------------| |
| 77 | +| 9–10 | All images have alt text + title, `.webp` format, video embeds present, screenshots current | |
| 78 | +| 7–8 | Images present with alt text but PNG format, or one missing caption | |
| 79 | +| 5–6 | Some images without alt/title, outdated screenshots | |
| 80 | +| 0–4 | No images or broken image links | |
| 81 | + |
| 82 | +--- |
| 83 | + |
| 84 | +## How to Run a Review |
| 85 | + |
| 86 | +### Quick Prompt (paste into chat) |
| 87 | + |
| 88 | +``` |
| 89 | +Review the documentation under `lang/en/docs/tutorials/` following the |
| 90 | +process defined in REVIEW.md. Score each page on the 5 criteria (C1–C5), |
| 91 | +produce a scorecard table, then refactor the lowest-scoring pages to bring |
| 92 | +the average above 9/10. Work in rounds of 5–8 files, updating the |
| 93 | +scorecard after each round. |
| 94 | +``` |
| 95 | + |
| 96 | +### Full Prompt (for thorough multi-round review) |
| 97 | + |
| 98 | +``` |
| 99 | +You are a review panel consisting of: |
| 100 | +
|
| 101 | +(1) An experienced computational materials scientist with 5–10 years of |
| 102 | + experience |
| 103 | +(2) A first-year postdoc in comp chem / AI for materials |
| 104 | +(3) A last-year PhD student in comp. mat. sci. |
| 105 | +
|
| 106 | +Read REVIEW.md, WRITING-STYLE.md, and AGENTS.md. Then: |
| 107 | +
|
| 108 | +1. Score every tutorial page under `lang/en/docs/tutorials/` on the 5 |
| 109 | + criteria defined in REVIEW.md (C1–C5, 0–10 scale). |
| 110 | +2. Produce a scorecard table grouped by section. |
| 111 | +3. Identify the lowest-scoring pages and refactor them in rounds of 5–8 |
| 112 | + files per round. |
| 113 | +4. After each round, re-score the refactored pages and update the |
| 114 | + scorecard. |
| 115 | +5. Continue until the mean score across all pages is ≥ 9/10. |
| 116 | +6. Produce a final scorecard and a walkthrough of all changes made. |
| 117 | +``` |
| 118 | + |
| 119 | +### Scoping a Partial Review |
| 120 | + |
| 121 | +To review a specific section only: |
| 122 | + |
| 123 | +``` |
| 124 | +Review only the files under `lang/en/docs/tutorials/dft/vibrational/` |
| 125 | +following REVIEW.md. Score, refactor, and re-score. |
| 126 | +``` |
| 127 | + |
| 128 | +--- |
| 129 | + |
| 130 | +## Style Checklist (Quick Reference) |
| 131 | + |
| 132 | +This distills the most common issues found during reviews. Check every |
| 133 | +page against this list: |
| 134 | + |
| 135 | +- [ ] One H1 (`#`) on line 1; sub-headers use sentence case |
| 136 | +- [ ] Sections numbered: `## 1.`, `### 1.1.` |
| 137 | +- [ ] Subheadings are imperative ("Import the workflow", not "Importing |
| 138 | + the workflow") |
| 139 | +- [ ] No list starts directly under a heading — open with prose first |
| 140 | +- [ ] Lists are flat (single level); images/code blocks are flush-left |
| 141 | +- [ ] Third person / passive voice throughout; no "you", "your", "we", |
| 142 | + "our" |
| 143 | +- [ ] None of the forbidden words from `WRITING-STYLE.md` |
| 144 | +- [ ] No acronyms in headings; acronyms introduced on first use in body |
| 145 | +- [ ] Same-site links use relative paths |
| 146 | +- [ ] Cross-site links use `{{ guide_url }}`, `{{ reference_url }}`, or |
| 147 | + `{{ dev_url }}` macros |
| 148 | +- [ ] All images have alt text and title: `` |
| 149 | +- [ ] Prefer `.webp` images; each file < 1 MB |
| 150 | +- [ ] Video embeds use the standard `<div class="video-wrapper">` pattern |
| 151 | +- [ ] Version notes include "and later" (e.g., "5.2.1, 5.4.0, 6.0.0, |
| 152 | + 6.3, and later") |
| 153 | +- [ ] `mkdocs.yml` updated if pages were added, renamed, or moved |
| 154 | + |
| 155 | +--- |
| 156 | + |
| 157 | +## Baseline Scores (June 2025) |
| 158 | + |
| 159 | +These scores reflect the state after 12 rounds of review. Use them as a |
| 160 | +starting point — re-score before making changes to account for any |
| 161 | +subsequent edits. |
| 162 | + |
| 163 | +| Section | Pages | Mean Score | Status | |
| 164 | +|---------|-------|------------|--------| |
| 165 | +| DFT Electronic | 16 | 9.2 | ✅ Refactored | |
| 166 | +| DFT Vibrational | 4 | 9.0 | ✅ Refactored | |
| 167 | +| DFT Thermodynamic | 1 | 9.2 | ✅ Refactored | |
| 168 | +| DFT Chemical | 2 | 9.2 | ✅ Refactored | |
| 169 | +| DFT Optical | 1 | 9.2 | ✅ Refactored | |
| 170 | +| DFT Addons | 2 | 9.2 | ✅ Refactored | |
| 171 | +| Python ML | 5 | 9.1 | ✅ Refactored | |
| 172 | +| ML (legacy + DeePMD) | 4 | 9.0 | ✅ Refactored | |
| 173 | +| Reference / Overview | 4 | 8.4 | ✅ Refactored | |
| 174 | +| **Tutorials overall** | **39** | **9.1** | | |
| 175 | +| Templating | 2 | ~6.0 | ⬜ Not yet reviewed | |
| 176 | +| General Functionality | 2 | ~5.5 | ⬜ Not yet reviewed | |
| 177 | +| Materials | ~12 | ~6.5 | ⬜ Not yet reviewed | |
| 178 | +| Materials (specific) | ~20 | ~6.0 | ⬜ Not yet reviewed | |
| 179 | + |
| 180 | +--- |
| 181 | + |
| 182 | +## Common Refactoring Patterns |
| 183 | + |
| 184 | +These patterns were applied repeatedly during the 12-round review. |
| 185 | +Future agents should follow the same approach: |
| 186 | + |
| 187 | +### Voice Fixes |
| 188 | + |
| 189 | +```diff |
| 190 | +-We will now calculate the band structure. |
| 191 | ++The band structure is calculated as follows. |
| 192 | + |
| 193 | +-In this tutorial, we demonstrate how to... |
| 194 | ++This tutorial demonstrates how to... |
| 195 | + |
| 196 | +-You should click the button. |
| 197 | ++Click the button. / The button should be clicked. |
| 198 | + |
| 199 | +-our platform |
| 200 | ++the platform |
| 201 | +``` |
| 202 | + |
| 203 | +### Section Numbering |
| 204 | + |
| 205 | +```diff |
| 206 | +-## Create Job |
| 207 | ++## 1. Create the job |
| 208 | + |
| 209 | +-## Choose Workflow |
| 210 | ++## 2. Select the workflow |
| 211 | + |
| 212 | +-### Examine Input Files |
| 213 | ++### 2.1. Examine the input files |
| 214 | +``` |
| 215 | + |
| 216 | +### Heading Style |
| 217 | + |
| 218 | +```diff |
| 219 | +-### 1.1. Importing a workflow |
| 220 | ++### 1.1. Import a workflow |
| 221 | + |
| 222 | +-### 4.2. Example Results |
| 223 | ++### 4.2. Example results |
| 224 | +``` |
| 225 | + |
| 226 | +### No List Under Heading |
| 227 | + |
| 228 | +```diff |
| 229 | + ### 1.1. Import a bank workflow |
| 230 | + |
| 231 | +- - Navigate to the Workflows Bank page. |
| 232 | +- - Search for the workflow. |
| 233 | ++First, navigate to the Workflows Bank page. |
| 234 | ++Then, search for the workflow. |
| 235 | +``` |
| 236 | + |
| 237 | +### Version Notes |
| 238 | + |
| 239 | +```diff |
| 240 | +- The present tutorial is written for Quantum ESPRESSO at versions |
| 241 | +- 5.2.1, 5.4.0, 6.0.0 or 6.3. |
| 242 | ++ This tutorial applies to Quantum ESPRESSO versions 5.2.1, 5.4.0, |
| 243 | ++ 6.0.0, 6.3, and later. |
| 244 | +``` |
| 245 | + |
| 246 | +### Verbose Workflow Details → Collapsible |
| 247 | + |
| 248 | +When a tutorial has extensive workflow/parameter documentation that |
| 249 | +interrupts the procedural flow, move it into a collapsible block: |
| 250 | + |
| 251 | +```markdown |
| 252 | +<details markdown="1"> |
| 253 | + <summary>Expand to view input parameter details</summary> |
| 254 | + |
| 255 | + ... detailed parameter documentation ... |
| 256 | + |
| 257 | +</details> |
| 258 | +``` |
| 259 | + |
| 260 | +--- |
| 261 | + |
| 262 | +## Extending This Guide |
| 263 | + |
| 264 | +When adding new evaluation criteria or refactoring patterns: |
| 265 | + |
| 266 | +1. Add the criterion to the "Evaluation Criteria" section with score |
| 267 | + descriptions. |
| 268 | +2. Add a corresponding checklist item to "Style Checklist". |
| 269 | +3. If a new refactoring pattern emerges, add a diff example to "Common |
| 270 | + Refactoring Patterns". |
| 271 | +4. Update the baseline scores table after each review cycle. |
0 commit comments