How cristiancutizaca/frontend-goleman works
Project type and purpose
• This is a Next.js front-end application (React-based) serving as an informational/marketing site (likely for an educational institution: admissions, courses, diplomados, contact, social showcase, etc.).
• No explicit “backend” folder or API routes—this is primarily a static/SSR site with forms, social widgets, and possibly serverless functions (authentication utilities are present in components/utils).
File structure
• Top level:
• app/ – Next.js “app router” pages and layouts
• components/ – reusable UI components organized by domain (admision, cursos, diplomas, home, share, etc.)
• hooks/, interface/ – custom React hooks and TypeScript types/interfaces
• public/ – static assets (images, fonts, 3D models, JSON animations)
• style/ – global CSS modules and Tailwind config
• next.config.js, tailwind.config.js, postcss.config.js, tsconfig.json – configuration files
• Patterns:
• Each page under app/ imports high-level components (e.g., AdmissionForm, SocialShowcase).
• A ThemeProvider wraps the entire app (dark/light mode).
• Utility modules handle auth, token config, password hashing—these hint at a possible serverless auth layer or integration with an external auth API.
• No dedicated “api/” folder—if there are serverless functions they might be under app/api (not shown), or else the project calls out to external services (e.g., WhatsApp widget, form submission endpoint).
README
• Standard Next.js boilerplate—no custom architecture notes.
• Deployment recommended on Vercel (serverless/edge functions are available).
Elements
• Client (Browser)
• Next.js Server / Edge Functions
• React App (App Router, Pages, Components)
• Theme & State (Context Provider)
• Static Assets CDN
• External Services (Email API, WhatsApp, Social Media)
• HTTP requests (Browser → Next.js SSR/SSG)
• Data fetch or POST actions (Forms → Serverless/API)
• Context value flow (ThemeProvider → Components)
• Asset fetching (Components → CDN)
• Blue for frontend components
• Green for serverless/backend utilities
• Orange for external services
• Gray for static assets