How divyanshu0-0/web-for-artists works
1. Repository shape
- This is a single-page, single-file static site. The entire application lives in mehndi-luxury-website.html, with README.md as documentation and no source subdirectories, build pipeline, or backend code.
2. Primary runtime model
- The site runs entirely in the browser using plain HTML, CSS, and vanilla JavaScript.
- All behavior is client-side; there is no server state, database, API layer, or framework runtime in the repo.
3. External dependencies
- The page pulls UI and animation libraries from CDN links, mainly:
- Three.js for the hero scene
- GSAP plus ScrollTrigger and ScrollToPlugin for motion and navigation
- VanillaTilt for 3D card interaction
- Google Fonts for typography
- These dependencies materially shape the architecture because the site’s visual system is built around them, but they are not bundled locally.
4. Global design system
- The CSS is organized as one large stylesheet with commented sections.
- A CSS custom property theme system controls the entire palette and supports dark/light mode by switching variables rather than swapping layouts or components.
- The styling layer also implements glassmorphism, ornamental frames, responsive layout rules, and all hover states.
5. Hero subsystem
- The top of the page is a 3D cinematic hero driven by Three.js.
- It renders a particle/mandala-style scene in a canvas and is animated by a dedicated requestAnimationFrame loop plus a GSAP entrance timeline after the preloader completes.
- Mouse movement influences the scene through parallax, making the hero a distinct interactive layer rather than static decoration.
6. Load and entrance flow
- A preloader is shown first, with an SVG mandala draw animation.
- Once loading completes or a timeout elapses, the preloader fades out and the rest of the page is revealed via GSAP.
- This creates a staged entry sequence: preloader → hero reveal → scroll-enabled section animations.
7. Scroll and reveal system
- Most content sections are connected by GSAP ScrollTrigger.
- Elements marked for reveal animate on scroll using opacity/transform-based transitions, which keeps the experience smooth and GPU-friendly.
- Smooth anchor navigation is handled by ScrollToPlugin, so internal nav links move to sections with offset compensation.
8. Navigation and layout boundaries
- The site has a top navigation bar, a mobile hamburger drawer, and persistent floating action buttons.
- The nav and CTA elements are separate from the content sections and serve as the main way users move between the one-page sections and trigger booking actions.
9. Content sections as functional modules
- The page is partitioned into distinct presentation modules:
- About
- Services
- Gallery
- Testimonials
- Booking
- Instagram/social proof
- Footer
- Each section has its own layout and animation behavior, but they all share the same global theme and motion system.
10. Interactive services subsystem
- The services area uses tilting cards and a detail modal.
- Service metadata is stored in a JavaScript object and used to populate package names, prices, durations, inclusions, and notes.
- User clicks open/close the modal; this is one of the few places where content is dynamically injected rather than hardcoded as static text.
11. Testimonials and social proof
- Testimonials are implemented as a carousel with GSAP-driven horizontal motion and auto-play behavior.
- The Instagram/social section is a static grid with hover effects, acting as visual proof rather than a data-connected feed.
12. Booking flow and external handoff
- The booking section is a 3-step form that does not submit to a backend.
- Instead, user input is converted into a pre-filled WhatsApp deep link, making WhatsApp the final transaction boundary for leads.
- This means the repo’s “booking system” is really a front-end lead capture funnel that hands off to an external messaging app.
13. Auxiliary experience layers
- Several cross-cutting enhancements sit above the content:
- custom cursor and particle trail
- ambient audio toggle via Web Audio API
- animated counters
- social icon interactions
- ESC-to-close modal behavior
- These are not separate subsystems in storage, but they are important architectural layers because they shape user interaction across the whole page.
14. Deployment and operational profile
- The site is designed to run by simply opening the HTML file, though some features like audio work best over HTTP/HTTPS due to browser policies.
- Because there is no build step, the operational boundary is minimal: serve one HTML file plus remote CDN assets.
15. Key architectural takeaway
- This repository is best understood as a highly choreographed static marketing experience: one document, one browser runtime, many client-side animation layers, and one external conversion path to WhatsApp.
Main entry points: mehndi-luxury-website.html HTML shell · README.md README
Components 19
Static site
Single-file browser experience with supporting docs.
- HTML shell · Main document that contains the full site structure, styles, and scripts.
mehndi-luxury-website.html - README · Repository documentation and usage notes.
README.md
Browser runtime
Client-side HTML, CSS, and JavaScript that drive the page.
- Theme CSS · Large stylesheet with custom-property theming, responsive layout, glassmorphism, and hover states.
mehndi-luxury-website.html - Navigation · Top nav, mobile drawer, floating actions, and smooth section jumping.
mehndi-luxury-website.html - Preloader · Initial loading screen with mandala draw animation and staged reveal.
mehndi-luxury-website.html - Hero scene · 3D canvas scene with particle/mandala visuals, parallax, and entrance animation.
mehndi-luxury-website.html - Motion engine · GSAP timelines, ScrollTrigger reveals, and scroll-to behavior across the page.
mehndi-luxury-website.html - Ambient FX · Custom cursor, particle trail, ambient audio toggle, counters, and similar cross-cutting interactions.
mehndi-luxury-website.html
Page sections
One-page presentation modules and conversion flow.
- Services · Card-based service showcase with tilt interaction and dynamic package data.
mehndi-luxury-website.html - Service modal · Modal dialog that injects service details and supports open/close flows.
mehndi-luxury-website.html - Gallery · Static image presentation with decorative hover treatment.
mehndi-luxury-website.html - Testimonials · Auto-playing horizontal testimonial slider driven by motion effects.
mehndi-luxury-website.html - Booking form · Three-step client-side form that gathers booking intent without backend submission.
mehndi-luxury-website.html - WhatsApp link · Pre-filled deep link used as the final conversion boundary.
mehndi-luxury-website.html - Instagram grid · Hoverable social gallery used as visual credibility content.
mehndi-luxury-website.html
CDN assets
Remote libraries and fonts loaded by the page.
- Three.js · Remote 3D rendering dependency for the hero scene.
- GSAP · Remote animation runtime used for reveals, timelines, and transitions.
- VanillaTilt · Remote tilt interaction library for interactive cards.
- Google Fonts · Remote typography assets that define the site’s visual tone.
Connections 24
- HTML shell → Theme CSS: defines · The single HTML file contains the full theme and layout styling.
- HTML shell → Navigation: contains · Navigation chrome lives inside the main page document.
- HTML shell → Preloader: contains · The page starts with a loading/entrance stage.
- HTML shell → Hero scene: contains · The hero section embeds the animated 3D scene.
- HTML shell → Motion engine: contains · Client-side script coordinates all scroll and entrance motion.
- HTML shell → Services: contains · The page includes a service showcase subsystem.
- HTML shell → Gallery: contains · The page includes a gallery presentation section.
- HTML shell → Testimonials: contains · The page includes a testimonial carousel module.
- HTML shell → Booking form: contains · The page includes the booking lead-capture flow.
- HTML shell → Instagram grid: contains · The page includes the social proof grid.
- HTML shell → Ambient FX: contains · Cross-cutting interaction layers are implemented in-page.
- Preloader → Motion engine: hands off to · The entrance sequence ends by triggering reveal animations.
- Motion engine → Hero scene: orchestrates · GSAP timelines coordinate the hero reveal and page motion.
- Motion engine → Services: reveal on scroll · Section visibility is animated as the user scrolls.
- Motion engine → Testimonials: drives · Motion logic powers the horizontal carousel behavior.
- Motion engine → Navigation: smooth scroll · Internal navigation uses animated scrolling with offsets.
- Services → Service modal: opens · Service cards populate and display the detail modal.
- Services → VanillaTilt: uses · Card tilt interaction comes from the external tilt library.
- Hero scene → Three.js: uses · The hero canvas is rendered with Three.js.
- Hero scene → GSAP: animates with · Entrance and transition effects use GSAP.
- Motion engine → GSAP: uses · ScrollTrigger and ScrollToPlugin power page motion.
- Booking form → WhatsApp link: redirects to · Submitted booking details are converted into a WhatsApp deep link.
- Theme CSS → Google Fonts: loads fonts · Typography is sourced from Google Fonts.
- README → HTML shell: documents · The README explains how to run and understand the single-page site.