What “server manager” actually meant
Not a title on a slide — day-to-day cPanel/WHM care, migrations, SSL, mail deliverability, and the unglamorous checks that stop a brand site from dying mid-campaign.
Dubai creative studio · 2021 — 2024
At KING.Graphics I lived in the gap between beautiful Figma files and servers that have to survive real traffic. Designers move fast; hosting and WordPress have to keep up without silent failures on launch morning.
My role WordPress developer / server manager — design-to-production, multi-site hosting, mail & SSL, campaign microsites.
Agency velocity vs fragile estates: multi-cPanel stacks, mail that lands in spam, SSL surprises, and campaign microsites that must go live on a calendar — not when “infra feels ready.”
I converted Figma into production WordPress, managed cPanel/WHM for client and company projects, tuned databases, fixed deliverability, and stood up launches like worldcup.king.graphics with the boring ops work done first.
A studio site and satellite launches that stayed online — with engineering account managers and designers could trust during crunch weeks.
Not a title on a slide — day-to-day cPanel/WHM care, migrations, SSL, mail deliverability, and the unglamorous checks that stop a brand site from dying mid-campaign.
Figma→WordPress for KING and client work meant matching the craft, not dumping everything into a page builder and hoping. Campaign microsites had to look intentional and still be recoverable when traffic spiked.
Pixel-faithful builds without painting the team into a dead-end stack.
Multi-site cPanel/WHM, mail, SSL, and Linux hygiene for client estates.
Timed launches under the KING umbrella — fast, branded, recoverable.
Inner pages captured from the live site — click a thumb to open the gallery, or open the real URL.