How limense/front-crea-bienestar works
Project Type & Purpose
• CREA Bienestar is a full-stack web application (Next.js 15 + React 19 + TypeScript) for managing student well-being, with authentication, role-based dashboards (Student, Professional, Tutor, Admin), appointment scheduling, resource library, and AI-driven dropout detection.
• Backend services are hosted on Supabase (PostgreSQL with RLS, Auth, Storage, Realtime) and planned integrations with Google Gemini API (AI chatbot) and Google Meet API.
File Structure Analysis
• src/app/ – Next.js App Router layout and pages, segmented by route groups:
• (auth): login, registro, recuperar/actualizar contraseña
• (estudiante)/(profesional)/(tutor)/(admin): dashboards
• citas: appointment pages + server/client handlers + wizard
• recursos: resource library
• src/components/ – Presentational React components organized by domain (citas, dashboard, ui, error-boundary)
• src/lib/ – Business logic and data-access layers:
• supabase (cliente, servidor, middleware)
• citas (actions.ts for server actions, disponibilidad, validaciones)
• auth helpers, accessibility utils, generic utils
• src/middleware.ts – Global route protection by role
• supabase/migrations/ – SQL migrations for DB schema
Key README Insights
• Authentication via Supabase Auth + middleware for route protection
• Server Actions for secure mutations (Next.js /app actions)
• Row-Level Security policies in Supabase for data isolation
• UI built with Tailwind CSS v4 + shadcn/ui components
• Accessibility (WCAG 2.1 AA) and professional UX patterns (skeletons, error boundaries)
Main Components & Interactions
a. Presentation Layer (Frontend)
• Browser → Next.js App (React Server + Client Components)
• Components: pages (app/routes), UI library (shadcn/ui), domain components (citas/calendar, dashboard sidebar)
• Middleware (src/middleware.ts) guards protected routes
b. Business Logic Layer
• Server Actions (src/lib/citas/actions.ts) invoked by React components for CRUD operations
• Client-side utilities (src/lib/citas/disponibilidad-client.ts) for real-time availability checks
• Auth helpers (src/lib/auth.ts) for session management
c. Data Layer & Services
• Supabase Client (src/lib/supabase/cliente.ts) used in Server Actions & middleware
• Supabase Server (src/lib/supabase/servidor.ts) for direct DB queries with RLS
• PostgreSQL database with tables for perfiles, citas, horarios_disponibilidad, conversaciones, mensajes, alertas, recursos, talleres, inscripciones_talleres, documentos_medicos, notificaciones, registros_auditoria
• Storage for medical documents & media
d. External APIs (future)
• Google Gemini API (AI chatbot)
• Google Meet API (virtual appointment links)
Architectural Patterns & Principles
• Layered Architecture: Presentation → Business Logic → Data Access → Database
• Next.js App Router with React Server Components for SSR/SSG & Client Components for interactive UI
• Server Actions for secure server-side mutations
• Row-Level Security in DB + middleware for zero-trust access control
• Domain-driven organization: “citas”, “recursos”, “auth”, “dashboards”
• Accessibility and UX patterns (error boundaries, skeleton loaders, ARIA compliance)