@piercebarney/whs-eleventy 2026.10.4 → 2026.10.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/standard/CHANGELOG.md +19 -0
- package/standard/core.md +2 -2
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@piercebarney/whs-eleventy",
|
|
3
|
-
"version": "2026.10.
|
|
3
|
+
"version": "2026.10.5",
|
|
4
4
|
"description": "The web house style's Eleventy + Netlify tooling — the compliance sweep, the infra doctor, the link/CSP integrity check, and the a11y scan, shared by every project on the stack.",
|
|
5
5
|
"bin": {
|
|
6
6
|
"whs": "cli.js"
|
package/standard/CHANGELOG.md
CHANGED
|
@@ -21,6 +21,25 @@ enforced, new *opt-in* chapters/capabilities, tooling-only changes — is
|
|
|
21
21
|
|
|
22
22
|
---
|
|
23
23
|
|
|
24
|
+
## 2026-10-05 [non-breaking]
|
|
25
|
+
|
|
26
|
+
### templates/commands
|
|
27
|
+
|
|
28
|
+
`/whs:adopt`'s step 5 npm-scripts proposal only ever covered
|
|
29
|
+
`check`/`compliance`/`status`, never `build`/`serve` — a real adopting
|
|
30
|
+
project ended up with no `npm run serve` at all and had to be told the
|
|
31
|
+
convention rather than adoption ever mentioning it. The step now also
|
|
32
|
+
proposes `build`/`serve`, using `templates/eleventy-netlify/package.json`'s
|
|
33
|
+
exact commands, with a per-script-name conflict check (not the all-or-nothing
|
|
34
|
+
check the adjacent proposal uses) — a pre-existing project is more likely to
|
|
35
|
+
already have some build/serve mechanism, possibly under a different name,
|
|
36
|
+
than to already have WHS-specific scripts, so each of the two names is
|
|
37
|
+
checked and proposed independently, and the human is told plainly to confirm
|
|
38
|
+
before treating either as net-new. Fourth `/whs:adopt`-vs-`/whs:new` parity
|
|
39
|
+
gap found this week. No `core.md` chapter changed. Fixed in `41f65c3`.
|
|
40
|
+
|
|
41
|
+
---
|
|
42
|
+
|
|
24
43
|
## 2026-10-04 [non-breaking]
|
|
25
44
|
|
|
26
45
|
### stacks/eleventy-netlify.md
|
package/standard/core.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Web project house style — CORE (stack-agnostic)
|
|
2
2
|
|
|
3
|
-
**Version:** 2026-10-
|
|
3
|
+
**Version:** 2026-10-05 · **Status:** active
|
|
4
4
|
|
|
5
5
|
This is the stack-agnostic contract every web project follows, regardless of
|
|
6
6
|
framework, host, or CSS system. It says **what** must be true, with concrete
|
|
@@ -1467,7 +1467,7 @@ governs it and follow that chapter — the slugs are the index (a `<script>` →
|
|
|
1467
1467
|
- production-url: https://example.com
|
|
1468
1468
|
- content-type: tool # tool | article (article => feeds)
|
|
1469
1469
|
- publishing-rate: ~5 pages/week
|
|
1470
|
-
- standard-version: 2026-10-
|
|
1470
|
+
- standard-version: 2026-10-05 # recommended — enables standard-version drift tracking (#compliance)
|
|
1471
1471
|
```
|
|
1472
1472
|
|
|
1473
1473
|
If the section is absent, the assistant's first action is to run the flow above
|