How josemacruz/opositandos-web-landing works
Project type and purpose
• This is a Next.js (React-based) front-end application—specifically a marketing/landing site with pages for home, FAQ, policy, terms, etc.
File structure
• src/app – Next.js App Router entries (page.tsx, layout.tsx, nested routes for /faq, /policy, /term-and-conditions).
• src/components – Reusable UI components organized by domain (landing, layout, modals, faq, ui primitives).
• src/hooks & src/lib – Shared React hooks (e.g. useContactModal) and utility modules.
• public/images – Static assets served by Next.js.
• Config files – tailwind.config.ts, next.config.ts, postcss.config.js, tsconfig.json, eslint.config.mjs.
• package.json & lockfile & pnpm workspace – defines dependencies, scripts, build/deploy commands.
README for additional insights
• It was bootstrapped with create-next-app, uses next/font, expects deployment on Vercel.
• All pages auto-update in dev mode; no custom API routes present.
Be very detailed—capture every architectural element
– Even though there’s no database, show the public folder as an asset store.
– Include config files as part of the build pipeline.
– Separate each UI domain (landing, faq, modals, ui primitives) to illustrate modularity.
– Show the Next.js routing layer distinctly from the component implementation.