@burdenoff/website-sdk 2026.1026.1 → 2026.1027.1

package/README.md

@@ -159,7 +159,9 @@ function Header() {
 |---|---|---|
 | `seo` | – | Renders `PageHead` with these overrides. Omit to manage `<head>` yourself. |
 | `productSlug` | – | The site this page is on. A soft hint to the assistant, not a hard filter. |
-| `examplePrompts` | – | Prompt chips used only when the backend catalog supplies none. |
+| `examplePrompts` | – | Prompt chips used only when the backend catalog supplies none. With `scope="product"` they are the only prompts shown, whatever the catalog has. |
+| `scope` | `'portfolio'` | `'product'` (with `productSlug`) makes the assistant one product's own. See [One product's own assistant](#one-products-own-assistant). |
+| `productName` | catalog name | The product's display name in the `product` scope. Default: the catalog's name for `productSlug`. |
 | `className` | – | Extra classes on the page root. |
 | `heightMode` | `'viewport'` | `viewport` pins the chat to the screen with an internally scrolling transcript, and is the only mode in which the component manages the host page's scroll position; `auto` lets the page grow and never touches its host's scrolling (for embedding). |
 | `viewportOffset` | `0` | Chrome to subtract in `viewport` mode, **before the first measurement only**. A number is pixels; a string is any CSS length (`'4rem'`). Once mounted the pane measures its own top and this value stops being used — so an approximate header height is fine, and the on-screen keyboard is handled for you. |
@@ -167,6 +169,80 @@ function Header() {
 | `onSend` | – | Fired with the message text each time a send is accepted (analytics). |
 | `welcomeTitle` / `welcomeBody` | catalog values | Override the welcome copy. `welcomeTitle` **is** the page `<h1>`. |
 
+#### One product's own assistant
+
+By default the assistant speaks for the whole portfolio: a "Focus on a product"
+picker lists every product, concept cards come from every product, and the
+catalog's copy invites comparing products. A product site that wants its
+assistant to be about that product alone passes `scope="product"` with its
+`productSlug`, on `ExplorePage`, on the site-wide `ExplorePanel`, or on both.
+`ExplorePanel` takes the same `scope`, `productName` and `examplePrompts` props
+and passes them to its chat.
+
+```tsx
+<ExplorePanel
+  open={open}
+  onOpenChange={setOpen}
+  productSlug="healthybowl"
+  scope="product"
+  productName="Healthy Bowl" // the panel is titled "Healthy Bowl assistant"
+  examplePrompts={[
+    "Our herd's health records are spread across three notebooks.",
+    'We only find out a field needs water once the crop is stressed.',
+  ]}
+/>
+```
+
+In that scope:
+
+- The panel's title is "{product} assistant", in the visitor's language and its
+  word order, named from `productName`, else from the catalog. Where a phone
+  leaves it too little room beside the tabs, it wraps to two lines, and the
+  header keeps its height. In English and most locales two lines hold the whole
+  title at 320px and wider; a narrower title box, such as Tamil's at 320px (its
+  tabs are wider), can still end the second line with an ellipsis.
+- There is no product picker. Every question is asked about this product, also
+  in a conversation that was stored, reopened or shared with another focus; the
+  request carries `productSlug` as it always has.
+- Only this product's concept cards show, and none at all when it has none.
+- The example prompts are your `examplePrompts` and nothing else (each once,
+  blank ones dropped), whatever the catalog has. Only when you pass none does it
+  fall back to the catalog's, without any that name another product and without
+  the built-in "Which of your products fits a problem like mine?". Pass your
+  own: the catalog's are written for every site at once, and even the ones that
+  name no product describe other sites' problems. Pass them to the
+  product-scoped view itself (`ExplorePanel` or `ExplorePage`): an
+  `ExploreChatProvider`'s own `examplePrompts` only stand in until the catalog
+  loads.
+- Unless you pass `welcomeBody`, the welcome invites the visitor to describe a
+  problem or ask what the product does, instead of the catalog's invitation to
+  compare products. A catalog title that names another product is replaced by
+  the built-in one. The welcome's "Compare across the ecosystem" tile is left
+  out.
+- The composer is the published one, unchanged: the same layout, the same size
+  and the same fit to its draft. Only its placeholder's text is shorter, "Ask
+  about {product}…" instead of "Describe a problem, or ask about {product}…",
+  because on a phone the field stays one line tall and cuts off a placeholder
+  that wraps. The English one fits that line at 320px and wider. Some longer
+  locales, such as Spanish and Tamil, may still wrap at 320px and narrower; that
+  is left for a follow-up, and HealthyBowl, the site this was made for, is
+  English-only.
+- The page's meta description (and its `og:` and `twitter:` copies) is the
+  product's own, "Answers about {product}, drawn from {product}'s
+  documentation…", never "and every other product we build". The title and
+  `og:site_name` name the product already.
+- A question that needs more searches than one answer can make (`TOOL_BUDGET`)
+  is asked to be narrowed to one part of it, in the visitor's language, instead
+  of to "two or three specific products".
+
+Answers still come from the backend unchanged: when a visitor asks about
+another product, the answer and its sources can mention it. Each view applies
+its own scope, so under an `ExploreChatProvider` a portfolio `/explore` page and
+a product-scoped panel still share one conversation. Without a `productSlug`,
+`scope="product"` has no product to pin to and behaves like the default (a
+development build logs a warning). The default, `scope="portfolio"`, renders
+exactly what it always has.
+
 **`ExploreCta` props**: `variant` (`'header' \| 'mobile' \| 'floating'`, required),
 `href` (default `/explore`), `label` (default `Ask AI`), `className`,
 `onNavigate`, `onClick`, `currentPath`. The `floating` variant hides itself on

package/dist/components/explore.d.mts

@@ -1,4 +1,4 @@
 import 'react';
-export { E as EXPLORE_PREFILL_MAX_LENGTH, d as ExplorePage, e as ExplorePageProps, l as ExploreProvenance, m as ExploreReferenceKind, f as answerPlainText, g as answerSpeechText, h as exploreQuestionHref, i as inlineImageOrigins, j as isInlineImageAllowed, k as isInlineVideoAllowed, n as logoUrlOf, o as productNamesByOrigin, r as referenceKindOf, s as summariseReferences } from '../explore-BRfKFfvI.mjs';
+export { a as EXPLORE_PREFILL_MAX_LENGTH, e as ExplorePage, f as ExplorePageProps, m as ExploreProvenance, n as ExploreReferenceKind, g as answerPlainText, h as answerSpeechText, i as exploreQuestionHref, j as inlineImageOrigins, k as isInlineImageAllowed, l as isInlineVideoAllowed, o as logoUrlOf, q as productNamesByOrigin, r as referenceKindOf, s as summariseReferences } from '../explore-BEgq1_0O.mjs';
 import '../explore-types-_9UJu6EA.mjs';
 import 'react-markdown';

package/dist/components/explore.d.ts

@@ -1,4 +1,4 @@
 import 'react';
-export { E as EXPLORE_PREFILL_MAX_LENGTH, d as ExplorePage, e as ExplorePageProps, l as ExploreProvenance, m as ExploreReferenceKind, f as answerPlainText, g as answerSpeechText, h as exploreQuestionHref, i as inlineImageOrigins, j as isInlineImageAllowed, k as isInlineVideoAllowed, n as logoUrlOf, o as productNamesByOrigin, r as referenceKindOf, s as summariseReferences } from '../explore-DkfcKgp6.js';
+export { a as EXPLORE_PREFILL_MAX_LENGTH, e as ExplorePage, f as ExplorePageProps, m as ExploreProvenance, n as ExploreReferenceKind, g as answerPlainText, h as answerSpeechText, i as exploreQuestionHref, j as inlineImageOrigins, k as isInlineImageAllowed, l as isInlineVideoAllowed, o as logoUrlOf, q as productNamesByOrigin, r as referenceKindOf, s as summariseReferences } from '../explore-CHiP9u-4.js';
 import '../explore-types-_9UJu6EA.js';
 import 'react-markdown';