The admin side of an events and ticketing platform: event review, ticket sales, organizers and permissions, in Arabic and English.
Frontend developer · admin dashboard
Blurred on purpose: client work under NDA
Sales by ticket tier
Each event’s status
Cover and gallery
Send the event back
1440 px
39010241440
Ban button
Switches grouped by area
Blurred on purpose: client work under NDA
Sales by ticket tier
01 / 07
Overview
What it is
Gudea is an events and ticketing platform in Iraq, and this is the dashboard its team runs it from: they review and publish the events organizers submit, follow ticket sales, manage organizer accounts and set who can do what. I wrote most of its frontend, working from the design team’s screens and the backend team’s API, Arabic first with English and dark mode.
Each event’s status
02 / 07
What it does
Moderation queue
The moderation queue: each event’s status, status filters and search, featured stars, and Take action enabled only while an event is pending.
How I built it
A shared TanStack Table with server paging, loading skeletons and resizable columns
Cover and gallery
03 / 07
What it does
Event review
Reviewing a pending event: its cover and gallery, title, description, ticket tiers and prices, and the organizer.
Send the event back
04 / 07
What it does
Approve, reject, or send it back
The decision: approve, reject, or send the event back to its organizer. Reject and send back need a note; here the admin asks for the trainers' names.
1440 px
39010241440
05 / 07
What it does
A sales page for every event
On a phone: one event’s sales, with the sidebar folded into a menu button.
How I built it
Arabic-first RTL with vue-i18n, Iraqi date and number formats, and IQD
Drag the edge of the screen and see it switch.
Ban button
06 / 07
What it does
Organizer profiles
An organizer’s profile: contact details, account status with a Ban button, organization details, and their sales.
Switches grouped by area
07 / 07
What it does
Staff access
Role permissions in English: switches grouped by area, with a count of what is enabled in each group.
How I built it
CASL rules from the user’s permissions guard routes, the sidebar and every button