Skip to content
openM!ndedby Simon van de Loo
← Back to overview
Live · volunteer work

VIDAhof e.V.

The website of an animal sanctuary near Kleve — taken over as a half-finished existing project and carried to completion. For openM!nded it is also the place where this way of working can be checked: what the model contributed is live on the page.

Visit the site: vidahof.de ↗
VIDAhof on a MacBook: homepage with the motto "For a life of dignity. For everyone."

An existing project, not a blank slate.

The association operates three farms near Kleve with around 130 rescued animals and is a recognized learning center for animal welfare. Therefore, the site must do more than just inform: it needs to recruit sponsorships and donations, showcase each animal individually, and host a community — member area with registration and dashboard, forum, donation flow.

It started at my previous employer and was never finished there. I took over the project: foreign code, foreign custom modules, plus a page builder where pages are stored as JSON in the database. I deliberately created new subpages as simple UIkit articles instead of using the builder — less convenient in the backend, but repairable if needed.

The association pays nothing for it. That is deliberate.

The model did the drudge work

  • 148alt texts, live on the site
  • 200+Photos with machine-determined cropping
  • 0Images that left the computer for it.

Every animal has a profile, every profile a photo, and every photo needs alt text and a crop that fits into two different layouts. With around 130 animals plus farm, team, and blog images, that's several hundred small decisions — none of which is interesting on its own, but together they cost days.

A!ley took over this part, the model running here anyway. No cloud service, no upload, no user data in someone else's hands.

Everything is still cross-checked. The model suggests, I decide — but deciding takes minutes and writing takes days.

Why that's more than convenience

Two years ago, by hand.

Several days of hard work

A municipal tourism project: over 120 physical exhibits were to be put online. What was delivered, as is common in such projects — mobile photos of varying quality and the specifications scattered across manufacturer emails.

Two cuts per piece: the wide shot with base and plaque, the close-up on the object alone. Plus handwritten notes in the schema, alt texts typed out myself, upload, next piece. I sat on this for several days — as an intern. If someone else had done it, those would have been paid developer hours, and they'd end up on the customer's bill.

Today

A stack run overnight

Two of the three steps worked exactly like that at VIDAhof: The crop becomes a coordinate question, and the alt-texts are generated in the same pass. The third — converting unstructured text from emails, notes, and data sheets into a clean schema instead of transcribing it — is the same mechanics, just applied to text instead of images.

What remains is the review. And that's the real work: a proposal that's off falls out in seconds. Writing it yourself from scratch takes minutes — two hundred times over.

For contextI didn't automate the tourism project back then — I didn't have the means for it. It's a comparison, not a second case study. The VIDAhof part is verifiable: the alt-texts, profile descriptions, and image snippets are live on the site and can be checked there.

What that changes in practice

JoomlaYOOtheme ProPHPMariaDBDockerMLX

Where the groundwork becomes visible