How saboo24/sabo works
Main components
• Frontend (Static Files): index.html, style.css, script.js
• Host/Delivery Network: GitHub Pages (or any static‐site host/CDN)
• External Service: EmailJS for contact form handling
• End User: Web Browser (Desktop, Mobile, Tablet)
Relationships and data flows
• The browser requests the static files from GitHub Pages.
• index.html pulls in style.css and script.js.
• script.js drives animations (typing effect, smooth scroll via IntersectionObserver) and handles the contact form.
• On form submission, script.js calls EmailJS APIs over HTTPS.
• EmailJS processes the request and forwards an email to the site owner.
• The browser renders the response (success/failure notification).
Architectural patterns and design principles
• Client‐side MVC-ish separation (HTML = view structure; CSS = styling; JS = behavior).
• Modular, component‐based JS (e.g., functions for typing animation, scroll listener, form handler).
• Single‐page architecture: no page reloads, smooth in‐page navigation.
Technologies to call out
• HTML5 for semantic markup
• CSS3 (Flex/Grid, keyframe animations)
• JavaScript ES6+ (modules, IntersectionObserver API)
• EmailJS (external form processing service)
• GitHub Pages (static asset hosting/CDN)