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.
Add a terminal-style animated glyph background to any section, and a decode-on-reveal effect that resolves a heading out of random characters. **Where:** Editor - select a section, open Background - "Character field" (Drift or Reveal mode); or right-click a heading, "Add animation" - Text - "Scramble / Decode". **How to test:** Select a hero or any section, pick Character field, toggle Drift/Reveal, adjust density/churn/speed/intensity, and Apply - the canvas paints behind your content and follows your brand color. For Scramble, right-click a heading, choose Scramble / Decode, and confirm the letters decode into the real word. **Watch for:** Content hidden behind the field (should never happen - the canvas sits behind text); the effect running on touch or reduced-motion devices (it should show a single static frame / final text instead of animating); a heading that stays scrambled after the animation finishes.
Applying a style Tweak, background pattern, animation or hover effect in the editor now records its own entry in Version History, so Undo reverts exactly that change instead of an unrelated earlier one. **Where:** Site editor → apply a Tweak / Background / Animation, then use the Undo button in the activity feed. **How to test:** Apply a background pattern to a section, click Undo, hard-reload the page — the pattern should be gone. **Watch for:** Undo reporting success while the change is still visible after reload.
Referencing one of your own past designs while planning a new site used to show a plain text pill ("V1" / "V2") with no way to search or preview. It's now a searchable screenshot grid with a large live preview pane — arrow keys to flip between designs, a poster image while the preview loads, and a clear "Use this design" button. **Where:** New-site planning chat → "+" → "Reference another design". **How to test:** Open the design-reference picker, search for a past site by name, arrow through a few results, and confirm the preview updates correctly before selecting one. **Watch for:** The picker is scoped to your own designs and copy is intentionally honest that it matches look & feel, not exact graphics — it doesn't promise pixel-identical output.
Picking a section type in the editor no longer fires an AI request instantly — it opens a quick review step so you can shape the request first. **Where:** Site editor → left rail → "+ Add section" → pick a type (e.g. Gallery) **How to test:** Click "+ Add section", choose Gallery. Confirm a review panel opens with an editable description, layout thumbnails (with an "Any layout" default), and a placement selector (Before the footer / Top / End). Nothing generates until you press "Add section". "Back" returns to the list; "Describe your own…" still opens the free-text chat. **Watch for:** A click on a type sending a message immediately (regression), or the review panel firing on open.
Writing a blog post, menu item, or product whose title matches one you already have now just works — the new item quietly gets a numbered web address (e.g. `-2`) instead of failing. **Where:** Dashboard assistant ("write a blog post…"), the "New item" button in any collection, and CSV import. **How to test:** With an item already titled "Test Post QA", ask the assistant to write another post titled "Test Post QA" and click Confirm. A new draft is created instead of an "already exists" error. **Watch for:** The original item keeps its address; the new one gets the next free suffix. Manually typed web addresses that collide are still flagged so you don't overwrite a page by accident.
When you selected an element on the page and then asked to add a new section (e.g. "add a blog section"), the new section could get placed *inside* the selected section — most often the hero — which broke the responsive layout on mobile and desktop. New sections now always land as a proper top-level block on the page, positioned near where you were pointing. **Where:** Site editor → select any element → ask the assistant to add a new section. **How to test:** Open a generated site, click/select the hero (or any section), then request "add a blog section" (or FAQ, gallery, etc.). Confirm the new section renders full-width as its own block in the page — not squeezed inside the hero — and that the page still looks correct at mobile width. **Watch for:** A new section appearing clipped/overlapping inside the hero, horizontal scrollbars at narrow widths, or the new section not rendering at all.
The site assistant can now add items to existing collections: "write a blog post about spring wedding trends" or "add a Margherita pizza to the menu" creates the row (as a draft by default) instead of dead-ending with an explanation. Published items appear on the site automatically. **Where:** Site dashboard (portal) assistant chat **How to test:** On a site with a blog collection, ask the assistant to "write a short blog post about X". It should preview/confirm, create the post as a draft, and tell you it's a draft you can publish. Check the post appears in the Blog collection table. Asking to add to a collection that doesn't exist should refuse and list the collections that do exist — never silently create one. **Watch for:** Items landing published without the user asking; the assistant putting content into the wrong fields for the collection's schema; the tool being used for inline content (services/testimonials) where add_content_item is correct.
When you ask the assistant to write a blog post or add a collection item, it now saves the item as a draft for you to review instead of publishing it live unless you explicitly ask to publish. **Where:** Site dashboard assistant chat → "write a blog post…" / "add a…" to any collection. **How to test:** Ask the assistant to "Write a short blog post titled X about Y" and confirm the Add Item card. The new post should be saved as a draft (hidden from the live site); it should only go live if your request explicitly said to publish or go live. **Watch for:** New items being created as "published" for a plain write/add request — they should be drafts unless you asked to publish.
If you asked the assistant to add an item to a collection you'd mis-named (e.g. "recipes" when your site actually has "Blog Posts"), it would quietly offer to create a brand-new, redundant collection instead of pointing out the one you probably meant. It now names your existing collections first and checks whether one of those is the right home for the item before ever proposing a new one. **Where:** Dashboard assistant chat — asking to add an item to a collection. **How to test:** With a "Blog Posts" collection already on the site, ask the assistant to "add a recipe to the recipes collection." It should mention "Blog Posts" and ask if that's what you meant, rather than jumping straight to creating a new collection. **Watch for:** If you genuinely have no collections yet, the assistant still offers to create one — this only changes behavior when at least one collection already exists.
When the AI assistant adds a blog post or other collection item, the confirmation card now clearly states whether the item will be saved as a draft or published live immediately — so nothing goes on your site without you seeing it first. **Where:** Dashboard assistant chat → "Add Collection Item" confirmation card **How to test:** Ask the assistant to "write a blog post titled X". Before confirming, the card shows the item title and either "saved as a draft" or a "will be PUBLISHED immediately" warning. **Watch for:** A publishing item should always show the live-publish warning; a normal add should read as a draft.
When you ask the assistant to "write a blog post" on a site that already has a Blog Posts collection, it now always adds the post as a draft item instead of occasionally re-running a "set up the collection" step that already existed and quietly did nothing while still saying "Done". **Where:** Site dashboard assistant chat → "Write a short blog post titled …". **How to test:** On a site with an existing Blog Posts collection, ask the assistant to write a post with no mention of publishing. It should create a draft item you can review; it should never reply "Done — created collection" without a new post actually appearing in the Content list. **Watch for:** A "Done" reply where no new draft row appears in the collection, or a new post going live without you asking to publish.
Setting up a new collection (like a blog) could non-deterministically end up with only the listing page or only the individual post/item page, but never both — a save-timing bug let the second write silently erase the first. Both pages now reliably persist together. **Where:** Adding a Blog/collection page from the Pages tab or via the assistant. **How to test:** Create a new "Blog" collection page and confirm both the `/blog` listing page and an example `/blog/[slug]` detail page exist and render afterward. **Watch for:** Any collection setup where the listing page loads but individual items 404, or vice versa.
Managing repeatable content (blog posts, menu items, listings) no longer hides two levels deep behind a "Functions" label. Sites with collections now show them directly in the dashboard's left menu (e.g. "Blog Posts" right under Site), blogs get a proper schema (title, excerpt, body, cover image, author, date) instead of a bare title+description form, and the interface explains how drafts and publishing work. **Where:** Site dashboard (portal) left rail; Content Library; dashboard Home card; command palette (Ctrl/Cmd-K → "blog"); Add Collection modal → "Blog posts" preset **How to test:** On a non-commerce site with a blog collection: (1) the left rail shows a "Blog Posts" entry after Site — clicking it opens the posts table directly; (2) with no runtime features the hub rail item reads "Content", not "Functions", and lands on the Content tab; (3) dashboard Home shows a "Your content library" card with an item count and a Manage button; (4) Ctrl/Cmd-K, type "posts" → "Content Library" appears; (5) Add Collection modal offers a "Blog posts" preset; creating it yields fields title/excerpt/body/cover image/author/date; (6) the empty collection state shows the one-line drafts-and-publishing explainer and the button reads "New Blog Post". **Watch for:** Rail overflow on small heights with 2 promoted collections; commerce sites must be unchanged (Products stays the promoted entry, no extra collection items); sites with zero collections must keep the historical 8-item rail byte-for-byte.
Generated sites with a blog now get a real Blog listing page, so the "Blog" nav link and "Read the Blog" button open a proper articles hub instead of silently re-loading the homepage. **Where:** Any newly generated site whose plan includes a blog. **How to test:** Generate a blog-intent site (e.g. "a consultant's site with a blog"), then open Pages — a "Blog" page is listed — and click the site's Blog nav link. **Watch for:** The Blog page should render even for a brand-new, empty blog (a friendly empty state), and the nav link must resolve to it rather than the homepage.
Starting a logo or creative generation in Brand Studio and then switching to another tab used to risk losing track of that generation's progress. It now persists in the background, so switching away and coming back shows the current status or finished result instead of a reset state. **Where:** Dashboard → Brand Studio → Create tab **How to test:** Start a generation, switch to another tab or section of the app, then return to Brand Studio — the generation should still be running or show its completed result. **Watch for:** A generation that was in progress before a full page refresh should still pick back up correctly.
Assistant suggestions about site issues now speak plain language ("Connect your Quote Request form") instead of technical labels ("Form not connected: quote_request", "Missing popup: Opens MobileMenu"), and two false alarms were removed entirely: mobile menus and other UI toggles are no longer reported as missing popups, and forms wired up through a popup in another part of the site are no longer reported as disconnected. Anything that can't be phrased in plain words is hidden rather than shown. **Where:** Site editor (portal) → Assistant panel suggestion chips, and the site health / launch checklist recommendations **How to test:** Open a site whose header uses a mobile menu toggle and whose quote form is connected via a popup button — the assistant panel should show no "Missing popup" or "Form not connected" chips. On a site with a genuinely dead button (href="#"), a chip like "Make the \"Get a Quote\" button work" should appear. **Watch for:** Real disconnected forms must still be flagged (now worded "Connect your … form"); genuinely missing popups (a modal setter with no modal anywhere) should still appear as "Fix the … popup".
Cash-on-delivery orders now complete even when the store's live address isn't in the payment redirect allowlist. **Where:** Storefront checkout on a COD-only store — /checkout, "Place order". **How to test:** On a COD-enabled store with no online payment gateway, add a product, go to checkout, fill in contact and shipping details, and click Place order. The order should confirm and redirect to the order-confirmation page. **Watch for:** The buyer should never see "return_url is not an allowed origin for this site" on a COD order. Prepaid (online payment) checkout still validates the redirect origin as before.
When a generated site includes a managed collection (like a blog), its listing page is now guaranteed to exist — even if the AI page generation hits a limit — so navigation links to it never lead to a blank page. **Where:** Any generated site with a Blog or other collection (nav/footer links to `/blog`, `/products`, etc.) **How to test:** Generate a site with clear blog intent, let it finish, then open the Blog link in the nav. You should land on a real Blog listing page (showing an empty state until you add posts), not the homepage. **Watch for:** A listing route that silently re-renders the homepage, or a nav link that goes nowhere.
New collections created with the "Add Collection" preset (like Blog Posts) now correctly display their published items on the collection's listing page. **Where:** Your site's collection listing page (e.g. `/blog`) **How to test:** Add a collection, publish an item, then republish the site — the item now appears on the listing page, not just on its own detail page. **Watch for:** A listing page stuck on its "currently being compiled / no items" empty state even though items are published and their individual detail pages work.
Writing a blog post no longer happens in a tiny 5-line box: long-form fields get a tall auto-growing editor with a word count and a Write/Reading toggle that previews your paragraphs. The assistant also got smarter about collections — it now knows each collection's actual fields (wrong field names get a helpful correction listing the real ones), and it can update existing items ("change the price of the Margherita to 12") with safe matching that asks for clarification instead of guessing when titles are ambiguous. **Where:** Content Library item editor (any long-text field); site dashboard assistant chat **How to test:** (1) Open a blog post's Body field — the editor should be tall, grow as you type, show a word count, and the Reading toggle should show paragraph breaks. Short description fields stay compact. (2) Ask the assistant to "update the [item] in my [collection] and set [field] to X" — it should confirm, patch just that field, and leave others intact. Ask it to update an item whose title matches several rows — it should list them and ask which one instead of picking. **Watch for:** Formatting characters (** or #) showing on the live site if typed — the editor is intentionally plain text; autosave regressions in the item editor; the assistant updating the wrong row or wiping fields it wasn't asked to change.
Applying a design skill now asks where it should go — apply to the design you're viewing, or create it as a new variation for side-by-side comparison — and then actually does it (previously it dead-ended in a "I'll build this as a new variation" message that never applied anything). The "Apply a design skill" menu shows only skills (no more variations/pages/sites mixed in), and picking a skill gives immediate feedback: the composer placeholder announces what will be applied, color-token skills instantly preview on your site, and the send button explains it will apply the skill. The picker also renders correctly in light mode instead of a dark unreadable panel. **Where:** Site editor → Assistant panel → "+" menu → "Apply a design skill" (also the @ dropdown's Design Skills section) **How to test:** 1. Open a site in the editor with the light theme active. 2. Click "+" in the composer → "Apply a design skill" — the dropdown should be light-themed and list ONLY design skills. 3. Pick a color/visual skill — a chip appears, the placeholder says "<skill> will be applied — add details, or just send", and the site preview tints with the skill's palette. 4. Hit send with no text — a choice card appears: "Apply to this design" vs "Create as new variation". Pick "Apply to this design" — code changes should land on the current design. Repeat and pick "Create as new variation" — the fork flow should start (base picker, then generation). 5. Type "@" manually — the full dropdown (skills + variations + pages + assets + sites) still appears. **Watch for:** Dark mode regressions in the @ dropdown; skills failing to apply when combined with typed text; the variation suggestion still appearing when a skill chip is attached; the skills-only picker showing other sections after typing to filter.
Applying a bold design skill (like Neobrutalism) could produce headlines so large they broke words mid-line, overflowed on mobile, and footers whose columns wrapped into an orphan row. Every skill application now carries a responsive execution contract: display type must be fluid with a hard cap (fits at 360px, never breaks words), restyled grids/footers must keep their mobile collapse behavior, and the result is checked at mobile/tablet/desktop widths. The skill compiler also rejects unbounded size superlatives ("oversized") in new skills, and the Neobrutalism starter skill now pins a concrete fluid headline size. **Where:** Site editor → Assistant → "Apply a design skill" (both apply-to-this-design and create-as-new-variation) **How to test:** 1. Apply the Neobrutalism skill to a site with a long hero headline (e.g. "Architecting the Future of Global Finance") and pick "Create as new variation". 2. The generated hero headline should be dramatic but fit: no mid-word breaks on desktop, no horizontal clipping on the mobile preview. 3. Check the footer: link columns should stay balanced on desktop (no lone wrapped column) and stack cleanly on mobile. **Watch for:** Skills now rendering too timidly (cap too aggressive); the contract text leaking into user-visible chat responses; two stacked skills duplicating the contract block (expected, harmless).
Design Skills now lives under Settings, and you can create a skill from scratch or rewrite an existing one's direction — not just save one from a design. **Where:** Settings → Organization → **Design Skills** tab (the old top-nav "Design Skills" link now redirects here). **How to test:** 1. Go to Settings → Design Skills. 2. Click **New skill**, pick a type (Visual / Motion / Voice), describe the look in plain words (colors, fonts, mood, do's and don'ts), and save. It appears under "Your skills". 3. On one of your skills, click **Edit direction**, revise the description, and update. 4. Open a site, and in the design chat apply the skill to steer an edit toward that look. **Watch for:** A skill created from a vague description may come back with a heads-up note (e.g. mixed concerns were trimmed) — that's expected. Skills shape AI edits in the design chat, not your first draft.
Skills created by saving or duplicating a design had no authored notes, so opening "Edit direction" showed an empty box — easy to mistake for "nothing to edit." It now starts from the skill's current compiled direction so you're revising real text, with a note explaining where it came from. **Where:** Settings → Design Skills → open a skill → Edit direction. **How to test:** Save a skill directly from a design (no notes written), then open Edit direction — it should be pre-filled with the current direction, not blank. **Watch for:** The box still opening empty for a design-derived skill.
After quickly finalizing a design, some sites incorrectly sent you back to the design-choice screen instead of into your site's Mission Control dashboard, because the app was checking a signal that finalizing never actually set. **Where:** Opening a site right after using the fast "finalize" option during design selection. **How to test:** Fast-finalize a design and reopen the site — it should land in Mission Control, not bounce back to design selection. **Watch for:** Older sites finalized before this fix still use a legacy fallback check and should be unaffected.
A one-time repair fixed collection listing pages (like a Blog or Menu page) on a small number of existing sites that were built before a related fix landed — they were stuck showing no items even though the underlying posts or items already existed. **Where:** Any published site's Blog, Menu, or other collection listing page. **How to test:** - This was a one-time backend repair for already-affected sites, so there's no new UI to test. - If you previously saw an empty listing page despite having items in the Content Library, confirm it now shows those items. **Watch for:** A collection listing page (Blog, Menu, Properties, etc.) still showing an empty state despite the Content Library having published rows of that type.
Applying a template could occasionally leave headings unreadable — dark text sitting on a dark background — because the automatic contrast fixup missed some muted dark colors, and in rare cases it over-corrected softly-muted light text into solid black. Also fixed clicking a second template quickly cancelling the first adaptation still in progress. **Where:** Site editor → apply/adapt a template. **How to test:** Adapt a template with a dark section using muted dark text (e.g. slate-700 on navy) — text should be legible. Click two different templates in quick succession — the first should keep running to completion rather than getting silently cancelled. **Watch for:** Dark-on-dark text after adaptation; a template adaptation that never finishes because a later click cancelled it.
Adding a new section (especially a gallery) no longer duplicates the page footer or drops a pop-up over the page on load. **Where:** Site editor → "+ Add section" → add a Gallery or any section "before the footer" **How to test:** Add a section to a page and confirm the new section lands directly above the single existing footer — not after it, and with no second footer appearing in the Structure tree. Add a gallery and confirm it renders as a normal grid; clicking a thumbnail opens the image viewer, and the page is NOT covered by an overlay when it first loads. **Watch for:** Two "Footer" entries in the Structure tree, a new section sitting below the footer, or a gallery/lightbox that appears open on page load and blocks the page.
On sites that plan a blog, the AI-generated homepage no longer invents fake "latest posts" cards with made-up titles and dates. The homepage blog preview is now wired to your real blog collection and stays empty (with a tidy placeholder) until you publish your first post — so everything you see on the homepage is something you can actually edit or remove from Content Manager. **Where:** Any newly generated site that includes a Blog page or a blog/"latest insights" homepage section. **How to test:** Generate a site whose plan includes a blog. Confirm the homepage "from the blog" section either is omitted or shows a graceful empty state, and that no fabricated posts appear. Publish a post and confirm it flows into that section, each card linking to /blog/your-post-slug. **Watch for:** Any hardcoded post cards on the homepage, or preview cards linking to a bare /blog instead of a per-post URL — those would indicate the contract was ignored.
Two follow-up fixes to "add a section" from chat: when the selected block appears on more than one page, the new section could land on the wrong one; and if the page didn't have a spot to slot it in, the new section could silently disappear instead of showing up somewhere. **Where:** Site editor → select any element → ask the assistant to add a new section. **How to test:** On a page that shares a section with another page (e.g. a CTA block used on both Home and About), select it while viewing About and ask to add a new section — it should appear on About, not Home. Also try adding a section on a page with an unusual layout; it should still render somewhere rather than vanish. **Watch for:** A newly added section appearing on the wrong page, or not appearing at all.
When you paste a URL to redesign and the scrape succeeds, the intake no longer re-asks about your look, tone, location, or page structure — those come from the scan. The intake card also now waits for that scan to finish before appearing, so it doesn't ask questions the scan is about to answer; a safety timer lets it show anyway if the scan stalls for more than a few minutes. Separately, a card with many required questions could previously drop one to stay within the usual question limit — required questions are now always kept, even if it means a slightly longer card. **Where:** New-site chat (planning flow) → paste a site URL to redesign. **How to test:** Paste a real site URL to redesign; once the scan finishes, the intake card should skip questions the scan already answered (look, tone, location, layout). If the scan takes unusually long, the card should still appear after a few minutes rather than hang indefinitely. **Watch for:** Questions already answered by the scan still showing up; the intake card stuck waiting forever on a failed scan; a required question missing from the card.
The "reference a design" question in the new-site intake card could fall back to a plain text list of outside brands (Apple, Stripe, Linear…) whenever the visual picker came up short — asking you to recall and type a brand name instead of just picking a screenshot. That text fallback is gone: the picker now always falls back to featured/recent gallery templates (on-industry first) so you always get something to click, and if nothing usable is found the question is skipped entirely rather than shown as text. A few other intake questions were also tightened so they don't get silently dropped or repeat ones you already answered. **Where:** Creating a new site → intake preference card, "Reference a design" and general question set. **How to test:** Start a new site with a sparse pitch (a few words) and confirm the reference-design question always shows clickable screenshots, never a text list of brand names to type. **Watch for:** Very niche industries with almost no gallery templates — the question should be omitted cleanly rather than showing an empty picker.
Previously a site whose plan included a Blog page almost never got an actual manageable blog collection (17 blog-intent sites existed; only 1 had one) — the dashboard had nothing to promote and the "blog you manage from your dashboard" promise went unkept. Generation now detects a blog page/section in the plan and stands up the blog collection (with its listing page and navigation) automatically, empty and ready to write. **Where:** Site generation; then the site dashboard left rail ("Blog Posts") and Content Library **How to test:** Generate a site whose plan includes a Blog page (e.g. "a consultant site with a blog"). After generation completes, the dashboard rail should show "Blog Posts", opening an empty posts table with the full schema (title, excerpt, body, cover image, author, date). Re-running generation must not duplicate the collection. A site with no blog in its plan must get nothing. **Watch for:** Blog collections appearing on sites without blog intent (over-triggering from unrelated sections); starter junk posts being seeded (there should be zero); duplicate Blog listing pages after regeneration.
The "pick a design you like" step now ranks style options that fit your industry first, with clearer per-style descriptions. "Decide for me" now works even on the style picker, where free-text answers aren't valid — you can still hand the choice to AI. **Where:** New-site chat (planning flow) → the "Pick a design you like" question. **How to test:** Start a new site in a clear industry (e.g. a restaurant) and reach the design question — on-industry styles should appear first. "Decide for me" should be present and work. **Watch for:** Off-industry styles ranked first, or "Decide for me" missing from the style picker.
Clicking a template in the gallery or on the public templates page now opens the real, interactive live preview first instead of a recorded scroll-through clip. The clip is still there — one toggle away — for templates that have one. **Where:** Admin → Gallery, and the public Templates page — click any template card. **How to test:** Open a template with a recorded clip; it should open on the live preview with a Preview/Video toggle. Open one without a clip; it should just show the live preview. **Watch for:** The toggle not appearing when a clip exists, or the live preview failing to load.
After picking a design and starting the full site build, you used to be stuck watching a progress screen for the whole build (which can take several minutes for a store with cart/checkout) with no way forward. As soon as the build starts, you're now taken straight into the editor, where a status banner tracks the build's progress in the background. **Where:** New-site flow → after choosing a design → "Build my site". **How to test:** Pick a design and start the build. You should land in the site editor almost immediately, with a build-in-progress banner, instead of waiting on the progress modal until the build finishes. **Watch for:** The editor loading before the build has actually started; the progress banner not updating or not clearing when the build finishes.
Fixed a bug where the checkout page could show "Your cart is empty" even though the header mini-cart displayed the item and the cart was saved. **Where:** Published storefronts — the /checkout page. **How to test:** Add a product to the cart on a published store, then open /checkout. The item, totals, tax, shipping and discount fields should appear. **Watch for:** The checkout summary matching the header mini-cart on first load, with no need to refresh.
Fixed the washed-out "Completed intake form" pill (and file-attachment chips) so they're readable in the chat, and the mobile plan sheet now opens as a simple list by default with a toggle to the visual wireframe. **Where:** New-site chat (planning flow) → chat transcript; on mobile, tap the "Plan ready" pill to open the plan sheet. **How to test:** Submit the intake form and confirm the "Completed intake form" pill and any attached PDF/image chips are dark-on-light and legible. On a narrow screen, open the plan sheet — it should show the list view first, with a List/Wireframe toggle in the header. **Watch for:** Any low-contrast (light-on-light) text on the pill or chips; the mobile toggle failing to switch views or losing drag-to-reorder.
When you ask the design chat for a site feature like a blog or booking ("add a blog page so I can post articles"), it now confirms your site supports it, explains when the page gets added, and offers a one-click pill to add a preview section to the current page — instead of only saying the request belongs on your dashboard. **Where:** Client editor design chat (and build editor chat) — ask for a feature page like "add a blog page I can manage myself" **How to test:** On a design-phase site, type "add a blog page so I can write articles" in the design chat. The reply should confirm blogs are supported, mention the page gets added after you pick a design, and show an "Add a blog section to this page" pill. Clicking the pill should add a blog section to the current page. A pure page-management request like "delete the About page" should still get the plain redirect with no pill. **Watch for:** The pill failing to send when clicked; feature affirmations appearing on non-feature requests (rename/delete page); awkward grammar in the reply for multi-word features (e.g. "online store").
When the planner asks which design you like, it now shows real screenshot previews of matching styles — labelled with a plain-language name and a quick descriptor — and ranks styles that fit your industry first. **Where:** New-site chat (planning flow) → the "Pick a design you like" question. **How to test:** Start a new site in a clear industry (e.g. a restaurant) and reach the design question. Options should render as screenshot tiles with a readable label and a short hint (e.g. "Light · Editorial · Airy layout"), with on-industry styles surfaced first. "Decide for me" stays available; the free-text "Other…" option is gone (it never made sense here). **Watch for:** Broken/missing preview images, options labelled with raw slugs (e.g. "Cinematic Ai Tech"), or the "Decide for me" pill disappearing.
Generated ecommerce pages (like Cart) could render their header/footer without actually importing them, crashing the page with a "Header is not defined" error. Also fixed FAQ sections incorrectly being treated as empty when using the standard content format. **Where:** Published ecommerce/catalog storefronts — Cart and product listing pages, and FAQ sections. **How to test:** Publish an ecommerce store and open the cart and product listing pages; they should render normally with header/footer intact. Check a page with an FAQ section renders its questions. **Watch for:** A blank or crashed cart/listing page, or an FAQ section rendering with no questions.
Customer accounts (password login, registration, and password reset) on published stores could fail because the browser's cross-origin security check couldn't identify which store the request belonged to, and portal sessions weren't set up to survive across your custom domain. **Where:** Any published store with customer accounts enabled — login, sign up, and password reset. **How to test:** On a published store with a custom domain, register a customer account, log out, then log back in. Try "forgot password" too. **Watch for:** Login/signup/reset failing silently or with a generic network error.
Opening a collection page (like Products) directly, right while its catalog was still being set up, could leave the item table permanently stuck with no fields — because it only looked at the schema available at the moment it first loaded. **Where:** Client portal → site editor → Pages → a catalog collection (e.g. Products). **How to test:** Open a catalog collection page during/shortly after a new site's catalog is being built; the table should pick up its fields once the schema is ready instead of staying empty. **Watch for:** A collection table showing no columns or an unusable item editor.
The planner's inline question card could silently drop a required question (like business name or location) when there were more mandatory questions than fit in one card, and a stuck site-analysis or slow reply could leave the chat waiting indefinitely. Required questions are now always included, a stalled analysis times out and lets you continue, and retrying a slow reply no longer risks a duplicate message. **Where:** New-site chat (planning flow) — the inline intake card, and pasting a URL to redesign. **How to test:** - Start a new site with a pitch likely to trigger several required questions (business name, location, structure) — all of them should appear in the card, even beyond the usual cap of three. - Paste a site URL to redesign; if analysis takes unusually long, the intake card/plan should still become available after a few minutes rather than hanging forever. - If a chat reply is slow and retries, you should get exactly one reply — never a duplicate. **Watch for:** an intake card missing an expected required question; a redesign flow stuck on "analyzing your site"; a duplicated assistant reply after a retry.
The planner now asks its quick questions inline in the chat conversation (a few at a time) instead of hiding them in a side panel — so it's obvious what to answer next, and your answers are collected as a tidy recap in the "Answers" tab. **Where:** New-site chat (planning flow). **How to test:** Start a new site and describe your business. The preference questions appear as a compact card in the chat on both desktop and mobile, capped at about three at a time. Answer them, then open the "Answers" tab to see the recap and an "Edit answers" option. The "Preview Plan" button stays clickable the whole time (it just softens to an outline with a hint while questions are still open). **Watch for:** The Preview Plan / Generate button ever becoming disabled while questions are pending (it must never be); the questions card not scrolling to its first question; duplicate cards appearing in both the chat and the Answers tab.
Single-SKU products (those created without size/color variants) can now be added to cart and purchased — previously checkout stalled on "Calculating total…" and showed a "variant_key required" error, blocking the sale. **Where:** Any published store's product page → Add to Cart → Checkout, for a product that has no variants. **How to test:** Open a product with no variants, add it to the cart, go to checkout, fill in contact + shipping details, and place the order. The summary (subtotal, discount, shipping, tax, total) should calculate and the order should go through. **Watch for:** Products that DO have variants should still require a variant selection; out-of-stock variants should still block checkout.
If one page on your site had a syntax problem (for example, a generated product-category listing), publishing the entire storefront was blocked. Publish now automatically attempts to repair just the broken page(s) and re-checks them before giving up — so the rest of your site isn't held hostage by one page. **Where:** Client portal → site editor → Publish. **How to test:** Publish a site with one intentionally broken page; publish should attempt an automatic repair and succeed if the repair works, only failing (with the same error as before) if the page truly can't be fixed. **Watch for:** Publish taking noticeably longer, or a genuinely broken page still incorrectly getting published.
Starting a new site by pasting a URL to redesign now always shows a clickable next step, and it survives a page refresh. **Where:** New Site → planning chat → first message like "Redesign https://example.com (a …)" **How to test:** Create a fresh site, send a redesign-from-URL as the first message, wait for the reply. You should see the "Is this your site?" confirm card (or an intake form), never just text with nothing to click. Reload the page — the card is still there. **Watch for:** A first-turn assistant reply that shows instructional text but no card or buttons, or a card that disappears after refresh.
When you redesign an existing site, the planner now mirrors that site's actual sections and page structure instead of dropping in a generic template — and it waits for the analysis to finish before drafting the plan, so the plan is grounded in real content. **Where:** New-site chat (planning flow) → paste a site URL and choose to redesign it. **How to test:** Paste a real site URL and pick the redesign path. The plan should recognizably follow the source's section order and page structure, and the planner should hold off until the site analysis has landed rather than proposing a plan immediately. The intake questions should skip things the analysis already captured (style, location, structure). **Watch for:** A generic vertical template replacing the source's layout; the plan drafting before analysis completes; re-asking for details the scrape already established. On a thin/single-page-app site that can't be read well, it should ask for structure rather than inventing sections.
Adapting a gallery template to your content is now more reliable and no longer blocks the editor. **Where:** Design view → Template Gallery → "Generate Adapted Preview" **How to test:** 1. Open a site's Design view and adapt a template from the gallery. 2. Confirm you get a small "Adapting…" progress chip near the top and can keep editing other designs while it runs. 3. When it finishes, the new design (e.g. D3) appears and its preview shows that design — not a previous one — without needing a refresh. 4. Check the adapted design's hero and feature sections render real images, and that no section has dark text sitting on a dark background. **Watch for:** a newly adapted design briefly showing another variation's layout; empty/black image areas where a photo should be; low-contrast headings/labels on dark sections; the adaptation trapping you behind a full-screen "Almost there…" wait.
On stores that don't sell in dollars, the product page showed the right currency but the cart, totals and checkout buttons still showed a dollar sign — same number, wrong symbol. Every money value on the storefront now uses your store currency. **Where:** Your live store — product page, cart drawer, floating cart badge, discount line, and the Pay Now / Place Order buttons. Course listings too. **How to test:** Set your store currency to something other than USD (Settings → Payments), open your published store, add a product to the cart and open the cart drawer. The symbol next to every amount should match the one on the product page. **Watch for:** Any remaining dollar sign next to a non-USD amount, especially on discount badges and the checkout button label.
The buyer-facing cart now displays configured tax (e.g. GST) and shipping as their own lines, so the total shown matches what's charged at the payment gateway. **Where:** Your published store → cart (`/cart`) and the slide-out cart drawer **How to test:** Configure a tax rate and shipping rate on your store, add a product to the cart, and open the cart. The summary should list Subtotal, Shipping, Tax, and a Total that adds them up — instead of only subtotal minus discount. **Watch for:** Carts with legacy (non-catalog) products keep the simple subtotal-only summary; shipping shows "Calculated at checkout" until a delivery address is entered on the checkout page.
Importing items from a CSV now lets you decide up front whether they arrive as drafts or go live on your site right away — the same choice the Shopify import already offered. **Where:** Site editor → Content → your collection (e.g. Products) → Import items → CSV **How to test:** Upload a CSV, map your columns, then set "Imported items land as" to "Published (live immediately)" and import. The new items should appear on your storefront listing page (e.g. All Products) after publishing. Repeat with "Draft (review first)" and confirm they stay hidden until you publish them from the items list. **Watch for:** Items imported as drafts are intentionally hidden from the live site — the dialog now says so. If published items still don't appear on a listing page, check that they show a green "Published" badge in the items table.
Fixed a contact record bug where chat conversations from a shared widget could show up under the wrong site, cart buyers with no form submission or booking were missing from the Contacts list, and opening the Product feeds card no longer silently creates and enables a public feed — enabling feeds is now an explicit action. **Where:** Client portal → Contacts, and Client portal → Settings → Product feeds **How to test:** - Open a contact's detail view and confirm only conversations tied to this site's widgets appear - Complete a checkout with no prior form/booking and confirm the buyer shows up under Contacts - Open Settings → Product feeds on a site that has never enabled feeds and confirm it shows "not configured" instead of an active feed URL, until you explicitly enable it **Watch for:** Contacts list missing buyers, feed URLs appearing enabled without an explicit opt-in, or a contact showing another site's chat history.
Deleting a design from the variations gallery could remove a neighbouring design instead, leaving the one you deleted still on screen. **Where:** Site builder → Design variations gallery → delete a design card **How to test:** On a site with several designs (especially one where a generation was interrupted at some point), delete a design and confirm that exact design disappears and the others are untouched. Refresh to confirm it stayed deleted. **Watch for:** A different design vanishing, the deleted design reappearing after refresh, or the design counter disagreeing with the number of cards shown.
A small number of older designs were saved in a broken form and showed "preview can't be displayed" instead of the design. Opening one of these now automatically rebuilds it from the saved data, so the design appears normally. **Where:** Site editor → design switcher → select the affected design **How to test:** Open a design that previously showed a preview error. It should load and render every section. Switch away and back — the repair is saved, so it stays fixed. **Watch for:** Sections rendering empty, a design that still shows the preview error after a reload, or a switch that hangs on "Repairing saved design...".
Publishing could fail with "pages could not be prepared for publishing" when a site's starting navigation or footer data was blank — it was overwriting your saved edits (like a custom header button label) with nothing. Your saved content now always wins over a blank starting value. **Where:** Site editor → Publish **How to test:** - Open a site whose header button (navigation CTA) has custom text - Publish the site - Confirm publish succeeds and the header button still shows your custom text on the live site **Watch for:** "N pages could not be prepared for publishing" errors, or a header/footer button reverting to blank or default text after publishing.
New sites wire the header button to the navigation CTA you can edit, instead of baking in a fixed label that ignored your changes. **Where:** Site editor → Pages → header section, and the navigation settings where the CTA label lives. **How to test:** Generate a new site, open the navigation settings, change the call-to-action text, and reload the preview — the header button should show your new wording. **Watch for:** Older sites generated before this change may still show a fixed header button; regenerate the header or edit it directly to pick up the new wiring.
When you ask the design assistant to create a new variation, the chat now shows a live "working" indicator for the whole build instead of a one-off message that looked like nothing was happening. **Where:** Site editor → Design surface → chat assistant (any "create a new variation" prompt or suggested-action chip) **How to test:** Open a design with variations, type a change that the assistant offers to build as a new variation (or click a suggested "Create variation" chip), and confirm a spinner/progress line stays visible at the bottom of the chat until the new variation is ready. **Watch for:** The indicator should appear immediately on confirm and clear exactly when the variation finishes generating — not before.
Buyers and leads are now one record, and store owners get a prioritized "what needs doing" list the moment they open Home. **Where:** Site editor → Home (for stores) and Customers / Leads → Inbox (any site) **How to test:** 1. Open a contact from either the Customers view or Leads → Inbox → Contacts. You now see one card with the person's lifetime value, order history, form submissions, chat conversations, notes, and activity — no matter which list you opened it from. A badge marks them as a Customer or a Lead. 2. On a store site's Home, an "Action needed" panel sits at the top listing concrete jobs: unfulfilled paid orders, cash-on-delivery payments to collect, return requests to review, and unread messages — each with a count and a one-click link to the right screen. When there's nothing to do, it shows a calm "all caught up" line. 3. If a publish fails, the top of Home says so plainly with the reason and a "Try again" button — never a silent "Draft". **Watch for:** the order/COD/returns counts should match the Orders screen; clicking a row should land on the matching filtered tab; non-store sites' Home should look unchanged except for the clearer failed-publish message.
Every merchant price field now shows the currency symbol and a live "= ₹4,999.00 on your storefront" preview as you type, so it's obvious whether you're entering ₹4,999 or a much larger amount. **Where:** Product editor price, variant grid (bulk-apply + column), discount codes, shipping rates, and Cash-on-Delivery limits. **How to test:** Open a product in your store, edit the Price — as you type 4999 you'll see "= ₹4,999.00". Type 499900 and the preview immediately reads "= ₹4,99,900.00", making an accidental extra-zeros entry easy to catch. **Watch for:** The number you enter is always in whole currency units (rupees/dollars), never paise/cents — the preview confirms the amount.
Shipping rates now have proper form fields for the common cases — no more hand-typing JSON. **Where:** Site editor → Settings → Shipping → open a zone → Add / edit a rate **How to test:** - Flat rate: set Price to 0 and "Order subtotal at least" to 2000 to offer free shipping over 2,000. - Price bands: pick "Price bands (by order total)" and add rows like "0 to 50 → charge 5", "50 to blank → charge 0". - Weight bands: pick "Weight bands (by cart weight)" and enter gram ranges with a charge each. - Power users can still click "Advanced: edit JSON" to edit the raw conditions object. **Watch for:** the simple form and the Advanced JSON view should describe the same rate — toggling between them must not lose your bands or thresholds.
Currency settings showed the wrong base currency for stores priced outside US dollars, and gave you no way to correct it. The base currency now reflects your actual store currency, and you can change it yourself. **Where:** Site editor → Settings → Currency **How to test:** Open a store priced in rupees (or euros, dirhams, pounds). The base currency should read INR rather than USD. Change it with the dropdown, confirm the warning, and check that the storefront, quotes and checkout all follow. **Watch for:** Changing the base currency relabels existing prices instead of converting them — 1,499 stays 1,499. Re-check your product prices after switching. Cached exchange rates are refetched against the new base, so give the rates table a moment to repopulate.
If your site has a store, the left menu is now built around running your shop: Orders, Products, and Customers are right there instead of buried inside other tabs, and Orders shows a badge for anything still waiting to be fulfilled. **Where:** Open any store site in Mission Control — the left rail now leads with Orders, Products, and Customers. Everything else (Leads inbox, other features) is a click away under "More." **How to test:** Open a store site, click Orders (see the unfulfilled badge), Products (your catalog), and Customers (your buyer list). Then open Settings — all store setup now lives in one "Store" section: Payments (incl. cash on delivery), Shipping & Returns, Tax/GST, Currency, Discounts, Fulfillment, and Product Feeds, with a setup-progress checklist at the top. **Watch for:** Non-store sites are unchanged. Old links to any of these screens still work.
Gallery template cards were showing only a static image — the hover scroll-through preview never started. Hovering a template card now glides through the full page design as intended. **Where:** Templates gallery (/templates), the template picker in the site builder, and template suggestion cards **How to test:** Open /templates, hover any template card — the preview should scroll slowly down the page design and ease back when you move the mouse away **Watch for:** Cards staying frozen on hover; previews that jump instead of gliding; scrolling continuing after the mouse leaves
When you tap an image on the canvas and ask the voice assistant to change it, it now acts on that exact image instead of asking you to describe it. **Where:** Site editor → Design view → voice mode (microphone button) **How to test:** Start voice mode, tap an image in the editor canvas, then say "replace this image". The assistant should change the image you tapped without asking which one you mean. Try it with a non-hero image and with several images selected at once. **Watch for:** The assistant asking "which image?" after you've already tapped one, or the change landing on the hero image instead of the one you selected. Selection resets after each change, so re-tap before the next request.
On the Mission Control screen (where you manage pages rather than edit the canvas), voice mode no longer asks you to "tap" an element that can't be tapped there. It now asks you to describe the image or element you mean and acts on that. **Where:** Site editor → Mission Control (Home / Pages) → voice mode (microphone button) **How to test:** From Mission Control, start voice mode and say "replace the hero image". The assistant should ask you to describe which image (or accept your description) and make the change — it should never tell you to tap or select an element, because there is nothing to tap on that screen. The canvas Design view is unaffected: tapping still targets the exact element. **Watch for:** The assistant asking you to "tap" or "select" an element while on Mission Control, or looping without ever making the change.
Clicking "Add page" and continuing through the page planner used to silently do nothing if you were in the full-canvas editor. It now opens the Page Planner correctly no matter where you started from. **Where:** Site editor → Pages → Add page **How to test:** From the full-page (non-Mission-Control) editor view, click "Add page", fill in the page purpose, and click Continue. The Page Planner should open and let you finish creating the page. **Watch for:** "Add page" quietly closing with no new page and no error message.
Rescheduling a booking with "Override availability" now updates the card to the correct new time range immediately, instead of pairing the new start time with a stale old end time until you reload. **Where:** Mission Control → Bookings tab → pencil "Edit date/time" on a booking → check "Override availability" → set a new time → Save changes. **How to test:** On a site with no availability rules configured, edit a pending booking (e.g. 11:15 AM – 11:45 AM), enable "Override availability", change the start to 3:30 PM, and save without reloading. The card should immediately read "3:30 PM – 4:00 PM" (the 30-minute duration is preserved). **Watch for:** A card showing an end time earlier than the start (e.g. "3:30 PM – 11:45 AM"), or the range only correcting itself after a manual page reload.
The "Service Requested" dropdown on booking/appointment pages was showing up empty and required, which meant customers couldn't submit a booking at all. It now automatically fills in from the services you've already added to your site. **Where:** Public site → Booking/appointment page → "Service Requested" field **How to test:** Open a published or previewed booking page for a site that has services listed under Services. The "Service Requested" dropdown should list those services, and submitting the booking form should work. **Watch for:** A booking page where "Service Requested" is still empty even though the site has services configured.
Clicking "Request Review" on a completed booking now shows a clear message when Google review requests aren't set up yet, instead of silently doing nothing. **Where:** Mission Control > Features > Manage bookings > Bookings tab, on a completed booking card. **How to test:** On a site with no Google review automation configured, mark a booking complete and click "Request Review" — you should see a message prompting you to set up Google review requests in Automation settings. With review requests configured, clicking it shows a confirmation that the request was sent. **Watch for:** No feedback at all after clicking, or an error that mentions internal terms instead of pointing you to Automation settings.
The template gallery can now be filtered by look — mood, light or dark, dominant color, typography, whitespace, and motion — and every template shows its Design DNA plus a row of similar looks. **Where:** Templates gallery (`/templates`) and the "Browse all templates" picker inside the site builder chat. There's also a new "Start from a design" button on the first-time builder screen. **How to test:** 1. Open `/templates`. Above the grid, use the new "Look & feel" filters (style chips, Light/Dark, color swatches, typography, whitespace, motion) and confirm the grid narrows. 2. Click a template card's "View details" to open its detail view. Confirm the "This design's DNA" panel shows a color palette, font pairing, style keywords, and feel, and that a "More with this look" row appears when there are similar designs. Click a similar thumbnail — it swaps the selection. 3. In the site builder chat empty state, click "Start from a design" — the template gallery opens with the same look filters. Confirm the preview pane shows the DNA panel and similar-looks row. **Watch for:** Templates that haven't been analyzed yet must still appear when no look filter is active, and look-filter options that no template matches should be hidden — the whole filter bar should disappear if nothing has been analyzed. The DNA panel and similar-looks row should quietly hide (not error) when there's no data.
Saving a site's chat widget configuration for the first time no longer fails with a "Failed to create widget" error. **Where:** Site editor > Leads > Automation > Settings > Widget Setup **How to test:** Open Widget Setup for a site that has never had a chat widget, adjust any values, and click Save Changes. The widget config should save and the Deploy tab should generate embed code. **Watch for:** A red error banner on save, or the settings not persisting after a page reload.
Fixed a data-loss bug where a new product/content item could silently drop its Description (or split its fields across a duplicate row) if you added an image or made another edit within a second of typing. **Where:** Site editor → Features → Content → open any collection → New item (Content tab) **How to test:** Create a new item, type a Description, then immediately paste an image URL + Enter (or star an image) before the "Edits autosave." indicator settles. Reload the page and reopen the list — the item should appear once, with both the description and the image intact. **Watch for:** Duplicate rows for the same item, an item whose Description column shows "—" after reload, or fields landing on different copies of the same item.
Double-clicking an existing item's title in a content collection now reliably opens the full item editor again, so you can get back to images, variants, size guide, SEO, and settings after closing it once. **Where:** Mission Control > Features > Content > any collection (Products, Menu Items, Team, etc.) **How to test:** Open a collection with saved items, double-click an item's title — the full editor drawer should open (single-click still starts an inline rename). **Watch for:** A double-click that only selects text in the rename box instead of opening the editor.
Adding a new page that includes a payment button no longer strips it out — the button now shows up and works as expected instead of silently vanishing or crashing the page. **Where:** Site editor → Pages → Add page (any page with a payment/checkout button) **How to test:** Add a new payment-collection page to a site. Open it and confirm the payment button renders and is clickable, instead of a "block not available" message or a blank/crashed page. **Watch for:** Any newly added page whose payment or other platform-provided button is missing or replaced with a placeholder.
When you add a page that collects a payment (for example "pay your outstanding balance"), the Pay Now button now starts a real checkout through your configured payment provider instead of opening a generic contact form — and the page no longer makes security or compliance claims it can't back up. **Where:** Site editor → page switcher → Add page → describe a page where customers pay. **How to test:** Add a "pay your balance" style page, generate it, then open the new page and click the Pay / Checkout button — it should start a payment link to your configured provider (Settings → Payments), not open an appointment/contact form. **Watch for:** A "Pay Now" button that opens a lead form instead of checkout, or fabricated badges like "256-Bit SSL Encryption" / "HIPAA Compliant Processing" appearing when no such guarantee exists.
On AI-generated payment pages, the main "Pay Your Balance" button sometimes linked to the appointment-booking page instead of the on-page payment section — so visitors got sent away from the only place they could actually pay. The generator now points the payment CTA at the on-page pay button, and a save-time safeguard corrects any that still slip through. **Where:** Any generated payment-collection page (e.g. a "pay your balance / pay your invoice" page). **How to test:** Generate a site with a payment/pay-balance page, open it, and click the hero "Pay" button — it should scroll down to the payment button on the same page, not navigate to the booking/contact page. **Watch for:** A separate, clearly-labelled "Book an appointment" link may still point at the booking page — only the payment CTA is redirected to the on-page pay section.
On sites that reuse a single shared hero component across pages, an AI-generated payment page's "Pay Now" hero button could still link to the appointment-booking page instead of scrolling to the on-page payment section — because the shared hero ignored the per-page link override the page tried to pass it. Generated hero components now read that override, so the payment CTA goes where it should. **Where:** Any generated payment-collection page (e.g. a "pay your balance / pay your invoice" page) whose hero is a shared component. **How to test:** Generate a site with a payment/pay-balance page, open it, and click the hero "Pay" button — it should scroll down to the on-page payment button, not navigate to the booking/contact page. **Watch for:** The homepage's hero button is unchanged — it still points at its normal booking/contact link; only pages that explicitly pass a different CTA destination are affected.
Saving a payment provider as active now automatically deactivates any other active provider, matching what the Settings panel already promised. **Where:** Site editor → Settings → Payments **How to test:** Configure and save Stripe (it becomes Active), then configure and save PayPal. Only PayPal should show the "Active" badge now; Stripe flips to "Configured". Reload to confirm exactly one provider is Active. **Watch for:** Two "Active" badges after saving a second provider, or a provider you just deactivated silently reactivating.
Rescheduling an appointment now keeps its original length instead of collapsing it to a zero-minute slot. **Where:** Site editor → Bookings → Edit date/time **How to test:** Take a booking that runs, say, 9:00–9:30. Edit its date/time — including with "Override availability" turned on for sites that have no availability rules yet — move it to a new time, and save. The rescheduled booking should still be 30 minutes long (e.g. 10:00–10:30), not 10:00–10:00. **Watch for:** A rescheduled booking whose start and end times are identical, or duration-aware views showing the appointment as zero-length.
Sites with online scheduling or booking requests now show a "Manage bookings" button that opens the appointments dashboard, so you can view, confirm, complete, cancel, or reschedule the bookings customers make. **Where:** Mission Control → Features. On an active "Online Scheduling" or "Booking Requests" feature, click "Manage bookings" (booking-request forms show it inside the Forms & Lead Capture picker). **How to test:** Activate a booking feature on a site, open Features, click "Manage bookings", and confirm the bookings list loads with view/confirm/complete/cancel/reschedule actions. **Watch for:** The action should appear alongside (not replace) "Manage Items" / "Edit form"; the bookings dashboard lives under the Bookings tab.
Your store can now feed its products straight into Instagram & Facebook Shopping and Google Shopping — kept up to date automatically — plus export a Shopify-ready catalog file. **Where:** Site editor → Growth → Marketing → Strategy (the "Product feeds" card appears for stores with products) **How to test:** 1. Open a site that has products and go to Growth → Marketing → Strategy. 2. In the "Product feeds" card, copy your feed link. Optionally set a brand name and a Google product category, then Save. 3. Paste the link into Meta Commerce Manager (Data sources → Add products → Scheduled feed) or Google Merchant Center (Products → Feeds → Add feed → Scheduled fetch). 4. Click "Download Shopify CSV" to get a Shopify-format export of the catalog. 5. Use "New link" to rotate the feed link if it was ever shared by mistake. **Watch for:** The feed only lists published products from a published site. Products on sale should show both the original and sale price. Product variants (size/colour) each appear as their own item grouped under the parent product.
Clicking Add to Cart on a published product detail page showed "Product is missing an id — cannot add to cart" and the cart stayed empty, blocking the whole buyer flow. Product pages now carry the identity of the product they were built from, so items add to the cart correctly. **Where:** Your published storefront — any product detail page, plus the same page in the editor preview. **How to test:** Publish a site that has products, open a product page, choose any options, and click Add to Cart. The cart count should increase and the item should appear in the cart and carry through to checkout. **Watch for:** Existing published sites need to be republished once to pick this up — the product page is built at publish time. If a product page still shows the error, republish the site and reload.
Every commerce block on a published site — cart drawer, mini-cart, checkout, funnel checkout/upsell, pay and subscribe buttons, booking deposits and digital-product buy buttons — now displays prices in the store's own currency instead of always defaulting to US dollars. **Where:** Any published storefront using cart/checkout/payment components on a non-USD store (INR, EUR, GBP, etc.). **How to test:** Publish a site whose currency is not USD, add a product to the cart, and open the cart/checkout — prices should render with the correct currency symbol. **Watch for:** A price showing "$" (or no symbol at all) on a non-USD store, or two different currencies inside the same checkout summary box.
Returning customers who are signed in to a store no longer have to retype their details at checkout — their name, email, and phone are filled in automatically, and the shipping address defaults to the one from their most recent order. **Where:** The checkout page of any published store with customer accounts enabled. **How to test:** Sign in to a published store as a customer who has ordered before, add an item to the cart, and open checkout. The contact step shows a "Welcome back" note with your details filled in; the shipping step defaults to your last order's address. Every field stays fully editable, and guests (not signed in) see the usual empty form. **Watch for:** Published sites need a republish to pick up the new checkout behavior. Anything the customer starts typing must never be overwritten when the prefill lands. Guests and stores without customer accounts should be unchanged.
Running Fix All in the Responsive Check panel now shows one consistent progress count, and fix status messages no longer hide behind the top toolbar. **Where:** Site editor → design view → Responsive Check panel → Fix All **How to test:** Open a site with responsive issues spanning more than one section file, click Fix All, and watch the header/progress bar. The counter now reads a single running "X of total" (e.g. 3 of 17) instead of one number in the message and a different one in the bar. Any "Fixed" / "Could not fix" toast appears just below the toolbar rather than overlapping the design tabs. **Watch for:** Progress counts that restart per section, or a status toast clipped by the top toolbar.
When a page can't be prepared during publishing, you now see a short, plain-language message naming the affected page instead of a raw technical error. **Where:** Mission Control → the "publish attempt failed" banner, and the retry dialog. **How to test:** Trigger a publish that fails on a page; confirm the banner and the retry dialog show a readable message (e.g. "1 page could not be prepared for publishing: /contact") with a Try Again action — not a stack trace or internal component name. **Watch for:** Any raw error text, stack traces, or internal names still leaking into the banner or dialog.
The design-variation tabs at the top of the editor now let you delete a design directly from the hover card, alongside the existing pin option. **Where:** Site editor - Design view - hover any design tab (D1, D2, ...) **How to test:** Hover a non-original design tab. The hover card shows both the pin ("Add to board") and a trash icon. Click the trash icon, confirm, and the design is removed. **Watch for:** The original/base design must not offer a delete option; deleting asks for confirmation before removing.
The hover card on the design tabs (D1, D2, …) no longer disappears while you are reaching for the pin or delete buttons — it now stays open as long as your pointer is on it and only closes once you move away. **Where:** Site editor - Design view - hover any design tab **How to test:** Hover a design tab, pause to read the caption, then move down to click the pin ("Add to board") or the trash icon. The card should remain visible the whole time and only dismiss after you leave it. **Watch for:** An abandoned card (pointer moved off without the card noticing) must still auto-dismiss so it never lingers over the canvas.
Some sites showed "The Faq section couldn't be displayed here" instead of the actual FAQ content — that's now fixed. **Where:** Any published or previewed site with a FAQ / Help Center section. **How to test:** - Open a site whose homepage includes a FAQ section. - Confirm the FAQ content (questions, search box, category filters) renders normally instead of an error placeholder. **Watch for:** FAQ sections that previously failed to render should now show their questions and answers; search and category filtering within the section should still work.
Fixed a bug where a FAQ section could show a blank/broken area instead of your questions and answers. **Where:** Any published or previewed site with a FAQ / Help section that includes a search box or category filter. **How to test:** Open a site whose FAQ section has a search bar, view it in the design preview and after publishing — the questions render and the search box works instead of the section disappearing. **Watch for:** FAQ sections that appear empty, or a preview error mentioning a help/search component.
FAQ and Help Center sections now reliably show their questions even when the site's content was stored under a differently-named field than the section expected. **Where:** Site Editor → any page with an FAQ / Help Center section **How to test:** Open a site whose FAQ section previously appeared blank (or reload/refine one). The questions and answers now display instead of an empty or errored section. **Watch for:** A truly content-free FAQ (a site that genuinely never had questions written) will still show an empty state by design — regenerate or refine that section to populate it.
Newly generated multi-page sites no longer ship menu links that lead to a "page not found" error. **Where:** Site header/navigation on generated sites (e.g. Shop, About, Contact menu items) **How to test:** Generate a new multi-page site and click each menu item — every link now lands on a real page instead of a 404. **Watch for:** A menu that used to show links to pages the builder never created (Shop, About, Contact) — those broken links are now removed so the menu only shows pages that actually exist.