Next.js Developer — 30+ Page Marketing Site from Figma

We're building a Web3 marketing website. The Figma design is complete and approved: around 30 pages, visually rich, with an animated hero and interactive image treatments (hover and click states) used throughout the site. To be clear on scope: this is a marketing site, not a dApp. No wallet connection, no on-chain data, and no smart contract interaction. We need an experienced Next.js developer with strong motion and interaction skills. The design is final. We're looking for faithful implementation, with expertise applied to code architecture, animation quality, and performance. Figma Dev Mode access will be provided. Approach We're Looking For This is not 30 bespoke pages. The design reuses sections heavily — hero variants, feature grids, CTA bands, card layouts, and interactive image galleries. We want a reusable component library built first, then pages composed from it, then those components exposed to our CMS so our marketing team can assemble and edit pages. Please include your proposed implementation approach when submitting a proposal. Scope of Work - Build a Next.js (App Router) site from the approved Figma design - Establish design tokens and a reusable component library before page assembly - Implement all pages, matching spacing, typography, colors, radii, and shadows to the Figma specification - Implement the animated hero and all interactive image behaviors (hover and click states) across the site - Integrate Payload CMS so marketing can edit copy, images, and page composition - Responsive across desktop, tablet (max-width: 1024px), and mobile (max-width: 768px) - Responsive navigation: horizontal navigation on desktop and an accessible hamburger menu with smooth transition below 1024px - Export, optimize, and correctly serve all image and icon assets according to the provided naming conventions - GitHub repository connected to Vercel with working preview and production deployments Technical Requirements - Framework: Next.js (App Router) with TypeScript - CMS: Payload CMS - Database: PostgreSQL (Neon or Vercel Postgres) - Styling: CSS Modules with design tokens as :root CSS variables and BEM-style class naming. No Tailwind, Bootstrap, or component UI kits. - Animation: Use either GSAP (with ScrollTrigger) or Motion. Simple hover transitions should be implemented with CSS. - Motion accessibility: Full prefers-reduced-motion support - Rendering: All page content must be server-rendered and included in the initial HTML - Performance: next/image for raster assets, lazy loading below the fold, and minimal layout shift. Target Lighthouse mobile performance score of 85 or higher on representative pages. - Semantic HTML5 - Accessible interactions with proper button elements, aria attributes, visible focus states, and full keyboard navigation - No jQuery - Avoid unnecessary dependencies