TYPO3 for companies in Stuttgart
The Stuttgart economy is shaped by mechanical engineering, vehicle technology and their suppliers: companies whose websites are rarely brochures. Product data from a PIM, several languages for international markets, finely graded permissions for specialist departments. Those are exactly the requirements TYPO3 was built for.
Add to that associations, chambers and public bodies for whom accessibility is not optional. Both are core cases for us: development with a sitepackage of your own, and accessibility to BITV 2.0 built into the foundation rather than retrofitted.
On site here really does mean on site
Our office is in Sieglestrasse in Feuerbach. For Stuttgart projects that means the kick-off happens around a table, workshops and training in our rooms or in yours, and when something in a project needs clearing up, a meeting is not a travel plan.
The daily work still runs the way it works best: development in Git, discussion over video calls, every change visible on a preview environment before it goes live.
Taking over existing Stuttgart installations
A large share of our enquiries from the region concerns installations that have grown over years and whose care is ending: the agency has dissolved, the contact has left, or the trust has. We take systems like that on with an inventory: version, extensions, custom code, the state of the backups.
After that you know what you have, and whether an update is enough or a relaunch is the more honest route.
What Stuttgart projects often need
Two requirements come up more often than average in the region, and they are connected.
Product data that does not originate in the CMS. Suppliers and machine builders maintain variants, characteristics and data sheets in an ERP or a PIM. The website should show the right thing from that without anyone typing it twice. Technically that is an interface question; the real work sits in the behaviour when something fails and in the coordination with the system on the other side.
Several languages for export markets. Hardly any site stays monolingual once customers sit outside Germany. Which structure carries that, and what happens to untranslated content, is decided before the first translation. We go through it in the guide on multilingual sites.
Where the two come together, a website becomes a system. That is exactly what TYPO3 is built for, and exactly why the groundwork on the structure matters more than any design draft.
When nobody knows how it runs any more
A pattern we see regularly in the region: the installation runs, but nobody can say how a deployment works, where the configuration lives, or whether the backups can be restored. Usually because the people have changed.
We start handovers like that with an inventory and write down what we found. That protects both sides and is the basis for somebody else being able to carry on afterwards, ourselves included, a year later.