GameOverNight is a serious solo project of mine — an HTML5 game portal for browser-based play.
From the beginning, I wanted to develop it in a clean, organized, and scalable way.
🧱 gon-workspace: One folder to rule them all
All source code, tools, and content related to GameOverNight are kept inside a single root folder called: gon-workspace. By keeping everything in one place, it's easier to manage, back up, and scale as the project grows.
📁 Current Folder Structure
gon-workspace/
├── client/ # Next.js project – main UI at gameovernight.com
├── api/ # Express.js backend – runs at api.gameovernight.com
├── posts/ # Static HTML posts
└── tools/ # CLI tools for zipping builds, backing up automatically
🔍 What each folder does
client/: The public-facing site built with Next.js. This is where games are listed and played.
api/: The backend written in Express.js. It handles routes, storage and analytics.
posts/: This folder stores draft HTML content before it's entered into the MySQL database. Since I currently manage my site directly via cPanel and phpMyAdmin — without a traditional admin page — I use this folder as a personal staging area. Later on, I might replace this workflow with a real admin interface or CMS.
tools/: A set of CLI scripts I wrote to automate zipping the web source code for deployment and backing up key files after each build.
💡 Why this matters
Organizing everything under a single workspace allows me to:
- Develop faster without switching between messy folders
- Automate builds and backups more easily
- Prepare for future scaling or open-sourcing
I'm sharing this structure in case it's useful to anyone building a similar project — whether it's for games, a dev tool, or a multi-part app.
Let me know what your structure looks like!
Top comments (0)