# azam-aa/tailor-connect architecture

> Architecture diagram of the GitHub repository azam-aa/tailor-connect, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-03-09). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/azam-aa/tailor-connect
- Repository: https://github.com/azam-aa/tailor-connect

## Overview

##### Project type and purpose (from file tree + README)
**Type:** Static, multi-page website (HTML + CSS only).
**Evidence:** Top-level contains only `.html` pages and a single `styles.css`; no `src/`, no server code, no JS, no package manager files.
**Purpose (implied by page names):** “Tailor-connect” looks like a small web UI for connecting customers and tailors, with basic informational and account flows (`login.html`, `register.html`, `customer.html`, `tailor.html`, `about.html`, `index.html`).

##### What the architecture actually is (based on structure)
Because this repo is **front-end only**, the “system design” is primarily a **static site delivery architecture**:

##### Main components present in repo
- **Client (Web Browser)**
- **Static hosting / web server** (GitHub Pages, Netlify, Nginx, S3+CloudFront, etc.—not specified, but needed to serve the files)
- **HTML pages**
- `index.html` (landing / entry)
- `about.html` (info)
- `login.html` (auth UI)
- `register.html` (signup UI)
- `customer.html` (customer-facing UI)
- `tailor.html` (tailor-facing UI)
- **Shared stylesheet**
- `styles.css` (shared visual system across pages)

Pages like login/register strongly imply:
- **Backend/Auth service** (API endpoints for login/register/session)
- **Database** (users, profiles, orders, etc.)

##### Static asset delivery
- Browser requests:
- `GET /index.html`
- `GET /styles.css` (and any images if they existed—none shown)

##### Navigation (typical)
- `index.html` → `about.html`
- `index.html` → `login.html` / `register.html`

##### Forms (implied integration)
- `register.html` → *(POST)* `/register`

If the HTML does not define `action=` attributes (unknown from tree), label these as **“intended submission”** rather than asserting exact endpoints.

##### Labels
- Use exact file names as component labels (e.g., `login.html`) to keep it auditably correct.
- “HTTP GET”
- “Navigate”
- “Submit login form (POST)”

##### Delivery: Static Hosting/Web Server
4) **Pages/Assets:** `index.html`, `about.html`, `login.html`, `register.html`, `customer.html`, `tailor.html`, `styles.css`

## Diagram (Mermaid)

```mermaid
flowchart TD
  %% =========================
  %% LAYER 1: SYSTEM CONTEXT
  %% =========================
  subgraph "System Context"
    direction TB

    subgraph "Actors"
      direction TB
      Customer["Customer (User Role)"]:::actor
      Tailor["Tailor (User Role)"]:::actor
    end

    subgraph "Client"
      direction TB
      Browser["Web Browser"]:::client
    end

    subgraph "Delivery"
      direction TB
      Host["Static Web Hosting / Web Server"]:::hosting
    end

    subgraph "Implied / Out-of-repo"
      direction TB
      API["Backend / Auth API (implied)"]:::external
      DB[("Database (implied)")]:::externalDB
    end

    Customer -->|"Interact"| Browser
    Tailor -->|"Interact"| Browser

    Browser -->|"HTTP GET (HTML/CSS)"| Host

    Browser -.->|"HTTP POST (login/register, implied)"| API
    API -.->|"Persist / query (implied)"| DB
  end

  %% ======================================
  %% LAYER 2: STATIC WEBSITE (REPO CONTENT)
  %% ======================================
  subgraph "Static Website (repo)"
    direction TB

    subgraph "Pages (HTML)"
      direction TB
      IDX["index.html (Landing)"]:::page
      ABT["about.html (Info)"]:::page
      LOG["login.html (Auth UI)"]:::page
      REG["register.html (Signup UI)"]:::page
      CUS["customer.html (Customer UI)"]:::page
      TAL["tailor.html (Tailor UI)"]:::page
    end

    subgraph "Shared Asset"
      direction TB
      CSS["styles.css (Shared Styles)"]:::asset
    end

    subgraph "Documentation"
      direction TB
      README["README.md (Repo Instructions)"]:::doc
    end
  end

  %% Hosting serves repo assets
  Host -->|"Serve static file"| IDX
  Host -->|"Serve static file"| ABT
  Host -->|"Serve static file"| LOG
  Host -->|"Serve static file"| REG
  Host -->|"Serve static file"| CUS
  Host -->|"Serve static file"| TAL
  Host -->|"Serve static file"| CSS

  %% Page navigation (typical / implied by UX)
  IDX -->|"Navigate"| ABT
  IDX -->|"Navigate"| LOG
  IDX -->|"Navigate"| REG
  LOG -->|"Implied role-based navigation"| CUS
  LOG -->|"Implied role-based navigation"| TAL

  %% Shared stylesheet dependency
  IDX -->|"Load CSS"| CSS
  ABT -->|"Load CSS"| CSS
  LOG -->|"Load CSS"| CSS
  REG -->|"Load CSS"| CSS
  CUS -->|"Load CSS"| CSS
  TAL -->|"Load CSS"| CSS

  %% Implied form submissions (out-of-repo)
  LOG -.->|"Submit login form (intended POST)"| API
  REG -.->|"Submit register form (intended POST)"| API

  %% Click events (paths only)
  click IDX "https://github.com/azam-aa/tailor-connect/blob/main/index.html"
  click ABT "https://github.com/azam-aa/tailor-connect/blob/main/about.html"
  click LOG "https://github.com/azam-aa/tailor-connect/blob/main/login.html"
  click REG "https://github.com/azam-aa/tailor-connect/blob/main/register.html"
  click CUS "https://github.com/azam-aa/tailor-connect/blob/main/customer.html"
  click TAL "https://github.com/azam-aa/tailor-connect/blob/main/tailor.html"
  click CSS "https://github.com/azam-aa/tailor-connect/blob/main/styles.css"
  click README "https://github.com/azam-aa/tailor-connect/blob/main/README.md"

  %% Styles
  classDef actor fill:#FFE8A3,stroke:#8A6D1D,stroke-width:2px,color:#1f1f1f
  classDef client fill:#D6ECFF,stroke:#2B6CB0,stroke-width:2px,color:#0b1f35
  classDef hosting fill:#DFF7E7,stroke:#1F7A3A,stroke-width:2px,color:#0c2a16
  classDef page fill:#EFE7FF,stroke:#5A3DA6,stroke-width:2px,color:#1c1038
  classDef asset fill:#FFD9E8,stroke:#B83280,stroke-width:2px,color:#3a0f25
  classDef doc fill:#ECEFF4,stroke:#4A5568,stroke-width:2px,color:#111827
  classDef external fill:#FFFFFF,stroke:#6B7280,stroke-width:2px,stroke-dasharray:6 4,color:#111827
  classDef externalDB fill:#FFFFFF,stroke:#6B7280,stroke-width:2px,stroke-dasharray:6 4,color:#111827
```
