sanjai-dev46/shalzz-genz-digital-marketer

Purpose and Entry Points

This is a Vite-powered React/TypeScript single-page presentation or marketing deck. It renders a sequence of full-screen content slides describing offerings, packages, add-ons, and contact information.

Application startup is src/main.tsx, which mounts the React tree into index.html. The root composition is src/App.tsx.

Application Shell and Slide Orchestration

src/App.tsx is the primary control boundary: it determines slide order and composes the deck from slide-level React components. There is no evidence of routing, backend integration, persistence, or asynchronous data loading.

Key paths:

• src/App.tsx

• src/main.tsx

• index.html

Slide Content Modules

Each business/presentation section is isolated as a dedicated React component under src/slides. This keeps content ownership separate while allowing the app shell to define presentation flow.

Core stages include:

• Introductory hero: src/slides/HeroSlide.tsx

• Rationale/value proposition: src/slides/WhyChooseUsSlide.tsx

• Content strategy: src/slides/ContentMixSlide.tsx

• Package offering: src/slides/GrowthPackageSlide.tsx

• Optional services: src/slides/AddOnsSlide.tsx

• Closing/contact CTA: src/slides/ContactSlide.tsx

Shared Presentation Primitives

Reusable components establish visual consistency across otherwise independent slides. SlideWrapper is the likely structural/layout boundary for slide sections; SlideTitle standardizes headings; FeatureCard supports repeated offering or benefit blocks.

Key paths:

• src/components/SlideWrapper.tsx

• src/components/SlideTitle.tsx

• src/components/FeatureCard.tsx

Styling and Theme Boundary

Global styling is centralized in src/index.css, while reusable theme values or design-token-like configuration live in src/theme.ts. Slide and shared components consume this styling layer rather than introducing a separate UI framework boundary.

Key paths:

• src/index.css

• src/theme.ts

• src/utils/cn.ts

Runtime and Assets

The client runs in the browser as a React application, built and served through Vite configuration in vite.config.ts. Static visual assets are expected under public/images and are served directly from the public asset space.

Key paths:

• vite.config.ts

• public/images

• package.json

Primary Flow and Boundaries

The runtime flow is: browser loads index.html → Vite bundle executes src/main.tsx → React renders src/App.tsx → app composes ordered slide modules → slides use shared layout/card/title primitives and global theme/styles. The repository appears fully frontend-only: no API clients, server runtime, database, authentication, or external service integration is represented in the supplied tree.