TYPO3 consulting and training

A second opinion before it gets expensive

Sometimes what is needed is not a project but two days of someone asking the right questions.

The most expensive decisions in a TYPO3 project are taken at the beginning and look harmless while they are: the choice of an extension, the structure of the page tree, the language concept, the question of whether content belongs in Content Blocks or in records of its own. Get one of those wrong and you notice two years later — and then pay a multiple to correct it.

Typical engagements

• An architecture review before a larger rebuild. We look at the page tree, the language concept, the extensions and the deployment, and write down what holds and what does not.
• A code review of an existing extension. Security, maintainability, compatibility with the next LTS — with concrete findings rather than general advice.
• A second opinion on a quote. Is the effort realistic, is anything essential missing, do the assumptions hold. We assess the substance, not the competitor.
• Editorial training. Half a day, on your own website, with your own content. Afterwards your team can maintain the pages it actually has to maintain.
• Support during a tender. We help with the requirements catalogue so that the quotes you receive are comparable.

How it works

Consulting engagements are billed by the day and deliberately kept small: one to three days, a written result, a conversation to go through it. What you do with it afterwards is your decision — even if it goes against working with us.

What a review actually delivers

What you get at the end is a written document, not meeting notes. For an architecture review that is usually 10 to 20 pages with a list sorted by urgency: what has to be done before the next LTS jump, what is technical debt without a deadline, and what is unpleasant but harmless.

Every finding names its location – extension, file, line or position in the page tree – and an estimated effort in hours. That lets you have the list worked through by somebody else. This is explicitly intended and no loss to us.

Training

An editorial training session takes half a day, covers a maximum of 8 people and takes place on your own installation. More than 8 people means half of them only watch; on a demo installation you learn workflows that do not exist in your setup.

For developers there is the full-day counterpart: sitepackage structure, Content Blocks, Fluid, Extbase and the question of which of those a project actually needs. We have worked exclusively with TYPO3 since 2008 – the examples come from real installations rather than from the documentation.