A new site for an earthworks company, from Figma to Elementor Pro

A small German earthworks company needed a new website to show its services and get enquiries. A partner marketing agency designed it in Figma and handled the client. The build came to me through a German web agency, and I was the only developer. The design had no mobile version and relied on scroll effects, with sections pinned while the page moves.

From the designer’s video walkthrough I estimated two options. The partner chose the full one, with all animations, on Elementor Pro.

From the Figma file to Elementor pages

I built the site from its own repository. My own tooling reads the Figma file, and scripts turn each page into standard Elementor content on staging. So the client edits real Elementor widgets, images from the media library, global colours and fonts, and counters.

The design had no mobile layout, so I designed it from scratch and checked every change at 1440, 820 and 414 pixels.

I also checked it on an iPhone, an iPad and a Mac, and the pinned scroll sections in full screen and in ordinary browser windows. After each kind of error I added an automated check, including one that refuses to overwrite texts the client edited.

Along the way I removed a duplicate Google Tag Manager load, so nothing reaches Google before the visitor consents. Downloadable staging backups sat in the migration plugin’s folder. I removed them, blocked the folder and moved the backups outside the web root. On staging I connected the contact form to the client’s mailbox and tested delivery end to end.

The move to the client’s host

The move wasn’t in the original scope. The host’s own tool failed, so I found the cause and prepared a clean export at half the size. The last review round with the agency closed with nothing open. After the move every internal link worked and every page matched staging at all three widths.