Example order, TYPO3: A trade fair landing page and overdue extension updates on a corporate website

This article describes a fictional but typical order. The company does not exist; the process corresponds to the way the Eywora AI Crew works.

The starting point

A mechanical engineering company runs its corporate website on TYPO3 12 LTS, set up by an agency three years ago, with its own site package and around fifteen extensions. In two weeks the most important trade fair of the year begins. Marketing needs a landing page with programme, contact form and appointment booking, in German and English. A look into the backend also reveals that eight extensions have been offering updates for months, including the ones for forms and for image processing. The order to the AI Crew combines both.

Step 1: Set the order of work

The AI team lead proposes doing the updates first and the landing page afterwards, so that the new page is built and tested on the updated state right away. It also proposes not to include the move to TYPO3 13 LTS in this order. A jump to a new major version affects site package, extensions and templates at the same time and belongs in a separate project that signundsinn assesses and takes on at a fixed price if desired. The owner agrees to both.

Step 2: Extension updates on the copy

The website is managed via Composer, as is the standard for TYPO3 12. On the copy, the agent for integrations and systems updates the eight extensions and reads the changelogs along the way: two updates contain security fixes, one changes the configuration of the form extension. This change is carried over in the site package, not in the extension itself, so that the next update does not overwrite it. The automated tests then call up all pages of the website, submit a test form and compare the most important pages before and after the update for visible differences.

Step 3: The landing page

The page is built from the content elements the site package already provides: hero, text columns, programme table, form, buttons. Nothing is hard-coded into templates, so that marketing can adapt the page itself after the fair or reuse it for the next one. The agent for content writes a text draft from marketing's bullet points; the translation agent delivers the English version. Both are a draft, not finished copy: marketing proofreads and changes in the preview whatever it does not like. The appointment booking is linked to the calendar tool the company already uses. The designer checks the page on smartphone and desktop; the agent for security and privacy checks the form and the calendar embed.

Step 4: Preview, approval, go-live

Marketing receives the preview of the copy, corrects texts and the order of the programme and approves after two rounds. On Thursday the release manager creates a backup, deploys updates and landing page and checks the page on the live system. In this scenario, six working days pass from order to go-live, with enough buffer before the fair. Should one of the updated extensions cause problems in live operation, the signundsinn team rolls the update back; the landing page is unaffected because both are versioned separately.

What this example shows

Tasks that are left undone because individually they are too small for an agency quote can be bundled and done in one go, without the website taking a risk. And a good development team also says what it does not take into the order. Which TYPO3 versions are supported is in the system list; how copy, approval and rollback work together is in the article Copy, approval, backup, rollback.

← Back to blog