Contributing

How to propose a change, keep the patch small, and validate the result.

Workflow

  1. Write the smallest useful patch.
  2. Check the relevant doc page or test case.
  3. Run validation before asking for review.

Docs quality rules (required)

  • No integrity= / crossorigin= on local docs assets (docs/*.html links to css/site.css, css/print.css, js/main.js).
  • Run full docs chain before push: bash tools/docs_pipeline.sh phase1.
  • Run local page smoke before push: tools/docs/verify_local_pages.sh (checks index/news/community styles).

Browser smoke checklist

  1. Open index.html, news.html, community.html on desktop and mobile viewport.
  2. Hard refresh each page.
  3. Verify browser console has 0 CSS/JS errors.

Post-deploy monitor

After deployment, run tools/docs/post_deploy_css_monitor.sh to alert if forbidden integrity= reappears on site.css in production.

Useful links