Importing a Shopify product export now recreates your catalog's category structure automatically and keeps your old collection links from breaking. **Where:** Site editor → Content → a products collection → Import → Shopify **How to test:** Export products from Shopify (Products → Export → CSV), then import that file. Make sure some products have a value in the "Type" column. After the import finishes, the summary tells you how many categories were built and how many old links were preserved. Check Content → Categories for the new rows, and open a product to see it filed under its category. **Watch for:** Only the "Type" column becomes a category — tags are left as tags on purpose, since they're usually labels like "sale" or "new" and would otherwise clutter your categories. Old `/collections/...` links are only redirected once your site actually has category pages to send them to; if you import before those pages exist, re-run the import afterwards to create the redirects. Product links need no redirect at all — they keep the exact same address they had on Shopify.
Layout ideas you generate are now saved and waiting for you next time, you can ask for a change to one instead of taking it or leaving it, and the picker no longer offers you the layout your section already uses. **Where:** Site editor → hover a section → Swap layout **How to test:** Generate a layout, close the picker, reopen it — your idea is under "Ideas you've generated", and clicking it brings it back. With one on screen, type a change ("tighter spacing", "image on the left") and press Revise. Switch between "New" and "Current" to compare against what's on your page. Under "Layout ideas", the arrangement your section already uses is marked as the current layout. **Watch for:** Saved ideas missing after a reload, a revision that ignores what you asked for, or the current-layout marker landing on the wrong tile.
Layout options in Swap layout were all showing the section you already had, so every suggestion looked identical and picking one seemed to do nothing. **Where:** Site editor → hover a section → Swap layout **How to test:** Open Swap layout on any section, press "Surprise me", and compare the three cards — each should now show a genuinely different arrangement of your content. Do the same with a gallery design or a layout idea tile and press "Adapt this design" / "Build this layout". **Watch for:** A preview that still matches your current section exactly, or two cards that look the same as each other.
The $49 Brand Launch Kit has been withdrawn — everything it bundled is still there, and now bills from your Creative Credit wallet at the normal per-generation rate. **Where:** Dashboard → Creative → pick a brand → Logo / brand mark. **How to test:** 1. Open the Logo Studio for any brand. The sidebar now shows what each step costs in credits and your current balance, with a link to top up. 2. Generate logo directions — the button reads "Generate 4 directions" and prices the batch in credits. 3. Scroll to "Starter layouts". The six social/ad layouts are still there and generate without needing a kit; the section states the credit cost per layout and for the full set. 4. Any layouts generated previously still appear in the grid. **Watch for:** - Starter layouts you generated before this change disappearing from the grid — they are matched by layout, and all six should still show. - The Logo Studio offering to sell a Launch Kit anywhere, or mentioning a "kit allowance". - Generations being blocked when you have enough credits, or going through when you do not.
Asking the AI to change a section heading sometimes updated a stored field that the page does not display — the assistant reported success and nothing on the page changed. Edits now target the field the page actually shows. **Where:** Site editor → Edit site → chat panel **How to test:** Open a site, and without selecting anything on the canvas ask "Make the contact section heading Come Say Hello". The heading on the canvas should change to match the assistant's reply. Repeat a few times with "heading", "headline" and "title" phrasing — every run should produce a visible change. **Watch for:** A reply that says a heading was updated while the canvas still shows the old wording; or a copy edit that unexpectedly restyles the section instead of only changing words.
Asking the assistant to bring something over from one of your other designs — "make this hero background like D2" — now hands it that design's actual code instead of a fragment, so you get the real thing rather than an approximation of it. **Where:** Any site with more than one design → open a design → Assistant panel (typed chat or voice) **How to test:** 1. Open a site that has several designs and switch to one of them. 2. Ask the assistant: "I don't like this hero background — copy the one we have in D2." 3. The change should reproduce D2's actual background, including its interactive parts, and should REMOVE the background image it replaced rather than fading it out behind the new one. 4. Repeat the same request in voice mode. It should make the change instead of asking you to attach a screenshot. **Watch for:** - The replaced background image lingering at low opacity under the new treatment — that was the old behaviour and should be gone. - A design named by a label the site doesn't have: the assistant should tell you which designs exist rather than inventing one. - In voice, a spoken "that change has been applied" after a question you only asked for information — reads and look-ups no longer claim to have changed anything. - The change list under a reply naming an internal piece of the page ("Preview Fallback") or listing the same area twice. One edited section should now read as one area, named after the section.
Gallery cards used to drop the inline styling and animation end state of animated elements, so designs built around them showed up on plain white backgrounds with empty or collapsed widgets (an interactive editor mock-up with a blank canvas, a missing aurora glow behind the hero). Cards now render every animated element where its animation lands, with its own styling intact, so the preview matches what you see when you open the design. **Where:** Site editor → Design Gallery (the grid of design cards), the homepage thumbnail in Mission Control, and public template previews. **How to test:** Open a site whose designs use animated sections (any imported or authored design with a dark theme is a good candidate). Compare each gallery card's hero against the same design opened in the editor: background colour, glows and gradients, and the contents of any animated mock-up or widget should match. If a card still looks stale, reload once — the browser cache of previews is versioned and refreshes automatically. **Watch for:** Animated counters still show their starting value in cards (they count up only in the live editor). A card that looks different from the editor after a reload is a new bug, not this one.
The "Directions for…" card in the design assistant sometimes showed a technical sentence about content keys that made no sense to site owners. It now explains in plain language when a section's saved copy couldn't be found, and lists warnings and assumptions as separate labelled items instead of one run-on paragraph. **Where:** Site editor → click a section → Explore directions → Assistant panel **How to test:** Open a hand-authored design (for example D11 on the Mondovo homepage site), click the hero, and run Explore directions. The amber note should read "We couldn't find this section's saved copy…" under a "Heads up" label, with any assumptions under their own label. **Watch for:** Any mention of keys, fields, effective content, or other internal terms in the amber box.
A round of fixes so that everything you do in the editor acts on the design in front of you, even when a teammate is looking at a different one. Restoring a section from history, deleting a form, renaming a page, activating a feature and asking the assistant to change your colours could each land on a different design than the one on your screen. Publishing a design no longer changes your site's design when the publish is refused, and a spoken "publish my site" now tells you which design goes live before it does. Choosing a design that the server cannot load reports the real error instead of claiming success. **Where:** Site editor, across the design switcher, version history, forms, pages, the Apps grid and the assistant. **How to test:** Open a site in two browsers as two people, on two different designs. In one, restore a section from version history, delete a form, rename a page, and ask the assistant to change the primary colour. Every change should appear on the design you had open and nowhere else. Then choose "Use this design" on a design that has no saved files: you should see an error, not a success message. **Watch for:** A change appearing on a design you did not have open; a success message for an action that did not take effect; the site's design changing after a publish that was refused.
Each person's editor now remembers which design they are viewing on their own. Opening D2 in one browser used to make D2 the site's design for everyone, so a teammate's Publish could put a design live that they never looked at. Now the site's design changes only when someone chooses it: "Use this design" in the design switcher or gallery, publishing from the editor (which publishes the design on screen), restoring a version, or the API's switch tool. A small badge marks the site's current design so you can see when the one you are viewing is different. **Where:** Site editor, design view. Hover a design pill or open the gallery to see the "Site design" badge and the "Use this design" action. **How to test:** Open the same site in two browsers. Open D3 in one and D5 in the other; the badge stays on the site's original design in both. In the second browser choose "Use Design 5 as your site's design"; the badge moves to D5 in both browsers after a refresh, and the first browser stays on D3. Edit text or an image in the first browser: the change lands on D3, not D5. **Watch for:** The badge moving after only switching designs; an edit made while viewing one design appearing on another; "Use this design" reporting success when the switch failed.
Selecting a headline whose second line is a separately styled accent (for example a coloured phrase) used to show only the first line in the Quick edit panel, with no way to change the accent from there. The panel now lists each line as its own field, named after the content it edits, so both lines can be changed from one selection. **Where:** Site editor → click a two-part headline on the canvas → Assistant panel → Quick edit **How to test:** On the Mondovo homepage site, open Design 11 and click the hero heading. The panel should show a "Title" field with "Every client brief deserves" and an "Accent" field with "more than one design." Edit either, save, and confirm the canvas updates. **Watch for:** Ordinary single-line headlines, and animated headlines split into per-word spans, should still show a single field.
Some AI edits were being saved to your site but not drawn on the preview, so the chat said the change was applied while the design in front of you stayed the same. **Where:** Site editor → any design → Chat panel → ask for a change to a section (e.g. "make the hero background darker", "change the site's accent colour") **How to test:** Open a design, ask the chat to restyle a section such as the hero or the overall theme colours, and watch the canvas after the reply arrives — the section should update in place, with no manual refresh or design switch needed. **Watch for:** A success reply paired with an unchanged preview, or the message "the edit was saved but the live preview couldn't update". Either means the edit landed in the database but not on screen.
When someone else opened a different design of the same site, the editor told you the site had changed and, if you pressed Refresh, moved you onto their design. Now a teammate merely viewing another design is not reported as a change, and Refresh pulls in their edits without moving you off the design you were on. **Where:** Site editor, design view. The amber "This site was changed in another session" notice at the top of the canvas. **How to test:** Open the same site in two browsers as two users. In browser A open D3. In browser B open D5 and switch between designs. Return to browser A: no notice should appear. In browser B make a text edit. Return to browser A: the notice appears; press Refresh. Browser A stays on D3 with browser B's edit applied to the shared content. **Watch for:** The notice appearing after only switching designs elsewhere; Refresh changing the design number in the URL; a blank or "Reconciling" canvas after Refresh.
Stepping through a section's history showed the page exactly as it looks today for every entry in the list, so there was no way to see what an older version actually looked like before restoring it. **Where:** Site editor → open a page → right-click a section → Section History **How to test:** Make two or three separate copy changes to the same section (for example, change a section heading three times), then right-click that section and choose Section History. Click through the entries in the left-hand list: each one should render the page with that entry's older wording in the highlighted section, and the newest entries should be labelled with the change that actually produced them. **Watch for:** Every entry looking identical to the live page; an entry whose description mentions a different part of the page than the one you right-clicked; the preview freezing on the first entry you open and not updating as you use the Older/Newer arrows.
On sites with multiple designs, Section History said "This section hasn't changed in its recent history" for every section, even right after an edit — the timeline was skipping every version saved before the site was split into separate page files, which on most design sites is nearly all of them. **Where:** Site editor → Edit mode → right-click a section → Section History **How to test:** Open a site that has several designs and a history of edits, switch between designs, and open Section History on a section you know was edited (a formatting change, a class change, a copy change). The list should show those versions, newest first, and Restore should step back to each one. **Watch for:** A section that genuinely has never been edited still shows the empty message — that's correct. Entries from a different design appearing under the design you're viewing would not be; each design's timeline stays its own.
Returning to a design you had already viewed in the same editor session could leave the canvas rendering the design you just came from, even though the design pill and the URL both said you were back on the one you picked. **Where:** Site editor → design toolbar → the design pills (D1, D2, …) **How to test:** Open a site with several designs, note the layout of the active design, switch to a different one, then switch back. The canvas should return to the first design's layout, matching the highlighted pill and the `?variation=` in the address bar. Bounce back and forth a few times. **Watch for:** A canvas whose sections do not match the highlighted pill; a section panel or Section History that reports the wrong section (or an empty history) because the canvas is showing a different design's sections.
Undoing a change on one design could rebuild it from a different design's files, replacing most of the page and losing sections that existed only on the design you were editing. **Where:** Any site with more than one design → open a design → Assistant panel → Undo (or Version History → restore) **How to test:** 1. Open a site with several designs. In a second tab, open a different design of the same site. 2. Back in the first tab, make a change to one section, then press Undo. 3. Only that section should revert. Every other section, and the design's own page structure, must be exactly as it was. 4. Check the change list under the reply names the section you edited — not a different design's sections. **Watch for:** - Fonts, header or spacing changing after an undo — that was the symptom of the old bug and should no longer occur. - Sections disappearing that exist only on the design you were editing. - An undo that reports it could not run: that is deliberate. It now refuses rather than rebuilding your design from another one. Nothing is changed when it refuses.
If a renewal payment fails or your bank asks you to confirm it, you'll get an email and an in-app notice with a link that fixes it — instead of finding out when something stops working. **Where:** Dashboard (banner appears at the top when there's a billing problem) and your billing email inbox. **How to test:** 1. Open the dashboard for a workspace whose subscription is marked past due — a banner appears above the header. 2. If the payment is waiting on bank approval, the banner says "Your bank needs to confirm your renewal" and links straight to the confirmation page. If the card actually failed, it says "We couldn't take your last payment" and links to the billing page. 3. Complete the payment. The banner disappears on the next page load. 4. Check the billing inbox for the matching email. It should arrive once per failed invoice, not once per retry. **Watch for:** - The same email arriving more than once for a single invoice, or arriving more than once a week for an ongoing problem. - The banner still showing after a payment has gone through. - A "confirm your payment" message when the card genuinely declined, or an "update your card" message when the card is fine and only needs bank approval — these two are deliberately different and must not be swapped. - Sites going offline for non-payment with no warning email in the days beforehand.
When an AI agent connected through the Mondovo MCP connector replaced a file, patched copy, or imported a design directly, the change saved but never appeared in version history, so Undo skipped past it and restored an older, unrelated version. Those edits are now recorded like any other change, and the connector tells agents when to edit directly versus ask our AI to refine. **Where:** Any MCP client connected to your Mondovo account (e.g. Claude with the Mondovo connector), then Site editor → version history **How to test:** With a connection that has the source-read permission, ask the agent to change one thing on a page by editing the file directly. Open the site's version history: a new entry should appear for that edit. Undo it from the editor or ask the agent to restore the previous version; the exact edit should revert and nothing else should change. Repeat with a copy-only change (a headline) and with adding a new authored design. **Watch for:** An edit that saves but lists no new version; Undo reverting a different, older change; an agent response containing a history warning; a design import attributed to nobody in history.
The design-phase toolbar is tidier and stays usable with many designs: the design pills now live in one box with "All designs" and "+ New", scroll on their own when there are more than fit, and the reaching-the-limit state is a dimmed "+ New" with an explanation instead of a yellow warning chip. **Where:** Client editor → a site in the design phase → the dark toolbar above the canvas (`/client/{clientId}/site/{siteId}/design`) **How to test:** 1. Open a site with 8–10 designs. The strip reads "All designs (N)" followed by D1…Dn and "+ New" in a single grey box. There is no separate "DESIGNS" label, no separate pin box, and no "Design → Build → Live" stepper next to "Build my site". 2. Narrow the browser window to about 1200px. The pills scroll horizontally inside the box while Fit/device buttons, Preview/Edit, Tweaks and "Build my site" stay fully visible. 3. Click D10 at that width. The strip scrolls so D10 is in view. 4. On a site with 10 designs: "+ New" is dimmed. Hover it for "10 of 10 designs. Delete one in All designs to make room". Clicking it opens All designs; it never opens the create flow. 5. Hover any pill: the "Add to board" pin is still in the hover card. **Watch for:** the strip sliding under the Fit/device buttons at narrow widths; "+ New" wrapping onto two lines; a real `disabled` "+ New" that shows no tooltip; the Mission Control header losing its Design → Build → Live stepper (it should still be there).
The search box on a directory's front page now actually searches it, the listing page shows every business instead of the first few, and each one has its own page with hours, ratings, contact details and a way for its owner to claim it. **Where:** Your directory's front page (the search bar in the header image), the **Directory** page itself, and any business's own page — click a card, or its name, or **View details**. **How to test:** 1. Open your directory site's preview. Type something into the search box on the front page — a trade, a business name, or a neighbourhood — pick an area from the dropdown next to it, and press **Search**. 2. You land on the directory page with those filters already applied, and the address bar shows them. Send that link to someone and they see the same filtered list. 3. On the directory page, try the rest: the keyword box, the area dropdown, the category buttons, and the sort (Recommended, Top rated, Most reviewed, A–Z). The count above the cards tells you how many match, and **Clear filters** gets you back. 4. Check the category buttons. Only the ones that several businesses actually belong to are shown; the odd one-offs are tucked behind **More categories**, which you can open. A directory of a hundred plumbers no longer offers you a button for the one accountant in it. 5. Scroll to the bottom. Businesses are shown 24 at a time with page controls, and the page number stays in the address bar so you can come back to it. 6. Click any business — its photo, its name, or **View details**. Its own page opens with the photo, star rating and review count, what it does, where it is, its phone number and website as buttons, its opening hours, and other businesses in the same area at the bottom. 7. On a business page, press **Claim this business** and **Send inquiry** to check both reach you. 8. If you have built best-of pages, open one. It lists that area's top ten with the same cards, and links back to the full directory. **Watch for:** Businesses that pay for featured placement stay at the top of the list in every sort order — that is deliberate, not a sorting bug. Sorting by rating puts unrated businesses last rather than treating them as zero. The "other businesses in the same area" strip loads a moment after the rest of the page. If a business was listed without a website, the website button simply is not there rather than leading nowhere. Your directory now has one listing page rather than two — if you had bookmarked the old second one, use the Directory page instead.
In the site editor, a chat edit that only changed text (a menu heading, a hero headline) could vanish from the canvas as soon as a later chat request changed the page's code, even though every edit had been saved. Reloading brought the text back. The editor now keeps its own copy of saved text edits in step with the canvas, so later code changes no longer reset it. **Where:** Client → site → Edit site → Edit mode → chat panel **How to test:** Ask the assistant to change a section heading, confirm it appears on the canvas, then ask for a code-level change (for example, add spacing to the hero). The heading you changed first must still be on the canvas after the second change lands, and after another 20 seconds. **Watch for:** The first heading reverting to its old text after the second request; an "Edit Conflict" dialog appearing when you made no manual edits; the change appearing only after a page reload.
From the second chat refinement of an editor session onward, the change was saved but the canvas kept showing the old copy until you reloaded. The editor mistook its own previous edit for something you had typed meanwhile, showed the Edit Conflict prompt, and quietly dropped the new result. The request-time and response-time content are now read from the same place, so only a real mid-flight edit raises the prompt. **Where:** Site editor → design canvas → chat panel ("Describe a change...") **How to test:** Open a build site's editor, send "Change the contact section heading to X", wait for it to render, then send "Change the hero headline to Y" in the same session. The hero should update within a few seconds without an Edit Conflict prompt and without reloading. **Watch for:** An "Edit Conflict — You made edits while AI was processing" prompt after a plain chat edit when you did not touch the canvas; a "Done" reply whose change never appears until reload; a conflict prompt stuck at "Auto-selected in 0s".
Pick the ready-made directory business, tell us what it lists and where, and it opens with real businesses in it — names, addresses, phone numbers, opening hours, ratings and photos — instead of an empty page you have to fill by hand. Each one is written up in a short, neutral description, and you can add more at any time. **Where:** Start a directory from **Ready-made businesses** (Templates, or your dashboard's Inspirations tab) and answer the two questions it asks — what the directory lists, and the town or city it covers. When it opens, your businesses are in **Directory → Listings**. Adding more later, and the best-of pages, are described below. **How to test:** 1. Start a ready-made directory. Give it something specific — "plumbers" and "Austin, Texas" — and let it finish setting up. 2. Open **Directory → Listings**. Around a hundred real local businesses are listed, each with an address, a phone number, a website, opening hours, a rating and a photo. Every one shows as unclaimed, so its owner can claim it later. 3. Read a few descriptions. They are written from the facts we found — nothing invented, no copied reviews. 4. Check **Directory → Queue**. Anything that looked like it does not belong in your niche — a landscaper in a plumbers directory, say — is waiting there for you rather than sitting on your live site. Approve or reject each one. 5. At the top of the Listings tab, press **Add businesses**. The card tells you first whether this one is included with your plan or costs credits, and how many you have. Anything already listed is skipped, so pressing it twice never duplicates your directory. 6. Open **SEO → Best-of pages**. It lists the areas you have enough businesses in to make a "Best … in …" page, and explains why the others were left out. Build them, and each page ranks that area's businesses — the ones you have featured or that have paid for placement come first. 7. Your home page checklist says how many are listed, how many owners have claimed theirs, and how many are waiting in your queue. **Watch for:** A search returns businesses from the surrounding towns as well as your own — that is normal, and each one is filed under its own area, so it appears on that area's page rather than on your city's. Some businesses come back without an area at all; those appear on your main directory page only. The first fill of a directory comes with your plan; every later one costs credits, and a fill that finds nothing new is not charged. Best-of pages built for you when the directory is set up go live with the site; ones you build yourself later from the SEO panel stay as drafts until you are happy with them. If your town is small, expect fewer businesses — we list what is really there rather than padding it.
Section History only listed versions where a section's layout code changed, so the edits people actually make most — "change this heading", "reword this intro" — never appeared in the timeline, and restoring an older step could leave the wording untouched. Each step now compares the section's code *and* the content it renders, and restoring a step rolls that content back on every layer the page reads from, so what you preview is what you get. **Where:** Site editor → Edit mode → right-click a section → Section History **How to test:** Ask the assistant to change a section's heading (for example "Change the menu section heading to Our Seasonal Selections") and wait for it to apply. Right-click that section and open Section History. The step just before your edit should be listed with the old heading; stepping onto it previews the old heading with the rest of the page unchanged. Apply it and the old heading is live again; the neighbouring sections keep their current copy. **Watch for:** An edit to a *different* section's copy showing up as a step for this one; a preview that shows the old heading but Apply leaving the new one in place; the timeline taking noticeably longer to open.
A request that mixes something site-wide with something about one section — "make it green themed and give the hero a background video" — now changes the whole design as asked, instead of rebuilding only the hero and quietly dropping the rest. **Where:** Site editor → design chat, plan panel **How to test:** Ask for a design change that combines a site-wide ask with a named section. The plan panel's scope should read as a whole-page change and the button should say "Build from D2", not "Update one section of D2". Then ask for only a section change ("just redo the hero") and confirm it still narrows to that one section. Also try "redo the hero and drop the FAQ" — both should happen. **Watch for:** Nothing you asked for in a single message should silently disappear. The scope shown in the plan panel is editable, so if it ever reads narrower than you meant, you can widen it before generating.
Asking the design assistant for a copy of an existing design ("clone D2", "duplicate this one") now produces an exact copy instantly and free, instead of rebuilding the page and sometimes coming back with sections missing. **Where:** Site editor → design chat (New Design / More like this) **How to test:** In the design chat, ask for a copy of a specific design and add no other instruction. The plan panel's button should read "Duplicate D2" rather than "Build from D2"; pressing it should add an identical design straight away. Then try "clone D2 but make the hero shorter" — that should go back to reading "Build from D2" and produce a new design with your change. **Watch for:** A plain copy request should never lose sections or take generation time. A copy request that carries any change should still be treated as a new design, never silently copied without the change.
Asking the assistant to clone or refine an existing design no longer produces a thinner page with sections quietly missing — the clone now reproduces the source design's full section lineup and only changes what you asked for. **Where:** Site builder → open a site's Design view → chat panel → "clone D2" (or any request that starts from an existing design, e.g. "same as D2 but darker") **How to test:** Open a site that has several designs and at least ten sections on the page. In the design chat, ask to clone one of them by name and confirm the generation. When the new design finishes, scroll it top to bottom and compare against the design you cloned — every section should be present, in the same order. **Watch for:** A clone that comes back noticeably shorter than its source, or that is missing a specific section (proof strip, showcase, FAQ) you never asked to remove. Also check that a request naming one section ("make the hero taller") still changes only that section.
Picking a design in "Select a Design to Clone" now copies that design — previously it copied whichever design you happened to be viewing, and the copy ran with no visible progress. **Where:** Site editor → New Design → Clone a Design → Select a Design to Clone **How to test:** On a site with several designs, open a design other than the one you want (say you are viewing D6). Start the clone flow, click D2 in the picker, and confirm the new design is a copy of D2. Repeat: click D2 again and confirm you get a second copy of D2, not a copy of the copy you just made. **Watch for:** The picker should stay on screen with a spinner over the card being copied until the new design appears, then close. It should not vanish instantly, and the New Design window behind it should not stay open afterwards. If the copy fails, the picker stays open with the error rather than closing.
Deleting a page was meant to move it to a trash you could restore from, but the deleted page was never actually kept — so the Trash list stayed empty and there was nothing to bring back. Deleted pages are now held safely, and you can restore one with its content and layout intact or remove it for good. **Where:** Site editor → the page list in the left sidebar → **Trash**, below your pages. It only appears once something has been deleted. **How to test:** 1. Open a site in the editor and pick any page other than the home page. 2. Delete it. It disappears from the page list and a **Trash** section appears below, with the page in it. 3. Click the page in Trash to preview it, then choose **Restore**. 4. The page comes back in the list with its content and layout as they were, and the Trash section empties. 5. Delete another page and choose **Delete permanently** instead — it leaves the Trash and cannot be brought back. **Watch for:** A page restored after you changed your navigation should reappear in the menu where it was; check the menu after restoring. Links from other pages to a deleted page are cleaned up when you delete it and are not automatically put back on restore, so re-check any buttons that pointed at it. The home page cannot be deleted, so it never appears in Trash.
On a phone the design gallery's top bar ran out of room and its buttons stacked on top of each other — the "Focus Mode" button ended up hidden underneath "New Design", so there was no visible way back to the editor. The bar now keeps only what matters at that size, and it finally has a Share button. **Where:** Open a site with more than one design → Design Gallery (the grid of designs) → view it on a phone or a narrow window. **How to test:** Narrow the browser to phone width. The bar should show only the back arrow, Focus Mode, New Design and Share — nothing overlapping and nothing cut off at the right edge. Tap Focus Mode to return to the editor. Tap Share to open the share-link dialog. Widen the window and the preview-width toggles and Import come back. **Watch for:** Any button sitting on top of another, a control running off the right edge, Focus Mode not returning you to the editor, or Share opening a dialog that never loads a link.
Every design now has a Duplicate button on the card itself, so making an exact copy is one click on the design you want instead of a trip through the New Design window. **Where:** Site editor → Designs gallery (button row on each card), and the design switcher in the preview toolbar. **How to test:** Open the designs gallery while a different design is selected, click the copy icon on the design you want, and confirm the new copy is of that design. The button shows a spinner while the copy is made and a confirmation names the new design. Duplicate disappears once you reach the design limit. **Watch for:** The copy should be of the card you clicked, never of the currently selected design. If a copy fails you should see an error message rather than nothing happening.
Mission Control now has a Preview button in the header, and the site switcher shows the site you are viewing even when it belongs to a different organization than the one you have selected. **Where:** Any site → Mission Control → top bar. **How to test:** Open a site's Mission Control. The header should show that site's name and thumbnail, not "Select Site". Click Preview: on an unpublished site it opens the visitor preview in a new tab; on a published site with no pending changes the button reads "View live" and opens the live site. **Watch for:** A popup blocker stopping the new tab; "Select Site" still showing for a site you can open; Preview opening the live site while changes are still unpublished.
Instead of starting from a design and building the business around it, you can now pick a business that already works — a local directory, for instance — answer a couple of questions, and get a finished site about two minutes later. A ready-made business arrives with more than a look. The directory comes with a listings section you can add to, pages where visitors browse and filter what you list, a way for visitors to submit a listing that waits for your approval, and a way for the businesses you list to claim their own entry by email and keep it up to date. Your site opens straight into its dashboard with a short list of what is already set up and what is worth doing next — add your first listings, set your prices for featured placement, publish. **Where:** The "Ready-made businesses" strip at the top of the [designs gallery](/templates), and the **Ready-made businesses** tab in Dashboard → Inspirations. They only appear once we have made one available, so if you do not see the strip or the tab yet, that is why — the rest of both pages is unchanged. **How to test:** 1. Open the designs gallery or Dashboard → Inspirations and look for **Ready-made businesses**. 2. Pick one and press **Use this business**. If you are not signed in you will be asked to, and your pick is remembered through sign-up or sign-in. 3. Answer the questions it asks — your business name, and for a directory the kind of businesses you list and the area you cover. 4. Press **Create my site**. You land in your site's dashboard while the setup finishes, with a checklist of what is in place. 5. Add a couple of listings from the Directory area, then publish. **Watch for:** The checklist fills in over the first few seconds as the setup finishes — a line missing on first paint should appear shortly after. Nothing on your site is public until you publish. Featured placement needs two steps before you can charge for it: your prices, set in Directory → Settings, and a payment provider connected in Settings — the checklist links you to whichever is still missing. Adding real businesses for you automatically, and the best-of pages for each area you cover, are not available yet; the checklist says so rather than pretending otherwise.
When you selected a section and asked for a change, the edit could come back as "I wasn't able to make the requested changes" even though the AI had produced a real edit — one malformed character in its first attempt threw the whole thing away instead of retrying. The editor now checks the AI's output before accepting it and falls back to its safer editing path, so these requests apply instead of failing. **Where:** Site editor → select any section on the canvas → ask the assistant to change it (e.g. "make these cards auto scroll horizontally") **How to test:** Open a site with several sections, click a section in the preview so the element chip appears above the message box, and ask for a visual change to it. The change should apply and the chat should describe what changed. Repeat on a few different sections — including a request for animation or motion, which is the kind most likely to produce a malformed first attempt. **Watch for:** A reply of "I wasn't able to make the requested changes. Could you try rephrasing your request with more specific details?" on a clearly-worded request; an edit that appears to apply but leaves the section blank or broken in the preview; or a section other than the selected one changing.
Opening a design used to show the page, then blank it out and rebuild it a second time. The canvas now stays up, and most designs skip the second rebuild entirely. **Where:** Site editor → open any design (Design tab) **How to test:** Open a design you have not viewed in a few days, so the preview is built fresh. Watch the canvas from first paint for about a minute. You should see one build, then the page — and it should stay. If a second build does run, the page stays visible with a small "Updating preview…" pill at the top instead of a white loading panel. **Watch for:** A white "Compiling…" panel appearing *over* a page that had already rendered. Switching designs, switching pages, and hitting refresh should still show the full loading panel — there is nothing valid to keep on screen in those cases, so that one is correct.
New designs now keep the headline and the image in a sensible balance at the top of the page, and an image shown inside a browser or app window is a product screen rather than a stock photograph. Two things were going wrong on the first screen. A design could give the headline a column far too narrow for its type size, so a short headline broke into a tower of one-word lines, the buttons slid below the fold, and the image — now most of the width — set the height of the whole section. Separately, a design could draw a browser window complete with a title bar and then put a photograph of people in a meeting inside it: the frame promised a product, the picture showed something else. The design instructions now state the relationship between headline size and column width directly, a check measures the finished layout and reports heroes that break it, and any image the layout presents inside a browser or device frame is produced as a product interface instead of being filled from the photo library. **Where:** Any new set of designs — the Design step of a site, then each design tab (D1, D2, D3). **How to test:** Generate a fresh set of designs for a business and look at the top of each one. The headline should read as full lines rather than one or two words per line, the primary button should be visible without scrolling, and copy and image should share the width rather than the image dominating. If a design draws a browser window in its hero, what's inside it should look like an app screen. **Watch for:** A headline that still stacks into very short lines; a hero image that fills most of the width and pushes the buttons out of view; a browser or phone frame containing a photograph of people or a place instead of an interface. Existing designs are unchanged — regenerate to pick up the fix.
PayPal checkout payments now advance the matching storefront order to paid, update inventory, and run the same confirmation flows as Stripe and Razorpay. Retried PayPal webhooks are deduplicated, and an oversold order automatically refunds its captured PayPal payment. **Where:** Published storefront → Cart → Checkout with PayPal **How to test:** Complete a PayPal sandbox checkout for an in-stock product. The order changes from pending payment to paid, inventory decreases once, and replaying the capture webhook does not decrease it again. **Watch for:** The order remaining pending after PayPal confirms the capture, inventory changing twice after a webhook retry, or an oversold capture requiring an unreported manual refund.
Right-click any section in the editor and pick Section History to step back through how just that section used to look, then put one earlier version back — the rest of the page stays exactly as it is now. **Where:** Site editor → right-click a section in the preview → Section History **How to test:** 1. Open a site in the editor and change a section (rewrite the hero, swap the pricing layout). 2. Make several more unrelated changes elsewhere on the page. 3. Right-click the section you changed first and choose Section History. 4. Step through the entries with the arrows or the list on the left. Each one shows the whole page with that section spotlit, exactly as the page would look if you restored it. 5. Pick one and choose Restore this version. Only that section changes; your later edits elsewhere survive. **Watch for:** - The list should only show versions where that section genuinely looked different. Repeats of the current state, or steps that look identical to each other, mean the timeline is not collapsing properly. - The spotlit section in the preview must be the one you right-clicked. If a different section is highlighted, stop and report it — restoring would overwrite the wrong part of the page. - Sections with no history yet show "This section hasn't changed in its recent history" rather than an empty list. - Browsing the history must not change the page on its own. Only Restore this version should alter anything. - The option is hidden while you are already previewing an older version of the whole site. - Restoring a section works even on a site that already has an unrelated page with a problem in it. Only breakage the restore itself would cause blocks the action.
A directory site can now take listings from the public, let real business owners take over their own entry, and sell a better spot in the list — with the money going straight to your own payment account. Visitors add their business through a form on your site. Nothing they submit appears anywhere until you approve it: submissions wait in a queue in Mission Control, where you can approve or reject each one with a note, and the person who sent it gets an email either way. Business owners can claim a listing you already added for them. They enter their email, we send them a link, and clicking it hands them that listing and signs them into their own account, where they can keep the details up to date. You choose which changes need your approval again — edit the business name and it comes back to your queue; fix a phone number and it just saves. You can also sell featured and sponsored placement. Set your prices and how long a placement lasts, and listing owners can buy one from their card on your site. Paid placements sort above free listings, and lapse on their own when the period ends. One thing to know: a paid placement starts the moment it is bought, but only appears on your live site the next time you publish — the Placements tab tells you how many are waiting. **Where:** Site editor → Features → Directory. New tabs: Queue, Claims, Placements, Settings. **How to test:** In Settings, turn on "Accept public submissions" and tick the fields visitors may fill in, then publish. From your live site's directory page, submit a business — it should not appear on the site, and it should show up under Queue with a count on the tab. Approve it, publish again, and it appears. To try paid placement, connect a payment provider first (Settings → Payments), then add a Featured tier with a price and a length; the "Feature this listing" button appears on directory cards, and a completed purchase shows under Placements with its end date. **Watch for:** A submitted listing appearing on the live site before you approve it; a claim link that still works after you revoke it under Claims; a placement that keeps its badge after its end date has passed; prices showing in the wrong currency; or the "waiting for your next publish" count not clearing after you publish.
Images in comparison sliders, showcase galleries and feature sections were sometimes unrelated to the section — a photo of a person where a website screenshot belonged — and list sections could repeat one decorative graphic for every item. **Where:** Any newly generated design, and the Site Health panel in the site editor. **How to test:** Generate a new design for a business whose homepage has a before/after slider, a showcase gallery, or a list of services or process steps. Check that each showcase card shows a distinct, on-topic image, that a before/after panel shows interfaces rather than people, and that a list of services does not repeat the same drawing beside every row. Site Health now also flags a section whose list items all render the same graphic. **Watch for:** A showcase card falling back to a generic photo instead of a site screenshot; a before/after panel still showing a photograph of a person; a list section where every item carries an identical illustration. Existing designs are unchanged — regenerate to pick up the fix.
Opening a site's design view no longer waits on a large background download, so the editor and its preview appear noticeably sooner — the difference is largest for accounts with many sites. **Where:** Any site → Design view (the site editor) **How to test:** Open a site's design view on an account with a dozen or more sites. The preview should appear within a couple of seconds. Open the site-name dropdown in the top-left — every site should still be listed, with the same names, thumbnails and Published/Draft/Planning badges, and search should still match on site name. **Watch for:** A site showing the wrong name (or "Untitled Site") in the dropdown; sites missing from the list; the wrong status badge; search failing to find a site by name.
When you looked at an earlier version of your site, the "Viewing version" bar at the top could balloon into a wall of text that filled the whole preview and pushed its buttons off screen, so there was no way back. **Where:** Site editor → Assistant panel → Version History → click any past revision **How to test:** Open a site with a long refinement history and click a revision whose summary lists a lot of changes. The bar stays a single line across the top of the preview, and Cherry-pick, Restore and Cancel are all still visible on the right. **Watch for:** The bar growing taller than one line, the summary wrapping, or the Cancel button disappearing on a narrow window.
Paste a website address and we read the whole site — its pages, brand, content and what it actually does — then design three new versions of it, without a single question first. **Where:** The new **Redesign** page at `/redesign`, or paste an address straight into the prompt box on your dashboard instead of describing a business. **How to test:** 1. Go to `/redesign` (or type just `example.com` into the dashboard prompt box). 2. Optionally say what isn't working today, and choose what should happen to your words: keep them exactly, sharpen them, or rethink the pitch. 3. Watch the progress screen — it shows what we found as we find it: the business name, brand colours, how many pages we'll rebuild, and which features your site already offers (contact forms, booking, a help centre, a store). 4. When the three designs finish, you land in the editor with them ready to compare. **Watch for:** A site behind a login, a cookie wall, or one that is still loading when we visit will report that we could not read enough of it — try another address or describe the business instead. The three designs should look genuinely new, not like copies of the site you started from; all three carry the same content so you are comparing designs, not wording.
Two checks in the Responsive Check panel were flagging correct code, so "Fix All" had nothing it could change and finished with a red "Failed to fix any issues" banner. **Where:** Site editor → the "···" menu in the preview toolbar → Responsive Issues **How to test:** Open a design whose panel previously listed "Fixed pixel heights" or "Important elements hidden on mobile". An image capped with a maximum height, and a desktop menu that already has a mobile hamburger beside it, are no longer reported. Real problems — an element with a hard fixed height, or a menu with nothing replacing it on phones — still appear and still fix. **Watch for:** A genuine issue disappearing from the list. If a section really does overflow on a phone and the panel reports nothing, that is worth reporting.
Changing a piece of text from the right-hand Quick edit field now records a Direct Edit entry in the Activity feed and gives you a working Undo, instead of saving silently and leaving the feed showing an older change. **Where:** Site editor → open a design → Edit → click a piece of text → right-hand "Quick edit" field → Save **How to test:** Open a design, click Edit, select a headline or tagline on the canvas, change the text in the Quick edit field on the right and click Save. Within a few seconds the Activity strip above the message box should read "Updated <field>: "old text" → "new text"", with an Undo button next to it. Click Undo and the original text should come back on the canvas. **Watch for:** An edit that saves but leaves the Activity strip showing an older, unrelated change; a Save that takes far longer than a few seconds; a field that offers no Undo after saving; or the Quick edit panel reporting that the text "isn't connected to editable content" for a headline that clearly is.
Swapping an image used to happen through a narrow window where the picker area collapsed to a sliver — the upload box was cut in half, the image preview was tiny, and scrolling never brought the whole thing into view. The window is now wider, the framing options sit in their own side column instead of squeezing everything else, and the preview grows to use the space that is actually available. **Where:** Site editor → click any image in the preview → Replace image **How to test:** Open a site in the editor, click an image, and choose to replace it. Pick any tab (Upload, URL, Stock Photos, AI Generate) and load an image. The preview should be clearly visible without scrolling, the layout and fit controls should appear down the right-hand side on a normal laptop screen, and Cancel / Apply should always be reachable at the bottom. On a narrow browser window the framing options collapse behind a "Framing & effects" toggle instead. **Watch for:** The Apply button being cut off at the bottom of the window, the image preview being clipped, or the framing controls failing to appear after you load an image.
Changing the background or text colour of a button, link or other element inside a page section now updates the preview immediately, instead of reporting success while the preview kept showing the old colour. **Where:** Site editor → click an element in the preview → Advanced → Text colour / Background colour → pick a swatch **How to test:** Open a design, click a call-to-action button inside any section (not the header or footer), open the colour swatches and pick a new colour. The button should change colour in the preview within a few seconds, and still be the new colour after reloading the page. **Watch for:** A colour that only appears after a manual page reload, a success message over an unchanged preview, or a section that goes blank after a colour change.
Deleting something part-way down a page could make a button elsewhere — usually the call-to-action in the header — disappear from the canvas until the next refresh, and undoing that delete could quietly reset link settings you had changed on other sections. **Where:** Site editor → click any element on the canvas → Delete **How to test:** Open a design whose header has a button with the same wording as a button further down the page (for example both saying "Order on WhatsApp"). Delete the lower one. The header button must stay exactly where it is, and only the element you picked should disappear. Then change a button's link somewhere else, delete an element in a different section, and press Undo — the link you changed must still be there. **Watch for:** the wrong element fading out; a button reappearing only after you reload; Undo reverting edits you made in a completely different section.
When you attach a picture and ask a section to match it, the result is now measured before you see it — and corrected once if the headline will not fit or the same photo has been used twice. **Where:** Site editor → open a design → attach a reference image and ask for a section to match it **How to test:** 1. Attach a screenshot of a layout you like and ask for the hero to match it. 2. The headline should be sized so the whole section still fits — the sub-heading, the button and any row of small stats should all be visible without scrolling. 3. If your headline is much longer than the one in your reference, expect smaller type rather than a headline that fills the screen. 4. Check the section is not showing the same photo twice — once as a background and again in a panel. **Watch for:** - A headline so large that the button below it is pushed off screen. That is the case this addresses. - One picture appearing twice in the same section, usually as a faded copy behind itself. - Your wording surviving. When the layout will not hold your copy, the type should shrink first; the assistant should say so if it changes any words.
The site editor showed "This site was changed in another session." after your own AI edit or design switch, prompting a refresh you did not need. **Where:** Site editor → design view (the amber bar above the preview) **How to test:** Open a site's design editor, ask the assistant for a change and let it apply, then switch to another browser tab and back. No warning bar should appear. The bar should still appear if someone else (or you in a second tab) edits the same site while you are away. **Watch for:** The warning failing to appear for a genuine change made in another tab — click Refresh there to pull it in.
When the editor's AI chat made a change that failed to save, the message card still showed a green "Applied" tick — and offered Undo and follow-up suggestions — above text saying the change couldn't be saved. The card now reports the failure honestly and leads with the reason. **Where:** Site editor → AI chat panel (the message card after a request that edits the page) **How to test:** Send an edit request in the chat. On a normal edit nothing changes — the card still shows "Applied", the Undo button, and the follow-up suggestion chips. If a change ever fails to save, the card now shows "Failed", opens with "This change couldn't be saved — please refresh and try again", lists what it had tried to change, and offers neither Undo nor follow-up chips. **Watch for:** A conversational answer (asking the assistant a question rather than requesting a change) must still render as a normal, non-failed reply — not red. Real applied edits must keep their Undo button and their follow-up chips.
When someone browses your site with an AI assistant helping them, that assistant can now find your enquiry forms, fill them in, and — if you allow it — send them, instead of guessing its way around the page. You choose how far it goes. "Fill in and send" lets an assistant complete an enquiry the same as the person typing it themselves. "Fill in only" means it can prepare the form but the person has to press the button. Either way assistants can always read your pages, which is how people find you when they ask an assistant for a recommendation. Enquiries sent by an assistant are labelled in your inbox, so you know a person asked for it but did not type it — worth knowing before you reply. **Where:** Site editor → Settings → General → AI assistants. Labels appear in Site editor → Inbox. **How to test:** Open Settings → General and switch between the two options; the choice saves immediately and applies the next time you publish. Then check your Inbox — enquiries sent by an assistant carry an "Assistant" tag next to the form name. **Watch for:** A sudden rise in enquiries that read as generic or repetitive. If that happens, switch to "Fill in only" — assistants can still fill your forms, but a person has to send them.
Upload a screenshot of the layout you want, click the section, and say "make this like this image" — the section now gets rebuilt to match, instead of the photo being quietly replaced. **Where:** Site editor → open a design → click a section or an image in the preview → attach an image in the chat and describe the change **How to test:** 1. Open a design and click an image inside a section (the hero is the clearest case). 2. Attach a screenshot of a layout you want — a mockup, or a screenshot of another page. 3. Ask for the section to match it: "make the hero section exactly like this image". 4. The section should be rebuilt to follow the reference's layout — column split, headline treatment, button style, any row of small stats along the bottom. 5. Now try the other kind of request on the same selected image: "replace this image with a warehouse worker". Only the picture should change; the layout around it stays put. **Watch for:** - The wrong one happening: a request to rebuild the section that comes back having only changed the picture, or a request to replace a picture that redesigns the whole section around it. - Wording should not decide the outcome. "make the hero like this image", "rebuild the hero to match this", and "make this section look like the attached" are the same request and should all rebuild the section. - Asking to turn a selected image into a video should still open the video picker rather than the code editor. - Your own wording and photos are kept when a section is rebuilt — the reference supplies the layout, not the words.
"Make the typography consistent" was being answered with a list of options rather than actually done. Requests to make things match each other are now carried out. **Where:** Site editor → open a design → describe the change in the chat **How to test:** 1. Ask for a fix in plain words: "make the typography consistent", or "the headings don't match the rest of the page — make the typography consistent". The page should change, not come back with "here are three ways to unify your typography". 2. Same for anything else that should match: "make the buttons all the same style", "the spacing is all over the place, even it out". 3. Now ask instead of telling: "is my typography consistent?" or "how should I make the headings match?". Those should still come back as an answer with suggestions, and change nothing. **Watch for:** - The two behaving the same way. Telling should act; asking should answer. If a question edits your page, or an instruction only replies, note the exact wording. - A follow-up "make it consistent" after a suggestion should apply the change rather than repeat the options.
If you use ChatGPT's desktop app or an AI-enabled Chrome, you can now ask it to build, refine and publish Mondovo sites while you're simply logged in — no connector to install, no approval screen, no API key. **Where:** Open any site in your workspace in ChatGPT desktop's built-in browser (or Chrome with AI features on), then ask it to do the work in plain language. **How to test:** Open a client workspace, ask the browser's assistant to "list my sites", then "add an About page to <site>". It should report the page is queued and then confirm when it lands. **Watch for:** Availability is still narrow — it needs the latest ChatGPT desktop app, and it isn't offered in Enterprise or Edu workspaces. If the assistant tries to click around the page instead of acting directly, the feature isn't switched on in that browser yet. The existing Mondovo connector for Claude and ChatGPT keeps working exactly as before, and remains the way to build sites from a phone or from a conversation that isn't on our site.
Selecting a heading, a paragraph or a button in Edit mode now offers a Delete action in the panel, so removing one no longer requires knowing the right-click shortcut. **Where:** Site editor → Edit → click any heading, paragraph or button in the preview → Quick Actions in the right-hand panel **How to test:** Open a site, click Edit, click a heading in the preview. The right-hand panel should list Longer, Fix readability and Delete. Click Delete, confirm in the dialog, and check the heading is gone from the preview and the change is recorded in Version History. Repeat with a button. **Watch for:** Delete should be the last action in the list, never the first; the confirmation dialog should always appear before anything is removed; images, icons and videos should keep their existing Remove action unchanged.
Asking to take a section off the page now works however you phrase it, and the check that stops a section being deleted by accident no longer switches itself off during ordinary styling edits. **Where:** Site editor → open a design → describe a change in the chat **How to test:** 1. Ask to remove a section in your own words: "we don't need the testimonials section", "get the FAQ off the page", "no more pricing section". Each should remove that section rather than coming back with "I couldn't safely apply that change". 2. Now make an ordinary styling edit that happens to use the same words: "remove the border radius from the buttons", "delete the extra padding under the heading", "strip the shadow off the cards". The styling should change and every section should still be on the page. 3. Same for moving things: "move the testimonials above the pricing section" should reorder the page, while "move the icon to the left of the text" and "swap the button colours" should change only what they name. **Watch for:** - A section quietly missing after an edit you did not expect to remove anything — that is the case this protects against, and it should now be refused rather than saved. - The opposite: a straightforward request to delete a section being refused. If that happens, note the exact wording used. - Requests that name a section explicitly ("remove the team section") and requests that only imply it ("scrap the team bit") should behave the same.
Direct edits made on the preview — deleting an element, moving one, editing text, changing a link or applying formatting — were saving correctly but were not being recorded in version history, so Undo could never reverse them. **Where:** Site editor → click any element on the preview → Delete / Move / Edit text, then use Undo (the button on the change card, or Ctrl+Z) **How to test:** 1. Open a design in the site editor and click an element on the preview (for example an image in the hero). 2. Delete it, and confirm the change card says "Applied". 3. Click Undo on that card. 4. The element should come back, and Version History should show an entry for both the delete and the undo. 5. Repeat with Move up/down, a text edit, and a link change. **Watch for:** Undo reporting success while the element stays deleted — that was the old behaviour. Because the delete had no history entry, Undo skipped past it and restored an *older, unrelated* change instead (for example reverting a header edit made minutes earlier). If you still see a change reported as undone but the page unchanged, note which design you were on and what the previous change was.
When two people (or two browser tabs) had the same site open, switching designs in one could redirect the other's element edits into the wrong design — deleting, moving or retyping something on a design nobody was looking at. **Where:** Site editor → open the same site in two tabs on two different designs → click an element on the preview and use Delete / Move / Edit text / change a link / formatting **How to test:** 1. Open a site with several designs in two browser tabs. 2. In tab A, switch to a different design (say D10). 3. In tab B, still on D9, click an element and delete it. 4. D9 should lose that element. D10 must be untouched. 5. Check Version History on D9 — the change should be listed there, and Undo should reverse it. **Watch for:** An edit that appears to apply but changes nothing on screen (it landed on another design), or a Version History entry showing up under the wrong design. If a design was deleted in another tab while you were editing it, you'll now get "That design no longer exists on this site. Reload the editor and try again." instead of the edit silently going somewhere else.
When an AI assistant refines a site or adds pages for you, that work no longer runs inside the request that started it. You get an immediate confirmation, the work continues on our side, and the assistant checks back until it lands — so a dropped connection or a closed tab no longer leaves you unsure whether your change went through. **Where:** The Mondovo connector in Claude and ChatGPT, the site assistant on WhatsApp and voice, and the public API. Editing directly in the site editor is unchanged. **How to test:** Ask the connector to add an About page, then close the conversation. Reopen the site a couple of minutes later — the page should be there. **Watch for:** Adding several pages at once now reports each page's outcome individually, so a batch can finish with one page flagged as failed while the rest succeed — read the report rather than assuming a finished batch means every page was created. Also, only one operation runs on a site at a time: asking for a refinement while a build is still going now says the site is busy instead of quietly queueing behind it.
Images of branded packaging, labels and signage are now generated by our text-capable AI, so the brand name printed on a pack reads correctly instead of coming back as scrambled lettering. **Where:** Any site with product, packaging or signage imagery — Site Editor → Design, or regenerating images from the image manager. **How to test:** Generate a design for a business whose product carries printed branding — a packaged good, a bottled product, a shop sign. Open the product or feature image at full size and read the text on the object. The brand name should be spelled the way you wrote it. Separately, upload a design reference and ask for a faithful replica: the photography generated from it should now reproduce the reference's own lettering rather than approximating it. **Watch for:** Packaging or signage images that still show scrambled words; ordinary photos (people, interiors, landscapes) that have started showing unwanted text baked into them; or reference-replica images that look flatter or duller than before.
Assistants and integrations that change your site can now attach a picture to show what a section should look like, instead of only describing it in words. **Where:** Anywhere Mondovo is driven through the API or a connected assistant — the `refine_site` tool now takes `image_urls` **How to test:** 1. From a connected assistant, upload an image with `upload_asset` and keep the permanent url it returns. 2. Call `refine_site` with that url in `image_urls` and an instruction that says what to do with it — for example "make the hero section match this layout". 3. The section should be rebuilt to follow the reference's structure, not just its colours. 4. Try passing a url from somewhere other than Mondovo storage. It should be refused with a message telling you to run `upload_asset` first. **Watch for:** - A result that only picked up the colours from your reference and ignored the layout — that suggests the image was not actually looked at. - The reference image itself appearing on the page. It is a guide for the design, not content to insert; to place a photo, say where it goes and give its url in the instruction. - Your existing wording and images should survive a layout change — the reference supplies the structure, not the words.
Per-design preview links handed out by the API pointed at the wrong design on any site where a design had been deleted — and silently, showing a real page rather than an error. Bare preview links now also pin the design they were shared for, so the page doesn't change under the recipient when someone switches designs in the editor. **Where:** Any per-design preview link from the API / assistant tools, and the `preview_url` they return **How to test:** 1. Open a site where at least one design has been deleted, so the chips read something like D1, D2, D3, D4, D8, D9 (numbers skipped). 2. Get its per-design preview links. 3. Open the link labelled D9 — it should show D9. Previously it showed whichever design was currently active. 4. Copy a plain preview link, then switch designs in the editor. Reopen the link: it should still show the design it was copied for. **Watch for:** A link that opens a design different from its label, or a shared link whose content changes after someone switches design in the editor. Both should now be impossible. Sites with only one design still get a plain link with nothing pinned.
Billing changes made through the payment portal — reactivating, cancelling, switching plans — now show up on your billing page again, instead of the page keeping whatever it last knew. **Where:** Organization → Billing **How to test:** Open the payment portal from your billing page, turn a scheduled cancellation off (or back on), return to Billing and reload. The banner and renewal date should match what you just chose within a few seconds. **Watch for:** A billing page that still says "your subscription will be cancelled on <date>" after you have reactivated, or a renewal date that does not move after a plan change. Both mean the update did not reach us.
Returning to the editor window could hijack the canvas with a full-screen "Switching design…" spinner — and sometimes reload the whole page — even though you hadn't clicked a design. It happened after your own edits, not just a teammate's. **Where:** Site editor → make any edit, click to another window or app, then click back **How to test:** 1. Open a design and make any edit (refine something, edit text, replace an image). 2. Click into another window or browser tab, then click back into the editor. 3. Nothing should happen — no spinner, no reload, and the design you were on stays on screen. 4. Now have someone else add or delete a design on the same site. On your next return, the design switcher updates to include it, but your canvas still doesn't move. 5. Switch designs repeatedly on an actively-edited site — it should just switch, never reload the page. **Watch for:** Any full-screen spinner you didn't ask for, or the editor reloading itself mid-session. If someone else is editing the same site, you should now see a small dismissible "changed in another session — Refresh" notice instead, which only applies when you click Refresh.
When you ask the assistant to change a headline, the section list on the left now shows the new wording immediately instead of keeping the old one until you reload. **Where:** Site editor → open a page → Structure panel (left) + Assistant chat (right) **How to test:** Select a section in the Structure panel, ask the assistant to change that section's headline, and wait for "Applied". The canvas and the Structure panel should both show the new headline within a second or two — no reload needed. **Watch for:** A section label that still reads the old headline after the change lands, or the label updating on the canvas but not in the panel.
Three fixes to how AI assistants interact with your published site's forms: the per-site opt-out now applies on republish, assistants can answer multiple-choice questions, and assistant submissions caught as spam no longer count as conversions. **Where:** Site editor → Settings → the AI assistant form controls, and Inbox for the submissions themselves. **How to test:** 1. On a published site, set the form control to "Fill in only" (assistants may fill but not send) and republish. Open the live site and confirm an assistant can no longer send the form — previously this only took effect if you also changed something else on the site. 2. Publish a site with a form containing a multiple-choice question (radio buttons, e.g. "Contact me by: phone / email"). Ask an assistant to fill it in choosing the second option. The correct option should be selected, and the form should send. 3. Check that a submission marked as spam in the Inbox does not appear as a conversion in your analytics. **Watch for:** After this change, the first republish of any site rewrites every page rather than only the changed ones — expect that publish to take longer than usual. Subsequent publishes return to normal. Also confirm that switching the setting back to "Fill in and send" and republishing restores sending.
Images you attach to the chat box now go with your request when you speak it, and the assistant tells you what it can see instead of quietly carrying on. Previously, attaching a screenshot and then asking by voice — "clone this layout into the section I selected" — sent only your words. The image never reached the change, the assistant had no way to know one was attached, and it confidently reported success. The thumbnail stayed on screen the whole time, so there was nothing to suggest it had been missed. **Where:** Site editor → Design view → the assistant chat box → microphone button **How to test:** 1. Open a site in the editor and select a section on the canvas. 2. Attach an image to the chat box with the image button. 3. Start voice mode and say "copy the layout in this image into the section I selected". 4. The assistant should say what it can see — naming the file — before it starts, and the change should reflect the image. 5. Now remove the image and ask the same thing again. It should tell you it can't see an attached image and ask you to attach one, rather than proceeding. 6. You can also attach an image mid-call now — the image button stays available while voice is running. **Watch for:** the assistant claiming to have used an image when nothing is attached; an attachment that is still uploading being treated as ready (it should say it's still uploading and wait); the section you selected being lost when the assistant checks your attachments; and on screens without a chat box, it should say attachments aren't available there rather than asking you to attach one.
If a teammate — or just another one of your own browser tabs — edits a site while you have it open, the editor now tells you instead of quietly showing you a stale copy. The "Switching design…" spinner also can no longer get stuck. **Where:** Site editor → open the same site in two tabs, edit in one, then click back into the other **How to test:** 1. Open a site in two browser tabs. 2. In tab A, make any change — refine something, edit text, or switch to a different design. 3. Click into tab B. A notice appears at the top of the preview: "This site was changed in another session." 4. Click **Refresh** — the preview and Version History update to include tab A's change. Or dismiss it with the × and keep working. 5. Repeat the change in tab B itself and click away and back: no notice, because you made that change. **Watch for:** The notice appearing after one of your *own* edits — that would be wrong. It's meant to fire only for changes made elsewhere, and only when you return to the tab (there's no background polling, by design). Also watch for a "Switching design…" spinner lasting more than about 25 seconds; it should now always clear itself.
Reopening the Brand Launch Kit purchase after closing it could show a "payment complete or timed out" page instead of a payment page, and there was no way to retry for the rest of the day. Checkout now always opens a live payment page. **Where:** Creative → Brand → Launch Kit → purchase **How to test:** Start a Launch Kit purchase, close the Stripe page without paying, then start it again — you should get a working payment page every time, including after a declined card. **Watch for:** A checkout page that opens with "You're all done here" rather than card fields, or a purchase that cannot be restarted.
Seeing all your designs and choosing one is easier to find and harder to misread — the button to compare them now has a name, and choosing one is a proper button instead of a tick icon. **Where:** The site editor while you have more than one design. **How to test:** With two or more designs, look for "All designs (N)" in the editor toolbar and click it. Each card now has a "Use this design" button under it, shows how many pages that design has, and the chosen one is marked "Selected". A line above the grid explains that previews are snapshots. Then click "Build my site" in the toolbar — the confirmation window that opens now says "Start the build" rather than repeating "Build my site". **Watch for:** The compare button missing its label or count; a card where the "Use this design" button does nothing or the page count looks wrong; the confirmation window still saying "Build my site" on its final button.
A workspace that has been deleted now says so plainly on its billing page instead of showing plan and credit packs you cannot actually buy. **Where:** Dashboard → Organizations → (a deleted workspace) → Billing & Subscription **How to test:** Open the billing page for a workspace you have deleted. The Creative Credit packs and the "Add site slot" button are no longer offered. If you reach a purchase another way, it is refused with "This workspace has been deleted, so it can no longer be billed" rather than the old, misleading "Organization not found". **Watch for:** Billing on an active workspace should be completely unchanged — credit packs, site slots and plan changes must all still work normally.
When you asked the assistant to change a selected section, the editor could also rewrite a second, unrelated part of the page — most often the file that lays out the whole homepage — so the result looked nothing like what you asked for. **Where:** Site editor → open a design → select a section → Assistant chat **How to test:** Open a design, click a section to select it, and ask for a change (for example "make it exactly like D1"). Only the section you selected should change; every other section should keep its existing layout and content. **Watch for:** Sections you did not mention changing anyway, the page layout shifting after a single-section edit, or a section losing its buttons or images after the edit is applied.
When you ask for a change, the editor now looks at every section of your site instead of guessing which few to open first. Multi-part requests get done in full, and the change lands sooner. **Where:** Site editor → open a design → Assistant panel. **How to test:** 1. Open a design and ask for several things at once — for example, change the headline, rewrite the steps, and update the examples section. 2. All the parts you asked for should change. Previously some requests came back having done only one or two of them. 3. It should not add a duplicate of a section you already have. 4. Time it — this should be quicker than before, not slower, despite reading more. **Watch for:** a request that still only does part of what you asked; a new section appearing next to an existing one that does the same job; or an edit that takes noticeably longer than it used to.
Workspace owners and admins can now open the hosted billing portal straight from the billing page to update the card on file, download receipts, or cancel and resume a subscription — previously the only action there was "View Invoices". **Where:** Dashboard → your workspace → Billing & Subscription → the plan card at the top ("Manage billing", next to "View Invoices") **How to test:** Open a workspace that has a paid plan with a card on file, click "Manage billing", and confirm the hosted billing page opens for that workspace and returns you to Billing when you're done. **Watch for:** The button is deliberately hidden when there is nothing to manage — a workspace with no paid billing account yet, a deleted workspace, or a member without billing permissions. If a workspace with an active paid plan shows no button, that is worth reporting.
An "Ideas for this section" card written before your latest change now folds into a short history entry instead of sitting in the chat as a live control panel — so you can't apply advice about a design that has already changed. **Where:** Site editor → open a design → the chat panel (desktop) or the chat dock (mobile) **How to test:** Ask for ideas on a section, apply one of them (or make any other change), then look back at the earlier ideas card. It should show its summary with a "superseded" label, its checkboxes and Apply buttons should be gone, and the chevron should let you read the ideas without being able to act on them. A card with only conversation after it stays fully usable. **Watch for:** A card collapsing while it is still the newest thing in the thread, or one staying live after a change has clearly landed. Undoing the change that superseded a card should bring it back to life.
Attaching a screenshot or mockup in the design chat and asking for that look now makes the change straight away, instead of opening a review with options to pick through. Attached pictures also show properly in the chat again, and when the editor does suggest ideas, it describes them in plain language. **Where:** Site editor → open a design → Assistant panel. Select a section, attach an image, describe the change. **How to test:** 1. Open a design and click a section in the preview so it is selected. 2. Attach a picture of the layout you want and say "make this section like this". 3. It should rebuild the section. It should not reply with a list of recommendations, and it should never ask you to send the picture you just sent. 4. Check the message you sent in the chat history — the attached picture should show as a thumbnail, not a broken-image icon. 5. Ask a question instead ("what do you think of this?") with a picture attached. That should still come back as advice, not an edit. **Watch for:** an edit that runs when you only wanted an opinion; a thumbnail that still fails to load after a page refresh; suggestions that mention class names, pixel values, or phrases like "vertical rhythm" — all of those should now be described in ordinary words.
Moving a contact to a different stage now records the change on their Activity timeline and starts any automation waiting on that stage — previously the stage saved but nothing else happened. **Where:** A client's Contacts list or a contact's detail page, then change the stage. Automations live under Automations → Journeys. **How to test:** Move a contact to a new stage, then open that contact's Activity tab — the change should be listed. If you have a journey that starts on a stage change, it should now begin. Move the contact to the same stage twice; the second save should not repeat the timeline entry or re-run the automation. On a site with custom stage names, saving one of your own stages should work rather than being rejected. Delete a contact that has open tasks and confirm those tasks leave both the task list and the overdue count. **Watch for:** A stage you know exists being refused; a stage change that saves but shows nothing on the timeline; automations firing twice for one move; tasks lingering after their contact is deleted; conversion figures on Lead Sources reading zero when your won stage has been renamed.
Clicking "Design D10" in the preview toolbar put `?s=design-9` in the address bar, which read as though you were looking at a different design. The link now says what the chip says. The toolbar also stays open when you switch between designs — it only closes when you click Hide, and it remembers that per site. **Where:** Any site preview link — the dark toolbar across the top. **How to test:** Open a preview with more than one design, click through the design chips and check the address bar matches the chip. Open the toolbar, switch designs a few times, reload — it should still be open. Click Hide, switch again — it should stay hidden. **Watch for:** Older links you have already shared still point at the same designs they always did; nothing was repointed.
If your workspace already had a live site from before you upgraded, the "Make it live" step could say the next site was included in your plan and then bill it as an extra — now the price you confirm is the price you pay. **Where:** Site editor → Publish changes → "Make it live"; also the Live sites card on Settings → Billing. **How to test:** On a workspace whose first site went live before the upgrade, open a second site and start publishing. The confirmation should read "$20/month" and the button should say "Publish — $20/month". Check the Live sites card: the complimentary + paid overage figures should add up to the live-site count. **Watch for:** A first-ever site on an empty workspace must still read "included in your plan"; a workspace holding a prepaid slot should offer that slot before charging anything new.
Opening billing for a deleted workspace used to show an empty page with a plan grid on it — so you could pick a plan that would then be refused. It now explains that the workspace has been deleted and points you back to your workspaces instead. **Where:** Dashboard → your organization → Billing & Subscription **How to test:** Open Billing for a workspace that has been deleted. You should see "This workspace has been deleted" with a link back to your workspaces, and no plan options. On an active workspace, everything behaves as before: Current Plan, Manage billing, View Invoices and the plan grid. The "Back to Organization" link at the top now lands on your workspace settings instead of a missing page. **Watch for:** A blank billing page with no explanation; plan options still offered on a deleted workspace; a plan panel that fails to load on an active workspace with no error shown; or "Back to Organization" leading to a not-found page.
Choosing a design takes you straight into the editor instead of leaving you on the grid, the screen says what it's for, and there's a clear way to say none of them are right. **Where:** The site editor, on the screen showing all your designs. **How to test:** Open a site with more than one design. The top of the screen should read "Pick a design to build on — you can switch any time", and while designs are still being made it should say how many more are coming. Click "Open this design" on any card — you should land in the editor on that design, where "Build my site" is. Scroll to the last tile: it should invite you to say what you'd change rather than just counting your designs. **Watch for:** "Open this design" changing the card but leaving you on the grid; the count of designs still coming not going down as they arrive; the last tile still reading like a quota.
If a workspace had previously cancelled Pro, paying to upgrade again could complete at checkout and then quietly leave the workspace on the Free plan — the new subscription was cancelled moments after it was paid for. Re-upgrades now activate correctly. **Where:** Workspace settings → Billing & Subscription → "Upgrade to Pro" **How to test:** Use a workspace that was on Pro and then reverted to Free, click Upgrade to Pro, and complete checkout (including the card-authentication step). The billing page should show Current Plan: Pro, and the subscription should stay active. **Watch for:** A workspace that still reads "Free" after checkout closes, or a plan that flips back to Free within a minute.
If you cancelled Pro and later decided to come back, the upgrade failed with an error instead of opening checkout — that's fixed, and re-subscribing now starts a fresh checkout as expected. **Where:** Dashboard → your organization → Billing & Subscription **How to test:** On a workspace that previously cancelled a Pro subscription, click "Upgrade to Pro — $20/mo", then Confirm. The Stripe checkout panel should open on the Pro plan. **Watch for:** An error message instead of the checkout panel; a checkout that opens on the wrong plan or amount; or the workspace still showing Free after a completed payment. Downgrading back to Free from a workspace whose subscription was already cancelled should also complete cleanly rather than erroring.
When a batch of designs finishes, you're taken to all of them side by side instead of a single one, designs still being made hold their place instead of looking broken, and you can ask for another design based on any one you like. **Where:** The site editor, straight after designs finish generating. **How to test:** Generate designs for a site and wait. When they're ready you should land on the grid showing all of them, with any that are still rendering saying "Designing D2…" and filling in on their own. A design that couldn't be created shows a short explanation instead of disappearing. Hover any finished design and click "More like this" to ask for a new one based on it. Press the browser Back button — it should return you to the single design, not throw you out of the editor. Revisit the site later and you should go straight to the design you were working on, not back to the grid. **Watch for:** Landing on the grid every single time you open the site, rather than only after new designs finish; a design that finished but still says "Designing"; "More like this" opening a blank request rather than one based on the design you clicked.
There's now a plain-English guide explaining how your site sends email, how to verify your own sending domain, and how to stay out of the spam folder — linked from the exact moment you need it. **Where:** app.mondovo.com/help/email, and from the message you see if a campaign refuses to send. **How to test:** Open the guide directly, or try sending a campaign before verifying a domain — the refusal now carries a "How sending domains work" link straight to the relevant section. **Watch for:** if too many people mark your campaigns as spam, sending pauses automatically until the rate recovers. That protects your own form notifications as much as anyone else's, and lifts on its own as older complaints age out — there's nothing to switch back on.
"Make my hero look like stripe.com" now changes the hero on the first try, instead of replying "I wasn't able to make the requested changes — try rephrasing" or quietly rebuilding the whole page. **Where:** Site editor → Assistant panel (the chat beside the preview) **How to test:** Open a site on any design and send a request that names one section and points at an outside site, e.g. "make my hero look like https://stripe.com". The assistant should apply a restyle to that section, keeping your own words and images, on the first message — no need to send it twice. **Watch for:** The change should stay inside the section you named — the rest of the page should be untouched, and no section should end up duplicated. A request that re-aims the whole page instead ("make the site feel like Apple") should still offer you a new design direction to confirm, and that offer should now appear rather than being swallowed. The "show me templates" reply should again come with a browse button attached.
Opening a design from a board used to land you on whichever design that site was currently set to — so every option pinned from the same site opened the same thing. The link now carries the pinned design, so you get the one you clicked. **Where:** Clients → a client → Boards → open a board → any option card → "Open in editor" **How to test:** Pin two or more designs from the SAME site to one board. Open each card's "Open in editor" in turn. Each should land on its own design — check the design number in the editor matches the card, and that the URL ends in `?variation=D…`. **Watch for:** Options pinned from a different client's site should still open under that site's own client. If a pinned design was since deleted, the link falls back to opening the site — it should never open a different design as if it were the pinned one.
Adding a live-site slot used to show "Successfully added 1 live-site slot" while the card still displayed the old count and offered the purchase button again — only a page reload revealed the slot you had just paid for. The count, the prepaid slot list, and the notice now appear together, and your invoices show the charge. **Where:** Workspace → Billing & Subscription → Live sites card **How to test:** On a Pro workspace, click "Add site slot", confirm, and watch the card the instant the green notice appears — the slot count should already include the new slot and the slot should be listed below it. Then open "View Invoices" and confirm the prorated charge is listed. **Watch for:** A success notice next to an unchanged count; a purchase button that stays available after a successful buy; an empty invoice list on a workspace that has been charged.
Each plan includes a monthly number of campaign emails, and you'll see exactly where you stand before a send rather than after. **Where:** Site editor → Leads → Inbox → Campaigns, when you press Send. **How to test:** Build a campaign whose audience is larger than the allowance you have left. The send is refused before anything goes out, and the message names how many you tried to reach, how many you have left, and the three ways forward — narrow the audience, wait for the reset, or upgrade. **Watch for:** the allowance counts people you actually emailed. Anyone skipped for having unsubscribed doesn't count against you — honouring an opt-out should never cost you anything. The allowance resets at the start of each calendar month.
When you added a collection to a site where a design had previously been deleted, the new listing and detail pages could be built against a different design's layout and styling than the one they were saved to. **Where:** Site editor → Pages → add a collection (or any flow that creates one) **How to test:** On a site where you've deleted at least one design, add a collection. Open the new listing page under each design in turn — each should carry that design's own header, footer, colours and typography. **Watch for:** A collection page that looks like a different design's page, or whose header/footer don't match the rest of the design it sits under.
Searching your dashboard by what a business *is* — "food", "fitness", "dental" — stopped working for anything built since roughly May, and hovering a site with several designs now tells you what each one actually looks like. **Where:** Dashboard → the search box above your site list, and any site card showing more than one design. **How to test:** 1. Go to your dashboard and search for a business by industry or description rather than its exact name — for example "restaurant" or "plumber". Sites whose *name* contains none of those words should still appear if that's what the business does. 2. Find a site card with several designs and hover it. The thumbnails cycle as before, but each now shows its design number (D1, D2, …) plus a one-line description such as "Earthy terracotta + charcoal, high-density" — so two cards for the same business are finally tellable apart. **Watch for:** - A site created in the last few minutes may take up to 15 minutes before it answers description-style searches; searching by name works immediately. - Designs generated before this rolled out don't all carry a description. Where one is missing, the card shows the design number alone rather than an empty caption. - The design numbers on hover should match the numbers in the design picker when you open the site. If a design has no thumbnail yet it is skipped in the cycle, but the remaining numbers should not shift.
Hovering a design on a board scrolls through the whole page preview at the same pace as the templates gallery, instead of using a separate, slower animation. **Where:** Clients → pick a client → Presentations → open a board. Also on the shared client-facing board link. **How to test:** Open a board with several pinned designs and rest your pointer on one. The preview should scroll from the top of the page to the bottom, then ease back when you move away. Tab to a design with the keyboard — it should do the same. Clicking still opens the full-page preview. **Watch for:** Cards that sit frozen on hover; a preview that jumps or scrolls past the bottom of the page into blank space; the "Hover to tour page" caption showing on a touch device (it should read "Tap to expand"); more than six cards animating at once on a large board. If your computer has animations turned off system-wide (Windows: Settings → Accessibility → Visual effects → Animation effects), previews stay still by design.
A design that lays out a section but has no content to put in it is now caught and repaired before you see it, instead of shipping as a blank band on the page. **Where:** Any newly generated design — most visible on sites recreated faithfully from a long reference, which have many similar sections. **How to test:** Generate a site from a reference with a long sequence of sections (a timeline, a step-by-step story, an FAQ). Scroll the whole page: every section should have a heading and content, with no empty gaps between the ones that are filled in. **Watch for:** A section that renders as blank space, or a heading with nothing under it.
Every lead already arrives tagged with where it came from — which form, which source. You can now actually filter by those tags, edit them yourself, and give your form fields proper names so the answers stop reading like raw data. **Where:** Site editor → Leads → Inbox → Contacts for the list and its new tag filter; open any contact to edit their tags and fields. **How to test:** Open the Contacts list and pick a tag from the filter — add a second one and the list narrows to contacts carrying *both*, not either. Open a contact: add or remove a tag on their record, and fill in their fields. Any form answer you have not described yet still shows up, under "Other form answers", so nothing is hidden. **Watch for:** tags that look near-identical (`block:contact` next to `block:Contact Form`) — those came from older auto-tagging and are shown exactly as stored, so pick from the list rather than typing. Notes also now appear on a contact's Activity timeline, which they never used to.
Leads can now be assigned to someone on your team, carry follow-up tasks with due dates, and move through stages you name yourself. **Where:** Site editor → Leads → Inbox. Open any contact for its owner and Tasks tab; the contacts list gains a "My leads" filter and an owner column. **How to test:** Open a contact, pick an owner — they get an email. Add a task with a due date and it appears on their list, overdue ones first. To rename your pipeline, set your own stages and mark which one counts as won; contacts already on an old stage stay where they are until you move them. **Watch for:** you can only assign to people who can already open the site. Deleting a stage does not move anyone off it — they stay put and reappear if you add it back, so nothing is lost by experimenting.
On some designs the properties panel offered an editable heading that silently discarded whatever you typed. Those fields are no longer shown, so what you can edit is what actually saves. **Where:** Site editor — select a section and use the properties panel on the right. **How to test:** Click through the sections of a design and edit a heading or paragraph in the right-hand panel. Every field offered should update the preview as you type and persist after you leave it. **Watch for:** A field that accepts text but leaves the preview unchanged — that is the failure this removes. Sections whose names contain hyphens are unaffected and stay fully editable.
Pasting a link to one of your own designs into the design assistant now works — the assistant reads that design's real code and copies from it, instead of asking you for the link you just gave it. **Where:** Site editor → Assistant panel (the chat beside the preview) **How to test:** Open a site with several designs, copy the address-bar link for one of them (for example the one ending `?variation=D9`), switch to a different design, then paste that link into the chat with a request like "copy the hero section from this and change the current one". The assistant should make the change rather than reply asking for a URL. **Watch for:** A link to a design you can't open, or to one that has been deleted, should now say so plainly and offer to work from a screenshot or one of your other designs. Links to other companies' websites are now opened too — see "Paste any website link in design chat and the assistant matches its look". The assistant should also never ask you the same question twice in a row.
You can now point the design assistant at someone else's website — "make my hero look like https://stripe.com" — and it opens that page, looks at it, and restyles your section to match. Previously it could only work from your own designs or an image you uploaded. **Where:** Site editor → design chat (the AI panel beside the preview) **How to test:** 1. Open a site in the editor and select a design. 2. In the chat, paste a public website link with a request, e.g. `restyle the booking section to match the visual style of https://stripe.com`. 3. Wait for the reply — the section should come back restyled in that site's visual direction (colours, spacing, typography), using your own text and images. 4. Now try a link that cannot be opened, e.g. `make the booking section look like https://not-a-real-site.example-invalid`. You should get a short explanation of why it could not be used, plus buttons to use one of your own designs instead — and **nothing on your site should change**. **Watch for:** - Any claim that a change was applied when your page did not actually change. A link that cannot be opened must always end with "nothing changed", never a silent edit. - The assistant asking you for the link you already pasted — that is the loop this replaces. - The reference site's own text, logo or screenshot being copied into your page. It should only guide the styling; your content stays yours. - Links to your own designs (an editor link or a share link) should still load that design's real layout, not a picture of a sign-in page. - The reply takes longer than usual — opening the page adds roughly 10–20 seconds before the edit starts.