vivek-cogniwide/event-managment-system

Purpose and runtime

This is a Create React App single-page frontend for an event-management experience. It presents landing, event, upcoming-event, pricing, contact, dashboard, and login-modal views. The browser runtime is React; development runs via npm start on port 3000 and production builds are static assets. Entry assets are public/index.html, src/index.js, and public/manifest.json.

Application bootstrap and routing

src/index.js mounts the React application. Route selection is centralized in src/routes/Approute.jsx, which is the primary navigation/control boundary between URL-level pages and reusable UI. Page-level assemblies reside in src/pages/Home.jsx, src/pages/Events.jsx, and src/pages/Upcoming.jsx (with analogous pages for contacts, pricing, starts, and login modals).

Page and feature composition

Pages compose feature-oriented components rather than directly owning all presentation. The core homepage/marketing surface is src/components/landing page/Page.jsx; event browsing is src/components/event/Event.jsx; upcoming-event presentation is src/components/upevents/Upcomingevents.jsx. Styling is colocated with components, such as src/components/event/Event.css and src/components/upevents/Upcomingevents.css.

Shared shell and user-entry UI

Navigation and footer establish the shared visual shell through src/components/navbar/Nav.jsx and src/components/footer/Foot.jsx. Authentication interaction appears to be client-side modal UI in src/components/login-modal/LoginModal.jsx; no backend authentication implementation is present in the tree. Dashboard content is represented by src/components/dashboard/Dashboards.jsx, indicating a separate authenticated or management-oriented presentation area.

API boundary

src/api/Request.js is the repository’s explicit client/API boundary. The tree does not establish a server implementation or identify a concrete deployed endpoint, so event data, login behavior, and dashboard persistence should be treated as dependent on whatever request configuration this module supplies. API contract artifacts are present at the repository root, including api.yaml, open-api.yaml, and swagger-api.yaml; these likely document or catalog external services rather than execute in the frontend runtime.

Delivery and infrastructure metadata

The application is deployed as a static CRA build, with no infrastructure-as-code or backend runtime shown. GitHub Actions workflows provide CI/security automation in .github/workflows/main_web-team-01.yml, .github/workflows/static.yml, and .github/workflows/semgrep.yml. Multiple catalog/component YAML files—such as catalog-info.yaml, component-info.yaml, and cicd-component.yaml—indicate service-catalog and CI/CD metadata integration.

Main flow

A browser loads public/index.html, executes src/index.js, and delegates navigation to src/routes/Approute.jsx. Routes render page assemblies from src/pages, which compose shared navigation/footer plus feature components. Components that need remote data or mutations should cross the single frontend service boundary at src/api/Request.js; the resulting state is rendered locally by the corresponding event, dashboard, or modal component.