The docs site under site/ lags on its build toolchain while the rest of the repo has standardised on pnpm:
@11ty/eleventy ^2.0.1 — v3 is current (ESM migration).tailwindcss ^3.4.15 — v4 is current (config rewrite).- Yarn 1.22 classic — deprecated;
frontend/ and the project docs use pnpm, so the repo carries two JS package managers.
Each is a breaking-change migration (deliberately held back per frontend/CLAUDE.md), so this is a tracking issue for a deliberate follow-up rather than a drop-in bump. Reasonable order: migrate site/ from Yarn to pnpm first (mechanical), then Eleventy 2 → 3, then Tailwind 3 → 4, verifying the built HTML output diff at each step.
The docs site under
site/lags on its build toolchain while the rest of the repo has standardised on pnpm:@11ty/eleventy^2.0.1— v3 is current (ESM migration).tailwindcss^3.4.15— v4 is current (config rewrite).frontend/and the project docs use pnpm, so the repo carries two JS package managers.Each is a breaking-change migration (deliberately held back per
frontend/CLAUDE.md), so this is a tracking issue for a deliberate follow-up rather than a drop-in bump. Reasonable order: migratesite/from Yarn to pnpm first (mechanical), then Eleventy 2 → 3, then Tailwind 3 → 4, verifying the built HTML output diff at each step.