feat(landing): add comparison pages

[lentil32]

One-Line Summary

Adds SEO-focused comparison pages for evaluating OneQuery against direct credentials, MCP database servers, internal agents, BI chatbots, Metabase, and DataGrip.

User-Facing Changes

• Adds a /compare/ index page that links to six OneQuery comparison pages.
• Adds comparison pages for direct database credentials, MCP database servers, internal data agents, BI chatbots, Metabase for AI agents, and DataGrip for AI agents.
• Adds a Compare link to the landing header navigation.
• Each comparison page includes a direct answer, criteria table, best-fit guidance, rollout steps, FAQ, and reference links.

Why This Changed

The landing site had docs, blog, and connector pages, but no dedicated comparison content for teams evaluating how AI agents should access production data. That left SEO and GEO coverage thin for OneQuery vs ... searches and made it harder to explain where OneQuery fits next to BI tools, IDEs, protocol adapters, and custom agents.

How It Changed

• Added a typed compare MDX content collection with validated frontmatter for page metadata, comparison criteria, FAQ content, rollout steps, and references.
• Added /compare/ and /compare/[comparisonSlug]/ Astro routes that render shared comparison layouts from MDX content.
• Added comparison-specific CSS for dense landing-page content, responsive tables, guidance panels, FAQ sections, and related comparison cards.
• Added comparison structured data for the index and detail pages, including CollectionPage, ItemList, WebPage, FAQPage, and breadcrumbs.

Extra Context / Decisions (Optional)

• The comparison pages are MDX content instead of hard-coded page data so SEO copy can be edited as content while the shared renderer keeps layout and schema consistent.
• No screenshot is attached because the in-app Browser backend was unavailable during local verification; generated and live HTML were checked instead.

Verification

• rtk bunx turbo typecheck --json --filter=@onequery/landing
• rtk bun lint --format json apps/landing/src/content.config.ts apps/landing/src/shared/components/Header.astro apps/landing/src/shared/seo/constants.ts apps/landing/src/shared/seo/schema.ts apps/landing/src/features/compare apps/landing/src/pages/compare
• rtk bunx oxfmt --check apps/landing/src/content.config.ts apps/landing/src/shared/components/Header.astro apps/landing/src/shared/seo/constants.ts apps/landing/src/shared/seo/schema.ts apps/landing/src/features/compare/data.ts apps/landing/src/features/compare/schema.ts apps/landing/src/features/compare/types.ts apps/landing/src/pages/compare/index.astro apps/landing/src/pages/compare/[comparisonSlug].astro
• rtk bunx turbo build --json --filter=@onequery/landing
• rtk bun run format
• rtk git push -u origin add-pages ran the pre-push lint-full hook successfully.

Video / Screenshot (Optional)

• N/A

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	onequery-landing	f28b8bd	Commit Preview URL Branch Preview URL	Jun 04 2026, 01:34 AM