Pakenham Hospital -- Appointment booking portal — patient and doctor sides

A semester-long group builds a fictional Victorian hospital. Patients can browse doctors by specialisation, open a profile, pick an available time slot, and register an account; doctors sign in to a separate dashboard to see their booking schedule and update appointment status.

I owned the frontend. That meant the visual language — a soft mint and deep-green palette, generous spacing, forms with icon-prefixed fields so each input reads at a glance — and then every page that language applied to: the landing page, the doctors grid, the individual doctor profile with its slot picker, patient registration and profile, the doctor login, and the doctor dashboard. All of it was hand-written HTML and CSS. This was also the project where I learned Tailwind CSS, picking it up alongside the build and carrying it into the work I've done since. I wired the frontend to the team's API, added the Help assistant — a browser-side chat widget for quick patient questions — and once the build came together, I moved onto testing, walking the booking and registration paths and reporting what broke.

What I did

• Designed the interface and component language across eight pages

• Built it in hand-written HTML, CSS and JavaScript — no framework, no UI kit

• Built the booking flow: directory → doctor profile → slot selection → confirmation

• Connected the frontend to the team's REST API with token-based sessions

• Added the in-page AI help assistant

• Learned Tailwind CSS during this project

• Tested the patient and doctor paths before submission

Tags: HTML · CSS · JavaScript · Tailwind CSS · UI design · REST API integration · Testing