Versions
TYPO3 14: What Is New and What the Update Means
Content Blocks in the core, a new backend, Fluid 5. What of that reaches daily work, and when the move is due.
TYPO3 since version 4
TYPO3 agency for installations that last
We build TYPO3 websites, take over installations that have grown over years, and keep them inside the supported range. No page builder, no bought-in theme: the sitepackage, the extensions and the editing interface are made for the case at hand.
aceArt GmbH is a Silver Member of the TYPO3 Association and helps fund the ongoing development of the system.
- Build
- Sitepackages, Extbase extensions and TypoScript for projects that go beyond a brochure site.
- Take over
- Including installations somebody else left behind. Read and understand first, touch afterwards.
- Run
- The LTS lifecycle, security advisories, and one contact who knows the installation.
Services
What we do with TYPO3
Seven areas that rarely stay separate. An update exposes old debts, a relaunch raises the accessibility question, and both decide later how well the site is found.
- TYPO3 Development Sitepackage, Extbase extensions and TypoScript for requirements no ready-made theme covers.
- TYPO3 Relaunch A new site without losing the visibility of the old one. With a redirect plan rather than crossed fingers.
- TYPO3 Update From a security patch to a jump across several major versions, with an inventory taken first.
- TYPO3 Emergency Blank page, dead backend, a failed update. We narrow it down before anything gets overwritten.
- TYPO3 Maintenance Security advisories, plannable updates and someone who knows the installation before anything happens.
- TYPO3 Monitoring Good numbers do not hold by themselves. Continuous measurement with SiteSentry, free, with an email when a threshold breaks.
- TYPO3 SEO URLs, metadata, hreflang and structured data solved where they arise: in the sitepackage.
- TYPO3 Page Speed In TYPO3 the big levers sit in the caching and in image delivery, not in image compression.
- TYPO3 Accessibility An audit, implementation in the sitepackage, and the training without which it slips again after three months.
- TYPO3 Training On your own installation rather than a demo, with the elements you genuinely use.
Lifecycle
Is your TYPO3 version still supported?
Once active maintenance ends, security fixes only reach paying ELTS customers. When ELTS runs out too, known holes stay open. The dates come straight from get.typo3.org.
Actively maintained ELTS only (paid) As of the site build, data from get.typo3.org
Process
How a project runs with us
Listen, then look
First we work out what you have in mind and what already exists. With an installation that is already running, we look at the version, the extensions and the database before we judge anything.
An assessment, not sales prose
You get an honest view of what makes sense, what can wait and where the risks sit. Including when the answer is that a small fix will do.
Work in steps you can follow
Development in Git, a preview on a separate environment, sign-off before anything goes live. You can see at any point what is being worked on.
Hand over and stay reachable
Editor training, documentation and an operating plan. After that you decide whether you take over yourself or we keep the maintenance running.
Knowledge
Field notes
Questions that come up in almost every TYPO3 project, answered at length.
Versions
When Support Ends: ELTS, Risk and the Alternatives
Extended support buys time, not a solution. When it is still the right call.
Decisions
TYPO3 Update or Relaunch? How to Decide
When an update is enough and when patching on costs more than rebuilding. With the criteria that genuinely count.
Questions people ask a TYPO3 agency
What does a TYPO3 agency do differently from a general web agency?
TYPO3 is not a system you pick up on the side. Sitepackage structure, TypoScript, TCA configuration and the Extbase lifecycle are subjects in their own right, and anyone who only touches them occasionally builds solutions that come apart at the next major update.
A specialised agency also knows the lifecycle: when a version drops out of support, what an LTS jump typically costs, and which extensions tend to cause trouble. That shapes the running costs of the next few years far more than the design of the home page does.
Do you take over existing TYPO3 installations from other providers?
Yes, and it is a large part of what we do. We start with an inventory: TYPO3 version, installed extensions, custom code, database size, server environment and the state of the editorial structure.
That tells us whether we can carry on directly or need to clear up first. You hear the answer before the work starts, not halfway through it.
We are not sure TYPO3 is the right system. Do you advise on that too?
Yes. TYPO3 earns its keep with multilingual sites, several domains inside one installation, finely graded editor permissions and connections to systems you already run. For a modest site with two or three editors it is often more machinery than the job needs.
If we conclude that something else fits better, we say so. A project that starts on the wrong system turns unpleasant for everyone involved.
What does a TYPO3 project cost?
That depends on things we have to know first: how many pages, how many languages, how many custom content elements are needed, whether interfaces are part of it, and what state an existing system is in.
So we do not quote flat rates. After a conversation and a look at what exists, you get an estimate with ranges that shows which part depends on what. There is more on this in the guide What makes a TYPO3 project expensive or cheap.
Where are you based, and do you work outside your region?
We sit in Stuttgart-Feuerbach. Development runs remotely anyway, in Git and with a preview on a separate environment, so distance barely affects how a project goes.
For kick-offs, workshops and training we travel. What that looks like in practice is described on the pages for Stuttgart and Munich; the locations overview lists the rest.
Can you work with our existing hosting?
Usually yes, as long as the environment meets the requirements of the TYPO3 version in use. What matters is the PHP version, the available extensions, the database version, Composer support and whether we can deploy over SSH.
If the environment does not fit, we name exactly what is missing. Moving is then a decision you make, not a condition we set.
Tell us about your TYPO3 project
A new build, an installation someone else left behind, or an update that has stalled: write and tell us what is on the table. You get an assessment back, not a stock offer.