Picking a color, font, spacing or opacity value from the quick-edit popover would close the panel immediately and act like it worked, even when the change hadn't actually saved yet — or had failed outright. The popover now stays open and shows "Applying change…" until the save is confirmed, closes on real success, and tells you plainly if it didn't work so you can retry. **Where:** Site editor → click any element on the canvas → use the color/font/spacing/opacity quick-edit popover **How to test:** - Select an element and open the quick color picker, then click a swatch - Confirm the popover shows a brief "Applying change…" state before closing - Reload the preview and confirm the new color actually stuck **Watch for:** The popover closing instantly with no loading state, or a change that appears applied in the preview but reverts after a reload
The "Needs your attention" section on your dashboard now also flags when a client has picked a design on a shared design board but no site has been started from it yet, when a growth prospect is scoring as a hot lead, and when a site has new form submissions you haven't seen yet — each with a direct link to act on it. **Where:** Dashboard → "Needs your attention" section (top of the home screen) **How to test:** - Share a design board with a client, have them choose a design, and confirm a "Needs your attention" card appears linking to that board - Check a site with unread form submissions and confirm a card appears linking to that site's inbox - Confirm the growth pipeline's hot-lead count matches what shows up in the attention strip **Watch for:** Missing or duplicate attention cards, or a card linking to the wrong board, lead, or inbox.
The dashboard's attention area could show a new form submission both as its own row in the attention strip and as part of the "N new leads" summary count — the same lead counted twice, and the extra row could crowd out other things that actually needed a decision from you. **Where:** Dashboard → home/portfolio view → attention strip and pulse summary row **How to test:** - Have a site receive a new form submission - Open the dashboard and confirm the new lead appears only in the "N new leads in the last 2 weeks" summary line, not as a separate row in the attention strip above it - Confirm the attention strip still shows real decisions (failed publishes, pending design approvals, hot leads) without leads eating one of its slots **Watch for:** A lead appearing as its own attention-strip row, or the lead count and the strip disagreeing about whether a lead was already seen.
A specific kind of placeholder component (one written as a one-line arrow function) could get corrupted by the automatic code-repair pass, which produced code that no longer parsed and made the whole pass throw away every other fix it had just made — with no visible error. That case is now handled correctly, and a bad fix can no longer take the rest of the pass down with it. **Where:** Site editor → any screen that runs auto-fix **How to test:** Run auto-fix on a site containing a placeholder component written as a single-line arrow function with JSX (e.g. `const Button = ({ x }) => <button>{x.label}</button>`), alongside other genuine issues, and confirm all the other issues still get fixed **Watch for:** An auto-fix run that reports success but leaves obviously broken code untouched, especially when a site has a one-line stub component
Growth outreach emails were going out with no working preview link — in the worst case, the literal placeholder text instead of a link. Emails now always carry a real, clickable link to the prospect's preview site. **Where:** Growth → Campaigns (outreach emails sent to prospects). **How to test:** - Build a preview for a prospect, then send them an outreach email from a campaign. - Open the sent email and confirm it contains a real, clickable preview link (not placeholder text). - Click the link and confirm it opens the prospect's actual preview site. **Watch for:** An email containing raw placeholder text where a link should be, or a link that doesn't resolve to the prospect's preview.
For sites imported from an existing website, choosing "start from this version" when generating a new page variation was ignored — the new variation was always built from the original page instead of the one you picked. Picking a specific existing version now actually works. **Where:** Site editor → a page with multiple saved versions → generate a new version, choose which existing version to start from **How to test:** On an imported site with a page that has more than one saved version, generate a new version and pick an existing version (not the original) as the starting point — the result should keep that version's distinguishing details while applying your requested change **Watch for:** A new page version that looks like it came from the original page instead of the one you selected as the starting point
Your plan no longer limits how many pages you can publish. Build sites as large as they need to be — the page counter is gone from billing, and publishing will never again be blocked because of a page count. **Where:** Dashboard → Organization → Billing & Subscription **How to test:** Open the billing page. The Current Usage panel should show published sites, draft sites, AI refinements, AI images, function invocations, and team members — with no "Published Pages" row. Publish a site with more pages than your old plan allowed; it should go live without a payment prompt. **Watch for:** Any lingering mention of a page limit or page add-on, or a publish that still gets blocked with a "page limit reached" message.
When you paste a written brief with the copy for each section of a page, the chat now treats it as one change and asks whether to apply it to your current design or build it as a new variation — instead of quietly chopping it into unrelated per-section steps. **Where:** Site editor → design chat (the message box next to your preview) **How to test:** Paste a multi-section brief (headline, subheadline, CTAs, pricing spelled out per section) and send it. You should get a card asking "Apply to current design" or "Create as new variation" — not a multi-step plan. **Watch for:** Requests that genuinely target several sections ("add an illustration to each section") should still produce a multi-step plan. Only dictated copy briefs are exempt.
The recent renames (Design boards → Presentations, Agency → Growth) now carry through every screen, tooltip, empty state, and AI assistant reply — one feature, one name. **Where:** Presentations pages (dashboard overview and per-client), the pin-to-board buttons in the gallery/editor, site Settings → Growth Template, the pricing page, plan-upgrade messages, and the AI assistants' vocabulary. **How to test:** 1. Open a client's boards page — heading now reads "Presentations", and the empty state talks about presentation boards. 2. Hover the pin button on a design in the gallery — tooltip says "Add to a presentation board". 3. In a site editor, open Settings — the template section is "Growth Template" and saving points to Growth → Templates. 4. Ask the site editor assistant "where do I find my boards?" — it should answer with "Presentations", never "Design boards". **Watch for:** Any leftover "Design boards" or "Agency" labels in user-facing copy (routes like /dashboard/boards and /dashboard/agency intentionally keep their URLs).
Opening the shareable preview link for a site that hadn't been generated yet showed a server error instead of a clear "nothing to show yet" message. This affected a large share of in-progress sites. Those links now show a normal not-found page instead of crashing. **Where:** Any site's shareable preview link, before the site has been generated **How to test:** - Create a new site but don't generate it yet, then open its shareable preview link - Confirm it shows a friendly "nothing to show yet" page instead of a server error - Open the preview link for an already-generated site and confirm it still loads normally **Watch for:** A server error page when opening a preview link for a brand-new, not-yet-generated site.
The custom preview-domain setup screen was showing internal infrastructure details, and in some cases could display other agencies' preview domains. It now shows only clean, agency-facing guidance and never surfaces information about other tenants. **Where:** Workspace settings → General → custom preview domain setup. **How to test:** - Open the custom preview domain setup screen for your workspace. - Click "Check now" to re-run the domain check. - Confirm the instructions and status messages never mention internal provider names or any domain other than your own. **Watch for:** Any status/error text referencing internal service names, or listing a domain that isn't yours.
Starting a site from Quick Start with a description that didn't name the business (e.g. "a family-run Italian restaurant in Naples FL") could end up with an invented brand name like "Bella Napoli" — quietly copied from Quick Start's internal working title into the actual business name, then spread to the homepage, SEO title, and footer. The system now only uses a name you actually typed; if you didn't provide one, you're asked for it in the intake form. **Where:** Quick Start site creation → chat / intake form business name question **How to test:** - Use Quick Start with a business description that never states a name (only type/location) - Confirm the intake form asks "What's your [business type] called?" instead of silently filling one in - Confirm no invented brand name appears anywhere on the generated site if you leave the name unanswered **Watch for:** A generated site with a business name that sounds invented and doesn't match anything you typed
Renaming a site in Settings could silently do nothing to its web address — the preview link kept pointing at the old name, with no error explaining why. This happened because the system was treating any site that merely had an address label as "already live," even when it had never actually been published. **Where:** Site editor → Settings → Domain, and Settings → general site rename **How to test:** - Create a new site (don't publish it) and let it pick up a default address from its name - Rename the site in Settings - Confirm the site's address updates to match the new name, and the "Share preview" link reflects the new address - Publish a site, then rename it, and confirm the address is now locked and does not change **Watch for:** A renamed draft whose preview link still shows the old address, or a published site's address changing when it shouldn't.
Select any element in the editor and its Replace, Insert Image, and Delete actions now sit right in the toolbar instead of hiding under collapsed "Advanced" and "Danger Zone" sections you had to expand first. **Where:** Site editor → click any element on the page → toolbar above the properties panel **How to test:** - Click a text block, image, or button on the page - Confirm Replace, Insert Image, and Delete icons appear directly in the header bar above the properties panel, with no need to expand anything - Click Delete and confirm it still removes the element as before **Watch for:** Missing icons for elements that don't support one of these actions (e.g. no Insert Image on a non-image element), or the delete action behaving differently than the old confirmation flow.
Saving a site as a reusable template used to keep its images pointing back at the original site's files. Deleting that original site later would silently break every image in every preview spun up from the template. Templates now keep their own independent copies of their images. **Where:** Agency → saving a site as a template, and any preview created from that template afterward. **How to test:** Save a site as a template, then delete the original site. Spin up a new preview from the template and confirm all images still load correctly. **Watch for:** Broken/missing images in a preview built from a template whose original source site no longer exists.
Clicking "Save as template" or "Adopt" more than once in quick succession could create duplicate templates and inflate their usage counts. Separately, a template adopted from the starter gallery could end up with a broken preview later if the original gallery site was regenerated or removed. Both are fixed. **Where:** Agency → Templates (save a site as a template, or adopt a starter from the gallery) **How to test:** - Click "Save as template" on a site and immediately click it again (or another card) before it finishes — confirm only one template is created and the other buttons stay disabled until the first save completes - Adopt a starter template from the gallery, then confirm its preview still renders correctly even if the original gallery starter changes later - Try adopting the same starter twice and confirm you get back the existing template instead of a duplicate or a confusing error **Watch for:** Duplicate templates appearing for the same source site, a raw database error instead of a friendly "already saved as a template" message, or a blank/broken preview on an adopted template.
A round of fixes to the section-by-section editor: sections no longer appear multiple times in the section list, clicking a section now reliably jumps to it, and the "Add element" menu no longer opens off the bottom of the screen. **Where:** Site editor → left section panel (desktop) or the section list from the chat (mobile) **How to test:** - Open a site with nested sections or repeated headings and confirm each section appears once in the list, not two or three times - Click through several sections in the list and confirm the page scrolls to each one, including after editing content - Near the bottom of a long page, open "Add element" and confirm the menu opens upward and stays fully visible - Type in a text field for several seconds and confirm it doesn't lose focus or drop keystrokes **Watch for:** Duplicate section entries in the rail, clicks that don't scroll anywhere, an Add-element menu clipped below the viewport, or typing that gets interrupted.
The editor now shows your page as a collapsible list of sections in a left rail — click any section to scroll to it and select it for editing, or collapse the rail to a slim strip. Adding new sections and site-wide add-ons (announcement bar, popups) now lives in the same place. **Where:** Site editor (desktop) → left rail. **How to test:** Open a site in the full editor on desktop, confirm the left rail lists your page's sections in order, click one to scroll/select it, and try collapsing the rail. **Watch for:** This is desktop-only for now; mobile editing is unaffected.
Requests like "add an illustration to each section" or "add an entrance animation to every section" used to silently do nothing on sites that were imported from an existing website, because the editor couldn't see their sections. It now recognizes each section on imported pages and can plan and apply changes across all of them. **Where:** Site editor → chat with the assistant on a site that was imported/extracted from an existing website **How to test:** Open an imported site, ask the assistant to make a change to every section on the homepage (e.g. "add a subtle entrance animation to each section"), and confirm it proposes a per-section plan instead of doing nothing or only touching one section **Watch for:** A whole-page request being silently ignored, or only a single section being affected when the request was meant for all of them
When you select an element to edit in the site editor, a breadcrumb now shows exactly where it lives on the page, and clicking the section name jumps you straight to that section's content editor. **Where:** Site editor → click any element on the page to open its editing controls **How to test:** - Open a site in the editor and click on an element inside a section (e.g. a button in the hero) - Confirm the context bar above the editing controls shows a breadcrumb like "Page ▸ Hero ▸ Button" - Click the section name in the breadcrumb and confirm it opens that section's content panel - Click "Page" in the breadcrumb and confirm it deselects the element **Watch for:** A missing or incorrect section name in the breadcrumb, or clicking the section crumb not navigating to the right section's content panel.
Selecting an element used to swap away your conversation with the assistant, so you'd lose sight of what it just did. A slim activity strip above the message box now always shows the latest result — with a one-click Undo — and the "editing about this element" indicator is now a compact chip instead of a bulky panel. **Where:** Site editor → select any element → AI assistant panel, above the message box **How to test:** - Ask the assistant to make a change, then click an element on the page to open its properties - Confirm a one-line status strip appears above the message box showing the result of your last request, with an Undo button - Click the strip to jump back to the full conversation - Select an element to include it in your next message and confirm it now shows as a small chip (name, type, and a clear button) instead of a large panel **Watch for:** The strip not appearing after a request finishes, Undo not reverting the right change, or the selection chip not clearing when you deselect.
When picking a web address for a draft or new site, the system was not checking against every published site already live at that address — so a new or older site could end up minting the same address as an existing customer's published site, sending visitors to the wrong place. Address checks now also account for already-published sites, closing that gap, and older sites that never had a shareable draft link now get one. **Where:** Any site's preview/draft link, and address selection during site creation or publishing **How to test:** - Open an older site created before shareable draft links existed and confirm it now has a working draft link - Attempt to create or rename a site to an address that's already used by a live, published site — confirm it's correctly rejected as taken **Watch for:** A draft preview link opening someone else's published site, or a site's draft link failing to load.
Actions that build or refresh your site's navigation menu (like adding a page) could crash if the site's design hadn't been generated yet, instead of simply showing an empty menu. **Where:** Client portal → Pages tab → add or manage pages on a site before generating its design **How to test:** Create a new site, don't generate a design yet, then add a page or trigger a navigation refresh — it should complete without error **Watch for:** Errors when adding pages or syncing navigation on a site with no generated design yet
The "Tweaks" button used to pop open a separate floating card over your site. It now opens a "Styles" tab inside the same assistant panel you already chat in, so switching between chatting and adjusting colors, fonts, and spacing feels like one continuous flow. **Where:** Site editor → toolbar → Tweaks button (opens the Styles tab in the assistant panel) **How to test:** - Open a site in the editor and click the Tweaks button in the toolbar - Confirm it opens a "Styles" tab inside the assistant panel (not a floating card) - Hover over a style option to preview it, then click to apply it - Confirm the panel returns to the chat view after the change is applied **Watch for:** The Tweaks button not toggling the tab correctly, or style previews not layering on top of your current design.
Agencies with no templates (or no sites at all) can now start from curated platform templates — and the suggestions are smart: they're ranked by who you're actually prospecting. What changed: - The Templates page and the campaign wizard now offer **starter templates** whenever you have none of your own. Each card shows *why* it's suggested — "Matches 12 of your prospects", "You recently scanned for 'plumbers'", "Related to your restaurant prospects" — based on the industries of your imported/scanned prospects and your saved scan territories. With no signals yet, the most popular starters show instead. - One click on "Use this template" adopts the starter as a real agency template (frozen copy, swappable business fields auto-detected) — in the wizard it's selected automatically and the campaign continues without leaving the flow. - The Templates page's "New template" picker now has two sections: **Your sites** and **Starter templates**. Starters you've already adopted show an "Added" chip instead of the button. **Where:** Top nav → Growth → Templates (empty state or "New template"), and Growth → Campaigns → New Campaign step 2 when you have no templates. **How to test:** In an org with prospects but zero templates, open Templates — starter cards should appear with match-reason chips that reflect your actual prospect industries. Click "Use this template" → it becomes one of your templates without leaving the page. Then start a New Campaign in a zero-template org and confirm step 2 offers the same starters and auto-selects after adopting. Adopt the same starter twice — no duplicate should be created. **Watch for:** Match reasons that don't reflect your prospects (e.g. restaurant suggestions for a plumbing-only prospect list); adopting failing with a raw error; the wizard step 2 dead-ending instead of showing starters; duplicate templates after double-clicking.
Starter template recommendations were supposed to highlight templates matching your prospects' industries, but a gap in how industries were recognized meant most templates couldn't be matched at all — so nearly everyone just saw generic "Popular starter" suggestions instead of ones tailored to their prospects. **Where:** Top nav → Growth → Templates (empty state) and Growth → Campaigns → New Campaign step 2 **How to test:** - In an org with prospects concentrated in a specific industry (e.g. mostly dentists), open the Templates starter suggestions - Confirm at least some cards show a specific match reason like "Matches N of your prospects" rather than every card saying "Popular starter" - Repeat in the campaign wizard's template step **Watch for:** Every starter template still showing only "Popular starter" for an org with industry-concentrated prospects; a template's industry label showing a raw internal value instead of a clean industry name.
When picking a starter template for a new prospect, the suggested industry tag sometimes showed a raw internal label (like "url-decision-intelligence-platform-oravia") instead of a readable name. On top of that, the suggestion ranking only looked at a subset of templates, so a perfectly-matching low-popularity template could be passed over for an unrelated popular one. **Where:** Growth → Templates, and Growth → Campaigns → New campaign → prospect step **How to test:** - Open Growth → Templates and Growth → Campaigns → New campaign - Check the suggested starter templates — any industry tag shown should be a readable name (e.g. "Plumbing"), never a slug with dashes, and templates with no clear industry match should show no tag at all - Confirm a strong industry match appears near the top of suggestions even if it has few past uses **Watch for:** A dash-separated or otherwise raw-looking label appearing on a suggestion chip, or an obviously-matching template being buried below unrelated popular ones.
Typing a description into the dashboard's quick-start prompt box and submitting it could silently do nothing — your message would appear in the chat, but no AI response ever came back. Quick-start now properly creates your site first and lands you in the builder, and it correctly uses whichever workspace you're currently viewing. **Where:** Dashboard → prompt box on the empty/getting-started screen **How to test:** - On a dashboard with no sites yet, type a business description into the prompt box and submit - Confirm you land in the site builder and the AI responds to your first message instead of the chat going silent - Switch to a different organization and repeat — confirm the new site is created in that organization, not another one **Watch for:** The prompt box appearing to accept your message but the builder never generating a response, or a quick-start site landing in the wrong workspace.
Submitting the guided intake form could silently overwrite the business description you'd already typed with a copy of the form's own questions and answers — and that description feeds your site's generated copy, design direction, and SEO summary, so the whole site suffered. **Where:** Site creation → intake form flow (fill out the guided questions after describing your business) **How to test:** - Start a new site, type a real multi-sentence business description, then continue through the intake form - After submitting the form, check that your original business description is still intact (not replaced with form-answer text like "here are my answers in full") - Confirm the generated site still reflects your original description **Watch for:** A business description that reads like a form transcript ("(you decide)", bolded question labels) instead of your own words; generated copy that ignores details you originally provided.
Selecting an element and asking for a simple style change (for example "change button color to purple") could come back with "I wasn't able to apply that change — the code came back unchanged", even though the right element was selected. The edit was being made correctly and then discarded before it reached your site. **Where:** Site editor chat — select any element on the canvas, then ask for a change. **How to test:** Open a site, click a button or heading inside a section, and ask to change its colour. The change should appear in the preview and persist after a reload. **Watch for:** Edits to elements that live in a shared block (header, footer, hero) or on a sub-page rather than the homepage — those were the ones most likely to silently do nothing.
Flipping a site's theme (for example dark to light) would repaint the background but leave some text using a fixed color that didn't change with it — leaving headings and other text invisible against the new background. Theme switches now re-check every piece of text against its actual background and automatically recolor anything that would become unreadable, while leaving intentionally colored text (like white text on a colored button) alone. **Where:** Site editor → Settings/Style → theme or color mode toggle, or ask the assistant to switch the site's theme **How to test:** - Open a site with a light theme and switch it to dark (or vice versa) - Check headings and body text throughout the homepage for any invisible or near-invisible text against its background - Confirm text intentionally placed on colored buttons or brand-colored blocks still looks the same as before **Watch for:** Text that's the same color as its background after a theme switch, especially headlines or stat numbers
Changing your active organization while building a campaign now restarts the wizard cleanly in the new organization, instead of carrying over a selection that no longer exists there. **Where:** Growth → Campaigns → New campaign, then switch organization with the org switcher. **How to test:** Start a campaign, select a few prospects, then switch to a different organization. The wizard returns to the Prospects step, the selection is empty, the counter reads "0 selected", and Continue stays disabled until you pick a prospect from the organization you're now in. **Watch for:** Continue being clickable with nothing selected; a footer that counts prospects you can't see in the list; a build step that offers "Build 0 preview sites" and then refuses to continue.
On sites that mix regular page content with a catalog like products or a menu, asking the assistant to edit a catalog item could make it try anyway, fail, and give you a clumsy "sorry, I can't do that" after wasting a turn. The assistant now knows upfront which parts of your content it can edit directly, so it goes straight to the right answer instead of attempting and failing. **Where:** Site editor → AI assistant chat, on a site with both inline content (contact, services, team) and catalog-backed content (products, menu, listings) **How to test:** - Open a site with both an inline section (e.g. contact) and a catalog section (e.g. products) - Ask the assistant to edit a product, then ask it to edit the contact details - Confirm the product request gets clear guidance without a failed attempt, and the contact edit still applies normally **Watch for:** The assistant attempting a catalog edit before explaining it can't, or inline edits (contact, services, team, FAQs) no longer working.
If you skipped the business name question in the guided intake form, the assistant would silently make one up and use it everywhere — the homepage, the browser tab title, and search results — even though the form promised leaving it blank was fine. Leaving the name blank now actually leaves it blank, and you're asked for it again before your site is generated. **Where:** Site creation → guided intake questions (business name question) **How to test:** - Start a new site from a description that doesn't mention a business name - When asked for the business name in the intake form, leave it blank and continue - Confirm you're prompted for the name again before generating, and that no invented name appears on the generated homepage, tab title, or search summary **Watch for:** A generated site with a business name you never provided, especially one that sounds plausible but wrong (e.g. a made-up brand name)
The small activity strip above the site preview could silently lose its Undo button as soon as anything else happened after your last change — even a simple status message — forcing you back into the chat tab just to undo. Undo now stays available and, when it's reverting something other than what's shown, it labels itself with what it will undo so you always know what you're about to revert. **Where:** Site editor → activity strip above the preview (appears after the AI assistant makes a change) **How to test:** - Ask the assistant to make a change, then send a follow-up message that doesn't change the site (e.g. a question) - Confirm the Undo button is still visible in the activity strip, and its label names the change it will revert if that's not the most recent message **Watch for:** The Undo button vanishing after any non-code-changing assistant reply; Undo reverting a different change than what's labeled.
Draft previews served on your site's own web address were loading with pieces missing, and the address itself was never shown to you. Both are fixed. **Where:** Site editor → Settings → Domain, and the draft preview link for any site. **How to test:** 1. Generate a new site and wait for it to finish. 2. Open Settings → Domain. You should now see the site's own address (e.g. `your-business.fullyloadedsites.com`) — not a blank field, and never the word "null". 3. Open that address with `/preview` on the end. The draft should load completely: images, pop-ups, forms and buttons all working. 4. Click through to an inner page, then use the browser's Back button. Everything should behave normally. **Watch for:** A preview that hangs on a spinner, or shows an error box mentioning an unexpected character. Also watch for any address containing "null", or a site on one of the newer domains being shown an address ending in a different domain than the one it actually lives on.
When you ask for simpler content, we now also rewrite the wording itself into plain, everyday language — not just trim its length. **Where:** Site editor → "simpler content" requests (variation feedback, describe modal, or chat) **How to test:** On an existing site, ask for simpler content. Headlines and section copy should drop jargon-heavy phrasing (invented tech-labels, corporate-speak) and read in plain language, while names, prices, and contact details stay exactly the same. **Watch for:** Any fact (price, name, number, contact info) changing — those should never change; only the wording and length should.
The dashboard no longer splits your work across Builds, Designs and Chats tabs. Every project is one card with a clear stage — Draft brief, Concepts ready, In production, Live — and a button that says exactly what you'll land in. New accounts start with a single question ("What are we building today?") instead of an empty management screen, and busy accounts get a "Needs your attention" feed that surfaces publish failures and fresh design concepts across all clients. **Where:** Dashboard (app.mondovo.com/dashboard). Header nav renamed: Design boards → Presentations, Agency → Growth, plus a new Inspirations link to the design gallery. **How to test:** 1. Log in with an account that has sites — you land on "My Sites" with stage filter pills (All / Drafts / Concepts / In production / Live) instead of tabs. 2. Check the "Needs your attention" section lists designs awaiting review and failed publishes; each links straight to the right place. 3. Search still works (including smart semantic matches), and grid/list toggle, rename, clone, delete, bulk move are unchanged. 4. On a build card forked from a design, check the "Built from a design · explore other concepts" link. 5. With a brand-new account (0 sites), the dashboard shows a prompt box — describe a business and it creates the site and drops you into the chat with your description pre-submitted. **Watch for:** Designs already used by a build are hidden from the default view (they appear under the Concepts filter, in search results, and via the build's lineage link) — make sure nothing seems "lost". Stage counts should match what each filter shows.
Spinning up a preview site for a prospect from a template used to leave behind the template's own business identity in places beyond the obvious ones: descriptive copy that still read like the original template's business, and SEO details (page titles, descriptions, keywords, social previews) that still named the template instead of the prospect. Both now fully rebrand to the prospect. **Where:** Growth → Prospects → Spin up preview (single or batch). **How to test:** Spin up a preview for a prospect in a different industry than the source template. Check the site's body copy, browser tab title, and a shared link preview (og:title) — all should name the prospect's business, not the template's. **Watch for:** Any page title, meta description, or shared-link preview still naming the original template business.
The Billing & Subscription page was showing an empty "Change Plan" section and a "Failed to load usage data" error. Both now load correctly. **Where:** Dashboard → Organization → Billing & Subscription **How to test:** Open the billing page for an organization that has at least one published site. The plan cards (Free, Starter, Pro, Growth, Partner) should render with the monthly/yearly toggle working, your current plan badged. The Current Usage panel should list published sites, draft sites, published pages, AI refinements, AI images, and team members instead of an error. **Watch for:** An empty plan grid, a "Failed to load usage data" message, or usage numbers that stay at zero for an org that clearly has published sites.
When importing an existing website fails (for example, it's temporarily unreachable), we now say upfront that we'll build from what you describe instead — with a prompt to paste your existing copy or retry the link — instead of leaving the failure looking like an unexplained error. **Where:** Site intake → "Clone my existing site" (URL import) **How to test:** Start a new site and provide a URL that can't be fetched (e.g. one returning a 503). The follow-up message should explain we'll build from what you share here, not just report that the fetch failed. **Watch for:** The retry/paste guidance missing, or the message still reading like a bare error.
The color question during intake no longer forces a pick from a handful of generic per-industry palettes — you now just say whether you want a light or dark look (or let us decide), and your actual colors are derived from your brand, logo, or reference at generation time. Colors stay fully editable afterward. **Where:** Site intake → preference questions → "Light or dark?" **How to test:** Start a new site through intake; confirm the color question is a simple light/dark/decide chip rather than a swatch palette picker, and the generated design's colors reflect your brand rather than a canned palette. **Watch for:** Picking dark mode but getting a light design (or vice versa).
Some sites showed a phantom "Contact Form" in their Forms list — one nobody created, with meaningless fields like "Field 1" and "Field 2" and a block of internal diagnostic text as its description. These were never real forms and could not be used; they were an artifact of the editor mistaking one of our own built-in components for a form you had authored. New sites can no longer pick these up, and the 51 existing sites that had one have been cleaned. **Where:** Site editor → Forms (Mission Control left rail) **How to test:** Open the Forms list for a site that previously showed a stray "Contact Form" with "Field 1"/"Field 2" fields. Only forms you actually created should be listed. Add a real form to a page and confirm it still gets picked up and listed correctly. **Watch for:** A genuine inline form on a page failing to appear in the Forms list, or a form you created disappearing from it.
Text and buttons that blended into their background — like a white "Book now" button on a white section — are now caught even when the background color comes from a surrounding section rather than the element itself. **Where:** Applies automatically during site generation and design edits — no action needed. **How to test:** Generate or refine a site and check that button and text colors always contrast with the surface behind them, including sections that set a background color on a parent container rather than the button itself. **Watch for:** A button or text that's still hard to read against its background, or a legitimate bordered/secondary button incorrectly flagged as low-contrast.
In rare cases, a catalog section (like a menu or product list) could be saved with a placeholder in place of its real items, which would break that section on the live page instead of just showing stale content. Saving now cleans this up automatically. **Where:** Any catalog-style site (restaurant, real estate, e-commerce, hospitality, car dealership, education, events) — menu, product, listing, or similar sections. **How to test:** - Open a catalog-vertical site (e.g. a restaurant menu or product listing) and confirm the section renders its items normally. - Make an edit and save; the listing should continue to render correctly with no errors. **Watch for:** A catalog section that fails to render entirely (blank where items should be) rather than just showing outdated items.
If you reloaded the page while your site was still building and that build later failed, you could get stuck on a "Generating..." spinner forever — even though a usable design had already been produced and was ready to show you. **Where:** Site editor, right after creating or regenerating a site. **How to test:** - Start generating a new site, then reload the page mid-generation to resume watching progress. - If the underlying generation run fails after the reload but a design had already been produced, you should be handed that design instead of being left on a spinner. **Watch for:** A "Generating..." spinner that never resolves after a page reload, even though the site actually finished (or partially finished) building.
If creating a site from the start page hit a rare, temporary hiccup, retrying with the same prompt could get permanently blocked with a "duplicate submission" error — even though no site had actually been created. Retries now recover automatically instead of dead-ending. **Where:** Start page → creating a new site from a business description. **How to test:** - Start a new site from a prompt; if creation ever fails partway through, retry with the same prompt. - The retry should succeed in producing a site rather than repeatedly failing with a duplicate-submission style error. **Watch for:** A "Failed to create site" error that keeps recurring on retry with the exact same prompt, with no way to proceed.
On phones, the "Undo last change" button could render on top of the "Ask AI for bigger changes" tip, covering its "Open Assistant" button and making both hard to use. The tips now sit above the floating controls, and they no longer run off the edge of narrow screens. **Where:** Site editor on a phone (or a desktop browser window narrower than 768px). **How to test:** Open a site in the editor on mobile, leave it idle for ~20 seconds so the "Ask AI for bigger changes" tip appears, and make a change so the "Undo last change" button shows. Both should be fully visible and tappable, stacked without covering each other. **Watch for:** Any tip card that gets clipped by the screen edge, or a tip that sits underneath the chat button, the undo button, or a status message.
Leads captured by your site forms are now labelled with real field names like `email`, `phone` and `company` instead of placeholders like `field_4` or garbled text pulled from example copy. **Where:** Site editor → Forms, and any form submission in your Inbox. **How to test:** Open a site with a contact or quote form, check the form's fields in the Forms panel, then submit a test enquiry and confirm the columns in the Inbox read as proper field names. **Watch for:** Forms you already created keep their existing field names — nothing is renamed, so past submissions stay intact. The improvement applies to forms detected from here on; regenerate or re-open a site's forms to pick it up.
The Growth (agency outreach) home page now teaches the workflow instead of just reporting on it, and generated preview sites can finally be approved or rejected before outreach. What changed: - The hub opens with a "next best action" banner — one computed suggestion based on where your pipeline actually is (e.g. "100 prospects haven't been assessed yet → Assess websites"). - Four numbered step cards (Find prospects → Build previews → Send outreach → Win clients) each show their live count and the action that unblocks them, including prerequisites like "Needs a template" or "Needs a sender email" that used to be discovered as dead ends deep inside sub-pages. - The pipeline funnel now shows real stages (Assessed, Email found, Preview built, Contacted, Won) and every row is clickable — it takes you to the filtered list where you act on that stage. Previously four of the six funnel rows could never be non-zero. - Every Growth page shares a persistent sub-nav (Overview · Prospects · Templates · Previews · Campaigns) — no more round-tripping through "Back to Agency". - Previews can now be Approved / Rejected (with Undo). The old button said "coming soon"; review status is now stored for real and the Pending/Approved/Rejected filters reflect it. - Prospect filters are shareable URLs (e.g. ?filter=unassessed), with new Unassessed and Has Email filters. **Where:** Top nav → Growth (app.mondovo.com/dashboard/agency) **How to test:** Open the Growth tab with prospects imported but nothing assessed — the banner should tell you to assess websites and link into the pre-filtered prospects list. Build a preview from a template, open Previews, click Approve, reload — the status should persist. Click each funnel row and confirm it lands on the matching filtered view. **Watch for:** Funnel rows showing zero after you've assessed prospects; Approve/Reject not persisting after reload; the sub-nav highlighting the wrong tab; deep-link filters not applying on first load.
The design gallery now lives inside your dashboard. Browse professionally designed sites, preview any of them, and click "Use as base" — we copy that design into a brand-new site in your workspace and drop you straight into the editor chat to make it yours. **Where:** Dashboard → Inspirations (top nav), or "start from a design you love" on a fresh account's home screen. **How to test:** 1. Click Inspirations in the dashboard header — the gallery opens inside your workspace (no more being sent to the public site). 2. Search ("restaurant", "law") and switch Popular / Newest / Featured. 3. Hover a design → Preview opens the live design; "Use as base" creates a new site from it and lands you in the design editor. 4. The new site appears on your dashboard as a concept ready to adapt. **Watch for:** "Use as base" copies the design's images into your own site's storage — the copy can take ~10 seconds on image-heavy designs; the button shows "Setting up…" while it works.
Site intake now always includes a "How should it sound?" question (Friendly & simple, Confident & modern, Professional & trustworthy, and more), and your answer reliably shapes the generated copy's voice — previously this question could be skipped, and even when answered wasn't always connected to the copy. **Where:** Site intake → preference questions → "How should it sound?" **How to test:** Start a new site, pick a tone like "Friendly & simple" during intake, and confirm the generated copy reads casually and plainly rather than defaulting to generic enterprise marketing language. **Watch for:** Copy still reading in a generic corporate register despite picking a distinct tone.
Chatting with the AI on mobile could behave noticeably differently from desktop — missing clarification questions, missing "are you sure" prompts before big rewrites, and confusing raw error text on failures. Mobile now goes through the exact same handling as desktop. **Where:** Site editor on a phone → chat bubble. **How to test:** - On a phone (or a narrow browser window), open the chat and send a request that would normally trigger a clarifying question or a "big change" confirmation on desktop. - Confirm the same clarification/confirmation options appear on mobile. - Trigger a failed request and confirm you see a friendly error message rather than a raw "Load failed" or "Failed to fetch". **Watch for:** Duplicate "Undoing changes..." spinners, or mobile chat silently applying a change that desktop would have asked to confirm first.
On phones, the intake questionnaire used to appear already scrolled to its footer, so it looked like it had ended and you had to scroll up to find the first question. It now opens on Question 1, and each section starts at the top as you move through it. **Where:** Create a site on a phone (or a narrow browser window) — enter your business name and description, then answer the questionnaire the assistant sends back. **How to test:** The form should land with Question 1 visible at the top. Tap Next through each section and confirm each one starts at its first question rather than at the buttons. Answering a question should never jump the page around. **Watch for:** The page jumping to the bottom of the chat while the form is open, a section opening mid-way down, or the form failing to come into view at all after the assistant sends it.
Requesting a new design variation now runs with the same intelligence as first-time generation: your feedback is translated into concrete design direction (an AI-authored design brief that deliberately diverges from every design you already have), requests like "video hero" or "simpler content" become real structural changes instead of being half-ignored, video/image heroes auto-fill from stock footage when you haven't uploaded an asset, and catalog sites (restaurants, real estate, etc.) keep using your real catalog items instead of inventing new ones. Variations also get their gallery screenshots and automatically retry on a backup model when the primary is overloaded. **Where:** Site editor → design gallery → "New variation" (both the quick text box and the describe modal), and variations created via connected AI tools **How to test:** On a site with 1–2 designs, ask for a new variation with "video hero and simpler content". The result should have a working background video in the hero (or an honest notice if no stock clip fit), visibly shorter copy, and a look clearly different from your existing designs. **Watch for:** Variations that still look like reskins of an existing design; a hero video that shows as a blank dark area (the new empty-media check should prevent this); catalog sections showing items that don't match your Content Manager items.
On iPhones and iPads, a brief network hiccup while a design's resources were loading could show a red error screen and roll the preview back to an older version — even though nothing was wrong with the design itself. The preview now recognises these as temporary loading failures, retries them, and shows a friendly "try again in a moment" message instead. **Where:** Site editor → any design preview, on an iPhone/iPad (or any browser on iOS). **How to test:** Open a site's design preview on iOS. Throttle or briefly drop the network while the preview loads. You should see the retryable "Preview didn't finish loading" message, not a red error, and the design should recover on retry rather than rolling back. **Watch for:** A design with genuinely broken code must still surface a real error — the friendly loading message should only appear for connection/loading failures, never for actual code problems.
A brief network hiccup while the preview loaded could leave Safari and iPhone users staring at a red "Preview Error" screen, even though nothing was wrong with their site. The preview now retries and recovers on every browser, instead of only on Chrome. **Where:** Site editor preview, on Safari or any browser on iPhone or iPad. **How to test:** Open a site in the editor on an iPhone or in desktop Safari and let the preview load. It should render the site; if a dependency is briefly unavailable it should retry and recover rather than showing a red error. **Watch for:** A red "Preview Error" screen that mentions a module or script failing to load. If one appears, it should now explain that it is a temporary network issue and that reloading will fix it, and it should no longer roll your design back or kick off an automatic repair.
When a design preview failed to load its resources, the editor showed a raw technical error instead of simply trying again. It now retries automatically, and if it still can't load you get a plain-language message and a Try again button. **Where:** Site editor and design pages — the preview panel. **How to test:** Open a site's design view on a flaky or slow connection (mobile Safari is the easiest way to reproduce). If the preview stumbles while loading, it should reload itself and come up normally rather than showing a red error block. **Watch for:** A red error panel containing technical text (dependency counts, package names, mentions of bundles). Nothing like that should ever reach the preview screen now — if it does, that's a regression.
Catalog-backed sections (products, menus, properties, listings) sometimes rendered as an empty grid in the design preview even though the items existed — they now stay filled while you switch designs, regenerate, or refresh. **Where:** Site editor, Design phase — any catalog section or listing page (for example an "All Products" page on a store site) **How to test:** Open a store or catalog site in the design editor, switch between designs (D1/D2), then open the products page. The product cards should be there every time, not just on the first load. **Watch for:** An empty catalog grid, or an item count that reads zero when the items clearly exist in your content library.
A dedicated listing page (like "All Products") was showing only the same handful of items as the homepage's preview section, instead of your full catalog — even though the published site correctly showed everything. Preview now matches what gets published. **Where:** Site editor preview → any dedicated listing page for a catalog (e.g. "All Products", "Full Menu"). **How to test:** - Open a catalog site with more items than the homepage preview shows (e.g. 12 products where the homepage only features 4). - Navigate to the listing page for that catalog in the editor preview. - Confirm the listing page shows all items, while the homepage section still shows its smaller featured set. **Watch for:** A listing page in preview showing fewer items than actually exist in your catalog, or preview and published site disagreeing on item counts.
The "+" menu in blueprint chat had stopped showing the "Manage connections" option, so it was no longer reachable from that chat surface. **Where:** Blueprint chat → the "+" menu next to the message box. **How to test:** - Open blueprint chat and click the "+" menu. - Confirm "Manage connections" appears and opens the connections view in place. **Watch for:** The "+" menu missing the "Manage connections" item, or the item navigating away instead of opening in place.
Previously, generating a new design by applying a different style ("See in Other Styles") could silently lose all progress if you closed the browser tab while it was working — despite the "this takes a minute" message suggesting it was safe to do so. That work now continues on our servers and lands as a new design automatically. **Where:** Site editor → Designs → "See in Other Styles" → pick a style. **How to test:** Start a style adaptation, then close the browser tab immediately. Reopen the site editor after a minute or two — the new design should appear in your Designs list without you having to redo anything. **Watch for:** A style adaptation that never completes or never shows up as a new design after closing and reopening the editor.
Typing a website idea into the prompt box on the homepage and hitting Generate now takes you straight into the site builder with your prompt already sent — instead of dropping you on the dashboard and making you type it again. **Where:** Homepage prompt box (the "Create a website for..." field), then Generate. **How to test:** From the homepage, enter something like "Create a website for a furniture company" and click Generate. You should land in the Site Builder for a brand-new site, with your prompt already posted as the first chat message and the assistant replying. Signing in (rather than registering) from that same flow should also resume the prompt instead of stopping at the dashboard. **Watch for:** Being redirected to the dashboard, an empty chat asking "What's your business or site name?", or a site that fails to get created.
If you describe your business without naming it (common when starting from the homepage prompt or the dashboard's "What are we building today?" box), the intake form now asks "What's your business called?" as its first question — instead of you discovering at the very end that Generate is blocked on a missing name. **Where:** The question form that appears after your first message in the site-builder chat. **How to test:** 1. Start a new site with a description that names no business (e.g. "a family-run Italian restaurant with online reservations"). 2. The intake form's first question asks for the business name. 3. Describe a business WITH a name ("a restaurant called Bella Napoli") — the question is skipped. **Watch for:** We never invent a name for you — leaving the question blank is allowed, and Generate still requires a name before it unlocks.
Renaming your workspace or changing its primary colour failed with a red error banner and silently reverted on reload. Both now save and persist. **Where:** Workspace settings → General **How to test:** Change the Organization Name and/or Primary Color, click Save Changes, then reload the page — the new values should still be there. **Watch for:** The error banner reappearing, the colour swatch resetting to blue after a reload, or the Organization Type field showing "Standard" instead of your actual workspace type.
Forms on your second design now work the moment it appears, instead of showing a red error box until you refreshed the page. Separately, buttons whose text matches their background colour — white-on-white, invisible — are now flagged automatically. **Where:** Design page → the D1 / D2 design switcher, and the Issues panel in the editor. **How to test:** 1. Generate a new site and wait for both designs to finish. 2. Click straight to D2 without refreshing, and scroll to the contact form. It should render its real fields — no red "Form config missing" box. 3. Switch back to D1 and confirm its form still renders too. 4. In the editor's Issues panel, a button styled with your theme's primary colour and matching text colour is now reported as low-contrast. **Watch for:** A form that renders on one design but not the other, or a design whose form fields differ from the ones you configured. Also watch for the Issues panel over-reporting contrast on buttons that only *hover* to a matching colour — that is correct styling and should stay unflagged.
Kicking off a new design now gives you a clear confirmation, and the "Generating…" indicator survives a page refresh so you always know a design is on the way. **Where:** Site builder → design page → "+ New" (generate a new design) **How to test:** Start a new design from the design page. You should get a confirmation explaining it takes a few minutes, runs in the background, and that your existing designs stay fully usable. Refresh the page while it's still generating — the "Generating…" tab and progress should still be there, and the new design should appear on its own the moment it's ready. **Watch for:** A refresh that drops back to a plain preview with no generating indicator, a "Generating…" tab that never clears, or a finished design that only shows up after a manual refresh.
Voice calls to your AI agent occasionally lost access to your site's real data and fell back to a generic, canned assistant that couldn't answer anything specific — this is now fixed, and the assistant rides out brief hiccups instead of giving up. **Where:** Voice calls to your site's phone number (and the Mondovo WhatsApp assistant number). **How to test:** - Call your site's voice agent number and ask something that requires real data (e.g. "what are your hours?" or "do you have any openings this week?") - Confirm the assistant answers using your actual site content, not a generic scripted response - If a request briefly fails, confirm the assistant treats it as a momentary hiccup ("having trouble reaching your account, try again in a moment") rather than acting like it has no way to look things up **Watch for:** The assistant reverting to a generic, tool-less persona for an entire call; answers that don't reflect the caller's actual site or account data.
Fixed a rare issue where a WhatsApp voice call placed during a platform update could lose access to its tools and be unable to answer questions for the rest of the call. **Where:** WhatsApp voice calls to any site with the voice bot enabled. **How to test:** - Place a WhatsApp voice call to a site with voice enabled during or right after a platform deploy. - Confirm the assistant can still answer business-specific questions instead of falling back to a generic, tool-less response. **Watch for:** A voice call that suddenly can't answer any business-specific questions for its entire duration — that would indicate the fallback persona is still being triggered.
The Site Assistant chat now reliably stays scrolled to the newest message, and reopening a chat lands you at the bottom ready to type — no more manual scrolling on mobile. **Where:** Site editor → Assistant panel (right rail and mobile sheet) **How to test:** Open a long existing chat on mobile — it should open at the most recent message. Send a prompt and watch the response stream in; the view should stay glued to the bottom instead of jumping. **Watch for:** Scrolling up to read earlier messages should still show the "New" jump pill and must not yank you back down mid-read.
Account Settings could not load your linked sign-in methods, and the account menu showed a plan you were never on. **Where:** Avatar menu → Account Settings, and the plan badge in the avatar menu itself **How to test:** 1. Open the avatar menu. The plan badge should match your actual subscription (Free, Starter, Growth, Pro, or Partner). 2. Click Account Settings and scroll to Linked Accounts. 3. Your existing sign-in methods should be listed with a "Connected" badge — no red error. 4. A provider you have already linked should never offer a "Link Account" button. **Watch for:** "Failed to load linked accounts" reappearing; a provider you use to sign in showing as "Not connected"; a plan badge reading "Enterprise" or any plan you do not pay for; the Current Plan on the Settings page disagreeing with the badge in the menu.
Follow-up fixes to the recent chat redesign: the copy button in AI chat now tells you when copying fails instead of doing nothing, and pages with custom letter-spacing (marketing pages, templates) no longer have it silently flattened. **Where:** Any AI chat panel (site editor assistant, dashboard assistant, blueprint chat); marketing/landing pages and site templates. **How to test:** 1. Hover an assistant message and click the copy icon — it should still copy normally and show the brief confirmation. 2. Visit a landing page or template that uses tighter/looser letter-spacing (e.g. a hero headline) — the custom spacing should render as designed instead of looking uniformly default. **Watch for:** Copy silently doing nothing with no error shown; headings on marketing pages or templates looking like default spacing when the design intends something tighter or looser.
The Mondovo assistant on our WhatsApp line can now actually work on your sites — check status, answer product questions, and make changes — with the same understanding it has inside the editor. **Where:** Message or call Mondovo's WhatsApp number. Link your number first from Dashboard → Settings → Account. **How to test:** 1. Link your WhatsApp number, then message the Mondovo number. 2. Ask about your sites ("what sites do I have?", "is my site published?") — you get real answers. 3. If you have more than one site, tap a site from the quick list to choose which one to work on, or just name it. 4. Ask for a change ("publish my site", "add an About page") — the assistant shows a summary with Confirm / Cancel buttons. Nothing happens until you tap Confirm. 5. Not linked yet? Ask a product question and you still get a helpful answer plus a one-tap link to connect your account. **Watch for:** Confirm buttons should run the action once and then expire; a stale or someone else's button must not do anything. Replies should read cleanly on a phone (no raw markdown), and the assistant must never mention how it's built.
The Mondovo assistant on WhatsApp is now built for working on the go: refer to any site by name, get a screenshot or a share link in the chat, check the numbers that matter, and even send a photo to use on your site. **Where:** Message Mondovo's WhatsApp number. Link your number first from Dashboard → Settings → Account. **How to test:** 1. Refer to a site by name ("show me the bakery site", "switch to Online Maximizer"). If two sites share a name, tap the right one from the list. 2. Ask to "see" or "preview" a site — you get a screenshot right in the chat, or a tappable preview link when there's no image yet. 3. Say "share the link" / "send this to my client" — you get a preview link with an "Open preview" button to forward. 4. Ask the on-the-go questions: "is it live?", "any leads today?", "how many visitors this week?", "did my domain verify?", "what's my plan and how many credits are left?", "show me version history". 5. Send a photo. With a caption ("use this as the hero"), you get a Confirm / Cancel summary. With no caption, you get quick buttons — Hero image, Save to library, or Cancel. The photo is saved to that site's library either way. **Watch for:** Every change still needs a Confirm tap and nothing runs until you tap it. A photo you send twice should only be handled once. If you haven't picked a site yet, the assistant asks which one rather than guessing. The assistant should never mention how it's built.
The Share Preview link couldn't be selected or copied reliably on mobile, and the copy button had no visible label. **Where:** Site editor → Share (toolbar Share icon) → Preview URL **How to test:** 1. Open Share Preview on a mobile device or narrow browser window. 2. Tap the Preview URL field — the full link should be selectable. 3. Tap "Copy Link" — it should show a labeled "Copied!" confirmation. 4. On a device that supports native sharing, a "Share" button should appear next to Copy Link and open the OS share sheet. **Watch for:** The Preview URL field not being selectable/tappable; the copy button showing only an icon with no confirmation; the Share button appearing on desktop browsers where it isn't supported.
The AI chat panels across the dashboard and site editor got a cleaner look — assistant replies now read more like plain text than chat bubbles, and you can copy any message with one click. Text sizing and spacing were also unified across every screen for a more consistent feel. **Where:** Any AI chat panel (site editor assistant, dashboard assistant, blueprint chat) and general dashboard/editor pages. **How to test:** 1. Open an AI chat panel and send a message — assistant replies should appear as clean, wide text rather than a narrow bubble. 2. Hover an assistant message and click the copy icon — the message text should copy to your clipboard with a brief confirmation. 3. Browse a few dashboard and editor pages — headings, labels, and body text should feel consistent in size and spacing. **Watch for:** Copy button failing silently, chat text overflowing its container on mobile, or inconsistent letter-spacing/text sizing on pages using custom fonts.
There were two different pages both called "Organization Settings", and the account menu mixed your profile in with features like Design boards. Features now live in the top nav, and all workspace settings live on one page with tabs. **Where:** Top navigation bar, and the avatar menu (top right) **How to test:** 1. Look at the top nav: Sites, Design boards, Agency, and Refer & Earn are now there, and the current section is highlighted. 2. Open the avatar menu. It now holds only Account, Workspace settings, Billing & credits, your organizations, and Sign Out. 3. Click Workspace settings. Tabs across the top: General, Team, Billing, Integrations, Advanced. 4. Check the Billing tab shows the plan you actually pay for. 5. Deleted sites and Leave/Delete organization now live under Advanced. API keys, Figma, and connected AI assistants live under Integrations. 6. An old `/dashboard/settings` bookmark should land on the Integrations tab. **Watch for:** A settings section you used that you can no longer find under any tab; the Billing tab naming a different plan than the badge in the avatar menu; a Figma or AI-assistant connection that returns you to a blank page after authorizing.
Changing to a lower plan used to count sites you had already deleted against your new plan's limits, telling you to "delete N sites" you could no longer even see. Deleted sites are now excluded from that check, and if usage can't be verified the downgrade is blocked instead of silently allowed. **Where:** Dashboard → Organization Settings → Billing → Change Plan **How to test:** Trash a few draft or published sites so your visible site count is under the new plan's limit, then attempt to downgrade — it should succeed without asking you to delete sites you can no longer see. **Watch for:** A downgrade being blocked for a plan-limit reason when your visible (non-trashed) site count is actually within the new plan's limits.
When a client's chosen design is applied to a different site, its catalog content (menu items, listings, product cards, etc.) now comes along, so the design lands with real content instead of empty sections. **Where:** Design Boards → "Mark as client's choice" → "make it live on {site}", when the picked design and the target are different sites. Also the same cross-site apply path used by the decision action. **How to test:** Pick a design that shows a catalog section (a restaurant menu, a properties/rooms grid, a product listing) as a client's choice and apply it to a different, empty site in the same workspace. Open the target site and confirm the catalog section shows the same items — with the same highlighted/featured picks and order — that the original design showed. Apply it a second time and confirm nothing duplicates. **Watch for:** If the target site already has its own items for that catalog, those are kept and the design uses them (it does not overwrite or duplicate). Highlighted items and their order should carry across. Images should appear immediately (they are referenced, not re-uploaded). Applying the design never fails just because content couldn't be brought over — the design still lands.
Generated sites can now feature a real ambient video in the hero — a slow cinematic pan, drifting clouds, ocean waves — sourced automatically from free stock footage, even without a connected video account. The clip is stored on our own CDN so published sites never depend on a third-party host. **Where:** Automatic during site generation. When the design calls for motion, the AI plans a single hero/atmosphere video slot; the platform fills it with a matching ambient clip (or falls back to a strong hero image when motion doesn't fit). **How to test:** 1. Generate a new site for a business where motion suits the brand (a cafe, a spa, a travel or real-estate site). 2. Open the design — the hero may show a muted, auto-playing, looping background video with a still poster image that displays until the clip loads. 3. Publish the site and confirm the hero video plays on the live site and the video URL points at our own storage (not pexels.com / pixabay.com). 4. If a video-capable creative account is connected, that account is still used first — stock video is only the free fallback. **Watch for:** A hero video that hotlinks a stock CDN instead of our storage; a stock photo landing in a slot that was meant to be video (or vice-versa); a 4K clip that makes the page heavy (clips are capped at 1080p); a missing poster image before the video loads; or a video slot appearing on sites where motion doesn't suit the design.
Searching your sites now matches each site on its own name instead of its folder's name, so a search for one brand stops pulling in every other site filed alongside it. **Where:** Dashboard → Builds / Designs / Chats tabs → the "Search sites" box **How to test:** Search for the name of a site that sits alongside other, differently-named sites. Only sites whose own name matches (plus smart matches on their content) should appear. Clear the search and confirm the full list returns. **Watch for:** A site you expected to find going missing — especially one still named "Untitled Site" or "New Site". Those are found by their content rather than their name, so they should still surface when you search the business name.
Organization owners can now permanently delete an organization from its settings page, with clear guardrails so it can never strand your account or destroy paid work. **Where:** Dashboard → Organization Settings → "Delete Organization" (owners only) **How to test:** 1. As the owner of a free-plan organization that has no active sites, open Organization Settings. 2. The "Delete Organization" card shows your plan and active-site count. Click Delete, type DELETE to confirm, and confirm. 3. You are switched to another organization and returned to the dashboard; the deleted org no longer appears in the switcher. 4. Try the same on an org that is on a paid plan, still has active sites, or is your only organization — the button is disabled with an inline note explaining exactly what to fix. **Watch for:** The button must stay disabled (and the note accurate) whenever the org is on a paid plan, has one or more active sites, or is the account's only organization. After deleting, the org must vanish everywhere it was listed, and you must never be left without a selected organization.
Hovering a design card on your dashboard now cycles through that site's design options again, and design thumbnails have returned to the gallery and to boards. **Where:** Dashboard → Designs tab (hover any card with more than one design) **How to test:** Open the Designs tab and hover a card for a site with two or more designs. The thumbnail should cycle every ~0.9s with dot indicators at the bottom. Leaving the card returns it to its resting image. The card's "N designs" pill should match the number of frames it cycles through. **Watch for:** Cards that stay on a single static image, thumbnails that render blank or white, hover cycling that snaps to a different design on the first frame, or a design count that doesn't match the number of frames shown. Sites generated before today may still show a single image until their previews finish regenerating.
You can now download a design board's screenshots and PDF in mobile (phone) view, not just desktop — so clients see exactly how each option looks on a phone. **Where:** A client's board → Export button → pick Desktop or Mobile, then Download screenshots (ZIP) / Download PDF. **How to test:** Open a board with a few pinned designs. Click Export, switch the device toggle to Mobile, and choose "Capture mobile screenshots" (takes a few seconds per design). Once done, export again in Mobile mode — the ZIP images and PDF pages render in phone proportions. Switch back to Desktop and confirm those exports are unchanged. **Watch for:** Mobile export only includes designs that have a mobile capture; any without one are skipped with a note. Mobile never falls back to the desktop image.
Design boards are now visible right from your dashboard instead of being tucked inside a client's menu. **Where:** Your dashboard — the user menu (top right) now has a "Design boards" entry, and any client card with saved boards shows a "Boards (N)" chip you can click straight through. **How to test:** 1. Open your dashboard. 2. If a client already has one or more boards, its card (or list row) shows a "Boards (N)" chip — click it to jump into that client's boards. 3. Open the user menu (top right) and click "Design boards" to see every board across all your clients, grouped by client, with thumbnails and shared / picked badges. Click any board to open it. **Watch for:** The overview always reflects the organization currently selected in the dashboard; switching organizations updates the list. Clients with no boards simply don't show a chip.
Correcting a design board is now effortless — the pin menu shows exactly which boards a design is already on, and you can move designs between boards or delete a whole board when it's no longer needed. **Where:** The pin (📌) button on any design in the gallery or shared preview; a client's Design boards page and any board's detail view. **How to test:** 1. Open a site's gallery, click the pin button on a design. The menu now shows every board with a checkmark on the ones this design is already on. Click a checked board to remove it; click an unchecked one to add it — the design can live on several boards at once. 2. After adding, the success toast has an "Undo" — click it to remove the pin you just made. 3. On a board, open a design's "Move to…" menu (folder icon) and pick another board. The design moves over with its label and presenter notes. If the target already has that design, it's simply removed from the current board. 4. On a board, open the "…" menu in the header and choose "Delete board". Confirm — it warns if the board is shared or has a recorded client choice — and you're returned to the boards list. A shared link to a deleted board stops working. **Watch for:** Checkmarks that don't match reality (a board that should be checked but isn't), an "Undo" that doesn't remove the pin, a move that drops the label/notes, or a deleted board still opening from its old share link.
Fixed a bug where a hero video slot could end up showing a broken video player instead of falling back to the poster image, and improved how the best stock video clip is chosen for a hero. **Where:** Automatic during site generation, for sites where the design includes a hero or atmosphere background video. **How to test:** 1. Generate a site for a motion-forward business (a video production studio, creative agency, or cinematic travel/hospitality brand). 2. Confirm the hero shows either a real playing background video or a clean static poster image — never a broken/empty video player. 3. Try a niche concept where stock footage has no close match; confirm it degrades gracefully to a poster image rather than a broken player. **Watch for:** A broken or blank video player in the hero, or a video that ignores the ideal clip length in favor of a longer/higher-resolution clip that doesn't loop as well.
The AI planning chat could occasionally show a raw, garbled reply instead of a normal message when the response had a small extra formatting glitch at the end. That case is now handled cleanly. **Where:** Site-planning chat (blueprint chat), any conversation turn. **How to test:** Have an extended back-and-forth in the planning chat across many turns; replies should always render as normal formatted text, never as raw unformatted text with stray characters at the end. **Watch for:** Any reply that still shows raw brackets/braces or looks unformatted — that's this same class of bug resurfacing.
Typing feedback on a shared design presentation could get interrupted mid-sentence — characters like +, -, and n were being caught by the presentation's zoom/navigation shortcuts instead of landing in the text box. Typing in the name or comment field now always works as expected. **Where:** Shared board link → Present mode → client feedback form **How to test:** Open a shared, presentable board as a viewer, start Present mode, and type a comment containing "+", "-", or the letter "n" — the characters should appear in the field instead of zooming the screenshot or toggling notes. **Watch for:** any remaining keyboard shortcut firing while a text field inside the presentation overlay has focus.
Fixed several issues that could cause the ambient hero video feature to silently fall back to a static image, or fail, on some sites — and motion-forward businesses now get it by default. **Where:** Automatic during site generation, same as the earlier cinematic hero video feature — most noticeable for video production, creative agency, and other motion-forward or atmosphere-led businesses. **How to test:** 1. Generate a site for a motion-forward business (a video production studio, creative agency, or cinematic travel/hospitality brand). 2. Confirm the hero shows a muted, auto-playing, looping background video with a poster image visible before it loads. 3. Publish the site and confirm the video still plays on the live version. **Watch for:** No hero video appearing on a clearly motion-forward site, or a design failing to save because a planned video slot never resolved.
Design screenshots that failed to capture under load (or on a site with many designs) used to get stuck missing permanently, since a single slow capture could time out the whole request before anything was saved. Capturing now retries transient timeouts and picks up where it left off across repeat visits, so previews fill in instead of staying blank. **Where:** Dashboard and gallery — design preview thumbnails **How to test:** Open a site with several design variations that haven't been screenshotted yet, and revisit the dashboard/gallery a couple of times — previews should progressively fill in rather than staying blank forever. **Watch for:** a design whose code doesn't compile — that one will correctly keep failing, since it's a real data problem, not a timeout.
You can now move one or many sites from one organization to another, right from your dashboard — with bulk multi-select. **Where:** Dashboard → hover any site card (or list row) and tick its checkbox. A "N sites selected" bar appears at the bottom → **Move to organization…** → pick the destination → **Move**. **How to test:** 1. Open the dashboard on an organization where you are an admin or owner. 2. Select one or more sites using the checkboxes (works in both grid and list view, on the Builds, Designs, and Chats tabs). 3. Click **Move to organization…**, choose another organization you also administer, and confirm. 4. Switch to the destination organization — the moved sites appear there with all their content, contacts, and settings intact. **Watch for:** - The destination picker only lists organizations you administer; you must be an admin or owner of both the source and the destination. - Everything tied to a site (its pages, images, forms, contacts, analytics connections) moves with it. Published sites keep their live URL. - If the destination organization would go over its plan's site allowance, you'll get a heads-up after the move.
Fixed a handful of bugs found while hardening the new organization delete and move-sites features: the Delete button could stay grayed out forever, a slow double-click on "Create site" could create two identical sites (and trigger AI generation twice), a deleted organization's name could never be reused, and splitting a client's sites into a new client could silently drop that client's logo. **Where:** Dashboard → Organization settings; Dashboard → "+ New Site" **How to test:** 1. Open Organization settings as an owner — the Delete button should become clickable normally (not stay disabled). 2. Click "+ New Site" rapidly twice in a row — only one site and one client should be created. 3. Delete an organization, then create a new one with the exact same name — it should succeed. **Watch for:** any org delete/move action returning a 500 instead of a clear reason; a split-off client missing its logo.
You can now add any design to a design board straight from the single-design editor — no need to switch to the gallery first. **Where:** Open a site in the editor (Focus Mode). Hover any design chip (D1, D2…) in the top toolbar, or use the pin button next to the design switcher for the design you're currently viewing. **How to test:** 1. Open a site that has more than one design. 2. Hover a design chip you are NOT currently viewing — its preview card now shows a pin on the right. Click it and choose one or more boards (or create a new one). 3. Click the pin button beside the design switcher to add the design you're currently viewing. 4. Open the client's Design boards to confirm the design landed on the board(s) you picked. **Watch for:** The board picker should stay open while you tick boards — moving your mouse onto it must not dismiss the hover card. Pins are always tied to the exact design you pinned, even after designs are reordered or deleted.
Your site editor's AI assistant can now collect designs onto a client's design board for you — just say "pin this design to a board" and it adds the design you're viewing, or "pin this to the Client Presentation board" to file it under a named board (it creates the board if it doesn't exist yet). You can also ask "what boards does this client have?" and it lists them with design counts and whether each is shared or decided. **Where:** Site editor → AI assistant chat (the assistant bar / rail). **How to test:** - Open a build's editor, ask the assistant "pin this design to a board named Client Presentation", then confirm the design appears on that board via the dashboard (client card menu → Design boards). - Ask "how many designs have I collected for this client?" / "list my design boards" and check the reply lists boards with counts, shared, and decided status. - Ask to pin the same design again and confirm it says the design is already on the board (friendly no-op, not a duplicate). **Watch for:** No board IDs or "variation" jargon in the assistant's replies; the pin should be attributed to you (not the org owner); pinning defaults to the design currently being viewed when you don't name one.
Fixed cases where dashboard search missed unnamed sites or cut off results too early, and where a design that already had a build was still shown as needing one. **Where:** Dashboard → Builds / Designs / Chats tabs → the "Search sites" box, and the Designs tab's Pending/Used split. **How to test:** - Search for a site still named "Untitled Site" or "New Site" using the name actually shown on its card (which may be its client's name) — it should now surface. - Run a broad search likely to match many sites and confirm results aren't capped too early. - Find a design that already has a live build and confirm it appears under "Used", not "Pending". **Watch for:** A design with an existing build still showing as "Pending" (which invites creating a duplicate build), or a site you expect to find missing from search results.
Presentation mode for design boards now lets you zoom into a design's screenshot, preview the live design at four device sizes, and export cleaner PDFs. **Where:** A shared board's presentation view (open a board and click "Present", or open a share link with presentation mode). PDF export from the board page. **How to test:** 1. Open a board and start Present. On a design's snapshot, scroll (or use the on-screen +/− buttons) to zoom in, drag to pan, and double-click or the fit button to reset. Arrow keys still move between designs; Esc first exits zoom, then closes the deck. 2. Switch a design to the live view and try the Desktop / Laptop / Tablet / Mobile buttons — the live preview re-renders at that width, scaled to fit the screen. 3. Export the board as a PDF and open it — there is no floating "Ask AI" bubble baked into the pages. **Watch for:** Zoom should never fight the keyboard (arrows move slides, not the image); the four device sizes should match what you see in the site editor; the exported PDF should contain only the board content.
Sites you create through the public API or a connected AI assistant (Claude, ChatGPT, etc.) now each get their own client — one client per site, exactly like the "+ New Site" button in the dashboard. Previously every API/assistant-created site was filed under whichever client was oldest in your account, so they all piled into a single client and the newest ones could go missing from listings. **Where:** Dashboard → your client list (each API/assistant-created site now shows as its own client), and any AI assistant connected to your account. **How to test:** Connect an assistant (or use your API key), create two sites, then list your sites — both appear, each under its own client named after the site. Listing sites now shows every site in your account, not just one client's. **Watch for:** Listing an assistant's/API's sites is now scoped to your whole account (organization), not a single client — new sites are always visible. Design boards now need a specific site or client to be named (there's no longer an implicit "default client"). Sites created before this change stay where they are; to consolidate the earlier ones, use the site-move (transfer) feature to move them to the right client yourself.
Background videos on generated sites now load faster, always play, and fall back to a tasteful ambient loop instead of a blank player when no perfect clip is found. **Where:** Any generated site that uses a hero or atmosphere background video. **How to test:** 1. Generate a site for a motion-forward business (e.g. a creative agency, cinematic hospitality brand) so the design plans a video hero. 2. Confirm the hero plays a real, smooth background video. 3. Regenerate or try a niche concept where stock has no match — confirm the hero still shows a moving ambient background (or a clean poster image) rather than an empty/broken player. **Watch for:** A hero video that fails to play, a play button sitting over a still that does nothing, or a "Placeholder Video" title — report these. Background videos should either play or degrade gracefully to a poster image.
Sites created through the public API or connected AI assistants now run the same conversion strategist as chat-built sites: an explicit goal drives the narrative, section flow, CTA rhythm, and coordinated copy — and the planner can design the full page architecture instead of defaulting to a single page. Callers can also state the site's conversion objective directly (e.g. "free trial signups from agencies"). **Where:** Sites created via the API / AI assistant integrations (create_site), visible in the generated design's copy and section flow. **How to test:** Create a site via the API with a section list but thin content and a `goal`. The generated homepage should show a coherent conversion arc (hero promise → proof → objection handling → action), CTAs matched to the stated goal, and no repeated angles across sections. Omit `pages` and the plan should include a full page map behind the navigation. **Watch for:** Chat-built sites regressing (their hero copy must NOT drift to generic phrasing — the planner must not overwrite chat-authored content), and API callers who pass a detailed section list still seeing their sections honored in order.