Local development
Use the Node version in website/.node-version and its bundled npm. The website is an independent package with locked dependencies.
Start the development server
Section titled “Start the development server”cd websitenpm cinpm run devOpen the localhost URL printed by Astro. Canonical documentation, examples, reference inputs, and presentation files are watched. Stop the server with Ctrl-C before starting another one.
Check the built site
Section titled “Check the built site”With other servers on port 4321 stopped, install Chromium once after setup or a Playwright update, then run the website checks:
npm run test:browsers:installnpm run verify:websiteThe aggregate checks release policy, references, content/types, unit tests, one static build, and browser behavior. It does not run the L compiler. Browser checks manage their own preview server and use .cache/ms-playwright by default; PLAYWRIGHT_BROWSERS_PATH can override that cache location.
After a successful build, inspect the site with:
npm run previewPreview serves http://127.0.0.1:4321/, including the Pagefind search index that is absent from the development server. Use HTTP rather than opening HTML with file://. Stop preview before another verification run. Individual commands in package.json are available for focused diagnosis.
Troubleshoot the right layer
Section titled “Troubleshoot the right layer”- Missing dependencies or browser: repeat
npm ciornpm run test:browsers:installwith the pinned Node. These downloads need network access; content builds use local inputs. - Missing route or fragment: check the content-map entry or target heading.
- Stale example or reference: review its source and evidence before regenerating snapshots. See authoring.
- No Git metadata: source archives still build, with unknown commit identity and repository-relative source attribution.
npm run test:archivechecks this path.
Keep native work opt-in
Section titled “Keep native work opt-in”Compiler bootstrap and expensive native validation follow the temporary validation pause. The optional example verifier requires explicit authorization and an existing compiler with its native prerequisites:
npm run examples:verify -- --compiler /absolute/path/to/l --id basicThis checks approved examples, not arbitrary Markdown fences or the full acceptance gate. Documentation CI runs website checks on pull requests. The legacy-named ci:verify-disabled command validates approved manual release paths and publication authorization. Publication requires an authorized manual dispatch from main; see deployment for activation and recovery.
Canonical source: docs/contributing/local-development.md.