How programmarself/space-travel-booking-platform- works
Project type and purpose
• This is a purely front-end, static web application (“Dubai to the Stars”) for booking hypothetical space trips.
• It consists of HTML, CSS, and JavaScript files served directly to the user’s browser—no server-side code or database.
File structure
• Top-level:
• index.html – the single entry point
• style.css – global styles (Flexbox, Grid)
• script.js – client-side logic (event handlers, DOM updates, countdown)
• .github/workflows – CI/CD pipelines (deploy to GitHub Pages, static checks)
• assets/ (implied in README) for images and fonts
• README.md documents features, tech stack, and file layout
README for additional insights
• Tech stack: HTML5, CSS3, JavaScript ES6, Google Fonts
• No back-end, database, or API endpoints
• CI/CD: GitHub Actions deploy via Jekyll on gh-pages (static.yml + jekyll-gh-pages.yml)
a. Main components
1. User’s Web Browser (Chrome/Firefox)
2. Static Host (GitHub Pages)
3. CDN for Fonts (Google Fonts)
4. Static Asset Store (images, fonts—either in same repo or CDN)
b. Relationships & interactions
• Browser requests index.html from GitHub Pages
• Browser downloads style.css and script.js from the same origin
• Browser fetches fonts from Google Fonts CDN
• User interacts with the UI; script.js updates the DOM, handles booking simulation
c. Architectural patterns & principles
• Single-page application (SPA) pattern (all UI delivered in one HTML)
• Separation of concerns:
– index.html defines structure
– style.css handles layout & styling
– script.js manages behavior & interactivity
• Static site deployment via GitHub Actions (CI/CD)
d. Key technologies & libraries
• HTML5, CSS3 (Flexbox, Grid)
• JavaScript ES6 (modules, DOM API)
• Google Fonts (Orbitron, Roboto)
• GitHub Actions (static.yml, jekyll-gh-pages.yml)