# taigaio/taiga-front architecture

> Architecture diagram of the GitHub repository taigaio/taiga-front, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-06-30). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/taigaio/taiga-front
- Repository: https://github.com/taigaio/taiga-front

## Overview

1. **What this repo is**
   - This is the Taiga Front client: a single-page, browser-based project management UI.
   - The app is built with **AngularJS**, authored mostly in **CoffeeScript**, with **Jade/Pug templates** and **SCSS** for styling.

2. **Top-level runtime boundary**
   - The browser loads a small bootstrap layer in `app-loader/`, then the main application from `app/`.
   - `app/index.jade` is the page shell; `app-loader/bootstrap.coffee` and `app-loader/app-loader.coffee` handle startup/loading concerns before the Angular app is fully active.

3. **Core application composition**
   - `app/coffee/app.coffee` is the main app entry point that wires together the major Angular modules.
   - The app is organized around feature modules, not a single monolith: each domain area has its own module, routes/controllers, and UI components.

4. **Feature subsystems**
   - Major user-facing domains are split into dedicated modules under `app/coffee/modules/` and `app/modules/`, including:
     - **auth**: login, registration, password recovery
     - **home**: landing/dashboard content
     - **projects**: project creation, listing, transfer, imports, project detail
     - **backlog**: sprint planning and user story backlog views
     - **kanban**: board view and drag/drop workflow
     - **taskboard**: task board and task movement
     - **issues / tasks / userstories / epics / wiki / team / profile / notifications / search**
     - **admin**: project administration, memberships, roles, values, integrations
     - **discover**: public project discovery/search pages

5. **UI building-block layer**
   - `app/modules/components/` contains reusable widgets and directives shared across features.
   - This layer includes lightboxes, filters, cards, attachments, avatars, tag controls, WYSIWYG editor wrappers, due date controls, board zoom, drag/drop helpers, and selection/search inputs.
   - These are the main presentation primitives that feature modules compose into screens.

6. **Service and resource boundary**
   - `app/modules/resources/` and `app/modules/services/` are the main non-visual layers.
   - Resource services map directly to backend entities and API endpoints: projects, users, issues, tasks, epics, history, attachments, imports, stats, etc.
   - Higher-level services handle cross-cutting client behavior such as current user state, permissions, theming, error handling, paging, avatar/logo handling, and activity tracking.

7. **Backend integration**
   - The frontend depends on a separate backend API, documented in the README as **Taiga API / taiga-back**.
   - Most feature flows are CRUD-like interactions through resource services, with the UI rendering server-backed domain models rather than keeping authoritative local state.
   - The architecture is therefore client-driven presentation on top of a REST-ish API boundary.

8. **State, navigation, and module organization**
   - Shared base utilities live in `app/coffee/modules/base/` and establish common concerns like URLs, HTTP behavior, storage, repository/model helpers, filters, and navigation helpers.
   - Feature modules typically depend on these shared primitives plus resource services.
   - Navigation, route-specific controllers, and detail views are split by domain so the same entity type can appear in list, detail, board, and edit contexts.

9. **Templates, partials, and styling**
   - `app/partials/` holds reusable Jade snippets for screen composition, lightboxes, tables, and common UI fragments.
   - `app/styles/` is layered into core, dependencies, layout, modules, and vendor-specific styles, which mirrors the feature/module structure.
   - This separation matters for architecture because most UI behavior is implemented as Angular directives/controllers, while layout and presentation are isolated in partials and SCSS.

10. **Rich interaction patterns**
   - The app relies heavily on drag-and-drop, sortable lists, lightboxes, inline editing, popovers, and WYSIWYG content editing.
   - These patterns appear across backlog, kanban, taskboard, epics, attachments, and wiki features, and are supported by shared components and custom JS helpers in `app/js/`.

11. **Localization and content**
   - `app/locales/taiga/` contains many JSON locale files, indicating multilingual UI rendering is a first-class concern.
   - User-visible text is largely externalized, so internationalization is part of the app’s core presentation architecture.
   - Emoji and markdown/rendering support are also included as static content helpers.

12. **Testing and verification**
   - Unit tests are colocated with modules and services as `*.spec.coffee`, with Karma-based test configs at the root.
   - End-to-end coverage lives under `e2e/`, with feature-focused suites mirroring the same domains as the app modules.
   - This reflects the architectural split between isolated UI/service behavior and integrated browser flows against a running Taiga backend.

13. **Build, packaging, and deployment**
   - `gulpfile.js` and related config files indicate a build pipeline that compiles CoffeeScript, templates, and styles into distributable assets.
   - Docker files and `conf/` templates show the app is designed to be served as a built frontend, with environment-specific configuration injected at runtime.
   - The README also points to `taiga-front-dist` for compiled artifacts, reinforcing that this repo is the source tree, not the deployment bundle.

14. **Diagram takeaway**
   - A good architecture diagram should show: browser entry → bootstrap/app shell → Angular feature modules → shared components/services/resources → Taiga backend API.
   - Surrounding that core should be the static asset layer, localization, build/test tooling, and E2E verification path, since those materially shape how the frontend is developed and delivered.

Main entry points: [`app/coffee/app.coffee`](https://github.com/taigaio/taiga-front/blob/main/app/coffee/app.coffee) (App entry), [`app/modules/resources`](https://github.com/taigaio/taiga-front/tree/main/app/modules/resources) (Resources), [`gulpfile.js`](https://github.com/taigaio/taiga-front/blob/main/gulpfile.js) (Build & deploy), [`app/modules/components`](https://github.com/taigaio/taiga-front/tree/main/app/modules/components) (UI components)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_runtime["Runtime"]
  node_browser(("Browser<br/>client runtime"))
  node_loader["App loader<br/>bootstrap layer"]
  node_shell["Page shell<br/>entry template<br/>[index.jade]"]
end

subgraph group_core["Core app"]
  node_app_entry["App entry<br/>angular bootstrap<br/>[app.coffee]"]
  node_base["Base layer<br/>shared foundation"]
  node_common["Common layer<br/>shared ui/services"]
  node_resources[("Resources")]
  node_services["Client services<br/>app services"]
  node_components["UI components<br/>shared widgets"]
end

subgraph group_features["Features"]
  node_auth["Auth<br/>[auth.coffee]"]
  node_home["Home<br/>dashboard"]
  node_projects["Projects<br/>project management"]
  node_planning["Planning<br/>backlog/board<br/>[backlog.coffee]"]
  node_work_items["Work items<br/>issue/task/story<br/>[issues.coffee]"]
  node_collab["Collaboration<br/>team/profile/wiki<br/>[team.coffee]"]
  node_admin["Admin<br/>[admin.coffee]"]
  node_discover["Discover<br/>public browse"]
end

subgraph group_assets["Assets"]
  node_partials_styles["Templates & styles<br/>presentation assets"]
  node_locales["Locales<br/>i18n"]
  node_js_helpers["JS helpers<br/>browser helpers"]
end

subgraph group_tooling["Tooling"]
  node_e2e["E2E suites<br/>browser verification"]
  node_build["Build & deploy<br/>tooling<br/>[gulpfile.js]"]
end

node_backend_api[("Taiga API<br/>backend api")]

node_browser -->|"loads"| node_loader
node_loader -->|"mounts"| node_shell
node_shell -->|"hosts"| node_app_entry
node_app_entry -->|"wires"| node_base
node_app_entry -->|"wires"| node_common
node_app_entry -->|"uses"| node_resources
node_app_entry -->|"uses"| node_services
node_app_entry -->|"composes"| node_components
node_app_entry -->|"includes"| node_auth
node_app_entry -->|"includes"| node_home
node_app_entry -->|"includes"| node_projects
node_app_entry -->|"includes"| node_planning
node_app_entry -->|"includes"| node_work_items
node_app_entry -->|"includes"| node_collab
node_app_entry -->|"includes"| node_admin
node_app_entry -->|"includes"| node_discover
node_components -->|"renders with"| node_partials_styles
node_components -->|"extends"| node_js_helpers
node_auth -->|"reads/writes"| node_resources
node_projects -->|"reads/writes"| node_resources
node_planning -->|"reads/writes"| node_resources
node_work_items -->|"reads/writes"| node_resources
node_collab -->|"reads/writes"| node_resources
node_admin -->|"reads/writes"| node_resources
node_discover -->|"reads/writes"| node_resources
node_resources -->|"calls"| node_backend_api
node_services -->|"calls"| node_backend_api
node_e2e -->|"verifies"| node_browser
node_build -->|"packages"| node_loader
node_build -->|"compiles"| node_partials_styles
node_build -->|"bundles"| node_locales

click node_loader "https://github.com/taigaio/taiga-front/tree/main/app-loader"
click node_shell "https://github.com/taigaio/taiga-front/blob/main/app/index.jade"
click node_app_entry "https://github.com/taigaio/taiga-front/blob/main/app/coffee/app.coffee"
click node_base "https://github.com/taigaio/taiga-front/tree/main/app/coffee/modules/base"
click node_common "https://github.com/taigaio/taiga-front/tree/main/app/coffee/modules/common"
click node_resources "https://github.com/taigaio/taiga-front/tree/main/app/modules/resources"
click node_services "https://github.com/taigaio/taiga-front/tree/main/app/modules/services"
click node_components "https://github.com/taigaio/taiga-front/tree/main/app/modules/components"
click node_auth "https://github.com/taigaio/taiga-front/blob/main/app/coffee/modules/auth.coffee"
click node_home "https://github.com/taigaio/taiga-front/tree/main/app/modules/home"
click node_projects "https://github.com/taigaio/taiga-front/tree/main/app/modules/projects"
click node_planning "https://github.com/taigaio/taiga-front/blob/main/app/coffee/modules/backlog.coffee"
click node_work_items "https://github.com/taigaio/taiga-front/blob/main/app/coffee/modules/issues.coffee"
click node_collab "https://github.com/taigaio/taiga-front/blob/main/app/coffee/modules/team.coffee"
click node_admin "https://github.com/taigaio/taiga-front/blob/main/app/coffee/modules/admin.coffee"
click node_discover "https://github.com/taigaio/taiga-front/tree/main/app/modules/discover"
click node_partials_styles "https://github.com/taigaio/taiga-front/tree/main/app/partials"
click node_locales "https://github.com/taigaio/taiga-front/tree/main/app/locales/taiga"
click node_js_helpers "https://github.com/taigaio/taiga-front/tree/main/app/js"
click node_e2e "https://github.com/taigaio/taiga-front/tree/main/e2e"
click node_build "https://github.com/taigaio/taiga-front/blob/main/gulpfile.js"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_browser,node_loader,node_shell toneBlue
class node_app_entry,node_base,node_common,node_resources,node_services,node_components toneAmber
class node_auth,node_home,node_projects,node_planning,node_work_items,node_collab,node_admin,node_discover toneMint
class node_partials_styles,node_locales,node_js_helpers toneRose
class node_e2e,node_build toneIndigo
class node_backend_api toneNeutral
```

## Components

### Runtime

Browser bootstrap and app shell

- **Browser**: client runtime · User loads the frontend in the browser
- [App loader](https://github.com/taigaio/taiga-front/tree/main/app-loader): bootstrap layer · Startup and pre-Angular loading · `app-loader`
- [Page shell](https://github.com/taigaio/taiga-front/blob/main/app/index.jade): entry template · Top-level HTML/Jade shell for the single-page app · `app/index.jade`

### Core app

Angular composition and shared platform

- [App entry](https://github.com/taigaio/taiga-front/blob/main/app/coffee/app.coffee): angular bootstrap · Main AngularJS app wiring · `app/coffee/app.coffee`
- [Base layer](https://github.com/taigaio/taiga-front/tree/main/app/coffee/modules/base): shared foundation · Core URL, HTTP, model, storage, and navigation helpers · `app/coffee/modules/base`
- [Common layer](https://github.com/taigaio/taiga-front/tree/main/app/coffee/modules/common): shared ui/services · Cross-cutting client behavior and reusable utility services · `app/coffee/modules/common`
- [Resources](https://github.com/taigaio/taiga-front/tree/main/app/modules/resources): api resources · Entity resource services for backend endpoints · `app/modules/resources`
- [Client services](https://github.com/taigaio/taiga-front/tree/main/app/modules/services): app services · Higher-level client services for permissions, user state, theme, errors, and activity · `app/modules/services`
- [UI components](https://github.com/taigaio/taiga-front/tree/main/app/modules/components): shared widgets · Reusable directives, controllers, and lightbox/UI primitives · `app/modules/components`

### Features

User-facing domain modules

- [Auth](https://github.com/taigaio/taiga-front/blob/main/app/coffee/modules/auth.coffee): auth flows · Login, registration, invitations, and recovery · `app/coffee/modules/auth.coffee`
- [Home](https://github.com/taigaio/taiga-front/tree/main/app/modules/home): dashboard · Landing and working-on views · `app/modules/home`
- [Projects](https://github.com/taigaio/taiga-front/tree/main/app/modules/projects): project management · Project create, listing, transfer, import, and detail flows · `app/modules/projects`
- [Planning](https://github.com/taigaio/taiga-front/blob/main/app/coffee/modules/backlog.coffee): backlog/board · Backlog, kanban, taskboard, and sprint planning · `app/coffee/modules/backlog.coffee`
- [Work items](https://github.com/taigaio/taiga-front/blob/main/app/coffee/modules/issues.coffee): issue/task/story · Issues, tasks, user stories, and epics detail surfaces · `app/coffee/modules/issues.coffee`
- [Collaboration](https://github.com/taigaio/taiga-front/blob/main/app/coffee/modules/team.coffee): team/profile/wiki · Team, profile, notifications, search, and wiki areas · `app/coffee/modules/team.coffee`
- [Admin](https://github.com/taigaio/taiga-front/blob/main/app/coffee/modules/admin.coffee): project admin · Project administration, memberships, roles, values, and integrations · `app/coffee/modules/admin.coffee`
- [Discover](https://github.com/taigaio/taiga-front/tree/main/app/modules/discover): public browse · Public project discovery and search pages · `app/modules/discover`

### Assets

Templates, styles, locales, and static helpers

- [Templates & styles](https://github.com/taigaio/taiga-front/tree/main/app/partials): presentation assets · Reusable Jade partials, SCSS layers, and static UI assets · `app/partials`
- [Locales](https://github.com/taigaio/taiga-front/tree/main/app/locales/taiga): i18n · Translated UI strings and language packs · `app/locales/taiga`
- [JS helpers](https://github.com/taigaio/taiga-front/tree/main/app/js): browser helpers · Vendor and custom browser-side helpers used by the app · `app/js`

### Tooling

Build, tests, and deployment

- [E2E suites](https://github.com/taigaio/taiga-front/tree/main/e2e): browser verification · Feature-oriented end-to-end browser tests · `e2e`
- [Build & deploy](https://github.com/taigaio/taiga-front/blob/main/gulpfile.js): tooling · Gulp, Karma, Docker, and config for packaging the frontend · `gulpfile.js`

### Other components

- **Taiga API**: backend api · Separate REST API backend consumed by the frontend

## Connections

- Browser → App loader: loads · Browser begins with the bootstrap layer
- App loader → Page shell: mounts · Loader brings up the page shell
- Page shell → App entry: hosts · Shell contains the Angular application entry
- App entry → Base layer: wires · App entry composes shared foundation modules
- App entry → Common layer: wires · App entry composes common cross-cutting modules
- App entry → Resources: uses · Feature flows are backed by resource services
- App entry → Client services: uses · App-wide behaviors come from client services
- App entry → UI components: composes · Features build screens from reusable UI components
- App entry → Auth: includes · Auth is one of the major routed feature areas
- App entry → Home: includes · Home is one of the major routed feature areas
- App entry → Projects: includes · Projects is one of the major routed feature areas
- App entry → Planning: includes · Planning modules drive backlog and boards
- App entry → Work items: includes · Work item detail and list modules are core features
- App entry → Collaboration: includes · Collaboration modules cover profile, team, search, wiki, and notifications
- App entry → Admin: includes · Admin routes and screens are wired from the app entry
- App entry → Discover: includes · Public discovery pages are part of the app surface
- UI components → Templates & styles: renders with · Shared widgets are backed by templates and styles
- UI components → JS helpers: extends · Components rely on custom browser helpers
- Auth → Resources: reads/writes · Auth flows talk to backend resources
- Projects → Resources: reads/writes · Project flows depend on project and import resources
- Planning → Resources: reads/writes · Boards and backlog use sprint, issue, and task resources
- Work items → Resources: reads/writes · Issue, task, story, and epic screens load server entities
- Collaboration → Resources: reads/writes · Profile, notifications, search, and wiki use backend data
- Admin → Resources: reads/writes · Admin pages manipulate project settings and memberships through resources
- Discover → Resources: reads/writes · Discovery views query public project data
- Resources → Taiga API: calls · Resources are the REST boundary to Taiga backend
- Client services → Taiga API: calls · Client services also wrap backend interactions
- E2E suites → Browser: verifies · End-to-end suites exercise the browser app
- Build & deploy → App loader: packages · Build pipeline compiles bootstrap and app assets
- Build & deploy → Templates & styles: compiles · Templates and styles are bundled into distributable assets
- Build & deploy → Locales: bundles · Translation files are included in the build
