Pages and content in one overview
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
What does your website need to do?
Shared content, distinct websites.
Central and local editors work in the same TYPO3 backend. They can reuse shared material while managing their own pages and translations.
Inside TYPO3
-
Sites & languages
Manage several brand and country websites in one TYPO3 installation.
-
Shared content
Maintain media and reusable content elements centrally.
-
Editorial permissions
Give each team editing access to the pages and languages they look after.
Prepare a campaign before it goes live.
Drafting, review and publishing all happen in TYPO3. Its workspaces let editors prepare changes inside the CMS without immediately changing the public website.
Inside TYPO3
-
Workspace drafts
Edit pages and content in a working version that has not been published.
-
Preview & approval
Review changes in the page preview and use configured approval stages to coordinate sign-off.
-
Publishing
Editors with publishing rights move approved workspace changes to the live version.
Keep product data at its source.
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.
Inside TYPO3
-
Imported product data
An integration we develop brings the required data into the TYPO3 data model.
-
Editorial content
Editors add use cases, images and supporting content in the CMS.
-
Catalogue & enquiries
We build the product pages, search and enquiry forms for the website.
Connected systems
-
PIM / ERP
The external source of product data. The integration defines which information TYPO3 imports.
-
CRM
Receives form enquiries through a separate API integration for the sales team to follow up.
Give each partner the right information.
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.
Inside TYPO3
-
Users & groups
Manage website users and assign them to the relevant user groups.
-
Private pages
Restrict pages and content to the groups authorised to access them.
-
Protected downloads
For confidential documents, we secure direct file access as well as the page containing the download link.
Connected systems
-
Existing sign-in service / SSO
We can connect your company’s identity provider. Access to the website’s private areas is enforced in TYPO3.
- System review, information architecture, content modelling, multi-site and multilingual planning
- Site packages, Site Sets, Fluid templates and custom TYPO3 extensions
- Roles, permissions, workspaces, approvals and editorial translation workflows
- Connections to CRM, PIM, DAM, search, portals and specialist applications
- Technical SEO, structured data, redirects, performance and accessible frontends
- Security, privacy, Composer-based deployment, automated tests and operational documentation
- Upgrades, migration, training, support and planned development
What comes next for your TYPO3 website?
From the first content examples to a working website.
For a relaunch, we plan content migration and existing URLs from the outset.
-
01
Agree the scope
Together with editors, business teams and IT, we establish the content, audiences, languages and integrations the site needs.
-
02
Try the structure
We test the site structure, content types and design with real material. The result is a prototype your team can use to make decisions.
-
03
Build & test
We develop templates and features, migrate content and check permissions, accessibility, redirects and integrations on staging.
-
04
Launch & support
Editors, IT and operations agree the switchover. Training, monitoring, updates and clear ownership are part of the handover.
Add what your website needs next.
A new requirement need not mean a relaunch. We establish what can stay and where the system needs to change.
-
01
Understand the system
We review the core, extensions, data model and hosting, and talk to the people using them. This reveals dependencies and outstanding risks.
-
02
Define the change
We agree one concrete workflow and its acceptance criteria, with a clear scope, priorities and an explained effort estimate.
-
03
Develop & safeguard
We build on a separate environment. Tests cover both the new feature and the existing workflows it affects.
-
04
Release & refine
We coordinate the release, monitor errors and feedback, then plan the next improvement with your team.
A version upgrade you can follow, step by step.
The starting version, custom extensions and integrations determine the work involved. We break larger jumps into steps that can be checked individually.
-
01
Check compatibility
We review TYPO3, PHP, the database, extensions and hosting, then agree the target version and the changes it requires.
-
02
Build the test coverage
Business-critical workflows, forms and integrations are documented and covered by automated tests where useful.
-
03
Migrate in stages
We handle the required version steps separately, checking data, functionality and editorial workflows after each one.
-
04
Approve & switch over
We agree acceptance, backups, rollback and a release window, then check the production system after the move.
- TYPO3 extension development New features and existing extensions
- TYPO3 14 upgrade Review, trial migration and planned release
- Website maintenance and support Security, operations and ongoing development
- Headless CMS Storyblok, Payload and hybrid content architectures
- Neos CMS In-page editing and multilingual corporate websites