@aglyn/aglyn 1.0.0-beta.199 → 1.0.0-beta.200

package/src/lib/app-utils/docs-index.generated.js

@@ -1500,7 +1500,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Reusable components',
         heading: 'Manage',
         anchor: '#manage',
-        text: 'From the site\'s Components page you can rename, edit the description, open the besigner, or delete a reusable component. The component\'s ID is persisted inside every screen that places it and never changes.\nYou can also give a component its own icon, from the same picker the besigner uses for icon elements — either in the Edit component dialog on the Components page, or on the component\'s detail page. Every instance is then marked with it: in the hierarchy, on the canvas badge, and in the element drawer under Your components. A page assembled from promoted sections becomes readable at a glance. Components without an icon keep the generic package glyph.\nFilters in the Components table\'s toolbar narrows the list by name, Used in (page or email), ID, description, or date, and Search matches any word of the name, ID, or description. Each filter in force shows as a chip above the table. The list pages as you go, so the first filter or search reads 100 components and matches over them, and paging past the last match reads further. See Filter and search a list.'
+        text: 'From the site\'s Components page you can rename, edit the description, open the besigner, or delete a reusable component. The component\'s ID is persisted inside every screen that places it and never changes.\nYou can also give a component its own icon, from the same picker the besigner uses for icon elements — either in the Edit component dialog on the Components page, or on the component\'s detail page. Every instance is then marked with it: in the hierarchy, on the canvas badge, and in the element drawer under Your components. A page assembled from promoted sections becomes readable at a glance. Components without an icon keep the generic package glyph.\nFilters in the Components table\'s toolbar narrows the list by name (a word of it, or the whole name), Used in (page or email), ID, or the date it was last updated, and Search finds a component by the start of any word of its name. Every filter and the search word are part of the list\'s query, so they look through every component on the site, not only the page on screen. Each filter in force shows as a chip above the table. A combination that cannot be asked at once — a name "contains" filter beside a search, or a second date range — is left out, and the table says which one and why. See Filter and search a list.'
     },
     {
         path: '/building-sites/besigner/reusable-components',
@@ -2263,7 +2263,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Layouts',
         heading: 'Find a layout',
         anchor: '#find-a-layout',
-        text: 'The site\'s Layouts page lists every layout. Filters in the table\'s toolbar narrows it by display name, ID, description, or the date it was created or last updated, and Search matches any word of the name, ID, or description. Each filter in force shows as a chip above the table; remove a chip to drop it. The list pages as you go, so the first filter or search reads 100 layouts and matches over them, and paging past the last match reads further; the table says so while more remain. See Filter and search a list.'
+        text: 'The site\'s Layouts page lists every layout. Filters in the table\'s toolbar narrows it by display name (a word of it, or the whole name), ID, or the date it was last updated, and Search finds a layout by the start of any word of its name. Every filter and the search word are part of the list\'s query, so they look through every layout on the site, not only the page on screen, and the pager turns through the matches. Each filter in force shows as a chip above the table; remove a chip to drop it. Some combinations cannot be asked at once — a name "contains" filter beside a search, or a second date range — and the table says which filter it left out and why rather than applying it to part of the list. See Filter and search a list.'
     },
     {
         path: '/building-sites/screens-and-layouts/layouts',
@@ -2774,7 +2774,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Build a blog',
         heading: '2. Write entries',
         anchor: '#2-write-entries',
-        text: 'Add rich blog entries with images, a live preview, and scheduling so posts publish at the right time.\nNew entry, or clicking any row in the entries table, opens that entry on its own page. The page has its own address, so you can bookmark an entry you\'re mid-way through or paste the link to a colleague and they land on the same one. Back to entries — or your browser\'s Back button — returns to the list; if the entry has edits you haven\'t saved, you\'re asked before they\'re dropped.\nThe table opens with the most recently Published entries first. A scheduled entry sorts by the date it\'s due to go out, so the next posts in your queue open the list, and when you reverse the column they come last among the dated entries. Click the Title, Status, Updated or Published header to sort by that column, and again to reverse it. Entries with nothing in the sorted column, such as a draft with no published date, follow the rest in either direction rather than dropping out. Filters in the table\'s toolbar narrows the list to one Status or one Category across the whole collection, not only the page you\'re on, and the filter in force shows as a chip above the table. One filter applies at a time, so a new one replaces the last, and the entries table has no search box. See Filter and search a list.\nEach entry carries, besides the title, excerpt, cover image, and markdown body:\n- Category — a single bucket (e.g. Guides) used for filtering and related posts, picked from the collection\'s category list (see below), never typed free-form.\n- Tags — comma-separated labels (e.g. nextjs, seo).\n- Author — the entry\'s byline: an author record from the Authors tab or a one-off custom byline. An entry needs one to be published or scheduled; a draft can be saved without it. See Authors.\n- SEO title / SEO d'
+        text: 'Add rich blog entries with images, a live preview, and scheduling so posts publish at the right time.\nNew entry, or clicking any row in the entries table, opens that entry on its own page. The page has its own address, so you can bookmark an entry you\'re mid-way through or paste the link to a colleague and they land on the same one. Back to entries — or your browser\'s Back button — returns to the list; if the entry has edits you haven\'t saved, you\'re asked before they\'re dropped.\nThe table opens with the most recently Published entries first. A scheduled entry sorts by the date it\'s due to go out, so the next posts in your queue open the list, and when you reverse the column they come last among the dated entries. Click the Title, Status, Updated or Published header to sort by that column, and again to reverse it. Entries with nothing in the sorted column, such as a draft with no published date, follow the rest in either direction rather than dropping out. Filters in the table\'s toolbar narrows the list by Title (a word of it), Status, Category, Author, or the Published or Updated date, and Search finds an entry by the start of any word of its title. Every filter and the search word are part of the list\'s query, so they look through the whole collection, not only the page you\'re on, and each filter in force shows as a chip above the table. While the list is filtered or searched it sorts by Published or Updated, and a date filter sorts by the date it filters; a note above the table says when the order moved. A combination that cannot be asked at once — a Title filter beside a search, or two date ranges — is left out, and the table says which one and why. See Filter and search a list.\nEach entry carries, besides the title, excerpt, cover image, and markdown body:\n- Catego'
     },
     {
         path: '/building-sites/site-templates/build-a-blog',
@@ -2858,7 +2858,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Save & share a template',
         heading: 'Start from a template',
         anchor: '#start-from-a-template',
-        text: 'Open the starter template gallery and install a template. It lands in your templates library as one page template per page — publishing nothing until you choose which pages you want. Aglyn\'s own starter templates still create their pages straight away, since you pick those when a site is empty.\nWhere to find it\nTemplates sits next to the create button on three lists, and each one offers templates of its own kind:\n| List | What the picker offers |\n| Screens | Page templates, plus Aglyn\'s starter sites and marketplace templates |\n| Layouts | Layout templates |\n| Components | Component templates |\nStarter sites and marketplace templates are whole-site page bundles, so they appear only on Screens — a layout or component picker would have nothing to do with them.\nUse the filter icon in the dialog\'s header to search by name, description or category.'
+        text: 'Open the starter template gallery and install a template. It lands in your templates library as one page template per page — publishing nothing until you choose which pages you want. Aglyn\'s own starter templates still create their pages straight away, since you pick those when a site is empty.\nWhere to find it\nTemplates sits next to the create button on three lists, and each one offers templates of its own kind:\n| List | What the picker offers |\n| Screens | Page templates, plus Aglyn\'s starter sites and marketplace templates |\n| Layouts | Layout templates |\n| Components | Component templates |\nStarter sites and marketplace templates are whole-site page bundles, so they appear only on Screens — a layout or component picker would have nothing to do with them.\nThe picker\'s search box finds a template, a starter or a marketplace listing by the start of any word of its name. Each shelf asks its own query, so the search looks through your whole library and the whole marketplace, not only the cards on screen, and your templates and the marketplace templates page through what matched.\nUse the filter icon in the dialog\'s header to search by name, description or category.'
     },
     {
         path: '/building-sites/site-templates/save-a-template',
@@ -2886,7 +2886,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Your templates library',
         heading: '',
         anchor: '',
-        text: 'Your templates library\nTemplates are saved starting points. A template is inert: nothing in your library is on your live site until you deliberately use it. That is the whole point of the library — it means installing something from the marketplace can never publish pages to a site you are running.\nFind it at Templates in a site\'s navigation, alongside Screens, Layouts and Components — the three things a template can produce.\nA template is a copy, not a live link: once you use one, the result is yours outright and editing the template never changes what you already made. If you want one edit to update every place a thing appears, you want a reusable component. If you want one frame around many pages, you want a layout.\nFilters in the library\'s toolbar narrows it by Kind (page, component, or layout), Source (marketplace, starter, or saved here), name, description, or date, and Search matches any word of the name, description or template ID. Filters look at every template the library read — its first 200 — not only the page on screen, and each one in force shows as a chip above the table. See Filter and search a list.'
+        text: 'Your templates library\nTemplates are saved starting points. A template is inert: nothing in your library is on your live site until you deliberately use it. That is the whole point of the library — it means installing something from the marketplace can never publish pages to a site you are running.\nFind it at Templates in a site\'s navigation, alongside Screens, Layouts and Components — the three things a template can produce.\nA template is a copy, not a live link: once you use one, the result is yours outright and editing the template never changes what you already made. If you want one edit to update every place a thing appears, you want a reusable component. If you want one frame around many pages, you want a layout.\nFilters in the library\'s toolbar narrows it by Kind (page, component, or layout), Source (marketplace, starter, or saved here), name (a word of it, or the whole name), or the date it was last updated, and Search finds a template by the start of any word of its name — a starter by its starter\'s name. Every filter and the search word are part of the library\'s query, so they look through every template on the site, and the library pages through the matches. Each filter in force shows as a chip above the table; a combination that cannot be asked at once is left out, and the table says which one and why. See Filter and search a list.'
     },
     {
         path: '/building-sites/site-templates/templates-library',
@@ -3117,7 +3117,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Product catalog',
         heading: 'Collections',
         anchor: '#collections',
-        text: 'Collections group products for landing pages and storefront blocks:\n- Manual collections are an ordered, hand-picked list.\n- Smart collections define rules — match by tag, category, price, name, or product type, with all or any semantics — and membership updates automatically as products change. Draft and archived products never appear.'
+        text: 'Collections group products for landing pages and storefront blocks:\n- Manual collections are an ordered, hand-picked list.\n- Smart collections define rules — match by tag, category, price, name, or product type, with all or any semantics — and membership updates automatically as products change. Draft and archived products never appear. A smart collection lists every product that matches, however large the catalog. Saving or deleting one updates which products it holds right away. On a big catalog that can take a few seconds after Collection saved appears.\nOn a Product grid scoped to a smart collection whose rules use any, is not, a name, or a price above, the grid\'s search box and its category and tag chips can\'t be combined with the collection. Using one shows a notice above the grid instead of narrowing it. The type, In stock and price controls still work.'
     },
     {
         path: '/commerce-and-bookings/commerce/catalog',
@@ -3152,28 +3152,28 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Commerce',
         heading: 'Products hub',
         anchor: '#products-hub',
-        text: 'The Products page is the catalog manager:\n- Products with up to 3 options and 100 variants each — per-variant SKU, barcode, price, compare-at (sale badge), weight, and stock. See Product catalog.\n- Categories & collections — a category tree plus manual and smart (rule-based) collections with a live match preview.\n- CSV import/export in the Shopify column dialect, with a dry-run report — switching from Shopify is a file upload.\n- Payments — Stripe Connect onboarding status and your plan\'s fee ladder.\nThe product list filters through its own toolbar. Search looks for the text in the field Search in names — Name, SKU (whole) or Barcode (whole) — and reaches the whole catalog, not only the rows on screen. Filters offers Status (Active, Draft, Archived); on its own it also reaches the whole catalog, and beside a search it narrows that search\'s matches. Each filter in force shows as a chip above the table; remove the chip to clear it. A search reads up to 500 matching products and uses the first word you type, matched on the start of a word. See Filter and search a list.'
+        text: 'The Products page is the catalog manager:\n- Products with up to 3 options and 100 variants each — per-variant SKU, barcode, price, compare-at (sale badge), weight, and stock. See Product catalog.\n- Categories & collections — a category tree plus manual and smart (rule-based) collections with a live match preview.\n- CSV import/export in the Shopify column dialect, with a dry-run report — switching from Shopify is a file upload.\n- Payments — Stripe Connect onboarding status and your plan\'s fee ladder.\nThe product list filters through its own toolbar, and every filter and the search reach the whole catalog, not only the rows on screen. The list is in name order and pages through whatever matches.\n- Search matches the start of a word in a product\'s name, using the first word you type.\n- Filters offers Product (the name contains a word, is, or starts with), Status (Active, Draft, Archived), Type (Physical, Digital, Service), Slug, SKU and Barcode. A SKU or barcode is matched whole, the way you copy or scan it; is any of takes several, separated by commas.\nFilters combine. The one exception: the search, a Product contains filter, and a SKU or Barcode filter each look a word or code up in a list, and only one of those lookups can apply at a time. The list says which one it set aside, above the table, rather than applying it to some products and not others. Each filter in force shows as a chip above the table; remove the chip to clear it. See Filter and search a list.\nExport writes every product the filters and search match, in the same order — up to 10,000 in one file. With nothing filtered, that is the whole catalog except deleted products.'
     },
     {
         path: '/commerce-and-bookings/commerce/overview',
         title: 'Commerce',
         heading: 'Inventory',
         anchor: '#inventory',
-        text: '- Per-variant stock; blank = untracked, 0 = sold out.\n- Oversell policy per product: stop selling or allow backorders.\n- Low-stock alerts notify managers once per threshold crossing.\n- Adjustment history with reason codes (sale, restock, correction…).\n- Locations split stock across warehouses/storefronts (plan-capped); adjustments and POS sales bucket per location.\n- Reserved in checkout holds units for a shopper who has reached the payment page, so the last one cannot be sold twice.\nReserved stock {#reserved-stock}\nWhen a shopper reaches the payment page, the units in their basket are reserved — the next shopper is offered what is left, not the same unit. It is what stops two people paying for the last one.\nYour stock count does not move when a unit is reserved. A reservation is a promise, not a sale, and the count means what is on the shelf. The products list names the difference instead: 3 (1 reserved) is three units on the shelf with one of them spoken for, so two are available to buy right now.\nA reservation is released when the shopper pays (the count moves then), when they abandon the checkout, or after 31 minutes, whichever comes first. A checkout page left open expires on its own, so nothing stays reserved by someone who walked away.\nTwo cases reserve nothing, deliberately: a variant with no stock tracking has no number to reserve against, and a product set to allow backorders is one you have told us to keep selling past zero.\nSales at the register are not affected — the till never refuses a sale, because the shelf in front of the cashier is the truth.\nStock movements {#stock-movements}\nInventory → Stock movements is the history behind every tracked count — the answer to "the shelf says four and the console says six, what happened?"\nFive things write to it and '
+        text: '- Per-variant stock; blank = untracked, 0 = sold out.\n- Oversell policy per product: stop selling or allow backorders.\n- Low-stock alerts notify managers once per threshold crossing.\n- Adjustment history with reason codes (sale, restock, correction…).\n- Locations split stock across warehouses/storefronts (plan-capped); adjustments and POS sales bucket per location.\n- Reserved in checkout holds units for a shopper who has reached the payment page, so the last one cannot be sold twice.\nReserved stock {#reserved-stock}\nWhen a shopper reaches the payment page, the units in their basket are reserved — the next shopper is offered what is left, not the same unit. It is what stops two people paying for the last one.\nYour stock count does not move when a unit is reserved. A reservation is a promise, not a sale, and the count means what is on the shelf. The products list names the difference instead: 3 (1 reserved) is three units on the shelf with one of them spoken for, so two are available to buy right now.\nA reservation is released when the shopper pays (the count moves then), when they abandon the checkout, or after 31 minutes, whichever comes first. A checkout page left open expires on its own, so nothing stays reserved by someone who walked away.\nTwo cases reserve nothing, deliberately: a variant with no stock tracking has no number to reserve against, and a product set to allow backorders is one you have told us to keep selling past zero.\nSales at the register are not affected — the till never refuses a sale, because the shelf in front of the cashier is the truth.\nStock movements {#stock-movements}\nInventory → Stock movements is the history behind every tracked count — the answer to "the shelf says four and the console says six, what happened?"\nFour things write to it and '
     },
     {
         path: '/commerce-and-bookings/commerce/overview',
         title: 'Commerce',
         heading: 'Gift cards & store credit',
         anchor: '#gift-cards',
-        text: 'Gift cards lists every card your store has issued, what is left on each one, and what that adds up to. Business plan and above.\nCards arrive two ways:\n- A shopper buys one. A gift-card purchase mints a card with a code at the moment the payment settles.\n- You issue one by hand. Enter an amount and, optionally, an email address and the code is created and mailed to that person. This is the goodwill gesture and the service-recovery path — a refund you would rather keep as store credit.\nBalances apply automatically at checkout; a shopper enters the code and the card is drawn down by what the order uses. Search the list by code or by recipient email to find one.\nOutstanding balance is a liability, not revenue The outstanding total at the top is money customers have already paid you and have not yet spent. It is store credit you owe against future orders, and it belongs on the liability side of your books — not in a sales figure. Cards are counted at zero or above, so a card that has somehow gone negative cannot flatter that total downward.\nVoiding a card zeroes whatever is left on it. The holder can no longer redeem it and the action cannot be undone, so you are asked to confirm the remaining amount first.'
+        text: 'Gift cards lists every card your store has issued, what is left on each one, and what that adds up to. Business plan and above.\nCards arrive two ways:\n- A shopper buys one. A gift-card purchase mints a card with a code at the moment the payment settles.\n- You issue one by hand. Enter an amount and, optionally, an email address and the code is created and mailed to that person. This is the goodwill gesture and the service-recovery path — a refund you would rather keep as store credit.\nBalances apply automatically at checkout; a shopper enters the code and the card is drawn down by what the order uses. Search by code or email finds a card anywhere in the list, not only on the page in front of you: type the start of its code (with or without GC-) or a word of the recipient\'s address. Search matches one word at a time and reads the first 12 characters of it.\nOutstanding balance is a liability, not revenue The outstanding total at the top is money customers have already paid you and have not yet spent. It is store credit you owe against future orders, and it belongs on the liability side of your books — not in a sales figure. Cards are counted at zero or above, so a card that has somehow gone negative cannot flatter that total downward.\nVoiding a card zeroes whatever is left on it. The holder can no longer redeem it and the action cannot be undone, so you are asked to confirm the remaining amount first.'
     },
     {
         path: '/commerce-and-bookings/commerce/overview',
         title: 'Commerce',
         heading: 'Recovery & alerts',
         anchor: '#recovery-and-alerts',
-        text: 'Two queues the storefront fills and Aglyn drains for you, both visible so you can see they are moving.\nAbandoned checkouts — a shopper who reached checkout, entered their email and left. Aglyn emails them once, with a link back to the cart they had built, about fifteen minutes after that checkout has been idle for an hour. A checkout that gets completed stops reminding itself, and one that is never completed is given up on after seven days. The card shows how many are due a reminder, how many are still inside the first hour, and how many have already been reminded, with the most recent few named. Pro plan and above.\nBack-in-stock alerts — anyone who used "Notify me when it\'s back" on a sold-out product is emailed once its stock goes above zero. The count of shoppers waiting is a demand signal worth restocking against. Available on every plan that includes commerce.\nBoth are read-only here on purpose. Sending is the scheduled job\'s to do, and a "send now" button would race it for a reminder you cannot un-send.'
+        text: 'Two queues the storefront fills and Aglyn drains for you, both visible so you can see they are moving.\nAbandoned checkouts — a shopper who reached checkout, entered their email and left. Aglyn emails them once, with a link back to the cart they had built, about fifteen minutes after that checkout has been idle for an hour. A checkout that gets completed stops reminding itself, and one that is never completed is given up on after seven days. The card shows how many are due a reminder, how many are still inside the first hour, and how many have already been reminded, with the five most recent open checkouts named. Pro plan and above.\nBack-in-stock alerts — anyone who used "Notify me when it\'s back" on a sold-out product is emailed once its stock goes above zero. The count of shoppers waiting is a demand signal worth restocking against. Available on every plan that includes commerce.\nEvery figure is counted across the whole queue, however long it is, and counted again when a checkout changes. Until a count arrives its chip shows a dash rather than a zero.\nBoth are read-only here on purpose. Sending is the scheduled job\'s to do, and a "send now" button would race it for a reminder you cannot un-send.'
     },
     {
         path: '/commerce-and-bookings/commerce/overview',
@@ -3222,7 +3222,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'POS & reservations',
         heading: 'The register',
         anchor: '#the-register',
-        text: 'Open /{site}/pos in the console for a touch-first register. Pick which register you\'re on at the top of the panel (skipped automatically when you have only one):\n- Product grid — tap to add; products with variants show quick chips.\n- Barcode scanners — any keyboard-wedge scanner works: it types the code into the search box and presses Enter, which adds the exact SKU/barcode match. No drivers or pairing needed.\n- Payments — cash (with change calculation), card via QR (the customer scans and pays on their phone; the sale completes automatically), or charge to room for checked-in reservation guests. Stripe Terminal readers can replace the QR step later without changing the flow.\n- Receipts print through the browser\'s print dialog — any receipt printer with a system print driver works. Set the paper size to your roll width once and the browser remembers it.\nPOS sales create normal orders tagged pos, decrement the same inventory as your online store (per location if you use locations), and appear in the orders list under the channel filter.\nPlatform fees at the register\nYour plan\'s platform fee is charged on the sale, not on how it was paid — the rate is the same whether the customer hands you cash, scans the QR, or charges it to their room. What differs is only how it reaches us:\n| Tender | How the fee is collected |\n| Card (QR) | Deducted from your Stripe payout for that sale |\n| Cash | No payout to deduct from — added to your next monthly invoice |\n| Charge to room | Same as cash: added to your next monthly invoice |\nThe customer never pays the fee, and the amount Due on the register is the same on every tender. On plans with a 0% fee there is nothing to collect either way. See Billing & plans for your plan\'s rates.\nSelling past the count\nIf a line is for more units than '
+        text: 'Open /{site}/pos in the console for a touch-first register. Pick which register you\'re on at the top of the panel (skipped automatically when you have only one):\n- Product grid — tap to add; products with variants show quick chips. The grid shows your first 500 active products by name; typing in the search box finds a product by the start of a word in its name across the whole catalog.\n- Barcode scanners — any keyboard-wedge scanner works: it types the code into the search box and presses Enter, which adds the exact SKU/barcode match. No drivers or pairing needed.\n- Payments — cash (with change calculation), card via QR (the customer scans and pays on their phone; the sale completes automatically), or charge to room for checked-in reservation guests. Stripe Terminal readers can replace the QR step later without changing the flow.\n- Receipts print through the browser\'s print dialog — any receipt printer with a system print driver works. Set the paper size to your roll width once and the browser remembers it.\nPOS sales create normal orders tagged pos, decrement the same inventory as your online store (per location if you use locations), and appear in the orders list under the channel filter.\nPlatform fees at the register\nYour plan\'s platform fee is charged on the sale, not on how it was paid — the rate is the same whether the customer hands you cash, scans the QR, or charges it to their room. What differs is only how it reaches us:\n| Tender | How the fee is collected |\n| Card (QR) | Deducted from your Stripe payout for that sale |\n| Cash | No payout to deduct from — added to your next monthly invoice |\n| Charge to room | Same as cash: added to your next monthly invoice |\nThe customer never pays the fee, and the amount Due on the register is the same on every tender. On pl'
     },
     {
         path: '/commerce-and-bookings/commerce/pos-and-reservations',
@@ -3579,7 +3579,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Companies',
         heading: 'The companies list',
         anchor: '#the-companies-list',
-        text: 'The list shows every company your site may see, newest activity first, with its domain, how many contacts are linked to it, its owner, when it was last changed and its next activity — when the earliest open task against it is due. The table\'s Search box, or Filters › Company, finds a company by the start of its name — the search reaches every company, not only the page on screen — Filters › Owner shows one teammate\'s accounts, and Next activity › is empty keeps only the companies with nothing scheduled. Company and Owner are answered by the query, one at a time — a new one replaces the other — while Next activity narrows the page already loaded and stays beside either; see Filter and search a list. Clicking a row opens the company\'s page.\nThe Contacts column is a count kept on the company and moved with every link and unlink, so a page of companies costs no lookup per row. A company linked before the count existed can read lower than its page shows; the company\'s own page counts live, and is the figure to trust when the two differ.'
+        text: 'The list shows every company your site may see, most recently changed first, with its domain, how many contacts are linked to it, its owner, when it was last changed and its next activity — when the earliest open task against it is due. The table\'s Search box finds a company by a word of its name or its domain. Filters › Company finds one whose name is exactly what you type, or starts with it — which orders the list by name — Filters › Owner shows one teammate\'s accounts, or any of several, and Next activity › is empty keeps only the companies with nothing scheduled.\nEvery filter and the search are answered by the list\'s query, so they reach every company, a page at a time, not only the page on screen, and filters on different columns add up. The search matches whole words from their start — "cof" finds Coffee, a fragment from the middle of a word does not — one word at a time: type several and it searches the first, and says so. Under a site, a member whose access is limited to particular sites searches by the start of a company\'s name, and a notice says so. When a combination cannot be answered by one query, the list does not apply that filter, and a notice above the table names it and says why; see Filter and search a list. Clicking a row opens the company\'s page.\nThe Contacts column is a count kept on the company and moved with every link and unlink, so a page of companies costs no lookup per row. A company linked before the count existed can read lower than its page shows; the company\'s own page counts live, and is the figure to trust when the two differ.'
     },
     {
         path: '/content-and-data/crm/companies',
@@ -3719,7 +3719,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'The contact record',
         heading: 'Finding a contact',
         anchor: '#finding-a-contact',
-        text: 'The list\'s filters reach every contact by name or email, one served filter at a time, and its search box narrows the thousand contacts the list read — see Filters on the Contacts list. The console\'s search (the magnifying glass in the top bar) finds contacts too — by name, email, phone number or company name — and opens the person\'s page. Contacts appear in that search only for members who can manage data on the site, and only while the CRM is available to them.\nThe phone number and company name are kept on the record itself for that lookup, as this site last saved them; the values you see on a person\'s page are always your own site\'s.'
+        text: 'The list\'s filters and its search box reach every contact, page by page; the search finds a person by a word of their name or email addresses — see Filters on the Contacts list. The console\'s search (the magnifying glass in the top bar) finds contacts too — by name, email, phone number or company name — and opens the person\'s page. Contacts appear in that search only for members who can manage data on the site, and only while the CRM is available to them.\nThe phone number and company name are kept on the record itself for that lookup, as this site last saved them; the values you see on a person\'s page are always your own site\'s.'
     },
     {
         path: '/content-and-data/crm/contact-record',
@@ -3824,7 +3824,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Deals pipeline',
         heading: 'The board and the table',
         anchor: '#the-board-and-the-table',
-        text: 'The section opens as a board of the chosen pipeline: one column per open stage, with Won and Lost folded away at the end until you expand them. Each card shows the deal\'s title, amount, the contact and company it is with, its owner, and how many days it has sat in its current stage. Drag a card between columns to move it, or use the card\'s menu to move it, mark it won, or mark it lost from the keyboard.\nAbove the board, three figures summarize what is open: the open count, the pipeline value (every open deal\'s amount, per currency) and the weighted value (each amount multiplied by its stage\'s probability).\nSwitch to the table for a paged list with the title, stage, amount, owner, expected close date, status and next activity of every deal in the pipeline, including the closed ones. The table\'s Filters panel narrows it by Status (open, won or lost), and Next activity › is empty keeps only the deals on the page with no open task scheduled against them — the ones the reports page counts as stuck. Search finds a deal by any word of its title, the middle of a title too, across every deal of the status and pipeline on screen rather than only the page. While it holds a word, the table lists the matches a page at a time, and a notice says so if it read the 1,000 most recently changed deals rather than all of them. Status is answered by the query, and Next activity stays beside it; see Filter and search a list.\nThe table\'s rows have checkboxes: tick some and a bulk bar appears above it to set their stage, set their owner, mark them lost with one reason, export them or delete them. Export CSV above the table downloads the deals on screen as deals.csv — title, pipeline and stage by name, the amount in major units beside its currency, the owner by email address, the expected close '
+        text: 'The section opens as a board of the chosen pipeline: one column per open stage, with Won and Lost folded away at the end until you expand them. Each card shows the deal\'s title, amount, the contact and company it is with, its owner, and how many days it has sat in its current stage. Drag a card between columns to move it, or use the card\'s menu to move it, mark it won, or mark it lost from the keyboard.\nAbove the board, three figures summarize what is open: the open count, the pipeline value (every open deal\'s amount, per currency) and the weighted value (each amount multiplied by its stage\'s probability).\nSwitch to the table for a paged list with the title, stage, amount, owner, expected close date, status and next activity of every deal in the chosen pipeline, including the closed ones, most recently changed first. The table\'s Filters panel narrows it by Status (open, won or lost — one, or any of them), and Next activity › is empty keeps only the deals with no open task scheduled against them — the ones the reports page counts as stuck. Search finds a deal by any word of its title.\nEvery filter and the search are answered by the table\'s query, so they reach every deal in the pipeline, a page at a time, not only the page on screen, and filters on different columns add up. The search matches whole words from their start — "cof" finds Coffee, a fragment from the middle of a word does not — one word at a time: type several and it searches the first, and says so. Under a site, a member whose access is limited to particular sites searches by the start of a deal\'s title, and a notice says so. When a combination cannot be answered by one query, the table does not apply that filter, and a notice above it names the filter and says why; see Filter and search a list. The board ha'
     },
     {
         path: '/content-and-data/crm/deals',
@@ -3971,7 +3971,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Leads',
         heading: '',
         anchor: '',
-        text: 'Leads\nA lead is somebody you have heard of but not yet qualified: a visitor who booked or wrote in through a form that routes leads, a person from a list you imported, or one you added by hand. It is a record of its own — the way it is in Salesforce — and it becomes a contact only when you convert it. The Leads section of the CRM is where the team works them — decides who owns each one, keeps notes, and either converts the lead into a contact or closes it with a reason.\nLeads live under the site that captured them, so each site\'s list is its own. Open CRM → Leads in the console, or use Open in CRM on a lead row in the Inbox\'s Site Members & Leads section.\nPlan availability Leads are part of the CRM, included from Starter. On Free the section is shown locked, with the rest of the CRM. Leads are still filed on Free, exactly as described below, and kept; workspace owners and admins can export every lead, or erase a person, from Settings → Privacy. See What each plan includes.'
+        text: 'Leads\nA lead is somebody you have heard of but not yet qualified: a visitor who booked or wrote in through a form that routes leads, a person from a list you imported, or one you added by hand. It is a record of its own — the way it is in Salesforce — and it becomes a contact only when you convert it. The Leads section of the CRM is where the team works them — decides who owns each one, keeps notes, and either converts the lead into a contact or closes it with a reason.\nLeads live under the site that captured them, so each site\'s list is its own. Open CRM → Leads in the console, or use Open in CRM on a row of the Leads list in the Inbox\'s Site Members & Leads section.\nPlan availability Leads are part of the CRM, included from Starter. On Free the section is shown locked, with the rest of the CRM. Leads are still filed on Free, exactly as described below, and kept; workspace owners and admins can export every lead, or erase a person, from Settings → Privacy. See What each plan includes.'
     },
     {
         path: '/content-and-data/crm/leads',
@@ -3992,7 +3992,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Leads',
         heading: 'The Leads list',
         anchor: '#the-leads-list',
-        text: 'The list shows the most recently seen leads first — a person who booked yesterday sits above one who signed up last month, whichever came first. Each row carries:\n| Column | What it shows |\n| Lead | The name the person gave, with their email beneath it — or the email alone. |\n| Company, Title | The lead\'s own company and job title, as text. |\n| Status | New, Working, Qualified or Unqualified. Change it in place from the row. |\n| Email | The last verdict on the lead\'s address — see Email state — or a dash when nothing is known. |\n| Owner | The team member working the lead, or Unassigned. A lead inherits its contact\'s owner when one is assigned on capture. |\n| Source | Every surface that captured this person: Booking, the form they submitted, an import, New lead, or the API — and Sign-up on leads filed before sign-ups stopped making leads. |\n| Lead source | The lead\'s lead source. Sorting by it follows the order of your list, not the alphabet. |\n| Tags | The lead\'s tags. |\n| Campaign | The campaigns the lead is filed under, by name. Under a site only — a campaign belongs to one site. |\n| Last seen | When the person last did something on your site. |\nFilter and search the leads {#filter-the-leads}\nThe table\'s own toolbar filters the list: Filters opens the filter panel, and Search finds a lead by name, email, company, title or tag. Status, Email, Owner, Lead source and Campaign are picked from a list in the panel, and from each column\'s menu. Status starts on Open (new or working), every lead that still needs working; pick one status instead, or remove the filter to see every lead. A lead nobody has touched yet has no status of its own and reads as New, so the leads your site collected before the CRM existed are already in the Open view. Email narrows by the address\'s verd'
+        text: 'The list shows the most recently seen leads first — a person who booked yesterday sits above one who signed up last month, whichever came first. It keeps that order: the column headers do not re-sort it. Each row carries:\n| Column | What it shows |\n| Lead | The name the person gave, with their email beneath it — or the email alone. |\n| Company, Title | The lead\'s own company and job title, as text. |\n| Status | New, Working, Qualified or Unqualified. Change it in place from the row. |\n| Email | The last verdict on the lead\'s address — see Email state — or a dash when nothing is known. |\n| Owner | The team member working the lead, or Unassigned. A lead inherits its contact\'s owner when one is assigned on capture. |\n| Source | Every surface that captured this person: Booking, the form they submitted, an import, New lead, or the API — and Sign-up on leads filed before sign-ups stopped making leads. |\n| Lead source | The lead\'s lead source. |\n| Tags | The lead\'s tags. |\n| Campaign | The campaigns the lead is filed under, by name. Under a site only — a campaign belongs to one site. |\n| Last seen | When the person last did something on your site. |\nFilter and search the leads {#filter-the-leads}\nThe table\'s own toolbar filters the list: Filters opens the filter panel, and Search finds a lead by a word of its name, its email address — and each part of the address, so the domain alone finds it — its company, its title or its tags. Status, Email, Owner, Lead source and Campaign are picked from a list in the panel, and from each column\'s menu. Status starts on Open (new or working), every lead that still needs working; pick one status instead, or remove the filter to see every lead. A lead nobody has touched yet has no status of its own and reads as New, so the leads your site co'
     },
     {
         path: '/content-and-data/crm/leads',
@@ -4160,7 +4160,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Reports',
         heading: 'Lead funnel',
         anchor: '#lead-funnel',
-        text: 'Of the leads this site captured in the period, where each one stands now, and why the ones closed without converting were closed.\n- Leads captured — leads first seen in the period, counted on the server, with the change against the previous period.\n- Qualified and Unqualified — how many of those captured have been converted, or closed without converting, each with its share of the leads captured.\n- Still open — leads that are New or Working.\n- Where they stand — one bar per status. A lead nobody has touched yet is New.\n- Why leads were unqualified — the reasons given when leads were unqualified, most common first, each with its share of the unqualified leads. Different spellings of one reason are counted together; a lead closed with no reason is listed as No reason given.\nA lead is placed by when it was first seen, so a returning visitor\'s second form does not make a second lead in a second period. The funnel is read from the period\'s 200 most recently captured leads — the same window the Leads list shows — and says so when the period held more. Because leads belong to a site rather than to the workspace, this card reports the site you are looking at; at the organization level it reads every site — at most 200 leads per site — and totals them, naming the per-site window when any site held more.'
+        text: 'Of the leads this site captured in the period, where each one stands now, and why the ones closed without converting were closed.\n- Leads captured — leads first seen in the period, counted on the server, with the change against the previous period.\n- Qualified and Unqualified — how many of those captured have been converted, or closed without converting, each with its share of the leads captured.\n- Still open — leads that are New or Working.\n- Where they stand — one bar per status. A lead nobody has touched yet is New.\n- Why leads were unqualified — the reasons given when leads were unqualified, most common first, each with its share of the unqualified leads. Different spellings of one reason are counted together; a lead closed with no reason is listed as No reason given.\nA lead is placed by when it was first seen, so a returning visitor\'s second form does not make a second lead in a second period. The funnel is read from the period\'s 200 most recently captured leads, and says so when the period held more. Because leads belong to a site rather than to the workspace, this card reports the site you are looking at; at the organization level it reads every site — at most 200 leads per site — and totals them, naming the per-site window when any site held more.'
     },
     {
         path: '/content-and-data/crm/reports',
@@ -4279,7 +4279,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Sequences',
         heading: 'Sequences',
         anchor: '#sequences',
-        text: 'A sequence is the emails, and the tasks between them, one person gets from one rep. Sequences → All sequences lists each one with its mailbox, its status, and how many people it has enrolled, and how many of them are still active, replied, bounced or opted out.\nThe table\'s toolbar filters the list. Filters narrows it by Status (pick one or several), name or mailbox, and Search matches any word of a sequence\'s name or mailbox. Both look at every sequence the list read — the 200 newest, which for nearly every organization is all of them, and a note under the table says when there are older ones — not only the page on screen, and each filter in force shows as a chip above the table; remove a chip to drop its filter. The Filters panel edits one filter at a time, and filters on different columns add up; see Filter and search a list.\nBuild a sequence {#build-a-sequence}\nSelect New sequence, name it, and choose the site whose CRM the people you enroll are contacts of and the mailbox it sends from. A sequence sends as the member who connected its mailbox, so only that member, or an organization owner or admin, can edit or activate it.\nThe Mailbox list offers the mailboxes you connected, and an owner or admin every mailbox in the organization. A disconnected mailbox is never offered. When exactly one of your own mailboxes is active, a new sequence starts on it. With none, connect one first.\nA sequence holds up to eight steps, of which up to four are emails:\n- Email — a subject and a body, or a CRM email template whose body is sent. Insert merge fields — the contact\'s first name, company or job title, your own name, the site\'s name — and {{enrollment.personalLine}}, the sentence you write for each person when you enroll them. Every email after the first replies in the first one\'s'
+        text: 'A sequence is the emails, and the tasks between them, one person gets from one rep. Sequences → All sequences lists each one with its mailbox, its status, and how many people it has enrolled, and how many of them are still active, replied, bounced or opted out.\nThe list is newest first, a page at a time. The table\'s toolbar filters it. Filters narrows it by Status or Mailbox (pick one or several), by the name (a word in it, or the whole name), or by the day it was Created (on, before or after a date). Search finds a sequence by the start of any word of its name. Every filter and the search are answered by the database across all your sequences, not only the page on screen, and each filter in force shows as a chip above the table; remove a chip to drop its filter. The Filters panel edits one filter at a time, and filters on different columns add up. A combination the database cannot answer at once — a name word together with a search, for example — is named above the table rather than applied to some rows. See Filter and search a list.\nBuild a sequence {#build-a-sequence}\nSelect New sequence, name it, and choose the site whose CRM the people you enroll are contacts of and the mailbox it sends from. A sequence sends as the member who connected its mailbox, so only that member, or an organization owner or admin, can edit or activate it.\nThe Mailbox list offers the mailboxes you connected, and an owner or admin every mailbox in the organization. A disconnected mailbox is never offered. When exactly one of your own mailboxes is active, a new sequence starts on it. With none, connect one first.\nA sequence holds up to eight steps, of which up to four are emails:\n- Email — a subject and a body, or a CRM email template whose body is sent. Insert merge fields — the contact\'s firs'
     },
     {
         path: '/content-and-data/crm/sequences',
@@ -4293,7 +4293,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Sequences',
         heading: 'Enrollments',
         anchor: '#enrollments',
-        text: 'A sequence\'s Enrollments tab lists everyone in it: their status, the step they\'re on, when the next one is due in the mailbox\'s timezone, when the last one went, and why they stopped when they have. A person enrolled as a lead is marked Lead until the lead converts. For each one you can:\n- Pause and Resume — nothing is sent while they\'re paused. An enrollment the engine held because its mail gateway refused you twice is paused the same way, and Resume on it sends the email anyway.\n- Stop — they get nothing more from this sequence.\n- Mark do-not-contact — puts the address on your organization\'s do-not-contact list, which every sequence checks before every send, and stops them in every other sequence too.\nThe tab\'s toolbar filters the people in it. Filters narrows them by Status, Enrolled as (contact or lead), name, email or stop reason, and Search matches any word of a name, address, step or stop reason. The filters look at the enrollments read so far, 200 at a time; on a sequence with more than that, the table says so, and paging forward reads the next 200. See Filter and search a list.'
+        text: 'A sequence\'s Enrollments tab lists everyone in it: their status, the step they\'re on, when the next one is due in the mailbox\'s timezone, when the last one went, and why they stopped when they have. A person enrolled as a lead is marked Lead until the lead converts. For each one you can:\n- Pause and Resume — nothing is sent while they\'re paused. An enrollment the engine held because its mail gateway refused you twice is paused the same way, and Resume on it sends the email anyway.\n- Stop — they get nothing more from this sequence.\n- Mark do-not-contact — puts the address on your organization\'s do-not-contact list, which every sequence checks before every send, and stops them in every other sequence too.\nThe tab lists the people newest enrolled first, a page at a time, and its toolbar filters them. Filters narrows them by Status, Enrolled as (contact or lead) and Stop reason (pick one or several), by the whole Email address, or by the day they were Enrolled (on, before or after a date). Search finds a person by the start of any word of their name or of their address — casey, morgan or example.com all find casey.morgan@example.com. Every filter and the search are answered by the database across everyone in the sequence, not only the page on screen; a combination it cannot answer at once is named above the table instead of being applied to some rows. See Filter and search a list.'
     },
     {
         path: '/content-and-data/crm/sequences',
@@ -4412,7 +4412,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Tasks & follow-ups',
         heading: 'The tasks page',
         anchor: '#the-tasks-page',
-        text: 'The Tasks section is one list with six views, chosen under Show in the table\'s Filters panel — My tasks unless you choose another:\n| View | What it shows |\n| My tasks | Open tasks assigned to you, soonest due first. Tasks with no due date come last. |\n| Overdue | Open tasks whose due date is before today. |\n| Today | Open tasks due at any time today. |\n| Upcoming | Open tasks due tomorrow or later. |\n| All open | Every open task, whoever it is assigned to. |\n| Done | Completed tasks, most recently due first. |\n"Overdue" and "today" are not stored on the task — nothing runs at midnight to stamp them. Each view is a window over the due date computed from your own clock and time zone when you look, and a tab left open across midnight repaints yesterday\'s work as overdue on its own.\nEach row shows a checkbox that completes or reopens the task, the title (with the first line of notes under it), the kind, the priority, the due date colored by where it stands — red when overdue, amber when due today — with a snooze beside it, the assignee, and the record it is for, as a link into that record\'s page. A view shows at most 200 rows and says so when it is full; narrow the view to see the rest.\nBeside Show, the Filters panel narrows a view by Kind (call, email, meeting, to-do), Priority (low, normal, high) and Assignee, and Search matches words in a task\'s title and notes. Those narrow the rows the view loaded — at most 200 — and add up with each other; see Filter and search a list.\nThe calendar view\nList and Calendar sit beside the view control. The calendar draws one month, placing each task on the day it is due, and clicking one opens the same drawer a row does. The arrows page a month at a time and Today comes back.\nThe calendar draws the same tasks the list is showing — the sa'
+        text: 'The Tasks section is one list with six views, chosen under Show in the table\'s Filters panel — My tasks unless you choose another:\n| View | What it shows |\n| My tasks | Open tasks assigned to you, soonest due first. Tasks with no due date come last. |\n| Overdue | Open tasks whose due date is before today. |\n| Today | Open tasks due at any time today. |\n| Upcoming | Open tasks due tomorrow or later. |\n| All open | Every open task, whoever it is assigned to. |\n| Done | Completed tasks, most recently due first. |\n"Overdue" and "today" are not stored on the task — nothing runs at midnight to stamp them. Each view is a window over the due date computed from your own clock and time zone when you look, and a tab left open across midnight repaints yesterday\'s work as overdue on its own.\nEach row shows a checkbox that completes or reopens the task, the title (with the first line of notes under it), the kind, the priority, the due date colored by where it stands — red when overdue, amber when due today — with a snooze beside it, the assignee, and the record it is for, as a link into that record\'s page. The list shows a view a page at a time, with the usual footer to pick how many rows a page holds and to turn to the next page.\nBeside Show, the Filters panel narrows a view by Kind (call, email, meeting, to-do), Priority (low, normal, high) and Assignee, and Search finds a task by a word of its title. The view, the filters and the search are all answered by the list\'s query, so they reach every task in the view, page by page, and add up with each other. The search matches whole words from their start — "cof" finds Coffee, a fragment from the middle of a word does not — one word at a time: type several and it searches the first, and says so. Under a site, a member whose access is li'
     },
     {
         path: '/content-and-data/crm/tasks',
@@ -4496,28 +4496,28 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Saved views',
         heading: 'Filters',
         anchor: '#filters',
-        text: 'Every CRM list filters through its table\'s own toolbar: Filters opens the filter panel, Search finds a record by its name and the words beside it, and each column\'s menu has Filter too. Pick a column, a condition and a value; a field with fixed choices — a status, a stage, an owner, a lead source, a campaign, a kind, a priority — is picked from a list, a date from a calendar, anything else typed.\nThe panel edits one filter at a time. Filters on different columns add up: filter one column, then another, and the list keeps both. Every filter in force shows as a chip beside the views control, where its ✕ removes it, and all of them are part of the saved view. A view saved before the panel existed keeps its filters as they were. The toolbar works the way it does on every console list — see Filter and search a list — and the sections below say what each CRM list\'s filters reach. On the companies and deals lists one served filter applies at a time, so a new one replaces the last.'
+        text: 'Every CRM list filters through its table\'s own toolbar: Filters opens the filter panel, Search finds a record by its name and the words beside it, and each column\'s menu has Filter too. Pick a column, a condition and a value; a field with fixed choices — a status, a stage, an owner, a lead source, a campaign, a kind, a priority — is picked from a list, a date from a calendar, anything else typed.\nThe panel edits one filter at a time. Filters on different columns add up: filter one column, then another, and the list keeps both. Every filter in force shows as a chip beside the views control, where its ✕ removes it, and all of them are part of the saved view. A view saved before the panel existed keeps its filters as they were. The toolbar works the way it does on every console list — see Filter and search a list — and the sections below say what each CRM list\'s filters offer.\nOn every CRM list the filters and the search are answered by the list\'s own query, so they reach every record, a page at a time, and never only the rows on screen. The search matches whole words from their start — "cof" finds Coffee, a fragment from the middle of a word does not — one word at a time: type several and it searches the first, and says so. It reads the first 12 letters of a long word.\nA few combinations cannot be answered by one query — two "contains" or "any of" filters at once, say, or one of them beside the search. Then the list does not apply that filter, and a notice above the table names it and says why.'
     },
     {
         path: '/content-and-data/crm/views',
         title: 'Saved views',
         heading: 'Filters on the Contacts list',
         anchor: '#filters-on-the-contacts-list',
-        text: 'On the Contacts list the fields are the list\'s columns and a few that are not — owner, stage, source, company, tags, form, orders, lifetime value, created and updated dates, email verdict, next activity, and one field per custom field your organization has defined.\nOne chip reaches every contact and the rest narrow what it found. The database answers one filter per query, so the first filter it can serve — a name, an email, a tag, a form, a date, an order count — is run against the whole collection, and every other filter narrows the first thousand contacts that query returned — the newest, unless the served filter sorts them its own way. The search box, over name, email, phone, company and tags, narrows those same thousand. The served chip is filled; the others are outlined; and the caption under the chips says which is which. Owner, stage, source, company and custom-field filters always narrow rather than reach, because those facts are kept per site and no query can reach them directly. On a site\'s Contacts list a name or tag contains filter narrows too, because the query already spends its one list match on the site. Sorting reorders the loaded window.'
+        text: 'On the Contacts list the fields are the list\'s columns and a few that are not — owner, stage, source, company, tags, form, site, orders, lifetime value, the updated date, email verdict, next activity, and one field per custom field your organization has defined.\nEach field offers what the list\'s query can answer:\n| Field | Filter by |\n| Contact | The name contains a word, is exactly a name, starts with or ends with some letters. |\n| Email | is an address, or starts with some letters. |\n| Tags | contains a tag, any of several, or is not empty. |\n| Form ID | contains a form\'s ID — the form\'s own page links here with it. |\n| Site ID | is a site\'s ID, or any of several. |\n| Orders, Lifetime value | is not empty — the person has bought, or is worth something. Each site keeps its own figures on its own record of the person, where no range reaches, so there are no numeric ranges. |\n| Created | on, after or before a date. |\n| Updated | on, after or before a date. |\n| Next activity | is empty — no next activity scheduled. |\n| Owner, Stage | is one, any of several, or is not empty. |\n| Source | is one, or any of several. |\n| Company | is one, or is not empty. |\n| Email verdict | is one verdict, any of several, is empty (nothing known) or is not empty. |\n| A custom field | equals a choice, or any of several, for a choice field; equals for text or a number; is or is not ticked for a checkbox; is not empty for any. |\nSearch finds a person by a word of their name, their email addresses or their company, or by the digits of their phone number — the whole number, or its last seven or last four digits, typed without spaces or brackets. Tags have their own filter.\nCreated, and a name or address that starts with or ends with some letters, each order the list by their own field, so each st'
     },
     {
         path: '/content-and-data/crm/views',
         title: 'Saved views',
         heading: 'Filters on the other lists',
         anchor: '#filters-on-the-other-lists',
-        text: '- Leads — Status, Email, Owner, Lead source and Campaign; see the leads list. The list reads the 200 most recently seen leads, and every filter and the search narrow those.\n- Companies — Company (starts with or is) and Owner reach every company; the search box is the same Company starts with filter. The list is paged, so one of the two applies at a time.\n- Deals (the table) — Status reaches every deal. The search box finds a deal by any word of its title, across the 1,000 most recently changed deals of that status and pipeline — for nearly every organization, all of them.\n- Tasks — Show is the task view (My tasks, Overdue, Today, Upcoming, All open, Done) and is answered by the query, up to 200 tasks a view; Kind, Priority and Assignee, and the search over title and notes, narrow the rows that view loaded.\nOn the contacts, companies and deals lists, Next activity › is empty keeps only the records with no open task scheduled against them (see next activity). It narrows the rows already loaded rather than the whole collection, the way a contacts filter that cannot be served does, and it stays beside the companies and deals lists\' one served filter.'
+        text: '- Leads — Status, Email, Owner, Lead source and Campaign; the search finds a lead by a word of its name, email address, company, title or tags. Campaign and the search cannot be combined. See the leads list.\n- Companies — Company (is exactly, or starts with, which orders the list by name), Owner (one teammate, or any of several) and Next activity; the search finds a company by a word of its name or domain. See the companies list.\n- Deals (the table) — Status (open, won or lost; one, or any of them) and Next activity; the search finds a deal by any word of its title. See the board and the table.\n- Tasks — Show is the task view (My tasks, Overdue, Today, Upcoming, All open, Done); Kind, Priority and Assignee filter it, and the search finds a task by a word of its title.\nOn the contacts, companies and deals lists, Next activity › is empty keeps only the records with no open task scheduled against them (see next activity). Like every other filter, it is answered by the query and adds up with the rest.'
     },
     {
         path: '/content-and-data/crm/views',
         title: 'Saved views',
         heading: 'Columns and sort',
         anchor: '#columns-and-sort',
-        text: 'Manage columns in any list\'s column menu chooses what shows, and Move left / Move right in the same menu put a column where you want it. A view keeps both — the choice and the order — and a view saved before a column existed shows the new column too, after the ones it names. Click a column header to sort; a view keeps that as well.'
+        text: 'Manage columns in any list\'s column menu chooses what shows, and Move left / Move right in the same menu put a column where you want it. A view keeps both — the choice and the order — and a view saved before a column existed shows the new column too, after the ones it names. On the Leads and Contacts lists the column headers do not sort: those lists keep their newest-first order.'
     },
     {
         path: '/content-and-data/crm/views',
@@ -4636,7 +4636,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Datasets & Dynamic Content',
         heading: 'Filter and search the records',
         anchor: '#filter-records',
-        text: 'The records table filters through its own toolbar: Filters opens the filter panel, where every field of the dataset\'s model is a column, and Search finds records by the words in their text. A field with a fixed list of options, and a true/false field, are picked from a list; numbers and dates take a value; reference, map, bytes, coordinates and null fields are not filterable. Each filter shows as a chip above the table, and removing the chip removes the filter. The panel and chips work as on every console list — see Filter and search a list; what differs here is how far a filter reaches.\nOne condition reaches every record. A single filter or a single search word is answered across the whole dataset and paged like the unfiltered table, when it is:\n- a field equals a value — for a text field, ignoring case;\n- a text field contains a word, which matches words that start with what you typed (kett finds Kettle, ttle does not);\n- a list field contains one of its entries;\n- one search word, which likewise matches the start of any word in the record\'s text fields, option fields and lists.\nIts chip is highlighted. Anything more is matched over the first 1,000 records that the first condition finds (or the first 1,000 records of the dataset, when none of the conditions can be answered that way): a second filter or search word, a filter that contains several words, number and date ranges, is empty, is not, and is any of. When there were more than 1,000 to look through, the table says so. A word is matched on its first 12 characters, and a text value\'s first 40 words are searchable.\nThis needs no database index — nothing to deploy on a self-hosted project. Records keep their filter terms in a filterKeys field that every write keeps current. Records written before the field existed '
+        text: 'The records table filters through its own toolbar: Filters opens the filter panel, where each filterable field of the dataset\'s model is a column, and Search finds records by the words in their text. Each filter shows as a chip above the table, and removing the chip removes the filter. The panel and chips work as on every console list — see Filter and search a list.\nEvery filter and the search reach the whole dataset. They are answered by the database across every record, and the table pages through the matches exactly as it pages through the unfiltered dataset — nothing is matched only against the records already on screen. What each field type offers:\n| Field | Filters |\n| -- | -- |\n| Text with a fixed list of options | is, is any of — picked from the options |\n| True/false | is — picked |\n| Number | = |\n| Plain text | equals and is any of, ignoring case; contains a word |\n| List | contains one of its entries, spelled exactly as stored |\nDates, references, maps, bytes, coordinates and null fields are not filterable, and no field offers ranges (greater than, before, after), is not, or is empty — the panel does not show what the database cannot answer this way.\nContains and search match the start of a word. kett finds Kettle; ttle finds nothing. The search looks at every text field, option field and list of the record. Each asks for one word: type several and the table uses the first and says so above the records. A word is matched on its first 12 characters, a text value\'s first 40 words are searchable, and equals compares the first 64 characters of a text value.\nCombine as many is, equals, is any of and = filters as you like, but only one contains or search at a time. A second one — a contains while a search word is typed, or a contains on a second field — is not appl'
     },
     {
         path: '/content-and-data/datasets/overview',
@@ -4811,7 +4811,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Forms & Lead Capture',
         heading: 'Find a form in the list',
         anchor: '#find-a-form',
-        text: 'The Forms table filters through its toolbar by every column it shows:\n- Display name and Slug, as text.\n- Submissions and Leads, as numbers: equal to, over, under, or empty. A form that doesn\'t route to leads never counts any, so its Leads shows a dash. Leads is empty finds those forms, and Leads = 0 finds a lead-routed form that hasn\'t produced one yet.\n- Last submission and Updated, as days: on, after or before a date, or empty.\nThe Filters panel also offers four columns the table keeps hidden:\n- Created, a day. Show it from Columns to see each form\'s date.\n- Status, active or retired.\n- Lead routing, on or off. This is the lead switch on the form\'s CRM routing card.\n- Campaign, the campaigns a form is filed under. It\'s offered once a form in the list is filed under one.\nSearch matches a form\'s name, slug or ID. Retired forms stay out of the list until you ask for them: choose Status in the Filters panel and pick Retired to find one and restore it. The list is paged, so the first filter reads the first 100 forms and matches over them, counts and dates included. The table says when there are more, and paging forward reads the next page. See Filter and search a list.'
+        text: 'The Forms table filters through its toolbar by every column it shows:\n- Display name, by a word in it: contains "audit" finds "Multi-brand site audit".\n- Slug, exactly.\n- Submissions, as a number: equal to, over or under a number, or empty. A form that hasn\'t had a submission shows a dash, and is empty finds it.\n- Leads, equal to a number, or empty. A form counts a lead only once it files one, so a form that doesn\'t route to leads, or hasn\'t filed its first, shows a dash. Is empty finds those forms. No form stores a zero, so Leads = 0 finds none.\n- Last submission and Updated, as days: on, before or after a date. Last submission is set finds every form that has had a submission.\nTwo more columns stay hidden until you show them from Columns, and the Filters panel offers them either way: Status (active or retired) and Lead routing (on or off, the switch on the form\'s CRM routing card). Campaign finds the forms filed under any of the campaigns you pick. The panel lists the site\'s campaigns once you open it.\nSearch finds a form by a word of its name or slug, or by its ID. It looks for one word, the first you type, and says so when you type more.\nEvery filter and the search look through the whole catalog, not just the page on screen, and the pager turns through the matches. Filters on different columns add up, with one limit: one range at a time, meaning a number over or under, or a date before or after. A second range isn\'t applied, and the list says which one it left out. Retired forms stay out of the list until you ask for them: choose Status in the Filters panel and pick Retired to find one and restore it. See Filter and search a list.'
     },
     {
         path: '/content-and-data/forms/overview',
@@ -4846,7 +4846,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Media Library & CDN',
         heading: 'Organize',
         anchor: '#organize',
-        text: '- Arrange media in a folder hierarchy. Folders appear as cards in the grid (folders first, before files) as well as in a side rail — open one to browse into it, and use the breadcrumb to step back out.\n- Drag and drop to reorganize: drag a file (or a whole selection) onto a folder to move it in, drag a folder onto another to nest it, or drop onto a breadcrumb to move items up and out. Nesting depth and name-collision rules are enforced automatically.\n- Move to folder… shows the full path, not just the folder name — Blog / Covers and Press / Covers are two different destinations and the menu says so. The same paths appear in the detail drawer\'s Folder field.\n- Big moves are safe to interrupt. Moving a large selection relocates the stored objects one at a time, so the library keeps working through it and tells you how far it has got. If it cannot finish everything, it reports the real split — Moved 7 of 19 — 12 could not be moved — and leaves the files that did not move selected, so clicking Move again picks up exactly where it stopped. Nothing is lost either way: a file is only ever in one folder, its URL keeps working, and a repeat move of a file that already arrived does nothing.\n- Filter by type, date, and size, search, and sort the library.\n- Search covers everything you authored, not just file names — alt text, description, tags, folder name and your own custom metadata values are all searchable. Results update as you type, and ✕ (or Esc) clears the box.\n- Wildcards: mock--noshadow.png matches a whole family of files. is any run of characters, ? is exactly one, and a wildcard pattern matches the whole value.\n- Search one field: tag:hero, name:logo, alt:product, desc:landing, folder:brand, or a custom field by key — meta.campaign:spring. Combine them with plain words'
+        text: '- Arrange media in a folder hierarchy. Folders appear as cards in the grid (folders first, before files) as well as in a side rail — open one to browse into it, and use the breadcrumb to step back out.\n- Drag and drop to reorganize: drag a file (or a whole selection) onto a folder to move it in, drag a folder onto another to nest it, or drop onto a breadcrumb to move items up and out. Nesting depth and name-collision rules are enforced automatically.\n- Move to folder… shows the full path, not just the folder name — Blog / Covers and Press / Covers are two different destinations and the menu says so. The same paths appear in the detail drawer\'s Folder field.\n- Big moves are safe to interrupt. Moving a large selection relocates the stored objects one at a time, so the library keeps working through it and tells you how far it has got. If it cannot finish everything, it reports the real split — Moved 7 of 19 — 12 could not be moved — and leaves the files that did not move selected, so clicking Move again picks up exactly where it stopped. Nothing is lost either way: a file is only ever in one folder, its URL keeps working, and a repeat move of a file that already arrived does nothing.\n- Filter, search and sort through the same toolbar as every other list in the console, in either of two views — see Filter and search and Grid and List views below.\n- Search finds a file by any word of its name — banner finds hero-banner2x.png, because a file name\'s words are split at dashes, dots and underscores as well as spaces. Results come from the whole library, however large, and ✕ (or Esc) clears the box.\n- Capture and edit metadata in a detail drawer — file name, alt text, description, tags, and your own custom key/value metadata (mirrored onto the delivered object\'s storage metadata)'
     },
     {
         path: '/content-and-data/media/overview',
@@ -5441,7 +5441,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Publisher handbook',
         heading: 'How installs work (the buyer side)',
         anchor: '#how-installs-work-the-buyer-side',
-        text: 'Browse is a catalog — cards link to the detail page, which is the only place an install happens. The buyer picks targets (all sites, selected sites, or org-wide for plugins), confirms a dialog that names exactly where the install lands, and the pin is written: your exact {version, sha256} pinned to the site or org, the plugin enabled for the workspace, loaded on their next visit. Buyers can uninstall from the listing\'s own detail page (Uninstall, or Uninstall org-wide for an org-scope pin) as well as from Marketplace → Installed — removing the pin and disabling it. Data your plugin created stays, so reinstalls resume cleanly. Paid listings require purchase before install; you see sales in your publisher ledger.\nThe detail page shows two install figures side by side: installs is the cumulative all-time total and only ever grows, while active counts the organizations and sites that currently hold a pin — it goes down when someone uninstalls. A big gap between the two is churn worth investigating.\nA purchase licenses the buyer\'s organization, and Marketplace → Licenses lists what the workspace holds and what the buyer bought across every workspace, one table each. Each table filters through its own toolbar: Search finds a listing by name, and Filters offers the listing, who bought it (You or A colleague) on the workspace\'s table, and which workspace a purchase landed in on the buyer\'s own. Both answer over every license the table holds, and each filter in force shows as a chip above it; see Filter and search a list.\nEvery listing shows its artifact type as a chip — Plugin, Component, Site template, Layout, Dataset schema, Email template or Email starter — so buyers know what they\'re getting before they open it. Dataset schemas and email templates read "Added (v1) · add aga'
+        text: 'Browse is a catalog — cards link to the detail page, which is the only place an install happens. The buyer picks targets (all sites, selected sites, or org-wide for plugins), confirms a dialog that names exactly where the install lands, and the pin is written: your exact {version, sha256} pinned to the site or org, the plugin enabled for the workspace, loaded on their next visit. Buyers can uninstall from the listing\'s own detail page (Uninstall, or Uninstall org-wide for an org-scope pin) as well as from Marketplace → Installed — removing the pin and disabling it. Data your plugin created stays, so reinstalls resume cleanly. Paid listings require purchase before install; you see sales in your publisher ledger.\nThe detail page shows two install figures side by side: installs is the cumulative all-time total and only ever grows, while active counts the organizations and sites that currently hold a pin — it goes down when someone uninstalls. A big gap between the two is churn worth investigating.\nA purchase licenses the buyer\'s organization, and Marketplace → Licenses lists what the workspace holds and what the buyer bought across every workspace, one table each. Each table filters through its own toolbar: Search finds a license by a word of its listing\'s name, and Filters offers who bought it (You) on the workspace\'s table, and which workspace a purchase landed in — or Every workspace you belong to, for a purchase that names none — on the buyer\'s own. Both answer over every license, not the page on screen, and each filter in force shows as a chip above it; a word that more than 30 listing names share is refused with a note asking for more of it. See Filter and search a list.\nEvery listing shows its artifact type as a chip — Plugin, Component, Site template, Layout, Datas'
     },
     {
         path: '/developers/plugins/publishing/publisher-handbook',
@@ -6407,7 +6407,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'The console tour',
         heading: 'Filter and search a list',
         anchor: '#filter-and-search',
-        text: 'Most lists in the console are tables with the same toolbar above them: Columns shows and hides columns, Filters narrows the rows, Export downloads the table, and Search finds rows by their words. They work the same way on every list.\n- Filters opens a panel that edits one filter at a time: pick a column, an operator and a value. Pick another column and set it too, and both apply — filters on different columns add up, and each column holds one filter. Clearing the value, or deleting the panel\'s row, drops that column\'s filter.\n- Chips above the table show every filter in force, each read as a sentence such as "Status is Live". The panel shows one filter at a time; the chips show them all. Remove a chip to drop its filter.\n- Search matches words. Type several and a row is kept when every word appears, in any order and either case, in one of the things that list searches — each list\'s page names them. Search adds to the filters, and an empty box shows the list unfiltered again.\n- The pager at the foot of the table then turns through the matches, not the whole list.\nHow far a filter or a search reaches depends on how the list reads its rows, and each list\'s page says which:\n- The whole list. A list that reads every row at once, or whose query applies the filter itself, answers across all of it — not only the page on screen.\n- The rows read. A long list reads a window of its rows instead: its newest rows up to a cap its page names, or, on a list that reads a page at a time, 100 rows as soon as the first filter or search word is set, and one page more each time you turn past the last match. A filter there looks through what has been read, and the table says when there is more.\n- One served filter. Some lists hand one filter to the server, which looks through every record, and'
+        text: 'Most lists in the console are tables with the same toolbar above them: Columns shows and hides columns, Filters narrows the rows, Export downloads the table, and Search finds rows by their words. They work the same way on every list. A list drawn as cards rather than a table — such as All Sites — keeps its cards and has the same Search box, Filters panel and chips above them.\n- Filters opens a panel that edits one filter at a time: pick a column, an operator and a value. Pick another column and set it too, and both apply — filters on different columns add up, and each column holds one filter. Clearing the value, or deleting the panel\'s row, drops that column\'s filter.\n- Chips above the table show every filter in force, each read as a sentence such as "Status is Live". The panel shows one filter at a time; the chips show them all. Remove a chip to drop its filter.\n- Search finds records by the start of a word in the things that list searches — each list\'s page names them. It matches one word at a time: type "acm" and "Acme Coffee" is found; type two words and the list searches the first and says so. A word is read up to its first 12 letters. Search adds to the filters, and an empty box shows the list unfiltered again.\n- The pager at the foot of the table then turns through the matches, not the whole list.\nEvery filter and every search word is answered by the list\'s query, across the whole list — never only the rows already on screen. A record that matches is found whether it would have been on the first page or the fortieth. Two limits follow from asking one query:\n- A filter a query can\'t answer isn\'t offered. The panel lists only the columns and operators the list can look up.\n- A combination one query can\'t hold is refused by name. A note above the list names the filt'
     },
     {
         path: '/getting-started/console-tour',
@@ -6428,7 +6428,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'The console tour',
         heading: 'The Sites list',
         anchor: '#the-sites-list',
-        text: 'All Sites is the front door of a workspace: a table with one row per site, for the workspace currently selected in the switcher. A site you can reach in another organization isn\'t missing — it\'s behind the workspace switcher.\nEach row carries:\n- The site\'s display name, with its hostname underneath — the custom domain when the site has one, otherwise its name.aglyn.app address. Both are also columns of their own, Aglyn domain and Custom domain.\n- A status pill (below).\n- When the site was created and last updated.\n- Visit, which opens the live site in a new tab, and Manage, which opens that site\'s dashboard in the console.\nFilters in the table\'s toolbar narrows the list by name, Status (Live, Draft, Maintenance or Suspended), either domain, Custom domain status (Connected, Pending while a connect or disconnect is unfinished, or None), or the date a site was created or last updated. Search matches any word of the name, the slug, or either domain. Each filter in force shows as a chip above the table; remove a chip to drop it. The list holds every site you have in the workspace, so a filter or a search looks through all of them, not only the page on screen. The site count beside the heading always counts every site. See Filter and search a list.\nThe status pill {#the-status-pill}\n| Pill | Hover tells you |\n| Live (green) | How many pages are published — "12 published pages." |\n| Draft (gray outline) | "Nothing published yet — visitors see the placeholder." |\n| Maintenance (amber) | "Every path serves the maintenance screen." |\n| Suspended (red) | "This site is serving a lockdown notice instead of content." |\nLive means exactly one thing: the site has at least one published page. Publishing writes the routing map the site is served from, and the pill is read off that map — '
+        text: 'All Sites is the front door of a workspace: one card per site, for the workspace currently selected in the switcher, in name order. A site you can reach in another organization isn\'t missing — it\'s behind the workspace switcher.\nEach card carries:\n- The site\'s display name as the title, with its hostname underneath as the subheader — the custom domain when the site has one, otherwise its name.aglyn.app address. Both are also listed inside the card, as Aglyn Domain and Custom Domain.\n- A status pill (below).\n- Visit, which opens the live site in a new tab, and Manage, which opens that site\'s dashboard in the console.\nAbove the cards are a Search box and a Filters button — the same controls a table\'s toolbar has, over the cards. Search finds a site by the start of any word of its name, its slug (the name in name.aglyn.app) or its custom domain: harbor, bakery and shop.harbor all find Harbor Bakery at shop.harbor-bakery.com. Filters narrows the cards by Custom domain (Connected or None) and by the date a site was Created (on, before or after a day). Each filter in force shows as a chip above the cards; remove a chip to drop it. A filter on the created date lists the cards newest first.\nThe search and the filters are answered by the query that reads the cards, across every site you have in the workspace, not only the cards on screen. The cards come twelve at a time; Load more adds the next twelve that match. The site count beside the heading always counts every site. Status, plan, owner and the last-updated date are not filters: a site\'s status can change with no save at all (a timed suspension ends on its own), and a site doesn\'t store its plan, owner or template. See Filter and search a list.\nThe status pill {#the-status-pill}\n| Pill | Hover tells you |\n| Live (green) | H'
     },
     {
         path: '/getting-started/console-tour',
@@ -6673,7 +6673,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Commerce end to end',
         heading: '3. Design the storefront',
         anchor: '#3-design-the-storefront',
-        text: 'Open a screen in the Besigner and add blocks from the Commerce group of the element picker:\n- Product grid — a responsive catalog grid. Its Show property scopes it to all products, a collection, a category, or a tag; set Columns, Sort, a cap, and optional visitor-facing filter chips. Cards link to /products/{slug}.\n- Product detail — gallery, variant picker, price (with sale badge, trial caption, and /mo·/yr when subscribing), Add to cart, and the buy button (Buy now / Subscribe, or the one-time-vs-subscribe toggle for "Both" products). Leave its Product slug blank on a template screen so it follows the URL. The Product page preset drops the whole commerce-standard page in one go: a Shop / {{product.name}} breadcrumb, the detail block, a You may also like strip, and product reviews.\n- Cart — two presets: a Cart button (app-bar icon with an item-count badge and a slide-out drawer — the badge updates live as blocks add to the cart) and a Cart page (inline, with coupon and gift-card fields). Both end in a Checkout button.\nCatalog search, filters, and sort\nThe Product grid carries a toggle per storefront catalog control, so a bare strip on the home page and a full shop page are the same block:\n- Search box — a debounced search field above the grid; matches product names, descriptions, and tags.\n- Category chips — one chip per product category (plus All), built from the categories you manage in the Products hub. Visitors tap to filter.\n- Sort select — newest, name, price low→high, price high→low, right-aligned above the grid.\n- Type filter — physical / digital / services chips, useful for mixed catalogs.\n- Price filter — a two-thumb price range slider, automatically bounded by the lowest and highest prices among the products currently showing (variant-priced products count b'
+        text: 'Open a screen in the Besigner and add blocks from the Commerce group of the element picker:\n- Product grid — a responsive catalog grid. Its Show property scopes it to all products, a collection, a category, or a tag; set Columns, Sort, a cap, and optional visitor-facing filter chips. Cards link to /products/{slug}.\n- Product detail — gallery, variant picker, price (with sale badge, trial caption, and /mo·/yr when subscribing), Add to cart, and the buy button (Buy now / Subscribe, or the one-time-vs-subscribe toggle for "Both" products). Leave its Product slug blank on a template screen so it follows the URL. The Product page preset drops the whole commerce-standard page in one go: a Shop / {{product.name}} breadcrumb, the detail block, a You may also like strip, and product reviews.\n- Cart — two presets: a Cart button (app-bar icon with an item-count badge and a slide-out drawer — the badge updates live as blocks add to the cart) and a Cart page (inline, with coupon and gift-card fields). Both end in a Checkout button.\nCatalog search, filters, and sort\nThe Product grid carries a toggle per storefront catalog control, so a bare strip on the home page and a full shop page are the same block:\n- Search box — a debounced search field above the grid; matches the start of a word in a product\'s name ("cof" finds "Acme Coffee"), using the first word typed.\n- Category chips — one chip per product category (plus All), built from the categories you manage in the Products hub. Visitors tap to filter.\n- Sort select — newest, name, price low→high, price high→low, right-aligned above the grid.\n- Type filter — physical / digital / services chips, useful for mixed catalogs.\n- Price filter — a two-thumb price range slider, automatically bounded by the lowest and highest prices among the p'
     },
     {
         path: '/guides/commerce-end-to-end',
@@ -6799,7 +6799,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Install your first marketplace item',
         heading: 'Step 2 — Find something',
         anchor: '#step-2-browse',
-        text: 'Browse All is a grid of listing cards you can search, filter and sort. Cards are a catalog only — clicking one takes you to its detail page, which is the only place an install can happen. You cannot install by accident from the grid.\nTwo things on a card are worth reading before you click into one:\n- The price chip. Every card has one. A paid listing shows $29; a free one shows the word Free, rather than leaving the corner empty for you to interpret.\n- The stars, and the number beside them. 4.8 (12) is twelve people\'s opinion; 5.0 (1) is one person\'s. A listing nobody has rated says Not yet rated instead of showing no stars.\nOn the detail page, read three things before anything else:\n1. The What\'s included box. Aglyn writes it from the listing itself, not the publisher, so it is the one description that cannot oversell. Its first row names what the install produces — a sandboxed plugin, an editable component, screens you rework in Besigner, a theme, or a new empty dataset with its fields already defined for a dataset schema, which is the reminder that records never travel: you get the shape, not somebody\'s data. The rows after it cover where it lands (step 4), review, license and updates. See What\'s included for every row it can produce.\n2. The badges. They make two different claims, and it\'s worth knowing which is which — see what the badges mean.\n3. The price. The header repeats the card\'s chip — $29, or Free — and the button spells out what pressing it does: a paid listing reads Buy for $29 rather than Install. Buying is one payment; the listing\'s updates are included in it.'
+        text: 'Browse All is a grid of listing cards you can search, filter and sort. Cards are a catalog only — clicking one takes you to its detail page, which is the only place an install can happen. You cannot install by accident from the grid.\nThe controls answer over the whole marketplace, not the cards already on screen:\n- Search components finds a listing by a word of its name. It matches one word at a time, from the start of the word (count finds Promo Countdown).\n- The category chips show one category\'s listings; click the chip again to clear it.\n- The sort menu orders by Newest, Most installed or Highest rated (listings nobody has rated come last).\nThe grid pages at the bottom. Your own organization\'s listings still waiting on review appear here too, so you can watch a submission move through review.\nTwo things on a card are worth reading before you click into one:\n- The price chip. Every card has one. A paid listing shows $29; a free one shows the word Free, rather than leaving the corner empty for you to interpret.\n- The stars, and the number beside them. 4.8 (12) is twelve people\'s opinion; 5.0 (1) is one person\'s. A listing nobody has rated says Not yet rated instead of showing no stars.\nOn the detail page, read three things before anything else:\n1. The What\'s included box. Aglyn writes it from the listing itself, not the publisher, so it is the one description that cannot oversell. Its first row names what the install produces — a sandboxed plugin, an editable component, screens you rework in Besigner, a theme, or a new empty dataset with its fields already defined for a dataset schema, which is the reminder that records never travel: you get the shape, not somebody\'s data. The rows after it cover where it lands (step 4), review, license and updates. See What\'s include'
     },
     {
         path: '/guides/install-your-first-plugin',
@@ -6960,7 +6960,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Member accounts',
         heading: '5. Manage members from the console',
         anchor: '#5-manage-members-from-the-console',
-        text: 'The site\'s Users page has two cards: Site users (your members — this guide) and Users (console collaborators). The Site users card is paged, newest first, with Email, Name, Joined, and Status columns, and no search box — filter by email instead. Filters in the table\'s toolbar narrows it by email, name, or join date, one filter at a time, across every member rather than the page on screen. Status (Active or Suspended) is a filter too, and it combines with any one of the others — suspended members whose email starts with a given address, say. Each filter in force shows as a chip above the table; see Filter and search a list. For members who may open the CRM, each row\'s ⋮ menu holds Open in CRM — the member\'s contact, found by the address they signed up with.\nClick a member to open the member drawer:\n- Profile — email, display name, and join date, with a Suspended chip when applicable.\n- Lifetime purchases — charged order totals minus refunds (pending and canceled orders excluded).\n- Orders — the member\'s payment history, newest first: order number, status, total, date, any refunded amount, and the Stripe payment reference. Needs the editor or admin role on the site.\n- Subscriptions — each with its renewal date and status chip.\n- Addresses — the member\'s saved addresses.\nSuspend & reactivate\nThe drawer\'s action button flips between Suspend member and Reactivate member, each behind a confirmation:\n- Suspend — the member can no longer sign in on the published site (they see an "account suspended" message), and their account page signs out on its next load. Orders, subscriptions, and history are all kept.\n- Reactivate — restores access with the member\'s existing password.\nBoth actions are recorded in the site\'s activity log.\nPassword help\nThe drawer\'s Password section gets a '
+        text: 'The site\'s Users page has two cards: Site users (your members — this guide) and Users (console collaborators). The Site users card is paged, newest first, with Email, Name, Joined, and Status columns. Its search box finds a member by the start of any word of their name or their email address — rae, donovan or example.com all find Rae Donovan at rae@example.com, and a member who never gave a name is found by their address. Filters in the table\'s toolbar narrows it by Email (the whole address), Name (a word of it, or the whole name), Joined (on a day, or before or after a date) and Status (Active or Suspended). The filters and the search add up, and every one is answered by the query that reads the list, across every member rather than the page on screen. Name contains and the search each look for one word, and one query can look for only one: while a search is typed, a Name-contains filter is not applied, and a notice above the table says so. Each filter in force shows as a chip above the table; see Filter and search a list. For members who may open the CRM, each row\'s ⋮ menu holds Open in CRM — the member\'s contact, found by the address they signed up with.\nClick a member to open the member drawer:\n- Profile — email, display name, and join date, with a Suspended chip when applicable.\n- Lifetime purchases — charged order totals minus refunds (pending and canceled orders excluded).\n- Orders — the member\'s payment history, newest first: order number, status, total, date, any refunded amount, and the Stripe payment reference. Needs the editor or admin role on the site.\n- Subscriptions — each with its renewal date and status chip.\n- Addresses — the member\'s saved addresses.\nSuspend & reactivate\nThe drawer\'s action button flips between Suspend member and Reactivate member, ea'
     },
     {
         path: '/guides/member-accounts',
@@ -7373,7 +7373,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Designed emails',
         heading: 'Find a template',
         anchor: '#find-a-template',
-        text: 'The templates table filters through its toolbar by name and Origin (yours, or installed from a listing), and Search matches any word of a template\'s name. On your organization\'s Emails page it also filters by Site, and Search matches site names too. The filters look at every template the table read, not only the page on screen. A site\'s own table reads its first 200 screens of every kind and lists the email templates among them; the organization\'s table reads up to 50 templates from each site on the page of sites it shows, and its Site filter offers those sites. Where a site holds more than the table reads, the note under it says so. See Filter and search a list.'
+        text: 'The templates table filters through its toolbar by name (it contains a word, it is, or it starts with), and Search matches the start of any word of a template\'s name, up to its first twelve characters. The filters and the search are asked of the site\'s templates themselves, so they reach every template the site holds, a page at a time in name order, not only the page on screen. A name that contains a word and Search both match words of the name, so only one of them applies at a time; a note above the table says which was set aside. The Origin column shows whether a template is yours or installed from a listing, but it is not a filter.\nOn your organization\'s Emails page the same filters and search run on each site\'s templates, and Site chooses which sites are read: any of your sites, wherever it sits in the pages of sites. Without it, the table reads the page of sites the Sites picker shows. It lists up to 50 matching templates from each site; where a site has more, the note under the table says so and links to that site\'s own list. See Filter and search a list.'
     },
     {
         path: '/marketing-and-automation/email-campaigns/designed-emails',
@@ -7492,14 +7492,14 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Email Campaigns',
         heading: 'Email lists',
         anchor: '#email-lists',
-        text: 'Lists are audiences shared across your organization\'s sites. Create them on the Marketing page and target any of them from the campaign composer. A list is one of two kinds, chosen when you create it.\nThe lists table filters through its toolbar: Filters narrows it by name or by Membership (manual or rule), and Search matches any word of a list\'s name. The table is paged, so the first filter reads the first 100 lists and matches over them; the table says when there are more, and paging forward reads the next page. See Filter and search a list.\nManual lists\nA manual list holds the people you put in it. Grow it with the "Enroll in a list" automation step (e.g. on form completion), popup email capture, the Add to a list card in the Inbox, or by hand from the list itself. Members stay until they are removed.\nSee and manage who is on a list {#list-members}\nPress Members on any list row to open it. You get the membership a page at a time — address, name, when they joined, how they got there, and what their consent record says — plus the controls to change it. Press Close to collapse it again; nothing is read until you open a list.\nHow tells a rule match apart from somebody who was added. A person a rule enrolled leaves when they stop matching; a person who was added stays.\nThe membership table filters through its toolbar by address, name, How (rule or added) and Consent (each of the kinds below), and Search matches an address, name or source. Like the lists table, it filters over the first 100 members it read and says when there are more; see Filter and search a list. The address and name boxes above the table add people; they are not filters.\nConsent is the basis the membership carries, read for the site you are on — or, on your organization\'s Emails page, for the site chosen'
+        text: 'Lists are audiences shared across your organization\'s sites. Create them on the Marketing page and target any of them from the campaign composer. A list is one of two kinds, chosen when you create it.\nThe lists table filters through its toolbar: Filters narrows it by name (it contains a word, or it is) or by Membership (manual or rule), and Search matches the start of any word of a list\'s name. The filters and the search are asked of your organization\'s lists themselves, so they reach every list, a page at a time in name order. A name that contains a word and Search both match words of the name, so only one of them applies at a time, and a note above the table says which was set aside. See Filter and search a list.\nManual lists\nA manual list holds the people you put in it. Grow it with the "Enroll in a list" automation step (e.g. on form completion), popup email capture, the Add to a list card in the Inbox, or by hand from the list itself. Members stay until they are removed.\nSee and manage who is on a list {#list-members}\nPress Members on any list row to open it. You get the membership a page at a time — address, name, when they joined, how they got there, and what their consent record says — plus the controls to change it. Press Close to collapse it again; nothing is read until you open a list.\nHow tells a rule match apart from somebody who was added. A person a rule enrolled leaves when they stop matching; a person who was added stays.\nThe membership table filters through its toolbar by Address (the whole address) and How (rule or added), and Search matches the start of any word of a member\'s name or of any part of their address: the local part, a piece of it such as doe in jane.doe, or the domain, with or without the @, up to the first twelve characters typed. The f'
     },
     {
         path: '/marketing-and-automation/email-campaigns/overview',
         title: 'Email Campaigns',
         heading: 'Experiments',
         anchor: '#experiments',
-        text: 'Business plans can A/B test screens, sections, and emails from the Experiments card on the Marketing page: weighted variants, deterministic visitor assignment, a conversion goal, and per-variant exposure/conversion rates with a pick-the-winner flow.\nTwo ways to finish a test without watching it:\n- End date — past it, visitors get the default and stats stop accruing until you pick a winner.\n- Auto-declare winner — opt in with a minimum exposure count per variant and a confidence level (90/95/99%); once a challenger clears the bar (or every challenger confidently loses to the control), the experiment completes itself and serves the winner. Auto-completed tests carry a chip in the results dialog.\n- Screens & sections — variants pin a screen version; visitors are split deterministically and the winning version serves to everyone once you pick it. Start a section test straight from the Besigner\'s Interactions panel.\n- Emails — variants override the campaign\'s subject and/or body. Attach a running email experiment in the campaign composer; each recipient deterministically receives one variant (re-sends reach the same variant), sends count as exposures, and once a winner is picked every later send uses the winning copy.\nThe Experiments table filters through its toolbar by name, what it tests (screen, section or email) and status, and Search matches any word of an experiment\'s name. The list is paged, so the first filter or search reads the first 100 experiments and matches over them; the table says when there are more, and paging forward reads the next page. See Filter and search a list.\nAcross your organization\'s sites {#experiments-across-sites}\nYour organization\'s own Marketing → A/B testing lists every site\'s tests, grouped by site, with what each one tests, how many varia'
+        text: 'Business plans can A/B test screens, sections, and emails from the Experiments card on the Marketing page: weighted variants, deterministic visitor assignment, a conversion goal, and per-variant exposure/conversion rates with a pick-the-winner flow.\nTwo ways to finish a test without watching it:\n- End date — past it, visitors get the default and stats stop accruing until you pick a winner.\n- Auto-declare winner — opt in with a minimum exposure count per variant and a confidence level (90/95/99%); once a challenger clears the bar (or every challenger confidently loses to the control), the experiment completes itself and serves the winner. Auto-completed tests carry a chip in the results dialog.\n- Screens & sections — variants pin a screen version; visitors are split deterministically and the winning version serves to everyone once you pick it. Start a section test straight from the Besigner\'s Interactions panel.\n- Emails — variants override the campaign\'s subject and/or body. Attach a running email experiment in the campaign composer; each recipient deterministically receives one variant (re-sends reach the same variant), sends count as exposures, and once a winner is picked every later send uses the winning copy.\nThe Experiments table filters through its toolbar by Experiment (a name that contains a word, or is exactly a name in either case), Tests (screen, section or email) and Status (draft, running, paused or done; one or several of each). Search finds an experiment by the start of any word in its name: cop finds Hero copy. Every filter and the search are answered by the query, across all of the site\'s experiments, a page at a time and in name order, not only over the page on screen. A combination the query cannot answer together is not applied, and a notice above th'
     },
     {
         path: '/marketing-and-automation/email-campaigns/overview',
@@ -7618,7 +7618,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Actions builder',
         heading: 'Run history',
         anchor: '#run-history',
-        text: 'Every automation row has a Runs button. It opens Runs — your automation with a Recent runs table of that one automation\'s executions, in four columns:\n| Column | What\'s in it |\n| Time | The clock time of the run; hover it for the full date and time. |\n| Trigger | The event, in words — formSubmission shows as Form submitted. A custom event keeps the name you gave it. |\n| Result | Succeeded, Failed, or Skipped. |\n| What happened | For a run, what each step did, joined with ·. For a failure, the errors. For a skip, which condition stopped it. |\nThe table\'s toolbar narrows it. Filters offers Trigger and Result as picked values, Time by day, and What happened as typed text; Search finds words in the trigger or in what happened. Both reach every run the table read — the runs among the 200 most recent activity entries this automation wrote — not only the page on screen, and each filter in force shows as a chip above the table. When the automation has written more than that, a note under the table says so. See Filter and search a list.\nSkipped is a result, not an absence — see Only run when a field matches. A run that fired but whose steps errored is Failed, and the errors are in the last column rather than in a log you have to go and find.\nAt the top of the Actions tab — and again on the Workflows tab, counting workflow runs — a line reads 1,284 action runs this month · 50,000 included: how many metered runs this site has used this calendar month, against the number your plan includes. This line is the only place action runs are counted for you — the billing usage meters meter workflow runs, not action runs. Watch it: once the month\'s runs reach the limit, triggered automations stop running rather than queueing or billing on. The line renders nothing at all while the counter o'
+        text: 'Every automation row has a Runs button. It opens Runs — your automation with a Recent runs table of that one automation\'s executions, in four columns:\n| Column | What\'s in it |\n| Time | The clock time of the run; hover it for the full date and time. |\n| Trigger | The event, in words — formSubmission shows as Form submitted. A custom event keeps the name you gave it. |\n| Result | Succeeded, Failed, or Skipped. |\n| What happened | For a run, what each step did, joined with ·. For a failure, the errors. For a skip, which condition stopped it. |\nThe table\'s toolbar narrows it. Filters offers Trigger and Result as picked values (is or is any of) and Time by day (is, after, on or after, before, on or before); Search finds a word at the start of any word in What happened. Every filter and the search are asked of the whole history, however far back it goes, and the table pages through the matches newest first, so a run from months ago is found as readily as one from this morning. Each filter in force shows as a chip above the table. Search and filters combine; a combination the history can\'t answer at once is named above the table and not applied, rather than applied to some runs and not others. See Filter and search a list.\nSkipped is a result, not an absence — see Only run when a field matches. A run that fired but whose steps errored is Failed, and the errors are in the last column rather than in a log you have to go and find.\nAt the top of the Actions tab — and again on the Workflows tab, counting workflow runs — a line reads 1,284 action runs this month · 50,000 included: how many metered runs this site has used this calendar month, against the number your plan includes. This line is the only place action runs are counted for you — the billing usage meters meter workflow r'
     },
     {
         path: '/marketing-and-automation/workflows-and-actions/actions-builder',
@@ -8388,7 +8388,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Invite teammates',
         heading: 'Activity log',
         anchor: '#activity-log',
-        text: 'The organization\'s Team page shows a Recent Activity log: what happened at organization level — renames, workspace URL changes, ownership transfers, members added/removed or re-roled, and invites sent, revoked, or accepted — together with the changes made on each of the organization\'s sites, newest first, each with who did it, where and when.\nVisible to members whose role carries the Activity & audit log permission. Owners and admins have it by default; viewers do not, and neither does a custom role until you grant it. Revoking it does not merely hide the card — the feed is served by an API that checks the permission, so a member without it cannot read the log by any route.\nEntries name the thing that changed and link straight to it, so "Saved the screen — Home" takes you to that screen. Entries recorded before this shipped show a plain description instead of a link.\nThe log filters through its table\'s toolbar, across the whole log rather than the page on screen:\n- Filters narrows it by Action — picked from the actions the log records as named entries, such as the AI entries below — by Who (one of the organization\'s members), by Where (the organization itself or one of its sites), and by When (before or after a date). They add up, and every one is answered by the log\'s own query.\n- Search matches the address of the person who made the change and the name of what changed. It reads the log as it goes, up to 250 entries a page, so a page of results can come back short; Next carries on from where it stopped.\nChanging a filter or the search starts the log again at its first page. See Filter and search a list.\nA site\'s own activity log, on its Setup page, filters through its table\'s toolbar: Filters narrows it to one Action (or several, with is any of) — typed as the action i'
+        text: 'The organization\'s Team page shows a Recent Activity log: what happened at organization level — renames, workspace URL changes, ownership transfers, members added/removed or re-roled, and invites sent, revoked, or accepted — together with the changes made on each of the organization\'s sites, newest first, each with who did it, where and when.\nVisible to members whose role carries the Activity & audit log permission. Owners and admins have it by default; viewers do not, and neither does a custom role until you grant it. Revoking it does not merely hide the card — the feed is served by an API that checks the permission, so a member without it cannot read the log by any route.\nEntries name the thing that changed and link straight to it, so "Saved the screen — Home" takes you to that screen. Entries recorded before this shipped show a plain description instead of a link.\nThe log filters through its table\'s toolbar, across the whole log rather than the page on screen:\n- Filters narrows it by Action — picked from the actions the log records as named entries, such as the AI entries below — by Who (one of the organization\'s members), by Where (the organization itself or one of its sites), and by When (on a day, or before or after a date). They add up, and every one is answered by the log\'s own query.\n- Search finds an entry by the start of a word of the address of the person who made the change (or the API key\'s name, for an entry an integration wrote) and of the name of what changed — ada, example.com or home — across the whole log. It matches one word at a time: type two and the log says it searched the first.\nEvery filter and the search are on the log\'s own query. Anything that query cannot take is not applied, and a notice above the table names it.\nChanging a filter or the '
     },
     {
         path: '/workspace-and-billing/teams-and-roles/invite-teammates',
@@ -8444,7 +8444,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Members-only areas',
         heading: 'Manage your members',
         anchor: '#manage-your-members',
-        text: 'The site\'s Users page lists everyone who signed up on your published site — paged, newest first. Filters in the table\'s toolbar narrows the list by email, name or join date, one at a time, and by Status (Active or Suspended) beside any one of them, across every member rather than the page on screen; the table has no search box. See Filter and search a list. Click a member to open their detail drawer:\n- Profile — email, display name, join date, and saved addresses.\n- Order history — the member\'s payment records, newest first: order number, status, total, and date, plus the Stripe payment reference and any refunded amount. Order history is visible to site admins and editors.\n- Subscriptions — active and past storefront subscriptions with their renewal date.\n- Lifetime purchases — everything the member actually paid: charged order totals minus refunds (pending and canceled orders don\'t count).\nSuspend or reactivate a member\nFrom the drawer you can suspend a member (with a confirmation). A suspended member:\n- can no longer sign in on your published site — they see a clear "account suspended" message;\n- is signed out the next time their account page loads;\n- keeps all orders, subscriptions, and history — nothing is deleted.\nReactivate restores access with the member\'s existing password. The member list shows each account\'s Active/Suspended status at a glance.'
+        text: 'The site\'s Users page lists everyone who signed up on your published site — paged, newest first. The search box finds a member by the start of any word of their name or email address, and Filters in the table\'s toolbar narrows the list by email, name, join date or Status (Active or Suspended). They add up, across every member rather than the page on screen, because the query that reads the list answers them all. See Filter and search a list. Click a member to open their detail drawer:\n- Profile — email, display name, join date, and saved addresses.\n- Order history — the member\'s payment records, newest first: order number, status, total, and date, plus the Stripe payment reference and any refunded amount. Order history is visible to site admins and editors.\n- Subscriptions — active and past storefront subscriptions with their renewal date.\n- Lifetime purchases — everything the member actually paid: charged order totals minus refunds (pending and canceled orders don\'t count).\nSuspend or reactivate a member\nFrom the drawer you can suspend a member (with a confirmation). A suspended member:\n- can no longer sign in on your published site — they see a clear "account suspended" message;\n- is signed out the next time their account page loads;\n- keeps all orders, subscriptions, and history — nothing is deleted.\nReactivate restores access with the member\'s existing password. The member list shows each account\'s Active/Suspended status at a glance.'
     },
     {
         path: '/workspace-and-billing/teams-and-roles/members-only',
@@ -8465,7 +8465,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Teams, Roles & Membership',
         heading: '',
         anchor: '',
-        text: 'Teams, Roles & Membership\nAglyn has two kinds of people: your team (who build and manage the site) and site members (visitors who sign up to your site). Both are permission-aware.\nPlan availability Paid. Seats are metered per tier; see Billing & plans.\nThe Team page\'s roster filters through its table\'s toolbar: Filters narrows it by Member (the name), Role or Access (team manager or site collaborator), and Search matches any word of a member\'s name, email, or title. Both look at the whole roster, not only the page on screen, and each filter in force shows as a chip above the table; see Filter and search a list. The role pickers and Permissions in each row work as before.'
+        text: 'Teams, Roles & Membership\nAglyn has two kinds of people: your team (who build and manage the site) and site members (visitors who sign up to your site). Both are permission-aware.\nPlan availability Paid. Seats are metered per tier; see Billing & plans.\nThe Team page\'s roster filters through its table\'s toolbar: Filters narrows it by Role (one role, or several at once) or Access (team manager or site collaborator), and Search finds a member by the start of any word of their name, email address or job title — ada, lovelace or example.com all find Ada Lovelace at ada@example.com. The filters and the search add up, and they are answered by the query that reads the roster, so the table lists every member who matches, not a narrowing of the rows already on screen. Each filter in force shows as a chip above the table; see Filter and search a list. The role pickers and Permissions in each row work as before.'
     },
     {
         path: '/workspace-and-billing/teams-and-roles/overview',