How sameer-mohapatra/nexus works
1. This repository is a hybrid event-management site: a mostly static public website for promoting events, plus a small PHP-backed administrative area for managing events and attendees.
2. The public-facing layer lives at the repository root and under event_pages/. It is composed of HTML landing pages, event-specific microsites, shared CSS/JS, and media assets. The main entry point appears to be index.html.
3. The frontend is assembled from static assets in css/, js/, img/, and lib/. The lib/ folder contains third-party browser libraries such as Bootstrap, jQuery, Font Awesome, Owl Carousel, WOW/animate, Venobox, easing, and Superfish, which suggests a template-driven marketing site with animated sections, carousels, galleries, and responsive navigation.
4. Event microsites are separated by event under event_pages/:
- hackathon/
- react_native_bootcamp/
- xbase/
Each event folder contains its own page markup, styling, speaker/detail pages, and in some cases an rsvp.php endpoint. This indicates a per-event content boundary rather than one monolithic event page.
5. The RSVP flow is handled close to each event page. The presence of rsvp.php beside individual event pages suggests form submissions are processed server-side per event, likely capturing registrations or interest signups from the public microsites.
6. The backend/admin subsystem is under backend/. It includes login/signup entry points (login.php, sign_up.php, and variants with underscores) and a dashboard area (backend/dashboard/). This is the operational control plane for managing events rather than a public-facing user area.
7. The dashboard area is split into functional screens:
- index.php for the main admin view
- create_event.php for event creation
- attendee.php and event_attendees.php for attendee management
- script.js and style.css for dashboard-specific behavior and styling
This layout implies CRUD-style workflows around events and registrations.
8. Shared backend utilities live in backend/partials/. _dbconnect.php establishes the database connection, while _functions.php likely hosts reusable server-side helpers. This creates a clear boundary between page-level PHP controllers and shared infrastructure code.
9. The main data flow is: public forms or RSVP actions post into PHP endpoints; those endpoints use the shared database connection and helper functions; the dashboard reads and manages the stored event/attendee records. The frontend and backend are therefore coupled through server-rendered PHP and shared storage, not through a separate API layer.
10. There is also a small contactform/ area with contactform.js, suggesting a client-side contact form submission path that is separate from the event RSVP flow.
11. Media is heavily organized by purpose: global assets under img/, and event-specific images inside each event folder. This reinforces the repo’s split between reusable site branding and isolated event microsites.
12. Overall, the architecture is a classic server-rendered PHP application with a static marketing frontend, per-event content modules, and a protected admin dashboard backed by a database. The main boundaries to show in a diagram are:
- public site vs admin backend
- shared assets vs event-specific assets
- RSVP/contact submission paths vs dashboard management paths
- PHP pages/controllers vs shared DB utilities
Main entry points: index.html Home page · _dbconnect.php DB connect · rsvp.php RN RSVP · _functions.php Helpers
Components 22
Public site
Static marketing pages and shared frontend assets.
- Home page · Main public landing page for the site.
index.html - Site styles · Shared styling for the public-facing site.
css/style.css - Site scripts · Shared client-side behavior for the main site.
js/main.js - Contact form · Client-side contact form handling.
contactform/contactform.js
Event microsites
Per-event pages, styles, media, and RSVP endpoints.
- Hackathon page · Hackathon microsite content and layout.
event_pages/hackathon/hackathon.html - Hackathon css · Styling for the hackathon microsite.
event_pages/hackathon/hackathon.css - Hackathon RSVP · Server-side RSVP handler for the hackathon event.
event_pages/hackathon/rsvp.php - RN bootcamp · React Native bootcamp microsite content.
event_pages/react_native_bootcamp/react_native.html - RN styles · Styling for the React Native bootcamp microsite.
event_pages/react_native_bootcamp/react_native.css - RN RSVP · Server-side RSVP handler for the React Native bootcamp.
event_pages/react_native_bootcamp/rsvp.php - Xbase page · Xbase event microsite content.
event_pages/xbase/event_page.html
Admin backend
PHP control plane for authentication, dashboard workflows, and persistence.
- Login · Admin authentication entry point.
backend/login.php - Sign up · Admin account registration entry point.
backend/sign_up.php - Dashboard · Primary admin dashboard view.
backend/dashboard/index.php - Create event · Dashboard screen for creating events.
backend/dashboard/create_event.php - Attendees · Dashboard screen for attendee management.
backend/dashboard/attendee.php - DB connect · Database connection bootstrap.
backend/partials/_dbconnect.php - Helpers · Reusable backend helper functions.
backend/partials/_functions.php
Shared assets
Reusable libraries and global media used across the site.
- Bootstrap · Responsive layout and component library.
lib/bootstrap/css/bootstrap.css - jQuery · Core client-side DOM and event library.
lib/jquery - Owl Carousel · Carousel/slider component library.
lib/owlcarousel/owl.carousel.js - Media assets · Shared images for events, galleries, venues, speakers, and supporters.
img
Connections 25
- Home page → Site styles: uses · Main page loads shared site styling.
- Home page → Site scripts: uses · Main page uses shared site behavior.
- Home page → Bootstrap: depends on · Public site uses Bootstrap for layout.
- Home page → jQuery: depends on · Public site uses jQuery for interactions.
- Home page → Owl Carousel: depends on · Public site uses carousel components.
- Site scripts → Contact form: invokes · Shared site scripting coordinates contact form behavior.
- Hackathon page → Hackathon css: uses · Hackathon page loads its event-specific styles.
- Hackathon page → Hackathon RSVP: posts to · Event registration flow submits to the RSVP handler.
- Hackathon page → Media assets: uses · Hackathon page consumes shared and event media.
- RN bootcamp → RN styles: uses · Bootcamp page loads its event-specific styles.
- RN bootcamp → RN RSVP: posts to · Bootcamp registration flow submits to the RSVP handler.
- RN bootcamp → Media assets: uses · Bootcamp page consumes shared and event media.
- Xbase page → Media assets: uses · Xbase page uses shared media assets.
- Login → DB connect: uses · Authentication screens share database setup.
- Sign up → DB connect: uses · Signup flow uses database setup.
- Dashboard → DB connect: uses · Dashboard reads and writes through the shared database connection.
- Create event → Helpers: uses · Event creation relies on backend helpers.
- Attendees → Helpers: uses · Attendee management relies on backend helpers.
- Dashboard → Create event: navigates to · Dashboard links to event creation.
- Dashboard → Attendees: navigates to · Dashboard links to attendee management.
- Hackathon RSVP → DB connect: uses · RSVP submissions persist through the database connection.
- Hackathon RSVP → Helpers: uses · RSVP processing shares backend helper logic.
- RN RSVP → DB connect: uses · RSVP submissions persist through the database connection.
- RN RSVP → Helpers: uses · RSVP processing shares backend helper logic.
- RN RSVP → Attendees: feeds · Captured registrations are managed in the admin dashboard.