How mikansc/connectlab works
Project type and purpose
• This is a single-page, front-end React application (built with Vite) that serves as the UI for the “DEVInHouse ConnectLab” platform.
• Purpose: allow users to log in, view devices, add/update devices and users, fetch weather info, and look up addresses by CEP.
• It integrates with an external back-end API (Node) and third-party services (Weather API, ViaCEP).
File structure
• Top-level:
• Dockerfile / docker-compose.yml / netlify.toml – containerization and deployment configs
• public/index.html – app shell
• src/ – application source
• src/App.jsx + src/main.jsx & src/routes – entry point + router
• src/components – atomic design layers (atoms → molecules → organisms → templates → pages)
• src/contexts – React Contexts for auth, devices, app state
• src/hooks – custom hooks for fetching data & controlling UI state
• src/services/http – HTTP service layer with Axios factories, adapters, and service functions (authService, deviceHttpService, weatherHttpService, etc.)
• src/services/local – local storage abstractions
• src/i18n – localization with translation JSONs
• src/themes – global styles and theme definitions
• src/validations – input validation schemas
README for additional insights
• Describes environment variables for API endpoints and keys
• Documents local and Docker-based setup
• Mentions a separate Node back-end repo
Final advice
• Interactions (authentication flow, data fetch/update).
• Essential architectural elements without over-splitting trivial files—focus on functional groupings.