How juanromero2719/frontend-cineconecta works
Main Components
• Next.js Framework Shell – Represent the entire application as a Next.js web application.
• Client/UI Layer – Map out the “src/app”, “src/components”, and “public” directories. Note that routes such as “(auth)” and “(dashboard)” indicate distinct areas for authentication and app-specific screens.
• Server/Backend Components – Recognize the server-side files auto‑generated under the “.next/server” folder (even though they’re generated, they represent the deployed logic, including SSR and API routes).
• Business Logic & Domain Layers – Highlight core parts like “src/models”, “src/services” (such as the axiosInstance), “src/adapters” (for login, register, token verification), and “src/hooks” and “src/contexts”. These files encapsulate the application’s logic, data fetching, error handling, etc.
Relationships and Interactions
• UI Components Interaction: Show that components like “header” or “Providers” (which integrate context providers such as AuthContext) pass data and state through hooks and adapters.
• Authentication Flow: Emphasize the path from the authentication UI (cardLogin components) to the corresponding adapters (login.adapter.ts, register.adapter.ts, verifyToken.adapter.ts) and hooks (useLoginUser, useRegisterUser), then to the context (AuthContext) to manage state.
• Server‑side Rendering & Caching: Note that Next.js automatically compiles pages into chunks (.next folder) and uses file‑based configuration to render both static and dynamic pages.
Important Architectural Patterns
• File‑based Routing in Next.js – Use this to indicate clear separation between “(auth)” and “(dashboard)” routes.
• Component-based Architecture – Stress how React components, hooks, and context providers are used for modularity and state management.
• Adapter & Service Layers – Identify the adapters as bridges between external API endpoints and internal logic. Also note the use of interceptors for handling request modifications and error handling.
• Separation of Client and Server Concerns – Even though Next.js supports both, indicate how the project distinguishes between client‑side components (in “src/app” and “src/components”) and server‑side artifacts (in “.next/server”).
Specific Technologies/Frameworks
• Next.js as the core framework for rendering and routing.
• React (with hooks and context API) for the client UI.
• Axios (with a custom interceptor) for handling HTTP requests.
• Vercel (deployment hints in the README) as the recommended hosting platform.
• (Optional) ESLint, PostCSS, and TypeScript, as inferred from configuration files (e.g., tsconfig.json, eslint.config.mjs, postcss.config.mjs).