How ever-co/ever-teams works
Project Type and Purpose
• This is a monorepo for a full-stack, multi-platform application—a work and project management platform. It provides web, mobile, desktop, and browser extension clients and connects to backend APIs (including Ever Gauzy APIs for business management).
• The README emphasizes work/time tracking, project/task management, integrations (e.g., with GitHub, GitLab, Bitbucket, JIRA), and rich user interfaces. The tech stack includes TypeScript, Nx/Lerna (for the monorepo), Next.js, React, React Native/Expo, Electron, and Tailwind.
File Structure
• Major top-level directories include:
– /apps/web: The Next.js–based web application.
– /apps/mobile: The Expo/React Native mobile app.
– /apps/desktop: The Electron-based desktop application.
– /apps/extensions: The browser extensions using Plasmo.
– /apps/server-api and /apps/server-web: These house the API server and the web server (wrapped in Electron) serving the frontend.
• Other directories (like /packages) host shared libraries and common code across the apps.
• Deployment configuration is found in the .deploy folder, along with Kubernetes manifests, Docker Compose files, and CI/CD workflows in .circleci and .github/workflows.
README for Additional Insights
• The README outlines how the system supports multiple platforms (web, mobile, desktop, extension) and how each piece is built using modern frameworks.
• It lists the technology stack (TypeScript, Nx/Lerna, Next.js, Expo/React Native, Electron, Tailwind, and several UI libraries) and deployment options (Docker Compose, Vercel, DigitalOcean, Kubernetes, etc.).
Elements
• Use clear labels for each major component (e.g., “Web Frontend (Next.js)”, “Mobile App (React Native)”, “API Server”, “Desktop App (Electron)”, “Browser Extension”, “Shared Services”, “Deployment Infrastructure”).
– Client requests from web/mobile/desktop/extension → backend services/API.
– CI/CD workflows → Build and deploy containers/images.
– Integration flows (e.g., API calls to Ever Gauzy) should be distinctly marked.
• Optionally, highlight external integrations (such as cloud hosting and third-party API dependencies).