TYPO3 in the Nuremberg metropolitan region
Between industry, mail-order retail, the trade fair business and the research landscape around Erlangen, the region is broadly set up digitally. For corporate sites with several languages, product data and finely graded editorial permissions, TYPO3 has long been the obvious choice here, and correspondingly many installations have grown over the years.
That is where we come in: updates that restore the connection to support, relaunches that keep the rankings, and development when the standard runs out.
A clear word instead of pretend proximity
We have no office on the Hauptmarkt, and we do not pretend otherwise. Our base is Stuttgart-Feuerbach; Nuremberg is around 200 kilometres away. For the daily project work that makes no difference: it runs in Git, over video calls and on preview environments. For the kick-off, the workshop and the training we come to the region, planned and dependable.
That openness is deliberate: an agency that plays tricks with its own address will hardly do otherwise with an estimate.
Accessibility as a Franconian subject
With chambers, associations, universities and municipal bodies, the region has many sites for which BITV 2.0 and the BFSG are binding. We implement accessibility in the sitepackage, audit what exists honestly, and train the editorial team, because a site only stays accessible when the daily work plays along.
When search is the main route through a site
In mail-order retail and with technical product ranges, search is not an emergency exit but the main route. Somebody looking for a product does not click through the navigation.
The built-in TYPO3 search often does not stretch that far: it finds hits, but it cannot narrow them down, forgives no typos and searches no data sheets. Where that is needed, Solr comes in, a standalone search engine with facets, autocomplete and search inside the contents of PDF files.
The honest flip side: Solr is an additional service that has to be run and monitored. Whether the hosting environment can carry it is something we settle before the decision, not after. A search that stops indexing after six months is worse than none.
Product data comes from the system, not from the CMS
The second regional subject connects to that. Product ranges with many variants do not belong typed into the backend; they sit in an ERP or a PIM and get fetched from there.
For TYPO3 that means custom data models through Extbase, an interface with defined behaviour when something fails, and output that can be shaped freely. What happens when the other side does not answer is the first thing we settle, because that is the part that counts in operation.