Ishagirlspg

Core System Architecture The project is a pure front‑end Next.js application that renders most pages as server components while isolating interactive parts as client components ('use client'). The Carousel component wraps the embla-carousel-react hook, exposing its API through a React context (CarouselContext) and a useCarousel hook, enabling any descendant to control scrolling and query state. Global styling is provided via app/globals.css and Tailwind utility classes, while reusable UI pieces live under components/ui.

Static Asset & Data Ingestion All content is static or fetched at build time. Images, fonts (via next/font), and CSS are processed by the Next.js compiler and Tailwind JIT. No runtime data ingestion pipelines exist; the site relies on pre‑rendered HTML and client‑side hydration for interactivity.

Execution Flow When a request hits the server, Next.js renders the page tree, streaming HTML to the browser. Upon hydration, client components such as Carousel and ContactForm initialize. The carousel registers event listeners (reInit, select) and updates its scroll state via React state hooks. Keyboard events are captured to provide Arrow‑key navigation, and the toast hook manages a single toast queue with time‑outs.

Security Guardrails The codebase respects Next.js security defaults: automatic XSS protection, CSP headers, and server‑only rendering for non‑interactive pages. Client‑only modules are explicitly marked with 'use client' to prevent accidental server‑side execution. No external API endpoints are defined, reducing attack surface.

Build Topology The application is built with the Next.js compiler, which bundles React, Tailwind, and third‑party libraries into optimized chunks. Deployment targets Vercel (or any Node‑compatible platform), leveraging incremental static regeneration where applicable. ESLint and TypeScript enforce code quality and type safety throughout the pipeline.