How finaticlabs/accodyn works
Project type and purpose
• This is a Next.js-based marketing/landing website (“Accodyn Tech Website”) for an NBFC software suite.
• It’s primarily a static/SSR React app with responsive layouts, deployed on Vercel, no standalone backend microservice—just optional middleware for redirects, security headers, and rate limiting.
File structure
• Top-level config: package.json, tsconfig.json, next.config.mjs, tailwind.config.ts, postcss.config.mjs, vercel.json.
• app/ directory (Next.js 13+ App Router): page.tsx files define routes (/, /about, /waitlist). layout.tsx and globals.css set global UI and styles.
• app/components/: shared layout pieces (Navigation, Footer, ClientLayout).
• components/ui/: reusable UI primitives (Button, Card).
• util/ and lib/: helper functions (e.g., cn.ts for classNames, utils.ts).
• public/: static assets (video, robots.txt, sitemap.xml).
• middleware.ts: global request handling (redirects, security headers, rate limiting).
README for additional insights
• Confirms use of Next.js, Tailwind CSS, Vercel deployment.
• No mention of a separate API service—waitlist form likely uses a client-side integration (e.g., Google Sheets via external API).
Detail
• Every route (/about, /waitlist)
• Rendering strategy per page (SSG vs. SSR)
• Global CSS and tailwind processing step
• Middleware rules (redirect www→non-www, CSP headers, rate limiting)