CGPU Event Management

Technologies Used

• Next.js – Application framework
• Tailwind CSS – Utility-first styling
• shadcn/ui – Reusable and accessible UI components
• Gemini CLI – Fast-paced development and productivity

---

Methodology and Purpose

This project is a frontend-only UI implementation for a CGPU Event Management website. It serves as a starter template that visually represents how the platform would look and function once fully developed.

The UI showcases:

• Event listings
• Attendee views
• Overall layout and visual structure of the CGPU website

All UI elements are non-functional and do not connect to a backend. The initial plan included integrating Firebase for authentication and data handling, but due to time constraints, this integration was intentionally deferred.

The primary purpose of this project was to rapidly design and deliver a clean, scalable UI foundation that can be extended in future iterations.

---

Conclusion

The main takeaway from this submission is to showcase my ability to deliver a well-structured and visually consistent solution within a short time frame. This project demonstrates my understanding of modern frontend tools, component-driven design, and rapid development workflows.

Thank you.

---

Deployed

• Live Demo: cgpu-task

Local Development

Prerequisites

Ensure the following are installed on your system:

• Node.js (v18 or later recommended) 👉 Download from: https://nodejs.org
• npm or yarn (comes with Node.js)
• Git (optional, for cloning repositories)

Verify installation:

node -v
npm -v

---

Step 1: Clone the Repository

git clone https://github.com/buildnshare/cgpu-task
cd cgpu-event-management

---

Step 2: Install Dependencies

Using npm:

npm install

Or using yarn:

yarn install

---

Step 3: Run the Development Server

npm run dev

or

yarn dev

---

Step 4: Open in Browser

Once the server starts, open:

http://localhost:3000

Notes

• This project is frontend-only with no backend integration
• Firebase integration was planned but not implemented due to time constraints
• UI components are built using Tailwind CSS and shadcn/ui
• about and teams page will return 404 since it is not required

---