Skip to content
STOFFEL.IO

00 / Case study

Four years.
Same developer.

AMCM builds customized metal 3D printing machines, used for parts like rocket engine combustion chambers. The agency that built their website no longer had time for it, so in 2022 I took it over. I kept it running, rebuilt it, and carried it across to a second design. Four years on I am still the one they come to when something needs doing.

  • 04

    Years as their
    developer

  • 02

    Designs on
    one build

  • 30+

    Blocks for
    the team

  • 01

    Point of contact

Client
AMCM GmbH
Role
Sole developer
Stack
Statamic
Since
2022, ongoing

01 / Starting point

AMCM builds customized metal 3D printing machines, used among other things for rocket engine combustion chambers. Their website ran on an early version of Statamic, built by an agency that no longer had the capacity for it. Nothing was wrong with the work. There was simply nobody with time to do the next thing.

I took it over in 2022. For two years I kept the old build running and added what the team asked for, when they asked for it: a certification badge, self-hosted fonts, a campaign landing page with its own sign-up form. None of it large, all of it done the week it was needed.

Then I rebuilt the site from scratch to a new design. Shortly after it went live, AMCM decided on a completely different look from another designer, and I carried the site over to it on the same build.

02 / Constraints

The machines carry the site
Every machine needed its own page with technical data, videos and downloads, and adding the next one could not mean building another template.
Someone who answers
AMCM has no developer of its own. What the team needed was not a project but a person: someone who replies, explains what is possible in plain terms, and makes the change rather than booking it in for next quarter.
The team publishes
News, events and trade-fair pages are published by AMCM's own staff, so every section had to be a block they can place and fill themselves.

03 / What I built

  • B/01

    A page for every machine

    Every machine has its own page with technical data, image tiles, videos and downloads. They share one set of blocks, so the next machine is a new entry rather than a new template.

  • B/02

    A block library

    More than 30 blocks, from fact tiles and image accordions to a company timeline, key contacts and a staff grid. The team combines them into new pages without me.

  • B/03

    Two designs, one build

    The rebuilt site had barely launched when AMCM chose a completely different look from another designer. Because the pages are made of shared blocks rather than fixed templates, moving to it meant reworking blocks, not starting again.

  • B/04

    News and events

    A news section with featured posts and a filter that keeps loading as the visitor scrolls, plus an event list for trade fairs.

  • B/05

    Accessible on every screen

    A main navigation and accordions that work with a keyboard and a screen reader, and a separate sub-navigation for phones.

  • B/06

    Scroll-driven animations

    Frame sequences that play as the visitor scrolls, showing beam shaping, laser wavelengths, spot sizes and build volumes. The technology is easier to follow in motion than in a paragraph.

The AMCM M 4K machine page: a large model name, the line
Fig 01 / A machine page: name, key figures and introduction, built from the same blocks as every other machine.
A rendering of the AMCM M 4K next to an accordion of its features, with Build Volume opened.
Fig 02 / Features next to the machine, in an accordion the team fills in themselves.
A news overview with a filter button and a grid of posts with photos of machines and printed parts.
Fig 03 / News and application stories, with a filter and more posts loading as the visitor scrolls.

04 / Credits

Built directly for AMCM, without an agency in between. The first design was by Steffen Hirth, the current one by Daniela Rost of Spreadfilms GmbH.

05 / Next step

Inherited a website nobody looks after?

It does not matter much what it runs on or who built it. Describe what it has to do next, and the answer comes back as keep it, fix it or rebuild it.