feat: add FAQ page explaining data source

[rootulp]

Adds a /faq page so visitors (and search/AI crawlers) can see where TriTimes gets its data — a question that came up on Reddit.

What

• New static /faq route with 3 Q&As: data source, IRONMAN affiliation, reporting issues.
• The data-source answer explains TriTimes reads from the Competitor.com results API (labs-v2.competitor.com) that powers IRONMAN's official results pages — not HTML-scraping, and not a documented public API.
• Q&A content + schema.org FAQPage JSON-LD live in a tested lib/faq.ts module (matches existing structured-data SEO pattern).
• Footer link for site-wide discoverability.

Testing

• New faq.test.ts (TDD); full suite 161/161 pass; eslint clean.
• Dev server smoke test: /faq returns 200 with the content and JSON-LD rendered.

No tracked issue exists; motivation is answering the recurring "do you scrape or use an API?" question.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
tritimes	Ready	Preview, Comment	Jul 16, 2026 4:29am

[coderabbitai]

Warning

Review limit reached

@rootulp, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 0753596a-8532-4c5b-b2c4-976f042781e5

📥 Commits

Reviewing files that changed from the base of the PR and between f364b9a and 4b520d5.

📒 Files selected for processing (4)

• app/src/app/faq/page.tsx
• app/src/components/Footer.tsx
• app/src/lib/__tests__/faq.test.ts
• app/src/lib/faq.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch faq-page

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}