Project Docs

Volume 9 Final QA

Status

Volume 9 is complete through Q450.

The current content boundary is:

Q376-Q450
75 questions
15 batches

Automated Checks

Run before publishing a final refresh:

npm run test
npm run typecheck
npm run build

Manual Browser Checks

Check these user workflows:

/volume-9
/batch/volume-9-batch-15
/questions/volume-9-closure-and-next-volume-planning
/practice/javascript
/practice/typescript
/docs

Practice Ground QA

Validate:

JavaScript run and console output
TypeScript feedback states
copy code buttons
copy console buttons
clear console action
Tab indentation
Shift Tab outdent
Alt ArrowDown duplicate line or block
Ctrl or Command Enter run shortcut
Ctrl or Command L clear shortcut
saved snippets save, load, conflict, delete, and reload behavior

Theme QA

Validate:

system-default initial theme
light theme
dark theme
theme persistence
button contrast
practice panels
snippet cards
docs pages
question reader

Responsive QA

Validate:

mobile width
tablet width
laptop width
desktop width
long titles
long snippet text
long console output
home topic cards
volume cards
batch cards

Artifact QA

Check:

PDF generation after Q450: generated for volume-9-batch-15.pdf
PDF visual open check: rendered and inspected the two-page PDF
portfolio screenshots after latest UI: captured locally in docs/portfolio-assets/screenshots
sitemap includes Q450 routes
manifest uses Learning Studio naming
favicon and app icons render
custom domain resolves: DNS resolves to Vercel; HTTPS reachability still needs live recheck

Pending Follow-Ups

  • Use docs/NEXT_FIXES.md as the main implementation backlog for the next UX pass.
  • Refresh portfolio screenshots from the live site after the custom domain is reachable.
  • Recheck live deployment routes after Vercel HTTPS is reachable from the network.
  • Decide whether Volume 10 should be project capstones, production debugging labs, or portfolio delivery.
  • Consider future saved-snippet search, export, and import after the current local workflow is stable.
  • Add browser-level tests for console cap behavior if the practice ground grows further.