Agent assisted markup with QA gates before the editor at IOT

IOT builds and maintains its digital experience on Magnolia, with a corporate design system that defines how every component should look and behave.

Automating frontend development is tempting for the speed and dangerous for the same reason: code generated fast that reaches the editor unchecked turns an hour saving into technical debt.

The problem was not producing, it was producing without degrading.

• Enterprise standards: accessibility, performance and code conventions that are not optional.
• A design system to respect: a component that drifts is not noticed one at a time, it is noticed in aggregate.
• The editor as the point of no return: once a component is available to the editorial team, the error spreads across every page that uses it.
• Real time to market: the pressure to ship does not disappear because a standard exists.

A broken component looks exactly like a correct one until someone uses it.

We set up a pipeline where the agents produce the whole frontend, but deployment is conditional: the output is verified before reaching the editor, not after.

Modular component and theme architecture

• Structured generation of FTL and YAML templates.
• Markup of content blocks and stylesheets aligned with the IOT design system.
• The standard is not remembered: it is applied from the component definition.

Automated QA gates

• Strict validation of accessibility, linting, web performance and code conventions.
• The verification runs before deployment to the editorial environment, the point where the error would stop being reversible.
• If a component does not pass, it does not ship. There is no fast lane around it.

Assisted CMS integration

• Automated dialog registration and area configuration.
• Interactive components wired with headless support.

Continuous integration with traceability

• A full assisted development cycle with traceability at every step.
• Environment isolation and prior verification, so stability does not depend on a manual review in the editor.

Architecture and technology

• An autonomous agent pipeline on Magnolia generating FTL, YAML, blocks and themes.
• Accessibility, linting and performance gates wired into the continuous integration flow.

Learn more about AI agents, software development and Magnolia CMS.

Frontend development sped up without leaving the standard to the goodwill of whoever was in a hurry.

What is running

• Components, FTL and YAML templates and themes generated by autonomous agents, with 4 chained gates before the editor.
• Automatic accessibility, linting, performance and convention gates before the editor.
• Automated dialog registration and area configuration.
• Full traceability of the assisted development cycle.

What changes in governance

• Meeting the standard stops being a review and becomes a deployment condition.
• The editorial team receives components that already passed the control, so it does not have to catch it.

Why it matters

• It is the concrete answer to the most common objection about AI in development: that it generates fast and leaves the team cleaning up.
• Here the generation is not the deliverable. The deliverable is the generation that passed the gate.