Now let me save the logo image and start building. I'll begin with the design system, then build the full site.

Now let me generate event images and set up the complete site:

Now let me update the design system (globals.css) with a deep navy blue theme inspired by the GTEC logo:

Now let me update the layout and start building components. I'll do several in parallel:

Now let me update the globals.css to add the new font families and update the tailwind theme:

Now let me build all the core components. First, the shared data file and then the components:

Now let me build the homepage components:

Now let me build the homepage and the secondary pages:

Let me also add the font-heading utility class support to the globals.css:

Good, the font-heading is already in the theme. Now let me add a @utility for the font-heading class so it works in Tailwind v4:

Now let me verify the contact page has the proper metadata since it's a client component. Let me split it properly:

I need to split the contact page into a server component for metadata and a client component for the form. Let me refactor:

I'll split the contact page so metadata can be exported from a server component:

The comprehensive GTEC Events Portal website is now complete. Here's what was built:

Homepage features a full-screen hero section with the GTEC logo, a live countdown timer to the next major event (Symphony 2026), campus statistics, featured upcoming events in card format, an event categories section with 5 categories (Technical, Cultural, Sports, Workshops, Seminars), an about-the-college preview with highlights, and a call-to-action section.

Events Page (/events) provides a filterable and searchable event listing with category filter tabs, an upcoming/past toggle, and responsive grid cards showing event images, dates, venues, and pricing.

Event Detail Pages (/events/[id]) include a hero banner, full event description, rules/guidelines, coordinator contacts, a sidebar with event details and prize info, related events, and an inline registration form with fields for name, email, phone, college, department, year, and team name.

About Page (/about) showcases the college's mission and vision, a timeline of milestones, stats, departments listing, and a CTA to explore events.

Contact Page (/contact) includes a contact form, department-wise contact information, an embedded Google Maps location, and office details -- all using the GTEC branding with the deep navy blue color scheme derived from the college logo.

Let me explore the current codebase thoroughly and then plan the implementation.

Now let me also read the remaining components:

Now I have a thorough understanding of the entire codebase. Let me also check the registration form:

Now I have complete understanding of the codebase. Let me check available integrations for the database:

No database is connected. Given this constraint, I need to decide on the data storage approach. For a college events website admin panel, I'll use localStorage-based state management with React Context, which lets the admin persist changes client-side without requiring a database integration. This keeps things self-contained and functional. Let me now write the plan.