Firecloud Studio is a personal website and product-facing web presence hosted at firecloud.studio. The homepage has been redesigned into a landing page for Social Hazard, an Android multiplayer game, while the rest of the site continues to support personal and experimental pages that show range beyond a single product surface.
The repository is intended to function as both:
- a page for my game and future programs to come, its marketing and advertisement
The homepage is built to present my game Social Hazard. It is designed to give visitors a clear first impression of the game and provide direct access to its key materials, including the APK, trailer, screenshots, and repository links.
- landing section for Social Hazard branding and primary calls to action
- Download access for the Android APK
- Trailer section for embedded gameplay or promotional video
- Screenshots section for game visuals and presentation assets
- GitHub links for the Android app and website repository
- Feedback / report section for collecting user bug reports and general feedback
- Supporting pages including About, Contact, P2G, Time, and Random
- HTML5
- CSS3
- Vanilla JavaScript
- PHP for feedback/report handling
- Nginx on a Linux VPS
- HTTPS for secure delivery
The site is deployed on a Linux VPS and served through Nginx over HTTPS. Static files are served directly, while feedback.php handles report submissions server-side. The production setup is intended to keep feedback storage outside the public web root.
Firecloud/
|-- index.html
|-- about.html
|-- contact.html
|-- playground.html
|-- time.html
|-- random.html
|-- feedback.php
|-- css/
| |-- style.css
| `-- home.css
|-- js/
| |-- home.js
| |-- site.js
| |-- playground.js
| |-- random.js
| `-- time.js
`-- assets/
|-- social-hazard-trailer.mp4
|-- social-hazard-poster.jpg
|-- gameplay screenshots
`-- supporting images
The homepage includes a feedback and bug report form that submits to feedback.php. The server validates the request, packages the submitted fields into structured JSON lines, and writes them to a feedback log stored in a configured directory. In local development, the project can fall back to .feedback-store/; in production, storage is intended to live outside the site root. It is a temporary solution for now till I figure something else out.
some other stuff can be explored on your own.
- optimize media delivery, especially trailer compression and streaming readiness
- add richer metadata and social sharing previews
- improve screenshot curation and presentation polish
- expand analytics or lightweight engagement tracking
- refine content hierarchy between product promotion and portfolio identity
I originally built the site as a personal space, but the homepage did not clearly communicate a strong purpose or feel interesting enough. I redesigned it into a landing page for Social Hazard for it's marketing advertisement and also deployemnt so the site could function as both a product surface. That change made the website more useful, more focused, and more easier for visitors to understand immediately.
Designing the website to fit my vision and for it to look visually appealing at the very first glance. balancing style with readability integrating video, screenshots, APK delivery, and feedback in one clean page making the site look like a product page instead of a collection of tabs
presentation is just as imnportant if not even more important I would say than the app or build itself website gives your build a clear home design is not only about visuals, but matching the visuals along with clarity and purpose deployment and content structure matter a lot
responsive/mobile behavior add a better release/version history section improve the feedback/report system add analytics or download tracking polish media optimization and loading performance