How prathik-ds/nexus works
1. Overall shape
FusionVerse is a mostly server-rendered PHP/MySQL monolith for a college fest platform. The core architecture is page-driven: browser requests land on PHP entrypoints, those pages query/update MySQL, and then render HTML with shared header/footer templates.
2. Main user-facing surfaces
The application is split into distinct role-based pages: index.php, login.php, register.php, dashboard.php, events.php, leaderboard.php, plus admin/coordinator pages such as admin.php, coordinator.php, and their related management screens. This makes the repo easy to diagram as a set of functional entrypoints over one shared backend.
3. Shared presentation layer
includes/header.php and includes/footer.php provide reusable shell markup, while assets/css/*.css, assets/js/*.js, and images under assets/img and images/ contain the site’s neon/sci-fi UI. The presence of bundled files like assets/index-*.css and assets/index-*.js suggests at least one prebuilt frontend asset output layered on top of vanilla PHP pages.
4. Authentication and session boundary
register.php, login.php, and logout.php form the auth boundary. The README indicates registration captures student identity details and generates a unique SYN-XXXX ID, which then becomes the primary identity used across the dashboard, registrations, and results pages. After login, PHP sessions gate access to private user/admin/coordinator screens.
5. User workspace flow
dashboard.php is the user’s main post-login hub. It aggregates profile data, registration history, event status, and notices, so its data flow is read-heavy: it pulls from the database to assemble a personalized view rather than acting as a simple static page.
6. Event discovery and registration pipeline
events.php is the browsing layer, while register_event.php, unregister_event.php, ajax_unregister.php, and team_actions.php handle mutations. The README describes duplicate-prevention and slot enforcement, so the architecture centers on transactional checks in PHP before writing registration state to MySQL.
7. Admin control subsystem
admin.php and the admin subpages (admin_users.php, admin_events.php, admin_explore_events.php, admin_leaderboard.php) are the operational back office. This area owns cross-cutting actions like user management, event oversight, score entry, and public announcements, and it feeds both the dashboard notice board and the leaderboard.
8. Coordinator workflow
coordinator.php, coordinator_actions.php, and coordinator_actions_ajax.php represent a separate operational role from admin. This likely handles event-day workflows such as participant status updates, results submission, or coordination tasks, with an AJAX endpoint for faster UI updates without full page reloads.
9. Results, ranking, and certificates
leaderboard.php, vortex_results.php, and certificate.php form the recognition/output path. These pages turn stored scores and statuses into public rankings and printable artifacts, so they are downstream consumers of the admin/coordinator data-entry flows.
10. Database as the system backbone
config/db.php is the single database connection boundary, and fusionverse_database.sql is the schema seed. The rest of the application depends on this relational store for users, events, registrations, scores, notices, and team/participant mappings.
11. Migration and maintenance scripts
install.php, migrate_teams.php, and scratch/update_db.php indicate that schema setup and data migration are part of the repo’s lifecycle, not separate infrastructure. export_data.php also shows an administrative data-extraction path, useful for reporting or backups.
12. Deployment/runtime assumptions
The repo is built to run on a classic PHP web server with MySQL, aided by .htaccess for routing or access rules. START_NETWORK_SERVER.bat and web.zip suggest local/network deployment convenience, but the architecture itself remains a traditional server-rendered PHP app rather than a SPA or microservice system.
Main entry points: db.php DB Config · dashboard.php Dashboard · admin.php Admin · header.php Header
Components 34
Public entrypoints
Browser-facing starting points and session boundary pages.
User workspace
Logged-in student flows for browsing, registration, and profile views.
- Dashboard · Personalized post-login overview of profile, registrations, and notices.
dashboard.php - Events · Lists events and entry points for registration.
events.php - Join Event · Registers a user or team for an event with validation.
register_event.php - Leave Event · Removes a registration from an event.
unregister_event.php - Ajax Leave · Asynchronous unregister action for the UI.
ajax_unregister.php - Team Actions · Handles team formation and team-related operations.
team_actions.php - Leaderboard · Public ranking view built from stored scores.
leaderboard.php - Certificate · Renders printable recognition artifacts.
certificate.php - Results · Shows event outcome and result data.
vortex_results.php
Admin console
Operational back office for users, events, scores, and announcements.
- Admin · Main operational console for site administration.
admin.php - Users · Manages user accounts and identity records.
admin_users.php - Events Admin · Creates and manages events and related settings.
admin_events.php - Explore Events · Admin view for inspecting event data and structure.
admin_explore_events.php - Admin Rank · Controls leaderboard data and ranking presentation.
admin_leaderboard.php
Coordinator tools
Role-specific event-day workflows and fast update endpoints.
- Coordinator · Coordinator workspace for event operations.
coordinator.php - Coord Actions · Processes coordinator updates and result submissions.
coordinator_actions.php - Coord Ajax · Fast asynchronous coordinator actions.
coordinator_actions_ajax.php
Shared app layer
Reusable templates, client assets, and deployment/runtime glue.
- Header · Shared page shell and navigation markup.
includes/header.php - Footer · Shared closing markup and page footer.
includes/footer.php - Styles · Primary site styling and themed UI assets.
assets/css/styles.css - Splash CSS · Splash screen styling.
assets/css/splash.css - Site JS · Shared client-side behavior for the PHP pages.
assets/js/script.js - Splash JS · Behavior for the splash/landing experience.
assets/js/splash.js - Built CSS · Prebuilt frontend stylesheet output.
assets/index-S1tavsFE.css - Built JS · Prebuilt frontend script output.
assets/index-tiyn2ZUY.js
Data layer
Database schema, connection boundary, and maintenance scripts.
- DB Config · Single connection boundary to MySQL.
config/db.php - Schema · Database schema and seed data.
fusionverse_database.sql - Install · Initial application and schema setup.
install.php - Migrate Teams · Converts or repairs team data shape.
migrate_teams.php - Update DB · Ad hoc database update utility.
scratch/update_db.php
Connections 48
- Home → Login: sign in · Users move from the landing page to authentication.
- Home → Register: sign up · New users can create accounts from the public entrypoint.
- Login → DB Config: verify · Credentials are checked through the database connection.
- Register → DB Config: create user · Registration writes identity records to MySQL.
- Login → Dashboard: session start · Successful login leads into the user workspace.
- Logout → Home: return · Logout sends users back to the public site.
- Dashboard → Events: browse · The dashboard links into event discovery.
- Dashboard → Leaderboard: view ranks · Users can inspect rankings from their workspace.
- Dashboard → Certificate: view cert · Certificates are reachable from the user hub.
- Events → Join Event: register · Browsing leads into event registration mutations.
- Events → Leave Event: withdraw · Users can unregister from an event.
- Events → Team Actions: team flow · Team-related event actions are delegated to team endpoints.
- Leave Event → Ajax Leave: async · The UI can use an AJAX path for unregistering.
- Join Event → DB Config: write reg · Registration state is stored in the database.
- Leave Event → DB Config: remove reg · Unregistration updates the relational store.
- Team Actions → DB Config: team data · Team membership and mappings are persisted in MySQL.
- Admin → Users: manage users · Admin console branches into user management.
- Admin → Events Admin: manage events · Admin console branches into event management.
- Admin → Explore Events: inspect · Admins can inspect event structures and records.
- Admin → Admin Rank: rank control · Admin console feeds leaderboard management.
- Users → DB Config: user ops · User administration reads and writes MySQL data.
- Events Admin → DB Config: event ops · Event administration persists event configuration.
- Admin Rank → DB Config: scores · Ranking data comes from the database.
- Coordinator → Coord Actions: workflow · Coordinator pages delegate core operations to action handlers.
- Coordinator → Coord Ajax: fast updates · Coordinator UI can use AJAX for quick state changes.
- Coord Actions → DB Config: update status · Coordinator actions modify operational records.
- Coord Ajax → DB Config: async update · Asynchronous coordinator actions persist through MySQL.
- Admin Rank → Leaderboard: publish · Admin-managed ranking data flows to the public leaderboard.
- Events Admin → Events: source data · Public event listings are driven by admin-managed records.
- Admin → Dashboard: notices · Administrative announcements and updates surface to users.
- Leaderboard → DB Config: read ranks · Leaderboard pages read ranking data from the database.
- Results → DB Config: read results · Results pages consume stored score and status data.
- Certificate → DB Config: verify award · Certificate generation depends on persisted results or identity data.
- Header → Styles: shell style · Shared templates pull in the main stylesheet.
- Header → Site JS: shared ui · Common shell markup is paired with shared client behavior.
- Footer → Site JS: page script · Footer includes or closes out shared script loading.
- Home → Header: layout · Public pages use the shared page shell.
- Dashboard → Header: layout · Logged-in views render through shared templates.
- Admin → Header: layout · Admin pages share the common shell.
- Coordinator → Header: layout · Coordinator pages use the shared shell.
- Home → Footer: layout · Public pages share a common footer.
- Dashboard → Footer: layout · Logged-in views share the footer template.
- Install → Schema: seed · Installer initializes the database schema.
- Migrate Teams → Schema: migrate · Team migration scripts adapt the schema or data.
- Update DB → Schema: repair · Maintenance updates are applied against the database structure.
- DB Config → Schema: connects to · All runtime data access flows through the database schema.
- Install → DB Config: bootstrap · Setup scripts rely on the DB connection boundary.
- Migrate Teams → DB Config: transform · Migration scripts use the same database connection.