TYPO3 interfaces and custom extensions.
Connect systems. Extend functions to fit.
Your website should use data from another system, pass on content or provide a special function? We develop the right TYPO3 interface or extend TYPO3 with a custom extension.
For this, we first clarify which data and processes are involved and whether an existing solution meets the requirements. Where a custom development makes sense, we agree the range of functions and implementation with you.
Maintain data once and use it several times.
An apprenticeship job board shows offers from a central database. A festival website takes over the programme from an event platform. An event calendar in TYPO3 also provides dates for screens on campus.
The direction of the data exchange differs. What these tasks have in common is that information should not be maintained by hand in several places. We clarify which system manages which data and where it is needed.
Depending on the requirement, data is imported regularly, queried directly when needed or provided by TYPO3 for other applications. We also define how changes, duplicate entries and missing data are handled.
Extend to fit and keep maintainable.
Before we develop our own extension, we check existing solutions. What matters is whether they meet your requirements and can be sensibly operated and developed further.
We implement our own functions via the extension options provided by TYPO3. We document the implementation and test the agreed processes. For later TYPO3 upgrades, we look at which adjustments are necessary.
What we connect and develop.
How we develop your connection.
An interface must not only transfer data, but also suit your workflows. That is why we clarify the professional and technical requirements together.
Clarify requirements
Which data is needed, where is it maintained and how up to date does it have to be? We review existing documentation and sample data and clarify the responsibilities on both sides.
Plan the implementation
We define data mapping, transfer route and updating. This includes rules for changes, deletions and error cases. We agree the decisions that are important for your workflow with you.
Develop and test
We implement the connection and test it in a test environment with suitable test data. We also take missing, incorrect or duplicate entries into account. If necessary, we coordinate with the provider of the connected system.
Publish and hand over
After the agreed checks, we put the connection into operation and check the first transfers. You receive the agreed documentation. We agree subsequent support separately.
Less duplicate maintenance. Clearly regulated processes.
Your editorial team maintains information in the system intended for it. The connection provides it where it is additionally needed. It is clearly defined which content TYPO3 takes over and which continues to be edited editorially.
Documentation and agreed error handling support further support. We take known running costs, for example for an external provider's interface access, into account in planning.
Interfaces in our projects.
Three examples of how we connect TYPO3 with specialist systems and external platforms.
Frequently asked questions
Questions about interfaces and extensions.
An interface, a data export or suitable database access can form the basis. Whether the connection is possible and sensible depends, among other things, on the available data, access rights and technical limits. We check this on the basis of your requirements and the documentation of the respective system.
Both. We first check whether a maintained extension meets your requirements. Where a suitable solution is missing, we develop our own functions or connections. We also take into account the effort for maintenance and later version changes.
We define this to suit the function and the data. Depending on the connection, the last imported data can continue to be displayed, marked as possibly outdated or hidden. We can take already known expiry dates into account.
The website cannot, however, recognise changes that have not yet reached us because of the outage. We agree how errors are logged and reported during planning.
Yes, as far as this is intended for the respective connection. We jointly define which information comes from the leading system and which your editorial team adds in TYPO3. We also agree how manual changes are handled in the next transfer.
On request, we take over maintenance and adjustments as part of agreed support. This can include checking transfers and reacting to changes in the connected system. We define responsibilities, scope and billing in advance.
The interface description or a sample export as well as information on the desired functions, access rights and update intervals are helpful. Sample data should as far as possible not contain any personal or confidential information. If documents are missing, we jointly clarify what is needed for an initial assessment.
Then we check other regulated ways, for example a file export that TYPO3 can read in. We take into account timeliness, reliability and the necessary effort. If no suitable access option is available or the effort is disproportionate, we discuss alternatives.
You receive the source code of our custom development and the agreed documentation. We regulate rights of use and further processing in the order; the licence conditions of the libraries and extensions used must still be observed. On this basis, another service provider can also take over further development.
Which connection or function do you need?
Briefly describe what your website should do and which systems are involved. Together we clarify which solution comes into question and which information is still needed for an effort estimate.