How cybertechyrappu/my-portfolio- works
Project type & purpose (from README + tree)
This repo is a static, client-only portfolio website (no backend code present) with:
• 3D/WebGL experience via Three.js (render loop, scene/camera, shaders/materials likely)
• UI/scroll/interaction animation via GSAP
• Contact form that sends email via EmailJS (client-side API call to EmailJS service)
• Multiple static pages: index.html, privacy.html, terms.html
• Styling in style.css, behavior in script.js
• Hosted as a static deployment (README points to Vercel, but the repo itself is plain static files)
What the file structure implies architecturally
Top-level files map almost 1:1 to runtime components:
• index.html
Entry point: DOM structure, canvas container for WebGL, sections, contact form, script/style includes.
• script.js
“Application” logic in a single bundle: Three.js scene setup, render loop, GSAP timelines/ScrollTrigger, “hacker text” animation, cursor/liquid glow tracking, anti-inspect/anti-debug behaviors, EmailJS invocation.
• style.css
Visual system: glassmorphism UI, layout, responsive styling, overlay panels, canvas positioning.
• privacy.html, terms.html
Separate document routes (static pages) that share the same CSS/JS or simplified versions.
No /src, no package manager manifests shown, no server code, no API routes → treat as static site where “modules” are logical blocks inside script.js.
Main components
Think in C4-style layers (Context → Container → Component) even for a static site.
Context (Level 1)
Actors & external systems
• Visitor (User)
• Portfolio Website (this project)
• EmailJS Service (external)
Containers (Level 2)
Runtime/deployment boundaries
Client Browser
• Loads HTML/CSS/JS
• Executes Three.js/GSAP
• Sends contact requests to EmailJS
Static Hosting/CDN (e.g., Vercel or any static host)
• Serves index.html, terms.html, privacy.html, style.css, script.js
• (If relevant) TLS/HTTP caching at edge
EmailJS API (External SaaS)
• Receives client-side request
• Triggers email delivery
Components (Level 3) — inside the Browser “container”
• UI Layer (DOM)
• Navigation, sections, overlays, contact form elements
• 3D Engine (Three.js)
• Scene/Camera/Renderer
• Assets/materials (if any)
• Animation/render loop
• Animation Orchestrator (GSAP / ScrollTriggers)
• Scroll-based transitions
• Timeline coordination between DOM + WebGL states
• Interaction Effects
• Cursor tracking / liquid glow background
• “Hacker text” decoding animation
• Contact/Transmission Module (EmailJS client integration)
• Form validation
• emailjs.send(...) (or equivalent)
• Success/failure UI state
• Anti-Inspect / Anti-Debug Module
• DevTools detection hooks
• Keybind blocking / context menu blocking (if implemented)
• User → Browser (interactions: scroll, mouse, touch, form submit)
• Browser → Static Host/CDN (HTTP GET for HTML/CSS/JS)
• Browser → EmailJS API (HTTPS request carrying template params)
• EmailJS API → Email Provider → Your Inbox (optional but clarifies “delivery”)
• “GET /index.html, /style.css, /script.js”
• “POST/SDK call to EmailJS (template params)”
Architectural patterns/design principles to highlight (specific to this project)
• Client-side only: all behavior runs in the browser; no server trust boundary.
• Render-loop based subsystem (Three.js): continuous animation loop + GPU rendering (WebGL).
• Event-driven UI orchestration (GSAP + DOM events): scroll/mouse events drive both DOM and 3D state.
• Externalized “backend capability” via SaaS (EmailJS): email sending outsourced to a third-party API.
What to label explicitly (technologies & boundaries)
• “Client Browser (HTML/CSS/JS + Three.js + GSAP)”
• “Static Hosting/CDN (Vercel/Edge CDN)”
• “EmailJS (3rd-party Email API/SaaS)”
Also label boundaries:
• “User device boundary”
• “Public Internet”
• “3rd-party SaaS boundary”
• Rectangles for containers (Browser, CDN, EmailJS)
• Nested rectangles for components inside Browser (Three.js engine, GSAP orchestrator, etc.)
• Protocol (HTTP GET, HTTPS POST)
• Payload type (static assets, template params)
• Trigger (user submit, scroll, mousemove)
• User
• Browser
• UI/DOM
• Three.js WebGL Renderer
• GSAP Animation Controller
• Interaction Effects (cursor/hacker text)
• Contact Module (EmailJS client)
• Anti-Inspect Module
• Static Host/CDN
• EmailJS API
• Email Destination (Inbox) (optional)
• User → Browser: “scroll/mouse/touch/form submit”
• Browser → Static Host/CDN: “GET HTML/CSS/JS”
• Contact Module → EmailJS API: “send email (template params)”
• EmailJS API → Inbox: “email delivery”