Michael Chihlas
05646465b8
Stripe's compliance crawler fetches the apex URL without executing JS and declined live-mode review when `https://resolutionflow.com/` returned the empty SPA shell that redirected to /landing client-side. Restructure the router so / serves LandingPage directly: - `/` → new `PublicLanding` wrapper (LandingPage for anon; Navigate to /home for authed users so there's no marketing-frame flicker). - Authed tree converted to a path-less layout route with absolute child paths. QuickStartPage moves to `/home`; all other children (`/trees`, `/pilot`, `/admin/*`, `/account/*`, etc.) keep their URLs. - `/landing` kept as a one-release stale-bookmark redirect to /. - `ProtectedRoute` unauth redirect flipped /landing → /; `state.from` preserved for post-login return. Reference updates: - Post-login / post-onboarding destinations → /home: OAuthCallbackPage (incl. `?welcome=teammate` query), WelcomeStep1/2/3 dismiss-rest, AssistantChatPage post-escalate, WelcomeRouter completion/dismiss redirects, VerifyEmailPage's three "Go to dashboard" links. - Authed chrome → /home: TopBar logo, AppLayout mobile nav + drawer logo, CommandPalette Dashboard entry. - Dashboard onboarding → /home: NextStepCard `ran_session.ctaPath`, SetupChecklist `ran_session.path`, SessionHistoryPage empty-state CTA. - Public back-links → /: TermsPage, PrivacyPage, PoliciesPage, ContactPage, PromotionsPage, PublicTemplatesPage (header + footer). SharedSessionPage's `to="/"` left as-is — now correctly lands anon visitors on the public landing. Crawlability: - New `frontend/public/robots.txt` allowlisting public pages and disallowing the authed app. - New `frontend/public/sitemap.xml` for /, /pricing, /contact-sales, /contact, /templates, /terms, /privacy, /policies, /promotions. - `PageMeta` gains an `og:url` (defaults to `window.location.href`) and flips `twitter:card` to `summary_large_image` when an `ogImage` is passed. Tests: - `AppLayout.test.tsx` updated to mount at `/home`. - New `ProtectedRoute.test.tsx` asserts unauthenticated `/home` redirects to `/` (not `/landing`) and preserves origin in `state.from`. If Stripe's crawler still cannot see the site after this (zero-JS crawler), the documented next escalation is server-side prerendering of public routes via `vite-plugin-ssg`. Out of scope here. Plan: docs/plans/2026-05-13-public-landing-routing-refactor.md Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
32 lines
1.2 KiB
TypeScript
32 lines
1.2 KiB
TypeScript
import { Navigate } from 'react-router-dom'
|
|
import { useAuthStore } from '@/store/authStore'
|
|
import { PageLoader } from '@/components/common/PageLoader'
|
|
|
|
/**
|
|
* `/welcome` index — redirect to the next incomplete step (or `/` if done /
|
|
* dismissed). Decision table:
|
|
*
|
|
* onboarding_dismissed === true → /home
|
|
* onboarding_step_completed >= 3 → /home
|
|
* onboarding_step_completed === null/0 → /welcome/step-1
|
|
* onboarding_step_completed === 1 → /welcome/step-2
|
|
* onboarding_step_completed === 2 → /welcome/step-3
|
|
*/
|
|
export function WelcomeRouter() {
|
|
const user = useAuthStore((s) => s.user)
|
|
|
|
// Auth gate sits above us — but if the user object is still loading, render
|
|
// the page loader rather than racing past the redirect.
|
|
if (!user) return <PageLoader />
|
|
|
|
if (user.onboarding_dismissed) return <Navigate to="/home" replace />
|
|
|
|
const completed = user.onboarding_step_completed ?? 0
|
|
if (completed >= 3) return <Navigate to="/home" replace />
|
|
if (completed === 2) return <Navigate to="/welcome/step-3" replace />
|
|
if (completed === 1) return <Navigate to="/welcome/step-2" replace />
|
|
return <Navigate to="/welcome/step-1" replace />
|
|
}
|
|
|
|
export default WelcomeRouter
|