nexoralabs-website/nexora-website

Nexora Labs is a marketing/agency website built as a Next.js 15 App Router application. The architecture is centered on a mostly static public site with a small interactive backend path for the contact form. Most of the code lives in app/, components/, and lib/, with styles/, public/, and types/ supporting presentation and shared contracts.

The application routes are simple and page-oriented: the landing page at app/page.tsx, plus dedicated privacy and terms pages. app/robots.ts and app/sitemap.ts indicate the site also generates SEO and crawl metadata at the framework level rather than through a separate backend.

The landing page is composed from modular sections in components/sections/ such as hero, services, projects, testimonials, FAQ, contact, and CTA. This suggests a single long-form conversion page broken into reusable blocks, which is typical for an agency site and makes the visual structure easy to diagram as a stack of independent content sections.

Shared chrome and persistent UI live in components/ outside the sections folder: navbar, footer, floating contact action, logo, and a loading screen. These components define the site shell around the route content and are likely reused across the legal pages and the main homepage.

The design system is built from shadcn/ui primitives under components/ui/, including button, card, input, label, textarea, accordion, and a couple of animated interaction components. This means the UI layer is split between composable base controls and higher-level marketing sections, rather than a monolithic page template.

Animation is a first-class concern. hooks/use-animations.ts, components/ui/animated-section.tsx, components/ui/magnetic-button.tsx, and the Framer Motion dependency in the README indicate scroll/entrance and interactive motion effects are layered into otherwise static content. For architecture diagrams, this is a client-side enhancement layer rather than a separate subsystem.

The primary dynamic workflow is the contact form. The form is validated with Zod via lib/validations/contact.ts, then submitted through a Next.js Server Action in app/actions/contact.ts. This gives the site a server-side boundary without a full API layer.

There is an optional persistence backend through Supabase, configured in lib/supabase.ts. The README makes clear that contact submission storage is optional: if Supabase credentials are absent, the form still validates and returns success for demo use. So the data flow is “client form -> server action -> optional Supabase insert,” with a graceful no-database fallback.

Shared application data and constants are centralized in lib/data.ts and lib/constants.ts, while lib/metadata.ts handles SEO metadata generation. This keeps content and site-wide configuration out of individual components, which is useful for diagramming a clean separation between content/config and presentation.

Utility and type boundaries are lightweight but explicit. lib/utils.ts likely contains helper functions, and types/index.ts provides project-wide TypeScript types. This indicates a small but intentional shared domain layer used by both components and server-side code.

The project is styled globally through styles/globals.css and Tailwind CSS v4, with postcss.config.mjs and next.config.ts handling build-time integration. Styling is therefore not managed by a separate design system service; it is fully embedded in the frontend build pipeline.

Static assets are stored in public/, including brand assets under public/brand. The README and scripts/extract-logos.mjs suggest brand/logo processing is part of the repo’s asset workflow, supporting a polished marketing presentation rather than dynamic media delivery.

Overall, the architecture has three main boundaries: a route/presentation layer in app/, a reusable UI/content layer in components/ and lib/, and a narrow server/data path for contact submissions via Server Actions and optional Supabase. The rest of the repository is mostly supporting infrastructure for styling, animation, SEO, and static assets.