Look ahead
I consider what a decision will mean after launch—not only what gets it shipped today.
Web developer · Portfolio
Hi, I'm Aiden. I build thoughtful digital experiences where useful code meets character, clarity, and a little delight.
Tip: the scene has a few things to discover.
01Selected work
A closer look at the systems I maintain, the journeys I improve, and the care I bring to shipping reliable work.

Maintaining a high-traffic B2B website and the conversion journeys behind it—from Gutenberg publishing to reliable lead flow and measurement.
Read case study

Converted a supplied design and concept HTML into a working Next.js site, with responsive interactions, forms, API endpoints, and GitHub-to-Vercel delivery.
Read case study

Built and maintained a WordPress content experience using Elementor, custom ACF structures, REST API delivery, and responsive iframe integration.
Read case study
A custom calling workflow built with CodeIgniter and Plivo, connecting application logic with programmable communications.
Read case study
An anonymized case study about organizing a complex client-document library into a clearer, more usable hierarchy.
Read case study
A practical approach to auditing an existing experience, challenging assumptions, and turning findings into implementable direction.
Read case study
A pixel-conscious conversion from WordPress to a structured Sanity CMS and Next.js experience deployed through Vercel.
Read case study
02About
I care about one question: how can I help? Sometimes the answer is a visible feature. Often it is the quieter work in the background that makes a team, system, or customer journey run better.
“Thinking outside the box” is a cliché for a reason. I like questioning defaults, finding the overlooked path, and then doing the careful work required to make a different idea practical.
Working style: INTJ. I use the label as shorthand, not a rulebook: I tend to think in systems, plan several moves ahead, work independently, and hold the details to a high standard.
I consider what a decision will mean after launch—not only what gets it shipped today.
I value background impact: fewer manual steps, clearer systems, and problems prevented before they become visible.
I challenge inherited assumptions when there is a clearer, simpler, or more durable route.
I use evidence, constraints, and the intended outcome to stay practical when the situation gets complicated.
My toolkit is always unfinished. Each project is a reason to understand another system more deeply.
03Skills & tools
Build
Connect
Ship
04 · Contact
Tell me what you're building, where it feels stuck, or why it matters. I'd love to hear about it.
Email Aidenaaduaban@gmail.com