@piercebarney/whs-eleventy

The web house style's Eleventy + Netlify tooling — one shared copy of the checks every project on the stack runs, so a fix lands once and npm update carries it everywhere.

whs compliance [--strict]              codebase-vs-standard conformance sweep
whs doctor [--live|--deploy-preflight] infrastructure drift check
whs links                              built-output link / CSP / JSON-LD integrity
whs a11y                               axe-core WCAG 2.1 A/AA scan of _site/
whs content-check                      lint · validate · build · links (no browser)
whs --version                          tooling + bundled-standard version

Each subcommand resolves the project against the current working directory and expects the eleventy-netlify layout (src/_data/*.js, netlify.toml, _site/, test/). It is not configurable — projects on this stack are copies of templates/eleventy-netlify/ and share that shape.

Install

npm i -D @piercebarney/whs-eleventy

Then in package.json:

{
  "scripts": {
    "links": "whs links",
    "a11y": "whs a11y",
    "doctor": "whs doctor",
    "compliance": "whs compliance",
    "content-check": "whs content-check"
  }
}

The /audit/ data files import the API directly:

const { runCompliance, summarize } = require("@piercebarney/whs-eleventy/lib/compliance.js");
const { runRepoChecks, readCache } = require("@piercebarney/whs-eleventy/lib/doctor.js");

The bundled standard

whs compliance's drift check reads core.md + CHANGELOG.md to compare the project's standard-version pin against the current standard. The package ships a snapshot of both under standard/, cut when the version is published. Override with WHS_STANDARD=/path/to/web-house-style (the authoring repo points this at itself). When neither resolves, the drift row is a visible MANUAL, never a silent pass.

Not in this package

scripts/og.js, scripts/icons.js, scripts/og-card.js stay in the project — they are asset generators wired into the eleventy build, with a per-project page list and card design.