mohammedadamdev/marriageinvitation

Purpose and delivery model

A static, browser-only wedding invitation template. It presents event content, supports in-browser editing, persists edits locally, and can be deployed as static files. Primary entry point: index.html; styling and responsive/print presentation: styles.css; client behavior: script.js.

Invitation presentation shell

index.html defines the public invitation page: hero content, ceremony/reception details, gallery placeholders, RSVP/contact affordances, navigation, and the editing UI. It references bundled media under assets/, including assets/videos/hero-video-BkP1eoiB.mp4 and assets/audio/wedding-background-music.mp3.

Configuration and content precedence

Default invitation data is maintained in config.js, with config-template.json serving as a portable configuration shape/template. On page initialization, client logic applies configured content to the DOM and uses browser-local persisted edits when present. This establishes a static-default versus per-browser customization boundary: local changes are not shared with other visitors or deployments.

Browser-side editing and persistence

script.js owns the administrative interaction flow: open/close the edit panel (including keyboard shortcut), collect edits, update rendered invitation fields, and save state to localStorage. It also supports configuration download for manual backup. No server API, authentication, or shared database exists; browser storage is the sole persistence runtime.

Sharing and QR workflow

qr-generator.html is a separate static entry point for producing a shareable QR-code experience around the hosted invitation URL. The invitation itself is intended to be distributed by link, messaging channels, or a printed QR code. External map/contact destinations are content-level browser links rather than backend integrations.

Static hosting and local serving

The site runs in any modern browser and needs only static-file hosting. vercel.json provides Vercel deployment configuration; DEPLOYMENT.md documents deployment concerns. For local preview, serve.py can serve the repository through Python, avoiding browser file-origin restrictions where applicable. Other hosting services are optional deployment targets, not application dependencies.

Asset and visual customization boundary

Visual system, responsiveness, and print behavior are centralized in styles.css; content structure remains in index.html. Media is repository-hosted under assets/images, assets/audio, and assets/videos. tools/optimize_images.py is an offline asset-preparation utility, separate from the page runtime.