wtclaude
e71ff4acd4
All checks were successful
PR checks / checks (pull_request) Successful in 9m36s
PLAN.md §13 phase 10, with four decisions of record — D47-D50, taking the count
to fifty. Three were straightforward; the CSP turned into the phase's real work,
because the thing meant to be a configuration flag was broken in a dependency and
broken silently.
D47 — search reaches the marketing pages, and the header gets a box.
Base.astro marks its <main> as a Pagefind body, so all ten join the index the
docs already query, and Search.astro opens it in a <dialog>. Nothing is fetched
until the dialog is opened (the bundle is 120 kB and these pages otherwise ship
almost no JavaScript). Pagefind titles a result from the first <h1>, and these
pages have editorial ones — "The app for a deployment you already use" — so the
index is given the page's short name instead. applyBrand.mjs now re-indexes after
a rewrite, closing a note phase 2 left for this phase.
D48 — the CSP is a real response header, sent by the container. Not a <meta>,
which ignores frame-ancestors, and not advice for someone's reverse proxy, which
puts the strictest promise in §6 outside what this repo tests. Three things
fought it, all the same shape — correct build, broken page, no error:
* Astro does not hash <script is:inline>, and Starlight ships six per docs
page, so the first build with CSP on had a strict header and a dead theme
switcher. The hashes are now generated into src/config/cspHashes.mjs and
checkCsp.mjs verifies every inline block against its own page's policy.
* Expressive Code writes ~3,700 inline style ATTRIBUTES, which cannot be
hashed, hence style-src-attr 'unsafe-inline' — scoped to that directive, so
script-src is untouched.
* @astrojs/node matched a request to a policy with pathname.includes(), a
substring test: /modules/ was served /docs/modules/building-a-module's
policy and rendered with its own stylesheet refused. scripts/serve.mjs keeps
the same _headers.json and matches by equality; test/headers.test.mjs starts
the server and reads the responses, because nothing that reads dist/ can see
this.
D49 — robots.txt allows everything and names the sitemap (there was no way to
find it: no robots.txt, and D9 rules out a search console). D50 — Organization
and SoftwareApplication, no ratings and no docs-wide Article markup.
checkA11y.mjs is the eleventh check: seven structural rules over all fifty pages,
verified by breaking each in turn. The walk at 390/768/1280 found no overflow
anywhere, the CSP violations above, a 17x17 consent checkbox (WCAG 2.2 SC 2.5.8
wants 24), and a skip link that moved the scroll but not the focus.
npm run verify is green: fourteen steps, both test suites, all eleven checks.
Co-Authored-By: Claude <noreply@anthropic.com>
35 lines
1.0 KiB
Plaintext
35 lines
1.0 KiB
Plaintext
---
|
|
import Base from '../layouts/Base.astro';
|
|
|
|
/**
|
|
* Ours rather than Starlight's (`disable404Route: true` in astro.config.mjs). A reader who
|
|
* mistypes a marketing URL should not land in documentation chrome with a sidebar of pages
|
|
* they were not looking for.
|
|
*/
|
|
---
|
|
|
|
<Base title="Page not found" description="That page does not exist on this site.">
|
|
<!-- The one page `Base`'s `data-pagefind-body` should not reach (D47): a search result
|
|
reading "That page does not exist" would be a small cruelty. -->
|
|
<section class="page notfound" data-pagefind-ignore>
|
|
<p class="eyebrow">404</p>
|
|
<h1>That page does not exist</h1>
|
|
<p class="prose">
|
|
The link may be out of date, or the page may not be written yet — this site is being
|
|
built in phases.
|
|
</p>
|
|
<p><a href="/">Back to the homepage</a> · <a href="/docs/">Documentation</a></p>
|
|
</section>
|
|
</Base>
|
|
|
|
<style>
|
|
.notfound {
|
|
padding-block: clamp(3rem, 9vw, 6rem);
|
|
}
|
|
|
|
.notfound h1 {
|
|
margin: 0 0 1rem;
|
|
color: var(--gold);
|
|
}
|
|
</style>
|