AHMAD NAJHANPortfolio / 2026
AN

AHMAD NAJHAN

PORTFOLIO / 2026

DIPLOMA IN COMPUTER SCIENCEUiTM TAPAH

INITIALISING EXPERIENCE

0%

Ahmad Najhan bin Khairman / Digital Portfolio

01Completed

DEVCON 2024 HACKATHONTICKET SELLING SYSTEM

A compact web application built during DevCon 2024 to support event ticket ordering, summary calculation, and customer order storage under hackathon time pressure.

Project Result

3rd Place Winner

Tailwind CSSPHPMySQLHTMLCSSJavaScript

01

Scope control

Challenge

A 24-hour hackathon window required a focused scope and fast decisions.

  • Focused ticket order flow
  • Fast planning decisions
  • Achievable feature set

02

Interface hierarchy

Design

The interface emphasized event details, order clarity, and responsive structure.

  • Event details first
  • Order summary checkpoint
  • Responsive structure

03

End-to-end form flow

Development

The team connected front-end input with PHP processing and MySQL storage.

  • Form submission handling
  • Total price calculation
  • Customer order storage

04

Verified stack

Technology

Tailwind CSS, PHP, MySQL, HTML, CSS, and JavaScript formed the build stack.

  • Tailwind CSS interface
  • PHP processing logic
  • MySQL database interaction

05

Hackathon recognition

Result

The project earned 3rd Place Winner recognition at DevCon 2024.

  • 3rd Place Winner
  • Working project scope
  • Future roadmap identified

01

Project Opening

The Ticket Selling System was created as a hackathon web application for DevCon 2024.

The work focused on a clear event purchase flow: select ticket quantity, review event details, submit customer information, calculate total price, and store the order.

02

Project Context

The project was built in a competitive hackathon environment where clarity, working functionality, and fast implementation mattered.

The goal was to create a practical system rather than a broad concept presentation.

03

24-Hour Challenge

The limited timeframe required fast planning, clear task ownership, and direct implementation decisions.

The team prioritized a working end-to-end flow over unnecessary features.

04

Problem

Manual event ticket ordering can be difficult to track when quantity, customer details, and total pricing are handled separately.

The system needed to reduce friction by combining order input, calculated summary, and database storage in one flow.

05

Proposed Solution

The proposed solution was a lightweight ticket selling system with a focused interface and server-side order processing.

It used a web form, total price calculation, and MySQL-backed storage for customer orders.

06

Target User

The target user was an event attendee or customer placing a simple ticket order for an event.

The interface needed to communicate event details clearly and keep the order process direct.

07

System Flow

The user reviews event details, selects ticket quantity, checks the order summary, enters required customer information, and submits the form.

The system calculates the total price and stores the customer order in the database.

08

Design Approach

The design approach emphasized clarity, hierarchy, and responsive layout.

The order summary was treated as a decision checkpoint so users could understand the total before submission.

09

Tailwind Front-End Implementation

Tailwind CSS helped speed up interface construction during the hackathon.

Utility classes supported spacing, layout, and responsive adjustments without slowing down the build process.

10

PHP Form and Calculation Logic

PHP handled form submission and total price calculation logic.

The form flow connected user input with the server-side processing needed to prepare an order record.

11

MySQL Storage Role

MySQL stored customer order data from the submitted form.

The database role was focused on order persistence and interaction, not production-scale commerce infrastructure.

12

Core Features

Core features included ticket quantity selection, event details, order summary, form submission, total price calculation, customer order storage, and database interaction.

13

Tech Stack

The verified stack was Tailwind CSS, PHP, MySQL, HTML, CSS, and JavaScript.

Placeholder for the event information and ticket selection interface.

Placeholder for total price and selected quantity confirmation.

Placeholder for the customer form and database submission flow.

15Challenges
  • Keeping the project scope achievable within a 24-hour hackathon.
  • Balancing interface clarity with backend processing needs.
  • Ensuring the order summary and total price calculation worked reliably.
16Lessons Learned
  • A focused feature set is easier to complete under time pressure.
  • Clear system flow helps both users and developers understand the product quickly.
  • Database-backed projects require careful attention to form data structure.
17Team Collaboration
  • The hackathon format required team coordination and fast communication.
  • Responsibilities were aligned around interface work, logic, and database interaction.
19Future Roadmap
  • Improve validation feedback and error states.
  • Add clearer administrative order review screens.
  • Refine visual hierarchy and accessibility details.
  • Document database structure and setup instructions more thoroughly.
99Project Index

Review the full project system.