ayush1974-rgb/ai_tronics_website

Purpose and Runtime

This is a single-page, visual/marketing-style Next.js application. The App Router entry point is app/page.tsx, with document-level setup in app/layout.tsx and global styling in app/globals.css. next.config.mjs and package.json define the Node/Next build runtime; no backend, API routes, database, or external service integration is present in the repository tree.

Application Shell and Entry Flow

app/layout.tsx establishes the shared page shell and is the boundary for global providers, fonts, and styles. app/page.tsx is the primary composition root: it assembles the landing experience from page-level sections and shared visual controls.

• app/layout.tsx

• app/page.tsx

• app/globals.css

Landing and Content Sections

The main page is organized as independently rendered content bands rather than routes or data-driven CMS entities. Core stages likely include hero/landing presentation, about, events, gallery, team, vibe, and contact content. Each section owns its markup and presentation data, making app/page.tsx the integration point for ordering and cross-section wiring.

• components/hero-section.tsx

• components/about-section.tsx

• components/events-section.tsx

• components/contact-section.tsx

Navigation and Page Interaction Layer

Navigation is implemented as page-local UI that likely scrolls or targets sections within the single landing page. A section menu, global navigation, footer, preloader, custom cursor, and theme provider form the persistent interaction layer around content. These components are key boundaries for browser-only behavior and page lifecycle effects.

• components/navigation.tsx

• components/section-menu.tsx

• components/preloader.tsx

• components/theme-provider.tsx

Visual Effects and Gallery Pipeline

Gallery content is served as static assets under public/gallery, separated by content type. The gallery presentation has both conventional and “infinite” variants; lib/gallery-canvas.ts is the notable rendering abstraction and likely encapsulates canvas-oriented gallery/effect behavior. Particle backgrounds and custom cursor effects are separate visual subsystems rather than application data services.

• components/gallery-section.tsx

• components/infinite-gallery-section.tsx

• lib/gallery-canvas.ts

• public/gallery/infinite

UI Foundation and Styling Boundary

Reusable primitives are centralized in components/ui, providing the shared component layer beneath page-specific sections. Styling is split between App Router globals and a legacy/shared global stylesheet location, while utility composition is centralized in lib/utils.ts. The UI directory appears to be a local component library, not an external API boundary.

• components/ui/button.tsx

• components/ui/dialog.tsx

• lib/utils.ts

• styles/globals.css

Assets and Deployment Characteristics

All visible media appears locally hosted from public/gallery, including event, landing, headshot, and infinite-gallery collections. The application can therefore be deployed as a standard Next.js frontend without required service credentials or runtime data dependencies evident from the tree.

• public/gallery/events

• public/gallery/heads

• public/gallery/landing