2023

AdComSys

Built the official full-stack digital platform for an international technical conference using Next.js and TypeScript. Developed server-less API architecture to interface with a MongoDB database for dynamic schedule and paper management. Integrated a Dialogflow-powered AI support bot to handle real-time attendee queries, wrapped in a modular, responsive UI system styled with SCSS.

View Live Demo Source Code

Scroll to explore

Project Highlights

Key metrics and achievements that define this project

Technologies

Year Released

Developer

Role

Interested in This Project?

Explore the live demo, check the code, or reach out to discuss it

View Live Demo View Source Code

Contact Me

Full Case Study

See the delivery timeline, architecture notes, and decision tradeoffs.

A conference platform that had to function as more than a brochure site: schedules, accepted papers, submissions, attendee support, and dynamic data all had to live in one coherent product.

View full case study

The Challenge

The Solution

Key Learnings

The Challenge

Creating a conference management system that handles dynamic schedules, paper submissions, and attendee management in real-time. The platform needed to support multiple concurrent sessions and provide instant updates to attendees.

The Solution

Built a serverless API architecture using Next.js API routes with MongoDB for flexible data storage. Implemented real-time updates using polling and optimistic UI updates. Created a comprehensive admin dashboard for conference organizers.

Key Learnings

Learned to architect serverless applications at scale, implemented advanced TypeScript patterns for type safety, and mastered creating intuitive admin interfaces for non-technical users.

Key Decisions

Engineering tradeoffs that shaped the build

A compact snapshot of the technical and product decisions that had the biggest impact on delivery.

See technical decisions Discuss a similar project

Build around dynamic conference data instead of a static event site

Schedules, accepted papers, and submission-related information shift during the lifecycle of a conference and cannot be managed comfortably as hand-edited static content alone.

Decision

I treated the conference as an application problem, not just a content problem, and used API routes plus Mongo-backed data handling for the dynamic pieces.

Keep the site mostly staticUse embedded third-party conference toolingOwn the data-backed experience in the Next.js app

Impact: The product could represent real conference operations instead of only the public marketing layer.

Tradeoff: This added backend responsibility to a site category that many teams would keep mostly static.

Keep conference schedules and paper views as first-class interfaces

Attendees and authors need direct access to schedules, accepted papers, and submission information without digging through generic pages.

Decision

I gave schedules, accepted papers, and submissions dedicated paths and supporting data structures.

Bury conference data inside long-form pagesLink out to external documentsCreate dedicated data-driven views in the platform

Impact: The conference information architecture feels intentional rather than improvised.

Tradeoff: More dedicated views means more upkeep for organizers and developers.

Include support and organizer telemetry in the app layer

A conference product serves both attendees and organizers, so information delivery alone is not enough.

Decision

I integrated Dialogflow support and lightweight count-oriented APIs alongside the public conference experience.

Leave support fully manualAdd isolated helper scripts outside the appExpose support and count-oriented tooling through the application

Impact: The app reflects real event operations instead of stopping at presentation.

Tradeoff: Operational helpers increase scope, but they make the platform more useful during the event lifecycle.

Open Full Image

Visual Showcase

A closer look at the shipped interface

This screen captures the production-facing design language, layout rhythm, and overall polish of the experience.

AssetProject Poster

Open Live Demo

Tech Stack

Built With

Scroll to explore technologies →

Next.js

TypeScript

MongoDB

Dialogflow

SCSS

Next Project

Continue Exploring

2025

Lake Como Style

Freelance Project

Architected a high-performance, cinematic event booking platform using the bleeding-edge Next.js 16 and React 19 stack. Engineered a scalable content management system with Sanity to handle 11+ custom schema types, ensuring seamless client updates. Implemented complex UI animations using Framer Motion and Lenis for smooth scrolling, while building a robust transactional email service with Nodemailer for automated booking confirmations.

View Project