How d1sh4nt121/solarverse works
Project type and purpose
• From the file tree and README, SolarVerse is a small, client-side web application (a static “Solar System” viewer) with no separate backend or database.
• Its primary function is to serve an interactive or visual representation of planets (assets under public/) via index.html, main.js, and style.css.
File structure
• Top-level files:
– index.html: entry point
– package.json / package-lock.json: Node-based build or dependency management (likely for bundling, linting, or local server)
– README.md: minimal project title
• Directories:
– public/: static assets (images or data for “csilla”, “earth”, “venus”, “volcanic”)
– src/: application source (main.js, style.css)
• No backend folder or API, no database connectors, no test or CI configs—this is purely front end.
README for additional insights
• README only contains “# SolarVerse”—no explicit architectural notes or external integrations.
• Assume a standard npm-based local dev server → build → deploy to static hosting (GitHub Pages / S3 / Netlify).