How luis3132/autolifefe works
Project type and purpose
• This is a Next.js-based front-end web application, written in TypeScript, styled with Tailwind CSS, and organized with the new app/ directory routing.
• It exposes multiple pages under /app/home, /app/taller, etc., and relies on reusable React components (e.g. auth, navbar, servicios, vehiculo) to compose the UI.
File structure
• Top-level config files: next.config.mjs, tsconfig.json, tailwind.config.ts, ESLint config.
• /public: static assets (images, logo).
• /src/app: Next.js routes and layouts; each subfolder corresponds to a route and contains its page.tsx.
• /src/components: shared UI components grouped by feature (auth, navbar, legislacion, etc.).
• /src/lib: helper hooks (auth.ts), scripts (comprobar.ts), and TypeScript types.
Key insights from README
• Bootstrapped with Create-Next-App.
• Optimized font loading via next/font.
• Designed for deployment on Vercel but can run locally with npm run dev.
Detailed capture of essential architecture
• Break out the Next.js Server into sub-components:
• Routing layer (/src/app)
• Component library (/src/components)
• Utility layer (/src/lib)
• That each top-level route folder under /app (home, taller, etc.) is a node in the routing graph.
• Data flow: user clicks → Next.js server renders page → uses hooks from /src/lib/auth to determine session → fetches data from external API → returns HTML/CSS/JS → browser hydrates client components.