How azam-aa/tailor-connect works
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