srk005/classa_web

Purpose and runtime

This is a Next.js App Router marketing/presentation site for Classa and “NextGen Learn.” It is a client-facing static-style website rather than an API-backed application. The runtime is Next.js/React with TypeScript, Tailwind/PostCSS styling, and Vercel-oriented deployment configuration: package.json, next.config.js, vercel.json.

Application shell and entry points

The root route and shared document shell are the primary execution entry points. src/app/layout.tsx establishes global layout/font/style concerns, while src/app/page.tsx renders the homepage. Global styling is centralized in src/app/globals.css. Next.js route resolution also exposes dedicated pages at /about, /classa, and /nextgen-learn.

Route-level content composition

Each major product or informational view has a route module that composes reusable presentation components:

• Homepage: src/app/page.tsx

• About page: src/app/about/page.tsx

• Classa page: src/app/classa/page.tsx

• NextGen Learn page: src/app/nextgen-learn/page.tsx

This boundary keeps URL ownership in src/app and section-level UI in src/components.

Shared site frame and conversion sections

Navigation and footer are reusable site-wide framing components, with contact content acting as the main conversion-oriented section:

• src/components/Navbar.tsx

• src/components/Footer.tsx

• src/components/ContactSection.tsx

Route pages likely assemble these around hero, informational, and trust/value sections. No server-side form handler, database, or backend integration is represented in the repository tree.

Brand and informational content modules

The core marketing narrative is implemented as reusable React sections: hero messaging, about/company copy, feature differentiation, and team presentation.

• src/components/HeroSection.tsx

• src/components/AboutUs.tsx

• src/components/WhyChooseSection.tsx

• src/components/MeetTheTeam.tsx

A separate NextGen Learn module supports the related route: src/components/NextGenLearn.tsx.

Motion and visual-experience layer

Animated and decorative components are separated from content sections, allowing pages to add visual effects without embedding animation mechanics in every route:

• src/components/AnimatedBackground.tsx

• src/components/AnimatedRocketHero.tsx

• src/components/AnimatedText.tsx

• src/components/FloatingOrbs.tsx

Additional experimental or specialized hero implementations live under src/components/ui/MaterialHero.tsx and src/components/ui/helix-hero.tsx. Ambient type declarations for animation/UI libraries are maintained in src/types/vanta.d.ts and related declaration files.

Assets, references, and deployment boundary

Public browser-served assets are housed in public/image and public/images. The ref/ directory contains prototype/replica source material, not application routes, including ref/WhyChooseSection.tsx and hero/contact JSX references. Deployment is intended for Vercel via vercel.json; no external data services or infrastructure dependencies are evident from the supplied tree.