Repository files navigation

A web-based platform for managing VR tournaments, games, and players.

The admin panel has been refactored to use a modular architecture:

renderer/├── js/│   ├── admin.js                  # Main entry point for admin panel│   ├── modules/│   │   ├── admin/│   │   │   ├── admin.js          # Core admin module│   │   │   ├── games.js          # Games management module│   │   │   └── ...               # Future modules (tournaments, players, etc.)

The admin panel now uses a modular approach:

1. Main Entry Point (admin.js):

   • Loads all required modules
   • Initializes the admin panel

2. Core Admin Module (modules/admin/admin.js):

   • Handles navigation
   • Manages dashboard
   • Provides shared utilities (modals, notifications)

3. Games Module (modules/admin/games.js):

   • Manages game CRUD operations
   • Handles game filtering and search
   • Manages game form

• Improved Maintainability: Each module has a single responsibility
• Better Organization: Code is organized by feature
• Easier Debugging: Issues can be isolated to specific modules
• Scalability: New features can be added as separate modules

• Add modules for tournaments, players, and settings
• Implement proper authentication
• Add real API integration
• Improve error handling and validation

• Tournament management
• Player registration
• Match scheduling and results tracking
• Cross-platform support (Windows, macOS, Linux)

• Node.js 14+ and npm

1. Clone this repository
2. Install dependencies:

npm install

3. Start the application:

npm start

To build the application for your current platform:

npm run build

Platform-specific builds:

# For Windowsnpm run build:win# For macOSnpm run build:mac# For Linuxnpm run build:linux

• main.js - Electron main process
• renderer/ - Frontend HTML, CSS, and JavaScript
• backend/ - Node.js backend services
  • database.js - Sequelize models and database setup
  • server.js - Express API server

This project is designed with cross-platform support in mind:

• Uses Electron for native desktop experience
• Full access to OS-level features
• Offline-first architecture with local database

• Will use Capacitor for wrapping the web application
• Responsive UI that adapts to mobile form factors
• Touch-friendly interface elements
• Native device API integration

• Core business logic
• Database schemas
• UI components (with responsive design)
• API integration

See the/mobile directory for more details on the mobile implementation strategy.

MIT