Code of the site's own, and a slider that turns

Four things developers ran into in the last two weeks, and what 0.9.24 does about each.

"Write me a plugin for that"

Until now the agent could install and set up plugins from WordPress.org, and build a theme, but it had no way to write code on a site. Ask for a shortcode, a custom post type with its own archive, a small integration with a booking API, an admin page, and it could only describe what such a plugin would look like.

Now it writes one. A plugin of the site's own lives in wp-content/plugins/tb-<name>, with a proper header, everything prefixed, input sanitised, output escaped, a nonce on every form. Before a single file lands, every PHP file is parsed; a syntax error never reaches the site. A few functions no site plugin needs, eval and exec among them, are refused outright. Activation runs under a guard: an error while the plugin loads is caught and the plugin stays off, and right after activation the site fetches its own front page and REST API once. A critical error there switches the plugin off again and the message comes back in the answer, so the agent fixes the code and writes again.

Only plugins T-Builder wrote can be read back, replaced or removed this way. The plugins you installed yourself are never touched by any tool.

A slider that is a slider

A template's hero slider used to come out as its first slide, or as one frozen HTML block. Swiper, Slick, Owl, Splide, a hand-made one: the converter now reads the slides and builds T-Builder's new Slider widget, one repeater item per slide with the picture, the small line, the heading, the text and up to two buttons, with the template's type and colours. Autoplay, fade or slide, arrows, dots, swipe on a phone, arrow keys, pause under the pointer. No library on the page. A visitor who asked their system for less motion sees the slides standing still, with the arrows to turn them.

You edit the slides in Elementor like any repeater, and the widget travels with a theme package next to the Marquee band.

Three cards become a grid you can grow

Three feature cards, four team members, six services: a template repeats a card, and Elementor used to get one container per card. Adding a fifth meant copying a container and editing its parts. Now the converter recognises the repetition and builds one Items grid: a repeater with a picture or mark, a small line, a heading, a text, a line under it and a link per item, with the template's columns, gap, card colour, radius, shadow and type. The client adds an item in the widget, and it looks like the others.

Running animations stay where they are

A floating icon, a pulsing badge, a spinning mark used to turn the whole section into one HTML block, because Elementor has no control for keyframes. Now the section stays native and the animated element becomes its own widget, carrying the animation in the Motion panel's new "Running animation": the CSS shorthand and its keyframes, exactly as the template had them, editable, printed scoped to that one element and switched off for visitors who prefer reduced motion.

New things in the site's design

Ask for a new section, a post type, a widget or a form and you got the WordPress default look. That is over. The agent reads the site's palette, fonts and the page first, then builds in that design: the same headings, buttons, cards and spacing as the sections next to it. When the request leaves the look, the fields or the place on the site open, it asks one short round of questions with its own suggestion marked as the default; when you say "just do it", it takes the site's own defaults and tells you what it chose. When the request needs a design of its own, a landing page, a new page type, it asks T-Design for one in the site's look and converts it.

The T-Builder form now takes the Elementor kit's primary colour by itself, and the agent sets the rest of its style to the section it sits in.

Every site on the account updates itself to 0.9.24. The full list is under Releases.