Queue-North-Website/docs
null aff80334df feat(content): publish Levi's approved UC and Contact Center pages
The work this batch exists for. Levi Halford approved two copy sheets on
2026-08-28 and sent them the same day; they were never deployed. Closes #220,
#219 and #218.

What ships, verbatim from the sheets:

  /services/unified-communications   1,125 words, 10 sections,  7 FAQs
  /services/contact-center           2,499 words, 12 sections, 10 FAQs

Titles, H1s, hero subheadings and descriptions are the approved strings exactly,
including descriptions at 164 and 191 characters, which are emitted whole rather
than clamped. Each section opens with its direct answer, because that passage is
what a search result or an AI answer quotes. Every section carries a stable,
letter-first anchor, so an answer can deep-link to it. The FAQ is visible h3 and
p, with no FAQPage markup, as the sheets require.

The old copy goes: the unattributed "99.999% uptime reliability" the sheet named,
and both pages' short blurbs, which the approved sections now say at length.
idealFor stays, because the services index prints it as "Best fit".

Levi's two constraints are held and proven, not assumed. The footer is byte for
byte identical to the pre-batch build on all 19 pages. The Quick Info box is on
both pages, unchanged.

Verified against the built HTML, not the source: title, description and H1 match
the sheets exactly; all 22 approved H2s and all 17 FAQ questions are present; no
website-manager direction survived (checked against 20 phrases); no 99.999, no em
dash, no U+FFFD, no markdown. In a browser: no horizontal scroll, no broken
image, no console error at 320, 390, 768 and 1024; hydration clean on all 18
pages; all 24 section anchors deep-link correctly.

Docs corrected in the same commit, because each would have sent the next writer
the wrong way: REDESIGN_REVIEW's metrics lists now carry the owner's 2026-09-10
direction that a figure must be current, vendor-attributed and verified;
OVERHAUL_PLAN gains the long-form blueprint and stops recommending an accordion
for an FAQ; README stops claiming a server-rendered privacy fallback that never
existed, and says what hydration actually does now.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-10 05:05:21 -05:00
..
architecture fix(seo): the production sitemap had no dates, and the build context had secrets 2026-09-10 04:58:37 -05:00
data docs: adopt project template, retire the markdown backlog 2026-08-18 01:21:13 -05:00
design feat(content): publish Levi's approved UC and Contact Center pages 2026-09-10 05:05:21 -05:00
history docs: log Batch 11 and Batch 16 — four false, two real, found by rendering 2026-08-18 04:09:31 -05:00
planning feat(deploy): production always runs a numbered version 2026-08-18 02:54:42 -05:00
qa fix(qa): the browser check measured 5 of 18 pages and heard no errors 2026-09-10 04:53:51 -05:00
security security: the scanner never ran its private-key pattern, and verify never saw dist 2026-09-10 04:23:39 -05:00
DOC_TRUST_MAP.md fix(security): stop secrets.sh flagging every prerendered page, and clear the dangling doc claims 2026-08-18 01:40:46 -05:00
OPERATIONS.md fix(seo): the production sitemap had no dates, and the build context had secrets 2026-09-10 04:58:37 -05:00
TOOLS.md fix(seo): the production sitemap had no dates, and the build context had secrets 2026-09-10 04:58:37 -05:00
WORK_CYCLE.md feat(deploy): production always runs a numbered version 2026-08-18 02:54:42 -05:00