How mehdibp/heliya works
Project type and purpose
• From the README (“Heliya: Designing a website for the Heliya Astronomy Association”) and the file list (index.html, main.css, main.js plus a .json/.xlsx of sky events), this is a simple static, data‐driven front-end website. Its goal is to display astronomical events in the browser, likely by loading the Sky Events JSON.
File structure
• Top-level assets:
• index.html – the entry point/view template
• main.css – styling
• main.js – client-side logic to fetch & render data
• Sky Events.json / Sky Events.xlsx – the raw data feed
• .gitignore – version control setup
• No server-side code, no build scripts or backend folder: implies deployment as a static site (e.g. GitHub Pages, Netlify, S3 + CloudFront).
README for additional insights
• No further architectural hints; it’s purely a static site for an astronomy association. The Excel file suggests a step where you convert to JSON (either manually or via a simple script/build step), but that process is outside the runtime architecture.
Detail
• Runtime environment (browser) vs. build-time tools (Excel conversion)
• How each file contributes to the overall user experience