# ever-co/ever-teams architecture

> Architecture diagram of the GitHub repository ever-co/ever-teams, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-04-01). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/ever-co/ever-teams
- Repository: https://github.com/ever-co/ever-teams

## Overview

##### 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).

## Diagram (Mermaid)

```mermaid
flowchart TD
    subgraph "Frontend Clients"
        direction TB
        Web["Web Frontend (Next.js)"]:::frontend
        Mobile["Mobile App (React Native/Expo)"]:::frontend
        Desktop["Desktop App (Electron)"]:::frontend
        Extension["Browser Extension (Plasmo)"]:::frontend
    end

    subgraph "Backend Services"
        direction TB
        APIServer["API Server"]:::backend
        ServerWeb["Server Web (Electron Wrapper)"]:::backend
    end

    subgraph "Shared & Common"
        direction TB
        Shared["Shared Libraries & Packages"]:::shared
    end

    subgraph "Deployment & Infrastructure"
        direction TB
        DeployConfig["Deployment Configurations (.deploy)"]:::deployment
        CircleCI["CI/CD (.circleci)"]:::deployment
        GitHubActions["CI/CD (.github/workflows)"]:::deployment
        Tools["Tools & Scripts (tools)"]:::deployment
    end

    subgraph "External Integrations"
        direction TB
        EverGauzy["Ever Gauzy APIs"]:::external
        ThirdParty["Other Integrations (GitHub,Slack,etc.)"]:::external
        Cloud["Cloud Hosting (Vercel/DigitalOcean)"]:::deployment
    end

    %% Connections between Frontend and Backend
    Web -->|"calls"| APIServer
    Mobile -->|"calls"| APIServer
    Extension -->|"calls"| APIServer
    Desktop -->|"calls"| ServerWeb
    ServerWeb -->|"bridges"| Web
    APIServer -->|"integrates"| EverGauzy
    ThirdParty -->|"integrates"| APIServer

    %% Shared libraries used by both Frontend and Backend
    Shared --- Web
    Shared --- Mobile
    Shared --- Desktop
    Shared --- Extension
    Shared --- APIServer
    Shared --- ServerWeb

    %% Deployment and CI/CD pipelines build and deploy services
    DeployConfig -->|"builds"| Web
    DeployConfig -->|"builds"| Mobile
    DeployConfig -->|"builds"| Desktop
    DeployConfig -->|"builds"| Extension
    DeployConfig -->|"builds"| APIServer
    DeployConfig -->|"builds"| ServerWeb

    CircleCI -->|"triggers"| DeployConfig
    GitHubActions -->|"triggers"| DeployConfig
    Tools -->|"supports"| DeployConfig
    DeployConfig -->|"deploys to"| Cloud

    %% Class definitions for color coding
    classDef frontend fill:#cce5ff,stroke:#004085,stroke-width:2px;
    classDef backend fill:#d4edda,stroke:#155724,stroke-width:2px;
    classDef shared fill:#fff3cd,stroke:#856404,stroke-width:2px;
    classDef deployment fill:#f8d7da,stroke:#721c24,stroke-width:2px;
    classDef external fill:#e2e3e5,stroke:#6c757d,stroke-width:2px;

    %% Click Events for Component Mapping
    click Web "https://github.com/ever-co/ever-teams/tree/develop/apps/web"
    click Mobile "https://github.com/ever-co/ever-teams/tree/develop/apps/mobile"
    click Desktop "https://github.com/ever-co/ever-teams/tree/develop/apps/desktop"
    click Extension "https://github.com/ever-co/ever-teams/tree/develop/apps/extensions"
    click APIServer "https://github.com/ever-co/ever-teams/tree/develop/apps/server-api"
    click ServerWeb "https://github.com/ever-co/ever-teams/tree/develop/apps/server-web"
    click Shared "https://github.com/ever-co/ever-teams/tree/develop/packages"
    click DeployConfig "https://github.com/ever-co/ever-teams/blob/develop/.deploy"
    click CircleCI "https://github.com/ever-co/ever-teams/blob/develop/.circleci"
    click GitHubActions "https://github.com/ever-co/ever-teams/tree/develop/.github/workflows"
    click Tools "https://github.com/ever-co/ever-teams/tree/develop/tools"
```
