How eliasmolina023/provetecnia-sync-field works
Project type and purpose
• This is a single‐page dashboard application (SPA) implemented in React + TypeScript, built with Vite, styled via Tailwind CSS and shadcn-ui.
• Its purpose is to present multiple pages (Dashboard, Servicios, Usuarios, Viáticos, Reportes) under a common layout (ProvetecniaLayout) and a custom UI component library.
File structure
• Top-level config: package.json, tsconfig*.json, vite.config.ts, tailwind.config.ts, eslint.config.js.
• public/: static assets (index.html, robots.txt).
• src/main.tsx: application entry point.
• src/App.tsx & src/App.css: root component and global styles.
• src/pages/: route components for each view.
• src/components/layout/: the shell (ProvetecniaLayout).
• src/components/dashboard/: dashboard‐specific widgets.
• src/components/ui/: shadcn-ui primitives and custom UI building blocks (buttons, cards, dialogs, etc.).
• src/hooks/, src/lib/: custom hooks and utility functions.
Key insights from README
• No backend in repo; purely frontend.
• Dev flow revolves around Lovable (for in-browser editing & auto commits) and local IDE + npm/Vite dev server.
• Deployment is “Publish” via Lovable to a static host, with optional custom domains.
a. Main components
• Developer Workstation (IDE + Git CLI or Lovable UI)
• Source Repository (GitHub or Lovable’s Git backend)
• CI/CD / Build Pipeline (Vite bundler + Tailwind compiler + npm scripts)
• Hosting/CDN (Netlify/Vercel or Lovable’s static hosting)
• Browser (end user)
b. Relationships & data flows
• Developer pushes code → Git repo
• Git hook or Lovable UI auto-triggers build → Vite compiles TSX + tailwind → produces static assets
• Built assets deployed to CDN/host
• Browser requests index.html → JS bundles loaded → React Router renders src/pages under ProvetecniaLayout
• User interactions → React state/hooks/utility functions → UI updates
c. Architectural patterns & principles
• Component-based design: UI primitives in src/components/ui, composed into higher‐level widgets and pages
• Feature/route folder organization (pages)
• Single entry point (main.tsx → App.tsx) with client-side routing
• Utility abstraction (src/lib/utils.ts) and custom hooks (src/hooks)
d. Key technologies
• Vite (dev server & bundler)
• React + React Router (routing via pages folder)
• TypeScript
• Tailwind CSS & shadcn-ui (design system)
• npm/Yarn (package management)
Essential detail checklist
• Separation of concerns: Dev vs. Build vs. Runtime
• Central React App (main.tsx → App.tsx) and routing layer
• Detail component hierarchy: layout → pages → widgets → UI primitives
• Optional custom domain and DNS pointing at CDN/hosting