How valameet99/love- works
Project type and purpose
• This is a static, multi‐page front-end “Love Proposal” website. There is no backend or database layer: just HTML pages, CSS stylesheets, JavaScript behavior, and an external font service. Its purpose is to serve a simple, charming presentation across two pages (index.html and pg2.html).
File structure
• Top-level files:
• index.html – the landing page
• pg2.html – secondary page (the proposal continuation)
• style.css and pg2css.css – global and page-specific style rules
• script.js and pg2js.js – global and page-specific scripts
• A Google Fonts import (css2?family=…)
• No server config, build scripts, or back-end directories → purely client-side.
README
• Title “Love Proposal” with no further technical details. Confirms a very small, static presentation project.
a. Main components:
• Web Browser (client)
• Static assets:
– HTML pages (index.html, pg2.html)
– CSS files (style.css, pg2css.css)
– JS files (script.js, pg2js.js)
• External service: Google Fonts CDN
b. Relationships and interactions:
• User’s browser requests index.html → HTML parser loads linked CSS and JS → browser renders UI.
• Navigation from index.html to pg2.html triggers a new HTML download and its CSS/JS.
• Both pages fetch font files from Google Fonts.
c. Architectural patterns/design principles:
• Separation of concerns: HTML for structure, CSS for styling, JS for behavior.
• Multi-page model (not single-page app).
• CDN usage for third-party font assets.
d. Key technologies:
• HTML5
• CSS3 (external and page-specific styles)
• Vanilla JavaScript
• Google Fonts