🌐 Landing Site Overview

Public marketing surface for AceSense — discovery, conversion, and AI-search visibility.

:::tip TL;DR

Repo: github.com/Acesense/acesense-landing
Live: acesense.io (Firebase Hosting target landing → site acesense-prod)
Stack: React 19 + Vite (Rolldown) + React Router + react-helmet-async + react-markdown
Content: 49 blog posts + 37 marketing pages, all markdown-driven with frontmatter
SSG: post-build prerender via Puppeteer — every content route gets static HTML for SEO + AI crawlers
Analytics: PostHog (EU) + Firebase Analytics (consent-mode v2) :::

🚀 What it does

The landing surface has three jobs:

Conversion — route users to the App Store and web app, show pricing, surface a sample post-match report.
Discovery — rank on Google + AI search for the question clusters described in SEO & Discovery, targeting evidence-backed tennis video analysis queries.
AI-search citation — every detail page ships pre-rendered HTML with Article / TechArticle / BlogPosting / FAQPage JSON-LD so PerplexityBot, ClaudeBot, OAI-SearchBot, and ChatGPT-User can ground answers in our content without executing JavaScript.
Agent discovery — /agents is an agent-facing surface advertising the public API catalog, MCP endpoint, and x402 agent-commerce path (see agent API).

🛠️ Tech stack

Technology	Version	Purpose
React	19.2.0	UI framework
Vite (Rolldown)	7.2.5	Build tool
TypeScript	5.9.3	Type safety
react-router-dom	7.x	Client routing for content tree
react-helmet-async	latest	Per-route metadata
react-markdown + remark-gfm + rehype-raw	latest	Markdown rendering
tiny local parser	n/a	YAML-ish frontmatter parsing at app build time
Puppeteer	latest (devDep)	Build-time SSG prerender
PostHog (`posthog-js` + `@posthog/react`)	latest	Product analytics, EU host
Firebase	12.x	Hosting, Analytics (consent-mode v2)

🗂️ Public route map

/                     ← homepage (App.tsx, hero + App Store badge + sample-report CTA)
/blog                 ← blog index (49 posts)
/blog/:slug
/compare              ← comparison hub
/compare/:slug        ← swingvision, pb-vision, baseline-vision, playsight, onform, topcourt, pricing-grid
/alternatives         ← alternatives hub
/alternatives/:slug   ← swingvision, onform, topcourt
/use-cases            ← persona hub
/use-cases/:slug      ← club-players, junior-coaches, parents-junior-tennis, adult-returners, coaches-async-review
/features             ← features hub
/features/:slug       ← shot-detection, ball-tracking, court-heatmap, stroke-quality, coaching-report
/how-to               ← how-to hub
/how-to/:slug         ← film-your-tennis-match, record-your-serve, share-report-with-coach
/how-it-works         ← pipeline pillar (TechArticle schema)
/accuracy             ← published methodology + benchmarks
/pricing              ← real route, not anchor
/faq                  ← FAQPage-schema FAQ
/changelog
/android              ← Android-wedge landing
/ios                  ← iOS landing
/biomechanics         ← biomechanics-keyword landing
/sweden               ← Sweden-region landing (EN/SV bilingual)
/examples             ← analysis sample gallery
/sample-report        ← static post-match report sample
/agents               ← agent-discovery surface (API catalog, MCP, x402)
/about
/contact, /privacy, /terms, /accessibility   ← static .html (Firebase rewrites)

All content + static routes are emitted into sitemap.xml (count is derived at build time from the content tree + vite.config.ts dynamic routes). The * catch-all renders a real 404 page.

📁 Source layout

acesense-landing/
├── public/
│   ├── robots.txt          ← all bots allowed (search, AI search, training)
│   ├── llms.txt            ← AI-agent content map
│   ├── og-image.png        ← 1200×630 brand card
│   └── *.html              ← static contact/privacy/terms/accessibility
├── src/
│   ├── main.tsx            ← root (HelmetProvider + BrowserRouter + PostHogProvider)
│   ├── AppRouter.tsx       ← all routes + lazy chunks
│   ├── App.tsx             ← homepage (hero + App Store badge + sample-report CTA + cookie banner)
│   ├── pages/
│   │   ├── BlogIndexPage.tsx
│   │   ├── BlogPostPage.tsx
│   │   ├── HubPage.tsx     ← /compare, /alternatives, /use-cases, /features, /how-to
│   │   └── ContentPage.tsx ← detail pages (markdown + frontmatter-driven)
│   ├── components/
│   │   ├── layout/
│   │   │   ├── PageShell.tsx      ← header/footer/Helmet wrapper
│   │   │   ├── MarkdownBody.tsx   ← strips leading H1, routes internal links
│   │   │   └── page-shell.css
│   │   └── CookieConsent.tsx
│   ├── lib/
│   │   └── content.ts      ← import.meta.glob loader for markdown files
│   ├── content/
│   │   ├── blog/           ← 49 .md files
│   │   ├── compare/        ← 7 .md files
│   │   ├── alternatives/   ← 3 .md files
│   │   ├── use-cases/      ← 5 .md files
│   │   ├── features/       ← 5 .md files
│   │   ├── how-to/         ← 3 .md files
│   │   └── static/         ← how-it-works, accuracy, pricing, faq, changelog,
│   │                        android, ios, examples, about, biomechanics,
│   │                        sweden, agents, founder, sample-report
│   └── firebase.ts         ← Firebase Analytics + consent-mode helpers
├── scripts/
│   └── prerender.mjs       ← post-build Puppeteer SSG
├── vite.config.ts          ← sitemap plugin, dynamic-routes from content
└── firebase.json           ← rewrites for static .html + SPA fallback

⚙️ Build pipeline

The prerender step is non-optional for AI-bot visibility. Skipping it means PerplexityBot et al. see only the SPA shell.

🤖 AI-discovery infrastructure

Asset	Purpose	Location
`robots.txt`	Per-bot allow rules — all bots welcome	`public/robots.txt`
`llms.txt`	Content map for AI agents	`public/llms.txt`
`sitemap.xml`	All indexable URLs (derived from content tree at build)	emitted by `scripts/prerender.mjs`
Per-route HTML	Pre-rendered with page-specific `<title>`, description, OG, JSON-LD	`dist/<route>/index.html`
Schema	`Organization` + `WebSite` + `SoftwareApplication` on `/`; `Article`/`TechArticle`/`BlogPosting`/`FAQPage` + `BreadcrumbList` on each detail	inline `<script type="application/ld+json">`

Cloudflare note. acesense.io is fronted by Cloudflare. Cloudflare's Content Signals feature can override the origin's robots.txt. Manage via Cloudflare dashboard → Security → Bots → Manage AI Bots.

See reference/seo-discovery for the full surface.

📊 Analytics

Tool	Surface	Why
PostHog (EU)	All routes	Cross-surface user journey, autocapture, no session recording on landing
Firebase Analytics	All routes	GDPR consent-mode v2, Google Ads parity if we ever run paid

PostHog token + host are in .env (gitignored). See reference/analytics for the cross-surface setup.

🚀 Common commands

cd acesense-landing
pnpm install
pnpm dev              # vite dev server
pnpm build            # tsc + vite build + SSG prerender
pnpm preview          # serve dist/ locally
firebase deploy --only hosting:landing

SEO discovery surface — sitemap, robots, llms.txt, JSON-LD, SSG
Cross-surface analytics — PostHog setup across all 6 surfaces
ADR-0005: PostHog EU as product analytics
Architecture overview

Was this page helpful?

🚀 What it does​

🛠️ Tech stack​

🗂️ Public route map​

📁 Source layout​

⚙️ Build pipeline​

🤖 AI-discovery infrastructure​

📊 Analytics​

🚀 Common commands​

📚 Related docs​