How christianglenogo/space-tourism works
Project type and purpose
• This is a purely frontend, multipage static website (“Space tourism”) built as a challenge solution.
• There is no backend server or database—content is served as static files (HTML/CSS/JS/JSON/assets).
File structure
• Top-level HTML files: index.html, destination.html, crew.html, technology.html
• css/ contains compiled CSS files. scss/ contains source SCSS modules.
• js/ contains vanilla-JS scripts that fetch data.json and swap content.
• data.json holds the dynamic page content for destinations, crew, and technology.
• assets/ holds images categorized by page.
README insights
• Built with HTML5, SCSS, Flexbox, Fetch API, vanilla JavaScript.
• Mobile-first responsive design.
• No server-side logic: Fetch API is used client-side to read data.json.
Main components and their interactions
a. Client (Browser)
• Renders HTML pages and applies CSS.
• Executes JavaScript to fetch data.json and manipulate the DOM.
b. Static Host / CDN
• Serves .html, .css, .js, .json, and asset files over HTTP/HTTPS.
c. SCSS Build Pipeline (Developer-side)
• Watches scss/* → compiles into css/*.
• (Optional) Could include autoprefixer, minifier before deployment.
d. data.json
• Acts as a mini “data store” fetched at runtime by JS.
e. Assets (images)
Architectural pattern & design principles
• Static website architecture (no backend).
• Separation of concerns: SCSS for style, JS for data binding, JSON for content.
• Mobile-first and responsive design (Flexbox, CSS variables).
• Unidirectional data flow: JS fetch → update DOM.
Elements to include for clarity
• Clear labels: “Browser (Client)”, “Static Host/CDN”, “SCSS Compiler”