When you chose a design in the "Pick a design you like" question, the finished site often looked nothing like it. Your pick now drives the first design directly — including a picture of the template handed to the design AI — while the second option stays a deliberate alternative in the same family. **Where:** Site setup form (the questionnaire in chat) → "Pick a design you like" → then generate. **How to test:** Start a new site, pick a template with a distinctive look (a warm, elegant one is easiest to judge), and generate. Design 1 should clearly share that template's palette, typography and spacing. Design 2 should feel related but laid out differently. **Watch for:** Design 1 drifting to a generic minimal look; Design 1 and 2 looking near-identical; or wording and sections from the template's own business (a different industry) turning up in your site — copy and sections should come only from your brief.
Catalog cards (real estate properties, products, rooms, cars) now reliably display their images instead of a "No Image" placeholder. **Where:** Any generated catalog site — homepage listing grids and individual detail pages. **How to test:** Open a real-estate or product site in the editor preview; every card should show its photo. Republish to update a live site. **Watch for:** Cards still showing "No Image" — that now means the row genuinely has no image assigned in the Content Manager.
When we found public information about a business on the same turn it was named, the setup questions we had just prepared (location, services, look and feel, template preference) were quietly dropped and never came back — so the plan was proposed without ever asking. The questions are now held and asked right after you accept or ignore the public information, which is also when we can tell which ones are still worth asking. **Where:** Site builder chat — the first few turns after you describe your business. **How to test:** Start a new site for a real, findable business (a named local shop or agency). When the "use these public details?" card appears, accept or ignore it. The intake questions should appear on the very next turn instead of jumping straight to a section plan. Existing sites that already lost their questions this way get them back on the next message. **Watch for:** The questions appearing twice, or appearing after you have already answered them — neither should happen; a form you were actually shown is never re-asked.
After the setup form was correctly re-offered following a delay, an internal marker meant to close out that obligation wasn't actually being cleared — which could cause the same follow-up to misfire later in the conversation. **Where:** Site builder chat — the setup questions flow (after the AI does its own research on your business). **How to test:** Start a new site, let the AI find your business online, respond to the research prompt, and confirm the setup questions arrive once and don't reappear unexpectedly later in the conversation.
A site could have one catalog section (for example, a properties or menu grid) that never showed its items, while a different section on the same page pulling from the same data displayed correctly. The affected section is now resolved the same way as every other collection-backed section. **Where:** Any generated site with more than one section pulling from the same collection (e.g. two different property or menu displays). **How to test:** Open a design with two sections drawing from the same collection (a "Featured" section and a full listing section). Reload a few times — both should consistently show their items, not just one of them. **Watch for:** A catalog section stuck on "New listings will appear here once published" while a sibling section with the same data displays fine.
The template detail view showed two buttons — "Use this design" and "Use the look only" — that both did exactly the same thing. There's now a single, clearly labeled "Use as inspiration" button. **Where:** /templates → click any template → detail view (and the hover button on a template card). **How to test:** Open the public template gallery, open a template's detail view, and confirm there's one "Use as inspiration" button, not two.
After a build finished, nothing pointed you toward making the site live — now there's a clear next step, in the app and in the email. **Where:** The editor header after a build completes, and the "your site is built" email. **How to test:** Build a site. When it finishes, the "Design → Build → Live" indicator in the editor header now shows an actionable **Go live** button (it opens the publish/domain dialog). The completion popup notes the site isn't live yet. The email now says the site is built but not yet live and links straight to the publish step. **Watch for:** The **Go live** CTA should only appear while the site is built-but-unpublished — once published it returns to a passive "Live" label. The email link (`?action=publish`) should auto-open the publish dialog on arrival.
When we build a form for you automatically, every part of it — field labels, hints, dropdown choices, the button and the thank-you message — is now written in your site's language instead of English. **Where:** Site editor → Forms (and any form the builder adds for you while generating or extracting a site) **How to test:** Create or extract a site whose language is not English, then open Forms. Check a richer form such as a quote or project inquiry: "Budget Range", "Timeline", "Company Size" and their dropdown options should all be in your language, and each form should keep its own button wording (for example "Send Inquiry" vs "Book Now") rather than a generic "Submit". **Watch for:** Dropdown values that are only numbers or price bands (1-10, 500+, $1,000 - $5,000) are intentionally left as-is. Sample email addresses and phone numbers also stay in their original format. Forms you have already edited yourself are never overwritten.
Clicking "Build my site" used to leave you back on the design screen with no sign anything had happened, so people clicked it again and ended up with two separate copies of their site being built. **Where:** Site design screen → "Build my site" **How to test:** Pick a design, click "Build my site", choose your pages and confirm. A "Your site is being built" screen should hold until your site opens — and if you retry the button, you land in the same build rather than a second one. **Watch for:** A second site appearing named "— Build 2" that you did not ask for, or the design screen becoming clickable again before your site opens.
Every built-in feature on a published site — cart, checkout, customer portal, booking and inquiry forms, product pages, galleries, catalogs and funnels — now shows its buttons, labels, placeholders and error messages in the site's language instead of English. **Where:** Any published non-English site. The built-in blocks (cart, checkout, /account portal, booking widget, quote form, product detail, order confirmation, help centre, listings and funnel pages). **How to test:** Set a site's language to something other than English, publish it, then open the storefront. Add an item to the cart, open the cart drawer and the checkout, and visit `/account` — the interface copy should be translated, not just the content you wrote. Publish an English site and confirm nothing changed. **Watch for:** A stray English label in a built-in block; a translated string that no longer fits its button; or a form field label that changed while the form's saved submissions still use the old one.
The pre-plan business questionnaire now shows the full set of questions — target audience, services, what sets you apart, primary goal, must-haves, a "what should visitors do" (Call / WhatsApp / Book / Buy) choice, and the visual design picker — instead of only the handful of basic logistics questions. Richer answers up front mean a more relevant, less generic first draft. **Where:** Start a new site and describe your business in the builder chat — the intake form that appears now asks 9–12 questions (grouped, with a stepper on mobile). **How to test:** Begin a new site with a short pitch (e.g. "a website for my plumbing business"). Confirm the intake form includes questions about your audience, services, USP, the action you want visitors to take, and a "pick a design you like" picker — not just name/location/light-or-dark. **Watch for:** The form should still stay tight for quick mid-chat follow-up questions (those remain 3–4 at a time). The primary intake is the one that should be complete.
The buyer cart drawer now fetches and displays the server-priced Subtotal, Tax, Shipping and Total for simple (no-variant) products, not just for products with selectable variants. **Where:** Published storefront → add a single-SKU product to the cart → open the cart drawer. **How to test:** On a store with tax and/or shipping rules configured, add a no-variant product and open the cart drawer. You should see distinct Subtotal / Tax / Shipping / Total lines (where applicable) plus the discount-code field, matching what checkout will charge. **Watch for:** Products with variants should still price correctly; legacy carts (items without a product id) should still fall back to the local subtotal display. Tax on destination-based rules still resolves at checkout once the shipping address is entered.
Ask the editor to pull in data from an address that needs a key, and it now opens a secure box for the key instead of sending you off to Settings. **Where:** Site editor → chat with the design assistant. Ask it to fill a section from one of your own web addresses, e.g. "show our live stock levels from https://api.yourcompany.com/v1/items". **How to test:** 1. Open a site in the editor and ask the chat to pull a list from an address of yours that requires a key. 2. The assistant tests the address, sees it refuse, and opens a "Connect a private data source" box. 3. Choose how the address expects the key (a bearer token, a header, or a value on the URL), paste the key, and hit Connect. 4. The box closes and your original request carries on automatically — the section gets bound to the new connection. 5. Republish, or sync the source under Settings → Data Sources, to see the data on the live site. **Watch for:** the key must never appear anywhere in the chat — not in your message, not in the assistant's reply, not in an error. The assistant should never ask you to type a key into the chat itself; it should always open the box. A public address that needs no key must still connect in one step, with no box at all.
When a generated contact form built its fields dynamically, the editor filled in English labels and an English thank-you message even on sites built in another language — now that fallback copy speaks the site's language. **Where:** Site editor → open any non-English site → a section containing a contact or enquiry form → Forms in the left rail **How to test:** Open a site whose language is not English and that has a form whose inputs are generated from a list. Let the preview compile, then check the Forms list: the field labels and the success message should be in the site's language, not "Full Name / Email / Message" and "Thank you! We'll be in touch." **Watch for:** Field labels reverting to English after a refinement or a design switch; a success message that stays English while the labels are translated; forms that already carried their own success message being overwritten.
You can now correct the wording of the platform's built-in storefront labels — "Add to Cart", "Subtotal", "Place order", "Filters" — per site and per language, instead of living with an automatic translation that reads wrong for your market. **Where:** Ask the AI assistant in the site editor, e.g. "the cart button should say Añadir al carrito, not Agregar al carro". **How to test:** Open a store site in the editor, ask the assistant to list the built-in cart labels, then ask it to change one. Publish the site and check the label on the live storefront. Ask it to "put the cart button back to the automatic translation" to undo. **Watch for:** Changes only appear on the live site after you publish. If you ask for wording in a language the site doesn't publish, the assistant will tell you it won't show up anywhere yet.
The legibility check that keeps text readable could not see hero background images that are shown conditionally, so it mistook a dark photo hero for a white page and rewrote white headline text to black — making it nearly invisible over the photo. **Where:** Any generated site with a hero that shows a background image plus a dark gradient over it. **How to test:** 1. Generate a site whose hero uses a background photo with a dark gradient scrim. 2. Confirm the headline stays white (and any accent line keeps its accent colour) instead of turning black. 3. Open the design preview and the published page — both should now agree with each other. **Watch for:** - Some existing sites still have black headline text saved in their design from before this fix. Those need a one-off repair pass; a preview showing a black headline over a dark photo is stored data, not a preview glitch. - The check still fixes genuinely unreadable text; it only stops treating photo-backed heroes as light backgrounds. - Design previews also no longer force permanently-visible hover overlays (captions, "view details" scrims) to show, so previews match what a visitor sees more closely.
When we detect a contact form in your site's design and register it for you, we now keep the confirmation message your site already uses instead of replacing it with an English one. **Where:** Site editor → open any page with a contact or enquiry form → Forms panel (the form entry the editor registers automatically) **How to test:** Open a site built in a language other than English, view a page with a form, then check that form in the Forms panel. The "thank you" message shown after someone submits should be in the site's language — matching what the page itself displays. Submit the form in the preview to confirm the visitor sees the same wording. **Watch for:** An English "Thank you! We'll be in touch." on a non-English site; a form whose field labels come back as Name / Email / Message in English when the rest of the page is translated.
Adding a translation language no longer renames the internal field keys on your forms, so submissions from a translated page arrive with the same field names as your original-language page. **Where:** Site editor → Settings → Languages → add a language, then Forms → Inbox **How to test:** On a site that has a form, add a non-English language and let the translation finish. Switch the site to that language, submit the form, and open the submission in Inbox — every answer should be filed under the same field it would use in English (Email under Email, and so on). Field labels, placeholders and dropdown choices should all appear translated. **Watch for:** Answers landing under oddly-named or blank fields, an answer disappearing from a submission, or a form's display name staying in English when its labels translated.
Prompts for grocery, supermarket, kirana, or general-store businesses now generate a true ecommerce site — a product catalog with per-item prices and an add-to-cart/checkout flow — instead of a generic phone/WhatsApp order page. **Where:** Site generation for grocery/supermarket-style business prompts. **How to test:** Create a site describing a grocery store with itemized products and prices, run generation, and confirm the result has a product catalog and cart/checkout (not just an "order by phone" form). **Watch for:** The industry resolving to E-Commerce so the catalog/collection planner and cart features are included.
Asking for a new design while reusing an existing design's copy now actually gives you a new layout — and your phone number, prices, hours and testimonials can no longer be rewritten by the generator. **Where:** Site editor → design gallery → "Regenerate with feedback" **How to test:** 1. Open a site with at least two designs where the second has its own content. 2. Click "Regenerate with feedback" and type something like "give me a dark editorial layout". 3. Leave the new option on "Try a different direction", and set "Use content from" to the second design. 4. Generate, then compare: the copy should carry over, the layout should be visibly different. 5. Check the contact block, prices and testimonials against the original — every one should match exactly. 6. Repeat with "Refine this design (keep the layout)" selected: the layout should stay put and only your requested change should land. **Watch for:** a "new direction" that comes back looking like the previous design; a phone number, price, opening hours or testimonial that changed on its own; copy that ignores an explicit request to reword it.
When you add a form to a non-English site, its field labels, button and thank-you message now come out in your site's language instead of English. **Where:** Site editor → click any button → "Link to form" → Create → choose a template. Also Mission Control → Forms → Settings. **How to test:** Open a site whose language is set to something other than English, add a form from a template, and check the preview — the name, email and message labels, the submit button and the success message should all be in the site's language before you save. **Watch for:** English sites should look exactly as they did before. Template-specific extras (budget ranges, company size, dropdown options) can still appear in English on languages we don't yet carry a translation for — those fall back rather than coming out blank.
Built-in booking, cart, checkout, customer-portal and pricing components had a handful of labels, success messages and error messages that stayed in English on translated sites — things like "Checkout", "Currency", "Share selection", "Request a Booking" and the cart's payment errors. They now translate with the rest of the site, and the check that catches untranslated text was widened so this class of string can't slip through again. **Where:** Any published site whose language is not English — booking forms, job-application forms, the cart drawer and discount box, checkout, the customer area, the pricing monthly/annual toggle, and the saved-selection share bar. **How to test:** Publish a site in a non-English language that uses any of those components, open the published page, and confirm the headings, button labels, success messages and error messages appear in the site language. English sites are unchanged — the wording is identical to before. **Watch for:** A string that renders as a raw key instead of words, or a mixed page where most text is translated but one label is still English.
Translating a site into another language kept the design intact instead of rewriting layout and style values as if they were text. **Where:** Any multi-language site with forms — the translated language version of the page. **How to test:** Add a second language to a site that has an inline or modal form, translate it, then view the translated language. Field widths, alignment, spacing, colors, and CSS classes should look identical to the original language. **Watch for:** Form fields stacking or misaligning, headings losing their alignment, or broken styling that only appears in the translated language and not the original.
Typing `@` in the assistant now lists your real designs with their correct D-numbers, instead of an extra "D1 (Original)" entry that pointed at nothing. **Where:** Site editor → assistant chat box → type `@` **How to test:** Open a site with two designs and type `@`. You should see exactly two entries, D1 and D2 — no third "Original" row, and no design labelled one number too high. Type `@` on a build site and you should see only the design it was built from. Expand another site in the same list and its designs should now appear too. **Watch for:** A design listed twice, a first design labelled "D2", an "Original" entry on a site that never had a pre-variation original, or another site expanding to show no designs at all.
When your site plan is ready, the chat now shows a one-tap tip that switches the Plan panel to Wireframe view — so you can see your layout visually instead of hunting for the toggle. **Where:** Site Builder — the chat, right when your plan is drafted (desktop). **How to test:** Start a site and chat until a plan is drafted (or click Preview Plan). In the assistant's plan-ready message, click "Tip: switch the Plan panel to Wireframe". The workspace opens the Plan tab in Wireframe view. **Watch for:** The tip should appear only when a real plan first lands (not on every message), and clicking it should land you directly on the visual wireframe, not the list.
Asking for four ad variations used to give you the same idea four times with a slightly different photo. Now each one is a genuinely different concept — a different kind of image, with its own headline and offer — and you can drop the ones you don't like before spending a single credit. **Where:** Brand Studio → Create → pick Ad creative, Social post, or Banner → Configure → Review. **How to test:** 1. Open Brand Studio → Create and choose "Ad creative". 2. On Configure, set "How many concepts" to 4 and continue to Review. 3. You should see 4 named concepts, each with a one-line note saying what it does that the others don't — one might be the product itself, another the place, another a screen, another people. 4. Untick one. The credit cost should drop straight away. 5. Generate. Each result card is titled with its concept name rather than "Variant 1", and the images should be visibly different kinds of picture — not four takes on the same scene. **Watch for:** - Two concepts that are obviously the same kind of shot. Some businesses genuinely only support two or three angles, in which case you'll see fewer concepts than you asked for and a note explaining why — that's intended. Four concepts that are all people is not. - Any price, discount, or guarantee in the suggested copy that you never told us about. Copy can only make a claim it can trace back to something in your brand details or your request; anything else is now blanked out before you see it. If an invented offer slips through, that is a bug worth reporting immediately. - Copy that wraps awkwardly on the finished image. Suggested headlines are now sized to the exact format you picked, so they should fit without editing.
Ad and social creatives were being generated without any of your headline, offer or button text visible, and the imagery behind them was often generic stock-style filler. Both are fixed. **Where:** Creative Studio → pick a brand → Create → Output, Configure, Review, Generate **How to test:** 1. Open Creative Studio and start a new creation for any brand. 2. Choose an Ad, pick a campaign goal, and enter a short prompt (or leave it blank). 3. On the Review step, read the proposed image description before generating — it should name a specific subject, place, time of day and lighting, not "a modern flat-lay on a clean desk". 4. Generate, then check the finished creative: your headline, offer and button label must all be readable in the image, in the bottom band. 5. Try a Logo → Launch Kit lockup as well; the brand name must be readable in the exported PNG. **Watch for:** - Any creative that still comes back with an empty dark bar and no readable words in it. - A button label that overflows or is clipped by its pill. - Words in the generated photo itself — signage, screen text, labels. The picture should contain no readable text at all; all wording is added afterwards. - Image descriptions that fall back to stock clichés (desks with coffee cups, glowing brains, floating dashboards, teams high-fiving). - Accented characters, currency symbols and quotes rendering correctly in the overlaid copy.
Sites written in a right-to-left language now publish with the correct text direction, and the built-in cart, checkout, customer portal, tabs, accordions and docs navigation mirror along with them. **Where:** Any site whose language is Arabic, Hebrew, Persian or Urdu — set during generation or in Settings, then Publish. **How to test:** Publish a site in one of those languages and open it. Text should read right-to-left, the mini-cart dropdown and its item count badge should sit on the left, portal amounts and table headers should align to the right edge, and the docs sidebar and its mobile drawer should open from the right. **Watch for:** A page that still reads left-to-right after publishing, a cart badge or dropdown stuck on the wrong side, or a docs drawer that stays on screen instead of sliding away.
You can now refer to your other designs by name in the editor chat — "make this section better, like D2", "use the layout from the second variation", "the dark one" — and the assistant loads that design's real code before making the change instead of guessing. It also tells the difference between a screenshot you paste to point at something and a reference design you want it to match. **Where:** Site editor → open any design → Assistant panel (right side) **How to test:** 1. Open a site with two or more designs (D1, D2, …) and switch to one of them. 2. Ask for a change that references another design by name: "make this section look more like D2". 3. It should apply the change directly, borrowing from that design — not reply asking which elements you meant. 4. Try the looser phrasings too: "the second variation", "the first one you made", or a description like "the dark one". 5. Now screenshot your own page, paste it in, and say "make this section better". It should treat the screenshot as *where to look*, not as the result you want. **Watch for:** A change that borrows from the wrong design; the assistant still asking you to clarify after you named a design; a pasted screenshot of your own page being copied into the design instead of being used as a pointer. If you genuinely want it to match a reference image, say so ("make it look like this") — that still works.
Clicking "New Design" after you've already seen a round now asks one quick question — grounded in the designs on your screen, like "These both came out light and editorial, what would you like different?" — instead of silently re-rolling and hoping. Your answer locks what you liked, changes what you didn't, and is remembered for every future round. After two unsatisfying rounds, we also suggest a few templates matched to what you said was wrong, alongside the normal generate button. The same idea now applies before your very first drafts: when we know too little about your taste (no style, no references, no history), we ask one direction question — "warmer", "more minimal", or your own words — with a "Just pick for me" escape, so round one starts from your answer instead of a guess. **Where:** Site builder → the "New Design" card in the design gallery (also the preview toolbar's generate button). **How to test:** Generate a site, then click "New Design" without typing any feedback. A card should appear with options grounded in your existing designs plus a "Just surprise me" escape. Pick an option — the next generation should honour it (e.g. "keep the colours" keeps the exact palette). Click "New Design" a third time and template suggestions should appear next to the question. Skipping the card lands you on the usual three-path picker. **Watch for:** Being asked twice in a row (should never happen — one question max, then it generates), the card blocking generation when the answer service is slow or down (it should fall through to the old behaviour), and "surprise me" returning a design nearly identical to what you already have.
Applying a section background (or any other one-click style change) in the site editor now updates the live preview immediately, instead of looking like nothing happened until you reloaded the page. **Where:** Site editor → select a section → Background → pick a texture → Apply **How to test:** Open a site in the editor, enter edit mode, select the hero, open Background, choose a texture and click Apply. The hero should visibly change within a couple of seconds, and still be there after a reload. **Watch for:** A change that saves (success toast) but leaves the preview on the old look; or a preview that flickers back to the previous version a moment after applying.
The automatic legibility check could flip white button text to black on designs that set their background colour dynamically — it couldn't see the background, assumed the button sat on white, and "corrected" text that was perfectly readable. It now recognises those backgrounds, and stays out of the way when it genuinely can't tell. **Where:** Anywhere a site is saved — editing content, refining a design, or importing one. **How to test:** Open a site whose buttons use the brand colour as a background with white label text. Make any edit and save. The labels should stay white. **Watch for:** Text that is genuinely invisible — white on white, dark grey on near-black — should still be corrected automatically. Only backgrounds the checker cannot read are now left alone.
Build a site in another language and the assistant now replies in that language — and auto-generated form labels come out translated too, instead of stray English. **Where:** The design/site editor chat, the dashboard and admin assistants, the blueprint planning chat, the public chat widget, and any forms the builder fills in for you. **How to test:** 1. Start a new site and describe your business in a non-English language (e.g. Chinese, Japanese, Spanish). 2. Chat with the assistant in that language — it now answers in the same language, and follows you if you switch languages mid-conversation. 3. Check a synthesized contact form: its default labels (Name, Email, Phone, Message, Submit) and the "thank you" message come out in the site's language. **Watch for:** This applies to newly generated sites (language is detected during generation) — regenerate an existing site to pick it up. Text your AI wrote into the page was already translated; this fixes the platform-owned parts (chat replies, the "that's handled on your dashboard" hand-off, and fabricated form labels). The full translation of built-in components (cart, checkout, customer portal) is a separate, larger follow-up.
Connecting Magnific (and the other creative accounts) could bounce you to a Google "400. That's an error" page instead of the sign-in screen — the connect request we handed the provider carried more data than Google's sign-in page would accept once it was passed along. **Where:** Site editor → Settings → Integrations → Creative Accounts → Connect **How to test:** Click Connect on Magnific while signed in to several Google accounts. The Google account picker should load, and after choosing an account the popup should close with the account showing as Connected. **Watch for:** A popup that lands on a Google error page, a popup that closes without connecting, or "Connecting…" that never resolves.
Linking an external API or feed to your site would often report that there were no sections available to connect — even on a finished site full of lists. Every list section is now offered. **Where:** Site editor → Settings → Data Sources → Connect a data source **How to test:** Open a site that has a list-style section (services, menu, showcase, stats, team). Start connecting a data source and open the section picker — the section should be listed, with the fields it displays. Connect a public JSON or RSS feed to it, publish, and the live site should show the fetched items. **Watch for:** A section missing from the picker; the picker showing a section that isn't really a list; connected data replacing a section's heading or intro text instead of just its items.
Image thumbnails in the Content Manager now pick the real picture even when the same item also stores a plain web address, so pictures that render perfectly on the site no longer appear broken in the editor. **Where:** Site editor → Content Manager → any section with an image group (e.g. a Hero with a set of preview images) **How to test:** Open a site whose section items carry both a display web address and a picture (for example, cards that mock up a browser window with an address bar). Open Content Manager, select that section, and confirm every thumbnail renders instead of showing a broken-image icon. **Watch for:** Groups that should still be recognised as images — plain lists of picture links, items that store the picture under "src" or "image" — must keep showing thumbnails. Lists of page links (label + address) should keep rendering as links, not as an image grid.
Opening the Content Manager while a section is selected now jumps straight to that section instead of always starting at SEO & Meta. **Where:** Site editor → select a section in the left Structure rail → "…" menu → Content **How to test:** Select any section (e.g. Hero) in the Structure rail, then open Content from the "…" menu. The Content Manager should open with that section already highlighted and its fields showing. Repeat with a different section to confirm it follows the selection, and open it with nothing selected to confirm it still starts at the top of the list. **Watch for:** The section shortcut inside the element properties panel should still scope correctly, and it must not leave a stale section selected the next time the Content Manager is opened from the menu.
Searching in the Content Manager used to only narrow the section list — you still had to hunt through every field to find the words you searched for. Now each hit is listed, counted and clickable, and opening one jumps to the exact field and highlights it. **Where:** Site editor → Content Manager → search box at the top of the section list **How to test:** 1. Open the Content Manager on any site and type a word you know appears in your copy. 2. Sections that contain the word show a "hits" badge, with the matching snippets listed underneath and your search term highlighted. 3. Click a snippet — the section opens, the item it lives in expands, and the field is outlined in amber and scrolled into view. 4. Press Enter (or use the up/down arrows in the search box) to step through every hit across all sections; the counter shows your position. 5. Press Escape to clear the search. **Watch for:** hits listed for a section that don't scroll anywhere when clicked (navigation, footer, SEO and image-gallery fields highlight at the section level only), snippet text that doesn't match the field it opens, or the counter and the listed hits disagreeing.
Ad and social creatives now come with eight ready-made layouts and a proper editor — drag the headline where you want it, pick a typeface, restyle the backdrop, and see exactly what will be produced before you commit. **Where:** Brand Studio → Create → generate a creative → **Edit layout** on the finished variant. **How to test:** 1. Open Brand Studio for a brand and create an ad or social post with a headline, an offer and a CTA. 2. When the variant finishes, click **Edit layout**. 3. Pick a different layout from the row of thumbnails — bottom band, card, side panel, centred hero, minimal caption and so on. The preview updates in place. 4. Drag the headline, offer or button around the image. They snap to the safe margins and the centre line. 5. In the panel on the right, change the typeface, size, weight and colour of the selected block; switch the backdrop between band, card, gradient and none; adjust its colour, opacity and feather; reorder the layers; hide anything you don't want. 6. Click **Apply exact copy** (still 0 credits) and confirm the downloaded creative matches the preview pixel for pixel. 7. Change the channel format (square / portrait / story / landscape) and re-check — the layout should re-flow sensibly at every size rather than clipping. **Watch for:** copy that disappears entirely from the finished image (that would mean a font failed to load on the server, not a layout problem); text sitting outside the dashed safe-area outline on story format; a preview that doesn't match the composed result; or an existing creative that re-composes differently than it did before — untouched creatives should be byte-identical to what they were.
When a generated design had an image that failed to load, the automatic repair step could quietly drop in an unrelated stock photo — including using one as a site's logo, as a customer headshot, or repeating the same photo across several different cards. Repairs now respect what each image slot is for, and every card gets its own picture. **Where:** Site editor → any newly generated design (Design 1…N) **How to test:** Generate or regenerate designs for a business, then open each design. The logo should be a brand mark (never a photo), testimonial/team pictures should be people, and gallery or portfolio cards should each show a different image. **Watch for:** A photo appearing in a logo slot, the same photo repeated across sibling cards, or an image that has nothing to do with the business. Existing designs keep the images they already have — regenerate to pick up the change.
Reordering, removing, or captioning an image in the Content Manager now keeps everything else stored alongside it — names, labels, headlines, links and nested details all survive the edit. **Where:** Site editor → Content Manager → any section with an image group **How to test:** Open a section whose items carry more than just a picture (for example cards that also have a name and a heading). Drag one thumbnail to a new position, then save and reopen. The names and headings must still be there and still attached to the right image. Repeat with removing an image. **Watch for:** Lists that store images as plain web addresses must stay plain web addresses after an edit — if those turn into structured items the images can disappear from the live page. Captions are intentionally not offered on those lists, since there is nowhere to keep them.
Saving a change to one page could fail because a completely different page on the same site had a rendering problem, leaving the whole site locked for editing. **Where:** Site editor — Edit mode, Background panel, colour and section controls **How to test:** Open a site, enter Edit mode, select a section, choose Background, pick a texture and click Apply. The change saves even if another page on the site has an unrelated issue. **Watch for:** A change that genuinely breaks the page you are editing should still be refused, with a plain-language message rather than technical details.
Our automatic readability check could mistake a dark coloured section for a light one and flip the text on it to black, leaving footers and dark panels unreadable — it now reads those sections correctly, and re-checks your design every time it is saved, not only when it is first created. **Where:** Any design in the site editor — most visibly deep-coloured footers and full-width dark sections. **How to test:** Open a design with a dark navy or deep-coloured footer and confirm the headings and button labels on it are light and readable. Refine the design, save, and check the same section again — a refinement that makes text unreadable is now corrected on save. **Watch for:** Text that was intentionally muted should stay muted — the check only steps in when text is effectively invisible against its background, not when it is merely subtle. Deliberate colour choices made in the colour editor are preserved.
Our automatic legibility check could repaint a hero headline black even though it sat on a dark photo — it didn't recognise animated background images as images. It now does, and existing sites with the problem have been repaired. **Where:** Any site or template with a full-screen photo hero — Site Editor → Home, and the Template Gallery preview. **How to test:** Open a site whose hero is a full-bleed photo with an animated (fade/zoom-in) background image. The headline should read light against the darkened photo, matching the subheadline underneath it. Generate a new design with a photo hero and confirm the same. **Watch for:** A headline that's a different colour from the paragraph directly below it in the same hero — that was the signature of this bug. Also check headlines over *light* photos still look as designed; we now leave those alone entirely rather than guessing.
You can now click, browse, and select hero patterns in the plan-mode wireframe, and attach the video or image a pattern needs before generating instead of only finding out when generation fails. **Where:** Site builder → Plan → Wireframe view → the hero section's pattern picker **How to test:** Open a site in plan mode, switch the Plan panel to Wireframe, click the hero card to open the picker, and click a pattern (e.g. "Cinematic Scroll-Scrub"). It should select immediately. Selecting a pattern that needs an asset (Cinematic video, Ken Burns image) now opens an upload dialog; the card also keeps an "Asset required — upload" note while selected. You can drag-scroll the pattern row too. **Watch for:** Section reordering still works — grab the grip handle on a card's left edge to drag. Report any card that starts dragging when you only meant to click.
When you tell the design chat you like a design and want to publish, it now offers a "Continue with this design" button instead of pointing you somewhere that couldn't help yet. **Where:** Site editor → design chat, while you're still comparing design options **How to test:** Open a site that's still in the design stage, then type something like "I like this one, let's publish it" or "move to build". The reply should say publishing unlocks once the design is locked in, with a "Continue with this design" button underneath. Clicking it starts the same flow as the "Build my site" button, using the design you're currently viewing. **Watch for:** The button should never act on its own — it always needs a click. It should not appear on sites that are already built (those keep the existing publish guidance), and it should use the design you're looking at, not a different one.
Design generation now carries what you've already said about a business — the feedback you typed, the options you rejected, and the design you picked — across every session and every site for that business, so a fresh start stops handing you the same look you walked away from last week. **Where:** Anywhere designs are generated for a business you've worked on before — the site builder's design step, "generate more designs", regenerate with feedback, and the design chat's suggestions. **How to test:** Create a site for a business, regenerate once or twice with specific feedback ("too corporate", "less violet"), then start a brand-new site for the same business name in the same workspace. The new designs should avoid the palettes and styles you already saw, and should not re-suggest a direction you rejected. Switching to a design (or approving one) records it as your pick. **Watch for:** Designs that ignore an explicit request — if you ask for a colour you rejected earlier, you should still get it; your current instruction always wins over the history. Also watch for a business whose name changed slightly ("Bella Napoli" vs "Bella Napoli Trattoria") — those are treated as separate businesses and each keeps its own history.
While the chat is asking you a few quick setup questions, the planning footer now keeps a clickable "Preview Plan" button so you can skip ahead any time — it no longer replaces it with a progress meter you can't act on. **Where:** Dashboard → New Site → the planning chat (right-side workspace footer) **How to test:** Start a new site, send a business description, and wait for the inline "quick questions" card. The footer should show a softened "Preview Plan" button (with a "answers improve the plan" hint), not a "% ready / Share in the chat" tile. Clicking it previews the plan immediately. **Watch for:** The button should be visible and enabled on both desktop and mobile while the card is unanswered, and only fall back to the readiness meter when no intake card is pending.
Asking for a page that no longer exists — because items were deleted, unpublished, or filtered out while you were browsing — now returns an empty page and the real item count instead of an error, so the list snaps back to a page that exists. **Where:** Any paginated list — Contacts, Form submissions, Orders, Bookings, Payments, Reviews, Chats, Clients, plus the public storefront category and product-review pages. **How to test:** Open a list, go to the last page, delete or filter out enough items that the page disappears, then reload or hit Next. The list should show an empty page with a corrected total, not a load error. **Watch for:** A list that still shows "Failed to load", or an item count that disagrees with the filters currently applied.
Pasting a Mondovo editor or preview link into the site-planning chat ("copy this site") now recognizes the site as yours and imports its design and content straight from your account — instead of trying to crawl the page from outside, which previously captured a sign-in screen and produced designs based on a login form. Several related guardrails shipped alongside: login-protected pages are now detected and refused with a clear message, web research about your business is shown for confirmation instead of being silently applied (and no longer picks up facts about older or unrelated same-named companies), design-preserving clones no longer ask contradicting "light or dark?" questions, and a clone that loses its reference screenshot now falls back visibly instead of generating blind. **Where:** Client editor → new site chat (`/client/{clientId}/site/new`) → paste a Mondovo editor URL, a `/preview/...` link, or any login-protected URL **How to test:** 1) Paste an editor URL of a site you own with "copy this site" — the chat should reply that it recognized your site and imported it directly (no scraping), and the reference thumbnail should show the actual design. 2) Paste a login-protected external URL — the chat should say the page only showed a sign-in screen. 3) After a clone of a public site, a "confirm research" card should appear before web-researched facts are used. **Watch for:** Editor links to sites the account can't access should produce a clear "couldn't open with your account" message (never a scrape of the login page); variation labels like `?variation=D12` should resolve to that exact design; preference forms for "keep my look" clones should no longer include light/dark or site-structure questions.
When the automatic pass that makes a page's content editable produced code that crashed, it gave up immediately and showed a raw technical error. It now gets a second attempt with the specific failure explained, and the message you see if it still fails is readable. **Where:** Site editor → "…" menu → Content (on a page whose content hasn't been prepared yet) **How to test:** Open the Content Manager on a page that has never been prepared. It should finish and open the section list. If it does fail, the message should be a single plain sentence, not a wall of technical detail. **Watch for:** It should still stop after the second attempt rather than retrying forever, and it must still refuse to save a page that would drop content or come out broken — a second chance is not a lowered bar.
Clicking "Preview Plan" in site planning now drafts a plan from what you already told us in chat, even if you haven't filled in the intake questions yet — no more dead clicks. **Where:** New Site → describe your business in chat → click "Preview Plan" (before answering the intake card) **How to test:** Send a message like "I run a family-run Italian restaurant in Austin with catering" without stating a business name, then click the softened "Preview Plan" button. A plan should draft. **Watch for:** The button used to silently do nothing when the business name/description fields were still empty; it should now always either produce a plan or tell you what it needs.
Listing pages like /blog, /products and /menu now show every published item, even on sites where the collection was set up before the listing wiring was corrected — those pages used to stay stuck on "No items yet" no matter how many items were published. **Where:** Your site's listing page — e.g. yoursite.com/blog — plus the matching page in the site editor preview. **How to test:** Open Content, publish an item in a collection that has a listing page (Blog Posts, Products, Menu…), then republish the site and open /<collection> on the live site. The published item should be listed, and drafts should still be hidden. **Watch for:** An existing site needs one republish for the change to reach the live page. If a listing page was already showing items correctly, or the section was hand-written with its own copy, nothing about it changes.
The index that powers content search and the "also used on" list had stopped rebuilding whenever a design was saved, so searches came back empty and repeated content looked like it appeared on only one page. It rebuilds correctly again. **Where:** Content search in the site editor, and the "where used" list shown when editing a piece of content. **How to test:** Edit and save any design, then search for a phrase you know appears on the site — it should be found. Open a headline that appears on more than one page and confirm the other pages are listed. **Watch for:** The index rebuilds on the next save, so a site that has not been touched since the fix may still look empty until you save it once.
Interactive components on Arabic, Hebrew, Persian and Urdu sites now flip the right way — the slide track, arrow positions, arrow icons and the comparison-slider drag all follow the page's right-to-left direction. **Where:** Any published site whose language is right-to-left, on sections using the image carousel, gallery lightbox, or before/after comparison slider. **How to test:** Publish a site with an RTL default language, open a page with a carousel and a before/after slider, and navigate them. The prev/next arrows sit on the mirrored edges and point the correct way, the carousel advances in the reading direction, and the comparison handle tracks your pointer. **Watch for:** Centered elements (counters, dots, the vertical slider handle) must stay put — only the direction-dependent parts should move.
The first setup card sometimes left out the location or business-name question, so you only found out something was missing when the Generate button stayed blocked. **Where:** Start a new site from the dashboard or homepage prompt, then answer the questions in the chat. **How to test:** Describe a business that already hints at where it operates (e.g. "a real estate blog covering upcoming projects"). The card should still ask where you're based, and the location box should offer a one-tap "Use my location" fill matching your actual city. **Watch for:** A card with no location question, no business-name question, or location examples from an unrelated country.
Sites opened through a shared preview link were rendering with fallback system fonts instead of the fonts chosen for the design — and in some cases without their brand colours. The preview now loads both correctly, matching what you see in the editor. **Where:** Any preview link you share with a client, and the draft address of a site before it's published. **How to test:** Open a site in the editor, note its headings font, then open the same site through its shared preview link. The headings should use the same font, not a generic one. Brand colours should match too. **Watch for:** A brief flash of the fallback font as the webfont loads is expected. A preview that stays on the generic font, or loses its colours, is not.
When our image planner aimed a picture at a whole section instead of that section's image slot, the picture replaced the section's entire contents — headline, subheading and all — leaving the section to fall back to placeholder wording and become uneditable. The image now lands on the section's image field and the written content survives. **Where:** Any generated design — most often the homepage hero. **How to test:** Generate a design with a hero image, then open the hero in the content editor and confirm its headline, subheading and supporting points are all present and editable. **Watch for:** Sections that previously lost their text will not recover it retroactively — this prevents the loss on new designs rather than restoring past ones. If an older design's hero shows placeholder wording that you cannot edit, it was affected before this fix.
Cart, checkout, and product-filter controls on published sites now render in the site's language instead of always showing English. **Where:** Any published non-English store — the cart drawer, mini-cart, checkout summary, and catalog filter sidebar. **How to test:** Publish (or republish) a site whose language is not English, then open the storefront and add an item to the cart. Labels like "Add to Cart", "Subtotal", "Total", "Place Order", "Filters", and "Clear all" now appear translated. English sites look exactly as before. **Watch for:** A newly translated label that reads oddly — the per-site override map lets a specific string be corrected without re-translating everything. If a label still shows in English, republish so the latest strings are baked in.
Deleting, restoring, or archiving the last items on the last page of a list used to strand the pager on a page that no longer existed, showing a load error over the whole list; those lists now return an empty page with a corrected count and jump back to a page that exists. **Where:** Trash (Dashboard → Trash), the Image Library tab in Assets, and the admin Deleted Sites, Retrieval Corpus, Gallery Section Blocks and Gallery Candidates lists. **How to test:** Open one of those lists, page to the last page, delete or restore enough items to empty it, then hit Next or reload. The pager should land on the last real page with an accurate count instead of showing an error. **Watch for:** A list stuck on "Failed to load", a page counter that keeps advertising pages with nothing in them, or a total that disagrees with the filters currently applied.
The "Upgrade Plan" button did nothing when clicked from the billing page, and the add-ons listed there (Agency, extra team seats, extra voice minutes) were price labels with no way to actually buy them. **Where:** Dashboard → your organization → Billing & Subscription **How to test:** 1. Open Billing & Subscription. If an "Approaching Plan Limits" panel appears, click **Upgrade Plan** — the page should scroll down to the plan cards instead of sitting still. 2. Scroll to the **Add-ons** row under the plan cards. Each add-on now has an **Add** button; seats and voice minutes also have a quantity stepper. 3. Click **Add** on one. It attaches to your subscription with a prorated charge and the tile updates to show the new quantity (or "Active" for Agency). 4. If you're not on a paid plan yet, the row offers **Upgrade to Pro** first rather than failing. 5. Check the **Live sites** card — the count against your allowance should read sensibly (no more "7 of 1"). **Watch for:** an "Add" button that spins without resolving; a quantity that doesn't update after purchase; the Upgrade Plan button jumping to the top of the page instead of the plan cards; the live-sites count showing more sites in use than your plan allows.
The setup questions no longer ask you to pick a writing voice from a list of vague adjectives — we work it out from your business instead. **Where:** The questions shown when you start a new site (site builder chat, first card). **How to test:** Start a new site with any business description, or point us at a site to copy. The card should ask about things like your business name, location and layout — but never "How should it sound?" with options like "Friendly & simple" or "Premium & understated". **Watch for:** Generated copy should still match the business — a neighbourhood plumber should not read like an enterprise software vendor. If you do want a specific voice, just say so in the chat ("keep it plain and warm, no jargon") and we will use it.
Sites for local businesses in markets where customers actually message on WhatsApp now launch with a working WhatsApp chat button already configured, instead of leaving it switched off until someone finds it in Settings. **Where:** Site editor → Popups & banners (also Settings → Integrations) **How to test:** Build a site for a local business — a restaurant, clinic, or home-services trade — and give it a real contact phone number during the chat intake. When the site finishes generating, open Popups & banners: "WhatsApp floating button" should be listed and switched on, with the business phone number filled in. Open the preview and click the green button — it should open a WhatsApp chat with a friendly pre-filled message. **Watch for:** The button should NOT appear when the business has no phone number, when it's a software or online-only business, or when the phone number belongs to a country where people don't message businesses on WhatsApp. If you switch the button off yourself, it must stay off — regenerating the site should never turn it back on.
When a new site finished generating, the design switcher sometimes skipped straight to D2 and D3 with no D1 at all — even though the first design was there the whole time, just wearing the wrong label. **Where:** Site editor, the DESIGNS switcher in the top bar **How to test:** Create a new site and let both starter designs finish generating. The switcher should read D1, D2 — never D2, D3. **Watch for:** A design labelled with a number one higher than it should be, or two designs sharing the same number, after generating additional designs on an existing site.
You can now see exactly how to connect Claude, ChatGPT, Cursor, or any other AI assistant to your workspace without leaving your settings — including a one-click copy of the connector URL. **Where:** Dashboard → Settings → Integrations → Connected Apps → "How to connect an assistant" **How to test:** Open the Integrations tab and expand "How to connect an assistant". Copy the connector URL, switch the assistant dropdown (Claude, ChatGPT, Claude Code, Cursor, VS Code, Gemini CLI, and more) and confirm the steps and setup snippet change for each. If you have no apps connected yet, the panel opens automatically. **Watch for:** The copy button should confirm with "Copied"; the "Full connection guide" link should open the public guide in a new tab; already-connected apps should still list and disconnect as before.
Sites you delete used to keep occupying a published-site or draft slot forever, so you could be told you were at your limit while the sites you could actually see were well under it. **Where:** Dashboard → your site list, and the publish flow on any site **How to test:** Note how many live sites your workspace shows. Delete a client that had a published site, then publish another site — the slot the deleted site was holding is now free, and the usage figures on the dashboard match what the publish step enforces. **Watch for:** A limit message that names a higher number than the sites actually listed; a draft or publish attempt refused when you are visibly under your plan's allowance; the dashboard's draft count disagreeing with the wall you hit when creating one.
New public developers page documenting both ways to drive Mondovo programmatically: the AI-assistant connector (Claude, ChatGPT, Claude Desktop — included on every plan, no API key needed) and the REST API for headless automation (Agency add-on), with curl examples, rate limits, error codes, and billing notes. A machine-readable OpenAPI 3.1 spec is now served too. **Where:** mondovo.com/developers (linked from the homepage footer, the connector guide at /connectors, and Dashboard → Settings → API Keys). Spec at /api/v1/openapi.json. **How to test:** Open /developers logged out — the page should load with connector setup steps, all 7 REST endpoints with curl examples, and a working link to /api/v1/openapi.json (valid JSON, no auth prompt). From the API Keys card in organization settings, the "developer docs" link should open the page. **Watch for:** The OpenAPI spec is hand-authored — if an endpoint's request or response shape changes, the spec must be updated in the same commit or the docs drift.
Pro workspaces can now add extra live-site slots directly from the billing page — no need to wait for a publish. A prepaid slot is billed like any extra live site ($20/month, prorated today), and your next publish uses it automatically at no new charge. Unused slots can be removed anytime (no refund; billing stops at your next renewal, same as taking a site offline). **Where:** Dashboard → Organization → Billing → "Live sites" card (left column). The publish confirmation also says when a site will use a prepaid slot instead of adding a new charge. **How to test:** 1. On a Pro (Stripe) org, open the billing page — the Live sites card shows "X of Y paid site slots in use". 2. Click "Add site slot", confirm — a prorated charge is applied and the slot appears as "Prepaid slot — ready for your next publish". 3. Publish a new site: the consent step says it uses a slot you already paid for (no new charge), and after publishing the slot is consumed. 4. Buy another slot and remove it with the trash icon — the subscription quantity drops immediately. 5. On a free org the card shows "Upgrade to Pro"; on a comped internal org it shows included-slot headroom with no buy button. **Watch for:** double-clicking Add/Remove (must never double-charge or double-decrement), two simultaneous publishes racing for one prepaid slot (one claims it, the other bills normally), and monthly credit grants counting prepaid slots (+150/month each, since they are paid).
Text lines grouped inside one block (e.g. a title stacked over a caption, or the rows of a stat card) are now editable line-by-line instead of being merged into a single combined field. **Where:** Design editor → click a text element in the preview → Quick edit **Two improvements:** - **Clicking a line** selects just that line — the Quick edit field shows only that line's text, with its own style preserved. Clicking the thin gap between lines snaps to the nearest line. - **Selecting a block, column, or whole section** that holds several lines now shows one edit field per line ("Heading", "Text", …) — each saves independently — instead of one textarea over the concatenated text. This works at any grouping level (up to ~30 lines), so a hero section lists all its text lines rather than merging them. **How to test:** Open a design with a card or section that stacks differently-styled text lines. Click the title → only the title is editable. Then select the surrounding block, column, or the whole section → the panel lists each line as its own field. Edit one and Save; the others are untouched. **Watch for:** Lines whose text is computed (e.g. "128 sources · $420k at stake" built from separate values) can't always be matched to a single source string — those route through the section AI to apply, which is expected. Selecting a very large region (a whole page, or a section with 30+ text lines) keeps the previous section-level behavior rather than listing every line.
Connecting an external API now lets you match its fields to what each section shows, and auth-aware buttons can detect users of your own login system, not just Mondovo's. **Where:** Site editor → Settings → Data Sources, or the AI assistant / refine chat. **How to test:** 1. Settings → Data Sources → Add Data Source → enter a REST endpoint → **Test Connection**. 2. On the mapping step, pick the section to fill. Your API's fields now appear with a suggested match to each section field (e.g. `post_title → title`, `attributes.unit_price → price`) — adjust any row, and expand "Preview one item" to see exactly what the section will receive. Save and **Publish**. 3. Or ask the assistant: "connect my products from https://… and map unit_price to price". It tests, proposes the mapping, and connects it. 4. If a section shows a blank or wrong value later, ask "fix the price mapping on my products data source" — no need to rebuild it. 5. Auth-aware buttons for your OWN app: ask the assistant "how does logged-in detection work?" It explains the options, including two that need no backend change — pointing at a cookie your app already sets, or a value it already puts on the page. **Watch for:** - Fields whose names already match are left unmapped on purpose — they pass straight through. - Data still populates at **publish time**. Republish or **Sync Now** after changing a mapping. - Detecting your own app's users via a "who am I" URL requires that endpoint to allow your site's address with credentials (CORS). The cookie/value options avoid that entirely. - This release also fixes a bug where external data source content did not appear on published sites at all — connected sources now render as expected.
When setting up billing for a site failed during publishing, the error was mislabeled as a generic "Compiling Code / Unexpected Error" with no mention of billing. It now shows a clear billing message so you know what actually went wrong. **Where:** Site editor → Publish Changes → the consent step on a per-site plan **How to test:** Publish a site whose billing setup fails; the error dialog should read "Billing Setup Failed" with a billing-specific message, not "Failed during: Compiling Code". **Watch for:** The error dialog still appearing, and never labeling a billing failure as a compilation error.
Clicking a section in the editor now puts its text fields right at the top where they used to be, instead of a wall of background controls. Backgrounds moved behind a single "Background" row, and picking one finally previews live. **Where:** Editor mode → click any section in the preview **How to test:** Select a section and confirm its content fields are the first thing you see. Click "Background" at the bottom of the panel to open the background surface, pick a colour, gradient or texture, and confirm the preview updates instantly before you hit Apply. Click "Back" to return to the content. Right-click a section → Background should open the same surface directly. **Watch for:** Any background overlay appearing on a section you only selected and never edited (nothing should preview until you pick something); the Apply button committing a look you never saw previewed; the Back button not returning to the content fields.
Three upgrades to section design swapping: a "Swap design" button now floats over the preview whenever you select a section (or click anything inside one) — no more hunting for the hidden hover icon; the gallery grid now shows designs from businesses like yours first (a restaurant site sees restaurant sections at the top); and you can simply ask the AI assistant — "show me other hero layouts" opens the design picker on the right section. **Where:** Site editor → click any section on the canvas (pill appears bottom-center), or ask the assistant **How to test:** Click inside any section in the editor preview — a "Swap design — {Section}" pill should appear at the bottom of the canvas and open the picker. On a restaurant/real-estate/SaaS site, confirm the top gallery results match the industry. In the assistant, type "show me other testimonial designs" — the picker should open scoped to the testimonials section. **Watch for:** The pill covering site content it shouldn't (it hides while the picker is open); assistant opening the wrong section for ambiguous names; industry ordering pushing visually better cross-industry designs too far down.
When you swap a section's layout, you now browse real, rendered section designs from our template gallery — with a search box to describe the style you want (e.g. "dark luxury") — instead of gray schematic wireframes. Picking a design adapts its layout and styling onto your own text, images and brand colours; nothing is copied verbatim, so your site stays unique. **Where:** Site editor → select a section → Swap layout **How to test:** Open any section's Swap layout. The "Designs from our gallery" grid should show real screenshots for common sections (hero, testimonials, footer…). Type a style description in the search box and watch results re-rank. Click a design — a preview adapts it to your content — then "Use this layout" to apply. Wireframe "layout ideas" still appear below, and are the main grid for rare section types with no gallery inventory. **Watch for:** A picked design should keep YOUR text, images and colours (only structure/styling changes); missing thumbnails or an empty gallery grid on common section types; search returning unrelated sections.
When you asked the design chat for something your site can have as its own page — a blog, a store, a booking area — it offered to drop a preview section onto the page you were looking at, but clicking that offer just repeated the same reply instead of adding anything. The offer now does what it says. **Where:** Site editor → design chat (the chat beside your design preview) **How to test:** Ask "add a blog page so I can write and manage articles myself", then click the "Add a blog section to this page" suggestion that comes back. The section should appear in the preview within a minute or so. **Watch for:** The new section landing in a sensible spot (not after the footer), the rest of the page staying exactly as it was, and the original request still pointing you to your dashboard for the real page.
Before you've settled on a final design, asking the design chat to "add a blog page" (or any other real page) used to randomly do one of two different things — sometimes correctly offering a preview section, sometimes going ahead and creating a real page early. It now consistently offers the preview-section suggestion until you've chosen your design and moved into the build phase. **Where:** Site editor → design chat, on sites where you haven't yet picked a working design **How to test:** On a fresh design-phase site, ask "add a blog page" a few times — it should consistently reply with the out-of-scope explanation and a section-preview suggestion, never create a real page. **Watch for:** Sites that have already moved into the build phase should still create real pages as expected — this only affects the earlier design-picking stage.
White-label agencies can now embed a footer credit — like "Made with ♥ by Your Agency" linking back to your own website — on every client site they publish. **Where:** Dashboard → Organization → White-Label Branding → "Client-site footer credit" (requires the white-label add-on) **How to test:** Enable the white-label add-on, turn on the footer credit, set the text (use `{heart}` for a heart icon) and your website URL, and save. Open a client site in the editor — the credit bar appears at the bottom of the preview. Publish the site and confirm it shows on the live page linking to your URL. **Watch for:** The bar should only appear for orgs with the white-label add-on; text should render exactly as typed (HTML is escaped), and the link must be https.
Tell the AI editor "make the hero glow blue", "add a subtle grid background to this section", or "make the headline decode in as you scroll" — and it applies the real, tested effect instead of improvising code. **Where:** Editor mode → select a section or heading → type the request in the AI chat **How to test:** Select the hero and ask "give the hero a glowing texture background"; select a heading and ask "make this decode in on scroll". Confirm the effect applies cleanly and matches what the Background / animation panels produce. **Watch for:** An effect being applied to an ordinary copy edit (it should NOT — plain edits stay plain); the wrong element being targeted; a request that's ambiguous getting a clarifying question instead of a guess.
When asking the assistant to add something to a collection that already exists (like writing a blog post when the Blog Posts collection is already set up), it could previously reply with confusing internal text instead of a clear next step. It now explains plainly that nothing was added yet and how to add it as a new item. **Where:** Site dashboard assistant chat. **How to test:** - On a site with an existing Blog Posts collection, ask the assistant to "write a blog post" in a way that routes to collection setup rather than item creation. - The reply should read as plain English with no code-like text (no tool names, parentheses, or `collection_type=` syntax). **Watch for:** Any assistant reply containing tool/function names, underscores-as-code, or route syntax visible to the user.
When you ask the site assistant to add an item to a collection that isn't set up yet, it now points you to the collections you actually have instead of guessing at unrelated page sections. **Where:** Site editor → assistant chat (e.g. "Add a recipe to my recipes collection") **How to test:** On a site that has a real collection (like Blog Posts) but no "recipes" collection, ask the assistant to add a recipe to a recipes collection. It should decline and mention your existing Blog Posts collection, rather than listing homepage sections or offering to create a collection you already have. **Watch for:** The assistant listing homepage content sections (Portfolio, Team, etc.) as if they were collections, or offering to create a collection that already exists.
Selecting a section in the editor canvas now opens its Background controls again, and right-clicking anywhere inside a section offers a Background option. **Where:** Site editor → Edit site → Edit mode → click a section (or right-click any element inside one) **How to test:** Open a site, enter Edit mode, and click the hero section. The right panel should show an expanded "Background" block with the texture, look, tint and intensity controls. Right-click the hero headline — the menu should include "Background", and choosing it should select the hero and jump to those same controls. Repeat on a lower section (About, Menu, Contact) and confirm the controls target that section, not the hero. **Watch for:** Controls that open but target the wrong section; a "Background" menu item that does nothing; the panel staying closed on pages whose sections live in a single page file rather than separate block files.
Design edits that failed to save because the database was briefly slow now retry automatically, and if they still can't save you'll see a plain "please try again" message instead of a raw technical error. **Where:** Site editor → Tweaks / Style panel (and any save that updates your design) **How to test:** Change a palette or style and click Apply. On a normal save nothing changes. If the backend is momentarily slow, the save quietly retries once before showing any error. **Watch for:** Any save-failure toast that still exposes internal system names or a millisecond timeout value — those should now always read as a friendly "taking longer than expected, please try again."
When you ask the assistant to write a blog post (or add any item) and that collection already exists, it now replies in plain language instead of showing a confusing internal instruction — and makes clear nothing was created so you can add the item as a draft. **Where:** Site editor → assistant chat (dashboard "write a blog post" style requests) **How to test:** On a site that already has a Blog Posts collection, ask the assistant "Write a short blog post titled 'X'". If it offers to create the collection and you confirm, the reply should clearly say the collection already exists and that you can add it as a new item (saved as a draft) — with no developer jargon or tool syntax in the message. **Watch for:** Any reply that still shows raw text like `add_collection_item` or `collection_type="blog"`, or a bare "Confirmed: Create Collection" with no follow-up explanation.
You can now pull content straight from your own API into a site section, ask the assistant to set it up for you in plain English, and show different buttons to visitors who are already signed in. **Where:** Site editor → Settings → Data Sources (new). Or just ask the AI assistant, e.g. "pull my pricing from my backend at https://…". **How to test:** 1. Open a site → Settings → the new **Data Sources** section under "Forms & Data". Previously this was only reachable by typing a URL — it now appears in the sidebar. 2. Click **Add Data Source**, enter a public REST or RSS endpoint, test the connection, and bind it to one of your site's content sections. 3. Or open the AI assistant and say "connect my pricing from https://…". It will list your bindable sections, test the endpoint, show you a sample of the real data, and connect it after you confirm. 4. Republish the site — the fetched data is baked into your pages. 5. For logged-in visitors: ask the assistant (or refine chat) to "make my sign-up button say Go to Dashboard for logged-in visitors". **Watch for:** - Data is fetched **when you publish**, not continuously in the visitor's browser. If new data doesn't show, republish or hit **Sync Now**. - The assistant only connects public endpoints. If yours needs an API key or bearer token, set it up in Settings → Data Sources — never paste secrets into chat. - Binding a section that already has a data source is rejected; disconnect the old one first. - Logged-in detection works automatically on your site's own address — its Mondovo subdomain or your connected custom domain. If buttons don't swap, make sure the site has been published and the custom domain is connected in Settings → Domain.
Asking the design chat to add a page (like "add a blog page") while you're still comparing designs now always responds the same way — it confirms the page can be added once you pick a design, and offers to drop that section onto the page you're viewing right now. Previously it sometimes did that and sometimes jumped straight to a page-plan card, which was confusing. **Where:** The AI chat on a site's Design screen (while comparing design options, before choosing one). **How to test:** Open a site that's still in the design/compare stage, open the design chat, and type "add a blog page so I can write and manage articles myself." You should get a short reply explaining the blog gets added once you choose a design, plus an "Add a blog section to this page" button. Try it a few times — the response should be the same every time. **Watch for:** A "Proposed plan" card appearing instead of the reply + button, or the response differing between attempts.
After saving a site as a personal template and then archiving it, trying to save that same site as a template again was silently blocked. It now works as expected. A few related rough edges were also cleaned up: My Templates now only shows templates that belong to your current workspace, and template cards with a broken thumbnail now fall back to a placeholder instead of a broken image icon. **Where:** Dashboard → My Templates (and the "Save as template" action in the site editor) **How to test:** Save a site as a personal template, archive it from My Templates, then save the same site as a template again — it should succeed instead of showing an error. **Watch for:** Switching workspaces should immediately update which templates you see in My Templates.
Applying a hero background to a hero that already has a full-width photo used to do nothing visible — the new texture was painted behind the photo. It now sits on top of the photo, and the live preview matches what you get after applying. **Where:** Site editor → Edit mode → right-click the hero → Background **How to test:** Open a site whose hero has a full-width background photo, pick a texture, look at the live preview, then click "Apply hero background" — the applied result should look the same as the preview. **Watch for:** The headline and buttons must stay fully visible and readable after applying, on both photo heroes and plain colored heroes.
Applying a textured hero background no longer washes out the secondary button or headline text. **Where:** Site Editor → select the Hero section → Background panel → pick a texture / Look → Apply hero background **How to test:** Apply a hero texture with the "Colorize" look, then check the hero — the headline, sub-headline, and both CTA buttons ("Book Your Table" and "View Menu") stay fully legible over the darker background. **Watch for:** Removing the hero background should return the hero to its original light styling with normal dark text (no leftover forced-light text).
The agency footer credit now has a per-site override: hide it on a specific client site, or give that site its own text and link — right from the editor's "Add to site" add-ons, or by asking the assistant. **Where:** Site editor → "Add to site" → **Agency footer credit** (white-label add-on required). Or tell the AI assistant "hide the footer credit on this site." **How to test:** With the white-label add-on enabled, open a site in the editor, open "Add to site", choose Agency footer credit → Hide → publish → confirm the credit is gone on that site while your other sites still show it. Try "Show" with custom text/link and confirm the override renders. Remove the override to revert to the agency default. **Watch for:** Only agency staff can change it (end clients in the portal can't). Custom links must be https. The credit still requires the white-label add-on to appear at all.
Starting a new site no longer borrows the business name from your account — the name and description you type in the first intake question are what the site is built around. **Where:** Your website → New site (the "What's your business or site name?" intake) **How to test:** Start a new site under an account whose name differs from the business you're building (e.g. an account named after an older site). Type a completely different business name and description, then check the site title and the plan the assistant drafts. **Watch for:** The site title, the assistant's follow-up questions, and the drafted sections should all reflect what you typed. Previously they could silently take on the account's name and even its industry — a bookshop could come back planned as a yoga studio.
Your saved templates are now more than exact copies: when you start a site from one you can personalize it for a different business on the spot, refresh a template to match how its source site looks today, and removing a template now fully cleans up behind itself. **Where:** Dashboard → Inspirations → My Templates **How to test:** 1. Open Inspirations and find a saved template under "My Templates". 2. Click "Use template" — a new step asks whether to use it as-is or personalize it. Fill in a business name, industry, and a one-line description, then "Personalize & create". The new site opens with the business name merged in, and the copy rewrites itself in the background (progress banner on the design surface). 3. Click "Use template" → "Use as-is" — you get an exact copy, no rewriting. 4. Open a template's ⋮ menu → "Update from current site" → confirm. The template's snapshot is replaced with the source site's current design; sites you already created from it are unchanged. 5. Remove a template from the ⋮ menu — it disappears from the list and its stored snapshot is cleaned up. **Watch for:** - Personalized spin-ups that never finish "tailoring" (banner stuck) — the rewrite is designed to settle back to a working verbatim copy on any failure. - "Update from current site" on a template whose original site or design was deleted should show a clear message, not a generic error. - Phone/email entered in the personalize step should appear in the new site's contact details.
Footer links that pointed at pages the site never got (Services, Pricing, Careers, FAQ…) are now removed when a site is published, and a Privacy Policy link that pointed at the wrong address is repointed at the real page instead of disappearing. **Where:** Any published site — the footer of every page. **How to test:** Publish (or re-publish) a site whose footer lists pages that were planned but never created, then open the live site and click every footer link. **Watch for:** A footer link that still 404s; the Privacy Policy or Terms link missing from the footer bar; a footer column disappearing entirely when its links were valid.
Publishing a site now guarantees its footer links point to pages that actually exist — no more dead "Privacy Policy", "Terms", or "Shop" links returning 404 on the live site. **Where:** Any published site — visible in the site footer. **How to test:** Publish a site whose footer lists legal or navigation links, then open the live URL and click each footer link. Every internal link resolves to a real page; Privacy Policy and Terms pages are always present. **Watch for:** Footer links to pages you never built should simply not appear; external links, email/phone links, and on-page anchors are left untouched.
Select a section (or right-click it) in the editor to open a new Background panel — pick a pattern, gradient, image, or one of six new tintable hero textures, and see it applied live before you commit. **Where:** Editor mode → select any section → the "Background" panel in the right sidebar (or right-click a section → Background) **How to test:** Open a site in the editor, click the hero section, expand Background, try a hero texture with a blend "Look" (Colorize/Flood), a tint, and a mouse interaction; adjust intensity; click Apply. Confirm the live preview matches the applied result and your headline stays readable. **Watch for:** Background covering the hero text after Apply; the mouse-follow effect running on touch devices or when reduced-motion is set (it should stay off); preview not clearing when you deselect the section.
You can now save a whole site — or a single design concept — as a personal template, then start new sites from it anytime. One "Save this design…" action lets you choose between saving an exact copy (Template) or just the look — colors, fonts, feel (Style, formerly called a design skill). Saved templates live in a new "My Templates" section, and each account can keep up to 10 active templates. **Where:** Design gallery → wand icon on any design card → "Save this design…"; Site editor → Settings → General → "Save as template…"; Dashboard → site card menu → "Save as template…". Saved templates appear at Dashboard → Inspirations → "My Templates". **How to test:** 1. Open a site's design gallery, click the wand icon on a design card, and pick "As a Template" — name it and save. 2. Go to Dashboard → Inspirations and confirm the template appears under "My Templates" with a preview image. 3. Click "Use template" and confirm a new site is created with the same design and content, landing in the design view. 4. From the same modal, pick "As a Style" and confirm it appears under Organization → Styles. 5. Try the dashboard card menu and site Settings entry points for whole-site saves. **Watch for:** Saving the same design twice should show a friendly "already saved" message, not an error page. After 10 active templates, new saves should explain the limit. New sites made from a template must keep their images working even if the original site is later deleted. Agency outreach template counts and lists must not include personal templates.
Ask the editor to make a paragraph or heading light up as you scroll and its words now brighten from dim to full in reading order — a highlight that sweeps through the text as the section scrolls into view. **Where:** Site editor - select a paragraph/heading, then use the refine chat. **How to test:** Open a site in the editor, click a body paragraph or heading, and type a request like "highlight the text as I scroll" or "make the paragraph light up on scroll, word by word". Publish or preview and scroll the section into view - the words should brighten in order. On a device with reduced-motion enabled, the text simply shows at full brightness with no animation. **Watch for:** It only applies to plain-text elements (a single string of words). If the selected element contains nested links, bold spans, or other markup, the editor declines and asks you to pick a simpler text element rather than risk breaking the layout.
Clicking a section in the editor shows the Section Library again, and "Explore Alternatives" now swaps the section you actually clicked — including sections that live in their own file on multi-page sites. **Where:** Site editor → click any section on the canvas → Properties panel → Section Library **How to test:** Open a site, click a section (hero, testimonials, contact), expand "Section Library", generate or pick an alternative, preview it, then apply. Repeat on a multi-page site where the section belongs to a separate block file. **Watch for:** The Library block not appearing at all; a preview or apply that changes a different section than the one selected; a preview that leaves the rest of the page looking wrong.
A Style can now be backed by a built-in visual effect — so applying it makes a precise, tested change to the section or element you selected, instead of asking the AI to interpret a design note. **Where:** Dashboard → Styles → New Style (pick a "Built-in effect"); then the design chat in the site editor → Apply a Style. **How to test:** 1. In Dashboard → Styles, click New Style, give it a name, choose a Built-in effect (e.g. "Hero background" or "Scramble text"), add a short description, and save. 2. Open a site in the editor, click a section or element in the preview to select it, then open Apply a Style and pick your new effect Style. 3. Send. The effect is applied straight to the selected section/element — no design generation step. **Watch for:** The effect Style chip stays disabled until you have a section/element selected. Effect Styles apply on their own — you can't combine one with a regular Style or a typed request in the same send. If you send without a selection, you get a prompt to select a section first (never a silent no-op).
You can now take a live site offline without deleting it — freeing up a publishing slot on your plan while keeping the site fully editable and ready to republish anytime. **Where:** Open the site, go to Settings → Advanced → "Take Site Offline". **How to test:** Publish a site, then open Settings → Advanced and click "Take Site Offline". Confirm the dialog. The public link goes offline, the slot is freed, and the site stays editable. Click Publish again to bring it back with one click. **Watch for:** The site's address and all your content/design should be preserved after taking it offline. The "Site Limit Reached" message now points you to this feature instead of only offering to upgrade or delete a site.
Changing your site's primary colour, fonts, corners or density from Tweaks could report "Applied" and then quietly keep the old look — on sites that had explored several design variations, the save was too big for the server to accept and was dropped without any warning. **Where:** Site editor → Tweaks (top toolbar) → Palette **How to test:** Open a site that has several designs, pick a different Primary colour, click Apply, then hard-reload the editor. The new colour should still be there. **Watch for:** If a save genuinely fails now, you'll see a clear "Failed to apply…" message in the activity feed instead of a false success.