Your videos can now talk. Pick a voice, describe how it should sound in plain words ("warm, unhurried, slight British accent"), edit the lines it reads, and the video is rebuilt around the recording — every scene is exactly as long as the words it carries, so picture and voice can never drift apart. The voiceover is included automatically in MP4 and WebM exports. **Where:** Creative Studio → brand → Motion Video → open a video → Voiceover **How to test:** 1. Open a generated video and expand Voiceover. 2. Pick a voice and hit Preview voice — a short sample plays, free. 3. Add a direction like "calm, slower on the last line", edit the lines if you want, then Create voiceover. 4. Each line appears as a clip you can play back, with its length shown. 5. Click Regenerate — the video is rebuilt so each scene matches its line. 6. Export MP4 and confirm the voice is in the downloaded file. **Watch for:** a line so long it can't fit the video's length (you should get a clear "shorten this line" message, never clipped audio); exporting without regenerating first (the panel should warn you); GIF exports are silent by design.
Create short branded motion-graphics videos from a simple brief — our AI designs the animation from your brand's colors, fonts, logo and assets, you preview it with play/scrub controls, and export a real MP4, GIF, or WebM file rendered on our servers (no screen recording). **Where:** Creative Studio → open a brand → "Motion Video" (also reachable from any Creative Studio workspace header). **How to test:** 1. Open Creative Studio, pick a brand, click "Motion Video". 2. Choose a format (try Vertical 9:16), set duration (~10s), pick "Promo", enter a key message and optionally 2–3 text beats and a CTA. 3. Optionally upload a logo/product image and assign it a role. 4. Click "Generate video" — progress phases stream in; expect under a minute. 5. Preview should play with working scrub, loop, and restart controls. 6. In Export, queue an MP4. The row appears as "pending" → "rendering" → "done" (requires the render runner; allow a few minutes), then Download and play it. 7. Try a GIF export on a ≤15s video; confirm GIF is disabled with an explanation on longer videos. **Watch for:** generation failing after the repair round (project shows a "didn't come out" card — Try again should work); a preview that never leaves the spinner (timeline never registered); exports stuck in "pending" (runner not draining); credit balance not decreasing (1 credit per generation, per-format pricing on export); the vertical preset rendering letterboxed instead of portrait.
You can now tell a finished video what to change in plain language — "make the headline bigger and switch to a dark background" — and it gets rebuilt around that change, keeping everything you didn't mention. You can also edit the brief of an existing video instead of starting a new one. **Where:** Creative Studio → open a brand → "Motion Video" → open a video. "Change something" sits under the preview; "Edit brief" is in the header next to Duplicate brief. **How to test:** 1. Open a video that already has a preview playing. 2. In "Change something", type "make the headline bigger" and press Enter (or click Apply change). Progress phases stream in; the preview reloads with the new version when it finishes. 3. Confirm the rest of the video is untouched — same copy, colours, timing, images — apart from what you asked for. 4. Confirm the change appears as a chip under "Recent changes", and that one credit was deducted. 5. Try a second change that builds on the first ("now slow down the ending") and confirm the first change survives. 6. Click "Edit brief", change the key message or a text beat, and Save. The summary updates and a "Brief saved" bar offers Regenerate — saving alone must NOT rebuild the video or charge anything. 7. Click Regenerate from that bar and confirm the new video reflects the edited brief. **Watch for:** a change that quietly redesigns things you didn't ask about; the preview still showing the old version after a change (it should reload itself); Export or Regenerate being clickable while a change is still running; a failed change replacing your working video (it should be left exactly as it was, with a "try describing it a different way" message and no credit charged); the format or length tier appearing editable in "Edit brief" (they are fixed — that's what Duplicate brief is for).
Longer motion videos (six to eight scenes) or ones that hit a slow AI provider could stall and fail outright instead of finishing. Generation now gives these runs enough time to complete, recovers cleanly instead of dying mid-run when a scene stalls, and — thanks to a recalibrated effort setting — typically finishes noticeably faster than before. **Where:** Creative Studio → Motion → generate or refine a video **How to test:** Generate a longer, multi-scene motion video. It should complete without stalling, and finish in roughly a third of the time compared to before. **Watch for:** A generation that hangs indefinitely, dies without a clear error message, or a composition using a `<link rel="preconnect">` tag that gets rejected and forces an unnecessary retry.
Long, multi-scene videos — or ones that hit a slower AI provider along the way — could run out of time and fail even though they were still making progress. Generation now has a longer runway to finish. **Where:** Creative Studio → Motion → generate a video **How to test:** Generate a long, multi-scene video (6-8 scenes). It should complete instead of timing out partway through. **Watch for:** A long generation that still fails to complete within the new time budget.
Your video now plays as one video. Press play and it runs start to finish — with the voiceover — instead of showing you a pile of separate scenes to click through. Scrub anywhere and the picture and the voice move together. New videos also ask about a voiceover *before* they are built, so every scene is held exactly as long as the line it carries rather than needing a rebuild afterwards. **Where:** Creative Studio → brand → Motion Video **How to test:** 1. Create a video from a suggestion — it should land on "Ready to build" and offer a voiceover rather than starting immediately. 2. Add a voiceover (or choose "Build it silent"), then build. 3. Press play — the whole video runs through, with sound if you recorded one. 4. Drag the scrubber across a scene change: picture and voice stay together. 5. Mute/unmute, loop, and restart should all behave like a normal player. 6. Open "Scenes" below to rebuild a single cut if you want one changed. **Watch for:** a white flash at a scene change; the voice drifting out of sync after scrubbing or after leaving the tab; sound not starting after the first play press; the last line not playing (record the voice, then rebuild).
Opening Motion Video now greets you with ready-to-go video ideas drawn from your own site — real headlines, your palette, different formats and goals — each one click from generating. Prefer to describe it yourself? A chat box turns what you say into a complete video plan (it asks at most one question), and recognizes when you actually want captions on your own footage and takes you there. The detailed form is still one click away and remembered as your preference. "Caption a video" is now visible in the workspace header too. **Where:** Creative Studio → brand → Motion Video → New video **How to test:** 1. Open Motion Video from a site context — 3–4 suggestion cards should show real copy from that site within a few seconds. 2. Click a card — a project is created and generation starts immediately. 3. Type "a 10 second teaser for our pricing page" in the chat — expect a proposal card (or one clarifying question at most), then Create this video. 4. Type "add subtitles to a clip I recorded" — expect it to point you to the captions flow. 5. Click "Use the detailed form instead" — the old form appears and stays your default until you switch back. **Watch for:** suggestions inventing prices/claims that aren't on the site; duplicate-looking cards; the chat asking more than one question; the captions entry not preserving your site context.
When you open Motion Studio from a site, a "From your site" panel now lists your pages and sections — pick one and the video brief fills itself with that section's real headlines, imagery, colors and fonts, ready to generate. **Where:** Creative Studio → Motion Video (entered from a site context) → New video → "From your site" panel. **How to test:** 1. Open Motion Studio from a site (site context in the URL). 2. In the new-video form, expand "From your site" and pick the Home page or a section. 3. The message, text beats, assets and style should fill with the site's real content — brand palette swatches appear in the brief summary. 4. Edit anything you like, then Generate; the video should visibly match the site's look. **Watch for:** beats containing form-field labels or ID-like junk; images that fail generation checks; empty seeding on sites without a design (a notice should explain); "Start blank" not clearing seeded fields.
The fast, low-cost pass that finds natural gaps between spoken lines almost never fired, so every video quietly paid for a slower fallback pass instead. It's fixed to actually catch the obvious cases now, and a second check now double-checks every cut lands in real silence, not mid-word. **Where:** Creative Studio → Motion → generate a video with voiceover **How to test:** Generate a multi-scene video with a voiceover script. Scene cuts should consistently land in the natural pause between lines. **Watch for:** A voiceover cut that clips the end of a word or starts a line noticeably late.
Scene cuts in a generated video's voiceover could land mid-word or mid-sentence, especially when one line was read quickly and the next was read slowly, or when a dramatic pause inside a line was wider than the actual gap between lines. **Where:** Creative Studio → Motion → generate a video with voiceover **How to test:** Generate a multi-scene video with a script that has both terse and long, dramatic lines. Play it back — each scene cut should land in a natural gap between lines, never mid-word. **Watch for:** A scene cut that clips off the end of a word or starts a line late.
Some Motion Video exports and caption burn-ins used to fail outright while combining video segments. That underlying rendering crash is now fixed. **Where:** Creative Studio → Motion Video → Export / Captions **How to test:** Generate a multi-scene Motion Video and export it, and separately generate captions on an uploaded video — both should complete without failing partway through. **Watch for:** An export or caption render that fails immediately with no progress at all.
Vertical (9:16) and other non-landscape Motion Video previews used to render into a boxed landscape frame with scrollbars, showing only one corner of the actual video. Previews now scale to fit their true aspect ratio, so the whole frame is visible at once. **Where:** Creative Studio → Motion Video → project preview (and the captions overlay preview) **How to test:** Open a 9:16 Motion Video project and look at the preview player — it should show the full vertical frame with no scrollbars or cropping. Captions overlay should stay aligned with the video underneath. **Watch for:** Any preview aspect ratio still showing scrollbars or a cropped corner.
Motion Video generation is more resilient and gives you more control: a stuck generation now recovers automatically instead of spinning forever, you can stop a run in progress, retry a failed run with a note about what to change, and finished scenes in a multi-scene video now appear as soon as they're ready instead of only after the whole project finishes. **Where:** Creative Studio → Motion Video → a generating or failed project **How to test:** Start a multi-scene Motion Video and watch the scene strip — completed scenes should appear while later ones are still generating. While a project is generating, click Stop and confirm it settles cleanly. On a failed project, retry with an optional note and confirm the note is applied to that run only. **Watch for:** A project stuck on "Designing the motion" for more than a few minutes, or the Stop button not settling the project state.
When a video's design calls for a photo or illustration you didn't upload, we now create it for you, on-brand, and it is saved permanently with the video instead of being left as an empty frame. **Where:** Creative Studio → Motion → open a video → Generate (or make a change from the refine box) **How to test:** Create a video with a brief that has no images — for example "promo for a late-night ramen bar, moody, neon" — and generate it. If the design needs a visual, the progress list shows "Creating the artwork it needs" and the finished video plays with a real image in place. Uploading your own assets in the brief still wins: with a hero image attached, the video should use yours rather than making a new one. Refine the video afterwards ("make the headline bigger") and confirm the image stays exactly the same. **Watch for:** A video is limited to two created visuals, and never a logo — a logo comes from your brief or the video stays typographic. Each created visual costs 1 extra credit on top of the video, charged only if the video finishes successfully; the total is shown before you spend it if your balance is short. Nothing should ever render as a blank or broken image — if the artwork can't be made, the run fails and you are not charged.
The newsletter and exit-intent popups can now be closed with their × button while you are working in the site editor, instead of sitting over your page with no way to dismiss them. **Where:** Site editor → any page with a Newsletter popup or Exit popup placed under Site Elements **How to test:** Open a site that has the Newsletter popup element, look at the canvas in either Edit or Preview mode, and click the × in the top-right of the popup card. The popup disappears. Click anywhere else on the page behind it and your click still selects the element underneath, as before. **Watch for:** The popup reappears when the editor preview reloads — that is expected, since the element is still placed on the site. Remove it from the Site Elements list in the left rail to take it off the page for good.
If you clicked a link while your site was still being set up, the editor said the page had been removed or renamed — even though it was being created at that moment. It now tells you the page is still being built and opens it automatically the second it's ready. **Where:** Site editor, right after you build a design (the canvas preview) **How to test:** Build a design, and while the "Building your site" step is still running, click a navigation link or a hero button such as "Shop Now". You should see "… is still being built", and the page should open on its own once it finishes. In a design you haven't built yet, the same click now explains the page gets created when you build, with a button to start. **Watch for:** The greeting in the chat panel should say your site is still being set up while pages are being created, and only say "Your site is ready" once it is. A link that genuinely has no page behind it should still warn you — but it should never claim the page was renamed or removed.
Editing a site's content or business details before a design exists — for example pasting in text carrying stray invisible characters — could fail to save with a generic "Failed to update" error, silently losing the edit. **Where:** Site editor → planning-stage content/business edits, geo-variables, and finalization **How to test:** On a site still in planning (no design generated yet), paste text containing invisible/control characters (e.g. copied from a PDF or old document) into a content field and save. The save should succeed with the visible text preserved. **Watch for:** A "Failed to update blueprint" error, or an edit that appears to save but reverts on reload.
Cleaning dead footer links could remove the site's own Privacy Policy or Terms link when the footer pointed at it by a different address (for example "/legal/privacy" instead of "/privacy-policy"). Those links are now corrected to the page the site actually publishes, and compliance links of any kind — cookies, GDPR, accessibility, Impressum — are never removed automatically. **Where:** Any generated site — the small legal row at the bottom of the footer, on every page. **How to test:** Generate a site, open the editor preview, and check the footer's legal row. Privacy Policy and Terms should still be listed, and clicking each should open that page (they are created when you publish). **Watch for:** A legal row that lost an entry, or a Privacy/Terms link that still lands on the not-found screen after publishing.
Asking the editor to make a selected heading bigger no longer shows a false "Applied" when the size never actually changed. **Where:** Site editor -> Edit mode -> select an element -> refinement chat **How to test:** Select the hero headline, send "Make this bigger." When the AI can't actually apply a larger size, it now says so and asks you to rephrase, instead of showing a success message and an Undo for a change that never landed. **Watch for:** Genuine size changes should still apply and report success normally.
Asking the AI to "increase the font size of all the body text" now changes the real text sizes instead of quietly editing a global rule that the page's fixed size classes override — and if it can't produce a visible change, it says so rather than reporting a false success. **Where:** Site editor → refinement chat (design/preview panel) **How to test:** Open a site whose paragraphs use Tailwind size classes, ask "Increase the font size of all the body text across the whole page", and confirm the paragraph sizes visibly grow (or you get an honest, actionable message). **Watch for:** A "✅ Increased the global body font size…" reply where nothing on the page actually changes — that specific false-success is what this fixes.
Asking the assistant to make a single selected piece of text bigger or smaller now reliably changes only that piece, instead of sometimes scaling everything around it. **Where:** Site editor → select any text element → the chat panel next to your design preview **How to test:** 1. Open a site in the editor and click a single heading to select it. 2. Ask: "Make this bigger." Note the phrasing — no need to say "font size". 3. Only that heading should change size. Its sibling text, the buttons beside it, and the rest of the section should be untouched. 4. Now try: "Make this section's main heading a bit larger, nothing else." Same result — mentioning the section should not widen the change. 5. Then ask for a deliberately broad change: "Increase the font size of all the body text across the page." This one *should* apply widely. **Watch for:** - A single-element resize that also changes sibling items, the surrounding container, or the whole section. - A request that says "all" or "across the page" that only changes one element. - Requests that are about fonts but *not* size — "use a serif font", "make the headings bolder", "change the text colour" — should still work normally and should not resize anything. - Asking why fonts don't match across sections should still produce a comparison-based answer.
Custom sections are saved automatically as you create them, so you can close the panel, come back later, and keep refining — and you can build a section around your own photos instead of describing one from scratch. **Where:** Site editor → select a section → Section Explorer → Library tab **How to test:** Under "Create Custom", add a few of your own photos, describe the section you want (for example "alternating photo and text rows"), and generate. The result appears under "My blocks". Use the Refine box to change it ("alternate the images left and right") and watch the revision number climb. Close the panel, reopen it, and click the block — your work is still there. Apply it to the page when it looks right. **Watch for:** A block that doesn't reappear in "My blocks" after reopening the panel, uploaded photos that don't show up in the generated section, or a Refine that returns something unrelated to what you asked for.
When your site was built, a "Shop" or "Collections" link in your menu could create a brand-new, empty catalog instead of listing the products you already had — leaving an empty page while your real products had no page at all and product cards on the homepage led nowhere. **Where:** Building a site from a design (the "Build my site" step), on stores and other catalog sites **How to test:** Build a design whose menu links to more than one catalog route (for example both "Shop" and "Collections"). Each page should list your actual products, and clicking a product card on the homepage should open that product's page. **Watch for:** Every catalog page in your menu should show real items. An empty catalog page, or a product card that goes nowhere, means a route didn't connect to the right catalog.
The building screen now finishes on its own even if the final "done" signal from the server is lost, so you no longer see the progress bar freeze near the end after your designs were actually ready. **Where:** The "Building your site… NN%" screen at the site builder (`/client/<client>/site/<site>/design`). **How to test:** Start a generation and watch the progress screen through to the end. It should transition to your finished designs automatically, without needing a manual page reload. **Watch for:** A progress bar that sits at a high percentage for more than a minute after the designs exist — it should now resolve to the finished builder within about a minute instead of hanging.
You can now label images when bulk-uploading them in chat, and the assistant automatically tags what each image is (headshot, screenshot, etc.) and can place them into specific sections or pages by name, with a preview before anything is applied. **Where:** Site editor → assistant chat → attach or bulk-upload images **How to test:** Upload several images at once with labels, then ask the assistant to place a specific labeled image into a section. It should show a confirmation preview before applying, and the placement should be undoable. **Watch for:** Images landing in the wrong section, or a label not carrying through to where the assistant references it.
Generated creatives were sometimes rendering your brand name or website name into the picture itself — often misspelled — instead of leaving the image clean for the copy layer that gets added on top. **Where:** Creative Studio → Social planner → "Create visual", and Brand Studio → Create **How to test:** Plan a social post, click "Create visual" on a text-style post, and generate. The finished image should be a clean photograph or graphic with no lettering anywhere in it; your headline, supporting line and call to action appear only in the composited copy layer. **Watch for:** Any lettering inside the artwork — a name painted on a wall, writing on a whiteboard or notepad, or readable labels on a screen in the scene. Concepts built around whiteboards, sticky-note walls or printed pages should no longer be proposed at all.
Shops built with a cart used to look finished while their Checkout button did nothing and some product links led nowhere — and nothing flagged it. Those routes are now created when the site is built, dead links are caught before you see them, and a page that doesn't exist says so instead of quietly showing the homepage. **Where:** Any site with products — open it from your client's site list and click through the preview. **How to test:** 1. Build a store site that has products. 2. In the preview, click a product card — you land on its detail page, or on a clear "isn't built yet" message naming the route. You should never land on the homepage under a product URL. 3. Add something to the cart, open the cart, click **Checkout** — the checkout page opens in the preview, before you publish anything. 4. Click through several pages in a row (Shop → a product → back). The address in the bar stays clean. **Watch for:** A URL that repeats a section name (`/shop/shop/...`) — that was the old bug and should not appear. Also watch for a Checkout button that closes the cart panel and does nothing; if you see either, note the exact click order that produced it.
Upload a clip, get captions, and now get a short list of suggested graphics on top of them — a number from the script called out big, a key phrase punched on screen, an opening title, a closing call to action, a lower-third highlight, or your logo in the corner. **Where:** Creative Studio → Motion → Captions → open a captioned video → after the words are written out, "Suggested graphics" **How to test:** 1. Open Creative Studio → Motion → Captions and upload a short clip with someone speaking. Include a sentence with a number in it ("we cut it by half", "53% faster"). 2. Wait for the words to be written out and the preview to appear. 3. Click **Suggest graphics** (1 credit). A few seconds later the graphics appear in the player and a list of them appears underneath. 4. Play the preview — each graphic should land on the moment it refers to, above the captions rather than on top of them. 5. Switch one off with its toggle. The preview rebuilds without it. 6. Click the pencil on a row, change the wording, Save. The preview rebuilds with the new text. 7. Export the video with captions — the graphics are baked into the exported file exactly as previewed. **Watch for:** a graphic overlapping the caption band instead of sitting above it; a graphic landing seconds away from the line it refers to; a number that was never said in the clip; a suggestion list that does not match what the player shows after a toggle; the logo graphic appearing when the brand has no logo; the export coming out without the graphics you can see in the preview.
The editor toolbar now shows every version of the page you're on (Original, V2, V3…), so you can flip between them, delete one, or create another without going back to Mission Control. **Where:** Site editor → toolbar, next to the page name. **How to test:** Open a site whose page has an alternative version (or ask the chat to "create an alternative version of this page"). The Original / V2 tabs appear in the toolbar — click between them and the canvas swaps to that version. The version you leave selected is the one that gets published. **Watch for:** The tabs only appear once a page actually has an alternative version. Switching saves your choice, so a reload should come back on the same version.
When an action failed, the site assistant sometimes repeated a raw technical error back to you — in one case reading an internal maintenance instruction out loud during a voice session. Failures are now explained in plain language, and voice checks whether an action applies to your site before attempting it. This now covers every assistant action, not just the ones that failed outright: around 110 messages across pages, forms, publishing, contacts, collections, analytics and images used to end with the underlying technical error, and each now names what failed and what to try next. Background failures that appear as a pop-up notification (such as creating several pages at once) are covered too. **Where:** Site editor → AI assistant (chat and voice), plus failure pop-ups **How to test:** In a site that has not been generated yet, ask the voice assistant to update the menu or page SEO. It should say the action isn't available yet rather than reporting an internal error. On a generated site, the same requests should work exactly as before. **Watch for:** A failure message that mentions file names, database terms, or steps meant for our team — none should appear. Also confirm genuinely useful messages still come through, e.g. asking to edit a page that doesn't exist should still name the pages that do.
If a design refinement failed partway through, your message could sit in the chat with no reply at all — and disappear on reload, as if the assistant had ignored you. Every refinement turn now always ends with a response, including an honest "something went wrong, please try again" when a change can't be applied. **Where:** The design assistant chat in the site editor. **How to test:** Send a refinement request; on any server-side failure you now see a clear failure reply in the chat instead of silence, and it survives a page reload. **Watch for:** A turn that shows your message with no assistant reply — that specific silent state should no longer happen.
Asking the assistant for something open-ended like "add a template catalog for my business" now reliably asks where it should live and whether it should be a managed collection, instead of quietly picking one and building it. The assistant also stopped losing its editing abilities on short requests that happened to mention a section name. **Where:** Site editor → assistant chat. **How to test:** Send "Add a template catalog for my business." The assistant asks a clarification before anything is created or changed. Then send "add a video section" — the assistant should actually make the edit rather than only offering to navigate. **Watch for:** A catalog, collection or page being created with no question asked first; or the assistant replying that it can only take you somewhere when you clearly asked for a change.
Video voiceovers are recorded as one continuous read instead of line by line, so the delivery carries across sentences the way a real narrator's does — plus 30 voices, accent options, and inline direction for individual moments. **Where:** Creative Studio → any motion video → the Voiceover panel under the preview. **How to test:** 1. Open a video project and scroll to Voiceover. 2. Pick a style under Recommended, or open "All voices" and choose one of the 30 by name — each shows what it sounds like. Preview is still free. 3. Set Language & accent if you want a specific accent (British, Australian, Indian English, Spanish for Spain or Latin America). The script's own language is detected automatically. 4. Write two or more lines and try a delivery tag inside one — open "Direct a moment inside a line" for the syntax, e.g. `[whispers] Just between us.` or `We cut your setup time [very slow] in half.` 5. Record, then play the clips back: the lines should sound like one take, with emphasis building across them rather than resetting at each line. 6. Regenerate the video and confirm the tag never appears as on-screen text. **Watch for:** a line whose audio is cut short or runs into the next one; a delivery tag showing up as visible type in the finished video; a voice from the "All voices" list failing to preview; an accent choice that doesn't change the read.
Asking the editor chat for an alternative version of a page could report success while nothing was created; the request is now honoured, and a genuine failure says so instead of pretending. **Where:** Site editor → chat → ask for a big copy or layout rewrite → "Create alternative version" **How to test:** Open a page in the editor, ask the chat for a comprehensive rewrite of the page's copy, choose "Create alternative version", then "Current design". The canvas switches to the new version when it's ready, and your original stays untouched under the Pages tab. **Watch for:** A success message with no new version behind it, or a failure that appears as silence.
A plain request to rewrite the wording across the page while keeping the design untouched now applies immediately instead of interrupting you with a "replace vs create alternative" choice prompt. **Where:** Site editor → refinement chat **How to test:** On an existing site, send "Rewrite the copy across the page to be punchier, but keep the design, layout, images and colours exactly as they are." The assistant should rewrite the text directly and tell you what it changed — no choice prompt. **Watch for:** Requests that explicitly ask for an *alternative version to compare* should still offer the "Create alternative version / Replace the current copy" choice.
Requesting a built-in feature (like a managed template catalog) while a specific section was selected could unexpectedly create a whole new page instead of updating the section you were pointing at. Selecting a section now keeps the change scoped to that section unless you explicitly ask for a separate page. **Where:** Site editor → select a section → assistant chat **How to test:** Select a section on the page, then ask the assistant to add a built-in feature to it (e.g. a managed template catalog). Confirm the feature is applied to the selected section, not moved to a newly created page. **Watch for:** A section-scoped feature request resulting in a brand-new page instead of an update to the selected section.
Asking to replace a selected section with Mondovo's live template gallery could get misread as a request to set up your own separate, empty template catalog — leading to an unnecessary setup question instead of just showing the real, live gallery in place. That request is now recognized correctly and binds the actual gallery data into the section you selected. **Where:** Site editor → select a section → assistant chat **How to test:** Select a section, then ask the assistant to "replace this with Mondovo's live template gallery." Confirm it shows real gallery content in that section rather than asking whether you want a managed template collection. **Watch for:** A request for the live/real gallery instead triggering a "set up your own collection" clarification question.
While comparing designs, asking the assistant "will I lose my other designs if I build this one?" now gets a clear, correct answer: building creates a new working site from your chosen design, and all your other designs stay saved and available from the Designs tab. The "Build my site" button and the Site Planner screen also now say this directly, so you don't have to ask. **Where:** Site editor → Designs view → assistant chat, and the Site Planner screen shown before building **How to test:** While viewing multiple designs, ask the assistant what happens to the other designs if you build one. Also open the Site Planner (via "Build my site") and check for the reassurance note near the top. **Watch for:** The assistant hedging or guessing about whether other designs are lost when building.
Buying, booking, or subscribing on a published site can now complete in an inline checkout form instead of sending visitors away to a separate hosted payment page — fewer steps, less chance of losing the sale. **Where:** Any published site with card payments enabled — cart, checkout, booking, digital product, subscribe/pay buttons, or funnel upsell. **How to test:** Open a published site with Stripe payments configured and start a purchase or booking. The checkout form should appear inline on the page rather than redirecting to a separate Stripe-hosted URL. **Watch for:** A purchase attempt still redirecting away, or the inline checkout form failing to load/submit.
The secure-payment pop-up on cart, checkout and booking sections showed its heading in English even on sites built in another language. It now uses the site's language like the rest of the page. **Where:** Any published site with a cart, checkout, or booking deposit — open the section and start a payment. **How to test:** Publish a site in a non-English language, add an item to the cart and start checkout. The pop-up heading and its screen-reader label should be translated, not "Complete your order". **Watch for:** A payment pop-up that still opens in English, or a heading that renders blank instead of translated copy.
While comparing designs, clicking a navigation link for a page that particular design doesn't include used to either silently generate a one-off preview that disappeared on reload, or show a misleading "page may have been renamed or removed" message. It now shows honest copy explaining the design simply doesn't include that page yet, with an "Add page & build" action that takes you straight into the build flow for it. **Where:** Site editor → Designs view → clicking a nav link **How to test:** While comparing designs, click a nav link (e.g. "Blog" or "Pricing") that the current design variation doesn't have a page for. Confirm you see "Design N doesn't include this page" with an "Add page & build" action, not a "renamed or removed" warning. **Watch for:** A missing-page click still triggering a one-off AI-generated preview or the old "renamed or removed" wording.
After setting up a catalog-style collection (like products, rooms, or listings), the actual listing page could end up missing even though links to it existed elsewhere on the site — leaving visitors clicking into a dead end. Declared collections are now reliably built out into real pages. **Where:** Site editor → sites with a catalog-style content type (products, rooms, listings, etc.) **How to test:** Set up a site with a catalog collection (e.g. a products or rooms listing) and confirm the listing page (e.g. /products) exists and any links to it work, immediately after generation. **Watch for:** A CTA or nav link pointing to a collection listing page that returns a missing-page error.
Picking a section in the Structure rail and then asking the assistant to connect a live data feed to "this section" now targets that exact section, instead of asking you which one you meant or wiring the feed into a different one. **Where:** Site editor → Structure rail (left) → click a section → chat panel on the right **How to test:** Open a site's editor without switching to Edit mode. Click a section in the Structure rail — a chip naming that section appears above the chat box. Ask the assistant to connect a public JSON feed to it. It should go straight to that section. **Watch for:** The chip should name the section you clicked; clicking the × next to it clears the selection so your next message is unscoped.
Asking the assistant to rewrite your website copy no longer overwrites your original wording without asking, invents facts about your business, or quietly restyles a design you asked it to leave alone. **Where:** Site editor → the chat panel next to your design preview **How to test:** 1. Open a site in the editor and ask: "Give me an alternative version of all the copy — rewrite every headline and CTA, but keep the design exactly the same." 2. You should be offered a choice before anything changes: **Create alternative version** (keeps your current copy for side-by-side comparison) or **Replace the current copy**. 3. Pick either one. When it finishes, check that the colours, spacing, images and layout are identical to before — only the words should have moved. 4. Now ask a question instead: "I'm not sure about some bits — what would you suggest improving?" The reply should list the actual suggestions in the message itself, not just as buttons. 5. If the assistant proposes copy and offers to apply it, there should be an **Apply these changes** button — you should never have to retype its suggestion. **Watch for:** - Any headline that loses a concrete credential, number, date or named award ("Founded by McKinsey Partners", "Since 1985", "Rated 4.9 by 300 customers"). These should survive a rewrite — rewording around them is fine, replacing them with vague phrasing is not. - Facts in a suggestion that you never told us — invented founding dates, wine lists, class schedules or prices. The assistant should ask you for a fact it doesn't have rather than supply one. - A copy-only request that changes anything visual. - A reply that ends on a colon with nothing after it. - Requests that ask for both wording *and* a visual change ("rewrite the hero and make the heading bigger") should still do both.
Deleting the design you were currently looking at used to leave the deleted design on screen until you manually refreshed, with no confirmation it worked. It now switches you to the previous design (or the original, if it was the first one) right away and shows a success message confirming the switch. **Where:** Site editor → Designs view → delete a design from the toolbar **How to test:** Open the design you're currently viewing and delete it from the preview toolbar. Confirm the canvas immediately switches to the previous design (or Original) and a "Design deleted" toast appears. **Watch for:** The deleted design still showing on screen after deletion, or no confirmation toast appearing.
When describing a new design variation in chat, a later message about layout or visuals only could silently reset an earlier decision about rewriting site-wide content — dropping the "apply this rewrite to the site" checkbox and the explanation text along with it. That choice is now preserved for the rest of the conversation unless you explicitly change it. **Where:** Site editor → "Describe a new design" chat **How to test:** In the describe-a-design chat, get a suggestion that recommends a content rewrite, then send a follow-up message about layout only. Confirm the "Apply this content rewrite to the site baseline" option and its explanation are still shown as before. **Watch for:** The baseline-rewrite checkbox or its explanation disappearing after a follow-up chat message.
Chat-based design edits that regenerate a whole section now skip redundant follow-up passes, roughly halving how long a big edit takes. Along with that, a bug where a wrapper component silently dropped a background color — leaving white text on a light background — is now automatically caught and repaired. **Where:** Site editor → assistant chat (design edits/refinements) **How to test:** Ask the assistant to substantially restyle a section and confirm it comes back noticeably faster than before. Check any section with colored panels/cards for readable text against their backgrounds. **Watch for:** White or light-colored text sitting on a light background (unreadable), or a large edit taking unusually long to complete.
Asking the site assistant to add certain built-in features (like a template catalog) could sometimes get a generic, unhelpful reply instead of the proper setup questions. Those requests now always go through the same feature-setup flow, so you get the right prompts every time. **Where:** Site editor → assistant chat / Site Planner **How to test:** In the editor chat, ask to add a runtime feature such as a template catalog or booking flow. You should get a relevant setup question (e.g. managed vs. simple collection), not a generic "here's how to plan a page" response. **Watch for:** A feature request that gets brushed off with generic planning advice instead of a specific setup question.
Selecting a section or element in the editor no longer leaves a blank, frosted rectangle hovering at the bottom of the preview — the multi-select tip that lives there is now readable. **Where:** Site editor → open a page → Edit mode → click any section or element in the preview **How to test:** Click a single element inside a light-coloured section. The tip at the bottom centre of the preview should read "Hold Ctrl + click to select multiple" in dark text on a light pill with a visible edge. **Watch for:** The tip disappearing entirely, unreadable text on dark sections, or the pill overlapping the "Swap design" button beneath it.
The design redesign preview and apply actions were erroring out on sites that had already been built out, because the site's design data wasn't being fully loaded before the redesign ran. **Where:** Site editor, redesign flow (preview a new design, then apply it) **How to test:** Open an existing site with generated pages, start a redesign preview, then apply it. Both should complete without an "internal server error". **Watch for:** Any "missing files" error during redesign preview or apply.
When the builder splits a generated page into separate pieces (like a footer or contact block), a piece could end up referencing a business detail — such as a phone number — that was only set up in a different piece, causing that section to fail to render. Those references are now automatically repaired during generation. **Where:** Any generated or redesigned site, especially footer/contact sections **How to test:** Generate or extract a new design and check that the footer and any contact-details sections render normally with the real phone/email/address instead of erroring out. **Watch for:** A section (commonly the footer) appearing blank or throwing an error where business details should show.
Pasting certain image or video URLs into the image replace tool could leave it spinning on "Detecting..." forever with no way to continue. It now falls back automatically after a few seconds so you can still use the link. Visual quality checks also now catch images that loaded but are actually blank or crushed to solid black. **Where:** Site editor → any section → replace image **How to test:** Open the image replace modal and paste a direct media URL from a host that doesn't return clear image/video info. Confirm the preview resolves within a few seconds instead of staying on "Detecting..." indefinitely. **Watch for:** The replace modal staying stuck on "Detecting..." with no preview or error shown.
The generation check that catches content mismatches — like a page referencing business details in a way that doesn't match how they're actually stored — used to only look at the homepage. Secondary pages (like a services or treatments page) are now checked the same way, so mismatched content on those pages gets caught during generation instead of shipping broken. **Where:** Multi-page generated or redesigned sites **How to test:** Generate a multi-page site and open its inner pages (not just the homepage). Content should be consistent and correctly bound rather than showing garbled or mismatched values. **Watch for:** An inner page (not the homepage) showing content that doesn't match the site's actual saved details.
Clicking an internal link in certain site previews stopped navigating to the target page — the click was being swallowed before the preview's own page router could handle it. Navigation is restored. **Where:** Site editor preview / demo preview (multi-page sites with a compiled router) **How to test:** Open a multi-page site preview and click a link that points to another page. The preview should switch to that page. **Watch for:** Clicking a link in preview doing nothing, or the page not changing.
A plain restyling request could sometimes get sidetracked into the assistant trying (and failing) to connect an external data source, coming back with "I couldn't find a way to pull that data in" and making no change at all. Those requests now go straight to the normal edit path. **Where:** Site editor → assistant chat (design edits/refinements) **How to test:** Ask the assistant to visually restyle a section (e.g. "make this section more visual" or "showcase this feature differently"). It should make the requested visual change instead of replying that it can't find the data. **Watch for:** A visual-only request answered with a message about not being able to pull in data, with no change applied.
On sites published in a language other than English, the secure payment window (and the wording around it) stayed in English. It is now translated along with the rest of the site. **Where:** Any published site page with a payment, subscription or booking deposit button, viewed in a non-English language. **How to test:** Publish a site in a non-English language, open it, and start a payment. The checkout window title, the "payments securely processed" line, the close button label and any loading error should all appear in the site's language. English sites are unchanged. **Watch for:** Mixed-language text inside the payment window, or a payment button whose window title falls back to English when the item has no description.
A section that pulled in some page content but was missing one setup line for another part — most often the footer's phone, email, address and social links — would fail to render and show an error card instead. The missing piece is now filled in automatically, so the real details appear. **Where:** Site editor preview, and any published page with a contact block (footer, contact section, location section) **How to test:** Open a site in the editor, view a design with a footer that shows phone/email/address and social icons. The footer should render with the real business details instead of an error card. Republish and confirm the live page matches. **Watch for:** A footer or contact block that renders empty rather than showing the saved phone/email/address — that means the details are missing from the site's content, not from the page code.
Navigating between pages inside a multi-page preview could drop preview-only settings (like which design variation or view mode you had selected) or lose a page's form configuration. Preview-only settings now stick around across page navigation while each page's own settings still apply correctly. **Where:** Site editor preview / shared preview links (multi-page sites) **How to test:** Open a preview with a specific design variation selected, then click through internal links and hash anchors between pages. The selected variation/view mode should persist, and any forms on the destination page should keep working. **Watch for:** The preview resetting to a different design variation or view mode after navigating, or a form losing its configuration after a page change.
Choosing to add a managed template catalog to the page you're already on could previously fail to place it, leaving the page unchanged even though the catalog itself had been created. It now inserts correctly alongside the page's existing sections. **Where:** Site editor → assistant chat (adding a template/product catalog) **How to test:** Ask the assistant to add a template catalog to the current page. A new catalog section should appear on that page without removing or replacing the sections already there. **Watch for:** The catalog being created but not showing up on the page, or an error saying no section could hold it.
When you ask the assistant whether building will lose your other designs, it now tells you exactly where to find them again — and it only brings the topic up while you are still choosing a design. **Where:** Site editor → assistant chat, on a site still in the design phase **How to test:** Open a site you are still picking a design for and ask "if I click build, will I lose my other designs?". The answer should reassure you that every design and variation is kept, and point you to the Designs button in a build's site header or the Concepts filter on your Sites dashboard. Then open a site you have already built and ask an ordinary editing question — the answer should stay on topic and never mention design preservation. **Watch for:** An answer that sends you to a "Designs tab" on the dashboard (there isn't one), or build-phase chat that volunteers reassurance about designs you are not currently choosing between.
Asking the site assistant to add a template catalog (or similar collection feature) now consistently asks whether it should be a managed collection or simple page content — instead of sometimes jumping straight to drafting a whole new page. **Where:** Site editor → assistant chat. **How to test:** Open a site and send "Add a template catalog for my business." The assistant should ask the managed-vs-simple (or current-page-vs-dedicated-page) clarification before drafting anything. **Watch for:** A drafted "Template Catalog" page appearing with no clarification first — that would be the old behavior returning.
Asking the assistant to add a template catalog could, in some cases, get intercepted by an older routing path before it reached the step that asks whether it should be a managed collection or simple page content — and even when it did ask correctly, reloading the editor could lose that question from the chat history. Both are fixed. **Where:** Site editor → assistant chat **How to test:** Ask the assistant to add a template catalog. It should ask the managed-vs-simple clarification. Reload the editor page — your message and the assistant's question should still be visible in chat. **Watch for:** The clarification question missing after a reload, or the assistant skipping straight to drafting a page without asking.
Buttons and links whose destination is filled in from page content (rather than typed in directly) were sometimes incorrectly flagged as non-functional during quality checks, which could trigger unnecessary "fixes." These are now recognized correctly as working links. **Where:** Site editor → Site Health / generation quality checks **How to test:** Generate or check a site with a call-to-action button whose link comes from page content (for example a "Book Now" button tied to a booking link). Confirm it is not flagged as a broken or placeholder link. **Watch for:** A visibly working button/link still showing up as "non-functional" in a health or quality report.
If a publish was interrupted, the site could stay stuck on "Publishing…" and refuse every retry for up to 20 minutes. Publishing can now recover on its own, so a second attempt works. **Where:** Site editor → Publish **How to test:** Publish a site. If a publish ever fails or is interrupted, click Publish again — it should start a fresh deploy rather than telling you one is already in progress. **Watch for:** A site that still reports "already being published" long after a failed attempt, or two publishes running at once on the same site.
When the design assistant offers a set of choices — for example, picking which design to base a change on — selecting one now reliably applies that exact choice instead of occasionally being treated as the answer to an unrelated question. **Where:** Site editor → design assistant chat **How to test:** Ask the assistant for a change that references another design (e.g. "make it look like design 2's header"), then click one of the options it offers and confirm it applies that specific choice. **Watch for:** A selected option not being applied, or being applied to the wrong earlier request.
Liking or disliking a design, adding a note, or marking one as the theme source could occasionally fail to save correctly and, in rare cases, unintentionally alter the design's code; grading now saves directly and safely. **Where:** Site editor → design gallery (👍/👎, notes, theme-source pin on a variation) **How to test:** On a site with multiple design variations, like/dislike a variation, add a note, and mark one as the theme source. Refresh the page and confirm all of it persisted and the design itself is unchanged. **Watch for:** A rating or note not persisting after a refresh, or a design's appearance changing unexpectedly right after rating it.
When a site reached its design variation limit, the oldest design was automatically removed to make space — even if it had already been reviewed and rated; rated designs are now protected from that cleanup. **Where:** Site editor → design gallery (variations) **How to test:** Rate or add a note to enough older design variations to fill the variation limit, then generate a new one — none of the rated designs should disappear. **Watch for:** A rated design vanishing from the gallery, or new variations failing to generate because every existing slot is already rated.
Large sites with many pages or images could hit a server time limit partway through publishing and fail; the publish process now gets more time to finish before that happens. **Where:** Site editor → Publish **How to test:** Publish a large site (20+ pages or many images) and confirm it completes instead of failing partway through. **Watch for:** A publish still failing partway through on an especially large site — this raises the limit but doesn't remove it; if it happens, publishing again should still succeed.
On larger sites the publishing progress bar used to freeze partway through and sit still until the site went live — the upload step reported nothing at all. It now advances as your pages are uploaded and shows the final "finishing up" stage. **Where:** Site editor → Publish (sites with more than 20 pages) **How to test:** Publish a site with 20+ pages and watch the progress indicator — it should keep advancing after the "rendering" stage instead of stalling, then finish. **Watch for:** A bar that stops moving for the whole upload, or one that jumps backwards to an earlier stage after the publish completes.
While a site was generating, a backup path could produce a second copy of one design and write it over the one that had already finished — so a design you had seen, and possibly rated, was quietly replaced by a different one under the same name. Generation now checks whether a design has already landed before writing, and any run that gets superseded discards its output instead of overwriting. This holds no matter how many designs a run produces, and it also covers starting a second generation on a site that is still busy. **Where:** Site editor → generate designs (including "add a variation") **How to test:** Generate a site with multiple designs, wait for all of them to finish, and rate one. Reload after a few minutes — the design you rated should be pixel-for-pixel the one you saw. Starting another generation while the first is still running is turned away with "generation is already in progress" instead of starting a rival run. **Watch for:** A design that visibly changes after it finished, a rating that seems attached to the wrong design, a preview that doesn't match the design after a reload, or a site stuck on "generating" that never completes.
Importing from another site now keeps your old links working, copies your images across, and cleans up leftover page-builder code — so switching doesn't cost you the traffic you already have. **Where:** Site editor → any collection → Import → WordPress, or a sitemap / single page URL **How to test:** 1. Open a site and go to a collection (Blog, Products, etc.), then choose Import. 2. Enter a WordPress site URL and run the import. Watch the progress: it fetches content, preserves the original links, then copies images. 3. Publish the site. 4. Visit one of the ORIGINAL URLs on your new domain (e.g. `/2019/03/some-post/`). You should land on the new page instead of a "not found" screen. 5. Open an imported post and confirm images load, and that there's no stray code like `[gallery]` or `<!-- wp:paragraph -->` in the text. 6. Try the two new sources: a sitemap URL (imports many pages from any platform) and a single page URL. **Watch for:** Images still pointing at the old site after import; original URLs showing "not found" after publishing; visible shortcode text or block comments in imported posts; a sitemap import that files whole pages under "Blog" instead of Pages; any redirect that bounces the browser in a loop or sends the homepage somewhere unexpected.
When the assistant replied with an explanation or a question instead of making an edit, the site editor could still refresh the preview or show an "updated" success message as if a change had been applied. Chat responses that don't actually change your site no longer trigger a refresh or a misleading success message. **Where:** Site editor → chat with the AI assistant (any refinement request) **How to test:** Ask a question that doesn't require a change (e.g. "what does this section do?") and confirm the preview doesn't refresh and no false "updated" message appears. Then request a real edit and confirm it still applies and refreshes normally. **Watch for:** A real edit failing to refresh the preview, or the assistant's response and the preview state disagreeing about whether something changed.
When the first of your three designs comes back malformed and can't be repaired, generation now automatically switches to the backup model instead of failing the run. **Where:** Site editor → Blueprint Wizard → Generate 3 Designs **How to test:** Start a fresh site generation from the wizard and confirm three designs come back. On a run where the first design's model has trouble, the design still arrives (produced by the backup model) rather than the generation erroring out. **Watch for:** A generation that stops with an "unparseable response" style error, or a run that returns only two designs when three were requested.
Generating a new site now produces three distinct design directions to choose from up front, instead of two — more variety to compare before you pick a starting point. **Where:** Blueprint Wizard → Generate Designs button **How to test:** Start a new site from a plan and generate designs. Confirm three designs come back instead of two, and the button reads "Generate 3 Designs". **Watch for:** Slower generation (more designs to produce), or fewer than three designs coming back on a run.
A closer look at last week's WordPress import turned up real bugs — some images could disappear entirely, legitimate text could get deleted along with leftover formatting, and old links could redirect in a loop or straight into a "not found" page. All fixed. **Where:** Site editor → any collection → Import → WordPress (or sitemap / single page URL) **How to test:** 1. Import a WordPress page that uses "lazy loading" for its images (most WordPress sites do) — the image should render, not disappear. 2. Import content containing bracketed notes like "[Editor's note]" or a code block — both should come through intact instead of being stripped. 3. Import a page whose old URL had already redirected once or twice before landing on its current address, then publish and visit the original URL — it should still land on the new page. 4. Check that no imported redirect points at a page that doesn't exist yet. **Watch for:** Imported items missing an image that clearly exists on the source page; content that reads like a sentence was cut off mid-paragraph; a redirect that loops or dead-ends in a "not found" page.
On some newly generated sites, the header's call-to-action button ("Get Started", "Book Now", etc.) could end up with no visible text because two internal systems disagreed on where the button's label was stored. **Where:** Site editor → header/navigation section, and the "Navigation" block editor **How to test:** - Generate a new site and check that the header CTA button shows its label text - Open the Navigation block editor and confirm the primary/secondary button text fields are populated and editable **Watch for:** Any header CTA button rendering blank, or the button text field in the Navigation editor appearing empty when a label was previously set.
A form that belongs to one of your alternate designs now loads its real fields in the editor and on the published site, instead of showing a red error box and publishing an empty form. **Where:** Site editor → switch to a design other than the first → any section containing a form **How to test:** Open a site with multiple designs, switch to Design 2 or 3, and check any form section. The form's own fields should render. Publish and confirm the live site shows the same fields. **Watch for:** A red "Form config missing" box, a form that renders only a Submit button with no fields, or a form defined on one design leaking into a different design.
Content import now works for any site with a sitemap, not just WordPress — and you can choose whether to bring in just the main pages or everything, instead of committing to a full crawl before you've seen the result. **Where:** Client portal → Pages → Import content → "Any other website" **How to test:** - Open the content import dialog and pick "Any other website" - Enter a site URL, choose "Main pages only" (the default) vs "Everything in the sitemap", and run the import - Confirm the progress log reports how many pages were imported out of the total found (e.g. "Importing the first 15 of 240 pages found") **Watch for:** Sites without a discoverable sitemap, or a sitemap depth setting that imports far more or fewer pages than expected.
Importing from another website now takes its own copy of every image, including the ones served from a separate image host — previously those stayed linked to the old site and would have gone missing the day it was switched off. **Where:** Site editor → any collection → Import → "Any other website" **How to test:** Import from a site whose images sit on a CDN (most WordPress, Shopify and Next.js sites do). When the import finishes, open an imported item and check the image address — it should be on your own site storage, not the source's. **Watch for:** An import that finishes reporting zero images copied even though the imported items clearly have pictures.
Importing content into a collection that already has a working detail page (like "Menu Items" or "Blog Posts") now creates the 301 redirects that point your old URLs to their new home, instead of silently skipping them. **Where:** Site editor → open a collection → Import → any source → Start import **How to test:** Import into a collection whose detail pages already render live, publish, then visit one of the original source URLs — it should 301-redirect to the new page instead of returning 404. **Watch for:** The "original links weren't preserved yet — this site has no page that displays … items" warning should no longer appear when the collection is already templated; the completion event should report a non-zero number of preserved links.
The page dropdown in the editor's left sidebar was locked to the sidebar's width, so page names and collection counts were cut off — now it opens wide enough to read, and stays on screen on narrow windows. **Where:** Site editor → left sidebar → click the page name at the top (the one with the chevron) **How to test:** Open a site with several pages and a collection, click the page name in the left sidebar, and check that each row shows its full name plus the item count and manage icon. Narrow the browser window and reopen it — the dropdown should shift inward rather than run off the edge. **Watch for:** The dropdown overlapping the page preview more than before is expected. It should still line up under the page name and close when you click away or press Escape.
If you had staged changes to corners, spacing, or fonts and then hovered a palette to preview it, those other unsaved changes would briefly disappear until you moved your pointer away. Hovering a palette now previews correctly without dropping anything else you were about to save. **Where:** Site editor → Design → Site styles → Tweaks → Palettes **How to test:** Stage a font or corner-radius change, then hover a different palette swatch. Confirm the staged font/corner change stays visible in the preview the whole time. **Watch for:** Any style knob still snapping back to its saved value while hovering a palette.
Hovering a palette or font in Site styles used to wrap every heading in a bright halo, while the palette itself barely changed anything. Both are fixed, and every style knob now previews consistently: what you see on hover is exactly what you get when you click. **Where:** Site editor → Design → Site styles → Tweaks **How to test:** Open a site's design view and hover across the palette tiles and font pairs. Headings should stay exactly as they render normally — no glow appearing or disappearing under the pointer. Then hover a palette clearly different from the current one: buttons, links and tinted panels should visibly take on the new color, and clicking the tile keeps exactly what you saw. Repeat for corners, density, elevation and border weight — each should hold its change after the click rather than snapping back. **Watch for:** Stack several changes before pressing Apply — pick a palette, then corners, then a font. Each one should stay visible while you hover the next; nothing should flicker back to the original as the pointer moves between tiles. Headings sitting on a photo should still be readable on the published site — that treatment is unchanged, only slightly tightened. Also check that a palette change moves lighter and darker shades together (button hover states, tinted backgrounds) rather than leaving some on the old color.
When you point us at your existing website, the chat now tells you how many posts and pages it found and offers to bring them over — instead of leaving you to wonder whether you'll be retyping everything. **Where:** Site setup chat — paste your current website address when asked about your business **How to test:** 1. Start a new site and give the chat your existing website address (a WordPress site shows the most). 2. Wait for it to analyse the site. The plan should mention how much content it found — e.g. "I found 312 posts" — and offer to bring it across. 3. Click "Bring my … posts across". Nothing imports yet — that's expected. 4. Continue and generate your site. Once the design is ready, the content is copied over automatically, along with your images, and your original links are set up to point at their new homes. 5. Check the collection (Blog, etc.) in the site editor to confirm the items arrived. 6. Try the other path too: click "Start fresh" instead. The offer should not come back on later turns. **Watch for:** A post/page count that looks too low or too round (it should reflect the real total, not a capped sample); the offer reappearing after you've already answered it; the offer appearing when your old site has no content; content importing before the design exists; imported items landing in the wrong collection.
Every "Use this design" button on the public template gallery was a dead end — it silently bounced visitors to the homepage and threw away their pick. Clicking it now carries your chosen template's look straight into a new site, including through sign-up or login. **Where:** /templates → any template card or detail view → "Use as inspiration". **How to test:** From a logged-out session, browse /templates, pick a template, and register or log in when prompted. You should land in the site-setup chat with that template's look already applied to the first design, not on the marketing homepage.
On a small number of sites, asking the assistant to add a brand-new section could fail with a code error, or take an extra repair pass before it worked — even though the assistant had built the section correctly. **Where:** Site editor → chat panel (any request that adds a new section, e.g. "add a pricing calculator section" or "add a booking configurator") **How to test:** Open a site in the editor and ask the assistant to add a new section that didn't exist before. It should be added and appear on the page on the first attempt, without an error message and without a noticeably long extra wait. **Watch for:** An error mentioning a problem with the generated code, the requested section silently not appearing on the page, or the request taking a second repair round before succeeding. Sites that already use an animated hero background were the most likely to hit this.
The "Autoplay + mute" quick action could add native video controls that popped up on hover, exposing a scrubber and duration readout — wrong for a muted, ambient background video. **Where:** Site editor → select a video element → Quick Actions → "Autoplay + mute". **How to test:** Apply "Autoplay + mute" to a video, then hover over it in preview — no native play bar, scrubber, or duration (e.g. "0:10 / 0:10") should appear.
The "Pick a design you like" question now has a Browse all templates button, so you are no longer limited to the six suggestions we picked for you. **Where:** Site setup form (the questionnaire in chat) → "Pick a design you like" → Browse all templates. **How to test:** Start a new site, answer the pitch, and open the setup form. Under the design tiles, click Browse all templates. Search or filter the gallery, open a template, and click "Use this design". The picker closes and that template appears as the selected tile — with its own screenshot and name — alongside the original six. Submit the form and generate; the site should be built in that template's style. **Watch for:** A design that gets selected but shows no tile (or a tile with the wrong/missing screenshot), the six original suggestions disappearing, or "Decide for me" no longer working on that question.
Some catalog sections (properties, menu items, products) were designed assuming a fixed number of cards, so when the number of published items differed, a card could stretch awkwardly or leave a half-empty slot. New designs now account for that count changing over time. **Where:** Any newly generated site with a catalog section (properties, menu, products). **How to test:** Generate a catalog-vertical site (real estate, restaurant, or ecommerce) and check the featured items layout — it should look balanced regardless of exactly how many items are published.
A section backed by a collection (property listings, menu items, products) could render its items and then blank out to "nothing published yet" a second later, on a site whose collection also has its own listing page. **Where:** Site editor → any design with a catalog section that also has a listing page (e.g. Properties, Products, Menu) **How to test:** Open a design whose homepage shows a catalog grid and which also has a listing page for that collection. The grid should fill and stay filled — reload a few times and watch it for several seconds after the page settles. **Watch for:** A grid that fills and then empties; a listing page showing fewer items than the homepage; a collection that stays populated after you delete all of its rows (it should empty).
Connecting a live data feed could leave one field (like a description or blurb) unmapped even when it clearly matched a slot, and an invalid or broken data-source link showed a generic server error instead of a clear "not found." **Where:** Site editor → Settings → Data Sources → connect or edit a feed. **How to test:** Connect a feed with a description-style field named something like "blurb," "tagline," or "caption" and confirm it's suggested for mapping automatically. Visit a stale or malformed data-source link and confirm you get a clean "not found," not a server error.
Catalog items no longer share a single photo — each product, dish, room, property or vehicle gets its own image, matched to that item's name. **Where:** Any catalog collection on a generated site — Products, Menu, Rooms, Properties, Vehicles, Courses, Events. **How to test:** Generate a site for a business with a catalog (a cafe, shop or restaurant works well), then open the collection section. Every card should show a different photo, and the photo should suit the item — a croissant on the croissant, not a coffee cup. **Watch for:** Items whose names are very unusual may fall back to a general photo for the collection, or to a coloured placeholder card if nothing suitable is found. If you have uploaded your own images to the site, those are used first and spread across items rather than repeated. Sites generated before this change keep their old images until they are regenerated.
A conflict between two editor features could make a generated hero section crash outright, showing "The Hero section couldn't be displayed here" instead of the actual hero. **Where:** Site editor preview and Preview tab — hero section of a generated site. **How to test:** Generate a site, open the preview, and confirm the hero section renders (no "couldn't be displayed" error). Click into the hero's call-to-action text via click-to-edit and confirm it still works. **Watch for:** "The Hero section couldn't be displayed here" on the hero, especially right after generation.
The Data Sources page was returning "site not found" for every site and every user due to an internal lookup bug, making the feature unusable. It works normally again. **Where:** Site editor → Settings → Data Sources. **How to test:** Open Data Sources for any site you have access to and confirm the page loads instead of showing "Site not found."
Some sites showed "The Header section couldn't be displayed here" in the editor preview, blocking header editing and preview. **Where:** Site Editor / Preview (the header bar at the top of the page). **How to test:** Open a design whose header shows a call-to-action button, switch to that design, and confirm the header renders instead of the red error banner. **Watch for:** The header's CTA button label should match the design (e.g. "Book a Table"), and the curated menu items should still appear.
Some new sites were coming out with a blank hero even though a hero image had already been chosen and saved for them — the image existed, the design just never displayed it. Generated designs now show the imagery they were built around. **Where:** Any newly generated site — Home, then the hero at the top of the page. **How to test:** Generate a new site for a business whose brief calls for a photographic hero (a clinic, restaurant or hotel is a good test). When the design finishes, check the hero: it should show a real photograph, not a plain white or flat-colour band. Generate a second design for the same business and confirm both show imagery. **Watch for:** A hero that renders as an empty white block, or a section whose images appear on one design but not the other. Also worth checking sections further down the page — services, about, team — for image slots that render as blank space or an empty bordered box.
After finishing the setup chat and clicking "Generate 2 Designs," an extra design-direction question used to interrupt before generation actually started. That question is now only asked when you request more designs later, not on the very first generation. **Where:** Site builder chat → after approving the plan → "Generate 2 Designs". **How to test:** Complete a new site's setup chat and click Generate 2 Designs — it should proceed straight to generating, with no extra pop-up question first.
Some designs still showed "The Header section couldn't be displayed here" when the site-wide call-to-action button was set but a specific design or page hadn't customized it. The header now renders correctly in every case. **Where:** Site Editor / Preview and published sites (the header bar at the top). **How to test:** Open a design whose header shows a CTA button, switch between designs and pages, and confirm the header renders the button label (e.g. "Get Started") instead of the red error banner. Publish and confirm the live header renders too. **Watch for:** Designs whose header reads a structured CTA (label + link) should be unchanged; only headers that render the CTA as plain text are affected.
On some newly generated sites, a menu or products section could appear with no items or no images, even though the items existed and were visible in the Content Manager. **Where:** Site editor → any generated site in a catalog industry (restaurant, ecommerce, real estate, hospitality, car dealership, education, events) → the menu, products or similar listing section on the homepage **How to test:** Generate a new site for a restaurant or shop, then look at the menu or products section on the homepage. Each item should show its picture and details. Open Content Manager and confirm the same items are listed there — the two should match. Existing affected sites have already been repaired, so previously blank sections should now fill in. **Watch for:** A listing section that renders its heading but no items underneath, item cards with blank image areas, or a mismatch between what Content Manager lists and what the page shows.
Some newly generated sites showed an empty menu, product, or listing grid on first load even though the items existed — a leftover placeholder value was silently overriding the real content. Newly generated sites now show their catalog items immediately. **Where:** Any newly generated catalog-vertical site (restaurant, real estate, ecommerce, etc.) — the homepage grid section backed by that catalog. **How to test:** Generate a new catalog-vertical site and check that the homepage's menu/product/listing grid shows images and items right away, without needing a refresh.