feat: build step 1 — scaffold, layout, header, footer, SEO; zero JavaScript
Build order step 1 (docs/01): scaffold, tokens, base layout, header, footer, SEO component, plus a temporary /type-scale/ proof sheet that step 2 deletes. THE FONTS WERE NEVER ON DISK. global.css declared six @font-face rules pointing at /fonts/*.woff2 and public/fonts/ did not exist, so every face had been silently falling back to Georgia and the system sans. Six cuts committed, 123,804 bytes, SIL OFL 1.1, provenance in docs/reference/fonts-provenance.md. ?v=1 on every URL because the deploy script serves them immutable for a year. ZERO JAVASCRIPT. The reveal was an inline IntersectionObserver in <head>; docs/05 specifies script-src 'self' with no unsafe-inline, so the only script on the site was the one thing the site's own CSP would refuse to execute. Replaced with animation-timeline: view() behind @supports. 0 script tags and 0 .js files in dist. The infinity mark is lifted verbatim from the deployed site's own smlMark loading thumbnail, not redrawn (Q32 asks whether a canonical vector exists). The proof sheet computes its contrast table from tokens.css rather than restating docs/02 — all eleven ratios reproduce the measured table exactly. Register: Canadian Tax Foundation added (§4, R10 widened); Q30 closed — SML Company Ltd is federally incorporated under the CBCA, and the footer publishes neither that nor the place of business; Q31 closed — Plausible, on EU-only data residency (D15 amended). ROLE constants added for "Director of Firm Operations" and "active litigation exposure" so step 3 does not hand-type them. Lighthouse unavailability now stated in six places rather than left as a control that had silently stopped existing (§7, R11). Both review agents ran twice. The second pass found four defects in the first pass's fixes, including the minifier bug written back into its own fix and a colour-alone repair that used the banned gold-on- cream pairing at 2.10:1. Measured in headless Chrome at thirteen widths with a seventh nav item injected: 0 overflow, 0 tap targets under 44x44, 0 focus-order inversions, state indicators at 12.29:1, 755 words of body text with no JavaScript. Opened: Q32-Q37. Closed: Q30, Q31. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012XquaEq4BgWMCwUqLEyNkF
This commit is contained in:
Pouya Lajevardi
co-authored by
Claude Opus 5
Claude Opus 5
parent
8f1df2c27c
commit
8134709548
+39
-12
@@ -1,7 +1,14 @@
|
||||
# 04 — Discoverability
|
||||
|
||||
The problem this project exists to fix. `AGENTS.md` §2 has the measurements: a
|
||||
server-side fetch of the live site returns three words.
|
||||
The problem this project exists to fix. `AGENTS.md` §2 has the measurements.
|
||||
|
||||
> **Those measurements are under review — `AGENTS.md` Q34.** They were taken on
|
||||
> 2026-08-25; a re-fetch on 2026-08-26 returned a bundler harness whose real
|
||||
> `<head>` sits JSON-escaped inside a `<script>` and whose application lives in
|
||||
> nine UUID-named files that were not fetched. Some of §2 reproduced exactly
|
||||
> (the 2.2 MB single file, the placeholder `<title>`); some could not be
|
||||
> reproduced from the served HTML at all. **Cite §2, and cite Q34 with it. Do
|
||||
> not put any of these figures in public copy until Q34 closes.**
|
||||
|
||||
---
|
||||
|
||||
@@ -82,15 +89,21 @@ to be machine-readable.
|
||||
|
||||
## Crawlability
|
||||
|
||||
**`public/robots.txt`:**
|
||||
**`public/robots.txt` is the artefact — read it, do not read a copy of it
|
||||
here.** This spec used to reproduce the file inline and the reproduction had
|
||||
already drifted from it by 2026-08-26, which is the failure mode the `AGENTS.md`
|
||||
§7 rule exists to stop.
|
||||
|
||||
```
|
||||
User-agent: *
|
||||
Allow: /
|
||||
Disallow: /legal/
|
||||
|
||||
Sitemap: https://adr.smlcompany.ca/sitemap-index.xml
|
||||
```
|
||||
**It disallows nothing, and that is deliberate.** This spec previously
|
||||
prescribed `Disallow: /legal/` alongside `noindex` on those pages, and the two
|
||||
cancel each other: a crawler forbidden to *fetch* a URL never reads the
|
||||
`noindex` on it. `/legal/privacy/` and `/legal/terms/` are linked from the
|
||||
footer of every page, so they are discovered regardless — and the likely result
|
||||
of the pair was Google listing the bare URLs as "no information available", the
|
||||
opposite of the intent, with the directive that would have suppressed them
|
||||
sitting unread behind the wall. **`noindex` is what de-indexes; `Disallow` is
|
||||
what prevents fetching.** Use the one that matches the problem, and never both
|
||||
on the same path.
|
||||
|
||||
Do not block AI crawlers. Being read by an assistant that a general counsel is
|
||||
using to shortlist neutrals is the point.
|
||||
@@ -117,7 +130,16 @@ Core Web Vitals are a ranking input, and the current build fails all of them.
|
||||
| CLS | < 0.05 |
|
||||
| INP | < 150 ms |
|
||||
| JS per route | < 100 KB |
|
||||
| Lighthouse (mobile) | ≥ 95 all four categories |
|
||||
| Lighthouse (mobile) | ≥ 95 all four categories — **not measurable until step 7, see below** |
|
||||
|
||||
> ⚠️ **Lighthouse verification is UNAVAILABLE until build step 7.** `@lhci/cli`
|
||||
> was removed on 2026-08-26 — it was the sole source of all 10 `npm audit`
|
||||
> findings (7 high), `0.15.1` is `latest` so there was no clean upgrade, and it
|
||||
> could not run at all with no pages and no `lighthouserc`. The budget below is
|
||||
> not suspended; the tool that measures it is absent. Re-add at step 7 under
|
||||
> `AGENTS.md` R11, checking for a patched release rather than assuming `0.15.1`
|
||||
> is still the ceiling. Until then, a run that skips this is skipping something
|
||||
> known — not something forgotten. `AGENTS.md` §7 has the state.
|
||||
|
||||
How: static HTML, self-hosted preloaded subset fonts, AVIF/WebP with explicit
|
||||
dimensions, critical CSS inlined, no third-party scripts on any page except the
|
||||
@@ -128,7 +150,10 @@ booking embed on `/contact/` — and that one is lazy-loaded behind a click.
|
||||
Not code, but it belongs in the launch checklist: Google Business Profile for the
|
||||
practice; ADRIC and ADRIO directory listings pointing at the site; a LinkedIn
|
||||
profile whose headline and Featured section match the brand (brief §VIII);
|
||||
consistent name, address, and phone across all of them.
|
||||
consistent naming across all of them. **Not "name, address and phone"** — §4
|
||||
publishes no phone number and no street address, only "Toronto, Ontario; by
|
||||
appointment". Directory forms that demand a full NAP get what §4 verifies and
|
||||
nothing more.
|
||||
|
||||
## Post-launch verification
|
||||
|
||||
@@ -139,3 +164,5 @@ consistent name, address, and phone across all of them.
|
||||
- [ ] Sitemap submitted to Google Search Console and Bing
|
||||
- [ ] No page returns 200 for a URL that should 404
|
||||
- [ ] Lighthouse ≥ 95 mobile on `/`, `/about/`, one practice page, one article
|
||||
— **blocked until `@lhci/cli` is re-added at step 7.** Do not tick this box
|
||||
from a manual Chrome DevTools run and call it the same check
|
||||
|
||||
Reference in New Issue
Block a user