Dimitris Poupalos photographs buildings and machines the way most photographers photograph people — with intimacy, with patience, and with an eye for the human presence inside apparently inhuman subjects. His architectural and industrial work has earned recognition at the highest level of the craft: a Hasselblad Masters Award nomination, given by the company that has produced the cameras behind some of the most significant photographs of the twentieth century, to the photographers they consider among the best working in the world.

A photographer at this level does not need a website to explain who he is. He needs a website that does not get in the way of showing what he does. When dpoupalos.com needed to be rebuilt — migrated from a highly bespoke legacy system to a modern CMS that could be maintained and expanded without ongoing developer dependency — the brief was simultaneously simple and extremely demanding: reproduce everything exactly. Not approximately. Exactly.

The Challenge: When Perfection Was Already Achieved

The most technically challenging web migrations are not the ones that need to be improved. They are the ones that need to be preserved. When a client has already paid a significant price — in time, in cost, in creative iteration — to achieve a specific digital aesthetic, and that aesthetic is working, the brief is not "make it better." It is "make it the same, on a better foundation." This is a more demanding brief than it sounds.

The original dpoupalos.com was built on a custom, bespoke platform — tailored specifically to the photographer's vision, with interaction sequences and animation timings that had been refined until they felt exactly right. The way images entered the frame. The speed and easing of transitions. The precise relationship between whitespace and image edge. The typographic rhythm of the portfolio navigation. Every one of these details had been arrived at deliberately, and every one of them needed to survive the migration intact.

Alongside the animation challenge was a more fundamental one: image performance. Dimitris Poupalos' photographs are large. Not in the casual sense — in the literal photographic sense. Files shot on medium format cameras at maximum resolution, processed to retain every tonal detail of a concrete surface or the texture of industrial steel, can be enormous. Serving these images in a way that maintains the visual fidelity the photographer requires while loading in a time frame that does not cause visitors to abandon the site requires a sophisticated, multi-stage image optimisation pipeline. The standard WordPress image handling is not adequate for this requirement.

The Solution: Preservation Engineering at the Pixel Level

Animation and Interaction Reproduction

The complex custom animations that defined the original site's character — the specific timing functions, the entrance and exit sequences for portfolio images, the navigation interaction patterns — were systematically recreated in custom CSS and JavaScript within the WordPress environment. This required first documenting every animated element in the legacy site with frame-by-frame precision, then building equivalent implementations in the new codebase, then testing at full-screen resolution until the timing, easing and visual result were indistinguishable from the original. On a project where the client has a professionally calibrated eye for visual precision, "close enough" is not a deliverable.

The Image Pipeline: Full Resolution, Instant Delivery

The image performance solution was built in several stages. First, a modern image format strategy: source files converted to WebP and AVIF formats that retain visual quality at significantly smaller file sizes than the legacy JPEG pipeline, without any perceptible quality loss at the resolutions the photographer uses. Second, a responsive image implementation that serves different file sizes to different screen resolutions — a visitor on a mobile device does not need the same file that a visitor on a 5K display does. Third, lazy loading implementation that prioritises the images currently in the viewport and defers others until they are needed, so the site loads immediately rather than waiting for all images in a portfolio section to download before showing the first one.

The combined effect of these optimisations produced a site that serves images at the full quality the photographer demands while loading at a speed that standard WordPress image handling cannot achieve for files of this resolution. The visitor perceives only the image. The technical infrastructure that makes that instantaneous impression possible is, appropriately, invisible.

CMS Independence: Giving the Artist Back His Archive

The third component of the rebuild — the custom WordPress backend — was in some respects the most commercially significant for the photographer himself. The legacy system required developer involvement to update portfolio content: adding new series, reordering existing work, retiring older projects from public view. For a working photographer whose portfolio is a living document that changes as new bodies of work are completed, this dependency was a practical constraint on how he presented himself.

The new WordPress backend was built with a custom content management interface specifically designed for portfolio curation — drag-and-drop series ordering, one-step image upload with automatic optimisation processing, intuitive project metadata management. Dimitris Poupalos can now update his portfolio, add new series as soon as they are completed, and adjust the presentation of his work without any developer involvement. His archive is his own.

What This Project Reveals About Building for Creative Professionals

The dpoupalos.com project is a specific type of engagement that most web agencies encounter rarely — and handle badly when they do. The natural instinct of a design-focused agency, given a project with maximum creative freedom, is to demonstrate its own aesthetic capability. A photographer of Dimitris Poupalos' standing is not looking for a collaborator's creative contribution. He is looking for a technical partner with the precision to realise a vision that is already formed.

This distinction — between creative partnership and technical execution in service of someone else's vision — defines a category of web work that requires a different kind of capability from a development team. It is less about creativity and more about fidelity: the ability to understand what already exists with sufficient depth to reproduce it exactly, improve it technically without altering it visually, and deliver a result that the client — who has the most acute possible eye for any deviation from intent — experiences as seamless.

Frequently Asked Questions