TYPO3 agency Hamburg.
Develop new websites. Move existing systems forward.
We develop and support TYPO3 websites – from the compact company website to the platform with several languages and editorial teams. We take over existing installations, modernise them and develop them further. We include content and structures that work instead of automatically rebuilding.
For your project, we combine design, front-end and back-end development and the necessary interfaces. We define together which services you need.
When the system slows down everyday work more than it supports it.
The situations are often similar: a university maintains degree programmes in several places because each faculty has developed its own processes over the years. A museum association wants a central presence, but the processes of the individual editorial teams do not mesh cleanly. Or a company runs several country websites where nobody knows for sure any more which text version is current.
The cause rarely lies with the editorial teams. Such structures arise when a system grows with its requirements over many years:
- Extensions are no longer maintained.
- Page structures reflect long-outdated responsibilities.
- Access rights were assigned once and have not been checked since.
At some point, coordination takes up more time than the actual editorial work.
At the same time, the technical pressure to act increases: older TYPO3 versions reach the end of their security support, while current PHP versions place new requirements on the system. The longer modernisation is postponed, the more laborious it can become.
Suitable architecture before trends.
How should your TYPO3 website be built? What matters is which architecture suits your requirements and workflows. We check with you whether a classic implementation makes sense or whether a separately developed front end offers concrete advantages.
When does a decoupled architecture make sense?
In a decoupled architecture, content is managed in TYPO3 and output to one or more front ends via interfaces. This can make sense if the same content is to appear on different channels – for example on a website, in an app or on another digital offering. Special integrations or independently developed front ends can also speak in favour of it.
If, on the other hand, your editorial team needs a reliable preview, well-established publishing processes and processes that are as simple as possible, a classic TYPO3 architecture is often the better choice. A decoupled system consists of more components, increases the effort in operation and can make the path from editing to publication more complex.
We therefore only recommend this approach if the additional technical effort offers a concrete benefit.
Why not everything always has to be rebuilt
An existing system contains a lot of knowledge about your content, processes and editorial requirements. That is why we do not automatically recommend a complete rebuild.
Instead, we check which components continue to work and where there is actually a need for action. Outdated extensions, templates or interfaces can often be replaced in a targeted way. This modernises the system without unnecessarily giving up proven structures.
Classic or decoupled – what suits your requirements?
Together we check the criteria that are decisive for your content, editorial processes and technical framework.
| Feature | Classic TYPO3 | Decoupled front end |
|---|---|---|
| Editorial preview | Directly in the system, without detours | Has to be built and maintained separately |
| The same content in a second place (app, partner site) | Can be retrofitted via interfaces | Provided for from the start |
| Operating effort | One system, one deployment | Several parts, several update paths |
| Freedom in the front end | Large, within the TYPO3 conventions | Very large, but more on your own responsibility |
| Getting started | Usually productive more quickly | More laborious to build, but more open |
| Fits if | The website is the main channel | Content serves several channels |
What we take on for you as a TYPO3 agency in Hamburg.
What we deliver beneath the surface.
A website becomes demanding where standard functions are no longer sufficient – for example with a central course database, a multi-stage application process or the connection of editorial content with existing specialist systems.
Standard before custom development
Before we write our own code, we check whether TYPO3 or a maintained extension already covers the task. We develop individually where the existing options are not sufficient. We take the later maintenance effort into account from the start.
Interfaces with a system
Before connecting, we clarify which system specifies the data, how often it is transferred and what should happen in the event of a fault. This way we define not only the data exchange, but also how the website behaves when a connected service is temporarily unavailable.
Performance from the start
We take loading times into account already during concept and development. We therefore check extensive data queries, large images or external services early. Supported TYPO3 versions and regular updates are also part of technical planning.
How your TYPO3 project runs with us.
Dedicated contacts, clear responsibilities and transparent decisions form the basis of our collaboration. We provide you with the current development states on a test environment. This allows you to check results early before changes are published.
Clarification
At the start, we talk about your goals, requirements and priorities. We look at the existing system and involve the people who will later work with it. From this we develop a shared vision – including the areas that are deliberately to remain unchanged.
Structuring
We organise content, functions and editorial responsibilities. Together we distinguish what is required for the start, what can sensibly be added and what may follow at a later date.
You make the decision. We provide the professional basis and show transparently what effects the various options have on effort, budget and schedule.
Development
We develop in manageable steps and provide the respective interim states on a test environment. This lets you see early how the solution works and give feedback.
Before publication, we check functions, display, usability and editorial work in the backend. If we identify further potential for improvement, we address it openly – even if it was not part of the original task.
Handover and support
We prepare your team for working with the new system and agree the publication together with you. The go-live takes place in a controlled way and only after your approval. We refrain from risky publications on Friday evenings.
Your contacts remain the same afterwards as well. We accompany ongoing operation and develop the system further based on the jointly agreed next steps.
Experience that counts.
As a specialised TYPO3 agency from Hamburg, our team combines more than 30 years of experience with TYPO3 – from consulting and concept to technical implementation. This knowledge becomes particularly valuable where decisions have long-term effects on operation and further development.
We recognise early where unnecessary complexity can arise: with extensions without a maintenance perspective, hard-to-follow permission concepts or migrations based on outdated data models. We address these risks openly while simple and economical solutions can still be found.
As a Silver Member of the TYPO3 Association, we also support the continuous further development of the system.
How we organise projects and work with you is described on our page about how we work. You can find concrete examples in our projects.
Communication works great and we have already done quite a lot together. From simple TYPO3 websites to complex applications – everything is covered.
What changes in everyday work.
A technical modernisation should also make daily work easier: content can be published more easily, responsibilities are clear and unnecessary coordination is no longer needed.
In concrete terms, this means:
- Editorial teams work in their own area without having to check back for every little thing.
- Content that appears in several places is maintained once.
- The editorial team can see which content has already been translated and where translations are still missing.
- Version changes become plannable and do not have to become a fundamental rebuild every time.
This allows the platform to be developed further without starting from scratch with every new requirement. How we accompany ongoing operation is described under Maintenance and support.
Three TYPO3 projects and what they achieve.
Your next step with TYPO3.
Different tasks. Suitable support.
Frequently asked questions
What clients ask us about working with TYPO3.
If your question is not here, feel free to ask us directly. We also answer when the honest answer is “it depends”, and say what it depends on.
TYPO3 plays to its strengths when you want to manage extensive content, several websites, different languages or differentiated editorial responsibilities. It also offers a reliable basis for connecting specialist systems and custom functions.
For smaller websites, TYPO3 can be set up lean. If the system is nevertheless oversized for your requirements – for example with a largely static website without regular maintenance – we tell you that openly. What matters is not which system is considered particularly modern, but which one sensibly maps your foreseeable requirements.
We can give you an initial cost range after a joint conversation. The effort depends, among other things, on the scope and condition of the existing content, the languages required, editorial processes, interfaces and custom functions.
We distinguish transparently between what is necessary for the start, sensible additions and functions that can follow later. This allows you to define the project scope on the basis of clearly described options.
The duration does not depend solely on the technical implementation. Preparing the content, necessary decisions, interfaces, coordination and approvals also influence the schedule.
That is why we plan the relaunch in stages. Together we define which content and functions are needed for the start and which can be added afterwards.
We implement new projects on a currently supported TYPO3 LTS version. We look at existing installations individually and plan necessary updates in good time before the end of the respective support period.
In addition to the TYPO3 core, extensions, custom code, PHP version and other technical dependencies must also be taken into account.
In many cases not: content and basic structures can be carried over. The effort depends on the age and structure of the system, above all on extensions and custom developments that are no longer maintained. How we plan assessment, target version and conversion is described on the page TYPO3 upgrade.
Yes. We regularly take over existing TYPO3 installations and continue or modernise them.
At the start, we check, among other things, the source code, the extensions used, the database, the server environment and the current maintenance status. From this we derive which components can be retained and where a revision is more economical.
For the check, we need agreed access to the relevant systems. If documents or permissions are missing, we support you with an orderly handover. We transmit access data via a secure, separately agreed channel.
Yes. TYPO3 allows differentiated rights by page areas, languages and editorial tasks. This allows several teams to work within one system without gaining access to areas for which they are not responsible.
Before the technical setup, we jointly clarify who may create, edit, approve or publish content. A good permission concept begins with clearly regulated responsibilities.
Yes. TYPO3 also supports websites where not every piece of content is available in all languages, different teams are responsible for individual language versions or further languages are added later.
It is important to define the translation process early: Which content is translated, who is responsible and how are changes to the source language handled? From this we develop a process that suits your editorial team.
Yes, if existing TYPO3 functions and maintained extensions do not sensibly cover the requirement. We keep custom developments manageable because every additional line of code has to be maintained in the long term. What we connect and develop is described on the page Interfaces and extensions.
Yes. We train your team directly on your own website and using the functions it uses in everyday work. The training takes place online or on site at your premises. You can find more information on content and procedure under TYPO3 training.
On request, we continue to accompany your TYPO3 website after publication. This can include security and maintenance updates, technical troubleshooting, monitoring and planned further development.
We agree the scope of services and response times to suit your system and its importance for ongoing operation. Your previous contacts remain the same wherever possible.
You can find more information under Maintenance and support.
First we get an overview of content, page structure and connected systems: What is still needed, what is outdated and which information is maintained more than once? Together with you, we then clarify the responsibilities and approvals of the editorial team.
We plan the technical conversion in stages and check the results on a test environment. If several websites or brands belong together, we also check whether a shared TYPO3 installation makes sense. An example of supporting an extensive university website is our project for HafenCity University Hamburg.
We support clients throughout Germany and also in Switzerland. Our headquarters are in Hamburg. During the project, we coordinate via video conference, by phone and through shared project documentation. Kick-off meetings, workshops and training take place online or on site at your premises by arrangement. Clear responsibilities and regular exchange are more important to us than physical proximity.
We take a later handover into account already during implementation and documentation. We record in the project contract which rights of use and further processing you receive. The respective licence conditions also apply to the libraries and extensions used.
We also agree the management of domains, hosting and system access with you. In the event of a change of service provider, we support an orderly handover of the required documents and access.
Let us talk about your TYPO3.
Do you want to develop a new TYPO3 website, improve an existing one or change the agency looking after you? Send us a short description and the link to your website. In the free initial consultation, we clarify your goals and the next steps; you do not need to compile technical documents for this yet.