Add Services FAQ page

[claude]

Requested by Sean, Michelle · Slack thread

Before: the site had no FAQ page — just a small six-question inline FAQ block on /services.

After: a dedicated FAQ page at /faq carrying all 12 Q&As from issue #34 under its four headings, linked from the services page (the inline FAQ is now a teaser pointing at /faq) and from the footer.

What: Adds the Services FAQ page drafted in #34, including Michelle's sequencing-technology Q&A verbatim, and reconciles the old inline services FAQ into a teaser.

How: New src/pages/faq.astro built from the existing BaseLayout / Eyebrow / PageNav / CtaBand components with the same section styling as /services. The FAQPage JSON-LD is now emitted by /faq (@id …/faq#faq, 12 questions) and removed from /services; the services page keeps its BioInfoOS and quote-builder asides in the teaser section. Footer gains a FAQ link, llms-full.txt points at the new route, and the e2e specs were updated to match (JSON-LD assertions moved to a new tests/e2e/faq.spec.ts).

Closes #34

Summary

• Add /faq with the 12 drafted Q&As (4 groups), scroll-spy PageNav, and FAQPage JSON-LD
• Replace the inline services FAQ with a teaser linking to /faq; add footer link; update llms-full.txt
• Update/add Playwright specs for the moved FAQ content

Scope

• Page copy or content (src/pages/*, src/data/*)
• Components / UI (src/components/*)
• Design tokens / styles (src/styles/*)
• Imagery (public/assets/images/*)
• Agent-facing data (public/llms.txt, src/pages/api/*.json.ts) — src/pages/llms-full.txt.ts
• Build / CI / deploy (astro.config.mjs, .github/, wrangler.toml)
• Tests (tests/**)
• Docs (docs/**, README.md)

Verification

• npm run check — 0 errors
• npm test — all pass (113/113)
• npm run test:e2e — not run in this sandbox (no Playwright browsers); specs updated to match the new structure, please run in CI
• Visually verified on desktop + mobile breakpoints (if UI-touching)
• Lighthouse didn't regress perf / a11y / SEO on affected pages
• JSON-LD validates (if structured data changed) — same shape as before, @id moved from services#faq to faq#faq; please spot-check

npm run build and npm run lint also pass (build's Request.cf fetch warning is the known Cloudflare-adapter sandbox fallback, unrelated).

Open questions for review

• CTA wording: the draft (per Michelle) says Click "talk to us" — the site's primary CTA is the quote builder, and "Talk to us →" exists only as a text link. I kept the "talk to us" phrasing and linked each mention (including the one inside Michelle's verbatim Q&A) to /contact?topic=sequencing. Michelle to decide the final wording/label.
• Preservation guidance ([confirm: preservation guidance per sample type]): kept generic — "requirements depend on sample type and assay; we'll cover them during scoping." Needs verification before adding specifics.
• Data ownership / confidentiality ([confirm: data ownership / confidentiality policy]): the unverified "Your project data belongs to you" claim is not published; the answer defers to scoping ("if your project has specific confidentiality or data-ownership needs, talk to us"). Needs the real policy wording.
• Inline-FAQ reconciliation choice: /faq is canonical; /services keeps only a teaser + link, and the FAQPage JSON-LD moved with the content to avoid duplicate structured data. The BioInfoOS / quote asides stayed on /services. Fine to revisit if you'd rather keep a few Q&As inline.

Notes for reviewer

Route chosen: /faq (flat, matching the site's flat page routing). Nav left unchanged (top level is intentionally tight); linking is via services teaser + footer.

---

Generated by Claude Code