Skip to content

site: FAQ page at /faq/ with FAQPage structured data - #12

Merged
tristanroth1 merged 4 commits into
mainfrom
faq-page
Oct 20, 2026
Merged

tristanroth1 merged 4 commits into
mainfrom
faq-page

Conversation

@tristanroth1

@tristanroth1 tristanroth1 commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Goal

A full FAQ for grcskills.com (founder ask 2026-10-20, via the conductor): the questions people asked under the 2026-10-19 launch post, plus the ones they will ask next. Plain, true facts in his voice, with FAQPage structured data.

Change

  • site/lib/faq.ts: 29 questions in 6 groups (the basics, getting started, data and safety, how the skills do the work, ISMS Copilot and updates, contributing). One source feeds the visible page and the FAQPage JSON-LD, so they cannot drift. The install and updates answers read the release tag and the skill count from the build.
  • site/app/faq/page.tsx: /faq/ with breadcrumbs, a section index, one anchor per question, and a "Still have a question?" link to GitHub issues.
  • FAQ in the menu, footer, sitemap and llms.txt. faq is now a reserved author slug. CSS in globals.css uses the existing variables.
  • From the launch post comments: client data and confidentiality, stale evidence, policy changes, judgment formed while gathering, traceability over time, first-line skills, sensitive data scanners.
  • CHANGELOG Unreleased line.

Verified

Each answer was checked against README, AGENTS.md, SECURITY.md, CONTRIBUTING.md, LICENSE, the skill files (evidence-freshness-check, document-consistency-check, phi-flow-mapping, each skill's output-folder rule), live llms.txt, the releases, and ismscopilot.com/mcp for the plan line. The frameworks list holds only tags at least one skill uses (no 800-171 or CMMC yet). The cost line on think mode is stated on ismscopilot.com/mcp ("Think and Beyond modes need a paid plan").

Tests

New built test: the FAQPage node exists, has the right url and at least 20 questions; every question and every answer part is in the visible text; no em dash; the install answer pins the current tag; every internal link resolves; FAQ is in the sitemap and llms.txt. 48/48, typecheck clean, SEO gate L0P pass (warnings: FAQPage is on the gate's deprecated-SERP list, because Google limits FAQ rich results; the markup is kept for answer engines and the ask).

Preview: https://grcskills-na7byxk3y-better-ismss-projects.vercel.app/faq/ (prebuilt from f8f4337, protected)

Standard change (CMP 5.1): marketing site, new content page.

CODEX_REVIEW: unavailable (Codex 429, Vibe 402) -> Opus subagent 2026-10-20: r1 FIX-FIRST (9 findings, applied in d847076, plus 3 questions it suggested); r2 FIX-FIRST on one claim, ships once fixed (applied in f8f4337 with its two optional points) = SHIP

Owner: founder
Next: r2 review, founder approves the final Q&A list (one AUQ), merge, tag the next release, deploy from the tag, verify /faq/ live.

🤖 Generated with Claude Code

26 questions and answers from the repo, the live site and the launch post
comments: what it is, who it is for, cost, frameworks, agents, install,
client data and safety, stale evidence, policy changes, traceability,
ISMS Copilot, updates, contributing. One source (site/lib/faq.ts) feeds
the page and its JSON-LD; a built test checks they match. FAQ in the
menu, footer, sitemap and llms.txt; faq is a reserved author slug.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Edits answer names the own-folder output rule; network calls listed in
full; validator scope as SECURITY.md says; ISMS Copilot Free limits;
freshness window from the skill; judgment and traceability no longer
overstate; scanner answer matches phi-flow-mapping. Adds who wrote the
skills, affiliation, and correction or removal.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…uthor line, gentler wrap)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tristanroth1
tristanroth1 merged commit a0e8447 into main Oct 20, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants