adityakumaaar/doctorbabu

Purpose and entry points

DoctorBabu is a Vite/React TypeScript marketing-site frontend. The browser bootstraps from index.html into src/main.tsx, which renders the application root in src/App.tsx. Styling is supplied through src/index.css and shared global styles in src/styles/globals.css.

Application composition and navigation

src/App.tsx is the primary composition and control boundary: it assembles the landing-page sections and exposes page-level views. The site appears to use client-side view selection rather than a dedicated router, with standalone marketing/conversion pages such as src/components/FeaturesPage.tsx, src/components/PricingPage.tsx, and src/components/SecurityPage.tsx.

Landing-page content pipeline

The main page is built as ordered presentational sections:

• Acquisition messaging: src/components/Hero.tsx, src/components/Benefits.tsx, src/components/Features.tsx

• Product/process explanation: src/components/HowItWorks.tsx, src/components/Cohorts.tsx

• Social proof and conversion: src/components/Clients.tsx, src/components/Testimonials.tsx, src/components/CTA.tsx

These components primarily flow static content and user interactions upward through the app-level page/navigation boundary.

Conversion flows

Dedicated views represent the key lead-generation lifecycle:

• Trial initiation: src/components/StartFreeTrialPage.tsx

• Demo request: src/components/BookDemoPage.tsx

• Completion/confirmation: src/components/AccountCreatedPage.tsx

The available tree contains no backend, API client, serverless function, or persistence layer. Any submission behavior is therefore either local/UI-only or delegated to mechanisms not represented in this repository.

Shared site shell and design system

src/components/Header.tsx and src/components/Footer.tsx define the persistent site chrome and likely own navigation triggers. Reusable interaction primitives live in src/components/ui/, notably src/components/ui/button.tsx, src/components/ui/dialog.tsx, and src/components/ui/form.tsx. This forms a boundary between product-specific marketing components and a generic UI component library.

Assets, runtime, and deployment

The runtime is a client-rendered React application built and served by Vite, configured through vite.config.ts; TypeScript configuration is in tsconfig.app.json. Static/public resources are hosted from public and component-associated assets from src/assets. netlify.toml indicates Netlify deployment infrastructure. src/components/figma/ImageWithFallback.tsx provides an image-rendering resilience boundary for design-derived assets. No external SaaS integrations are identifiable from the supplied tree.