One TYPO3 installation can manage several websites and languages. Editors can be given access to the pages, fields, languages and media they are responsible for. Workspaces keep proposed changes separate from the live site until the team is ready to publish.
We agree the site structure, content elements and functionality with your editors and business teams. We then develop the design, TYPO3 site package and required extensions. For existing websites, we assess which parts can be reused and where changes are needed.
The page tree shows the site structure. Alongside it, the Layout view places content in the areas defined for the website, giving editors a clear set of components to work with.
Product view: © TYPO3 GmbH
TYPO3 14.3 LTS — official release screenshots
We build new TYPO3 websites and take on specific tasks within existing projects, working with your editors, IT team and other agencies.
We plan navigation, page types and reusable content elements, and design the website for desktop and mobile devices. Fluid templates and configuration are brought together in a site package. Editors get input screens for their content, such as services, locations or contacts, and test the structure with their own text and images.
For multiple brands or countries, we define which pages and media are shared and which are maintained locally. We configure language versions, editorial permissions and workspaces. Previews and approvals are agreed with the teams involved, and training uses their everyday tasks.
We develop data imports, catalogues, search, multi-step forms and restricted customer or partner areas. We first review the extensions and custom code already in use. For new functionality, we define the data model, input screens and permissions, using TYPO3’s supported extension points.
Whether passing enquiries to a CRM, importing product data from a PIM or integrating images from a DAM, we define the data mapping, direction of transfer and update process. Logging and error handling make failed transfers identifiable and allow them to be processed again.
We work on page titles, metadata, structured data, internal links and the relationships between language versions. Our load-time checks include images, JavaScript, caching and server responses. For navigation and forms, we address keyboard operation, clear labels, focus management and error messages.
For a version upgrade, we check compatibility across the core, PHP, site package and extensions. When changing CMS, we map content, media and records to the new structure. We test the migration on staging, check forms and integrations, and plan redirects and the transfer of changes made in the old system before launch.
We manage core and extension updates, fix bugs and develop new features. Changes are version-controlled and checked in a separate environment. We agree responsibility for backups, incidents and releases with your IT team and hosting provider. Source code, configuration and documentation are available to your company.
Central and local editors work in the same TYPO3 backend. They can reuse shared material while managing their own pages and translations.
Manage several brand and country websites in one TYPO3 installation.
Maintain media and reusable content elements centrally.
Give each team editing access to the pages and languages they look after.
Drafting, review and publishing all happen in TYPO3. Its workspaces let editors prepare changes inside the CMS without immediately changing the public website.
Edit pages and content in a working version that has not been published.
Review changes in the page preview and use configured approval stages to coordinate sign-off.
Editors with publishing rights move approved workspace changes to the live version.
Your PIM supplies the product details; TYPO3 adds the editorial content. Enquiries from the website should reach the right sales team with the information they need.
An integration we develop brings the required data into the TYPO3 data model.
Editors add use cases, images and supporting content in the CMS.
We build the product pages, search and enquiry forms for the website.
The external source of product data. The integration defines which information TYPO3 imports.
Receives form enquiries through a separate API integration for the sales team to follow up.
Sales partners need different documents from employees. The website should make the right material available and, where needed, connect to an existing sign-in service.
Manage website users and assign them to the relevant user groups.
Restrict pages and content to the groups authorised to access them.
For confidential documents, we secure direct file access as well as the page containing the download link.
We can connect your company’s identity provider. Access to the website’s private areas is enforced in TYPO3.
For lotterien.at, we connected Storyblok as an editorial source to the existing TYPO3 website. Our integration transfers articles, images and SEO metadata and handles publication, updates and withdrawals. Existing pages and custom TYPO3 extensions remain in place.
The printed Vinaria wine guide is prepared in InDesign. Our TYPO3 extension imports regions, wineries and wines from the XML export into a searchable online catalogue.
For DONAU’s website, we implemented accessible navigation, almost a hundred forms and insurance application journeys, together with &US and in collaboration with Austria’s Hilfsgemeinschaft der Blinden und Sehschwachen. The website received WACA Bronze certification in 2024.
For a relaunch, we plan content migration and existing URLs from the outset.
Together with editors, business teams and IT, we establish the content, audiences, languages and integrations the site needs.
We test the site structure, content types and design with real material. The result is a prototype your team can use to make decisions.
We develop templates and features, migrate content and check permissions, accessibility, redirects and integrations on staging.
Editors, IT and operations agree the switchover. Training, monitoring, updates and clear ownership are part of the handover.
A new requirement need not mean a relaunch. We establish what can stay and where the system needs to change.
We review the core, extensions, data model and hosting, and talk to the people using them. This reveals dependencies and outstanding risks.
We agree one concrete workflow and its acceptance criteria, with a clear scope, priorities and an explained effort estimate.
We build on a separate environment. Tests cover both the new feature and the existing workflows it affects.
We coordinate the release, monitor errors and feedback, then plan the next improvement with your team.
The starting version, custom extensions and integrations determine the work involved. We break larger jumps into steps that can be checked individually.
We review TYPO3, PHP, the database, extensions and hosting, then agree the target version and the changes it requires.
Business-critical workflows, forms and integrations are documented and covered by automated tests where useful.
We handle the required version steps separately, checking data, functionality and editorial workflows after each one.
We agree acceptance, backups, rollback and a release window, then check the production system after the move.
We can take on the maintenance of your TYPO3 website or work alongside your IT team and current agency on specific tasks.
We review TYPO3 and PHP versions, custom extensions, integrations, source code and documentation. Together with your editors, we identify daily requirements and known faults.
You receive a prioritised assessment of required changes, effort and dependencies. It separates security and compatibility issues from planned features and identifies unresolved questions that still affect the estimate.
We coordinate the handover with your IT team and current agency, agree responsibility for updates, backups and incidents, and check changes in a separate environment. Your hosting contracts remain directly with your provider.
We have maintained and developed these platforms over many years.
An upgrade updates the technical foundation. If the design, site structure and editorial workflows still meet your needs, they can often stay as they are. A relaunch becomes relevant when those areas also need substantial changes. We assess the two separately: a version upgrade alone is no reason to rebuild a website.
We review their purpose, integrations and dependencies, and check the code against the target version. We make any necessary changes to custom extensions and review available updates and features for third-party extensions. If no suitable update is available, we compare adapting the extension, replacing it or building a new one, based on the functions you actually use.
Development and trial migrations take place in a separate environment. For the switch, we agree when editing in the existing system will stop and how to transfer content changed in the meantime. Whether this requires a brief pause in editing depends on the content, data volumes and connected systems.
We preserve existing URLs where the new structure allows. For addresses that change, we map them to the appropriate destination pages and set up redirects. We check content, metadata, internal links and language versions before the switch, then review indexing and errors in Search Console after launch.
