Exporting begins with the structure
Mid-sized firms with customers across half of Europe all face the same task: the website has to work in several languages without maintaining it turning into a second full-time job.
The mistake made most often is too much too early. Creating five language versions is quick; keeping them current is not something anyone manages on the side. So we recommend cutting the multilingual area deliberately small and maintaining it completely. The decisions behind that are set out in the guide on multilingual sites.
Two neighbouring cities, two sets of requirements
Reutlingen and Tübingen sit close together and still pose different tasks. Here product communication, sales support and export markets. There research sites with many departments, distributed editorial teams, and the accessibility obligation of publicly funded institutions.
For us that does not mean two approaches but the same care in different places: fine-grained permissions and workspaces there, data structures and interfaces here.
Close enough for an afternoon
Feuerbach to Reutlingen is a good half hour. That makes on-site meetings straightforward: a kick-off in the morning, editorial training in the afternoon, without anybody losing a whole day.
What stays remote all the same is the development, in Git, with a preview environment and sign-off before go-live.