' source/**/*.md`. A genuine addition
+ is referenced from at least one page; an asset added to `source/` but referenced nowhere is
+ an orphan and moves no count at all.
+4. Check the delta is accounted for exactly: one new page reference to a new distinct asset
+ should move `references`, `copySet` and `mapEntries` by the same amount, in the same
+ direction, for a reason that traces to the named file; a reference to an asset already in
+ the corpus moves only `references`. A removed page's assets move the counts down the same
+ way.
+5. **The signal that a count moved for a real reason is that every count it touches moves
+ together in a way the named file explains.** A single count moving alone, or a count moving
+ by an amount the named change does not account for, is not a legitimate content change —
+ treat it as a transform defect and debug it as one, per this file's standing rule not to
+ adjust an expectation to match a broken run.
+6. Once steps 1–5 establish the change is genuine, update the specific `EXPECTED` value(s) in
+ `scripts/assets.mjs` and/or `scripts/convert.mjs`, and **record the change in this file**:
+ which count, old value, new value, the asset name, the page(s) referencing it, and the
+ evidence from steps 2–4. A human signs off on that entry before the updated expectation is
+ committed — this is not a change a script makes to itself.
+
+This is deliberately conservative under time pressure: on cutover day, the fast path (assume
+legitimate, bump the number) and the correct path (name the file, prove the delta) look
+identical from the failing output alone. Steps 1–4 are the difference, and they cost one
+`grep` and one `ls` against the cost of shipping a broken build, or worse, adjusting an
+expectation to hide one.
+
+### Concerns
+
+None blocking. The `{% file %}` coincidental-match gap and the `EXPECTED.images` no-map fallback
+caveat are both structurally sound today and both explicitly logged above so a future GitBook
+sync that changes shape fails loudly rather than silently.
+
+## 2026-07-30 — Phase 4 gate: look and feel complete
+
+Scope was widened at the outset, on Pat's decision: the six measured items in the Phase 2
+and Phase 3 handoffs **plus** the chrome items in `MIGRATION-BRIEF.md`'s Phase 4 section,
+which are additive to those handoffs rather than superseded by them.
+
+### Gate evidence
+
+- `astro build` green, 205 pages.
+- `node scripts/routes.mjs` — route parity OK, 204 live sitemap URLs, 0 unreachable.
+- 231 unit tests pass (up from 187).
+- `npm run convert` byte-identical across consecutive runs.
+- Deployed to `opendialog-docs.opendialog.workers.dev`; a 30-route sample all served 200 on
+ the first poll.
+- No horizontal overflow at 375, 768, 1024, 1440 or 1920.
+
+### The defect underneath several others: cascade layer order
+
+`custom.css` opened `@layer starlight.core { … }`, and Astro bundles `customCss` ahead of
+Starlight's own stylesheets. A layer's priority is fixed by where it **first appears**, so
+`starlight.core` registered first and became the **lowest**-priority layer — beneath
+`starlight.reset`, whose `* { margin: 0 }` then beat every margin Starlight sets in `core`.
+Measured in the bundle: first `@layer starlight.core{` at byte 2,086, Starlight's own layers
+not until 38,915. Starlight's intended order, from `style/layers.css`, is
+`base, reset, core, content, components, utils`.
+
+This had been true since Phase 1 and was **not** cosmetic-only. It silently disabled:
+
+- the search dialog's `margin: 4rem auto auto`, which is why the modal opened pinned to the
+ top-left corner rather than centred;
+- `PageTitle.astro`'s `h1` and `.page-description` margins — dead since Phase 1;
+- Starlight's own `.title-wrapper` negative margin, which is why the logo sat 4px right of
+ the sidebar edge;
+- `.sl-container > * + *`'s 1.5rem rhythm between content blocks.
+
+Fixed by restating the canonical order as the first statement in `custom.css`. **That
+statement must stay first in the file.** Lightning CSS strips the bare `@layer` statement
+from the bundle but physically reorders the layer blocks to match it, which is what makes
+the fix work — verified by reading the built CSS, not assumed.
+
+Consequence for anyone editing `custom.css`: `starlight.core` is *below* `starlight.content`
+and `starlight.components`. A rule that must beat Starlight's markdown or component styling
+has to sit **outside** `@layer` — several rules here deliberately do, and say so.
+
+### Corrections to earlier entries in this file
+
+- **The brand-token font row (line ~168) is wrong.** It records "Inter (body), Fragment Mono
+ (code)" as taken from `opendialog.ai`. Measured today, the marketing site loads **Sofia
+ Pro** and no Inter at all; the note was written a day earlier, so the site is very unlikely
+ to have changed under it. More importantly the docs site being replaced serves **Poppins**
+ and **IBM Plex Mono**, which is what the migrated site now serves. This is the same
+ unverified-claim shape as the ffmpeg entry the Phase 4 prompt warns about.
+- **`scripts/sidebar.mjs`'s "nav entries" counter and its comment were stale** the moment the
+ Sidebar override landed: a parent page is no longer two rows. It now reports
+ `data entries: 245 (41 parent pages counted twice)` and `rendered rows: 204`.
+- **`reference/` holds no visual snapshots.** The Phase 4 prompt's definition of done says to
+ verify "against the `reference/` snapshots"; that directory contains only `llms.txt`,
+ `sitemap.xml` and `sitemap-pages.xml`, and `screenshots/` is git-ignored. All visual
+ comparison in this phase was made against the live GitBook site, which is still up. **There
+ is still no committed visual oracle that outlives GitBook.**
+
+### What changed
+
+**Typography.** Poppins and IBM Plex Mono, self-hosted via Fontsource (OFL-1.1), latin
+subset only — the corpus's 27 non-ASCII codepoints are all inside latin's range or emoji that
+fall back to the system face. Zero external font requests preserved. Heading scale matched to
+GitBook exactly: h1 36/700/45/−0.9, h2 30/600/36/−0.375, h3 24/600/32/−0.3, h4
+20/600/28/−0.25. `--sl-text-h5` deliberately untouched: `asides.css` uses it for the aside
+title and 258 hint blocks depend on it.
+
+**Header.** Site title 18px/600/−0.025em near-black with a 32px logo, against Starlight's
+24px brand blue. `opendialog.ai` and the "Talk to an expert" CTA carried across from GitBook
+with their real hrefs; the three social icons GitBook does not have are gone. Search moved to
+the right of the CTA, as GitBook orders it — that needed a full `Header` override, not the
+`SocialIcons` override first assumed, because Starlight puts search in a middle column.
+
+**Page shell.** GitBook constrains its layout to a 1440px box centred in the viewport with
+32px inner padding while the header band stays full-bleed. One inset variable now drives the
+header padding, the fixed sidebar and the main frame together.
+
+**Light-only.** The live GitBook site is light-only — hard-coded `light` on ``, no
+switcher, no theme key in storage. `ThemeProvider` pins light and ignores a stored `dark`
+preference, so anyone who chose dark on the preview still gets light. Dark tokens stay in
+`custom.css`, so it is one file to undo. **Caveat: the pin is an inline script, so with
+JavaScript disabled the page falls back to Starlight's `:root` default, which is dark.**
+Fixing that properly needs `data-theme` on the server-rendered ``, i.e. a `Page`
+override.
+
+**Breadcrumb.** The ancestor-group chain, section down to immediate parent, excluding the
+page. GitBook links its top-level crumb to paths like `/core-concepts`, which are **not
+pages** — it 307-redirects them to the section's first page, and they appear in neither the
+live sitemap nor `route-map.json`. The crumb points straight at the redirect target instead:
+same destination, no hop, no route invented. **All 636 breadcrumb links across 204 pages
+resolve to a real route.** A section is a structural bucket and never a page, so its crumb
+always shows; where the section's first page *is* the current page it renders as plain text
+rather than linking to itself (6 pages).
+
+**Sidebar.** 207 rows and 7,760px of scroll became 44 rows — GitBook shows 44. Nested groups
+start collapsed (`sidebar-tree.mjs`); Starlight already opens a collapsed group holding the
+current page, so the nav opens along the path being read and nothing else. `SidebarSublist`
+folds a parent page's duplicate entry into the group's own clickable row, so 245 nav entries
+render as 204. Type matched: section headers 12px/600 uppercase against Starlight's 16px/600,
+rows 14px/400 muted, current page marked by weight, colour and a 1px rule rather than a
+filled block, 34px row pitch, 21px indent per level, hairline only from the second level down.
+
+**Images.** The 64 `width=` attributes dropped in Phase 2 are carried through — 21 inside
+wrapper divs, **43 on standalone figures**, which GitBook sizes just the same. One 188px
+thumbnail had been rendering at 720×1075. The width rides in the markdown title slot and
+`rehype-image-width` turns it into an inline width and strips the title. `rehype-figures`
+pairs each image with the caption beneath it into `figure`/`figcaption`, which both fixes the
+rows and restores the semantics Phase 2 lost. All 15 wrappers render on one row.
+
+**Emoji, embeds, covers.** GitBook's four shortcodes render as characters, with `emoji 5` and
+`survivingShortcodes 0` as invariants. Video embeds emit as raw HTML rather than a component,
+returning **28 pages to `.md`** (`mdx` 46 → 18). Card covers are restored via `CoverCard`
+(`covers 13`), and `assets.mjs` copies them again (`copySet`/`mapEntries` 500 → 509).
+
+### The Phase 2 decision that was open, now closed without a markup change
+
+`progress-bar-message`'s `` needed two markup changes to parse as MDX — the dropped
+`` and the joined `` — and that was escalated to Pat in Phase 2 with no decision
+recorded. **Neither change happens any more.** Measuring the rendered page first showed the
+real problem was worse than the one escalated: through MDX the block also **lost its
+indentation and had its straight quotes rewritten as curly by SmartyPants**, breaking an XML
+sample readers copy. The identical construct in the `.md` page `using-jmespath-expressions`
+was untouched across all 20 of its blocks. The page is `.mdx` only because of one ``;
+emitting embeds as raw HTML returns it to `.md`, where `unwrapPreCode` never runs. **The
+generated `` is now byte-identical to the source.** No markup change is made to
+documentation content, so the standing rule is not bent.
+
+### Traps worth keeping
+
+- **`SidebarSublist` is not an overridable component.** The `components` schema accepts
+ `Sidebar` but not `SidebarSublist`, and Starlight's `Sidebar` imports it by relative path.
+ Naming it in `astro.config.mjs` is **accepted silently and does nothing** — no error, no
+ warning. It has to be reached through a `Sidebar` override.
+- **Clicking a linked group label also toggled it**, and `SidebarPersister` carried that
+ collapsed state across the navigation, so landing on a parent page hid its children. Only
+ visible by clicking through; the server-rendered HTML was correct.
+- **A block element at column 0 closes any enclosing list.** 7 embeds on
+ `ai-agent-creation-overview` sit in list items inside a stepper, and `` requires a
+ single `` child, so the page failed the build outright. Every emitted embed line now
+ carries the indentation of the block it replaces — the same hazard `figures.mjs` documents
+ for captions, and the reason the width could not be carried in a wrapper ``.
+- **`reflowImageDiv` and `convertFigures` both reject markup they do not expect**, and an
+ embed's `
` wrapping a `` is exactly that shape. Embeds convert *after* both
+ passes rather than either guard being weakened.
+- **`CSSStyleRule` exposes an empty-but-truthy `.cssRules`** for CSS Nesting. An ad-hoc
+ cascade-debugging script that branches on `if (rule.cssRules)` therefore treats every leaf
+ rule as a container and reports that nothing matches. Two measurements in this phase were
+ wrong that way before being caught; use `instanceof CSSStyleRule`.
+
+### Not done, and why
+
+- **The two non-video embeds still render as plain links.** `fetchify.com` in
+ `address-autocomplete-message` and `webaim.org` in `designing-accessible-chatbots`. GitBook
+ renders a bookmark card carrying the **target page's `
`, its domain and its favicon**,
+ all fetched from the third-party site at render time — measured: "WebAIM: Contrast Checker /
+ webaim.org". Reproducing that needs external metadata we do not have, and inventing a title
+ would be fabricating content. Left as links deliberately, for Pat to decide.
+- **`src/assets` is 48.4 MiB, up from 32.0**, against the 60 MB gate, and the largest file is
+ 4.0 MiB. Four of the nine restored covers are photographic PNGs of 11–14 MB that the
+ pipeline preserves as PNG. Format preservation is a Phase 3 decision and redesigning the
+ asset pipeline was out of scope; `astro:assets` still optimises what ships.
+- **`sharp@0.34.5` carries a high-severity advisory** (libvips CVEs) with a
+ `dependabot/npm_and_yarn/sharp-0.35.3` branch already open. Pre-existing, untouched here.
+ Note that bumping it means deleting `asset-map.json` and re-encoding, so it is not free.
+
+### Handoff to Phase 5 — verification and cutover
+
+**Nothing in this phase verified route parity against the deployed site**, only against
+`route-map.json` and a 30-route sample. Still outstanding before DNS:
+
+- Full route parity for all 204 live sitemap URLs against the deployed build.
+- A broken-link check covering **raw HTML anchors**, not just markdown links — 13 survive,
+ and the 12 in-page anchors (`#h.t23f6ncuijwz` ×7, `#what-is-a-list-message` ×5) need
+ checking against the *rendered* heading slugs.
+- **Anchor parity is still assumed, not verified.**
+- Accessibility: **455 of 529 images still have an empty `alt`**, and a linked group row now
+ nests an anchor inside a `<summary>`, which is worth a look in that pass.
+- The light-only pin's JavaScript-disabled fallback, above.
+
+---
+
## 2026-08-25 — First post-cutover content edit: release notes hand-edited
The release-notes page (`src/content/docs/release-notes/release-notes/index.mdx`) was updated
@@ -1363,3 +2052,179 @@ created:** any future `npm run convert` re-run against a `source/` snapshot will
drop these sections — the conversion pipeline must be treated as retired for content, or this
page's post-cutover additions re-applied after any regeneration. Phase 3 (assets, PR #18)
must rebase over this change and must not re-run the full conversion on top of it.
+
+---
+
+## 2026-08-27 — The conversion pipeline is retired; `src/content/docs/` is now authored
+
+`origin/main` was merged into `phase-4/look-and-feel` to bring the April–August 2026 release
+notes onto the branch. The release-notes page existed on both sides and both sides had
+changed it, so the resolution is worth recording: `main` carried the five new sections on top
+of Phase 2 output, which still referenced `/.gitbook/assets/image (627).png` and friends
+directly; `phase-4` carried the same page regenerated with `~/assets/…` paths, image widths
+and no dead `Embed` import. Git auto-merged them because the new sections sit above
+`## March 2026` and the asset rewrites sit below it. Verified rather than assumed: five new
+`<h2>`s render in reverse-chronological order, all four of the new absolute links resolve to
+pages that exist in `dist`, and the page emits 22 `_astro` images and zero `.gitbook`
+references.
+
+**The pipeline is now retired for content.** Conversion was always a one-time process, and it
+has run: `npm run convert` on this branch immediately before the merge left
+`git status --short` empty, so the generated corpus and `source/` agree exactly. That is the
+last time it should run. From here `src/content/docs/` is hand-authored in Starlight dialect
+and is the source of truth. `CLAUDE.md` hard rules 2 and 3 have been rewritten accordingly:
+rule 2 inverted, and rule 3 now forbids `npm run convert` outright rather than describing the
+idempotency it needs.
+
+`source/`, `scripts/convert.mjs` and the 261-test suite are kept, unchanged and still passing,
+as the record of how the corpus was produced. `assets.mjs` and `routes.mjs` are still safe to
+run alone. `source/` is deliberately left frozen: Stuart's release-notes sections were *not*
+back-ported into `source/release-notes/release-notes.md`. The two are now expected to diverge,
+and `source/` means "what GitBook held at cutover", not "what the site says".
+
+**Superseded:** the constraint recorded in the 2026-08-25 entry above — that Phase 3 "must
+rebase over this change and must not re-run the full conversion on top of it" — is resolved
+rather than outstanding. Phase 3 is contained in `phase-4/look-and-feel`, the merge is done,
+and no further conversion run is permitted by rule 3.
+
+### Inherited failure: `npm run verify:images` exits 1, and retirement makes it structural
+
+`verify:images` fails on this branch and **already failed at `dfb58cf`**, the commit that
+introduced it — this merge did not cause it. Proof: the merge adds 109 lines carrying no
+images, built `<img>` count is 746 and empty-alt content images 455, both exactly the
+documented pre-merge baseline, and regenerating `reports/alt-text-todo.md` on the merged tree
+produces a file byte-identical to the committed one.
+
+The check compares two figures with different provenance (`scripts/verify-images.mjs:119`):
+`emptyAltInBuild` is counted from `dist/`, while the work-list `rows` are parsed from
+`source/` (line 65 reads `source/<route.source>` directly). They disagree 448 vs
+455 — the source-side parse undercounts the build by 7. 455 is the figure used consistently
+elsewhere in this file; 448 appears nowhere else and is unexplained. Root cause of the 7 is
+not diagnosed here.
+
+**Retiring the pipeline turned this from a bug into a design fault.** A work list derived from
+`source/` describes the frozen GitBook corpus, not the site being served, and the two would
+diverge further with every page authored.
+
+**Fixed the same day.** `alt-audit.mjs` now parses the authored pages under
+`src/content/docs/` — `~/assets/…` destinations, markdown titles, and the
+emphasis-paragraph-after-image convention `rehype-figures.mjs` uses — so a caption is reported
+only where a reader actually sees one. `verify:images` reports 455 rows against 455 in the
+build and exits 0.
+
+**The 7 were not a counting error.** Seven images on three pages
+(`getting-ready`, `…/transfer/components`, `…/conversation-hand-off/chatwoot`) are still
+hotlinked from `googleusercontent.com` and `freshdesk.com`. The old parser matched only
+`.gitbook/assets/…`, and one of its tests asserted that anything else was skipped, so the
+blind spot was pinned in place by a test. Those images ship with an empty `alt` exactly as
+local ones do and are now reported; that is the whole of 448 → 455.
+
+Two measurement cautions worth keeping. **Astro serialises `alt=""` as a bare `alt`**, so any
+check written against `alt="([^"]*)"` alone silently misses every empty-alt image — that
+mistake produced a phantom count of 372 during this investigation. And the split is now
+**303 captioned, 152 uncaptioned**; the uncaptioned rows sort first in the report, because
+those are announced as nothing at all.
+
+Never affected what is served: the same build reports **0** images with no `alt` attribute at
+all and **0** `src` values with no file behind them.
+
+
+---
+
+## 2026-08-28 — `docs/superpowers/` removed
+
+The three design specs, three implementation plans and two phase-continuation prompts under
+`docs/superpowers/` are deleted. They were scaffolding for the phased build, not documentation
+of the site, and the durable record of what was decided and measured is this file.
+
+Nothing is lost: they are in git history, last present at `9ea473e`. Retrieve one with
+`git show 9ea473e:docs/superpowers/plans/2026-07-31-phase-5-verification.md`. Citations into
+those paths elsewhere in this file — the Phase 3 design spec reference in the ffmpeg
+correction above — now resolve only there. Those entries stand unedited under the append-only
+rule.
+
+**`.superpowers/` is deliberately kept.** It holds the per-task ledgers, briefs and review
+diffs, is git-ignored, and is therefore the only copy of several rulings and carried findings
+that were never transcribed here. Deleting it would be unrecoverable. Removing it is a
+separate decision, and the findings below should be transcribed first.
+
+### Phase 5 is unfinished, and this is what is left
+
+- **Task 6 — axe-core accessibility audit. Not started.** No `axe-core` dependency, no
+ `scripts/axe.mjs`, no `verify:a11y` script. Scoped to measure the two questions Phase 4 left
+ open rather than reason about them: the `<a>` nested inside a `<summary>` in a linked sidebar
+ group, and `CoverCard`'s deliberate `alt=""`. The plan has it stopping at a report before
+ anything is changed.
+- **Task 7 — Phase 5 gate write-up. Not done.** No Phase 5 gate entry exists in this file.
+- Both are specified in detail in the plan at the commit named above.
+
+### Carried findings that are still open
+
+- **Five hotlinked images are dead on the live site.** All five are on
+ `/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/transfer/components`
+ and return **404** — expired Google Docs export URLs, inherited from GitBook, not a migration
+ regression. Two further hotlinked images still resolve: one `googleusercontent` on
+ `/getting-started-1/getting-ready` and one `freshdesk` on
+ `/opendialog-platform/actions/conversation-hand-off/chatwoot`. This is a content defect for
+ the docs team, not a build defect. Status measured 2026-08-28; do not bake HTTP status into
+ any generated report, since that would break its idempotency.
+- **`reports/inherited-broken-links.json`'s `note` is partly false.** It claims the inherited
+ defects "are logged in `MIGRATION-NOTES.md`". True of the 9 links; **not** true of the 16
+ anchors, which are still only described as "assumed, not verified".
+- **An alt text containing `]`, or a caption containing `*`, breaks the emitted markdown.**
+ Flagged during Phase 2 review as owed to this file and never written down until now. It
+ matters more since the retirement: the docs team now writes alt text directly into
+ `src/content/docs/`, which is exactly the edit that would trigger it.
+
+---
+
+## 2026-08-28 — The npm-11 lockfile regression recurred, exactly as predicted
+
+The PR preview workflow (#21) merged into `phase-4/look-and-feel` at 13:43:34Z and its first
+run failed nine seconds later at `npm ci`:
+
+```
+npm error Missing: @emnapi/core@2.0.0-alpha.4 from lock file
+npm error Missing: @emnapi/runtime@2.0.0-alpha.4 from lock file
+npm error Missing: @emnapi/wasi-threads@2.0.1 from lock file
+```
+
+Same three packages as the 2026-07-29 Workers Builds failure, one alpha later. The entry above
+called this: *"Any `npm install` run locally under npm 11 rewrites the lock back into the
+npm-11-only shape and breaks CI again."*
+
+**The merge revealed it; it did not cause it.** `package-lock.json` lost the three top-level
+`@emnapi/*` entries at **`22cf3dd`** ("Serve Poppins and IBM Plex Mono"), 30 July — the first
+Phase 4 commit, which ran `npm install` to add the font packages and rewrote the lock as a
+side effect (10 `@emnapi` entries down to 7; 42 deletions against 8 insertions). It sat
+undetected for four weeks because nothing ran `npm ci` against this branch: Workers Builds
+builds `main`, and every deploy from here was a local `wrangler deploy` against a `dist/`
+built from an existing `node_modules`. The preview workflow is the first thing to install
+from the lock.
+
+`@napi-rs/wasm-runtime` — an optional wasm32 fallback reached through `sharp` and `rolldown` —
+requires `@emnapi/core ^2.0.0-alpha.3`, and nothing in the lock satisfied it. The version moved
+alpha.3 → alpha.4 only because that caret range floats across prereleases; the missing entries,
+not the float, are the defect.
+
+**Reproduced before fixing**, on Node 24.18.0 / npm 11.16.0 — the exact toolchain
+`.node-version` pins CI to — against a copy of the branch's `package.json` and
+`package-lock.json`. Identical error, identical three packages.
+
+**Fix:** `npm install --package-lock-only` under npm 11.16.0. The diff is 34 lines, all
+additions: the three `@emnapi/*` entries, marked `optional` and `peer`. No dependency version
+changed anywhere else.
+
+**Verified under both toolchains**, which is the part that makes it durable rather than a
+swap of which side breaks:
+
+| toolchain | `npm ci` | rewrites the lock? |
+|---|---|---|
+| Node 24.18.0 / npm 11.16.0 (CI) | exit 0 | no |
+| Node 22.19.0 / npm 11.6.0 (local) | exit 0 | no |
+
+**It will recur again.** The trap is unchanged: an `npm install` under a local npm older than
+CI's silently prunes optional cross-platform entries. The durable fix is still what the
+2026-07-29 entry asked for and never got — pin the local toolchain to `.node-version` so both
+sides run npm 11.16.0. Until then, after any `npm install`, check that
+`node_modules/@emnapi/core` is still in the lock before committing.
diff --git a/asset-map.json b/asset-map.json
new file mode 100644
index 0000000..f61c0ab
--- /dev/null
+++ b/asset-map.json
@@ -0,0 +1,3568 @@
+{
+ "generated": "scripts/assets.mjs",
+ "assets": {
+ "0.png": {
+ "slug": "0.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/0.png",
+ "hash": "1d7232363b9a576374351cce01d85b4a5fd1a9509c3fd194462c87235cf29c14"
+ },
+ "1 (1).png": {
+ "slug": "1-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1-1.png",
+ "hash": "cf066efdd3f301975f9e0de870222319f6ebf1a038047f13164a3a5c7e315cad"
+ },
+ "1 (3).png": {
+ "slug": "1-3.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1-3.png",
+ "hash": "c853cfe17b7d5fbdda73eee84abf420ca0dcd7107440a0f3af807528ec690405"
+ },
+ "1.png": {
+ "slug": "1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1.png",
+ "hash": "c7e451dc3ae5b105809691a78b0330e81f33ed319f70aa78a8fd66429d56750f"
+ },
+ "1000008687.jpg": {
+ "slug": "1000008687.jpg",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1000008687.jpg",
+ "hash": "199adee5bb52380b1e897c39ade44307c53a9a2f2c8fab07f0a4a4df58da8b9e"
+ },
+ "1000008688.jpg": {
+ "slug": "1000008688.jpg",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1000008688.jpg",
+ "hash": "26058d7faf70c9b6d24011186970b37d4266abd2f2d7038c0ed385711853e373"
+ },
+ "1270x760 - Image (20).png": {
+ "slug": "1270x760-image-20.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1270x760-image-20.png",
+ "hash": "c232028ae44be77f677968a9831fc33f17951a1d15d3d962781b80fe9da0115b"
+ },
+ "1270x760 - Image (21).png": {
+ "slug": "1270x760-image-21.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1270x760-image-21.png",
+ "hash": "abb75a83706bff4b3ef324c3f44e8402d3fd3c288b6c7b33b94932aad69ffd47"
+ },
+ "1270x760 - Image (22).png": {
+ "slug": "1270x760-image-22.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1270x760-image-22.png",
+ "hash": "788ffc33fda81b7e7e949cb3fe502e8b55cc1d7b76f02a44685cea736736ec7a"
+ },
+ "1270x760 - Image (23).png": {
+ "slug": "1270x760-image-23.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1270x760-image-23.png",
+ "hash": "775900846b8d7404fa2fac12e57351cb6e8219a5f6e4181a2e49ed0867555b33"
+ },
+ "1270x760 - Image (24).png": {
+ "slug": "1270x760-image-24.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1270x760-image-24.png",
+ "hash": "fd49a09e3bd30743a65f549c38fbe04da92b6db40f431552a9246f3ceca76410"
+ },
+ "1270x760 - Image (26).png": {
+ "slug": "1270x760-image-26.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1270x760-image-26.png",
+ "hash": "1fa66e5c22ef0d971b0c6e1384fbae3d9b2f9a051c1661c701faddb2b56a95bb"
+ },
+ "1270x760 - Image (27).png": {
+ "slug": "1270x760-image-27.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1270x760-image-27.png",
+ "hash": "717c9c98054786e381a2b5c9dd08a923123c848a26f707589f283b7c51a17510"
+ },
+ "1270x760 - Image (28).png": {
+ "slug": "1270x760-image-28.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1270x760-image-28.png",
+ "hash": "8727f6939e092addfd7c309ee1dedfeeddcac78658e2d6a7c31891122daaa710"
+ },
+ "1270x760 - Image (29).png": {
+ "slug": "1270x760-image-29.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1270x760-image-29.png",
+ "hash": "85be8e260bba8097775263d3f8ed23acdc64cf3ea7e727364e97bf4a120a8985"
+ },
+ "1270x760 - Image (30).png": {
+ "slug": "1270x760-image-30.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1270x760-image-30.png",
+ "hash": "244703abe4a63d5b578efa9f3bdb6c1418ec944edf839b4658ca0e430b7bf210"
+ },
+ "1270x760 - Image (31).png": {
+ "slug": "1270x760-image-31.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1270x760-image-31.png",
+ "hash": "b448952af83d7fe0455c1b148098094670530d5c678c3c67052e49267a52d9e1"
+ },
+ "1270x760 - Image (32).png": {
+ "slug": "1270x760-image-32.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1270x760-image-32.png",
+ "hash": "d75a64980d51f7a2e6c6addf23255b4648e4ab521c40bbb5ae7439396f093387"
+ },
+ "1270x760 - Image (33).png": {
+ "slug": "1270x760-image-33.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1270x760-image-33.png",
+ "hash": "c726a69ab1d20f7d617cda3f5c6a77a75081b93559e5996487b48cfce17b911b"
+ },
+ "1270x760 - Image (34).png": {
+ "slug": "1270x760-image-34.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/1270x760-image-34.png",
+ "hash": "f8353c85a32adc459d4a123f7a96e454d912784a2ba2048972edb1dff8535374"
+ },
+ "2 (1) (2).png": {
+ "slug": "2-1-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2-1-2.png",
+ "hash": "cce58bfe17a6b8f1a97b8563cc5c6eaf87fb5facacd1f1fcc161885805cd62fd"
+ },
+ "2 (2).png": {
+ "slug": "2-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2-2.png",
+ "hash": "c3a26575bf6c74905cecd28eaad9e3049a22ae0ee388f92d1d807802b0c47277"
+ },
+ "2.png": {
+ "slug": "2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2.png",
+ "hash": "10cec6c46f9cd3ac6f90f13ecc1c8a5e767ff5a6985d8ef19c3c7d71710cd9a8"
+ },
+ "2021-06-07_17-01-18 (1).png": {
+ "slug": "2021-06-07-17-01-18-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2021-06-07-17-01-18-1.png",
+ "hash": "d02454d557ded488613efc6ca599a98973c51f71e89da25bbbae57b628fe46c5"
+ },
+ "2022-09-21_16-47-08.png": {
+ "slug": "2022-09-21-16-47-08.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2022-09-21-16-47-08.png",
+ "hash": "9d96f7429a0da23d8f3af2dd2932d2f302a35b4bdcf4d5a835fc610b3b9b0a10"
+ },
+ "2023-03-08_16-29-24 1.png": {
+ "slug": "2023-03-08-16-29-24-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-03-08-16-29-24-1.png",
+ "hash": "ecc5c06ef3dcd8fb642cda0bddbc446383b5eba09154353c2a15c902abbb1c68"
+ },
+ "2023-05-01_10-54-09.png": {
+ "slug": "2023-05-01-10-54-09.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-01-10-54-09.png",
+ "hash": "5afbca1942e4d49c82c413d277f6fc0f00a108b4ee6c210b6731fd6624ae73c9"
+ },
+ "2023-05-01_14-35-48.png": {
+ "slug": "2023-05-01-14-35-48.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-01-14-35-48.png",
+ "hash": "1d559561f9e60eb107eff87bfcf4f672d598c05530985ce28a9927bbbfe01e22"
+ },
+ "2023-05-01_15-15-11 copy (1).png": {
+ "slug": "2023-05-01-15-15-11-copy-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-01-15-15-11-copy-1.png",
+ "hash": "da31a9e467c40cc15187b185e3234332588e3760939a55f02333411a0ffd345a"
+ },
+ "2023-05-01_15-57-54.png": {
+ "slug": "2023-05-01-15-57-54.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-01-15-57-54.png",
+ "hash": "05b9021f44d666da64ded48b971347e10d0a03c6cfd3f65b7b49a9db1754ced1"
+ },
+ "2023-05-01_16-32-21.png": {
+ "slug": "2023-05-01-16-32-21.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-01-16-32-21.png",
+ "hash": "97ac8dd4fd4a48003c3e3b5c85aa5523c39bac6c2dc5eee41c0c671eae789e0c"
+ },
+ "2023-05-01_16-43-02.png": {
+ "slug": "2023-05-01-16-43-02.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-01-16-43-02.png",
+ "hash": "03d1c141d85d304d38b8d31c0d5d68791c05ad1967316204e85d006ad25b5a38"
+ },
+ "2023-05-02_09-13-40.png": {
+ "slug": "2023-05-02-09-13-40.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-02-09-13-40.png",
+ "hash": "1924c9b190269a56fbefd9649fb42c0cf1ed06b242f80ca05a692bc09ebc04c1"
+ },
+ "2023-05-02_12-11-15.png": {
+ "slug": "2023-05-02-12-11-15.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-02-12-11-15.png",
+ "hash": "8da80e3cdef84fb490599a3b1fa2c7b10365e9e76a83fb358df739740e0d4722"
+ },
+ "2023-05-02_12-11-35.png": {
+ "slug": "2023-05-02-12-11-35.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-02-12-11-35.png",
+ "hash": "608184627cfc7b5268365ab5a31310ffab265b60836911afb97b9d3eccb81dc9"
+ },
+ "2023-05-02_15-20-54.png": {
+ "slug": "2023-05-02-15-20-54.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-02-15-20-54.png",
+ "hash": "da829c1bdbf56d3c4cbfb2f4db4532c04cc9b69d105a3af3825fca05181bc515"
+ },
+ "2023-05-02_15-28-26.png": {
+ "slug": "2023-05-02-15-28-26.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-02-15-28-26.png",
+ "hash": "0fee5f4bf63621d49408fe712f788b386ddbd0a57ec48adf58a69b15b7bbbf41"
+ },
+ "2023-05-02_15-32-45.png": {
+ "slug": "2023-05-02-15-32-45.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-02-15-32-45.png",
+ "hash": "11b4c70e4f2d642d2da2824ac3873580994b0e6a27c2756eb2023267c1f4866b"
+ },
+ "2023-05-02_15-33-04.png": {
+ "slug": "2023-05-02-15-33-04.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-02-15-33-04.png",
+ "hash": "b171fa9e81599ba66cbb6dd4a76c7d70c4862e1bfc7f1c74a8fd35860927f75f"
+ },
+ "2023-05-04_15-58-27 (1).png": {
+ "slug": "2023-05-04-15-58-27-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-04-15-58-27-1.png",
+ "hash": "0ebbde79f45bd8ea161129379369e65caaaa2738f94abd6bd8b1c73833c25437"
+ },
+ "2023-05-04_16-17-09 (1).png": {
+ "slug": "2023-05-04-16-17-09-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-04-16-17-09-1.png",
+ "hash": "8faa3698469644e375a5752a70c03b73d8fc4b3f638f6e1031da04aeab0917c7"
+ },
+ "2023-05-04_16-23-35 (1).png": {
+ "slug": "2023-05-04-16-23-35-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-04-16-23-35-1.png",
+ "hash": "3c1a55878e859ddb9162158c0a908b0f3a19b2789c7770207634ce6569cfa86a"
+ },
+ "2023-05-15_20-24-57.png": {
+ "slug": "2023-05-15-20-24-57.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-15-20-24-57.png",
+ "hash": "42f97a59a38ee8cc380d633f34bd80f6acdabac0a6862042545ebb95e27980e3"
+ },
+ "2023-05-15_20-27-38.png": {
+ "slug": "2023-05-15-20-27-38.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-15-20-27-38.png",
+ "hash": "b4c03700539d8b4d7e94dc8af5106ffdf4e708dd2e20ef897ebdcc36f9ec9ec3"
+ },
+ "2023-05-15_20-34-34.png": {
+ "slug": "2023-05-15-20-34-34.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-15-20-34-34.png",
+ "hash": "130da66eead387364c9e73cb7ab441c2b501109baa67ea89b799d38cd72c8cab"
+ },
+ "2023-05-17_07-53-21.png": {
+ "slug": "2023-05-17-07-53-21.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-17-07-53-21.png",
+ "hash": "538e890707b2dbd737b7e69183ed18780f38cb9982ed7b2fa36ddb5c1f68fc49"
+ },
+ "2023-05-17_07-54-16.png": {
+ "slug": "2023-05-17-07-54-16.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-17-07-54-16.png",
+ "hash": "7e57c9a7dd6d43b438048be671acd83c987206155a22f4590ed4cdc96c129b65"
+ },
+ "2023-05-18_14-54-46.png": {
+ "slug": "2023-05-18-14-54-46.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-18-14-54-46.png",
+ "hash": "04416a3090cc776953b0993e7a347bc058835789e0f268267ff58afb629d4253"
+ },
+ "2023-05-18_15-08-12.png": {
+ "slug": "2023-05-18-15-08-12.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-18-15-08-12.png",
+ "hash": "4881a95749d4fb029527a6e517e274414071e1a53502f44d7962c77e6cc55b93"
+ },
+ "2023-05-18_15-09-06.png": {
+ "slug": "2023-05-18-15-09-06.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-18-15-09-06.png",
+ "hash": "bf110c98cc88eda167e8e5e0fd7e5d60be351577c1fd1d31e5453b101be09c3d"
+ },
+ "2023-05-18_15-18-42.png": {
+ "slug": "2023-05-18-15-18-42.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-18-15-18-42.png",
+ "hash": "d8ffc75bd74904b7983349efe8bf2f07812ec98bb1a60466452c0ba690c46069"
+ },
+ "2023-05-18_15-25-33.png": {
+ "slug": "2023-05-18-15-25-33.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-18-15-25-33.png",
+ "hash": "7be1741df9d9fe2af7f6ed2a8158babe074dcf0017ce3191f4c6130a7a606963"
+ },
+ "2023-05-18_15-29-56.png": {
+ "slug": "2023-05-18-15-29-56.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-18-15-29-56.png",
+ "hash": "e6ae80c248139bf66ceed858091049f1db25964778a1758ad039e53bbda197a6"
+ },
+ "2023-05-18_15-38-33.png": {
+ "slug": "2023-05-18-15-38-33.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-18-15-38-33.png",
+ "hash": "e0243696d9450a1903c367d7385028604666bc9986c0e974f5c318772334c24f"
+ },
+ "2023-05-19_19-36-01.png": {
+ "slug": "2023-05-19-19-36-01.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-19-19-36-01.png",
+ "hash": "7adfa4d6f8fa547c26a6b3659dd26389fadb85fef311219be79f38e7eb1ce263"
+ },
+ "2023-05-23_10-57-47 (2).png": {
+ "slug": "2023-05-23-10-57-47-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-23-10-57-47-2.png",
+ "hash": "37f76c365748238c3ced1f6f7074906d500037458bff10e536226d0871c08c91"
+ },
+ "2023-05-23_10-57-47 (5).png": {
+ "slug": "2023-05-23-10-57-47-5.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-23-10-57-47-5.png",
+ "hash": "37f76c365748238c3ced1f6f7074906d500037458bff10e536226d0871c08c91"
+ },
+ "2023-05-23_13-09-37.png": {
+ "slug": "2023-05-23-13-09-37.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-23-13-09-37.png",
+ "hash": "697a38a828f2571f7d3291e5f706a8f1364d0d9f16e5d5a09138f872eb6165a2"
+ },
+ "2023-05-23_13-10-36.png": {
+ "slug": "2023-05-23-13-10-36.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-23-13-10-36.png",
+ "hash": "1c5a57a75b6aebbd2a1e2e6c962aa140a6518c3c78467dfcaedf728f7af33d3d"
+ },
+ "2023-05-23_14-09-08.png": {
+ "slug": "2023-05-23-14-09-08.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-23-14-09-08.png",
+ "hash": "b7721e1eeea4e7906ff45fc137859f5b944188959d51d17f7f7dfb33bec8a887"
+ },
+ "2023-05-23_14-14-16.png": {
+ "slug": "2023-05-23-14-14-16.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-23-14-14-16.png",
+ "hash": "304f7a1b1f75860e9a485d2ae591526da9339ef2b050ebee72c364643a8d14fa"
+ },
+ "2023-05-23_14-19-32.png": {
+ "slug": "2023-05-23-14-19-32.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-23-14-19-32.png",
+ "hash": "1cd177e7dd2bb58fd2577d3cce87ae2fc879286bef7edac5f87c03a0ffbfb126"
+ },
+ "2023-05-23_14-21-42.png": {
+ "slug": "2023-05-23-14-21-42.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-05-23-14-21-42.png",
+ "hash": "819cf96020ff022d6162daa8139c92efa5f96dd8deb920bf097581641e852749"
+ },
+ "2023-06-09_15-27-50.png": {
+ "slug": "2023-06-09-15-27-50.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-09-15-27-50.png",
+ "hash": "05e0b72dc6db9e9306f35152a5f055f81c3e5b3a1aa4266b91206fd8932dc06c"
+ },
+ "2023-06-09_15-46-54.png": {
+ "slug": "2023-06-09-15-46-54.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-09-15-46-54.png",
+ "hash": "4f13628972a82a549cc6eb8d575d8d07ba4737821ce82ce230e98979b20581ab"
+ },
+ "2023-06-09_16-10-54.png": {
+ "slug": "2023-06-09-16-10-54.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-09-16-10-54.png",
+ "hash": "70d8e1e2e275468eb0816cc4f18d3c31d3d7f580d319dd0f19c100ebb02ab413"
+ },
+ "2023-06-09_16-11-08.png": {
+ "slug": "2023-06-09-16-11-08.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-09-16-11-08.png",
+ "hash": "97b78f3e7fb596237bf9a6dc95bc86f3827c2dd78f63a851cd61519d188fb1ae"
+ },
+ "2023-06-09_16-11-21.png": {
+ "slug": "2023-06-09-16-11-21.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-09-16-11-21.png",
+ "hash": "483cc97cfc2b3ea47404d18cada8db88386786ceaddbdf93324819e2baf95aa7"
+ },
+ "2023-06-14_13-08-01 copy.png": {
+ "slug": "2023-06-14-13-08-01-copy.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-14-13-08-01-copy.png",
+ "hash": "e831cef2b11b9522ab083d01e28f23e281863c9e85476890e6dc39df8800d0cd"
+ },
+ "2023-06-14_16-31-02.png": {
+ "slug": "2023-06-14-16-31-02.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-14-16-31-02.png",
+ "hash": "36e8b189fd51410d6b8e390b250fe7eecdb681b93fca2f92a49d4deed7200c34"
+ },
+ "2023-06-15_14-42-00.png": {
+ "slug": "2023-06-15-14-42-00.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-15-14-42-00.png",
+ "hash": "07412184776261a27cf47bee635e674fb96fa2ae07dc3c35073c0d3167f63dbd"
+ },
+ "2023-06-16_07-32-11.png": {
+ "slug": "2023-06-16-07-32-11.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-16-07-32-11.png",
+ "hash": "51c5e695eaa11b4c32704a1256a94a21bd3039dc6d5c7e88106927c764cb4c19"
+ },
+ "2023-06-16_07-40-11.png": {
+ "slug": "2023-06-16-07-40-11.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-16-07-40-11.png",
+ "hash": "67b6091754da9cef9d0dd44f44b269a1ac60477a059345c4decc7b47f19bb816"
+ },
+ "2023-06-16_07-40-37 (1).png": {
+ "slug": "2023-06-16-07-40-37-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-16-07-40-37-1.png",
+ "hash": "a854a0d6359fb50470ab5f356a4acc31de1ea76e324c946068ea7559cb6ac771"
+ },
+ "2023-06-16_07-44-00 copy.png": {
+ "slug": "2023-06-16-07-44-00-copy.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-16-07-44-00-copy.png",
+ "hash": "b991dc923b7446ef891c37f9baf32b0aa05519c2797b96a09f220eb784feb554"
+ },
+ "2023-06-16_07-44-00.png": {
+ "slug": "2023-06-16-07-44-00.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-16-07-44-00.png",
+ "hash": "ebb89ba1f54625d26ca7c731366ca3d8615cecc8b5c58d5f8be68f355230f312"
+ },
+ "2023-06-16_07-47-08.png": {
+ "slug": "2023-06-16-07-47-08.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-16-07-47-08.png",
+ "hash": "302fec564ce2b46b0b771543bba75e86ce17e77842b7ce975fb65ef11e57ae05"
+ },
+ "2023-06-20_15-55-55.png": {
+ "slug": "2023-06-20-15-55-55.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-20-15-55-55.png",
+ "hash": "85f0f4489196e7d6ea3e197e082ae341d05fd528e4c3a8163c6b7ca8b5ac06f5"
+ },
+ "2023-06-20_15-59-11.png": {
+ "slug": "2023-06-20-15-59-11.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-20-15-59-11.png",
+ "hash": "4e55e304f21b8f839717af77683e45bc2a5932a5f96e45a9a21db2f9648cc1a4"
+ },
+ "2023-06-20_15-59-35.png": {
+ "slug": "2023-06-20-15-59-35.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-20-15-59-35.png",
+ "hash": "3301cfb2e744ca987e77163efa8fa3c810d20cd5c41848c2a872d3e8b2811047"
+ },
+ "2023-06-20_16-05-02.png": {
+ "slug": "2023-06-20-16-05-02.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-20-16-05-02.png",
+ "hash": "1a4737d6a3b432f1bb01b5243d55b6e90f44f444ec62438c8e7f60f3c4b97fae"
+ },
+ "2023-06-30_15-33-50.png": {
+ "slug": "2023-06-30-15-33-50.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-06-30-15-33-50.png",
+ "hash": "3a220cd1fc3c0e0ff25a0a50e7423d8622031107f765ec5447d83d3551c6781c"
+ },
+ "2023-11-09_18-39-04.png": {
+ "slug": "2023-11-09-18-39-04.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-11-09-18-39-04.png",
+ "hash": "94a83187206e7fb1e39f2d8ee4dd5b8f8504ff3300986ae76cb818e0cad06d61"
+ },
+ "2023-11-09_18-41-49.png": {
+ "slug": "2023-11-09-18-41-49.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-11-09-18-41-49.png",
+ "hash": "bf6f410c3f3b98eed527f49d10acd13d7ab90e6e3f30077923c77e117157d335"
+ },
+ "2023-11-09_18-48-53.png": {
+ "slug": "2023-11-09-18-48-53.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-11-09-18-48-53.png",
+ "hash": "c348807b8a44cc00aba294af1865c92612d2774731f247449d37d6a8ac63987d"
+ },
+ "2023-11-09_18-52-09.png": {
+ "slug": "2023-11-09-18-52-09.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-11-09-18-52-09.png",
+ "hash": "8d94690e10991c49ca4d6ab9a37edffa95d66778cd2aa4e5eb6a277263ba3ee5"
+ },
+ "2023-11-09_18-53-48.png": {
+ "slug": "2023-11-09-18-53-48.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-11-09-18-53-48.png",
+ "hash": "52b65d100d0493098693945d2313e5c8b05dc75fa518212c00b5fae676c685b4"
+ },
+ "2023-11-09_19-07-11.png": {
+ "slug": "2023-11-09-19-07-11.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-11-09-19-07-11.png",
+ "hash": "9a627c38d1ac95363fd1f3443fd5898df12344cadabf294670b05fe47cd77577"
+ },
+ "2023-11-09_19-08-09 (1).png": {
+ "slug": "2023-11-09-19-08-09-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-11-09-19-08-09-1.png",
+ "hash": "da0a49fc310429422f17776aac1eec8a358810838f62279d02be89af4fbd7e8d"
+ },
+ "2023-11-10_14-20-10.png": {
+ "slug": "2023-11-10-14-20-10.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-11-10-14-20-10.png",
+ "hash": "d6e1fb3a135853e53a1423df027892f3fd6e1c75a640bffed75c54f95615aa93"
+ },
+ "2023-11-10_14-24-27.png": {
+ "slug": "2023-11-10-14-24-27.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-11-10-14-24-27.png",
+ "hash": "39bf0ce28645a2a303424a09c77c0d8b83aff04024ec0b435f0a103dffdcc026"
+ },
+ "2023-11-10_14-27-21.png": {
+ "slug": "2023-11-10-14-27-21.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-11-10-14-27-21.png",
+ "hash": "1dff1a6d1941df6fbd321db0b31fe3d0a7eb8fcbf7d2757858984663002d7a35"
+ },
+ "2023-11-10_14-29-11.png": {
+ "slug": "2023-11-10-14-29-11.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-11-10-14-29-11.png",
+ "hash": "bd313164360dffdc63790ebeb94f923312522b9be8920af064764874e5c42ed5"
+ },
+ "2023-11-10_14-29-36.png": {
+ "slug": "2023-11-10-14-29-36.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2023-11-10-14-29-36.png",
+ "hash": "3a55b322a7fee1e80c1338b09400bb95437b2827a6e3264b42f8019cae0d5b52"
+ },
+ "2B.png": {
+ "slug": "2b.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/2b.png",
+ "hash": "37a060658e4aa85f4571f6b23e72f18e663fd1daced1ffb41820c91c5942ed9c"
+ },
+ "3 (1).png": {
+ "slug": "3-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/3-1.png",
+ "hash": "fb002bb0c33e3110a6c4b104f9535b01539af62412d7a0a102717caec66d5bc3"
+ },
+ "3.png": {
+ "slug": "3.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/3.png",
+ "hash": "ed625d8c8b3c2941c78bf3d45c180d06aaaad4aca699ea9f88c4bc6f999609ab"
+ },
+ "3B.png": {
+ "slug": "3b.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/3b.png",
+ "hash": "431659ccc907628f0ff3e6e0b096da7f8a2f6bf8e7d9118b0759cb9bfe3f1992"
+ },
+ "4 (1).png": {
+ "slug": "4-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/4-1.png",
+ "hash": "f5ee094a51b409ee80323b092e2055a962c84cdc123ed0b2fcefe4af114d6daf"
+ },
+ "5B.png": {
+ "slug": "5b.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/5b.png",
+ "hash": "d93c3aceeac957cf15a0029900c3a8592b819214842631bb1aeaec08ad0956ce"
+ },
+ "AIAgent_testsheet.png": {
+ "slug": "aiagent-testsheet.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/aiagent-testsheet.png",
+ "hash": "70dec8ca18ffbafc9d323cb5ca9af76f07e9ba658fca9fbfebfdf0e1425310b8"
+ },
+ "Actions landing page.png": {
+ "slug": "actions-landing-page.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/actions-landing-page.png",
+ "hash": "8ee353d229b97bd4c594d95de43845aafe0e29dcab1647f2654d40bb165d8cfd"
+ },
+ "Alt tags (1).png": {
+ "slug": "alt-tags-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/alt-tags-1.png",
+ "hash": "8c1743552515fcf15cf9f7d14353fe2b3150c7f3d996a122b7644ea8425c26a7"
+ },
+ "Buttons.png": {
+ "slug": "buttons.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/buttons.png",
+ "hash": "7035c94b93330bd2881ce51ba7d8ba2c280b4735e23d65be91e58dde4eb51c9f"
+ },
+ "Chatwoot Handover.png": {
+ "slug": "chatwoot-handover.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/chatwoot-handover.png",
+ "hash": "164db4c4955e44809e3870285bea95f5a2256b490a62283559630a874debf00c"
+ },
+ "Colour contrast (2).png": {
+ "slug": "colour-contrast-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/colour-contrast-2.png",
+ "hash": "197efb5a610a761f6c79e0ab87d2b6cd20418beecabda6cd83248e8d65a54a0a"
+ },
+ "DeliveryKnowledgeBase.csv": {
+ "slug": "deliveryknowledgebase.csv",
+ "kind": "file",
+ "destination": "public/files",
+ "reference": "/files/deliveryknowledgebase.csv",
+ "hash": "4ed804578a9ac62af5db27f09a5137b68cb5a359147df5a0b9c3f76d2ef5b10b"
+ },
+ "DesignOption_NotExpanded.png": {
+ "slug": "designoption-notexpanded.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/designoption-notexpanded.png",
+ "hash": "322bd9769d8fb73c8c1c1a1a60d776dfcc96281b83122b79040d2483584bc904"
+ },
+ "FAQ Interface Turns.png": {
+ "slug": "faq-interface-turns.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/faq-interface-turns.png",
+ "hash": "082bff572534b3510fe1015f21139568a34d1c3ab34a1ce93a02cbb8211b223c"
+ },
+ "FAQ Turn.png": {
+ "slug": "faq-turn.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/faq-turn.png",
+ "hash": "d22e3eef67a287dab2088021cb85ccf8c09e933f4466981f7f1dc31f87d9b88e"
+ },
+ "Group 1 (1) (1).png": {
+ "slug": "group-1-1-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-1-1-1.png",
+ "hash": "4a6b831c3309fc6392d02c6479c3fa4be5c8b9da9a20dfca70483dbcaf0114a1"
+ },
+ "Group 1 (1).png": {
+ "slug": "group-1-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-1-1.png",
+ "hash": "b87acbda5abfac71f5bba54406c2d95df290f3caa9d6e8713b377729ad51c373"
+ },
+ "Group 10 (1).png": {
+ "slug": "group-10-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-10-1.png",
+ "hash": "5de888afcb64597a09b92c7eebd83e6065a7e0f1210f86f895b751fa5423f890"
+ },
+ "Group 10 (2).png": {
+ "slug": "group-10-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-10-2.png",
+ "hash": "dbcb66daec2f1a534145c06a2a16c79c2f6d7a0a3ceb387f74bf584ea1a05d10"
+ },
+ "Group 11 (1).png": {
+ "slug": "group-11-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-11-1.png",
+ "hash": "ff33491a58a57d4b2791d462142d544c05d50ca7b2c67a4714be4cd80875d3c6"
+ },
+ "Group 11.png": {
+ "slug": "group-11.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-11.png",
+ "hash": "e8b76a9d9d21488c5bbf5230af1809419a760089ae5d1efbf7bc3c226f6fa59f"
+ },
+ "Group 12.png": {
+ "slug": "group-12.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-12.png",
+ "hash": "cbe8d9d284a69e5bef0420b9411f9e4002fcb1386d13b7d9646554330ad8fe10"
+ },
+ "Group 13.png": {
+ "slug": "group-13.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-13.png",
+ "hash": "1cc1e7b235317cafc15d728195d2dec237c9c15b158457b37a8aa578e2103b4b"
+ },
+ "Group 14.png": {
+ "slug": "group-14.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-14.png",
+ "hash": "3914cacdfca727df3944ec12fa8be514cf37da382bc0deb923dc1a0d6634192b"
+ },
+ "Group 15.png": {
+ "slug": "group-15.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-15.png",
+ "hash": "10b891acddee5160304d90e041320c0278565999f69d432f2b8e4e7183e75aff"
+ },
+ "Group 16.png": {
+ "slug": "group-16.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-16.png",
+ "hash": "31e546d8d73e6f22c999de9da81aab9d4e8444c82613260f315018d4847692f0"
+ },
+ "Group 17.png": {
+ "slug": "group-17.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-17.png",
+ "hash": "3fadaba92a38588dd297821e8e2224a4963ff939b2424f4eca1bd31adfa42d59"
+ },
+ "Group 18.png": {
+ "slug": "group-18.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-18.png",
+ "hash": "d885612c5b5761b7edbec35f9197ef0fc83ff6a6fab8d51a939595604981b8b3"
+ },
+ "Group 19.png": {
+ "slug": "group-19.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-19.png",
+ "hash": "f60e1defbc314889aa16f4166c8fb3dfd8935cb1d438229590ba34a9c0770e8d"
+ },
+ "Group 2 (1).png": {
+ "slug": "group-2-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-2-1.png",
+ "hash": "c0986419aa49db6a6dd718c0434f43d3d444cf324d00371ee87690654e93be4d"
+ },
+ "Group 2 (2).png": {
+ "slug": "group-2-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-2-2.png",
+ "hash": "225c22275524ea1c73909496019bd83bdd9dcf7e9ae2b2ad305e5d75bb8131f3"
+ },
+ "Group 2 (3).png": {
+ "slug": "group-2-3.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-2-3.png",
+ "hash": "c4de80d44cbfec1117a4b428f3dff573303d9b128119e7912619aba6640643ab"
+ },
+ "Group 20.png": {
+ "slug": "group-20.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-20.png",
+ "hash": "28c72f243b7e4a2151c9d6949129913afe3662a56e2b4a016f6f50fc754bb789"
+ },
+ "Group 21.png": {
+ "slug": "group-21.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-21.png",
+ "hash": "a53d8ef6056c4637e79d9d8c3bbc21ed5862edff00a36b9e5c7d5b5cab17bf93"
+ },
+ "Group 24.png": {
+ "slug": "group-24.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-24.png",
+ "hash": "5c38b94a1a56bef2d4e1457ca7eda66ca769589d9ce2f62294f9c889c7b622e4"
+ },
+ "Group 25.png": {
+ "slug": "group-25.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-25.png",
+ "hash": "166a9cf355e412362b8766a8500f0ec31f3aa0b1307d290caf9e9dd39ee89dc2"
+ },
+ "Group 26.png": {
+ "slug": "group-26.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-26.png",
+ "hash": "ebf44642f4d5daa9960b598f1142cb8a5ce0ad31831267db5719e0b0b576706d"
+ },
+ "Group 27.png": {
+ "slug": "group-27.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-27.png",
+ "hash": "bf70dc4c1b8f2e4e917adf1aa209c37db1d2d8dd4494914b65060613d8f3874b"
+ },
+ "Group 28.png": {
+ "slug": "group-28.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-28.png",
+ "hash": "834cab6aca2d5819760ffb703d0dfd9de56d25441a79c631f1aec5c919576b18"
+ },
+ "Group 3 (1) (1).png": {
+ "slug": "group-3-1-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-3-1-1.png",
+ "hash": "d9f26a276bb27a62ccd0209c2c2248270a33df3035042e7d669622eebbf6aac0"
+ },
+ "Group 3 (1).png": {
+ "slug": "group-3-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-3-1.png",
+ "hash": "b746d7526c47b070467d8433909f1f42e6618cb70a8bb0c72e21848961516df9"
+ },
+ "Group 30.png": {
+ "slug": "group-30.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-30.png",
+ "hash": "f3c781f2502880aee8140ed37518efda1bf4790cd15b2d9ce03c200d086a2b88"
+ },
+ "Group 4 (1).png": {
+ "slug": "group-4-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-4-1.png",
+ "hash": "c77f8a45f267ea1b8f736c4363a7567ddb80b7a2663db9d66f60ea40803297aa"
+ },
+ "Group 4.png": {
+ "slug": "group-4.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-4.png",
+ "hash": "9607660a843a8603302ce3e743ad3e20618530d24847c5569371ac6515f9e364"
+ },
+ "Group 5 (1).png": {
+ "slug": "group-5-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-5-1.png",
+ "hash": "f33f02f90f3325a1cdffd3c44b38abce03d99b1017ab2d6e26b9bb15903fe638"
+ },
+ "Group 5 (2).png": {
+ "slug": "group-5-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-5-2.png",
+ "hash": "107d5ef3dfdae408683df65c77e9cf345016b61bd46caf7505a3513606729ddf"
+ },
+ "Group 5.png": {
+ "slug": "group-5.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-5.png",
+ "hash": "0bea1aaeca46bbba3a7882bd273a134c2f305a7e3e0479f7eb06b0dee6905427"
+ },
+ "Group 6 (1).png": {
+ "slug": "group-6-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-6-1.png",
+ "hash": "27954e56920a5bf4f9a6ed6a847c4e9e474b99f4882bfbb19d286e00edc91510"
+ },
+ "Group 7 (1) (1).png": {
+ "slug": "group-7-1-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-7-1-1.png",
+ "hash": "53bda4472038f164ec5a4c02d409e570ff9fb1f1843a755163f3d2aafbc75410"
+ },
+ "Group 7 (1).png": {
+ "slug": "group-7-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-7-1.png",
+ "hash": "11d6fb9172a84cda95e88b5dcd27a08a08dd281bbd50fad4572ee06208739bf8"
+ },
+ "Group 8 (1).png": {
+ "slug": "group-8-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-8-1.png",
+ "hash": "5cc2c6cf4162f7757c143894e7b4f893f820698a58ca50642712f7b1018ff9e0"
+ },
+ "Group 8.png": {
+ "slug": "group-8.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-8.png",
+ "hash": "28f2fbd4bedb984597346a8c2cd6230c0d1b5fee8e60063a2483b8e5df2f7989"
+ },
+ "Group 9.png": {
+ "slug": "group-9.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/group-9.png",
+ "hash": "0cf6aa2a5ccb13d39e48dba24588a05fe0092ea72cb3b10ceb0b23f6fca15160"
+ },
+ "Images Slidedeck 1 (1).png": {
+ "slug": "images-slidedeck-1-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/images-slidedeck-1-1.png",
+ "hash": "18df2cf3ddda651a3df5e566d6f91c9773dc140f73cc77c362a426d1f8d659e4"
+ },
+ "Images Slidedeck 1 (2).png": {
+ "slug": "images-slidedeck-1-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/images-slidedeck-1-2.png",
+ "hash": "89c94b87e11de0b07b6ae7c4867532656bfff50afcff613f8bc07d2bc88f14de"
+ },
+ "Images Slidedeck 1 (3).png": {
+ "slug": "images-slidedeck-1-3.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/images-slidedeck-1-3.png",
+ "hash": "9c3df0fb2728833cb7e0e6db63475b02cac6481e0eec110915fbdb22aa55becc"
+ },
+ "Images Slidedeck 1.png": {
+ "slug": "images-slidedeck-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/images-slidedeck-1.png",
+ "hash": "df1cf9386aea56296645c074fbc2f2f9071a622596a226b5a2e5aeb5ad8e039e"
+ },
+ "Images in text (1).png": {
+ "slug": "images-in-text-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/images-in-text-1.png",
+ "hash": "ac09fa02c3578cf5cbdeb995ac90b8bc1b629405769e78ceb12456341685460c"
+ },
+ "Inclusive (3).png": {
+ "slug": "inclusive-3.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/inclusive-3.png",
+ "hash": "e47253958d92a798447df531fede561ee04769d4a100c0579ba9d9cd08bde0df"
+ },
+ "Intent and virtual intents.png": {
+ "slug": "intent-and-virtual-intents.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/intent-and-virtual-intents.png",
+ "hash": "a08de064139ae4ac7b4b16c2829e24ba0ce8d0e6928e972777f25bbbb85cf2de"
+ },
+ "Interface elements.png": {
+ "slug": "interface-elements.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/interface-elements.png",
+ "hash": "f827b5ad0eb44d9865c6b70c6f6acd0d311e2db111a007147c5878e61f2738f9"
+ },
+ "Knowledge Base Demo.gif": {
+ "slug": "knowledge-base-demo.mp4",
+ "kind": "video",
+ "destination": "public/media",
+ "reference": "/media/knowledge-base-demo.mp4",
+ "hash": "8a62cb1b8bf749d681eeaff569e01589072b0319aabd17f51b999933d06c8a05"
+ },
+ "L3-Levels 1.png": {
+ "slug": "l3-levels-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/l3-levels-1.png",
+ "hash": "50d421dced3fdf2a70f8a323c23924392ba796dc92d705b08cd2a59f5df35ea1"
+ },
+ "LLMAction_Setup (1).png": {
+ "slug": "llmaction-setup-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/llmaction-setup-1.png",
+ "hash": "06f1b005125c3f7a9de9fe79ae83aa2810a608688dc070dfb9aa3d9f0a84690e"
+ },
+ "LLMAction_basicprompt config with attributes.png": {
+ "slug": "llmaction-basicprompt-config-with-attributes.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/llmaction-basicprompt-config-with-attributes.png",
+ "hash": "6247b5a969bf08bf060c57b520e3366772dac576935449aff06f402fe3e87d3c"
+ },
+ "LLMAction_basicprompt config.png": {
+ "slug": "llmaction-basicprompt-config.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/llmaction-basicprompt-config.png",
+ "hash": "f01ce2233c97931456339b715099468e37a4b3e467f364a333c3eb329c869c04"
+ },
+ "LLMActions_AdvancedSettings.png": {
+ "slug": "llmactions-advancedsettings.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/llmactions-advancedsettings.png",
+ "hash": "5d605ea231e9f87743dbbd70376e61b00d9797996cf784d9baca6e5ab63b9aa1"
+ },
+ "LLMActions_AttributesforReuse - 1.png": {
+ "slug": "llmactions-attributesforreuse-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/llmactions-attributesforreuse-1.png",
+ "hash": "6f7392e97aa285535e773447ad46cbffa4812de59e7218b5d1a5f17bc399f837"
+ },
+ "LLMActions_AttributesforReuse -2 - in Messages.png": {
+ "slug": "llmactions-attributesforreuse-2-in-messages.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/llmactions-attributesforreuse-2-in-messages.png",
+ "hash": "28821ea3807be87616427be87819b591a806021201fac049734e678a24122fed"
+ },
+ "LLMActions_TestPanel.png": {
+ "slug": "llmactions-testpanel.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/llmactions-testpanel.png",
+ "hash": "48a0920fb1581eba5df203632b8c970a771a8ff76e3c75cc6b597e89791eb359"
+ },
+ "LLMActions_safeguarding.png": {
+ "slug": "llmactions-safeguarding.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/llmactions-safeguarding.png",
+ "hash": "da75340403c8986b8f0bbe21db92cd11e634d77e5866fb893106b5414ff00ea8"
+ },
+ "New waiting time (1).gif": {
+ "slug": "new-waiting-time-1.gif",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/new-waiting-time-1.gif",
+ "hash": "655158f1c0ab72276ae50f6a630244d72613bffc7d5d0334667d137ee4af6987"
+ },
+ "Null alt tag (1).png": {
+ "slug": "null-alt-tag-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/null-alt-tag-1.png",
+ "hash": "6076eb924fc29b951161f0255a5bd35f56373d237ab40a22aafe942e7e32276f"
+ },
+ "OD-basicmodel.png": {
+ "slug": "od-basicmodel.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/od-basicmodel.png",
+ "hash": "d09899e88d7c897d0ab3daefd3f41cec0008a3cc635d8c79dccb151e2a1e600d"
+ },
+ "OD-workspacecreatenew.png": {
+ "slug": "od-workspacecreatenew.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/od-workspacecreatenew.png",
+ "hash": "c9c6b81d948400ec32fd1ca39adb7515f001f31ca3d466f3a80ee0af30110c7b"
+ },
+ "OD-workspacedashboard.png": {
+ "slug": "od-workspacedashboard.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/od-workspacedashboard.png",
+ "hash": "67e4ed1df946afad6a6e8cbc168161b206849e2b8cf143cb4c8c82c6521b2657"
+ },
+ "OD-workspacenavigation.png": {
+ "slug": "od-workspacenavigation.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/od-workspacenavigation.png",
+ "hash": "17ba3422cf4d8bd0ccf7d7ca6df413923e9ae1703c976babd4197b2128296ef1"
+ },
+ "Pick a date and time.png": {
+ "slug": "pick-a-date-and-time.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/pick-a-date-and-time.png",
+ "hash": "746e4f4a2fcc77a713e1109db0fb24234c3c06eb3a8d72109cf935d810ae0cfc"
+ },
+ "Pick a time.png": {
+ "slug": "pick-a-time.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/pick-a-time.png",
+ "hash": "aee5cee6bb6ce465cc324cfe1c6658192866eccb7d25fd6d78d4f27492bdfb84"
+ },
+ "Pick a year and month.png": {
+ "slug": "pick-a-year-and-month.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/pick-a-year-and-month.png",
+ "hash": "1bc4ca94f6c24bab7ede64811c524b8ca704cb31153e18b89ae81921273d37f2"
+ },
+ "Pick a year.png": {
+ "slug": "pick-a-year.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/pick-a-year.png",
+ "hash": "59bb51d758c2a4df38f51a8183c75853eb02459dc8f7a69e95743b10ca55376c"
+ },
+ "Placeholders (1).png": {
+ "slug": "placeholders-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/placeholders-1.png",
+ "hash": "56feb1c0d4011b23711e7cf894d9b08e173df600c9264f3c4a935f2d327e5aaf"
+ },
+ "Preview Attribute.jpg": {
+ "slug": "preview-attribute.jpg",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/preview-attribute.jpg",
+ "hash": "431379fbce61e6bac80078ada896d54ba15648fd5284c3bfbe9e3530943e63bf"
+ },
+ "Preview Considered Path.jpg": {
+ "slug": "preview-considered-path.jpg",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/preview-considered-path.jpg",
+ "hash": "06dcb483267545da8427341fd1a0ec4d304b28f2b2ba22a9738af763e42c9aff"
+ },
+ "Preview Main (1).jpg": {
+ "slug": "preview-main-1.jpg",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/preview-main-1.jpg",
+ "hash": "b18c9bb764ede1baf5f914e79d7fba55ada823c84159be7ab88998a56de7ff23"
+ },
+ "Preview Selected Path.jpg": {
+ "slug": "preview-selected-path.jpg",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/preview-selected-path.jpg",
+ "hash": "26b30db52b3816b0b5657ead2aca76ad2f622a20c7d79c3c2980550be0920613"
+ },
+ "Preview Sidebar.jpg": {
+ "slug": "preview-sidebar.jpg",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/preview-sidebar.jpg",
+ "hash": "39d7187f586a68997c1963b2c40099cd2cae50c0e8300af7a5089cc005764969"
+ },
+ "RAG-LLMactions.png": {
+ "slug": "rag-llmactions.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/rag-llmactions.png",
+ "hash": "f4db0dedf58021baf9ed4504f17acdafe13bab847e719713b7e0f2ecf3282fae"
+ },
+ "RAG-diagram.png": {
+ "slug": "rag-diagram.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/rag-diagram.png",
+ "hash": "c653cbfbb5558e5d44c46b9cd74c5ebb2422cfd9cf97876d97a511884f7f6848"
+ },
+ "RAG-overview.png": {
+ "slug": "rag-overview.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/rag-overview.png",
+ "hash": "2f226ed8313d2e5a0846e6f816796b0e79450c7a360e8951372494e10a9e4ebc"
+ },
+ "RAG-response.png": {
+ "slug": "rag-response.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/rag-response.png",
+ "hash": "8f4c5c345ce43e50ea7c03016df33edd4102127e6e69e747b1066b750e1f36a5"
+ },
+ "RAG-settings-use.png": {
+ "slug": "rag-settings-use.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/rag-settings-use.png",
+ "hash": "e09c8f1e1d58f3638398b21f811a3c2d7cdcfc9d1136e25204a9a9da82297520"
+ },
+ "RAG-vectorisation.png": {
+ "slug": "rag-vectorisation.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/rag-vectorisation.png",
+ "hash": "234ac549400558d089712d2d80892ab9f06ad06bede715f269ea84f087eeb9de"
+ },
+ "Scenes.png": {
+ "slug": "scenes.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/scenes.png",
+ "hash": "068a3ff219ecd88201f8f30821aa671b99528acd2876a357113bd36d387d63a1"
+ },
+ "Screen Shot 2022-02-17 at 11.15.00 AM.png": {
+ "slug": "screen-shot-2022-02-17-at-11-15-00-am.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screen-shot-2022-02-17-at-11-15-00-am.png",
+ "hash": "d5f58e3329d803cee354d6de0ad7dfd8743497fe9b69031d7445ac8af95a7142"
+ },
+ "Screenshot 2021-11-01 at 09.19.03.png": {
+ "slug": "screenshot-2021-11-01-at-09-19-03.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2021-11-01-at-09-19-03.png",
+ "hash": "8b5f94ed407ed1abb654eaebfd23a72cb62dc22721a1d6551c94a48c1ca7bbd5"
+ },
+ "Screenshot 2021-11-01 at 09.22.33.png": {
+ "slug": "screenshot-2021-11-01-at-09-22-33.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2021-11-01-at-09-22-33.png",
+ "hash": "dea491464b2e7d4b04f3bd75d960ef0103714dd43fa5c09e632eccb1f5c112be"
+ },
+ "Screenshot 2021-11-01 at 09.24.03.png": {
+ "slug": "screenshot-2021-11-01-at-09-24-03.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2021-11-01-at-09-24-03.png",
+ "hash": "7a7468323f800dd5fd67cb22e88801fe3bfee7f7a1f1368ba1d62791a3d1bcce"
+ },
+ "Screenshot 2021-11-01 at 09.28.03.png": {
+ "slug": "screenshot-2021-11-01-at-09-28-03.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2021-11-01-at-09-28-03.png",
+ "hash": "82e5da8363fa47f4c6b0050d59c1eab43f6c0100058abc88504a3f7967b93574"
+ },
+ "Screenshot 2021-11-01 at 09.32.48.png": {
+ "slug": "screenshot-2021-11-01-at-09-32-48.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2021-11-01-at-09-32-48.png",
+ "hash": "7d4edf964121a97a1b03d482543d0343032e6472a9c6933749f7b6627df40495"
+ },
+ "Screenshot 2021-11-01 at 09.38.44.png": {
+ "slug": "screenshot-2021-11-01-at-09-38-44.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2021-11-01-at-09-38-44.png",
+ "hash": "60b10945105aa873519541335e031d22404ea9c0ab11245ee38941a5c34f7fb2"
+ },
+ "Screenshot 2021-11-01 at 09.42.01.png": {
+ "slug": "screenshot-2021-11-01-at-09-42-01.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2021-11-01-at-09-42-01.png",
+ "hash": "66b326af1681f02ab9c594044102d8bb66de6da83f5f8e16bf3b4f857040ed82"
+ },
+ "Screenshot 2021-11-01 at 09.42.38 (1).png": {
+ "slug": "screenshot-2021-11-01-at-09-42-38-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2021-11-01-at-09-42-38-1.png",
+ "hash": "614eb596109a5853ad4d03d625930782bf434a593b9eb590b1e1bc3c4c5d5a2c"
+ },
+ "Screenshot 2023-05-11 at 13.01.33.png": {
+ "slug": "screenshot-2023-05-11-at-13-01-33.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-05-11-at-13-01-33.png",
+ "hash": "8bed4c7b780037e01074bd6f5031cd3e0d8b2ff878930c3dd2f4150e698aecfe"
+ },
+ "Screenshot 2023-05-11 at 13.11.46.png": {
+ "slug": "screenshot-2023-05-11-at-13-11-46.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-05-11-at-13-11-46.png",
+ "hash": "080b51bc7b19840caab76b4954a9cee5921ea751a00363aec6a22cc2d85930c2"
+ },
+ "Screenshot 2023-05-11 at 13.12.57.png": {
+ "slug": "screenshot-2023-05-11-at-13-12-57.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-05-11-at-13-12-57.png",
+ "hash": "15a8913898c252241f0892d5a5b1b9684b6e4b0fae42a11b7eff06b2d30d5055"
+ },
+ "Screenshot 2023-05-11 at 14.33.04.png": {
+ "slug": "screenshot-2023-05-11-at-14-33-04.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-05-11-at-14-33-04.png",
+ "hash": "cb2c962e7dfae7ef08ce5a9f1b9491a52b3394ce967a9eb65524f03a87595db7"
+ },
+ "Screenshot 2023-05-11 at 14.52.54.png": {
+ "slug": "screenshot-2023-05-11-at-14-52-54.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-05-11-at-14-52-54.png",
+ "hash": "c9c70adfed6ac283a70818ac0629c35c2c381492df8305e20b261e629fd6b784"
+ },
+ "Screenshot 2023-05-11 at 14.54.32.png": {
+ "slug": "screenshot-2023-05-11-at-14-54-32.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-05-11-at-14-54-32.png",
+ "hash": "41babf1eaeb06ff93570eee257a9763f37e1b7b1319afb22d50e37641db7cf82"
+ },
+ "Screenshot 2023-05-11 at 14.54.46.png": {
+ "slug": "screenshot-2023-05-11-at-14-54-46.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-05-11-at-14-54-46.png",
+ "hash": "0c297fa03013f3d29b2f1b743f0ce2cf1fdbfeed6d5be407607b8a545ba2a94c"
+ },
+ "Screenshot 2023-05-11 at 18.20.26.png": {
+ "slug": "screenshot-2023-05-11-at-18-20-26.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-05-11-at-18-20-26.png",
+ "hash": "d1768fe16d3b20602d6a16448881f41fc761d1eb76abe3c62cd80ffd09968f40"
+ },
+ "Screenshot 2023-05-26 110829.png": {
+ "slug": "screenshot-2023-05-26-110829.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-05-26-110829.png",
+ "hash": "f4031b8fdfebd337596cddc612ea4109d2e6ed9754dec75470418cd8a360be4f"
+ },
+ "Screenshot 2023-05-26 111039.png": {
+ "slug": "screenshot-2023-05-26-111039.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-05-26-111039.png",
+ "hash": "044ea67052ff65e93d0d6ff60c5f6cf7387d8d6a1db71dea25402eec65548733"
+ },
+ "Screenshot 2023-05-26 at 12.51.54.png": {
+ "slug": "screenshot-2023-05-26-at-12-51-54.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-05-26-at-12-51-54.png",
+ "hash": "56b99134e137ffa8793c96b89a5736c16795087c84df224335c0a8135634241a"
+ },
+ "Screenshot 2023-05-26 at 12.59.19.png": {
+ "slug": "screenshot-2023-05-26-at-12-59-19.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-05-26-at-12-59-19.png",
+ "hash": "9f28729de779efa10893a0a100775c5699d8ae0abd23cdd44d3b9a015d60370b"
+ },
+ "Screenshot 2023-05-26 at 13.05.41.png": {
+ "slug": "screenshot-2023-05-26-at-13-05-41.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-05-26-at-13-05-41.png",
+ "hash": "05acb55663e662306316858f0c7acb25be53a9e99c296c88f2fdcca3fc8cf6d4"
+ },
+ "Screenshot 2023-05-26 at 14.16.37.png": {
+ "slug": "screenshot-2023-05-26-at-14-16-37.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-05-26-at-14-16-37.png",
+ "hash": "e77b8dffe29c9452381b7cf44ea13aa1b49bff4c7c08e0a77b92e7527ce6754d"
+ },
+ "Screenshot 2023-05-31 at 16.18.00.png": {
+ "slug": "screenshot-2023-05-31-at-16-18-00.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-05-31-at-16-18-00.png",
+ "hash": "05409d31405e0ecae5d772446ca86623425a628829635c35af03c0f4ac1aab5b"
+ },
+ "Screenshot 2023-06-01 at 10.05.01.png": {
+ "slug": "screenshot-2023-06-01-at-10-05-01.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-06-01-at-10-05-01.png",
+ "hash": "2deb6c3298610d5f981f568d846b61090113b0215b7f096f103488e30113a6f1"
+ },
+ "Screenshot 2023-06-02 at 10.02.49.png": {
+ "slug": "screenshot-2023-06-02-at-10-02-49.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-06-02-at-10-02-49.png",
+ "hash": "c159993730a97bcc44363996adc87efe4f808e17993ee8c158f37f88bd217872"
+ },
+ "Screenshot 2023-07-28 at 16.26.42.png": {
+ "slug": "screenshot-2023-07-28-at-16-26-42.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-07-28-at-16-26-42.png",
+ "hash": "549eb99430a960c1711bd1fa886fe41b82a96c30ca05d3f242fb02886146da8b"
+ },
+ "Screenshot 2023-10-25 at 12.13.26.png": {
+ "slug": "screenshot-2023-10-25-at-12-13-26.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-10-25-at-12-13-26.png",
+ "hash": "430bbab83a3f2717f68a2f1bf522a3ba33b032bfac38a1b992a7cb7d6878f50a"
+ },
+ "Screenshot 2023-12-20 at 14.19.39 (1).png": {
+ "slug": "screenshot-2023-12-20-at-14-19-39-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2023-12-20-at-14-19-39-1.png",
+ "hash": "2ef2c905e4a77dfef874ed1747590ef4bca8d49d23209896057bef7019f81229"
+ },
+ "Screenshot 2024-01-09 at 09.56.45.png": {
+ "slug": "screenshot-2024-01-09-at-09-56-45.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-01-09-at-09-56-45.png",
+ "hash": "0b66f399f6eccd8157e2dc37894539901bc9b4a094bb7fd520a8492f37f839e9"
+ },
+ "Screenshot 2024-01-09 at 09.58.23.png": {
+ "slug": "screenshot-2024-01-09-at-09-58-23.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-01-09-at-09-58-23.png",
+ "hash": "433abffba44e77d1167d21f43accdd02423b542e8ebda5b44649a2ddad5c965f"
+ },
+ "Screenshot 2024-02-27 at 09.18.27.png": {
+ "slug": "screenshot-2024-02-27-at-09-18-27.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-02-27-at-09-18-27.png",
+ "hash": "229842d99d19a5726e199ad80da7ef53586bb63030751779a93a70369b277fdb"
+ },
+ "Screenshot 2024-02-27 at 11.21.09.png": {
+ "slug": "screenshot-2024-02-27-at-11-21-09.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-02-27-at-11-21-09.png",
+ "hash": "f84e372155a8b5412e5cca75acef8e3f4ad41076619ac06bd7f090c927e2aaaf"
+ },
+ "Screenshot 2024-02-27 at 11.22.29.png": {
+ "slug": "screenshot-2024-02-27-at-11-22-29.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-02-27-at-11-22-29.png",
+ "hash": "d9b3a6b56cd2cb11e14e4ea1dc08d39d41f4b3ac6272cf632cfc7d59748741a9"
+ },
+ "Screenshot 2024-02-27 at 11.22.41.png": {
+ "slug": "screenshot-2024-02-27-at-11-22-41.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-02-27-at-11-22-41.png",
+ "hash": "5ea3d6257b05fc23b1e5c994dfdf7202ac10b8c8710b70dd642ffdd12bad7612"
+ },
+ "Screenshot 2024-02-27 at 11.24.56.png": {
+ "slug": "screenshot-2024-02-27-at-11-24-56.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-02-27-at-11-24-56.png",
+ "hash": "3da9262602d074e4d196adc604cf045ed738475ec3df742ad3bece24cb4ead59"
+ },
+ "Screenshot 2024-02-27 at 11.26.11.png": {
+ "slug": "screenshot-2024-02-27-at-11-26-11.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-02-27-at-11-26-11.png",
+ "hash": "1cc05fc900db82484bd21d384648d0ed8e051d2eb33b70fabfb5b66939dc3cf9"
+ },
+ "Screenshot 2024-02-27 at 12.58.47.png": {
+ "slug": "screenshot-2024-02-27-at-12-58-47.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-02-27-at-12-58-47.png",
+ "hash": "b63ca06007542b632d2fc4607bf47b8f94c6d190070329db4f4aa90abb132434"
+ },
+ "Screenshot 2024-03-27 at 08.40.11.png": {
+ "slug": "screenshot-2024-03-27-at-08-40-11.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-03-27-at-08-40-11.png",
+ "hash": "5f448b063eec59591df5cc4c2f863892a3e8acc2da19b078b70ae14939db1249"
+ },
+ "Screenshot 2024-04-25 at 22.56.32.png": {
+ "slug": "screenshot-2024-04-25-at-22-56-32.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-04-25-at-22-56-32.png",
+ "hash": "b56f03ff20768b3ef00ed713e53e037b6ff8d4b8d7cad8a922fac62bdc5c9b49"
+ },
+ "Screenshot 2024-04-28 at 10.15.32.png": {
+ "slug": "screenshot-2024-04-28-at-10-15-32.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-04-28-at-10-15-32.png",
+ "hash": "3ae0be2a6311b3f2b0bd42fc6bb72a7c3bd67236144dc2a70743d44bc76d0619"
+ },
+ "Screenshot 2024-04-29 at 07.48.11.png": {
+ "slug": "screenshot-2024-04-29-at-07-48-11.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-04-29-at-07-48-11.png",
+ "hash": "2eaf3e416e16e374c843d056f6d0e410b7ae17c77c333de85fc17f692a460e8c"
+ },
+ "Screenshot 2024-06-04 at 10.14.39.png": {
+ "slug": "screenshot-2024-06-04-at-10-14-39.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-06-04-at-10-14-39.png",
+ "hash": "144ef58dc45796dd73f4b8a575e67c95749236bb3114add3c5fb19ce2820ac75"
+ },
+ "Screenshot 2024-06-04 at 10.18.10.png": {
+ "slug": "screenshot-2024-06-04-at-10-18-10.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-06-04-at-10-18-10.png",
+ "hash": "82d21ddac7c25cb292da6167c92dbdc88dbae6cac747183d5daf0fe2b2b989cf"
+ },
+ "Screenshot 2024-06-04 at 10.31.07.png": {
+ "slug": "screenshot-2024-06-04-at-10-31-07.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-06-04-at-10-31-07.png",
+ "hash": "730ee0fb8d70ed18f4543d3548d740ebc72a623217747c06b5de2c243d88d9db"
+ },
+ "Screenshot 2024-06-04 at 10.31.14.png": {
+ "slug": "screenshot-2024-06-04-at-10-31-14.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-06-04-at-10-31-14.png",
+ "hash": "114749bbc1be9d91d5dfc8a4026a3ebbdbe0b37d5ecfe8c61b3df852100409f1"
+ },
+ "Screenshot 2024-06-04 at 10.38.15.png": {
+ "slug": "screenshot-2024-06-04-at-10-38-15.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-06-04-at-10-38-15.png",
+ "hash": "1d5242d08d0e8165b679a471c228fd7b487bd57c86915e13698bd59a6b5f75aa"
+ },
+ "Screenshot 2024-06-04 at 11.03.22.png": {
+ "slug": "screenshot-2024-06-04-at-11-03-22.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-06-04-at-11-03-22.png",
+ "hash": "b145f0bc65831a77bc18aa3462c856820eb54613d54d97235d28468c5433cb4c"
+ },
+ "Screenshot 2024-06-04 at 11.07.11.png": {
+ "slug": "screenshot-2024-06-04-at-11-07-11.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-06-04-at-11-07-11.png",
+ "hash": "617d5c93b514e0aa0a946f5b5583a4fcc9f93e4225bb93e147cd4977db82df13"
+ },
+ "Screenshot 2024-06-04 at 11.08.49.png": {
+ "slug": "screenshot-2024-06-04-at-11-08-49.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-06-04-at-11-08-49.png",
+ "hash": "97dee4e57917daf0f8c087256700747ffed0eb278c117d32c9fe26785e11728f"
+ },
+ "Screenshot 2024-06-04 at 11.25.53.png": {
+ "slug": "screenshot-2024-06-04-at-11-25-53.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-06-04-at-11-25-53.png",
+ "hash": "04b1ebc1dd8f0c6f7c8b0a2dbe65065cd58975ec0639fb39f9a97272d43c521d"
+ },
+ "Screenshot 2024-06-04 at 11.26.02.png": {
+ "slug": "screenshot-2024-06-04-at-11-26-02.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-06-04-at-11-26-02.png",
+ "hash": "b041b0e9347baf82858471def8e2f6b96b846fdec124c4a443555cf05d1371b1"
+ },
+ "Screenshot 2024-06-05 at 13.47.08.png": {
+ "slug": "screenshot-2024-06-05-at-13-47-08.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-06-05-at-13-47-08.png",
+ "hash": "38bba498c1742bce372ca9b2b09f4c9bdd36c35682f182646461077bc34cdcb2"
+ },
+ "Screenshot 2024-06-05 at 15.36.41.png": {
+ "slug": "screenshot-2024-06-05-at-15-36-41.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-06-05-at-15-36-41.png",
+ "hash": "39f95415739e7c0bc76e5b9419b586fa943c2e36f0a422c450c206294593742a"
+ },
+ "Screenshot 2024-07-08 at 18.05.09.png": {
+ "slug": "screenshot-2024-07-08-at-18-05-09.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-07-08-at-18-05-09.png",
+ "hash": "fde3a616fcecd0d6bd5ece628c82c2cacc79a53f401106cd53a5b3940000694a"
+ },
+ "Screenshot 2024-07-08 at 18.21.46.png": {
+ "slug": "screenshot-2024-07-08-at-18-21-46.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-07-08-at-18-21-46.png",
+ "hash": "8ace5c7842101de165745dfbf34c49caaff4453d9f41bdb5c86b18913e2d054c"
+ },
+ "Screenshot 2024-07-08 at 18.25.21.png": {
+ "slug": "screenshot-2024-07-08-at-18-25-21.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-07-08-at-18-25-21.png",
+ "hash": "2673ac1f452bfdd8ba0b4915c135334550699f72718c6cc59673946d9c1b85a8"
+ },
+ "Screenshot 2024-07-08 at 18.30.02.png": {
+ "slug": "screenshot-2024-07-08-at-18-30-02.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-07-08-at-18-30-02.png",
+ "hash": "eab190caded7bd2bd331ffa6d1ceefd492d3f763c0519c6b32fba1777f8c4712"
+ },
+ "Screenshot 2024-07-09 at 09.52.58 (1).png": {
+ "slug": "screenshot-2024-07-09-at-09-52-58-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-07-09-at-09-52-58-1.png",
+ "hash": "23df9967fa462a5dca343c3214289ca34a45fe7b7104eecb39db2d21ef495927"
+ },
+ "Screenshot 2024-07-09 at 09.52.58.png": {
+ "slug": "screenshot-2024-07-09-at-09-52-58.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-07-09-at-09-52-58.png",
+ "hash": "23df9967fa462a5dca343c3214289ca34a45fe7b7104eecb39db2d21ef495927"
+ },
+ "Screenshot 2024-08-12 at 14.26.34.png": {
+ "slug": "screenshot-2024-08-12-at-14-26-34.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-08-12-at-14-26-34.png",
+ "hash": "3d46f923daed5ad8ad0cbee67f87d78bfb3ac0a8b9297ed799b127ba5f225c07"
+ },
+ "Screenshot 2024-08-23 at 15.30.55.png": {
+ "slug": "screenshot-2024-08-23-at-15-30-55.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-08-23-at-15-30-55.png",
+ "hash": "a2a5c5e8166910d80e23381fe73a323bca5898dfe3be3b61a67c29cf2473a3b4"
+ },
+ "Screenshot 2024-08-23 at 15.40.04.png": {
+ "slug": "screenshot-2024-08-23-at-15-40-04.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-08-23-at-15-40-04.png",
+ "hash": "599f93074c076c22d50b854674652c657a0487411d8cc2a559a9bdfb48fce6e9"
+ },
+ "Screenshot 2024-09-03 at 13.04.59.png": {
+ "slug": "screenshot-2024-09-03-at-13-04-59.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-09-03-at-13-04-59.png",
+ "hash": "84ec8fe5f66617df924354f8779b32f4d110aad84fd959d799ca505623b5e7c8"
+ },
+ "Screenshot 2024-09-26 at 10.28.52.png": {
+ "slug": "screenshot-2024-09-26-at-10-28-52.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-09-26-at-10-28-52.png",
+ "hash": "25656705d455263eb56191c3abaea2ac1dc03c953f4d11ff0c1457b6f5d3c262"
+ },
+ "Screenshot 2024-09-26 at 10.32.32.png": {
+ "slug": "screenshot-2024-09-26-at-10-32-32.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-09-26-at-10-32-32.png",
+ "hash": "6a63313d19e4789a205043ca81f4e3bad200a9598897f1b2bb2e69f52f9ec510"
+ },
+ "Screenshot 2024-09-26 at 10.38.51.png": {
+ "slug": "screenshot-2024-09-26-at-10-38-51.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-09-26-at-10-38-51.png",
+ "hash": "5624c52dcf4a823d47f7992ea1b4283e931ef5133398037f2945a1e8446f8ce3"
+ },
+ "Screenshot 2024-10-01 at 15.28.40.png": {
+ "slug": "screenshot-2024-10-01-at-15-28-40.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-10-01-at-15-28-40.png",
+ "hash": "d67f4b3cd5595466e1ca1291e03f823eee0e6bfb784fd47847a697fe37dfbec3"
+ },
+ "Screenshot 2024-10-01 at 15.31.13.png": {
+ "slug": "screenshot-2024-10-01-at-15-31-13.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-10-01-at-15-31-13.png",
+ "hash": "df7c5641af5cf22cf15670bd1c424ef1cca0282b97d8916d823fad460a68b5d4"
+ },
+ "Screenshot 2024-10-01 at 15.31.33.png": {
+ "slug": "screenshot-2024-10-01-at-15-31-33.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-10-01-at-15-31-33.png",
+ "hash": "e495a174c08cd7c380b04451ffe291c5bb944d67d72fab8091e61f2661aee77c"
+ },
+ "Screenshot 2024-10-01 at 15.32.22.png": {
+ "slug": "screenshot-2024-10-01-at-15-32-22.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-10-01-at-15-32-22.png",
+ "hash": "2308c44e5ed1163c8829b98ba9d74314153f8f9fb773d8d2d52ec71ff6db96e2"
+ },
+ "Screenshot 2024-11-09 at 11.35.40.png": {
+ "slug": "screenshot-2024-11-09-at-11-35-40.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-11-09-at-11-35-40.png",
+ "hash": "e497da1bbe56d4a3e4c3a0e9b310642f92eaa46f9387ff8ec6104e242e2129cd"
+ },
+ "Screenshot 2024-11-09 at 18.23.33.png": {
+ "slug": "screenshot-2024-11-09-at-18-23-33.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-11-09-at-18-23-33.png",
+ "hash": "37010ee315c7276642b29996f086d55cc7d8d1cc52656401d19073f9e7fac0c6"
+ },
+ "Screenshot 2024-11-09 at 18.24.23.png": {
+ "slug": "screenshot-2024-11-09-at-18-24-23.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-11-09-at-18-24-23.png",
+ "hash": "cf0315b72bf2a5c274269eace95131886c08c5e481298e472c0531523d54bb58"
+ },
+ "Screenshot 2024-11-09 at 18.28.28.png": {
+ "slug": "screenshot-2024-11-09-at-18-28-28.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-11-09-at-18-28-28.png",
+ "hash": "1c3932fe675ad492de1cfdf9ee6488452101c67122b42bbb93af25fd471e055a"
+ },
+ "Screenshot 2024-11-09 at 18.33.30.png": {
+ "slug": "screenshot-2024-11-09-at-18-33-30.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-11-09-at-18-33-30.png",
+ "hash": "ea9eb8eebd1d2121740914eff80ce1417cbe124b873c037566577d880b09b8c3"
+ },
+ "Screenshot 2024-11-09 at 18.35.20 (1).png": {
+ "slug": "screenshot-2024-11-09-at-18-35-20-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-11-09-at-18-35-20-1.png",
+ "hash": "532b7852537b1359d7215b3bbbfe4ba13627eda9233e8d58ae7bccffe96ebcd9"
+ },
+ "Screenshot 2024-11-09 at 18.43.42.png": {
+ "slug": "screenshot-2024-11-09-at-18-43-42.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-11-09-at-18-43-42.png",
+ "hash": "91dbf7422669f19be11d2b5474ffbd684932b25918157bfe1c24510522f487a8"
+ },
+ "Screenshot 2024-11-29 at 14.07.49.png": {
+ "slug": "screenshot-2024-11-29-at-14-07-49.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2024-11-29-at-14-07-49.png",
+ "hash": "18a938b213ac20c1aa19047830237175f11b54aec2c98ec69677f03f7d609a49"
+ },
+ "Screenshot 2025-03-06 at 11.09.33 (1).png": {
+ "slug": "screenshot-2025-03-06-at-11-09-33-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2025-03-06-at-11-09-33-1.png",
+ "hash": "6131b5bb4f0d3206c768b1a56ebeb53fa5c25fc56e755813443e552889a1e60c"
+ },
+ "Screenshot 2025-07-11 at 11.59.08.png": {
+ "slug": "screenshot-2025-07-11-at-11-59-08.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2025-07-11-at-11-59-08.png",
+ "hash": "ad447a567eb28165ee440c34d6add2f8bef7e42126fdf85c5ef1ab5cc5a5b3b3"
+ },
+ "Screenshot 2025-07-11 at 16.48.00.png": {
+ "slug": "screenshot-2025-07-11-at-16-48-00.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2025-07-11-at-16-48-00.png",
+ "hash": "6ec615d444f07af36e3bda02718d117910cfed0d1d29ee4360ac90494b716e80"
+ },
+ "Screenshot 2025-07-11 at 17.09.31.png": {
+ "slug": "screenshot-2025-07-11-at-17-09-31.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2025-07-11-at-17-09-31.png",
+ "hash": "d7ab07616e3e3c8cb85eb6745e282a961e6baf98aab694005093aa3360677053"
+ },
+ "Screenshot 2025-11-03 at 13.25.37.png": {
+ "slug": "screenshot-2025-11-03-at-13-25-37.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2025-11-03-at-13-25-37.png",
+ "hash": "8bb74ffd3c2992ef15ba905252c55d6b5920cb5baec300b6fb91e7688481e81f"
+ },
+ "Screenshot 2026-01-08 at 15.53.37.png": {
+ "slug": "screenshot-2026-01-08-at-15-53-37.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2026-01-08-at-15-53-37.png",
+ "hash": "a57c7248c1fe04d36221133e2f1862918b7661925a738b683dd3516bf5a31892"
+ },
+ "Screenshot 2026-01-08 at 16.33.54.png": {
+ "slug": "screenshot-2026-01-08-at-16-33-54.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screenshot-2026-01-08-at-16-33-54.png",
+ "hash": "08f8098d2f973e9e3e5cdbf3c7a790e6ba1265c822e981e548d834c8e307f0d4"
+ },
+ "Search_Message.png": {
+ "slug": "search-message.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/search-message.png",
+ "hash": "78e51e0eba45569a68ac350aa3cd49097d026440ac622f63f15c956475def274"
+ },
+ "Search_Scenario_View.png": {
+ "slug": "search-scenario-view.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/search-scenario-view.png",
+ "hash": "d6027f024964c47560007a616057237e59dd6e4773907594b1fcc6d42875c7cd"
+ },
+ "Select source type.png": {
+ "slug": "select-source-type.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/select-source-type.png",
+ "hash": "e4600bff98b565a0d1a13cc406208b6b89ab875e035d6a831ead2ff87dfc2c9b"
+ },
+ "Sensory (2).png": {
+ "slug": "sensory-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/sensory-2.png",
+ "hash": "04eebf9d31ed3833c11b87fd1a1a1eb61d136ef95bf62d3c4adfa6659e7b6659"
+ },
+ "Text.png": {
+ "slug": "text.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/text.png",
+ "hash": "cbe2e41c481abc4af571cbb64c8045e6f04ebc549975a6affb1ad6eaee07672e"
+ },
+ "Translate_languageselection.png": {
+ "slug": "translate-languageselection.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/translate-languageselection.png",
+ "hash": "a30c6a6c908e0fb1bfed9762a2bdc4db934701aa45bb29d57faa60ad815331ab"
+ },
+ "URL 1.png": {
+ "slug": "url-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/url-1.png",
+ "hash": "d03fb6a837eea4d4d9a64be5be79277c19489c1e25d9d2c3c718a70d5b55c8db"
+ },
+ "URL 2.png": {
+ "slug": "url-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/url-2.png",
+ "hash": "088d76f90d4096093d0ae8e0b4d92fc6716bc7ea1bb13fec26fb69085f25c89b"
+ },
+ "URL 3.png": {
+ "slug": "url-3.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/url-3.png",
+ "hash": "3fdde823eeb8026024f9ecef7a3936463ef807aed574c65e25c604e1e46eb701"
+ },
+ "URL 4.png": {
+ "slug": "url-4.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/url-4.png",
+ "hash": "ba822907908cd674da3f5a04b9c0db7b7421011ac80f29ba0ae5a7d5a2ae89c3"
+ },
+ "Untitled.png": {
+ "slug": "untitled.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/untitled.png",
+ "hash": "bacc2c326da2059cec9c60a0c7877a8c642d2b9b722e8399b9c32bbfd04ccfda"
+ },
+ "Zrzut ekranu 2025-11-3 o 14.37.53.png": {
+ "slug": "zrzut-ekranu-2025-11-3-o-14-37-53.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/zrzut-ekranu-2025-11-3-o-14-37-53.png",
+ "hash": "2089734b4be735246a9313324bdb989a7cf014e00caa720a2fe1a4ffd19d2b42"
+ },
+ "Zrzut ekranu 2025-11-3 o 14.48.02.png": {
+ "slug": "zrzut-ekranu-2025-11-3-o-14-48-02.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/zrzut-ekranu-2025-11-3-o-14-48-02.png",
+ "hash": "ecb51d445b15e25c21b559a05e6e49bed3c99bed75732a73070882fe605b886a"
+ },
+ "add_topic_source.png": {
+ "slug": "add-topic-source.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/add-topic-source.png",
+ "hash": "80c561c7ce9823fec0c9549b4138a139fd4bf77fd79fee52518fcdb91f5846ed"
+ },
+ "ai-agent-completed.png": {
+ "slug": "ai-agent-completed.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/ai-agent-completed.png",
+ "hash": "acd925745e016f7802bcf78e70f189abb1b1c0427ca97f20a8ad0f2130f15260"
+ },
+ "applicationdesign.png": {
+ "slug": "applicationdesign.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/applicationdesign.png",
+ "hash": "58357d6f69aefcc847ca3d06eddff899f37decf6509b66f05087a5546c87c849"
+ },
+ "authentication_mtls.png": {
+ "slug": "authentication-mtls.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/authentication-mtls.png",
+ "hash": "525583514475981a5cef586e97f0b598fdf6656885f5fc1bff3c4e14cce9899d"
+ },
+ "authentication_selection.png": {
+ "slug": "authentication-selection.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/authentication-selection.png",
+ "hash": "bb886ee72d24d701f042e52aeb610c0533d804f000febde6c031221e25478abb"
+ },
+ "authenticaton_headers.png": {
+ "slug": "authenticaton-headers.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/authenticaton-headers.png",
+ "hash": "da1661400527af88208f1a6e3b943d5bb6154c413d5d11554130940ab70eed99"
+ },
+ "certificate management.png": {
+ "slug": "certificate-management.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/certificate-management.png",
+ "hash": "7c0334788173af7290d8b1f23cd9c032fd3022f0dc47e5925d4fb29c9569088b"
+ },
+ "conditions (1).png": {
+ "slug": "conditions-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/conditions-1.png",
+ "hash": "19d2cf411ce58d29a6da55c8903afaad426b9c89c11bba39f4419fee472cd235"
+ },
+ "create_new_alias.png": {
+ "slug": "create-new-alias.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/create-new-alias.png",
+ "hash": "1f50b72b7a6ba63be33c8469b86dd351b1be86ca9a3ede15a1a852cd179cbd1f"
+ },
+ "created.png": {
+ "slug": "created.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/created.png",
+ "hash": "f1e880e2fd09aa9febd3caa5c5e2f9d025d71be13fad05c540c84e653bfd95ab"
+ },
+ "description.png": {
+ "slug": "description.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/description.png",
+ "hash": "a7185a780178523e681dfa92c8855f66c7e3cf4f19e7bb2f1234ca4e7395aa2a"
+ },
+ "design - conversation 1.png": {
+ "slug": "design-conversation-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/design-conversation-1.png",
+ "hash": "87f5d598bcdbbf710ff0a7bfe4c14ce59db7c8442bf64891bec2af207eb7e98d"
+ },
+ "design - scenario 1.png": {
+ "slug": "design-scenario-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/design-scenario-1.png",
+ "hash": "b51d7faf8059240c6f8337cea6a8085769fb8e76bd6f1ef9be49601dd72e0d49"
+ },
+ "e-sign.png": {
+ "slug": "e-sign.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/e-sign.png",
+ "hash": "c9b3813fcadbe7421b29dbb778d1308ef648664bd263c6ed6c654bec67d44388"
+ },
+ "engineer-maintenancing-ai-systems-2023-11-27-05-12-07-utc.jpg": {
+ "slug": "engineer-maintenancing-ai-systems-2023-11-27-05-12-07-utc.jpg",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/engineer-maintenancing-ai-systems-2023-11-27-05-12-07-utc.jpg",
+ "hash": "f9d9175de0787f586d87a7394b619027d2689127eab2222381e0825762ca25e8"
+ },
+ "expand-message-demo.png": {
+ "slug": "expand-message-demo.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/expand-message-demo.png",
+ "hash": "81c01cc274df7d084c820d51c132dac03c73618aefc418ef5c64cbe3c28014a3"
+ },
+ "image (1) (1) (1) (1) (1).png": {
+ "slug": "image-1-1-1-1-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-1-1-1-1-1.png",
+ "hash": "7313157173f1747a0e943659c1b7f9870f484f68635362c1ef22a83cd8a6b75a"
+ },
+ "image (1) (1) (2) (1).png": {
+ "slug": "image-1-1-2-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-1-1-2-1.png",
+ "hash": "84f8ebc7bf2e913be95a747eb40d012545a1848e13c118c164d90306c9c04b77"
+ },
+ "image (1) (1) (2).png": {
+ "slug": "image-1-1-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-1-1-2.png",
+ "hash": "1703497d3ed0eea15912ffaa7114fc6c2197962361c1dc79832be984732d606a"
+ },
+ "image (1) (1) (3) (1).png": {
+ "slug": "image-1-1-3-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-1-1-3-1.png",
+ "hash": "47df2203393a30ac7e46268619581523a0a1dd355c61dca55489439098ae9e7f"
+ },
+ "image (1) (1).png": {
+ "slug": "image-1-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-1-1.png",
+ "hash": "fd2e481f27035d4c9d69e64e15134e00ff69038aa941d7ecd70d57387218c626"
+ },
+ "image (1) (2).png": {
+ "slug": "image-1-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-1-2.png",
+ "hash": "4bf6a162c4a43660c1cbf790a2a7e2a5eb80c5b54b73962f7de2a1597da76048"
+ },
+ "image (1) (4).png": {
+ "slug": "image-1-4.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-1-4.png",
+ "hash": "b262d190d3f90f6b3bb450f03793b8461bc2c141c68c4f85369ed67c6840f98c"
+ },
+ "image (101).png": {
+ "slug": "image-101.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-101.png",
+ "hash": "f44f04551d8d3ded45890c278dfa8471adbee81252820f735da79c4870b4796a"
+ },
+ "image (149).png": {
+ "slug": "image-149.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-149.png",
+ "hash": "16d7e87fa603e8260b3f60b11389dbc9bc9fae7b71860e912eb90a781a62b24a"
+ },
+ "image (192).png": {
+ "slug": "image-192.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-192.png",
+ "hash": "7e20cc7b32c03d6cde67e0ca2bb3a2dc914a7a8d0c5fc8095b5cd4811a797707"
+ },
+ "image (2) (1) (1).png": {
+ "slug": "image-2-1-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-2-1-1.png",
+ "hash": "9ce84e2949621a53a299bd3e3b00676a9bb7d502f043359aac1fd27beba63bb2"
+ },
+ "image (2) (1).png": {
+ "slug": "image-2-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-2-1.png",
+ "hash": "b9987817b2ea5d721a8bd8c6307e050e8081e587ba17f207ef2a7dc2dd2dc977"
+ },
+ "image (2) (2) (1).png": {
+ "slug": "image-2-2-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-2-2-1.png",
+ "hash": "2f7e5cd7ca6c80d54a61f88aaf37149bc81f9ba07473cd4e95c952cd4ad5013f"
+ },
+ "image (2) (3).png": {
+ "slug": "image-2-3.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-2-3.png",
+ "hash": "3d601ef59ed576b0cee34d5e155e3be6a51dea4561f48e401ea4b567e4122afe"
+ },
+ "image (2) (4).png": {
+ "slug": "image-2-4.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-2-4.png",
+ "hash": "e5c2816066dc0378f48a4088423be721cb53299fa22ce38166492afa2e85f09f"
+ },
+ "image (2) (5).png": {
+ "slug": "image-2-5.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-2-5.png",
+ "hash": "a79d453215d3e6859a5d95cf0e84b8cf3a7d37069dc795dbc0d1ccd2f89f092a"
+ },
+ "image (2).png": {
+ "slug": "image-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-2.png",
+ "hash": "8789f2410e56c6aee455793eb9efb88cbeaf3c6d1105ad76bd9045f196a15008"
+ },
+ "image (21).png": {
+ "slug": "image-21.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-21.png",
+ "hash": "cc53cf2e214767e98e21f66fa9a4fe14093fff4f16892eea57e25786c73eb9bb"
+ },
+ "image (242).png": {
+ "slug": "image-242.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-242.png",
+ "hash": "1b63da277cf7087df5b087242bb54cc290ff103ebd76b3260b0c574580482917"
+ },
+ "image (248).png": {
+ "slug": "image-248.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-248.png",
+ "hash": "5a3d60602ae5970f56deab10d8e0ef13675c7c2ec966917eb54d4c5f8e6b554c"
+ },
+ "image (254).png": {
+ "slug": "image-254.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-254.png",
+ "hash": "05ac8e30320b874bd12686e583ecc4d066109cf1c25f536c1e4000e09b3473bb"
+ },
+ "image (256).png": {
+ "slug": "image-256.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-256.png",
+ "hash": "186f3d8eb9eca379d5bd06e3b1477f47a51004a81457bab7d153a0cabfc7a31d"
+ },
+ "image (263).png": {
+ "slug": "image-263.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-263.png",
+ "hash": "d4e51c81d0a274f92dff60d513c51c8f006f7462ec6540b4eed0f3542763335c"
+ },
+ "image (279).png": {
+ "slug": "image-279.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-279.png",
+ "hash": "509cf4829c79cdad51cec9f1a53eae77995e3206348f53a3be1452cf9bbec31c"
+ },
+ "image (281).png": {
+ "slug": "image-281.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-281.png",
+ "hash": "cf81654a042e14ea162c4c37d33093fb0493d3d8f792310e77324c5e39a99af7"
+ },
+ "image (282).png": {
+ "slug": "image-282.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-282.png",
+ "hash": "a892cc53d58b66448f66517ec0f11c78c856a9e95c4a126afd7a645521663dd7"
+ },
+ "image (285).png": {
+ "slug": "image-285.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-285.png",
+ "hash": "670d85a393eb7264a5e24a91d2ea88b0774becc77824730c42834bd972a3ce6e"
+ },
+ "image (3) (1).png": {
+ "slug": "image-3-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-3-1.png",
+ "hash": "42af0f9e64cefaffb9051cc7ac81aa1843763c2bcbb6975136e04b0779fe99de"
+ },
+ "image (3) (2).png": {
+ "slug": "image-3-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-3-2.png",
+ "hash": "3f0bcb1d8d6e518a6592dedc840d27dd7d7447128640da92cfffe8431f30fde5"
+ },
+ "image (3) (3).png": {
+ "slug": "image-3-3.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-3-3.png",
+ "hash": "3dfb988860f48763770a83d177a69dc28379da547224f857de02153c43219b17"
+ },
+ "image (3) (4).png": {
+ "slug": "image-3-4.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-3-4.png",
+ "hash": "184c82d3d059cdf16fbae16d4a855086d9800879cbd3ddedc4d74d20b580c434"
+ },
+ "image (3).png": {
+ "slug": "image-3.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-3.png",
+ "hash": "45a4baa2b448daf82f3e9bf96d0c89bdf7514fa98ad0cc1fc73f3114bfe985e0"
+ },
+ "image (33).png": {
+ "slug": "image-33.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-33.png",
+ "hash": "e15085debf3ddbb67ee9d7b54a8e1b8e8e9be2c484fe86c2ad9355729168fde7"
+ },
+ "image (339).png": {
+ "slug": "image-339.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-339.png",
+ "hash": "e3f232077da901dce3689ee0ccee0640b747f8be58167791c33f0677cd8ede58"
+ },
+ "image (380).png": {
+ "slug": "image-380.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-380.png",
+ "hash": "20f4e7ec424a50746f56255cdf98d995e48dcbceee7f98cb0d0668a0605c169f"
+ },
+ "image (386).png": {
+ "slug": "image-386.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-386.png",
+ "hash": "21d02e33ace228a92325400040d4cad2b5fa4a53a089b3df9b9d027709ccc315"
+ },
+ "image (394).png": {
+ "slug": "image-394.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-394.png",
+ "hash": "336ac4df19b7d7a69a8adaf0083f2997401d7073aacd0fd654abfecc6e9e26b3"
+ },
+ "image (4) (1) (1).png": {
+ "slug": "image-4-1-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-4-1-1.png",
+ "hash": "b52062c8dbc7e90f6ae687f218a64a74f73e1e2bad1759acbe26c6296fd27611"
+ },
+ "image (4) (1).png": {
+ "slug": "image-4-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-4-1.png",
+ "hash": "0d2f3bd1c4a5949cf74797729a9b80c248ab51a7e13fa96533fe2a5f2445c2c9"
+ },
+ "image (4) (3).png": {
+ "slug": "image-4-3.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-4-3.png",
+ "hash": "2056f99586ea4c8c92a698236c09642f3b497442af5b84e05bdf5ff2052b677f"
+ },
+ "image (4).png": {
+ "slug": "image-4.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-4.png",
+ "hash": "cc68d6f85700f6fc83b7d80a244f7ab65573f487a4977ebb18850781b7be1adb"
+ },
+ "image (40).png": {
+ "slug": "image-40.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-40.png",
+ "hash": "7456e2f6e63d43cad87bb0c9fa557c3c4f1cf5a7377225475c1d8134e655cb08"
+ },
+ "image (403).png": {
+ "slug": "image-403.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-403.png",
+ "hash": "9720d16469025420f1b16031c06e04356abed709204e1a2054b1d7b1bd305127"
+ },
+ "image (408).png": {
+ "slug": "image-408.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-408.png",
+ "hash": "987caa62b5e96949ff89e16578f3cd24edfb256a0d73a3a05581943563de6b17"
+ },
+ "image (414).png": {
+ "slug": "image-414.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-414.png",
+ "hash": "687ef514dfa5f5015f8790999b54278999024e2d034110bb5368c2be18679733"
+ },
+ "image (426).png": {
+ "slug": "image-426.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-426.png",
+ "hash": "50333862917a212cbb2b5d44a8d7d1e6e3f52ae4764ead9f3092ae49584fbfcf"
+ },
+ "image (428).png": {
+ "slug": "image-428.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-428.png",
+ "hash": "88911070dd9a2994de435c12f8d377b6de80ef600af8ae3e99dc530e144c58d1"
+ },
+ "image (434).png": {
+ "slug": "image-434.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-434.png",
+ "hash": "f44d9d6dce8f38ff9935a08af37a70695038c96ea147f03811c27a0b3e4c21d5"
+ },
+ "image (436).png": {
+ "slug": "image-436.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-436.png",
+ "hash": "44bbf021c18ef72c4c924fc6aad6503d43025188035d322eebcc2c5c8b882760"
+ },
+ "image (444).png": {
+ "slug": "image-444.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-444.png",
+ "hash": "5f62eae537b038642dd5570067b66ec0310d9e8862e965a51938f07d77aabbc5"
+ },
+ "image (459).png": {
+ "slug": "image-459.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-459.png",
+ "hash": "cb0272defc4391168b75682beaff562e7d70af05a4a73607d191f2f9a56584b1"
+ },
+ "image (5) (1) (1).png": {
+ "slug": "image-5-1-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-5-1-1.png",
+ "hash": "15deb016984fae1cf46c111a79051606636d3da828f8221e18529da4eea2a4ef"
+ },
+ "image (5) (1).png": {
+ "slug": "image-5-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-5-1.png",
+ "hash": "05c5a03001724f7408815d4eeb45846ac506807f9762a4a3a43cab6e3f0403b7"
+ },
+ "image (5) (2).png": {
+ "slug": "image-5-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-5-2.png",
+ "hash": "2c9a866490e073992f66a57f017a0e782e090355417d29e8a6c5340757ea8c70"
+ },
+ "image (5).png": {
+ "slug": "image-5.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-5.png",
+ "hash": "449d9615a91b6ef90e2a5644dda2eca5536b511b63094bf29ee1029bc2e9728c"
+ },
+ "image (514).png": {
+ "slug": "image-514.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-514.png",
+ "hash": "31c279896c6d1467328f2371de9562bbf013a4edd4f8b1a358e00f287f27c5d3"
+ },
+ "image (528).png": {
+ "slug": "image-528.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-528.png",
+ "hash": "d8111c06ad7dd47216cacb67692e2b9af6f443776e8f12162d1b745a452d14f7"
+ },
+ "image (529) (1).png": {
+ "slug": "image-529-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-529-1.png",
+ "hash": "a227714edc25a737731b52c4a88d7a818e1bcb7b0b87a87d5caa952d0ef41720"
+ },
+ "image (529).png": {
+ "slug": "image-529.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-529.png",
+ "hash": "c2c238d4e57f445253f513f3211b3c7aacf2ce96af861a111c826f0a1f7bb0e1"
+ },
+ "image (530) (1).png": {
+ "slug": "image-530-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-530-1.png",
+ "hash": "88df9b8b21798657dec1898163d45304da52b42c3083cff83f8111e17bcb3bb0"
+ },
+ "image (530).png": {
+ "slug": "image-530.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-530.png",
+ "hash": "bc157885252b382ba0c4aaf9b00e151a53d57314c142f67a8d1ca90c5e268136"
+ },
+ "image (531).png": {
+ "slug": "image-531.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-531.png",
+ "hash": "e15466304caf426c91e3eb7737a1d1f28d80a0b1414a3e8035cb6f8e83a2699a"
+ },
+ "image (532).png": {
+ "slug": "image-532.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-532.png",
+ "hash": "9fcc82241eefb4e9f5b4c7be3024fe8bdab486fae43f0166600e4be7d1f4a8e6"
+ },
+ "image (535).png": {
+ "slug": "image-535.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-535.png",
+ "hash": "41d61aaf29f960b2f04e086f9bee6d1cc1b717cab57fe11f2d07355f0e2bf0e2"
+ },
+ "image (536).png": {
+ "slug": "image-536.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-536.png",
+ "hash": "6e11971b794708946d0a66702a5f6d405ffacae6afe07076de02f7a4f9b90dfa"
+ },
+ "image (537).png": {
+ "slug": "image-537.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-537.png",
+ "hash": "931df4c533c2d61ca80196a3ff973eb0d833f39b901eab2a9a08bb6e9a1c15ab"
+ },
+ "image (538).png": {
+ "slug": "image-538.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-538.png",
+ "hash": "f51ed3861e9dc8d661271a9619c5f301ed3b78833b5b5252bfdffc75d5c5c17b"
+ },
+ "image (539).png": {
+ "slug": "image-539.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-539.png",
+ "hash": "fb1d9b8d017e9828f37c0a1c2e92c99e99586687b174f8dfb7dac4a4b58b89d9"
+ },
+ "image (540).png": {
+ "slug": "image-540.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-540.png",
+ "hash": "faf00f33365a75f767664c2cc77cedcd0045be9b05b45d4c49d3c3e260ba33f4"
+ },
+ "image (541).png": {
+ "slug": "image-541.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-541.png",
+ "hash": "f37bf5843003ef18aa20a2ff39df16c484fa303853e6262d7fc58000d82e58ac"
+ },
+ "image (542).png": {
+ "slug": "image-542.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-542.png",
+ "hash": "e737bca892bec79e5b4d902ea2000632d0405a3b5f43e5d4840d14c9e81ecd0c"
+ },
+ "image (543).png": {
+ "slug": "image-543.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-543.png",
+ "hash": "8f09a697d26c8a89b08e92f8cf7fccc1085f5f63a9c96f92a6ab6beafc0e9d7f"
+ },
+ "image (544).png": {
+ "slug": "image-544.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-544.png",
+ "hash": "af3c1a8f0ff9aefcee0fa591861e5b7e89f9e8029446ea2e090541c46d4992ae"
+ },
+ "image (545).png": {
+ "slug": "image-545.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-545.png",
+ "hash": "9af752f2ec08ecd19082119838cfc300f4e0220043fedd4c6e3657d57a8b2a78"
+ },
+ "image (546).png": {
+ "slug": "image-546.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-546.png",
+ "hash": "082bacce5f576cfd142041dab2944181457e18a3f7a23226d4c7faa7885a603b"
+ },
+ "image (547).png": {
+ "slug": "image-547.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-547.png",
+ "hash": "cfe1f8ffbcd549cfb73e32444496e801424713e7be3a44d64f56d1e6c2c98350"
+ },
+ "image (548).png": {
+ "slug": "image-548.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-548.png",
+ "hash": "e22c392d5f3cb4c63f5939e400eff69d4805c4192b50891888030d16c4b8c1e6"
+ },
+ "image (549).png": {
+ "slug": "image-549.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-549.png",
+ "hash": "3acd969f6b3b562a3c611103852227a99d6d37011fabdad625b8018691209661"
+ },
+ "image (55).png": {
+ "slug": "image-55.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-55.png",
+ "hash": "a291f0dbdee8d115c32a8ee0c5177b712cbbc86e087e5cd9c2a4408548293866"
+ },
+ "image (551).png": {
+ "slug": "image-551.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-551.png",
+ "hash": "6646018a99620a0b83f3d8affb0897ec4d96f4ee063db28d037b88231dc7ba70"
+ },
+ "image (552).png": {
+ "slug": "image-552.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-552.png",
+ "hash": "74d2718fdc26f90b6558c953cb9aa33abb2312205ee4165a6678f69cd5ab69b7"
+ },
+ "image (553).png": {
+ "slug": "image-553.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-553.png",
+ "hash": "8a54c0d4c856dd872bbd13a387e57c2dcd254ae2e0a14341dc9f015f24f7aa6d"
+ },
+ "image (554).png": {
+ "slug": "image-554.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-554.png",
+ "hash": "9b382f5dad3c01b73026a0fb1074966f06123c60f1c237095870661509331924"
+ },
+ "image (556).png": {
+ "slug": "image-556.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-556.png",
+ "hash": "776e5f166c2a95269b175ea46ec134e3f75fef594a7afc1dd7361bf601542918"
+ },
+ "image (559).png": {
+ "slug": "image-559.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-559.png",
+ "hash": "af198665830113d3a3bab6a3ed29cab2768bf8fc2611943b5c11c5038f8e2cc4"
+ },
+ "image (560).png": {
+ "slug": "image-560.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-560.png",
+ "hash": "d533a83c7b0a4f9619a24eb05a23dca942dac76d72b9a14d138964fe8aa1b9fa"
+ },
+ "image (561).png": {
+ "slug": "image-561.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-561.png",
+ "hash": "2b9c485f842f86753d8939ba081e6207867845178b50e01d8997068de6f8867a"
+ },
+ "image (562).png": {
+ "slug": "image-562.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-562.png",
+ "hash": "5c568ad80b438b384a33a826e86516f0bd45aa2e68df170a0717b97a22d71e9d"
+ },
+ "image (563).png": {
+ "slug": "image-563.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-563.png",
+ "hash": "2239fafa035e1e7cbfdb25472218af877a24a1744fa0313e54d4b087add0f61a"
+ },
+ "image (565).png": {
+ "slug": "image-565.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-565.png",
+ "hash": "3e9e7f99a2803fd81085c630fb8b6958ff42a116a80de64567b03ffb71d3be56"
+ },
+ "image (567).png": {
+ "slug": "image-567.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-567.png",
+ "hash": "87159607c1d7e664ff6150e037e0b82c68711826a21964b0a49be82de1391281"
+ },
+ "image (569).png": {
+ "slug": "image-569.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-569.png",
+ "hash": "ab5668a5837b40797aac405db74b0021be66a4a6b20db184dc674778594150dc"
+ },
+ "image (571).png": {
+ "slug": "image-571.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-571.png",
+ "hash": "e6b98a2d220fb7a5dd580f20f6793600538ff3a1183ffff0cf033688f60c288c"
+ },
+ "image (572).png": {
+ "slug": "image-572.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-572.png",
+ "hash": "b6d9202cebce31f018df6cea23f3b3183f641614c6a1033d45da4ee05725e510"
+ },
+ "image (574).png": {
+ "slug": "image-574.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-574.png",
+ "hash": "acdd4b61bad9cc6833c48d5f5c7da7b4fb4d8c64fb2cdb365901d7611b9a19aa"
+ },
+ "image (575) (1).png": {
+ "slug": "image-575-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-575-1.png",
+ "hash": "ce8e4c1d4940db79e75b373ce82cf261c4d5b459d1e02f332589235b53bd3db8"
+ },
+ "image (577).png": {
+ "slug": "image-577.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-577.png",
+ "hash": "20a23370fe760e1add7bed333c6072bc1bdbd0eec8c165afed20dc9c105d1cf0"
+ },
+ "image (578).png": {
+ "slug": "image-578.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-578.png",
+ "hash": "efe0325f500973e2005ce8e49235b53b1d8dc9e9b3fe28014cf0d309fb31ae20"
+ },
+ "image (579).png": {
+ "slug": "image-579.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-579.png",
+ "hash": "cc5e90ec6163265dfd3dcb69459742dd2b5c0da45208b8dad5345c51746cea69"
+ },
+ "image (581).png": {
+ "slug": "image-581.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-581.png",
+ "hash": "9f50ef34fa9b2e56ee1f8e6fbbaf8370e282fbffe986274554821da2c6fe9398"
+ },
+ "image (582).png": {
+ "slug": "image-582.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-582.png",
+ "hash": "5d950f4c57fd08caf61169f65a141d8af6b5bd9f78686e7086a0885e33bc7881"
+ },
+ "image (583).png": {
+ "slug": "image-583.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-583.png",
+ "hash": "25571a37d6c3a5d66ebd96a55f43c8d45113ed110b6496ca0862382e5ae80680"
+ },
+ "image (584).png": {
+ "slug": "image-584.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-584.png",
+ "hash": "f64a26c8a11ab137adf605463f53e4c07134409982afa16845fc049a92ce57d4"
+ },
+ "image (585).png": {
+ "slug": "image-585.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-585.png",
+ "hash": "5e018e771bbe5c695cee181d61a91aacad25362c52fd491fdcab0029234746fe"
+ },
+ "image (586).png": {
+ "slug": "image-586.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-586.png",
+ "hash": "ff7d912e0fc229e861d7bf7019bc43fb832e32508be828b9cac789f3f2eb599d"
+ },
+ "image (588).png": {
+ "slug": "image-588.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-588.png",
+ "hash": "dacdfecd08605332224d89ef5a5a6e7869d1d6bf3e63d1a2646a53b6b709bd3b"
+ },
+ "image (590).png": {
+ "slug": "image-590.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-590.png",
+ "hash": "dc24d112074c5947912bd9afee794819b2d3570a2bb86a588d096391d7082d33"
+ },
+ "image (592).png": {
+ "slug": "image-592.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-592.png",
+ "hash": "5e767b574055dcccb02702c16f832e079b858492d5140194db6479afdd508ba5"
+ },
+ "image (593).png": {
+ "slug": "image-593.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-593.png",
+ "hash": "c8bddea83ab1f09c9a8d9e022f111949c70544c4a50dcc217d5bbe9e67feec38"
+ },
+ "image (594).png": {
+ "slug": "image-594.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-594.png",
+ "hash": "069763c5b65b13b68b8d450d923c3e032e5ca8d75dc996264611f369ae9c8dde"
+ },
+ "image (595).png": {
+ "slug": "image-595.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-595.png",
+ "hash": "b967d827afde92c53ff29fc3dd86df0cf393a434368f7af3370348aba0346236"
+ },
+ "image (596).png": {
+ "slug": "image-596.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-596.png",
+ "hash": "d3b02319d9fc07635188c9b35b23a86d36d710d79c6a2d6e488ba3ba2fac4d8c"
+ },
+ "image (597).png": {
+ "slug": "image-597.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-597.png",
+ "hash": "84446291f605e56f3fc2c85db3e40e966a41ab080e23ce8a40d5c92ca03c01e5"
+ },
+ "image (6) (1).png": {
+ "slug": "image-6-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-6-1.png",
+ "hash": "9fdc826fb4d586dc9438fa5e6134889e4839e70adcfeeb6fa9178c2deedacb15"
+ },
+ "image (6) (2).png": {
+ "slug": "image-6-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-6-2.png",
+ "hash": "5a2197d9082e68a331ea19d25a3689188670858ca7bb6dd1cbfe3f52719dbeec"
+ },
+ "image (6).png": {
+ "slug": "image-6.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-6.png",
+ "hash": "fe8cd905a3f2db24f963d8e6dafa54a5788ec6d54d8dd6dcbb91411894ac1ece"
+ },
+ "image (601).png": {
+ "slug": "image-601.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-601.png",
+ "hash": "21a748ba56222374a73a88cdcc2fe74edae94edbf48e09351418cf4d099ebf66"
+ },
+ "image (602).png": {
+ "slug": "image-602.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-602.png",
+ "hash": "a980777146e43e06496bc03f82c6535353ddf8a5bff287305079a864e4204df4"
+ },
+ "image (603).png": {
+ "slug": "image-603.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-603.png",
+ "hash": "50e6c4c9e9d42bf694f0ffbc0bed26548dc61ec32f3e4199723cec35848745c6"
+ },
+ "image (604).png": {
+ "slug": "image-604.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-604.png",
+ "hash": "1bf1e0272ecf63d5785475360bdcf35bb936c8502b60631375627d40bc733b80"
+ },
+ "image (605).png": {
+ "slug": "image-605.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-605.png",
+ "hash": "655e1bd8812a6c3dcdd4c7ff0bb997469fdb843159d0f7cf57d1bc2506edf8ae"
+ },
+ "image (606).png": {
+ "slug": "image-606.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-606.png",
+ "hash": "e221cc1e2a117be0a1611df0d81ec52fe2e69d6bc4d38f68a6ffeb71b61ded66"
+ },
+ "image (607).png": {
+ "slug": "image-607.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-607.png",
+ "hash": "93cec0ea8a64bd7d37cb3b3e60e86566efdaa8af90cff81cd9ac1ae5281fad40"
+ },
+ "image (608).png": {
+ "slug": "image-608.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-608.png",
+ "hash": "cf2d3188980d54b69ad8459b846bd86ec9d752e18d616889edca75186587c8ca"
+ },
+ "image (609).png": {
+ "slug": "image-609.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-609.png",
+ "hash": "b116a4fba4dc529112e2c57820988b3a9406c707afd2f9018ebb8968a60e039a"
+ },
+ "image (611).png": {
+ "slug": "image-611.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-611.png",
+ "hash": "2f7532648ac63596cd11dc9a414622fe76d871eab9057f8659f36dca871dd03d"
+ },
+ "image (612).png": {
+ "slug": "image-612.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-612.png",
+ "hash": "a2f0b22778048340bdf383e262fb9d9dcabad6264a6ba3dd46527ff7d8f7ea32"
+ },
+ "image (613).png": {
+ "slug": "image-613.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-613.png",
+ "hash": "5078481cceda2b0a089f28dd6cc51d3ee110b85de429bf9453ee83a0110e1087"
+ },
+ "image (614).png": {
+ "slug": "image-614.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-614.png",
+ "hash": "0c8c15ce359de20be2ab80128b5826ac8c5134b2d112282f0fe66c87a58ef555"
+ },
+ "image (615).png": {
+ "slug": "image-615.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-615.png",
+ "hash": "06cc047e735215f266a61f97564e3ad6d787d277c7c133a02ffe0807061df4e8"
+ },
+ "image (618).png": {
+ "slug": "image-618.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-618.png",
+ "hash": "3ce9f9b6b7e3baceb5214ab449f79d656154d72c0435fc9037c08bc4a8380172"
+ },
+ "image (619).png": {
+ "slug": "image-619.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-619.png",
+ "hash": "e6f71832395f4f039fc49f77d0adea23cb63affb20d1eac3c82b4d79464a8b0b"
+ },
+ "image (621).png": {
+ "slug": "image-621.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-621.png",
+ "hash": "53ad95ee5403c27684e9af0bc221ae54ab4a4bd066b725cc5253e16683964fa0"
+ },
+ "image (622).png": {
+ "slug": "image-622.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-622.png",
+ "hash": "8d2ef89885111899823492222d73276e006e30a1671b8b1cf6db99383d61de63"
+ },
+ "image (623).png": {
+ "slug": "image-623.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-623.png",
+ "hash": "49ceb6b054474aa75089ab63c97230b10b59b38c405f4440631dd206b7f4b060"
+ },
+ "image (624).png": {
+ "slug": "image-624.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-624.png",
+ "hash": "40426cb8a9d51834779a8c4e4df975159d9e21a8b2709c9afe9112d1abf0f17d"
+ },
+ "image (626).png": {
+ "slug": "image-626.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-626.png",
+ "hash": "60b3d39e01c84b15319a69552c1f59453c6b12cb08ff6304cc3d0098e1d0e07f"
+ },
+ "image (627).png": {
+ "slug": "image-627.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-627.png",
+ "hash": "6a6b9b2ad82b17db852362d33e91292d64c8148673abce19f29410aa1ec18dee"
+ },
+ "image (8).png": {
+ "slug": "image-8.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-8.png",
+ "hash": "c9aa66e3a590599a1c357a801046a4a4183269754cac4a86c6feddea74dc48a1"
+ },
+ "image (81).png": {
+ "slug": "image-81.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-81.png",
+ "hash": "c3f315b04863675e4939b844a0bf94b971f923496e0fc3b3d283fabfda774488"
+ },
+ "image (84).png": {
+ "slug": "image-84.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-84.png",
+ "hash": "0a124535e841de11dd2f5bbddaf9f70bb70de119df0245854fc030997721758d"
+ },
+ "image (89).png": {
+ "slug": "image-89.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-89.png",
+ "hash": "6f78cb4ab1106d5cac2f56ab7c667d347e21ab0665c8854bf8f94020f6ab81ed"
+ },
+ "image (91).png": {
+ "slug": "image-91.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/image-91.png",
+ "hash": "7ae8e6155d93404e2359ea5ad957aa00a59f048ca00e2e0500259a73c435c2e0"
+ },
+ "intents.png": {
+ "slug": "intents.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/intents.png",
+ "hash": "b6707259dad8405009a74c571a9edc73cf3d8c6cfcc275bdc560b5776072659f"
+ },
+ "legoblocks.png": {
+ "slug": "legoblocks.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/legoblocks.png",
+ "hash": "9476a161c55e3ea4e5b8b58a41a5adb55b7db62348d4fcd1529940a3ad810f6e"
+ },
+ "location.png": {
+ "slug": "location.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/location.png",
+ "hash": "a724985cc1afc3cce21d68b4fcd6df9a6adabd22fe679810c85269b833fe2057"
+ },
+ "luis-add-to-intent.png": {
+ "slug": "luis-add-to-intent.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/luis-add-to-intent.png",
+ "hash": "283c3b1912bb9e862c02c39dfc9a125f24c2adea2b2e2f90f6d5c9d170ba203e"
+ },
+ "luis-app-id.png": {
+ "slug": "luis-app-id.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/luis-app-id.png",
+ "hash": "e6a79743eb4e34f05e95c724c609fc5c3c04540c68713c8b181e1c002f4a0234"
+ },
+ "luis-create-intent.png": {
+ "slug": "luis-create-intent.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/luis-create-intent.png",
+ "hash": "08c5e6b2aa56dec07378b25a76ac21352b0572a0183beedbf4b793217d95c733"
+ },
+ "luis-intent-entity.png": {
+ "slug": "luis-intent-entity.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/luis-intent-entity.png",
+ "hash": "9187d9308d6febb318968383fd38151ee4eb545c1f6ee7345b84de6f1227d487"
+ },
+ "luis-interpreter-entity.png": {
+ "slug": "luis-interpreter-entity.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/luis-interpreter-entity.png",
+ "hash": "15dca8b04e438938b7456f82b855c602a7dfc7ea435808ac86509d547999c1ce"
+ },
+ "luis-interpreter.png": {
+ "slug": "luis-interpreter.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/luis-interpreter.png",
+ "hash": "dd2b3249957d182c36c925bd5625c75428cdbbb67ea5f0c7bb6cfd2b14c14464"
+ },
+ "luis-preview.png": {
+ "slug": "luis-preview.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/luis-preview.png",
+ "hash": "ccadf77c4f5706cb3aad39c546b3fbb7550b65215d5e23bcac6d9a22d11f716b"
+ },
+ "luis-sub-key-app-url.png": {
+ "slug": "luis-sub-key-app-url.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/luis-sub-key-app-url.png",
+ "hash": "2e635a58096807327bb05642bee4cc87fa5c605886d990fcaa04c30828dd400a"
+ },
+ "luis-test.png": {
+ "slug": "luis-test.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/luis-test.png",
+ "hash": "c382f2e9f1febf2316da90ade67f6b169ba1707c571410beb19dd1fbd0e0a337"
+ },
+ "luis-utterances.png": {
+ "slug": "luis-utterances.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/luis-utterances.png",
+ "hash": "e7c28d54e0ea9321440228e27b77cfde700f64958123565baad479d1e67204ef"
+ },
+ "no_messages_passing_conditions.png": {
+ "slug": "no-messages-passing-conditions.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/no-messages-passing-conditions.png",
+ "hash": "a135e75a3579d43f289cbc4ff121ea6ff046ee26265e4f4adeaff0fb80525f63"
+ },
+ "nomatch.png": {
+ "slug": "nomatch.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/nomatch.png",
+ "hash": "6c1fa21a4eb2adcfb92be208ae7cc79c477a04798dc19bea0dfa214a2fc19455"
+ },
+ "oauth2 config.png": {
+ "slug": "oauth2-config.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/oauth2-config.png",
+ "hash": "52ae3ad5b4ef6f99067078afb39fb2672f2142cde74ef3c38b704b9081deec09"
+ },
+ "od-kamau.cloud.opendialog.ai_admin_conversation-builder_scene_0x13c2efd_scenario=0x13c2efa (1).png": {
+ "slug": "od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0x13c2efd-scenario-0x13c2efa-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0x13c2efd-scenario-0x13c2efa-1.png",
+ "hash": "5d1af32392d3160aebcfcd0ac3a05c1134005e2b991211ba49c5a4c5a89b495b"
+ },
+ "od-kamau.cloud.opendialog.ai_admin_conversation-builder_scene_0x13c2efd_scenario=0x13c2efa (7).png": {
+ "slug": "od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0x13c2efd-scenario-0x13c2efa-7.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0x13c2efd-scenario-0x13c2efa-7.png",
+ "hash": "47d777339762b9a16ebe1a88d55d24563501658ae9dd75293ef50fd6180dc38b"
+ },
+ "od-kamau.cloud.opendialog.ai_admin_conversation-builder_scene_0x13c2efd_scenario=0x13c2efa (8).png": {
+ "slug": "od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0x13c2efd-scenario-0x13c2efa-8.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0x13c2efd-scenario-0x13c2efa-8.png",
+ "hash": "a6e1ccb1b826654e43064d559e828db5fc67a048ae9d68ccf80f30626a6a10e1"
+ },
+ "od-kamau.cloud.opendialog.ai_admin_demo_scenario=0x13c2efa (3).png": {
+ "slug": "od-kamau-cloud-opendialog-ai-admin-demo-scenario-0x13c2efa-3.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/od-kamau-cloud-opendialog-ai-admin-demo-scenario-0x13c2efa-3.png",
+ "hash": "8a48ec98021880308c9e07735edd6ecdd41a4eb470868aa4bd2a5710c89a70e0"
+ },
+ "od-kamau.cloud.opendialog.ai_admin_interpreters_mapping_99_scenario=0x13c2efa (1).png": {
+ "slug": "od-kamau-cloud-opendialog-ai-admin-interpreters-mapping-99-scenario-0x13c2efa-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/od-kamau-cloud-opendialog-ai-admin-interpreters-mapping-99-scenario-0x13c2efa-1.png",
+ "hash": "2c33fe677682d362311d13cb5b6d2706641d6024b51bf44902b29f068d48a64c"
+ },
+ "od-kamau.cloud.opendialog.ai_admin_interpreters_mapping_99_scenario=0x13c2efa.png": {
+ "slug": "od-kamau-cloud-opendialog-ai-admin-interpreters-mapping-99-scenario-0x13c2efa.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/od-kamau-cloud-opendialog-ai-admin-interpreters-mapping-99-scenario-0x13c2efa.png",
+ "hash": "5662eab42112751fa74c60329d7a37637fe248e7f07cfcca8069eab71a972cc9"
+ },
+ "opendialog_actions_122024.png": {
+ "slug": "opendialog-actions-122024.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/opendialog-actions-122024.png",
+ "hash": "5aba61daab431157ba36acdc96fbfc1e0f638c19112e280da93bde4345a01756"
+ },
+ "opendialog_actions_2.png": {
+ "slug": "opendialog-actions-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/opendialog-actions-2.png",
+ "hash": "2cfd96897611f830a30973ab9c2bdc449ec598910ba2a32e51971434c787f880"
+ },
+ "opendialog_model.png": {
+ "slug": "opendialog-model.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/opendialog-model.png",
+ "hash": "f49cc07a16f69af1b0ff7a218cfe1359f78b0042db8a7bc1ae5ace124d5b46ca"
+ },
+ "personalisation.png": {
+ "slug": "personalisation.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/personalisation.png",
+ "hash": "84c2816eb095c700858e07c62dc5002fd33fce746a1493540186b59448191358"
+ },
+ "pic 2.png": {
+ "slug": "pic-2.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/pic-2.png",
+ "hash": "28031c8307718f64b58d56804a0969e722e0f111d42d808b3bca288801ad49a5"
+ },
+ "pic 3.png": {
+ "slug": "pic-3.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/pic-3.png",
+ "hash": "08602bc977dec2beb00da4421ca115dc6587441d6ed1594da360cd5b119ce40f"
+ },
+ "pic 4.png": {
+ "slug": "pic-4.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/pic-4.png",
+ "hash": "49d532fbb477760365fe28b630da69a669b1f49c76c1745cddc7793cef0e9585"
+ },
+ "pic 5.png": {
+ "slug": "pic-5.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/pic-5.png",
+ "hash": "2861a165df613db1864ef004434f6fd71451b82c68539e406952a3bbaa110d61"
+ },
+ "preview-overview.png": {
+ "slug": "preview-overview.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/preview-overview.png",
+ "hash": "9db50ffeb6b1b18e1b45d903fa7e5025d8004d461293e69d65596caca33f05a1"
+ },
+ "putting it all together (1).png": {
+ "slug": "putting-it-all-together-1.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/putting-it-all-together-1.png",
+ "hash": "98cc059533f553cebc2c848bf091e560677829cfddd85ac8569c74d617485515"
+ },
+ "qna-add-to-intent.png": {
+ "slug": "qna-add-to-intent.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/qna-add-to-intent.png",
+ "hash": "93230a3ff9770be2d5b99599ce48b0f24e9a65e5d8a0913a4aacdf0b2cd6eda6"
+ },
+ "qna-answer-intent.png": {
+ "slug": "qna-answer-intent.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/qna-answer-intent.png",
+ "hash": "7b6cb76e465bcf71130c8298f341931909db4c01e155e35071b94bd123146d40"
+ },
+ "qna-interpreter.png": {
+ "slug": "qna-interpreter.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/qna-interpreter.png",
+ "hash": "721352e8a2fc65d5db7120c058e33cf0dbaf3d7da2e5b023f0bc2c3be9b9259a"
+ },
+ "qna-message.png": {
+ "slug": "qna-message.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/qna-message.png",
+ "hash": "00dd35c3c19910194087f26a4a9114a0dbacd920f275d18165dcf2053fae9765"
+ },
+ "qna-new-pair.png": {
+ "slug": "qna-new-pair.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/qna-new-pair.png",
+ "hash": "5df631b61629488a92bf8e2e050cc3e69f449e24dc4fb754ca55016a4574283c"
+ },
+ "qna-pairs.png": {
+ "slug": "qna-pairs.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/qna-pairs.png",
+ "hash": "62b27f194e4717698468ba2e5e7dceb5152d0add3a4bd66be23c1854647b5dec"
+ },
+ "qna-preview.png": {
+ "slug": "qna-preview.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/qna-preview.png",
+ "hash": "d18db8d9f60c3ec6d65badc1e5b3a319c369d0f8b5550855f7a081b473416fa3"
+ },
+ "qna-publish.png": {
+ "slug": "qna-publish.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/qna-publish.png",
+ "hash": "9583c61aaff54e1963a453219909aa208521dd8dd9194b53606ce1a9007aad7a"
+ },
+ "qna-test.png": {
+ "slug": "qna-test.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/qna-test.png",
+ "hash": "11ab0f01dc3729a02c9cf631a8172c97f9108f985f354a8eb30851919c355e07"
+ },
+ "qna-turn.png": {
+ "slug": "qna-turn.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/qna-turn.png",
+ "hash": "b4a7292808698c1be317ae063c3f9ce9c03ce678cb0b2105a48296355f0ccec2"
+ },
+ "screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-interpreters-configure-1125899907000034-2024-09-05-09_59_52.png": {
+ "slug": "screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-interpreters-configure-1125899907000034-2024-09-05-09-59-52.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-interpreters-configure-1125899907000034-2024-09-05-09-59-52.png",
+ "hash": "0f2287f65e663cce8242f2f1ba849df9a465fac02cc4ad16d11160ea3f3ac170"
+ },
+ "screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-language-services-type-2024-09-05-09_54_57.png": {
+ "slug": "screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-language-services-type-2024-09-05-09-54-57.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-language-services-type-2024-09-05-09-54-57.png",
+ "hash": "bb1f77386dff4bb94782c87e92aa9b705eadc3187d3614d71aad627c085fbe06"
+ },
+ "screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09_54_06.png": {
+ "slug": "screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09-54-06.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09-54-06.png",
+ "hash": "e34104ea59f659c7a17feecc1459db57430d87c8f8408dbe38689c78d4cdfc0c"
+ },
+ "screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09_57_33.png": {
+ "slug": "screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09-57-33.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09-57-33.png",
+ "hash": "e216b96722ebaa267fef60d1d7f50b6bd9f1702ea0f21f53ef9073639650c55b"
+ },
+ "screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09_58_09.png": {
+ "slug": "screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09-58-09.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09-58-09.png",
+ "hash": "7c04892072953f46db80850a17570a7b234d65919a9206d8d25cc8ba1143f334"
+ },
+ "screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-prompt-2024-09-05-09_58_53.png": {
+ "slug": "screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-prompt-2024-09-05-09-58-53.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-prompt-2024-09-05-09-58-53.png",
+ "hash": "8007b4018b75f30d2ebf7cdd1882afc4edb2e615a275b0997c8d3defac2c279f"
+ },
+ "screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-new-2024-09-05-09_56_18.png": {
+ "slug": "screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-new-2024-09-05-09-56-18.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-new-2024-09-05-09-56-18.png",
+ "hash": "90b4bb365bb680bf9aedf16ed55a1ed139e07c8696593499d8654ad50b8a4624"
+ },
+ "secret managemnet.png": {
+ "slug": "secret-managemnet.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/secret-managemnet.png",
+ "hash": "cbb4a68bd93c7cb3314163ec6150dee389a0b107e978dd5cd8dd0c0ec977e8b9"
+ },
+ "smiley flash (1).gif": {
+ "slug": "smiley-flash-1.gif",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/smiley-flash-1.gif",
+ "hash": "70546540c58ecf78172216da320a4a777e4d47f3ed5ea09c916a11b83de42fa7"
+ },
+ "spaces_IT4T0sJdqeqCXi1fUCAu_uploads_mWtXL3ueFl5AvnJIeQBH_IMG-6998.webp": {
+ "slug": "spaces-it4t0sjdqeqcxi1fucau-uploads-mwtxl3uefl5avnjieqbh-img-6998.webp",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/spaces-it4t0sjdqeqcxi1fucau-uploads-mwtxl3uefl5avnjieqbh-img-6998.webp",
+ "hash": "78cdeb85b3bcbd8e86e3561996211f2404759f2c972adfb6a7b64742f6396617"
+ },
+ "spaces_IT4T0sJdqeqCXi1fUCAu_uploads_uK8yZf49ckvTwbfi1qDG_IMG-6996 (1).webp": {
+ "slug": "spaces-it4t0sjdqeqcxi1fucau-uploads-uk8yzf49ckvtwbfi1qdg-img-6996-1.webp",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/spaces-it4t0sjdqeqcxi1fucau-uploads-uk8yzf49ckvtwbfi1qdg-img-6996-1.webp",
+ "hash": "97b49fa7b9c970694a1480bbe5448e4c891ac2a21ca511a4762b73eec96d18d2"
+ },
+ "start-from-scratch-scenario.png": {
+ "slug": "start-from-scratch-scenario.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/start-from-scratch-scenario.png",
+ "hash": "41ec20632e6a7a4590423c796f4a428f4d7221e3ae937e365e97b5d4dd4211cb"
+ },
+ "test-agent.png": {
+ "slug": "test-agent.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/test-agent.png",
+ "hash": "e80854e02f23917f826d4c0e5ccf195ee9c5aeb3ced6d503631a38c06a7b2e0a"
+ },
+ "turns.png": {
+ "slug": "turns.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/turns.png",
+ "hash": "4a9e28c1dc85c840b2cadc74f1be8459f5c5645d4ec4b6b65753bdf305cae352"
+ },
+ "usinglanguageservice.png": {
+ "slug": "usinglanguageservice.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/usinglanguageservice.png",
+ "hash": "c6e7d516d5f0ce9586fc3ef8d50a596dc24b21a65b09a825b73d62a4940e8f73"
+ },
+ "vectorise.png": {
+ "slug": "vectorise.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/vectorise.png",
+ "hash": "a3a1759497a908a4d5e0cb8113a1f9ed8bfa84793c12cfd4804dd4f7a32d03b8"
+ },
+ "webhook_auth_demo.png": {
+ "slug": "webhook-auth-demo.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/webhook-auth-demo.png",
+ "hash": "83000b84349480a662d624330757a05ef2b3ac1b4e5276522e489b3a093596c5"
+ },
+ "welcome-conversation.png": {
+ "slug": "welcome-conversation.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/welcome-conversation.png",
+ "hash": "d25d451864fe297cb8585590ad1567e333533e4c0603093f0562d7786dc46ab0"
+ },
+ "welcome-scene.png": {
+ "slug": "welcome-scene.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/welcome-scene.png",
+ "hash": "7df92b72e71b053114a406b5790ae91086fa97c97870529f1e9874f5bfca517c"
+ },
+ "welcome-turn.png": {
+ "slug": "welcome-turn.png",
+ "kind": "image",
+ "destination": "src/assets",
+ "reference": "~/assets/welcome-turn.png",
+ "hash": "37023cbad28de66bde54acb9767c2393d7429557c4db1639fc2db85976d40bbd"
+ }
+ }
+}
diff --git a/astro.config.mjs b/astro.config.mjs
index 38ec9f8..f27d6ff 100644
--- a/astro.config.mjs
+++ b/astro.config.mjs
@@ -2,6 +2,32 @@
import { defineConfig } from 'astro/config';
import starlight from '@astrojs/starlight';
import sidebar from './src/sidebar.generated.mjs';
+import { rehypeImageWidth } from './scripts/lib/rehype-image-width.mjs';
+import { rehypeFigures } from './scripts/lib/rehype-figures.mjs';
+import { readdirSync, readFileSync, writeFileSync } from 'node:fs';
+import { fileURLToPath } from 'node:url';
+import { pinLightTheme } from './scripts/lib/light-theme.mjs';
+
+/**
+ * Rewrites the colour scheme Starlight hard-codes into every emitted page.
+ *
+ * @type {import('astro').AstroIntegration}
+ */
+const pinLightThemeIntegration = {
+ name: 'pin-light-theme',
+ hooks: {
+ 'astro:build:done': ({ dir, logger }) => {
+ const out = fileURLToPath(dir);
+ const pages = readdirSync(out, { recursive: true }).filter((f) => String(f).endsWith('.html'));
+ if (!pages.length) throw new Error('pin-light-theme: no HTML pages in the build output');
+ for (const page of pages) {
+ const path = `${out}/${page}`;
+ writeFileSync(path, pinLightTheme(readFileSync(path, 'utf8')));
+ }
+ logger.info(`pinned data-theme="light" on ${pages.length} pages`);
+ },
+ },
+};
// https://astro.build/config
export default defineConfig({
@@ -10,6 +36,12 @@ export default defineConfig({
// and canonical URLs in the same shape keeps navigation free of redirect hops
// and keeps the canonical URL identical to the one indexed today.
trailingSlash: 'never',
+ // Applies the per-image widths GitBook authored, which convert.mjs carries through
+ // the markdown title slot. Astro's MDX integration extends this config by default,
+ // so .mdx pages get it too.
+ markdown: {
+ rehypePlugins: [rehypeImageWidth, rehypeFigures],
+ },
integrations: [
starlight({
title: 'OpenDialog Docs',
@@ -19,13 +51,24 @@ export default defineConfig({
components: {
// Renders the frontmatter description under the title, as GitBook does.
PageTitle: './src/components/PageTitle.astro',
+ // Orders the header as GitBook does and carries its opendialog.ai link
+ // and "Talk to an expert" call to action.
+ Header: './src/components/Header.astro',
+ // The site ships light-only, as GitBook does: no switcher, theme pinned.
+ ThemeSelect: './src/components/ThemeSelect.astro',
+ ThemeProvider: './src/components/ThemeProvider.astro',
+ // Would otherwise leave an empty bordered strip in the mobile menu.
+ MobileMenuFooter: './src/components/MobileMenuFooter.astro',
+ // Renders a parent page as one clickable, expandable row rather than
+ // repeating it as the first child of its own group. Must be wired through
+ // Sidebar: SidebarSublist is not an overridable component, and naming it
+ // here is accepted silently and does nothing.
+ Sidebar: './src/components/Sidebar.astro',
},
- social: [
- { icon: 'github', label: 'GitHub', href: 'https://github.com/opendialogai' },
- { icon: 'linkedin', label: 'LinkedIn', href: 'https://www.linkedin.com/company/opendialogai/' },
- { icon: 'x.com', label: 'X', href: 'https://twitter.com/opendialogai' },
- ],
+ // No `social`: GitBook carries no social icons, and Starlight renders them in
+ // the header and the mobile menu whenever the key is present.
sidebar,
}),
+ pinLightThemeIntegration,
],
});
diff --git a/docs/superpowers/plans/2026-07-29-phase-2-conversion-script.md b/docs/superpowers/plans/2026-07-29-phase-2-conversion-script.md
deleted file mode 100644
index c0400a7..0000000
--- a/docs/superpowers/plans/2026-07-29-phase-2-conversion-script.md
+++ /dev/null
@@ -1,2755 +0,0 @@
-# Phase 2 Conversion Script Implementation Plan
-
-> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
-
-**Goal:** `node scripts/convert.mjs` turns the 204 published GitBook pages in `source/` into valid Starlight content under `src/content/docs/`, and `node scripts/sidebar.mjs` generates the site's sidebar from `source/SUMMARY.md`.
-
-**Architecture:** Pure `string -> string` transform functions in `scripts/lib/`, each unit-tested against inline fixtures with no filesystem access. Two code-safety primitives in `lib/segments.mjs` guarantee fenced code and inline code spans are never touched. Thin orchestrators (`convert.mjs`, `sidebar.mjs`) do the I/O, then assert corpus-wide invariants and exit non-zero on any divergence — the same self-verifying pattern `scripts/routes.mjs` already uses against the sitemap snapshot.
-
-**Tech Stack:** ESM (`"type": "module"`), `node:test` for tests, Astro 7.1.5 + Starlight 0.41.5. `.node-version` pins CI to Node 24.18.0; the local shell runs Node 22.19.0 with npm 11.6.0. Both npm are 11.x, so the lockfile shape agrees and the Node skew affects only the test-runner invocation noted below.
-
-**Verified while planning:** the `segments.mjs` and `sidebar-tree.mjs` implementations below were extracted from this document and run against their own tests — 17 pass. The other modules' code is written to the same standard but has not been executed.
-
-**Design spec:** `docs/superpowers/specs/2026-07-29-phase-2-conversion-design.md`. Read it before starting — it carries the measured counts and the eight corrections to `MIGRATION-BRIEF.md`.
-
-## Global Constraints
-
-- **Never hand-edit `src/content/docs/`.** It is generated. Fix the script and re-run.
-- **`source/` is read-only and git-ignored.** Scripts read from `source/`, write to `src/`. Never mutate `source/` in place. Repopulate with `git archive documentation | tar -x -C source/`.
-- **Never write to the `documentation` branch.** GitBook syncs to it bidirectionally.
-- **Do not edit documentation prose.** Not typos, not clarity. Log in `MIGRATION-NOTES.md`.
-- **Scripts must be idempotent.** Same input gives byte-identical output. No timestamps, no randomness, no filesystem-ordering dependence.
-- **No new npm dependencies.** The lockfile has broken CI twice (see `MIGRATION-NOTES.md`, npm 10/11 skew). `node:test` is built in. If a task seems to need a package, stop and ask.
-- **Expected counts are authoritative.** If output diverges from an invariant, the script is wrong. Do not adjust the expectation to match the output.
-- **Stop at the phase gate.** Task 13 ends Phase 2. Do not begin Phase 3 asset work.
-- Node's built-in test runner: add `"test": "node --test \"scripts/lib/*.test.mjs\""` to `package.json` in Task 1, and use `node --test scripts/lib/<name>.test.mjs` for single files. **Use the quoted glob, not a bare directory** — `node --test scripts/lib/` fails with `Could not find` on Node 22.x, which is what runs locally, even though `.node-version` pins CI to 24.18.0. Verified both forms.
-- All new files use ESM `import`/`export`, 2-space indent, single quotes, semicolons — matching `scripts/routes.mjs`.
-- Comments use JSDoc `/** ... */` for exported functions, explaining WHAT and WHY, never history or "improved".
-
-## File Structure
-
-| File | Responsibility |
-|---|---|
-| `scripts/lib/summary.mjs` | Parse `source/SUMMARY.md` into ordered nav entries. Shared by `routes.mjs` and `sidebar.mjs`. |
-| `scripts/lib/segments.mjs` | The two code-safety primitives every other transform is built on. |
-| `scripts/lib/frontmatter.mjs` | Parse GitBook frontmatter (including folded block scalars), emit Starlight frontmatter. |
-| `scripts/lib/links.mjs` | Extract link/image targets safely; rewrite page links to route URLs. |
-| `scripts/lib/gitbook-blocks.mjs` | All `{% … %}` block syntax: hint, code, file, embed, stepper, columns. |
-| `scripts/lib/link-cards.mjs` | Route-map-dependent card emission: `{% content-ref %}` and card-tables. |
-| `scripts/lib/figures.mjs` | `<figure>` / bare `<img>` to markdown images. |
-| `scripts/lib/mdx.mjs` | JSX normalisation and brace escaping for `.mdx` output. |
-| `src/components/Embed.astro` | Lazy 16:9 Loom/YouTube iframe. |
-| `scripts/convert.mjs` | Orchestrate the per-file pipeline, assert corpus invariants, report. |
-| `scripts/sidebar.mjs` | `SUMMARY.md` to `src/sidebar.generated.mjs`. |
-| `scripts/routes.mjs` | Existing. Modified in Task 1 to import `lib/summary.mjs`. |
-| `astro.config.mjs` | Existing. Modified in Task 12 to import the generated sidebar. |
-
-### Refinement to the spec, found while planning
-
-The spec proposed `splitSegments()` / `mapProse()` in `lib/segments.mjs`. Measurement showed
-`{% columns %}` / `{% column %}` **wrap fenced code blocks** (1 and 2 instances), so a block's
-open and close markers can land in different prose segments — a per-segment mapper would fail
-to pair them. Two primitives replace it:
-
-- `mapLines()` — walks lines with fence state, calls the callback **only** on lines outside
- fences. Block constructs keep their own state across the walk, so they span fences safely.
-- `protectCode()` — masks fenced blocks and inline code spans with placeholder tokens, runs a
- regex transform over the remainder, restores. For inline transforms that never span a fence.
-
-The spec's intent is unchanged: code is immune to every transformation.
-
----
-
-### Task 1: Shared `SUMMARY.md` parser
-
-`scripts/routes.mjs` carries a `SUMMARY.md` parser that `scripts/sidebar.mjs` needs to reuse
-verbatim — including the escaped-bracket trap that silently drops four live pages. Extract it
-so there is one parser, in one place, to get wrong.
-
-**Files:**
-- Create: `scripts/lib/summary.mjs`
-- Create: `scripts/lib/summary.test.mjs`
-- Modify: `scripts/routes.mjs` (delete lines 20–50, import instead)
-- Modify: `package.json` (add `test` script)
-
-**Interfaces:**
-- Consumes: nothing.
-- Produces:
- - `slugify(s: string) -> string`
- - `parseSummary(text: string) -> Array<{ depth: number, label: string, source: string, section: { label: string, slug: string } }>`
-
-- [ ] **Step 1: Write the failing test**
-
-Create `scripts/lib/summary.test.mjs`:
-
-```js
-import { test } from 'node:test';
-import assert from 'node:assert/strict';
-import { parseSummary, slugify } from './summary.mjs';
-
-test('slugify lowercases and hyphenates', () => {
- assert.equal(slugify('CORE CONCEPTS'), 'core-concepts');
- assert.equal(slugify('Developing With OpenDialog'), 'developing-with-opendialog');
-});
-
-test('a section heading anchor id becomes the section slug', () => {
- const entries = parseSummary(
- '## GETTING STARTED <a href="#getting-started-1" id="getting-started-1"></a>\n' +
- '\n* [Introduction](README.md)\n'
- );
- assert.equal(entries[0].section.slug, 'getting-started-1');
- assert.equal(entries[0].section.label, 'GETTING STARTED');
-});
-
-test('a section heading without an anchor slugifies its text', () => {
- const entries = parseSummary('## CORE CONCEPTS\n\n* [Model](model.md)\n');
- assert.equal(entries[0].section.slug, 'core-concepts');
-});
-
-test('escaped brackets in a label are unescaped, not dropped', () => {
- // A label regex of \[([^\]]*)\] silently drops these four live pages.
- const entries = parseSummary(
- '## CREATE AI APPLICATIONS\n\n* [\\[Deprecated\\] webhook actions](a/b.md)\n'
- );
- assert.equal(entries.length, 1);
- assert.equal(entries[0].label, '[Deprecated] webhook actions');
- assert.equal(entries[0].source, 'a/b.md');
-});
-
-test('indentation is captured as depth', () => {
- const entries = parseSummary(
- '## S\n\n* [Parent](p/README.md)\n * [Child](p/c.md)\n * [Grandchild](p/c/g.md)\n'
- );
- assert.deepEqual(entries.map((e) => e.depth), [0, 2, 4]);
-});
-
-test('percent-encoded paths are decoded', () => {
- const entries = parseSummary('## S\n\n* [X](a/b%20c.md)\n');
- assert.equal(entries[0].source, 'a/b c.md');
-});
-
-test('list items before any section heading are ignored', () => {
- assert.deepEqual(parseSummary('* [Orphan](x.md)\n'), []);
-});
-```
-
-- [ ] **Step 2: Run test to verify it fails**
-
-Run: `node --test scripts/lib/summary.test.mjs`
-Expected: FAIL — `Cannot find module './summary.mjs'`
-
-- [ ] **Step 3: Write the implementation**
-
-Create `scripts/lib/summary.mjs` by moving the parser out of `scripts/routes.mjs` unchanged:
-
-```js
-/**
- * Parses source/SUMMARY.md, GitBook's navigation file, into an ordered list of entries.
- *
- * SUMMARY.md is the source of truth for both the sidebar and the live URL of every page.
- * routes.mjs and sidebar.mjs must agree exactly, so they share this parser.
- */
-
-/** Lowercases and hyphenates a heading into a URL segment. */
-export const slugify = (s) => s.toLowerCase().replace(/[^a-z0-9]+/g, '-').replace(/^-|-$/g, '');
-
-/** Parses SUMMARY.md into an ordered list of nav entries. */
-export function parseSummary(text) {
- const entries = [];
- let section = null;
- for (const line of text.split('\n')) {
- const heading = line.match(/^##\s+(.*)$/);
- if (heading) {
- const raw = heading[1];
- // "## GETTING STARTED <a href="#getting-started-1" id="getting-started-1"></a>"
- // The anchor id, where present, is the URL segment for the section.
- const anchor = raw.match(/id="([^"]+)"/);
- const label = raw.replace(/<a\b[^>]*>.*?<\/a>/g, '').trim();
- section = { label, slug: anchor ? anchor[1] : slugify(label) };
- continue;
- }
- // Labels may contain escaped brackets — "[\[Deprecated\] webhook actions]" — so the
- // label is matched greedily up to the final "](".
- const item = line.match(/^(\s*)\*\s+\[(.*)\]\(([^)]+)\)/);
- if (item && section) {
- entries.push({
- depth: item[1].length,
- label: item[2].replace(/\\([[\]])/g, '$1'),
- source: decodeURIComponent(item[3]).trim(),
- section,
- });
- }
- }
- return entries;
-}
-```
-
-- [ ] **Step 4: Run test to verify it passes**
-
-Run: `node --test scripts/lib/summary.test.mjs`
-Expected: PASS, 7 tests
-
-- [ ] **Step 5: Point `routes.mjs` at the shared parser**
-
-In `scripts/routes.mjs`, delete the `slugify` const (line 20) and the whole `parseSummary`
-function (lines 22–50), and add to the imports at the top:
-
-```js
-import { parseSummary } from './lib/summary.mjs';
-```
-
-`slugify` is not used elsewhere in `routes.mjs`, so no other change is needed.
-
-- [ ] **Step 6: Verify `routes.mjs` still passes 204/204**
-
-Run: `node scripts/routes.mjs`
-Expected output ends with:
-```
-pages derived : 204
-live sitemap URLs : 204
-unreachable : 0
-not live today : 0
-route parity: OK
-```
-
-- [ ] **Step 7: Verify `route-map.json` is unchanged**
-
-Run: `git diff --stat route-map.json`
-Expected: no output. The refactor must not alter the generated file by even one byte.
-
-- [ ] **Step 8: Add the test script**
-
-In `package.json`, add to `"scripts"`:
-
-```json
- "test": "node --test \"scripts/lib/*.test.mjs\"",
-```
-
-Verify: `npm test` runs and reports the summary tests. The quoted glob matters — a bare
-directory argument fails on the locally installed Node 22.x.
-
-- [ ] **Step 9: Commit**
-
-```bash
-git add scripts/lib/summary.mjs scripts/lib/summary.test.mjs scripts/routes.mjs package.json
-git commit -m "Share the SUMMARY.md parser between routes and sidebar"
-```
-
----
-
-### Task 2: Code-safety primitives
-
-Fenced code and inline code spans must be immune to every transformation. The corpus contains
-`{first_name}` inside JSON fences, `{% code %}` wrapping fences, `{% columns %}` spanning
-fences, and 1,317 asset filenames containing parentheses. This is the single largest source of
-silent corruption, so it is the most heavily tested module.
-
-**Files:**
-- Create: `scripts/lib/segments.mjs`
-- Create: `scripts/lib/segments.test.mjs`
-
-**Interfaces:**
-- Consumes: nothing.
-- Produces:
- - `mapLines(text: string, fn: (line: string) => string | string[] | null) -> string` — calls `fn` only on lines outside fenced code. Returning `null` deletes the line; returning an array splices in several. Fence delimiter lines and fence contents pass through untouched.
- - `protectCode(text: string, fn: (masked: string) => string) -> string` — masks fenced blocks and inline code spans with `\u0000<n>\u0000` tokens, applies `fn`, restores.
-
-- [ ] **Step 1: Write the failing test**
-
-Create `scripts/lib/segments.test.mjs`:
-
-```js
-import { test } from 'node:test';
-import assert from 'node:assert/strict';
-import { mapLines, protectCode } from './segments.mjs';
-
-const upper = (line) => line.toUpperCase();
-
-test('mapLines transforms prose lines', () => {
- assert.equal(mapLines('a\nb', upper), 'A\nB');
-});
-
-test('mapLines leaves fenced code and its delimiters untouched', () => {
- const input = 'a\n```json\n{ "k": "v" }\n```\nb';
- assert.equal(mapLines(input, upper), 'A\n```json\n{ "k": "v" }\n```\nB');
-});
-
-test('mapLines lets a block construct span a fence', () => {
- // {% columns %} wraps fenced code in the real corpus. Open and close markers must
- // both reach the callback even though a fence sits between them.
- const seen = [];
- const input = '{% columns %}\n```json\n{ "a": 1 }\n```\n{% endcolumns %}';
- mapLines(input, (line) => {
- seen.push(line);
- return line;
- });
- assert.deepEqual(seen, ['{% columns %}', '{% endcolumns %}']);
-});
-
-test('mapLines does not treat an indented info string as a closing fence', () => {
- const input = '```js\nconst a = 1;\n```\nx';
- assert.equal(mapLines(input, upper), '```js\nconst a = 1;\n```\nX');
-});
-
-test('mapLines supports tilde fences', () => {
- assert.equal(mapLines('~~~\nx\n~~~\ny', upper), '~~~\nx\n~~~\nY');
-});
-
-test('mapLines treats an unterminated fence as code to the end', () => {
- assert.equal(mapLines('a\n```\nb\nc', upper), 'A\n```\nb\nc');
-});
-
-test('mapLines can delete and splice lines', () => {
- assert.equal(mapLines('a\nb', (l) => (l === 'a' ? null : ['x', 'y'])), 'x\ny');
-});
-
-test('protectCode hides fenced blocks from a regex transform', () => {
- const input = 'say {hello}\n```\nkeep {hello}\n```';
- const out = protectCode(input, (t) => t.replaceAll('{hello}', 'WORLD'));
- assert.equal(out, 'say WORLD\n```\nkeep {hello}\n```');
-});
-
-test('protectCode hides inline code spans', () => {
- const out = protectCode('a `{x}` b {x}', (t) => t.replaceAll('{x}', 'Y'));
- assert.equal(out, 'a `{x}` b Y');
-});
-
-test('protectCode handles a path with parentheses outside code', () => {
- const input = '.png>)';
- const out = protectCode(input, (t) => t.replace('../.gitbook/assets/', '/.gitbook/assets/'));
- assert.equal(out, '.png>)');
-});
-
-test('protectCode is a round trip when the transform does nothing', () => {
- const input = 'a\n```js\nconst x = `t`;\n```\n`inline` b';
- assert.equal(protectCode(input, (t) => t), input);
-});
-
-test('protectCode restores double-backtick spans', () => {
- const input = 'a ``code with ` tick`` b';
- assert.equal(protectCode(input, (t) => t), input);
-});
-```
-
-- [ ] **Step 2: Run test to verify it fails**
-
-Run: `node --test scripts/lib/segments.test.mjs`
-Expected: FAIL — `Cannot find module './segments.mjs'`
-
-- [ ] **Step 3: Write the implementation**
-
-Create `scripts/lib/segments.mjs`:
-
-```js
-/**
- * Code-safety primitives. Every markdown transformation in this pipeline is built on one of
- * these two functions so that fenced code blocks and inline code spans are never modified.
- *
- * The source contains `{first_name}` inside JSON fences, `{% code %}` blocks wrapping fences,
- * and 1,317 asset filenames containing parentheses. A transform that reaches inside code
- * corrupts content silently, which is why these are the foundation rather than a convenience.
- */
-
-const FENCE = /^(\s*)(`{3,}|~{3,})(.*)$/;
-const TOKEN = '\u0000';
-
-/** True when `line` closes a fence opened with `marker`. A closing fence carries no info string. */
-function closesFence(match, marker) {
- return match[2][0] === marker[0] && match[2].length >= marker.length && match[3].trim() === '';
-}
-
-/**
- * Applies `fn` to every line that sits outside a fenced code block.
- *
- * Fence delimiters and fence contents pass through untouched and are never shown to `fn`.
- * Because this is a single stateful pass over all lines, a block construct whose open and
- * close markers straddle a fence — as `{% columns %}` does — still sees both markers.
- *
- * `fn` may return a string, an array of strings to splice in, or null to delete the line.
- */
-export function mapLines(text, fn) {
- const out = [];
- let marker = null;
- for (const line of text.split('\n')) {
- const match = line.match(FENCE);
- if (marker === null) {
- if (match) {
- marker = match[2];
- out.push(line);
- continue;
- }
- const result = fn(line);
- if (result === null) continue;
- if (Array.isArray(result)) out.push(...result);
- else out.push(result);
- continue;
- }
- if (match && closesFence(match, marker)) marker = null;
- out.push(line);
- }
- return out.join('\n');
-}
-
-/**
- * Masks fenced code blocks and inline code spans, applies `fn` to what remains, then restores.
- *
- * For inline transformations — link rewriting, entity stripping, brace escaping — which never
- * span a fence. Note that a fenced block collapses to a single token line while masked, so
- * `fn` must not depend on line structure. Use mapLines for anything that does.
- */
-export function protectCode(text, fn) {
- const stash = [];
- const keep = (s) => `${TOKEN}${stash.push(s) - 1}${TOKEN}`;
- const masked = [];
- let marker = null;
- let block = [];
-
- for (const line of text.split('\n')) {
- const match = line.match(FENCE);
- if (marker === null) {
- if (match) {
- marker = match[2];
- block = [line];
- continue;
- }
- masked.push(line.replace(/(`+)(?:(?!\1).)*\1/g, keep));
- continue;
- }
- block.push(line);
- if (match && closesFence(match, marker)) {
- masked.push(keep(block.join('\n')));
- marker = null;
- block = [];
- }
- }
- // An unterminated fence is still code; keep it masked rather than exposing it to `fn`.
- if (marker !== null) masked.push(keep(block.join('\n')));
-
- return fn(masked.join('\n')).replace(
- new RegExp(`${TOKEN}(\\d+)${TOKEN}`, 'g'),
- (_, index) => stash[Number(index)]
- );
-}
-```
-
-- [ ] **Step 4: Run test to verify it passes**
-
-Run: `node --test scripts/lib/segments.test.mjs`
-Expected: PASS, 12 tests
-
-- [ ] **Step 5: Commit**
-
-```bash
-git add scripts/lib/segments.mjs scripts/lib/segments.test.mjs
-git commit -m "Add code-safety primitives for markdown transforms"
-```
-
----
-
-### Task 3: Frontmatter
-
-29 of the 71 GitBook `description` values use YAML folded block scalars (`>-`). A line-based
-`^description:\s*(.*)$` parser returns an empty string for all 29, silently dropping the lead
-text that Phase 1 added a `PageTitle` override specifically to display. `hidden: true` appears
-on two pages that are both live in the sitemap and must be dropped, not honoured.
-
-**Files:**
-- Create: `scripts/lib/frontmatter.mjs`
-- Create: `scripts/lib/frontmatter.test.mjs`
-
-**Interfaces:**
-- Consumes: `mapLines` from `./segments.mjs`.
-- Produces:
- - `parseFrontmatter(text: string) -> { data: Record<string, string>, body: string }` — throws on any YAML construct it does not recognise.
- - `emitFrontmatter(fields: { title: string, description?: string }) -> string` — returns the block including trailing newline.
- - `takeTitle(body: string) -> { title: string | null, body: string }` — removes the first H1 and returns it. Title derivation lives beside frontmatter emission because the title comes from the body, not from the frontmatter.
-
-- [ ] **Step 1: Write the failing test**
-
-Create `scripts/lib/frontmatter.test.mjs`:
-
-```js
-import { test } from 'node:test';
-import assert from 'node:assert/strict';
-import { emitFrontmatter, parseFrontmatter, takeTitle } from './frontmatter.mjs';
-
-test('a file with no frontmatter returns the whole text as body', () => {
- assert.deepEqual(parseFrontmatter('# Title\n'), { data: {}, body: '# Title\n' });
-});
-
-test('a plain scalar description is read', () => {
- const { data, body } = parseFrontmatter('---\ndescription: Hello there\n---\n\n# T\n');
- assert.equal(data.description, 'Hello there');
- assert.equal(body, '\n# T\n');
-});
-
-test('a folded block scalar is folded into one line', () => {
- // 29 of 71 descriptions use this form. A line-based parser drops them all.
- const text =
- '---\ndescription: >-\n Before jumping into the build process, you need a clear\n' +
- ' understanding of the key building blocks.\n---\n\n# T\n';
- assert.equal(
- parseFrontmatter(text).data.description,
- 'Before jumping into the build process, you need a clear understanding of the key building blocks.'
- );
-});
-
-test('hidden is parsed so the caller can drop it deliberately', () => {
- assert.equal(parseFrontmatter('---\nhidden: true\n---\n\n# T\n').data.hidden, 'true');
-});
-
-test('quoted scalars are unquoted', () => {
- assert.equal(parseFrontmatter("---\ndescription: 'a: b'\n---\n").data.description, 'a: b');
-});
-
-test('an unrecognised YAML construct throws rather than losing data', () => {
- assert.throws(() => parseFrontmatter('---\ntags:\n - a\n - b\n---\n'), /unsupported/i);
- assert.throws(() => parseFrontmatter('---\ndescription: |\n literal\n---\n'), /unsupported/i);
-});
-
-test('emitFrontmatter writes title and description', () => {
- assert.equal(
- emitFrontmatter({ title: 'Getting ready', description: 'Some text' }),
- '---\ntitle: Getting ready\ndescription: Some text\n---\n'
- );
-});
-
-test('emitFrontmatter omits an absent or empty description', () => {
- assert.equal(emitFrontmatter({ title: 'T' }), '---\ntitle: T\n---\n');
- assert.equal(emitFrontmatter({ title: 'T', description: '' }), '---\ntitle: T\n---\n');
-});
-
-test('emitFrontmatter quotes values that YAML would misread', () => {
- assert.equal(
- emitFrontmatter({ title: 'Semantic Classifier: Query Classifier' }),
- "---\ntitle: 'Semantic Classifier: Query Classifier'\n---\n"
- );
- assert.equal(
- emitFrontmatter({ title: '[Deprecated] webhook actions' }),
- "---\ntitle: '[Deprecated] webhook actions'\n---\n"
- );
-});
-
-test('emitFrontmatter doubles single quotes inside a quoted value', () => {
- assert.equal(
- emitFrontmatter({ title: "Don't: stop" }),
- "---\ntitle: 'Don''t: stop'\n---\n"
- );
-});
-
-test('parse then emit round trips a folded description', () => {
- const { data } = parseFrontmatter('---\ndescription: >-\n a\n b\n---\n');
- assert.equal(emitFrontmatter({ title: 'T', description: data.description }),
- '---\ntitle: T\ndescription: a b\n---\n');
-});
-
-test('takeTitle removes the H1 and returns its text', () => {
- assert.deepEqual(takeTitle('# Getting ready\n\nBody text.\n'), {
- title: 'Getting ready',
- body: '\nBody text.\n',
- });
-});
-
-test('takeTitle strips inline tags and unescapes brackets', () => {
- assert.equal(takeTitle('# \\[Deprecated] webhook actions\n').title, '[Deprecated] webhook actions');
- assert.equal(takeTitle('# Best <mark>practices</mark>\n').title, 'Best practices');
-});
-
-test('takeTitle ignores a # line inside a fenced code block', () => {
- // Four source files open a shell fence with a comment; that must not become the title.
- const body = '```bash\n# Install the CLI\n```\n\n# Real title\n';
- const { title, body: rest } = takeTitle(body);
- assert.equal(title, 'Real title');
- assert.ok(rest.includes('# Install the CLI'), 'the fenced comment must survive');
-});
-
-test('takeTitle removes only the first H1', () => {
- const { title, body } = takeTitle('# One\n\n# Two\n');
- assert.equal(title, 'One');
- assert.ok(body.includes('# Two'));
-});
-
-test('takeTitle returns null when there is no H1', () => {
- assert.equal(takeTitle('Just prose.\n').title, null);
-});
-```
-
-- [ ] **Step 2: Run test to verify it fails**
-
-Run: `node --test scripts/lib/frontmatter.test.mjs`
-Expected: FAIL — `Cannot find module './frontmatter.mjs'`
-
-- [ ] **Step 3: Write the implementation**
-
-Create `scripts/lib/frontmatter.mjs`:
-
-```js
-/**
- * GitBook frontmatter in, Starlight frontmatter out.
- *
- * The corpus uses exactly two YAML scalar forms: plain, and folded block scalars ( >- ) which
- * carry 29 of the 71 page descriptions. Anything else throws, so a shape that appears in a
- * later GitBook sync fails loudly at cutover instead of silently dropping a description.
- *
- * Title derivation lives here too: Starlight takes the title from frontmatter, but GitBook
- * keeps it as the body's H1, so the two belong together.
- */
-import { mapLines } from './segments.mjs';
-
-const KEY = /^([A-Za-z_][\w-]*):[ \t]*(.*)$/;
-
-/** Strips matching surrounding quotes from a plain YAML scalar. */
-function unquote(value) {
- const match = value.match(/^(['"])([\s\S]*)\1$/);
- return match ? match[2].replace(/''/g, "'") : value;
-}
-
-/**
- * Splits leading YAML frontmatter from the markdown body.
- *
- * Returns every key as a string; the caller decides which to keep. `hidden` in particular is
- * parsed but must be dropped by the caller — the two pages carrying it are both live.
- */
-export function parseFrontmatter(text) {
- const match = text.match(/^---\n([\s\S]*?)\n---\n?/);
- if (!match) return { data: {}, body: text };
-
- const data = {};
- const lines = match[1].split('\n');
- for (let i = 0; i < lines.length; i++) {
- const line = lines[i];
- if (line.trim() === '') continue;
- const kv = line.match(KEY);
- if (!kv) throw new Error(`unsupported YAML in frontmatter: ${JSON.stringify(line)}`);
- const [, key, rest] = kv;
-
- if (rest === '>-' || rest === '>') {
- const folded = [];
- while (i + 1 < lines.length && /^\s+\S/.test(lines[i + 1])) folded.push(lines[++i].trim());
- data[key] = folded.join(' ');
- continue;
- }
- if (rest.startsWith('|')) {
- throw new Error(`unsupported YAML literal block scalar for key ${key}`);
- }
- if (rest === '') throw new Error(`unsupported YAML nested value for key ${key}`);
- data[key] = unquote(rest.trim());
- }
- return { data, body: text.slice(match[0].length) };
-}
-
-/** True when a value must be single-quoted to survive a YAML round trip. */
-function needsQuoting(value) {
- return /^[\s>|*&!%@`'"[{#-]/.test(value) || /: |:$|\s#|\s$/.test(value);
-}
-
-/** Serialises one scalar, quoting only when YAML would otherwise misread it. */
-function scalar(value) {
- return needsQuoting(value) ? `'${value.replace(/'/g, "''")}'` : value;
-}
-
-/** Emits the Starlight frontmatter block, including its trailing newline. */
-export function emitFrontmatter({ title, description }) {
- const lines = ['---', `title: ${scalar(title)}`];
- if (description) lines.push(`description: ${scalar(description)}`);
- lines.push('---', '');
- return lines.join('\n');
-}
-
-/**
- * Removes the first H1 from the body and returns its text.
- *
- * Starlight renders the frontmatter title as the page heading, so leaving the H1 in place
- * would show it twice. Uses mapLines so a "# comment" opening a shell fence — which four
- * source files have — is never mistaken for the title.
- */
-export function takeTitle(body) {
- let title = null;
- const rest = mapLines(body, (line) => {
- if (title !== null) return line;
- const h1 = line.match(/^#\s+(.*)$/);
- if (!h1) return line;
- title = h1[1].replace(/<[^>]*>/g, '').replace(/\\([[\]])/g, '$1').trim();
- return null;
- });
- return { title, body: rest };
-}
-```
-
-- [ ] **Step 4: Run test to verify it passes**
-
-Run: `node --test scripts/lib/frontmatter.test.mjs`
-Expected: PASS, 16 tests
-
-- [ ] **Step 5: Verify the parser handles the whole corpus**
-
-Run:
-```bash
-node -e '
-import("./scripts/lib/frontmatter.mjs").then(({ parseFrontmatter, takeTitle }) => {
- const fs = require("fs");
- const rm = JSON.parse(fs.readFileSync("route-map.json", "utf8"));
- let withDescription = 0, withTitle = 0;
- for (const r of rm) {
- const { data, body } = parseFrontmatter(fs.readFileSync("source/" + r.source, "utf8"));
- if (data.description) withDescription++;
- if (takeTitle(body).title) withTitle++;
- }
- console.log("descriptions parsed:", withDescription, " titles found:", withTitle);
-});'
-```
-Expected: `descriptions parsed: 71 titles found: 204`.
-
-A description count below 71 means the folded block scalar handling is wrong — that is the
-failure mode this module exists to prevent, and it is silent. Any throw means an unrecognised
-YAML shape; fix the parser, do not widen the catch.
-
-- [ ] **Step 6: Commit**
-
-```bash
-git add scripts/lib/frontmatter.mjs scripts/lib/frontmatter.test.mjs
-git commit -m "Parse GitBook frontmatter including folded block scalars"
-```
-
----
-
-### Task 4: Link extraction and rewriting
-
-381 in-prose page links must become route URLs: 311 in `.md` form and 70 in directory form
-(`.../webhook-action/`), the latter absent from the brief entirely. A naive `\]\(([^)]+)\)`
-regex truncates at the first `)` inside `image (149).png` and mangles 1,317 asset filenames —
-this is not hypothetical, it produced a false "unresolved link" report during design.
-
-**Files:**
-- Create: `scripts/lib/links.mjs`
-- Create: `scripts/lib/links.test.mjs`
-
-**Interfaces:**
-- Consumes: `protectCode` from `./segments.mjs`.
-- Produces:
- - `extractTargets(text: string) -> Array<{ start: number, end: number, target: string, angled: boolean }>` — character offsets of every markdown link/image destination.
- - `resolveSource(fromSource: string, target: string) -> string | null` — resolves a relative link to a `source/`-relative `.md` path, clamping `..` at the root. Returns `null` for external, `mailto:`, bare anchors and `/broken/pages/`.
- - `rewriteLinks(text: string, { source: string, routes: Map<string, { url: string }> }) -> string` — throws `Error` naming the file and target on any unresolved internal page link.
-
-- [ ] **Step 1: Write the failing test**
-
-Create `scripts/lib/links.test.mjs`:
-
-```js
-import { test } from 'node:test';
-import assert from 'node:assert/strict';
-import { extractTargets, resolveSource, rewriteLinks } from './links.mjs';
-
-const routes = new Map([
- ['a/b.md', { url: '/section/a/b' }],
- ['a/c/README.md', { url: '/section/a/c' }],
- ['top.md', { url: '/section/top' }],
-]);
-const ctx = { source: 'a/start.md', routes };
-
-test('extractTargets keeps balanced parentheses in a bare path', () => {
- const found = extractTargets('.png)');
- assert.deepEqual(found.map((f) => f.target), ['../.gitbook/assets/image (149).png']);
-});
-
-test('extractTargets reads the angle-bracket form', () => {
- const found = extractTargets('.png>)');
- assert.equal(found[0].target, '../.gitbook/assets/a b (1).png');
- assert.equal(found[0].angled, true);
-});
-
-test('extractTargets finds several targets on one line', () => {
- assert.deepEqual(extractTargets('[a](x.md) and [b](y.md)').map((f) => f.target), ['x.md', 'y.md']);
-});
-
-test('extractTargets ignores an unclosed destination', () => {
- assert.deepEqual(extractTargets('[a](x.md'), []);
-});
-
-test('resolveSource resolves a relative .md link', () => {
- assert.equal(resolveSource('a/start.md', 'b.md'), 'a/b.md');
- assert.equal(resolveSource('a/start.md', '../top.md'), 'top.md');
-});
-
-test('resolveSource maps a directory link to that directory README', () => {
- assert.equal(resolveSource('a/start.md', 'c/'), 'a/c/README.md');
-});
-
-test('resolveSource clamps .. at the source root', () => {
- // secret-context.md carries one ../ too many and would otherwise escape the repo.
- assert.equal(
- resolveSource('core-concepts/contexts-and-attributes/secret-context.md',
- '../../../opendialog-platform/actions/webhook-action/'),
- 'opendialog-platform/actions/webhook-action/README.md'
- );
-});
-
-test('resolveSource returns null for links that are not internal pages', () => {
- for (const t of ['https://x.com/y', 'mailto:a@b.c', '#anchor', '/broken/pages/abc']) {
- assert.equal(resolveSource('a/start.md', t), null, t);
- }
-});
-
-test('resolveSource returns null for an asset reference', () => {
- assert.equal(resolveSource('a/start.md', '../.gitbook/assets/x.png'), null);
-});
-
-test('rewriteLinks maps a .md link to its route URL', () => {
- assert.equal(rewriteLinks('see [B](b.md)', ctx), 'see [B](/section/a/b)');
-});
-
-test('rewriteLinks preserves an anchor', () => {
- assert.equal(rewriteLinks('[B](b.md#how-to)', ctx), '[B](/section/a/b#how-to)');
-});
-
-test('rewriteLinks maps a directory link', () => {
- assert.equal(rewriteLinks('[C](c/)', ctx), '[C](/section/a/c)');
-});
-
-test('rewriteLinks leaves external links, anchors and broken pages alone', () => {
- const input = '[x](https://a.b) [y](#z) [w](/broken/pages/QQ) [v](mailto:a@b.c)';
- assert.equal(rewriteLinks(input, ctx), input);
-});
-
-test('rewriteLinks does not touch links inside code', () => {
- const input = '```\n[B](b.md)\n```\n`[B](b.md)`';
- assert.equal(rewriteLinks(input, ctx), input);
-});
-
-test('rewriteLinks leaves asset references untouched for Phase 3', () => {
- const input = '.png>)';
- assert.equal(rewriteLinks(input, ctx), input);
-});
-
-test('rewriteLinks throws, naming file and target, on an unresolved page link', () => {
- assert.throws(() => rewriteLinks('[Q](missing.md)', ctx), /a\/start\.md.*missing\.md/s);
-});
-```
-
-- [ ] **Step 2: Run test to verify it fails**
-
-Run: `node --test scripts/lib/links.test.mjs`
-Expected: FAIL — `Cannot find module './links.mjs'`
-
-- [ ] **Step 3: Write the implementation**
-
-Create `scripts/lib/links.mjs`:
-
-```js
-/**
- * Rewrites GitBook's relative page links to the live route URLs held in route-map.json.
- *
- * Destinations are extracted by scanning rather than by regex: 1,317 asset filenames contain
- * parentheses, and `\]\(([^)]+)\)` truncates at the first one, silently mangling the path.
- */
-import path from 'node:path';
-import { protectCode } from './segments.mjs';
-
-const ASSET = /(^|\/)\.gitbook\/assets\//;
-
-/** Character offsets of every markdown link or image destination in `text`. */
-export function extractTargets(text) {
- const found = [];
- for (let i = 0; i < text.length - 1; i++) {
- if (text[i] !== ']' || text[i + 1] !== '(') continue;
- const open = i + 2;
- if (text[open] === '<') {
- const close = text.indexOf('>', open);
- if (close === -1 || text[close + 1] !== ')') continue;
- found.push({ start: open, end: close + 1, target: text.slice(open + 1, close), angled: true });
- i = close + 1;
- continue;
- }
- let depth = 1;
- let j = open;
- for (; j < text.length; j++) {
- if (text[j] === '(') depth++;
- else if (text[j] === ')') { if (--depth === 0) break; }
- else if (text[j] === '\n') { depth = -1; break; }
- }
- if (depth !== 0) continue;
- found.push({ start: open, end: j, target: text.slice(open, j), angled: false });
- i = j;
- }
- return found;
-}
-
-/**
- * Resolves a link destination to a source-relative .md path, or null when it is not an
- * internal page link.
- *
- * `..` is clamped at the source root. GitBook clamps too, which is why
- * core-concepts/contexts-and-attributes/secret-context.md resolves on the live site despite
- * carrying one ../ too many.
- */
-export function resolveSource(fromSource, target) {
- const clean = target.trim();
- if (clean === '' || /^(https?:|mailto:|tel:|#)/.test(clean)) return null;
- if (clean.startsWith('/broken/pages/')) return null;
-
- const withoutAnchor = decodeURIComponent(clean.replace(/#.*/, ''));
- if (withoutAnchor === '' || ASSET.test(withoutAnchor)) return null;
-
- let relative;
- if (withoutAnchor.endsWith('/')) relative = `${withoutAnchor}README.md`;
- else if (withoutAnchor.endsWith('.md')) relative = withoutAnchor;
- else return null;
-
- const joined = path.posix.join(path.posix.dirname(fromSource), relative);
- // path.posix.normalize keeps leading "../" segments; drop them to clamp at the root.
- return path.posix.normalize(joined).replace(/^(\.\.\/)+/, '');
-}
-
-/** Rewrites every internal page link in `text` to its route URL. Throws on any that misses. */
-export function rewriteLinks(text, { source, routes }) {
- return protectCode(text, (masked) => {
- let out = '';
- let cursor = 0;
- for (const { start, end, target, angled } of extractTargets(masked)) {
- const resolved = resolveSource(source, target);
- if (resolved === null) continue;
- const route = routes.get(resolved);
- if (!route) {
- throw new Error(`${source}: link target does not resolve to a page: ${target} -> ${resolved}`);
- }
- const anchor = target.includes('#') ? target.slice(target.indexOf('#')) : '';
- const url = `${route.url}${anchor}`;
- out += masked.slice(cursor, start) + (angled ? `<${url}>` : url);
- cursor = end;
- }
- return out + masked.slice(cursor);
- });
-}
-```
-
-**Offsets:** `start` and `end` bracket exactly the text to replace, so both forms splice
-identically. For the angle-bracket form `start` is the index of `<` and `end` the index just
-past `>`, so writing `<url>` replaces the whole bracketed destination and leaves the `)`. For
-the bare form `start` is the first character of the path and `end` the index of `)`. The
-"leaves external links alone" and "leaves asset references untouched" tests are round trips —
-if they pass, the offsets are right.
-
-- [ ] **Step 4: Run test to verify it passes**
-
-Run: `node --test scripts/lib/links.test.mjs`
-Expected: PASS, 16 tests
-
-- [ ] **Step 5: Verify against the whole corpus**
-
-Run:
-```bash
-node -e '
-Promise.all([import("./scripts/lib/links.mjs")]).then(([{ rewriteLinks }]) => {
- const fs = require("fs");
- const rm = JSON.parse(fs.readFileSync("route-map.json", "utf8"));
- const routes = new Map(rm.map((r) => [r.source, r]));
- let rewritten = 0;
- for (const r of rm) {
- const before = fs.readFileSync("source/" + r.source, "utf8");
- const after = rewriteLinks(before, { source: r.source, routes });
- if (before !== after) rewritten++;
- }
- console.log("files with rewritten links:", rewritten);
-});'
-```
-Expected: completes without throwing. A throw names the offending file and target — investigate
-it rather than loosening the check.
-
-- [ ] **Step 6: Commit**
-
-```bash
-git add scripts/lib/links.mjs scripts/lib/links.test.mjs
-git commit -m "Rewrite relative page links to route URLs"
-```
-
----
-
-### Task 5: GitBook blocks that stay in `.md`
-
-Hints (258), `{% code %}` (7) and `{% file %}` (1) need no Starlight component, so files
-containing only these stay `.md`. `{% code %}` must run **before** any fence-aware pass,
-because it wraps a fence and rewrites that fence's info string.
-
-**Files:**
-- Create: `scripts/lib/gitbook-blocks.mjs`
-- Create: `scripts/lib/gitbook-blocks.test.mjs`
-
-**Interfaces:**
-- Consumes: `mapLines` from `./segments.mjs`.
-- Produces:
- - `convertCode(text: string) -> string` — run first, before segmentation-dependent passes.
- - `convertHints(text: string) -> string`
- - `convertFile(text: string) -> string`
- - `stripEntities(text: string) -> string`
-
-- [ ] **Step 1: Write the failing test**
-
-Create `scripts/lib/gitbook-blocks.test.mjs`:
-
-```js
-import { test } from 'node:test';
-import assert from 'node:assert/strict';
-import { convertCode, convertFile, convertHints, stripEntities } from './gitbook-blocks.mjs';
-
-test('each hint style maps to its Starlight aside', () => {
- const cases = [
- ['info', 'note'],
- ['success', 'tip'],
- ['warning', 'caution'],
- ['danger', 'danger'],
- ];
- for (const [style, aside] of cases) {
- assert.equal(
- convertHints(`{% hint style="${style}" %}\nBody\n{% endhint %}`),
- `:::${aside}\nBody\n:::`
- );
- }
-});
-
-test('hints inside a fence are left alone', () => {
- const input = '```\n{% hint style="info" %}\n```';
- assert.equal(convertHints(input), input);
-});
-
-test('convertCode moves title onto the fence info string', () => {
- assert.equal(
- convertCode('{% code title="index.html" %}\n```html\n<p></p>\n```\n{% endcode %}'),
- '```html title="index.html"\n<p></p>\n```'
- );
-});
-
-test('convertCode maps lineNumbers to showLineNumbers', () => {
- assert.equal(
- convertCode('{% code lineNumbers="true" %}\n```json\n{}\n```\n{% endcode %}'),
- '```json showLineNumbers\n{}\n```'
- );
-});
-
-test('convertCode drops fullWidth, which Expressive Code has no equivalent for', () => {
- assert.equal(
- convertCode('{% code fullWidth="false" %}\n```ts\nx\n```\n{% endcode %}'),
- '```ts\nx\n```'
- );
-});
-
-test('convertCode preserves a fence with no language', () => {
- assert.equal(
- convertCode('{% code title="t" %}\n```\nx\n```\n{% endcode %}'),
- '``` title="t"\nx\n```'
- );
-});
-
-test('convertCode leaves an ordinary fence untouched', () => {
- const input = '```js\nconst a = 1;\n```';
- assert.equal(convertCode(input), input);
-});
-
-test('convertFile becomes a link whose text is the basename', () => {
- assert.equal(
- convertFile('{% file src="../../.gitbook/assets/DeliveryKnowledgeBase.csv" %}'),
- '[DeliveryKnowledgeBase.csv](</.gitbook/assets/DeliveryKnowledgeBase.csv>)'
- );
-});
-
-test('an end-of-line entity is stripped, not turned into a trailing space', () => {
- // "word " -> "word " would be a markdown hard break the live site does not render.
- assert.equal(stripEntities('Put a JSON payload here. '), 'Put a JSON payload here.');
- assert.equal(stripEntities('Best practices '), 'Best practices ');
-});
-
-test('a mid-line entity becomes a single space', () => {
- assert.equal(stripEntities('* **Anonymous Authentication**'), '* **Anonymous Authentication**');
- assert.equal(stripEntities(' We split the update'), ' We split the update');
-});
-
-test('entities inside a fence are left alone', () => {
- const input = '```\n \n```';
- assert.equal(stripEntities(input), input);
-});
-```
-
-- [ ] **Step 2: Run test to verify it fails**
-
-Run: `node --test scripts/lib/gitbook-blocks.test.mjs`
-Expected: FAIL — `Cannot find module './gitbook-blocks.mjs'`
-
-- [ ] **Step 3: Write the implementation**
-
-Create `scripts/lib/gitbook-blocks.mjs`:
-
-```js
-/**
- * Converts GitBook's {% %} block syntax to Starlight equivalents.
- *
- * Hints, code and file blocks need no component, so a file containing only these stays .md.
- */
-import { mapLines } from './segments.mjs';
-
-const ASIDE = { info: 'note', success: 'tip', warning: 'caution', danger: 'danger' };
-
-/**
- * Folds {% code %} attributes into the fence's info string.
- *
- * Must run before any fence-aware pass: this block wraps a fence, so removing its markers
- * changes what the fence scanner sees.
- */
-export function convertCode(text) {
- return text.replace(
- /^[ \t]*\{%\s*code([^%]*)%\}\n([ \t]*)(`{3,}|~{3,})([^\n]*)\n([\s\S]*?\n)[ \t]*\3[^\n]*\n[ \t]*\{%\s*endcode\s*%\}[ \t]*$/gm,
- (_, attrs, indent, fence, lang, body) => {
- const info = [lang.trim()];
- const title = attrs.match(/title="([^"]*)"/);
- if (title) info.push(`title="${title[1]}"`);
- if (/lineNumbers="true"/.test(attrs)) info.push('showLineNumbers');
- const suffix = info.filter(Boolean).join(' ');
- return `${indent}${fence}${suffix ? ` ${suffix}` : ''}\n${body}${indent}${fence}`;
- }
- );
-}
-
-/**
- * Removes GitBook's entity, of which there are 1,203.
- *
- * 1,192 sit at end of line, where the entity is a no-op trailing space. Replacing those with a
- * literal space would leave "… \n" on the 84 lines that already end in a space, which markdown
- * renders as a <br> the live site does not have. Only the 11 mid-line occurrences are real.
- */
-export function stripEntities(text) {
- return mapLines(text, (line) => line.replace(/ $/, '').replaceAll(' ', ' '));
-}
-
-/** Maps {% hint %} blocks to Starlight asides. */
-export function convertHints(text) {
- return mapLines(text, (line) => {
- const open = line.match(/^[ \t]*\{%\s*hint\s+style="([a-z]+)"\s*%\}[ \t]*$/);
- if (open) return `:::${ASIDE[open[1]] ?? 'note'}`;
- if (/^[ \t]*\{%\s*endhint\s*%\}[ \t]*$/.test(line)) return ':::';
- return line;
- });
-}
-
-/** Turns the single {% file %} block into a markdown link to a Phase 3 asset placeholder. */
-export function convertFile(text) {
- return mapLines(text, (line) => {
- const match = line.match(/^[ \t]*\{%\s*file\s+src="([^"]+)"\s*%\}[ \t]*$/);
- if (!match) return line;
- const name = match[1].split('/').pop();
- return `[${name}](</.gitbook/assets/${name}>)`;
- });
-}
-```
-
-The `convertCode` info string is assembled as: language first, then `title="…"`, then
-`showLineNumbers`, single-space separated, with no trailing space when there are no
-attributes. `filter(Boolean)` drops the empty language, which is why a fence with no language
-still produces ` ``` title="t" ` and not ` ``` title="t" `.
-
-- [ ] **Step 4: Run test to verify it passes**
-
-Run: `node --test scripts/lib/gitbook-blocks.test.mjs`
-Expected: PASS, 11 tests
-
-- [ ] **Step 5: Verify the entity count against the corpus**
-
-Run:
-```bash
-node -e '
-import("./scripts/lib/gitbook-blocks.mjs").then(({ stripEntities }) => {
- const fs = require("fs");
- const rm = JSON.parse(fs.readFileSync("route-map.json", "utf8"));
- let before = 0, after = 0, breaks = 0;
- for (const r of rm) {
- const text = fs.readFileSync("source/" + r.source, "utf8");
- before += (text.match(/ /g) || []).length;
- const out = stripEntities(text);
- after += (out.match(/ /g) || []).length;
- breaks += (out.match(/ {2,}$/gm) || []).length;
- }
- console.log("entities before:", before, " after:", after, " lines ending in 2+ spaces:", breaks);
-});'
-```
-Expected: `entities before: 1203 after: 0`. The trailing-space count is informational — it
-must not be *higher* than the same measure taken on the source, which is what the rule exists
-to guarantee.
-
-- [ ] **Step 6: Commit**
-
-```bash
-git add scripts/lib/gitbook-blocks.mjs scripts/lib/gitbook-blocks.test.mjs
-git commit -m "Convert hint, code and file blocks"
-```
-
----
-
-### Task 6: GitBook blocks that need a component
-
-Embeds (38 across 31 files), steppers (3 blocks / 15 steps) and the single `{% columns %}`
-instance. The columns block wraps fenced code, which is exactly the case `mapLines` exists to
-handle.
-
-**Files:**
-- Modify: `scripts/lib/gitbook-blocks.mjs`
-- Modify: `scripts/lib/gitbook-blocks.test.mjs`
-
-**Interfaces:**
-- Consumes: `mapLines` and `protectCode` from `./segments.mjs`.
-- Produces:
- - `convertEmbeds(text: string) -> string` — video URLs become `<Embed …/>`; others become an autolink.
- - `convertSteppers(text: string) -> string`
- - `convertColumns(text: string) -> string`
- - `isVideoEmbed(url: string) -> boolean` — exported for its own unit test; `convert.mjs` decides `.mdx` promotion from the emitted `<Embed ` marker rather than re-parsing URLs.
-
-- [ ] **Step 1: Write the failing test**
-
-Append to `scripts/lib/gitbook-blocks.test.mjs`:
-
-```js
-import { convertColumns, convertEmbeds, convertSteppers, isVideoEmbed } from './gitbook-blocks.mjs';
-
-test('a self-closing embed becomes an Embed element', () => {
- assert.equal(
- convertEmbeds('{% embed url="https://youtu.be/RhUc_mgkNl8" %}'),
- '<Embed url="https://youtu.be/RhUc_mgkNl8" />'
- );
-});
-
-test('an embed with a caption passes it as title', () => {
- assert.equal(
- convertEmbeds('{% embed url="https://www.loom.com/share/abc" %}\nBuilding an agent\n{% endembed %}'),
- '<Embed url="https://www.loom.com/share/abc" title="Building an agent" />'
- );
-});
-
-test('a caption containing a double quote is escaped for the attribute', () => {
- assert.equal(
- convertEmbeds('{% embed url="https://youtu.be/x" %}\nThe "best" way\n{% endembed %}'),
- '<Embed url="https://youtu.be/x" title="The "best" way" />'
- );
-});
-
-test('a non-video embed becomes a plain link and needs no component', () => {
- assert.equal(
- convertEmbeds('{% embed url="https://webaim.org/resources/contrastchecker/" %}'),
- '<https://webaim.org/resources/contrastchecker/>'
- );
-});
-
-test('isVideoEmbed recognises Loom and YouTube only', () => {
- assert.equal(isVideoEmbed('https://youtu.be/x'), true);
- assert.equal(isVideoEmbed('https://www.youtube.com/watch?v=x'), true);
- assert.equal(isVideoEmbed('https://www.loom.com/share/x'), true);
- assert.equal(isVideoEmbed('https://www.fetchify.com/address-auto-complete'), false);
-});
-
-test('a stepper becomes a Steps ordered list with indented bodies', () => {
- const input = [
- '{% stepper %}',
- '{% step %}',
- '### Navigate to the Secret Context',
- '',
- 'Open the Secret Management page.',
- '{% endstep %}',
- '{% step %}',
- '### Add a secret',
- '{% endstep %}',
- '{% endstepper %}',
- ].join('\n');
- assert.equal(
- convertSteppers(input),
- [
- '<Steps>',
- '',
- '1. ### Navigate to the Secret Context',
- '',
- ' Open the Secret Management page.',
- '',
- '2. ### Add a secret',
- '',
- '</Steps>',
- ].join('\n')
- );
-});
-
-test('columns becomes a CardGrid and the fenced code inside survives', () => {
- const input = [
- '{% columns %}',
- '{% column %}',
- 'Do',
- '```json',
- '{ "firstName": "{first_name}" }',
- '```',
- '{% endcolumn %}',
- '{% column %}',
- "Don't",
- '{% endcolumn %}',
- '{% endcolumns %}',
- ].join('\n');
- const out = convertColumns(input);
- assert.match(out, /^<CardGrid>/);
- assert.match(out, /<\/CardGrid>$/);
- assert.ok(out.includes('{ "firstName": "{first_name}" }'), 'fenced code must survive verbatim');
- assert.ok(!out.includes('{% column'), 'no column markers may remain');
-});
-```
-
-- [ ] **Step 2: Run test to verify it fails**
-
-Run: `node --test scripts/lib/gitbook-blocks.test.mjs`
-Expected: FAIL — `convertEmbeds is not a function` (or an import error)
-
-- [ ] **Step 3: Write the implementation**
-
-Append to `scripts/lib/gitbook-blocks.mjs`, and add `protectCode` to the existing
-`./segments.mjs` import at the top of the file:
-
-```js
-const VIDEO = /^(youtu\.be|youtube\.com|loom\.com)$/;
-
-/** True when an embed URL is one the Embed component can render as an iframe. */
-export function isVideoEmbed(url) {
- try {
- return VIDEO.test(new URL(url).hostname.replace(/^www\./, ''));
- } catch {
- return false;
- }
-}
-
-/** Escapes a caption for use inside a double-quoted JSX attribute. */
-function attribute(value) {
- return value.replace(/&/g, '&').replace(/"/g, '"');
-}
-
-/** Renders one embed. Non-video URLs become autolinks and so need no component. */
-function renderEmbed(url, title) {
- if (!isVideoEmbed(url)) return `<${url}>`;
- return title ? `<Embed url="${url}" title="${attribute(title)}" />` : `<Embed url="${url}" />`;
-}
-
-/**
- * Converts {% embed %} blocks. 36 of the 38 are Loom or YouTube and become <Embed>; the other
- * two are ordinary web pages and become autolinks, so they do not promote a file to .mdx.
- *
- * Done with regex under protectCode rather than a line state machine because no embed block
- * wraps a fenced code block — measured across the corpus, only {% columns %} does — and a
- * state machine would need an end-of-input flush for the 19 self-closing form.
- */
-export function convertEmbeds(text) {
- return protectCode(text, (masked) =>
- masked
- .replace(
- /^[ \t]*\{%\s*embed\s+url="([^"]+)"[^%]*%\}\n([\s\S]*?)\n[ \t]*\{%\s*endembed\s*%\}[ \t]*$/gm,
- (_, url, caption) => renderEmbed(url, caption.replace(/\s+/g, ' ').trim())
- )
- .replace(/^[ \t]*\{%\s*embed\s+url="([^"]+)"[^%]*%\}[ \t]*$/gm, (_, url) => renderEmbed(url, ''))
- );
-}
-
-/** Converts {% stepper %} to a Starlight <Steps> ordered list. */
-export function convertSteppers(text) {
- let inStepper = false;
- let number = 0;
- let body = null;
- return mapLines(text, (line) => {
- if (/^[ \t]*\{%\s*stepper\s*%\}[ \t]*$/.test(line)) {
- inStepper = true;
- number = 0;
- return ['<Steps>', ''];
- }
- if (/^[ \t]*\{%\s*endstepper\s*%\}[ \t]*$/.test(line)) {
- inStepper = false;
- return ['</Steps>'];
- }
- if (!inStepper) return line;
- if (/^[ \t]*\{%\s*step\s*%\}[ \t]*$/.test(line)) {
- number++;
- body = [];
- return [];
- }
- if (/^[ \t]*\{%\s*endstep\s*%\}[ \t]*$/.test(line)) {
- const lines = body ?? [];
- while (lines.length && lines.at(-1).trim() === '') lines.pop();
- const [first, ...rest] = lines;
- body = null;
- return [`${number}. ${first ?? ''}`, ...rest.map((l) => (l.trim() === '' ? '' : ` ${l}`)), ''];
- }
- if (body !== null) {
- body.push(line);
- return [];
- }
- return line;
- });
-}
-
-/** Converts the single {% columns %} block to a CardGrid. */
-export function convertColumns(text) {
- return mapLines(text, (line) => {
- if (/^[ \t]*\{%\s*columns\s*%\}[ \t]*$/.test(line)) return '<CardGrid>';
- if (/^[ \t]*\{%\s*endcolumns\s*%\}[ \t]*$/.test(line)) return '</CardGrid>';
- if (/^[ \t]*\{%\s*(end)?column\s*%\}[ \t]*$/.test(line)) return [];
- return line;
- });
-}
-```
-
-- [ ] **Step 4: Run test to verify it passes**
-
-Run: `node --test scripts/lib/gitbook-blocks.test.mjs`
-Expected: PASS, 15 tests
-
-- [ ] **Step 5: Hand-check the three real steppers and the one columns block**
-
-Run:
-```bash
-node -e '
-import("./scripts/lib/gitbook-blocks.mjs").then(({ convertSteppers, convertColumns }) => {
- const fs = require("fs");
- for (const f of [
- "source/tutorials/ai-agent-creation-overview.md",
- "source/core-concepts/contexts-and-attributes/secret-context.md",
- "source/opendialog-platform/actions/webhook-action/README.md",
- ]) {
- const out = convertColumns(convertSteppers(fs.readFileSync(f, "utf8")));
- console.log("=== " + f + " ===");
- console.log(out.split("\n").filter((l, i, a) =>
- /<Steps>|<\/Steps>|<CardGrid>|<\/CardGrid>|^\d+\. /.test(l)).join("\n"));
- }
-});'
-```
-Expected: `<Steps>`/`</Steps>` and `<CardGrid>`/`</CardGrid>` pairs are balanced, and step
-numbers run 1..n within each block. Read the output — this transform is the fiddliest in the
-set and only 15 steps exist, so it is cheaper to check by eye than to over-test.
-
-- [ ] **Step 6: Commit**
-
-```bash
-git add scripts/lib/gitbook-blocks.mjs scripts/lib/gitbook-blocks.test.mjs
-git commit -m "Convert embed, stepper and columns blocks"
-```
-
----
-
-### Task 7: Link cards
-
-`{% content-ref %}` (51) and GitBook card-tables (8 tables, 41 cards) both emit `<LinkCard>`
-and both need `route-map.json` to turn a filename into a title. The content-ref inner link
-text is a raw filename, not a title — GitBook substitutes the target page's title at render.
-
-**Files:**
-- Create: `scripts/lib/link-cards.mjs`
-- Create: `scripts/lib/link-cards.test.mjs`
-
-**Interfaces:**
-- Consumes: `mapLines` from `./segments.mjs`; `resolveSource` from `./links.mjs`.
-- Produces:
- - `convertContentRefs(text: string, { source, routes, titles }) -> string`
- - `convertCardTables(text: string, { source, routes, titles }) -> string`
- - `countDroppedCovers(text: string) -> number` — how many `data-card-cover` assets this file loses, for the Phase 3 orphan-protection list.
- - Both take `titles: Map<string, { title: string, description?: string }>` keyed by source path, built by `convert.mjs` in a first pass over the corpus.
-
-- [ ] **Step 1: Write the failing test**
-
-Create `scripts/lib/link-cards.test.mjs`:
-
-```js
-import { test } from 'node:test';
-import assert from 'node:assert/strict';
-import { convertCardTables, convertContentRefs, countDroppedCovers } from './link-cards.mjs';
-
-const routes = new Map([
- ['a/text-message.md', { url: '/design/text-message' }],
- ['the-opendialog-model/README.md', { url: '/core-concepts/the-opendialog-model' }],
-]);
-const titles = new Map([
- ['a/text-message.md', { title: 'Text message', description: 'Send plain text.' }],
- ['the-opendialog-model/README.md', { title: 'The OpenDialog model' }],
-]);
-const ctx = { source: 'a/README.md', routes, titles };
-
-test('a content-ref becomes a LinkCard titled from the target page', () => {
- const input = [
- '{% content-ref url="text-message.md" %}',
- '[text-message.md](text-message.md)',
- '{% endcontent-ref %}',
- ].join('\n');
- assert.equal(
- convertContentRefs(input, ctx),
- '<LinkCard title="Text message" description="Send plain text." href="/design/text-message" />'
- );
-});
-
-test('a content-ref to a page with no description omits the attribute', () => {
- const input = [
- '{% content-ref url="../the-opendialog-model/" %}',
- '[the-opendialog-model](../the-opendialog-model/)',
- '{% endcontent-ref %}',
- ].join('\n');
- assert.equal(
- convertContentRefs(input, ctx),
- '<LinkCard title="The OpenDialog model" href="/core-concepts/the-opendialog-model" />'
- );
-});
-
-test('a card-table becomes a CardGrid of LinkCards', () => {
- const input =
- '<table data-card-size="large" data-view="cards" data-full-width="false">' +
- '<thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th>' +
- '<th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody>' +
- '<tr><td><a href="../the-opendialog-model/"><strong>The OpenDialog model</strong></a></td>' +
- '<td>Take a deepdive.</td>' +
- '<td><a href="../the-opendialog-model/">the-opendialog-model</a></td>' +
- '<td><a href="../.gitbook/assets/OD-basicmodel.png">OD-basicmodel.png</a></td></tr>' +
- '</tbody></table>';
- assert.equal(
- convertCardTables(input, ctx),
- [
- '<CardGrid>',
- ' <LinkCard title="The OpenDialog model" description="Take a deepdive." href="/core-concepts/the-opendialog-model" />',
- '</CardGrid>',
- ].join('\n')
- );
-});
-
-test('a card pointing at a broken page keeps the broken href', () => {
- const input =
- '<table data-view="cards"><thead><tr><th></th><th></th>' +
- '<th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody>' +
- '<tr><td><a href="/broken/pages/2lcI5UfFruOL0M8VSp3d"><strong>Core concepts</strong></a></td>' +
- '<td>The core concepts.</td>' +
- '<td><a href="/broken/pages/2lcI5UfFruOL0M8VSp3d">Broken link</a></td></tr>' +
- '</tbody></table>';
- const out = convertCardTables(input, ctx);
- assert.ok(out.includes('href="/broken/pages/2lcI5UfFruOL0M8VSp3d"'), out);
- assert.ok(out.includes('title="Core concepts"'), out);
-});
-
-test('countDroppedCovers counts the cover assets LinkCard cannot show', () => {
- const input =
- '<table data-view="cards"><thead><tr><th></th>' +
- '<th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody>' +
- '<tr><td><a href="x.md"><strong>X</strong></a></td>' +
- '<td><a href="../.gitbook/assets/a.png">a.png</a></td></tr>' +
- '<tr><td><a href="y.md"><strong>Y</strong></a></td>' +
- '<td><a href="../.gitbook/assets/b.png">b.png</a></td></tr>' +
- '</tbody></table>';
- assert.equal(countDroppedCovers(input), 2);
-});
-
-test('an ordinary table is left alone', () => {
- const input = '<table><thead><tr><th>A</th></tr></thead><tbody><tr><td>1</td></tr></tbody></table>';
- assert.equal(convertCardTables(input, ctx), input);
-});
-```
-
-- [ ] **Step 2: Run test to verify it fails**
-
-Run: `node --test scripts/lib/link-cards.test.mjs`
-Expected: FAIL — `Cannot find module './link-cards.mjs'`
-
-- [ ] **Step 3: Write the implementation**
-
-Create `scripts/lib/link-cards.mjs`:
-
-```js
-/**
- * Emits Starlight <LinkCard> markup from the two GitBook constructs that render as cards.
- *
- * Both need route-map.json: a content-ref's inner link text is a raw filename, and GitBook
- * substitutes the target page's title at render time.
- */
-import { mapLines } from './segments.mjs';
-import { resolveSource } from './links.mjs';
-
-/** Escapes a value for use inside a double-quoted JSX attribute. */
-function attribute(value) {
- return value.replace(/&/g, '&').replace(/"/g, '"');
-}
-
-/** Builds one LinkCard element. `description` is omitted when absent. */
-function linkCard({ title, description, href }) {
- const parts = [`title="${attribute(title)}"`];
- if (description) parts.push(`description="${attribute(description)}"`);
- parts.push(`href="${href}"`);
- return `<LinkCard ${parts.join(' ')} />`;
-}
-
-/** Resolves a card href, leaving /broken/pages/ and external URLs as they are. */
-function hrefFor(target, { source, routes }) {
- const resolved = resolveSource(source, target);
- if (resolved === null) return target;
- const route = routes.get(resolved);
- if (!route) throw new Error(`${source}: card target does not resolve: ${target} -> ${resolved}`);
- return route.url;
-}
-
-/** Converts {% content-ref %} blocks to <LinkCard>. */
-export function convertContentRefs(text, ctx) {
- let url = null;
- return mapLines(text, (line) => {
- const open = line.match(/^[ \t]*\{%\s*content-ref\s+url="([^"]+)"\s*%\}[ \t]*$/);
- if (open) {
- url = open[1];
- return [];
- }
- if (url === null) return line;
- if (/^[ \t]*\{%\s*endcontent-ref\s*%\}[ \t]*$/.test(line)) {
- const target = url;
- url = null;
- const resolved = resolveSource(ctx.source, target);
- const meta = resolved ? ctx.titles.get(resolved) : null;
- if (!meta) throw new Error(`${ctx.source}: content-ref has no title for ${target}`);
- return [linkCard({ ...meta, href: hrefFor(target, ctx) })];
- }
- // The inner "[filename](filename)" line is discarded; the title comes from route-map.
- return [];
- });
-}
-
-/** Returns the row elements of a card-table's tbody. */
-function rows(table) {
- const body = table.match(/<tbody>([\s\S]*?)<\/tbody>/);
- return body ? [...body[1].matchAll(/<tr>([\s\S]*?)<\/tr>/g)].map((m) => m[1]) : [];
-}
-
-/** Returns the cell contents of one row. */
-function cells(row) {
- return [...row.matchAll(/<td>([\s\S]*?)<\/td>/g)].map((m) => m[1]);
-}
-
-/** Strips tags and collapses whitespace, for card titles and descriptions. */
-function plainText(html) {
- return html.replace(/<[^>]*>/g, '').replace(/\s+/g, ' ').trim();
-}
-
-const CARD_TABLE = /<table(?=[^>]*\bdata-view="cards")[^>]*>[\s\S]*?<\/table>/g;
-
-/**
- * Converts <table data-view="cards"> to a CardGrid of LinkCards.
- *
- * Attribute order varies — one of the eight reads data-card-size first — so the detector is
- * order independent. data-card-cover images have no LinkCard equivalent and are dropped;
- * countDroppedCovers reports them so Phase 3 does not delete those assets as orphans.
- */
-export function convertCardTables(text, ctx) {
- return text.replace(CARD_TABLE, (table) => {
- const cards = [];
- for (const row of rows(table)) {
- const cell = cells(row);
- const anchors = cell.flatMap((c) => [...c.matchAll(/<a href="([^"]*)"[^>]*>([\s\S]*?)<\/a>/g)]);
- const first = anchors[0];
- if (!first) continue;
- const title = plainText(first[2]);
- const withText = cell.find((c) => !/<a /.test(c) && plainText(c) !== '');
- const targetAnchor =
- anchors.find((a) => !/\.(png|jpe?g|gif|svg|webp)$/i.test(a[1])) ?? first;
- cards.push(
- linkCard({
- title,
- description: withText ? plainText(withText) : undefined,
- href: hrefFor(targetAnchor[1], ctx),
- })
- );
- }
- if (cards.length === 0) return table;
- return ['<CardGrid>', ...cards.map((c) => ` ${c}`), '</CardGrid>'].join('\n');
- });
-}
-
-/** Counts data-card-cover image references lost in conversion, for the Phase 3 handoff. */
-export function countDroppedCovers(text) {
- let total = 0;
- for (const [table] of text.matchAll(CARD_TABLE)) {
- if (!/data-card-cover/.test(table)) continue;
- total += [...table.matchAll(/<a href="[^"]*\.(?:png|jpe?g|gif|svg|webp)"/gi)].length;
- }
- return total;
-}
-```
-
-- [ ] **Step 4: Run test to verify it passes**
-
-Run: `node --test scripts/lib/link-cards.test.mjs`
-Expected: PASS, 6 tests
-
-- [ ] **Step 5: Hand-check all eight real card-tables**
-
-Run:
-```bash
-node -e '
-Promise.all([import("./scripts/lib/link-cards.mjs")]).then(([{ convertCardTables, countDroppedCovers }]) => {
- const fs = require("fs");
- const rm = JSON.parse(fs.readFileSync("route-map.json", "utf8"));
- const routes = new Map(rm.map((r) => [r.source, r]));
- const titles = new Map(rm.map((r) => [r.source, { title: r.title }]));
- let covers = 0, cards = 0;
- for (const r of rm) {
- const text = fs.readFileSync("source/" + r.source, "utf8");
- if (!/data-view="cards"/.test(text)) continue;
- const out = convertCardTables(text, { source: r.source, routes, titles });
- covers += countDroppedCovers(text);
- cards += (out.match(/<LinkCard /g) || []).length;
- console.log("=== " + r.source + " ===");
- console.log(out.split("\n").filter((l) => /CardGrid|LinkCard/.test(l)).join("\n"));
- }
- console.log("\ncards:", cards, " dropped covers:", covers);
-});'
-```
-Expected: `cards: 41` and `dropped covers: 26`. Read the titles and hrefs — 8 tables is
-hand-checkable and this transform parses HTML with regex, which deserves eyes on the output.
-
-- [ ] **Step 6: Commit**
-
-```bash
-git add scripts/lib/link-cards.mjs scripts/lib/link-cards.test.mjs
-git commit -m "Convert content-refs and card-tables to link cards"
-```
-
----
-
-### Task 8: Figures
-
-The highest-value transformation in the migration. Raw HTML `<img>` bypasses `astro:assets`
-entirely, so 541 MB of images would ship unoptimised. 430 `<figure>` blocks each hold exactly
-one `<img>`, plus 6 bare `<img>` outside any figure.
-
-Assets do not exist under `src/` until Phase 3, and Astro treats an unresolvable relative
-image path as a fatal build error. Paths are therefore emitted root-absolute
-(`/.gitbook/assets/…`), which Astro reads as a `public/` path and does not resolve at build
-time. No asset path in the corpus has a subdirectory under `.gitbook/assets/`, so resolution
-is a plain suffix match with no need for the source file's location.
-
-**Files:**
-- Create: `scripts/lib/figures.mjs`
-- Create: `scripts/lib/figures.test.mjs`
-
-**Interfaces:**
-- Consumes: `protectCode` from `./segments.mjs`.
-- Produces:
- - `assetPath(src: string) -> string` — any `…/.gitbook/assets/X` to `/.gitbook/assets/X`; remote URLs unchanged.
- - `convertFigures(text: string) -> string`
- - `rewriteAssetRefs(text: string) -> string` — normalises the 93 pre-existing markdown `![]()` paths the same way.
-
-- [ ] **Step 1: Write the failing test**
-
-Create `scripts/lib/figures.test.mjs`:
-
-```js
-import { test } from 'node:test';
-import assert from 'node:assert/strict';
-import { assetPath, convertFigures, rewriteAssetRefs } from './figures.mjs';
-
-test('assetPath makes a relative asset reference root-absolute', () => {
- assert.equal(assetPath('../../../.gitbook/assets/image (601).png'), '/.gitbook/assets/image (601).png');
- assert.equal(assetPath('.gitbook/assets/Preview Sidebar.jpg'), '/.gitbook/assets/Preview Sidebar.jpg');
-});
-
-test('assetPath leaves a remote URL alone', () => {
- const url = 'https://lh3.googleusercontent.com/abc';
- assert.equal(assetPath(url), url);
-});
-
-test('a figure with a caption becomes an image plus an italic caption', () => {
- assert.equal(
- convertFigures(
- '<figure><img src=".gitbook/assets/Preview Sidebar.jpg" alt="">' +
- '<figcaption><p>Default conversation design view</p></figcaption></figure>'
- ),
- '\n\n*Default conversation design view*'
- );
-});
-
-test('a figure with an empty caption emits only the image', () => {
- assert.equal(
- convertFigures('<figure><img src=".gitbook/assets/a.png" alt=""><figcaption></figcaption></figure>'),
- ''
- );
-});
-
-test('alt text is preserved and never invented', () => {
- assert.equal(
- convertFigures('<figure><img src=".gitbook/assets/a.png" alt="A diagram"><figcaption></figcaption></figure>'),
- ''
- );
-});
-
-test('angle brackets are used only when the path needs them', () => {
- assert.equal(convertFigures('<figure><img src=".gitbook/assets/plain.png" alt=""></figure>'),
- '');
- assert.equal(convertFigures('<figure><img src=".gitbook/assets/a b.png" alt=""></figure>'),
- '');
- assert.equal(convertFigures('<figure><img src=".gitbook/assets/a(1).png" alt=""></figure>'),
- '.png>)');
-});
-
-test('a bare img outside any figure is converted too', () => {
- assert.equal(convertFigures('<img src="../.gitbook/assets/x.png" alt="X">'),
- '');
-});
-
-test('figures inside a fence are left as literal text', () => {
- const input = '```html\n<figure><img src=".gitbook/assets/a.png" alt=""></figure>\n```';
- assert.equal(convertFigures(input), input);
-});
-
-test('rewriteAssetRefs normalises existing markdown image paths', () => {
- assert.equal(
- rewriteAssetRefs(''),
- ''
- );
- assert.equal(rewriteAssetRefs(''), '');
-});
-
-test('rewriteAssetRefs leaves page links alone', () => {
- assert.equal(rewriteAssetRefs('[a](/section/a/b)'), '[a](/section/a/b)');
-});
-```
-
-- [ ] **Step 2: Run test to verify it fails**
-
-Run: `node --test scripts/lib/figures.test.mjs`
-Expected: FAIL — `Cannot find module './figures.mjs'`
-
-- [ ] **Step 3: Write the implementation**
-
-Create `scripts/lib/figures.mjs`:
-
-```js
-/**
- * Converts raw HTML images to markdown image syntax so astro:assets can optimise them.
- *
- * Raw <img> in markdown bypasses Astro's image pipeline entirely, which would ship 541 MB of
- * screenshots unoptimised. This is the highest-value transformation in the migration.
- *
- * Paths are emitted root-absolute. Assets do not reach src/assets/ until Phase 3, and Astro
- * treats an unresolvable *relative* image path as a fatal build error, whereas a leading "/"
- * is read as a public/ path and left alone. assets.mjs rewrites these in Phase 3.
- */
-import { protectCode } from './segments.mjs';
-
-const NEEDS_ANGLE = /[ ()]/;
-
-/** Rewrites any .gitbook/assets reference to its root-absolute form. Remote URLs pass through. */
-export function assetPath(src) {
- if (/^https?:/i.test(src)) return src;
- const match = src.match(/\.gitbook\/assets\/(.*)$/);
- return match ? `/.gitbook/assets/${match[1]}` : src;
-}
-
-/** Renders a markdown image, bracketing the path only when it would break link parsing. */
-function image(alt, src) {
- const path = assetPath(src);
- return ` ? `<${path}>` : path})`;
-}
-
-/** Converts <figure> blocks and bare <img> tags to markdown images. */
-export function convertFigures(text) {
- return protectCode(text, (masked) =>
- masked
- .replace(
- /<figure>\s*<img\s+([^>]*?)>\s*(?:<figcaption>([\s\S]*?)<\/figcaption>)?\s*<\/figure>/g,
- (_, attrs, caption) => {
- const src = attrs.match(/src="([^"]*)"/)?.[1] ?? '';
- const alt = attrs.match(/alt="([^"]*)"/)?.[1] ?? '';
- const text = (caption ?? '').replace(/<[^>]*>/g, '').replace(/\s+/g, ' ').trim();
- return text ? `${image(alt, src)}\n\n*${text}*` : image(alt, src);
- }
- )
- .replace(/<img\s+([^>]*?)\/?>/g, (whole, attrs) => {
- const src = attrs.match(/src="([^"]*)"/)?.[1];
- if (!src) return whole;
- return image(attrs.match(/alt="([^"]*)"/)?.[1] ?? '', src);
- })
- );
-}
-
-/** Normalises the paths of markdown images that were already in the source. */
-export function rewriteAssetRefs(text) {
- return protectCode(text, (masked) =>
- masked.replace(/!\[([^\]]*)\]\((<[^>]*>|[^)]*(?:\([^)]*\)[^)]*)*)\)/g, (whole, alt, dest) => {
- const src = dest.startsWith('<') ? dest.slice(1, -1) : dest;
- if (!/\.gitbook\/assets\//.test(src)) return whole;
- return image(alt, src);
- })
- );
-}
-```
-
-- [ ] **Step 4: Run test to verify it passes**
-
-Run: `node --test scripts/lib/figures.test.mjs`
-Expected: PASS, 10 tests
-
-- [ ] **Step 5: Verify the corpus counts**
-
-Run:
-```bash
-node -e '
-import("./scripts/lib/figures.mjs").then(({ convertFigures }) => {
- const fs = require("fs");
- const rm = JSON.parse(fs.readFileSync("route-map.json", "utf8"));
- let before = 0, after = 0, images = 0;
- for (const r of rm) {
- const text = fs.readFileSync("source/" + r.source, "utf8");
- before += (text.match(/<img/g) || []).length;
- const out = convertFigures(text);
- after += (out.match(/<img/g) || []).length;
- images += (out.match(/!\[/g) || []).length;
- }
- console.log("img before:", before, " img surviving:", after, " markdown images after:", images);
-});'
-```
-Expected: `img before: 436 img surviving: 0 markdown images after: 529` (436 converted plus
-the 93 that were already markdown). A non-zero survivor count means an `<img>` shape the
-regex missed — find it, do not ignore it.
-
-- [ ] **Step 6: Commit**
-
-```bash
-git add scripts/lib/figures.mjs scripts/lib/figures.test.mjs
-git commit -m "Convert HTML figures to markdown images"
-```
-
----
-
-### Task 9: MDX normalisation
-
-Applied only to the 46 files promoted to `.mdx`. In MDX, raw HTML is JSX: unclosed `<br>`
-breaks the parse, `class` is not an attribute, `style` must be an object, and a bare `{` opens
-an expression. 15 lines across 6 files carry `{ attribute }` template syntax in prose.
-
-**Files:**
-- Create: `scripts/lib/mdx.mjs`
-- Create: `scripts/lib/mdx.test.mjs`
-
-**Interfaces:**
-- Consumes: `protectCode` from `./segments.mjs`.
-- Produces: `normaliseForMdx(text: string) -> string`
-
-- [ ] **Step 1: Write the failing test**
-
-Create `scripts/lib/mdx.test.mjs`:
-
-```js
-import { test } from 'node:test';
-import assert from 'node:assert/strict';
-import { normaliseForMdx } from './mdx.mjs';
-
-test('void elements are self-closed', () => {
- assert.equal(normaliseForMdx('a<br>b'), 'a<br />b');
- assert.equal(normaliseForMdx('<hr>'), '<hr />');
-});
-
-test('an already self-closed element is left alone', () => {
- assert.equal(normaliseForMdx('a<br />b'), 'a<br />b');
-});
-
-test('class becomes className', () => {
- assert.equal(normaliseForMdx('<div class="x">y</div>'), '<div className="x">y</div>');
-});
-
-test('a style string becomes a style object', () => {
- assert.equal(
- normaliseForMdx('<mark style="color:purple;">x</mark>'),
- "<mark style={{ color: 'purple' }}>x</mark>"
- );
-});
-
-test('a multi-declaration style becomes a camelCased object', () => {
- assert.equal(
- normaliseForMdx('<span style="background-color: red; font-weight: bold">x</span>'),
- "<span style={{ backgroundColor: 'red', fontWeight: 'bold' }}>x</span>"
- );
-});
-
-test('bare braces in prose are escaped', () => {
- assert.equal(normaliseForMdx('_For example, {llm_response}_'), '_For example, \\{llm_response\\}_');
- assert.equal(normaliseForMdx('Type an opening curly brace { to continue'),
- 'Type an opening curly brace \\{ to continue');
-});
-
-test('braces inside fenced code and inline spans are untouched', () => {
- const input = '```json\n{ "a": 1 }\n```\n`{b}` c';
- assert.equal(normaliseForMdx(input), input);
-});
-
-test('braces in emitted component attributes are not escaped', () => {
- const input = '<LinkCard title="X" href="/y" />\n<Embed url="https://youtu.be/z" />';
- assert.equal(normaliseForMdx(input), input);
-});
-
-test('a style object emitted by this pass is not then brace-escaped', () => {
- assert.equal(
- normaliseForMdx('<mark style="color:purple;">x</mark>'),
- "<mark style={{ color: 'purple' }}>x</mark>"
- );
-});
-```
-
-- [ ] **Step 2: Run test to verify it fails**
-
-Run: `node --test scripts/lib/mdx.test.mjs`
-Expected: FAIL — `Cannot find module './mdx.mjs'`
-
-- [ ] **Step 3: Write the implementation**
-
-Create `scripts/lib/mdx.mjs`:
-
-```js
-/**
- * Normalises markdown for MDX output, where raw HTML is parsed as JSX.
- *
- * Applied only to the 46 files promoted to .mdx. Escaping bare braces is output encoding for
- * the target format, not a prose edit: MDX renders "\{" as a literal "{", which is what
- * GitBook shows today for the 15 lines carrying { attribute } template syntax.
- */
-import { protectCode } from './segments.mjs';
-
-const VOID = ['br', 'hr', 'img', 'input', 'meta', 'link', 'source', 'area', 'col', 'embed'];
-const VOID_TAG = new RegExp(`<(${VOID.join('|')})\\b([^>]*?)(?<!/)>`, 'gi');
-const TAG = /<\/?[A-Za-z][^>]*>/g;
-// Tags are stashed behind a U+0001 delimiter, distinct from the U+0000 protectCode uses, so
-// the two maskings nest without colliding. Verified: the source contains no control
-// characters at all, so neither token can occur naturally.
-const TAG_TOKEN = '\u0001';
-
-/** Converts a CSS declaration list to a JSX style object literal. */
-function styleObject(css) {
- const entries = css
- .split(';')
- .map((d) => d.trim())
- .filter(Boolean)
- .map((d) => {
- const index = d.indexOf(':');
- const property = d.slice(0, index).trim().replace(/-([a-z])/g, (_, c) => c.toUpperCase());
- return `${property}: '${d.slice(index + 1).trim().replace(/'/g, "\\'")}'`;
- });
- return `{{ ${entries.join(', ')} }}`;
-}
-
-export function normaliseForMdx(text) {
- return protectCode(text, (masked) => {
- // Tags are stashed before brace escaping so attributes — including the style objects
- // produced here — are never treated as prose.
- const tags = [];
- const withTags = masked
- .replace(VOID_TAG, (_, name, attrs) => `<${name}${attrs.trimEnd()} />`)
- .replace(TAG, (tag) => {
- const normalised = tag
- .replace(/\bclass=/g, 'className=')
- .replace(/\bstyle="([^"]*)"/g, (_, css) => `style=${styleObject(css)}`);
- return `${TAG_TOKEN}${tags.push(normalised) - 1}${TAG_TOKEN}`;
- });
-
- const escaped = withTags.replace(/[{}]/g, (brace) => `\\${brace}`);
-
- return escaped.replace(
- new RegExp(`${TAG_TOKEN}(\\d+)${TAG_TOKEN}`, 'g'),
- (_, index) => tags[Number(index)]
- );
- });
-}
-```
-
-- [ ] **Step 4: Run test to verify it passes**
-
-Run: `node --test scripts/lib/mdx.test.mjs`
-Expected: PASS, 9 tests
-
-- [ ] **Step 5: Commit**
-
-```bash
-git add scripts/lib/mdx.mjs scripts/lib/mdx.test.mjs
-git commit -m "Normalise markdown for MDX output"
-```
-
----
-
-### Task 10: Embed component
-
-36 Loom and YouTube embeds need a component. The other 2 embeds are ordinary web pages and
-became autolinks in Task 6.
-
-**Files:**
-- Create: `src/components/Embed.astro`
-
-**Interfaces:**
-- Consumes: nothing.
-- Produces: `<Embed url="…" title="…" />`, imported by generated `.mdx` files from `~/components/Embed.astro`.
-
-- [ ] **Step 1: Write the component**
-
-Create `src/components/Embed.astro`:
-
-```astro
----
-/**
- * Renders a Loom or YouTube video in a lazily-loaded 16:9 iframe.
- *
- * GitBook's {% embed %} shows a caption under the video; `title` reproduces that and doubles
- * as the iframe's accessible name.
- */
-interface Props {
- url: string;
- title?: string;
-}
-
-const { url, title } = Astro.props;
-
-/** Maps a share URL to its embeddable form. */
-function embedSrc(raw: string): string | null {
- const parsed = new URL(raw);
- const host = parsed.hostname.replace(/^www\./, '');
- if (host === 'youtu.be') return `https://www.youtube-nocookie.com/embed/${parsed.pathname.slice(1)}`;
- if (host === 'youtube.com') {
- const id = parsed.searchParams.get('v');
- return id ? `https://www.youtube-nocookie.com/embed/${id}` : null;
- }
- if (host === 'loom.com') return raw.replace('/share/', '/embed/').split('?')[0];
- return null;
-}
-
-const src = embedSrc(url);
----
-
-{
- src ? (
- <figure class="od-embed">
- <div class="od-embed-frame">
- <iframe
- src={src}
- title={title ?? 'Embedded video'}
- loading="lazy"
- allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
- allowfullscreen
- />
- </div>
- {title && <figcaption>{title}</figcaption>}
- </figure>
- ) : (
- <p><a href={url}>{title ?? url}</a></p>
- )
-}
-
-<style>
- .od-embed {
- margin: 1.5rem 0;
- }
- .od-embed-frame {
- aspect-ratio: 16 / 9;
- border-radius: 0.5rem;
- overflow: hidden;
- border: 1px solid var(--sl-color-gray-5);
- }
- .od-embed-frame iframe {
- width: 100%;
- height: 100%;
- border: 0;
- display: block;
- }
- .od-embed figcaption {
- margin-top: 0.5rem;
- font-size: var(--sl-text-sm);
- color: var(--sl-color-gray-3);
- }
-</style>
-```
-
-- [ ] **Step 2: Verify it renders**
-
-Create a scratch page to prove the component builds before 46 files depend on it:
-
-```bash
-mkdir -p src/content/docs/_embedcheck
-cat > src/content/docs/_embedcheck/index.mdx <<'PAGE'
----
-title: Embed check
----
-
-import Embed from '~/components/Embed.astro';
-
-<Embed url="https://youtu.be/RhUc_mgkNl8" title="A caption" />
-<Embed url="https://www.loom.com/share/abc123?t=1" />
-PAGE
-npx astro build 2>&1 | tail -5
-```
-Expected: build succeeds. If `~/components/…` does not resolve, check `tsconfig.json` for the
-path alias and use a relative import in the generated files instead — note whichever form
-works, because Task 11 must emit the same one.
-
-- [ ] **Step 3: Confirm the rendered markup**
-
-Run: `grep -o 'youtube-nocookie[^"]*' dist/_embedcheck/index.html`
-Expected: `youtube-nocookie.com/embed/RhUc_mgkNl8`
-
-- [ ] **Step 4: Remove the scratch page**
-
-```bash
-rm -rf src/content/docs/_embedcheck
-```
-
-- [ ] **Step 5: Commit**
-
-```bash
-git add src/components/Embed.astro
-git commit -m "Add the video embed component"
-```
-
----
-
-### Task 11: The conversion script
-
-Orchestrates the per-file pipeline and asserts the corpus invariants. This is where the
-`.md` / `.mdx` decision and the component imports are made.
-
-**Files:**
-- Create: `scripts/convert.mjs`
-
-**Interfaces:**
-- Consumes: every `scripts/lib/` module, and `route-map.json`.
-- Produces: `src/content/docs/**` and a summary report on stdout. Exits non-zero on any failed invariant.
-
-- [ ] **Step 1: Write the script**
-
-Create `scripts/convert.mjs`:
-
-```js
-/**
- * Converts source/ (a pristine GitBook export) into Starlight content under src/content/docs/.
- *
- * Idempotent: src/content/docs/ is cleared before writing, output order follows
- * route-map.json, and nothing depends on timestamps or filesystem ordering. Re-runnable
- * against a fresh GitBook sync right up to cutover day.
- *
- * Verifies its own output against the counts measured from the source corpus and exits
- * non-zero on any divergence, in the same spirit as routes.mjs checking itself against the
- * live sitemap snapshot.
- */
-import { mkdirSync, readFileSync, rmSync, writeFileSync } from 'node:fs';
-import { dirname, resolve } from 'node:path';
-import { fileURLToPath } from 'node:url';
-
-import { emitFrontmatter, parseFrontmatter, takeTitle } from './lib/frontmatter.mjs';
-import { convertFigures, rewriteAssetRefs } from './lib/figures.mjs';
-import {
- convertCode,
- convertColumns,
- convertEmbeds,
- convertFile,
- convertHints,
- convertSteppers,
- stripEntities,
-} from './lib/gitbook-blocks.mjs';
-import { convertCardTables, convertContentRefs, countDroppedCovers } from './lib/link-cards.mjs';
-import { rewriteLinks } from './lib/links.mjs';
-import { normaliseForMdx } from './lib/mdx.mjs';
-import { mapLines } from './lib/segments.mjs';
-
-const root = resolve(dirname(fileURLToPath(import.meta.url)), '..');
-const OUT = `${root}/src/content/docs`;
-
-const routeMap = JSON.parse(readFileSync(`${root}/route-map.json`, 'utf8'));
-const routes = new Map(routeMap.map((r) => [r.source, r]));
-
-/** Counts occurrences of `pattern` in prose only, ignoring anything inside a fenced block. */
-function countInProse(text, pattern) {
- const prose = [];
- mapLines(text, (line) => {
- prose.push(line);
- return line;
- });
- return (prose.join('\n').match(pattern) || []).length;
-}
-
-/** First pass: every page's title and description, so cards can be titled from their target. */
-const titles = new Map(
- routeMap.map((r) => {
- const { data, body } = parseFrontmatter(readFileSync(`${root}/source/${r.source}`, 'utf8'));
- const { title } = takeTitle(body);
- if (!title) throw new Error(`${r.source}: no H1 found`);
- return [r.source, { title, description: data.description }];
- })
-);
-
-const stats = {
- files: 0,
- mdx: 0,
- asides: 0,
- contentRefCards: 0,
- cardTableCards: 0,
- embeds: 0,
- steps: 0,
- cardGrids: 0,
- images: 0,
- droppedCovers: 0,
- survivingBlocks: 0,
- survivingEntities: 0,
- survivingImgTags: 0,
-};
-
-const COMPONENTS = [
- ['<LinkCard', 'LinkCard'],
- ['<CardGrid', 'CardGrid'],
- ['<Steps>', 'Steps'],
-];
-
-rmSync(OUT, { recursive: true, force: true });
-
-for (const route of routeMap) {
- const raw = readFileSync(`${root}/source/${route.source}`, 'utf8');
- const { data, body } = parseFrontmatter(raw);
- const meta = titles.get(route.source);
- const ctx = { source: route.source, routes, titles };
-
- stats.droppedCovers += countDroppedCovers(body);
-
- let text = takeTitle(body).body;
- text = convertCode(text);
- text = convertHints(text);
- text = convertFile(text);
- text = convertContentRefs(text, ctx);
- text = convertCardTables(text, ctx);
- text = convertEmbeds(text);
- text = convertSteppers(text);
- text = convertColumns(text);
- text = convertFigures(text);
- text = rewriteAssetRefs(text);
- text = stripEntities(text);
- text = rewriteLinks(text, ctx);
-
- const used = COMPONENTS.filter(([marker]) => text.includes(marker)).map(([, name]) => name);
- const hasEmbed = text.includes('<Embed ');
- const isMdx = used.length > 0 || hasEmbed;
-
- if (isMdx) {
- text = normaliseForMdx(text);
- const imports = [];
- if (used.length) imports.push(`import { ${[...new Set(used)].sort().join(', ')} } from '@astrojs/starlight/components';`);
- if (hasEmbed) imports.push("import Embed from '~/components/Embed.astro';");
- text = `\n${imports.join('\n')}\n${text}`;
- }
-
- const target = `${OUT}/${route.target}${isMdx ? 'x' : ''}`;
- const output = `${emitFrontmatter({ title: meta.title, description: meta.description })}${text.replace(/^\n+/, '\n')}`;
- mkdirSync(dirname(target), { recursive: true });
- writeFileSync(target, output.replace(/\s*$/, '\n'));
-
- stats.files++;
- if (isMdx) stats.mdx++;
- stats.asides += (output.match(/^:::(note|tip|caution|danger)/gm) || []).length;
- stats.embeds += (output.match(/<Embed /g) || []).length;
- stats.cardGrids += (output.match(/<CardGrid>/g) || []).length;
- stats.steps += (output.match(/^\d+\. /gm) || []).length;
- stats.images += (output.match(/!\[/g) || []).length;
- // In .mdx a surviving block reads "\{% … %\}", so the escaped form still matches "{%".
- stats.survivingBlocks += countInProse(output, /\{%/g);
- stats.survivingEntities += countInProse(output, / /g);
- stats.survivingImgTags += countInProse(output, /<img/g);
- if (/hidden:/.test(output.split('---')[1] ?? '')) throw new Error(`${route.source}: hidden survived`);
-}
-
-const EXPECTED = {
- files: 204,
- mdx: 46,
- asides: 258,
- embeds: 36,
- cardGrids: 9,
- images: 529,
- droppedCovers: 26,
- survivingBlocks: 0,
- survivingEntities: 0,
- survivingImgTags: 0,
-};
-
-let failed = false;
-for (const [key, expected] of Object.entries(EXPECTED)) {
- const actual = stats[key];
- const ok = actual === expected;
- if (!ok) failed = true;
- console.log(`${ok ? 'ok ' : 'FAIL'} ${key.padEnd(20)} ${actual}${ok ? '' : ` (expected ${expected})`}`);
-}
-// Informational, not asserted: the corpus contains ordinary numbered lists too, so a
-// "^\d+\. " count cannot isolate the 15 stepper steps. Task 6 checks those by eye.
-console.log(` ${'ordered list items'.padEnd(20)} ${stats.steps}`);
-console.log(`\nwrote ${stats.files} pages to src/content/docs`);
-
-if (failed) {
- console.error('\nA count diverged. The script is wrong — do not adjust the expectation.');
- process.exit(1);
-}
-```
-
-- [ ] **Step 2: Run it**
-
-Run: `node scripts/convert.mjs`
-Expected: every line prefixed `ok`, then `wrote 204 pages to src/content/docs`.
-
-If a count diverges, fix the responsible `lib/` module and its unit test — never the
-expectation, and never the generated file. `survivingBlocks`, `survivingEntities` and
-`survivingImgTags` must all be 0.
-
-- [ ] **Step 3: Verify idempotency**
-
-```bash
-node scripts/convert.mjs > /dev/null
-find src/content/docs -type f | sort | xargs shasum > /tmp/run1.txt
-node scripts/convert.mjs > /dev/null
-find src/content/docs -type f | sort | xargs shasum > /tmp/run2.txt
-diff /tmp/run1.txt /tmp/run2.txt && echo "IDENTICAL"
-```
-Expected: `IDENTICAL`
-
-- [ ] **Step 4: Verify the build**
-
-Run: `npx astro build 2>&1 | tail -20`
-Expected: succeeds, reporting 204 page(s) built (plus Starlight's 404). Any MDX parse failure
-names a file — fix the responsible `lib/` module, re-run `convert.mjs`, rebuild.
-
-- [ ] **Step 5: Commit**
-
-```bash
-git add scripts/convert.mjs src/content/docs
-git commit -m "Convert the GitBook corpus to Starlight content"
-```
-
----
-
-### Task 12: Sidebar generation
-
-`SUMMARY.md` nests five levels deep across six sections. Starlight groups are not linkable —
-`SidebarGroupSchema` in `node_modules/@astrojs/starlight/schemas/sidebar.ts` has no `link`
-field — so each of the 41 entries that is both a page and a parent becomes a group whose first
-item is the parent page itself, carrying the same label.
-
-**Files:**
-- Create: `scripts/sidebar.mjs`
-- Create: `scripts/lib/sidebar-tree.mjs`
-- Create: `scripts/lib/sidebar-tree.test.mjs`
-- Modify: `astro.config.mjs` (replace the Phase 1 placeholder sidebar)
-
-**Interfaces:**
-- Consumes: `parseSummary` from `./lib/summary.mjs`; `route-map.json` for slugs.
-- Produces:
- - `buildSidebar(entries, slugFor) -> Array<{ label: string, items: Array<object> }>` where `slugFor(source: string) -> string` maps a source path to a Starlight slug.
-
-- [ ] **Step 1: Write the failing test**
-
-Create `scripts/lib/sidebar-tree.test.mjs`:
-
-```js
-import { test } from 'node:test';
-import assert from 'node:assert/strict';
-import { buildSidebar } from './sidebar-tree.mjs';
-
-const slugFor = (source) => source.replace(/(^|\/)README\.md$/, '').replace(/\.md$/, '');
-const section = { label: 'CORE CONCEPTS', slug: 'core-concepts' };
-
-test('a section becomes a top-level group', () => {
- const entries = [{ depth: 0, label: 'Model', source: 'model.md', section }];
- assert.deepEqual(buildSidebar(entries, slugFor), [
- { label: 'CORE CONCEPTS', items: [{ label: 'Model', slug: 'model' }] },
- ]);
-});
-
-test('a parent page becomes a group whose first item is the page itself', () => {
- const entries = [
- { depth: 0, label: 'Message design', source: 'design/README.md', section },
- { depth: 2, label: 'Text message', source: 'design/text.md', section },
- ];
- assert.deepEqual(buildSidebar(entries, slugFor), [
- {
- label: 'CORE CONCEPTS',
- items: [
- {
- label: 'Message design',
- items: [
- { label: 'Message design', slug: 'design' },
- { label: 'Text message', slug: 'design/text' },
- ],
- },
- ],
- },
- ]);
-});
-
-test('nesting continues to arbitrary depth', () => {
- const entries = [
- { depth: 0, label: 'A', source: 'a/README.md', section },
- { depth: 2, label: 'B', source: 'a/b/README.md', section },
- { depth: 4, label: 'C', source: 'a/b/c.md', section },
- ];
- const [group] = buildSidebar(entries, slugFor);
- assert.deepEqual(group.items[0].items[1], {
- label: 'B',
- items: [
- { label: 'B', slug: 'a/b' },
- { label: 'C', slug: 'a/b/c' },
- ],
- });
-});
-
-test('the root README becomes the empty slug', () => {
- const entries = [{ depth: 0, label: 'Introduction', source: 'README.md', section }];
- assert.deepEqual(buildSidebar(entries, slugFor)[0].items, [{ label: 'Introduction', slug: '' }]);
-});
-
-test('sections keep SUMMARY.md order', () => {
- const other = { label: 'RELEASE NOTES', slug: 'release-notes' };
- const entries = [
- { depth: 0, label: 'A', source: 'a.md', section },
- { depth: 0, label: 'R', source: 'r.md', section: other },
- ];
- assert.deepEqual(buildSidebar(entries, slugFor).map((g) => g.label), ['CORE CONCEPTS', 'RELEASE NOTES']);
-});
-```
-
-- [ ] **Step 2: Run test to verify it fails**
-
-Run: `node --test scripts/lib/sidebar-tree.test.mjs`
-Expected: FAIL — `Cannot find module './sidebar-tree.mjs'`
-
-- [ ] **Step 3: Write the tree builder**
-
-Create `scripts/lib/sidebar-tree.mjs`:
-
-```js
-/**
- * Turns the flat SUMMARY.md entry list into Starlight's nested sidebar shape.
- *
- * Starlight groups are not linkable — SidebarGroupSchema has no `link` field — so an entry
- * that is both a page and a parent becomes a group whose first item is the page itself,
- * carrying the same label. That keeps every SUMMARY.md label exact, keeps all 204 pages
- * reachable from the nav, and invents no text. A clickable group needs a Sidebar component
- * override, which is Phase 4 chrome work.
- */
-
-/** Builds the ordered section groups for Starlight's `sidebar` option. */
-export function buildSidebar(entries, slugFor) {
- const groups = [];
- const stack = [];
-
- // Build a plain tree first. Every node carries a `children` array, always present so there
- // is no lazy-initialisation case to get wrong; the shaping pass below decides which nodes
- // actually became parents.
- for (const entry of entries) {
- if (!groups.length || groups.at(-1).label !== entry.section.label) {
- groups.push({ label: entry.section.label, children: [] });
- stack.length = 0;
- }
- while (stack.length && stack.at(-1).depth >= entry.depth) stack.pop();
-
- const node = { label: entry.label, slug: slugFor(entry.source), children: [] };
- const siblings = stack.length ? stack.at(-1).node.children : groups.at(-1).children;
- siblings.push(node);
- stack.push({ depth: entry.depth, node });
- }
-
- // A node with children becomes a group. Starlight cannot link a group, so the page keeps
- // its own entry as that group's first item, carrying the same label.
- const shape = (node) =>
- node.children.length
- ? {
- label: node.label,
- items: [{ label: node.label, slug: node.slug }, ...node.children.map(shape)],
- }
- : { label: node.label, slug: node.slug };
-
- return groups.map((group) => ({ label: group.label, items: group.children.map(shape) }));
-}
-```
-
-- [ ] **Step 4: Run test to verify it passes**
-
-Run: `node --test scripts/lib/sidebar-tree.test.mjs`
-Expected: PASS, 5 tests
-
-- [ ] **Step 5: Write the generator**
-
-Create `scripts/sidebar.mjs`:
-
-```js
-/**
- * Generates the Starlight sidebar from source/SUMMARY.md.
- *
- * Writes a separate module rather than splicing into astro.config.mjs, so generated data and
- * hand-written configuration never share a file or a diff.
- */
-import { readFileSync, writeFileSync } from 'node:fs';
-import { dirname, resolve } from 'node:path';
-import { fileURLToPath } from 'node:url';
-
-import { parseSummary } from './lib/summary.mjs';
-import { buildSidebar } from './lib/sidebar-tree.mjs';
-
-const root = resolve(dirname(fileURLToPath(import.meta.url)), '..');
-const OUT = `${root}/src/sidebar.generated.mjs`;
-
-const routes = new Map(
- JSON.parse(readFileSync(`${root}/route-map.json`, 'utf8')).map((r) => [r.source, r])
-);
-
-/** A page's Starlight slug is its live URL without the leading slash. */
-const slugFor = (source) => {
- const route = routes.get(source);
- if (!route) throw new Error(`no route for ${source}`);
- return route.url === '/' ? '' : route.url.slice(1);
-};
-
-const entries = parseSummary(readFileSync(`${root}/source/SUMMARY.md`, 'utf8'));
-const sidebar = buildSidebar(entries, slugFor);
-
-const count = (items) =>
- items.reduce((total, item) => total + (item.items ? count(item.items) : 1), 0);
-
-writeFileSync(
- OUT,
- '// Generated by scripts/sidebar.mjs from source/SUMMARY.md. Do not edit.\n' +
- `export default ${JSON.stringify(sidebar, null, 2)};\n`
-);
-
-console.log(`sections : ${sidebar.length}`);
-console.log(`nav entries : ${count(sidebar)}`);
-console.log(`wrote ${OUT}`);
-
-if (entries.length !== 204) {
- console.error(`expected 204 SUMMARY.md entries, parsed ${entries.length}`);
- process.exit(1);
-}
-```
-
-- [ ] **Step 6: Run it**
-
-Run: `node scripts/sidebar.mjs`
-Expected: `sections : 6`, and `nav entries : 245` — 204 pages plus the 41 parent pages that
-appear a second time as their group's first item. Confirm the arithmetic holds: 204 + 41 = 245.
-
-- [ ] **Step 7: Wire it into the config**
-
-In `astro.config.mjs`, add the import at the top:
-
-```js
-import sidebar from './src/sidebar.generated.mjs';
-```
-
-and replace the whole `sidebar: [ … ]` placeholder array (lines 27–45, including the two
-Phase 1 comment lines above it) with:
-
-```js
- sidebar,
-```
-
-- [ ] **Step 8: Build and check the nav**
-
-Run: `npx astro build 2>&1 | tail -5`
-Expected: succeeds.
-
-Run: `npx astro dev` and open a page. Confirm the six sections appear in `SUMMARY.md` order,
-that a parent such as "Message design" shows as an expandable group whose first item repeats
-the label, and that the four `[Deprecated]` / `[Legacy]` entries are present — they are the
-ones a careless label regex drops.
-
-- [ ] **Step 9: Commit**
-
-```bash
-git add scripts/sidebar.mjs scripts/lib/sidebar-tree.mjs scripts/lib/sidebar-tree.test.mjs src/sidebar.generated.mjs astro.config.mjs
-git commit -m "Generate the sidebar from SUMMARY.md"
-```
-
----
-
-### Task 13: Phase gate
-
-Prove the gate criteria, record what was found, and stop.
-
-**Files:**
-- Modify: `MIGRATION-NOTES.md` (append only)
-
-- [ ] **Step 1: Run the full test suite**
-
-Run: `npm test`
-Expected: all tests pass across all `scripts/lib/*.test.mjs` files.
-
-- [ ] **Step 2: Re-run the full pipeline from scratch**
-
-```bash
-node scripts/routes.mjs && node scripts/convert.mjs && node scripts/sidebar.mjs
-```
-Expected: route parity OK, every convert invariant `ok`, 204 pages, 6 sections.
-
-- [ ] **Step 3: Prove the gate criteria**
-
-```bash
-npx astro build 2>&1 | tail -5
-echo "--- pages built ---"
-find dist -name index.html | wc -l
-echo "--- {% outside code fences (must be 0) ---"
-node -e '
-import("./scripts/lib/segments.mjs").then(({ mapLines }) => {
- const fs = require("fs"), path = require("path");
- let hits = 0;
- (function walk(d) {
- for (const e of fs.readdirSync(d, { withFileTypes: true })) {
- const p = path.join(d, e.name);
- if (e.isDirectory()) walk(p);
- else {
- mapLines(fs.readFileSync(p, "utf8"), (line) => {
- if (line.includes("{%")) { hits++; console.log(p + ": " + line.trim()); }
- return line;
- });
- }
- }
- })("src/content/docs");
- console.log("surviving GitBook blocks:", hits);
-});'
-```
-Expected: build succeeds; 205 `index.html` files (204 pages plus the 404 page — confirm the
-extra one is the 404 and not a stray); surviving GitBook blocks 0.
-
-- [ ] **Step 4: Confirm no placeholder pages survived**
-
-Run: `git status --short src/content/docs | head`
-Expected: the four Phase 1 hand-written placeholders recorded in `MIGRATION-NOTES.md`
-(`index.md`, `getting-started-1/getting-ready/index.md`,
-`core-concepts/the-opendialog-model/index.mdx`, `tutorials/ai-agent-creation-overview/index.mdx`)
-are replaced by generated files, not left alongside them.
-
-- [ ] **Step 5: Append to `MIGRATION-NOTES.md`**
-
-Append a dated section covering, at minimum:
-
-- The eight corrections to the brief from the design spec, with the measured counts.
-- The `mapLines` / `protectCode` refinement and why per-segment mapping was abandoned.
-- The final invariant table as it actually ran.
-- Everything from the spec's "Logged, not fixed" list: the "laaunched" typo; the 12
- `/broken/pages/` placeholders; the source link with an extra `../`; 391 images with empty
- `alt`; `{% code fullWidth="false" %}` dropped; the 3 pages where H1 and nav label differ.
-- **The Phase 3 handoff, stated explicitly:** every `/.gitbook/assets/…` placeholder must be
- rewritten and survivors asserted to zero, and the 26 card-cover assets have no surviving
- reference after conversion and must be excluded from orphan deletion.
-- The Phase 4 handoff: linkable sidebar groups, `<figure>` semantics, card-cover images.
-
-- [ ] **Step 6: Commit and open the PR**
-
-```bash
-git add MIGRATION-NOTES.md
-git commit -m "Record Phase 2 conversion findings"
-git push -u origin phase-2/conversion-script
-gh pr create --title "Phase 2: conversion script" --body "$(cat <<'BODY'
-Converts all 204 GitBook pages to Starlight content and generates the sidebar from SUMMARY.md.
-
-Gate: 204 pages converted, `astro build` succeeds, zero `{%` outside code fences, re-run
-byte-identical.
-
-Design spec: `docs/superpowers/specs/2026-07-29-phase-2-conversion-design.md`
-Findings and handoffs: `MIGRATION-NOTES.md`
-
-Images 404 on the preview until Phase 3 — paths are root-absolute placeholders by design, so
-the build passes without committing 541 MB of assets into git history.
-
-🤖 Generated with [Claude Code](https://claude.com/claude-code)
-BODY
-)"
-```
-
-- [ ] **Step 7: Stop**
-
-Report to Pat and wait. Do not begin Phase 3 asset work. `ffmpeg` is still not installed and
-is needed for the 28 MB GIF that breaks Cloudflare's 25 MiB file cap.
diff --git a/docs/superpowers/specs/2026-07-29-phase-2-conversion-design.md b/docs/superpowers/specs/2026-07-29-phase-2-conversion-design.md
deleted file mode 100644
index 29ed80a..0000000
--- a/docs/superpowers/specs/2026-07-29-phase-2-conversion-design.md
+++ /dev/null
@@ -1,505 +0,0 @@
-# Phase 2 — conversion script: design
-
-Status: approved for planning, 29 Jul 2026
-Supersedes nothing. Corrections to `MIGRATION-BRIEF.md` are listed in full below and are
-also destined for `MIGRATION-NOTES.md`.
-
----
-
-## Goal
-
-`node scripts/convert.mjs` turns the 204 published GitBook pages in `source/` into valid
-Starlight content under `src/content/docs/`, and `node scripts/sidebar.mjs` turns
-`source/SUMMARY.md` into the site's ~204-entry sidebar.
-
-**Gate:** all 204 pages converted, `astro build` succeeds, zero `{%` sequences outside code
-fences, a second run byte-identical to the first. Stop and report; do not chain into Phase 3.
-
-## Non-goals
-
-- Assets. Images emit as root-absolute placeholders; `assets.mjs` rewrites them in Phase 3.
-- Prose edits of any kind, including the known typo and the 12 pre-existing broken links.
-- Visual refinement. Card, aside and sidebar presentation are judged in Phase 4.
-- Route derivation. `scripts/routes.mjs` already does this and is unchanged in behaviour.
-
----
-
-## Measured corrections to the brief
-
-Each of these was verified against `source/` during design. Where a count differs from the
-brief, the number here is the measured one.
-
-### 1. `hidden: true` must be dropped, not honoured
-
-`luis-interpreter.md` and `qna-interpreter.md` carry `hidden: true` in GitBook frontmatter.
-Both appear in `SUMMARY.md` and both are live in `reference/sitemap-pages.xml`. Honouring
-the key would silently remove two live URLs and fail route parity. The converter drops it.
-
-### 2. ` ` is not uniformly "replace with a space"
-
-1,203 occurrences, of which **1,192 sit at end of line** and 84 of those follow an existing
-space. Converting those to a literal space yields `… \n`, which markdown renders as a `<br>`
-that does not exist on the live site.
-
-**Rule:** strip ` ` when it is the last thing on a line; replace it with a single space
-elsewhere (11 cases). This preserves live rendering exactly.
-
-### 3. `{% include %}` is never used
-
-The brief says `.gitbook/includes/navigate-to-the-next-level-….md` is "transcluded somewhere"
-and asks for it to be inlined. There are **zero** `{% include %}` directives in the corpus.
-The file is dead. No work.
-
-### 4. Every page has an H1
-
-All 204. The brief's "or the `SUMMARY.md` link text if no H1" fallback is never taken. It is
-still implemented, but as an assertion that fails loudly rather than a silent default.
-
-### 5. Directory-form links exist and the `.md` link count is wrong
-
-The brief lists "499 relative `.md` links to rewrite". That figure includes `SUMMARY.md`'s own
-204 nav entries. Measured, excluding `SUMMARY.md`:
-
-| Link form | Count |
-|---|---|
-| `](path/to/page.md)` | 311 |
-| `](path/to/dir/)` — resolves to that directory's `README.md` | **70** |
-| **Total in-prose page links to rewrite** | **381** |
-| `.gitbook/assets/…` references | 535 |
-| External (`http`, `mailto`) | 189 |
-| `/broken/pages/…` | 12 |
-| Bare `#anchor` | 13 |
-
-The 70 directory-form links appear nowhere in the brief. Left unhandled they 404.
-
-### 6. One genuinely broken relative link in the source
-
-`core-concepts/contexts-and-attributes/secret-context.md` links to
-`../../../opendialog-platform/actions/webhook-action/`. From a file two directories deep,
-three `../` escapes the repo root. The intended target is
-`opendialog-platform/actions/webhook-action/README.md`.
-
-**Rule:** clamp `..` traversal at the source root before resolving. This is what GitBook
-itself does, it is a general rule rather than a special case, and it is an output-encoding
-decision, not a prose edit. Any link that resolves only after clamping is logged.
-
-### 7. Card-table attribute order varies
-
-`<table data-view="cards">` is not a literal. One of the eight reads
-`<table data-card-size="large" data-view="cards" data-full-width="false">`. The detector must
-be attribute-order independent. All eight are single-line HTML.
-
-### 8. `.mdx` promotion is 46 files, not 11
-
-`MIGRATION-NOTES.md` records 11 `.mdx` candidates, measured before `<Embed>` and the
-card-table decision. Actual drivers:
-
-| Driver | Files |
-|---|---|
-| `{% embed %}` → `<Embed>` | 30 |
-| `{% content-ref %}` → `<LinkCard>` | 9 |
-| `<table data-view="cards">` → `<CardGrid>` | 8 |
-| `{% stepper %}` → `<Steps>` | 2 |
-| `{% columns %}` → `<CardGrid>` | 1 |
-| **Union** | **46 of 204** |
-
-The embed driver is 30 files, not the 31 that contain an embed:
-`opendialog-platform/conversation-designer/designing-accessible-chatbots.md` embeds only the
-WebAIM contrast checker, which renders as a plain link, so it stays `.md`.
-
-Brace risk re-measured across all 46 after GitBook block syntax is consumed: **6 files, 15
-lines**, all `{ attribute }` template syntax in prose. All are handled by the general escaping
-rule in §"MDX normalisation". The notes' "one line in the whole set" figure is superseded.
-
----
-
-## Architecture
-
-Small, independently testable units under `scripts/lib/`, with thin orchestrators on top.
-Every transform is a pure `string -> string` (or `string -> {body, meta}`) function with no
-filesystem access, so each is unit-testable against inline fixtures.
-
-```
-scripts/
-├── convert.mjs orchestrate, assert corpus invariants, report
-├── sidebar.mjs SUMMARY.md -> src/sidebar.generated.mjs
-├── routes.mjs exists; refactored to import lib/summary.mjs
-└── lib/
- ├── summary.mjs SUMMARY.md parser [shared: routes + sidebar]
- ├── segments.mjs code/prose segmentation [foundation]
- ├── frontmatter.mjs parse in, emit out
- ├── gitbook-blocks.mjs {% … %} -> asides and components
- ├── figures.mjs <figure>/<img> -> ![]()
- ├── card-tables.mjs <table data-view="cards"> -> <CardGrid>
- ├── links.mjs relative page links -> route URLs
- └── mdx.mjs JSX normalisation and brace escaping
-```
-
-`routes.mjs` currently carries its own `SUMMARY.md` parser. `sidebar.mjs` needs the identical
-parse — including the escaped-bracket trap that silently drops four entries — so the parser
-moves to `lib/summary.mjs` and both import it. One parser, one place to get it wrong.
-
-### `lib/segments.mjs` is the load-bearing piece
-
-Fenced code blocks and inline code spans must be immune to **every** transformation. This is
-the single largest source of silent corruption: the corpus contains `{first_name}` inside JSON
-fences, `{% code %}` blocks wrapping fences, and 1,317 asset filenames containing parentheses.
-
-```js
-splitSegments(text) -> [{ kind: 'code' | 'prose', text }]
-mapProse(text, fn) -> string // fn applied to prose segments only
-```
-
-Everything downstream is expressed as `mapProse`. `{% code %}` is the sole exception — it
-brackets a fence and is handled before segmentation, by rewriting the fence's info string.
-
-### Link and image extraction must not use a naive regex
-
-`\]\(([^)]+)\)` truncates at the first `)` inside `image (149).png` and silently mangles
-1,317 filenames. The extractor handles both the angle-bracket form
-`.png>)` and balanced parentheses in bare paths. This is proven — the same
-naive regex produced a false "unresolved link" report during design.
-
----
-
-## Per-file pipeline
-
-1. Parse frontmatter. Keep `description`. **Drop `hidden`.** Drop everything else.
-2. `{% code %}` → fence info string (must precede segmentation).
-3. Segment into code and prose. All remaining steps run on prose only:
- 1. GitBook block syntax → asides and components
- 2. `<figure>` / bare `<img>` → markdown images
- 3. card-tables → `<CardGrid>`
- 4. ` ` handling
- 5. page-link rewriting
-4. Extract the first H1 → frontmatter `title`; remove it from the body.
-5. Choose `.md` or `.mdx`: `.mdx` if and only if a component was emitted.
-6. If `.mdx`: JSX-normalise and escape bare braces.
-7. Write to the `target` path given by `route-map.json`.
-
----
-
-## Transformation catalogue
-
-### Asides — 258
-
-| Source | Output |
-|---|---|
-| `{% hint style="info" %}` | `:::note` |
-| `{% hint style="success" %}` | `:::tip` |
-| `{% hint style="warning" %}` | `:::caution` |
-| `{% hint style="danger" %}` | `:::danger` |
-| `{% endhint %}` | `:::` |
-
-Works in `.md`; no component, no `.mdx` promotion.
-
-### `{% content-ref %}` → `<LinkCard>` — 51
-
-```
-{% content-ref url="chat-management-conversation.md" %}
-[chat-management-conversation.md](chat-management-conversation.md)
-{% endcontent-ref %}
-```
-becomes
-```jsx
-<LinkCard title="Chat management conversation" description="…" href="/…/chat-management-conversation" />
-```
-
-The inner link text is a raw filename, not a title — GitBook substitutes the target page's
-title at render. Title and `href` come from `route-map.json`; `description` from the target's
-frontmatter `description` where it has one, matching GitBook's card. The `url` attribute and
-the inner link target agree on all 51, so either may be used; the `url` attribute is
-authoritative.
-
-### `{% embed %}` → `<Embed>` — 38
-
-Two forms, 19 each:
-
-```
-{% embed url="U" %} -> <Embed url="U" />
-
-{% embed url="U" %}
-Caption text
-{% endembed %} -> <Embed url="U" title="Caption text" />
-```
-
-Providers: 19 Loom, 17 YouTube, 2 other (`fetchify.com`, `webaim.org`). The two non-video
-URLs render as plain markdown links and are not a promotion driver. One of them,
-`webaim.org` in `designing-accessible-chatbots.md`, is that file's only embed, so the file
-stays `.md`; the `fetchify.com` one sits in a file that has video embeds anyway.
-
-`src/components/Embed.astro` — new: takes `url` and optional `title`, detects Loom vs YouTube,
-emits a lazy `<iframe>` in a 16:9 aspect-ratio wrapper, uses `title` as the iframe's
-accessible name and renders it as a visible caption below.
-
-### `{% stepper %}` / `{% step %}` → `<Steps>` — 3 / 15
-
-Starlight's `<Steps>` wraps a single ordered list. Step bodies contain an `###` heading plus
-paragraphs, so the body is indented three spaces to stay inside the list item:
-
-```jsx
-<Steps>
-
-1. ### Get started with a Quickstart AI Agent
-
- The Quick Start AI Agent is an optimised journey…
-
-2. …
-
-</Steps>
-```
-
-The fiddliest transform in the set, but only 15 steps — hand-checked at the gate.
-
-### `{% code %}` → fence info string — 7
-
-| Attribute | Handling |
-|---|---|
-| `title="x"` | ` ```lang title="x" ` |
-| `lineNumbers="true"` | ` ```lang showLineNumbers ` |
-| `fullWidth="false"` | no Expressive Code equivalent — dropped, logged |
-
-### `{% columns %}` / `{% column %}` → `<CardGrid>` — 1 / 2
-
-One instance, in `opendialog-platform/actions/webhook-action/README.md`: a "✅ Do" / "❌ Don't"
-pair, each column containing a JSON fence. `<CardGrid>` wraps the two column bodies directly —
-its children need not be `<Card>` elements. Hand-checked at the gate.
-
-Note the fences here contain `{first_name}`, which is exactly the case `lib/segments.mjs`
-protects.
-
-### `{% file %}` → markdown link — 1
-
-`{% file src="…/DeliveryKnowledgeBase.csv" %}` becomes a link whose text is the file's
-basename and whose href is a Phase 3 asset placeholder.
-
-### `<figure>` and bare `<img>` → markdown images — 436
-
-430 `<figure>` blocks, each containing exactly one `<img>` (verified — no figure holds zero or
-several), plus 6 bare `<img>` outside any figure. A further 93 pre-existing markdown `![]()`
-references pass through, needing only the path rewrite.
-
-The highest-value transformation in the migration: raw HTML `<img>` bypasses `astro:assets`
-entirely, so 541 MB of images would ship unoptimised.
-
-```html
-<figure><img src="../../.gitbook/assets/Preview Main (1).jpg" alt="Alt">
-<figcaption><p>Caption</p></figcaption></figure>
-```
-becomes
-```markdown
-.jpg>)
-*Caption*
-```
-
-- Angle brackets are used **iff** the path contains a space, `(` or `)`.
-- 101 figures have an empty `<figcaption>` → image only, no caption paragraph.
-- 391 have an empty `alt`. It stays empty — inventing alt text is a prose edit. Logged for
- the docs team; Phase 5 checks alt coverage.
-- 2 `src` values are remote `https://` URLs and pass through unchanged.
-- Markdown has no `<figcaption>`. Restoring `<figure>` semantics via a rehype plugin is a
- Phase 4 item if it matters visually.
-
-### Card-tables → `<CardGrid>` + `<LinkCard>` — 8 tables, 41 cards
-
-```jsx
-<CardGrid>
- <LinkCard title="The OpenDialog model"
- description="Take a deepdive into the underpinning model…"
- href="/core-concepts/the-opendialog-model" />
-</CardGrid>
-```
-
-- Title from the `<strong>` inside the first `<a>`; description from the following cell;
- `href` from the `data-card-target` column, resolved through `route-map.json`.
-- 6 of the 42 links are `/broken/pages/…` and stay broken, as they are on the live site today.
-- **26 `data-card-cover` image references are dropped** — `<LinkCard>` has no image slot.
- Two consequences, both logged: a visual gap for Phase 4, and 26 assets that Phase 3 must
- **not** treat as orphans despite having no surviving reference.
-
-### ` ` — 1,203
-
-Strip at end of line (1,192); replace with a single space elsewhere (11). See correction §2.
-
-### Page links → route URLs — 381
-
-```
-[x](../foo/bar.md) -> [x](/section/foo/bar)
-[x](../foo/bar.md#anchor) -> [x](/section/foo/bar#anchor)
-[x](../foo/) -> [x](/section/foo)
-```
-
-Resolved source-relative against `route-map.json`, with `..` clamped at the source root
-(correction §6). Anchors are preserved verbatim — GitBook and Starlight both slugify headings
-the same way for these pages, and anchor correctness is a Phase 5 link-check concern.
-
-External links, `mailto:`, bare `#anchor` and `/broken/pages/…` pass through untouched.
-
-**Any link that fails to resolve fails the run.** No silent pass-through.
-
-### Preserved as-is
-
-`<mark>` (131), `<br>` (52), `<div>` (22), `<table>` (18, non-card), `<details>`/`<summary>`
-(14), `<a>` (58), `<strong>` (49). Kept verbatim in `.md`; JSX-normalised in `.mdx`.
-
----
-
-## Images at the Phase 2 gate
-
-Astro treats an unresolvable relative image path in markdown as a **fatal build error** —
-verified during design:
-
-```
-[ImageNotFound] Could not find requested image `…/nope.png`. Does it exist?
-```
-
-Assets do not land in `src/assets/` until Phase 3, so Phase 2 emits **root-absolute
-placeholders**: ``. Astro treats a leading `/` as a
-`public/` path and does not resolve it at build time, so the gate passes cleanly.
-
-`assets.mjs` rewrites these to relative `src/assets/` paths in Phase 3 and asserts that zero
-`/.gitbook/` references survive. Between the two phases, images 404 on the preview. This is
-the accepted cost; the alternative — staging assets in Phase 2 — would commit 541 MB into git
-history permanently, which Phase 3's slimming could never reclaim.
-
----
-
-## `.md` vs `.mdx`
-
-Default `.md`. Promote **only** when a Starlight component is emitted: 46 of 204 files.
-
-### MDX normalisation
-
-Applied to `.mdx` output only:
-
-- Self-close void elements: `<br>` → `<br />`, `<img …>` → `<img … />`
-- `class=` → `className=`
-- `style="a: b; c: d"` → `style={{ a: 'b', c: 'd' }}` — 131 `<mark style="color:purple;">`
- instances make this load-bearing, not theoretical
-- Escape bare `{` and `}` in prose as `\{` and `\}` — 15 lines across 6 files
-
-The escaping rule is general output encoding for the target format, not a per-file special
-case and not a prose edit. It renders a literal `{`, which is what GitBook shows today.
-
----
-
-## Sidebar generation
-
-`scripts/sidebar.mjs` writes `src/sidebar.generated.mjs`; `astro.config.mjs` imports it and
-stays hand-maintained. No regex-splicing into a file that also holds hand-written config, and
-re-run diffs never mix generated with hand-written changes.
-
-`SUMMARY.md` nests five levels deep (32 / 35 / 47 / 51 / 39 entries by indent) across six
-sections.
-
-### Page-and-group entries — 41
-
-Starlight groups are **not linkable**. Confirmed by reading the installed package rather than
-the published guide: `node_modules/@astrojs/starlight/schemas/sidebar.ts` defines
-`SidebarGroupSchema` as `label` / `translations` / `badge` / `collapsed`, with
-`attrs: z.never()`. There is no `link` field.
-
-41 `SUMMARY.md` entries are both a page and a parent. Each becomes a group whose **first item
-is the parent page itself, carrying the same label**:
-
-```js
-{ label: 'Message design', items: [
- { label: 'Message design', slug: 'opendialog-platform/…/message-design' },
- { label: 'Text message', slug: 'opendialog-platform/…/text-message' },
-] }
-```
-
-The label repeats. That is accepted for Phase 2 because it keeps every `SUMMARY.md` label
-exact, keeps all 204 pages reachable from the nav, and invents no text. GitBook's actual
-behaviour — one clickable row that expands — needs a `Sidebar` component override, which is
-Phase 4 chrome work where GitBook parity is already the stated goal.
-
-Section headings become top-level groups. The root `README.md` is `slug: ''`.
-
----
-
-## Idempotency
-
-`convert.mjs` deletes `src/content/docs/` wholesale before writing, removing the four Phase 1
-placeholder pages recorded in `MIGRATION-NOTES.md`. Output ordering is derived from
-`route-map.json`, which is itself derived from `SUMMARY.md` order. No timestamps, no
-randomness, no filesystem-order dependence.
-
-The gate asserts a second run is byte-identical to the first.
-
----
-
-## Testing
-
-`node:test`, run with `node --test`. No new dependency: the lockfile has broken CI twice
-already, and adding a test framework to get `describe`/`it` is not worth a third.
-
-Tests are written before implementation, one file per lib module, against inline fixtures
-drawn from real source text. The cases that matter most:
-
-- **`segments.mjs`** — `{first_name}` inside a JSON fence survives untouched; inline code
- spans are immune; `{% code %}` wrapping a fence; nested and unbalanced fences.
-- **`links.mjs`** — balanced parens in `image (149).png`; the angle-bracket form; the
- directory form; anchor preservation; root-clamped `..`; unresolvable target throws.
-- **`gitbook-blocks.mjs`** — all four hint styles; both embed forms; stepper indentation;
- each `{% code %}` attribute.
-- **`figures.mjs`** — empty caption; empty alt; remote src; angle-bracket path selection.
-- **`mdx.mjs`** — brace escaping outside code only; `style` string to object; void elements.
-- **`summary.mjs`** — the escaped-bracket label trap; section anchor ids; depth nesting.
-- **`frontmatter.mjs`** — `hidden` dropped; `description` preserved; YAML escaping of titles
- containing `:` and quotes.
-
-## Corpus invariants
-
-`convert.mjs` asserts these against the real corpus and exits non-zero on any miss, in the
-same spirit as `routes.mjs` self-verifying against the sitemap snapshot:
-
-| Invariant | Expected |
-|---|---|
-| Files written | 204 |
-| `.mdx` files | 46 |
-| Asides emitted | 258 |
-| `<LinkCard>` from `content-ref` | 51 |
-| `<LinkCard>` from card-tables | 41 |
-| `<Embed>` emitted | 36 (38 less 2 non-video) |
-| `<Steps>` / steps | 3 / 15 |
-| `<CardGrid>` | 9 (8 card-tables + 1 `columns`) |
-| HTML `<img>` converted to markdown images | 436 (430 in figures + 6 bare) |
-| Pre-existing markdown `![]()` refs preserved | 93 |
-| Page links rewritten | 381 |
-| Unresolved page links | 0 |
-| ` ` surviving | 0 |
-| `{%` surviving outside fences | 0 |
-| `hidden:` surviving in output | 0 |
-| Second run byte-identical | yes |
-
-A divergence means the script is wrong. Per `CLAUDE.md`, the expectation is not adjusted to
-match the output.
-
----
-
-## Logged, not fixed
-
-Appended to `MIGRATION-NOTES.md` at the gate:
-
-- The `README.md` "laaunched" typo.
-- 12 `/broken/pages/…` placeholders, 6 of them inside card-tables. Broken today, broken after.
-- The one source link with an extra `../` (correction §6), resolved by clamping.
-- 391 images with empty `alt`.
-- 26 dropped card-cover images — **Phase 3 must not treat these assets as orphans.**
-- `{% code fullWidth="false" %}` dropped, no Expressive Code equivalent.
-- 3 pages where the H1 and the nav label genuinely differ: `Default interpreter` /
- `OpenDialog interpreter`, `Integrations introduction` / `Integrating with OpenDialog`,
- `Adding a new topic of discussion` / `Add a new topic of discussion`. Frontmatter `title`
- takes the H1, sidebar takes the nav label — as GitBook does. Spot-check in Phase 5.
-- Both stray `.gitbook/assets/*.md` files contain absolute image paths from a contributor's
- local machine (`/Users/elliotmassen/…`). Neither publishes; no action.
-
-## Cross-phase handoffs
-
-**To Phase 3.** Every `/.gitbook/assets/…` placeholder must be rewritten and the count of
-survivors asserted to zero. The 26 card-cover assets are referenced by nothing after
-conversion and must be excluded from orphan deletion.
-
-**To Phase 4.** Linkable sidebar groups; `<figure>` semantics and caption styling; card-cover
-images; `{% columns %}` and `<Steps>` rendering in context.
diff --git a/package-lock.json b/package-lock.json
index 6a4ce67..86357dc 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -9,10 +9,10 @@
"version": "0.0.1",
"dependencies": {
"@astrojs/starlight": "^0.41.5",
- "@fontsource-variable/inter": "^5.3.0",
- "@fontsource/fragment-mono": "^5.3.0",
+ "@fontsource/ibm-plex-mono": "^5.3.0",
+ "@fontsource/poppins": "^5.3.0",
"astro": "^7.0.2",
- "sharp": "^0.34.5"
+ "sharp": "^0.35.3"
},
"devDependencies": {
"playwright": "^1.62.0"
@@ -615,9 +615,9 @@
}
},
"node_modules/@emnapi/core": {
- "version": "2.0.0-alpha.3",
- "resolved": "https://registry.npmjs.org/@emnapi/core/-/core-2.0.0-alpha.3.tgz",
- "integrity": "sha512-AZypUeJ/yByuxyS7BlSNRDOMLMlROYtjYdIAuBmJssVz1UJDSeYxLrdizhXCFYhedC5bqd/ASy8EuNXbVVXp9g==",
+ "version": "2.0.0-alpha.4",
+ "resolved": "https://registry.npmjs.org/@emnapi/core/-/core-2.0.0-alpha.4.tgz",
+ "integrity": "sha512-KjoUR6mNvjT+z5bKMy+a5QDI+kTNTiMZi6uPKzWuWjwZGNa0UPwIVduTfeBRdf6v8Ws5fmHDh7Usf15w/ANfkg==",
"license": "MIT",
"optional": true,
"peer": true,
@@ -627,9 +627,9 @@
}
},
"node_modules/@emnapi/runtime": {
- "version": "2.0.0-alpha.3",
- "resolved": "https://registry.npmjs.org/@emnapi/runtime/-/runtime-2.0.0-alpha.3.tgz",
- "integrity": "sha512-hFPAhMUjJD9BSyCANEISPOogeXC9Zo9ZQl7L6vKnaVsMkCtzznaW/naYypeyl0Gv5rYfWYsZbpixTMpjDJzQeA==",
+ "version": "2.0.0-alpha.4",
+ "resolved": "https://registry.npmjs.org/@emnapi/runtime/-/runtime-2.0.0-alpha.4.tgz",
+ "integrity": "sha512-Wy1TQ99obRP3Ah7cf/OOtK1zD9t3pYTWz+G/SpAwTFMhG5hoMdlvfzBpYoHUigS/izu3q+VhYMKhJd7Ii/trpg==",
"license": "MIT",
"optional": true,
"peer": true,
@@ -1109,19 +1109,19 @@
"@expressive-code/core": "^0.44.1"
}
},
- "node_modules/@fontsource-variable/inter": {
+ "node_modules/@fontsource/ibm-plex-mono": {
"version": "5.3.0",
- "resolved": "https://registry.npmjs.org/@fontsource-variable/inter/-/inter-5.3.0.tgz",
- "integrity": "sha512-OupL48va4JNofb97w6NYeF9S7W/kHNKM0Er8Dem5nqi4jeOLrVJDoE8tZEpnMJmtkvNbB1EIPPwHcdkF6b1oUA==",
+ "resolved": "https://registry.npmjs.org/@fontsource/ibm-plex-mono/-/ibm-plex-mono-5.3.0.tgz",
+ "integrity": "sha512-eTgnZjZEGk1QtD3ZstF+Vclo2HLAni8YMy34/DxllwZvyz1lR/1RF/xTiAquOBO7MvqBx8D2Ig2WCPMVfdZu7Q==",
"license": "OFL-1.1",
"funding": {
"url": "https://github.com/sponsors/ayuhito"
}
},
- "node_modules/@fontsource/fragment-mono": {
+ "node_modules/@fontsource/poppins": {
"version": "5.3.0",
- "resolved": "https://registry.npmjs.org/@fontsource/fragment-mono/-/fragment-mono-5.3.0.tgz",
- "integrity": "sha512-vpOLZhWq7Z6wUPo1qMl16Y4yjQJiN0d9TXX2oUtiYXmqUrXU23Wuto73Knyak+osdlIuHz46srpBZb2pfhHCIA==",
+ "resolved": "https://registry.npmjs.org/@fontsource/poppins/-/poppins-5.3.0.tgz",
+ "integrity": "sha512-cms1nM7U6SN8epIV1WMVOV8VsA645aSm3wHfzIQnkk188U341ThbJGSl2Sv54V29gnDbT2arMPfLzvVIIVCceQ==",
"license": "OFL-1.1",
"funding": {
"url": "https://github.com/sponsors/ayuhito"
@@ -1137,9 +1137,9 @@
}
},
"node_modules/@img/sharp-darwin-arm64": {
- "version": "0.34.5",
- "resolved": "https://registry.npmjs.org/@img/sharp-darwin-arm64/-/sharp-darwin-arm64-0.34.5.tgz",
- "integrity": "sha512-imtQ3WMJXbMY4fxb/Ndp6HBTNVtWCUI0WdobyheGf5+ad6xX8VIDO8u2xE4qc/fr08CKG/7dDseFtn6M6g/r3w==",
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-darwin-arm64/-/sharp-darwin-arm64-0.35.3.tgz",
+ "integrity": "sha512-RMnFX7YQsMoh7lWfcM4NEHHymBX/rLuKNPVM84XE9ONPcaSCDgE7CHIHpSgPcO2xcRthgBy1HfNO319mwhIAkg==",
"cpu": [
"arm64"
],
@@ -1149,19 +1149,19 @@
"darwin"
],
"engines": {
- "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+ "node": ">=20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
},
"optionalDependencies": {
- "@img/sharp-libvips-darwin-arm64": "1.2.4"
+ "@img/sharp-libvips-darwin-arm64": "1.3.2"
}
},
"node_modules/@img/sharp-darwin-x64": {
- "version": "0.34.5",
- "resolved": "https://registry.npmjs.org/@img/sharp-darwin-x64/-/sharp-darwin-x64-0.34.5.tgz",
- "integrity": "sha512-YNEFAF/4KQ/PeW0N+r+aVVsoIY0/qxxikF2SWdp+NRkmMB7y9LBZAVqQ4yhGCm/H3H270OSykqmQMKLBhBJDEw==",
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-darwin-x64/-/sharp-darwin-x64-0.35.3.tgz",
+ "integrity": "sha512-Xo+5uFBtLN0BKqieTxiFzFPQAUlBbbH5iBKyRX/z1JrbnYsHTfKJnUfL8+p2TPXr1pXqao4eeL4Rl144uDpK9w==",
"cpu": [
"x64"
],
@@ -1171,19 +1171,38 @@
"darwin"
],
"engines": {
- "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+ "node": ">=20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
},
"optionalDependencies": {
- "@img/sharp-libvips-darwin-x64": "1.2.4"
+ "@img/sharp-libvips-darwin-x64": "1.3.2"
+ }
+ },
+ "node_modules/@img/sharp-freebsd-wasm32": {
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-freebsd-wasm32/-/sharp-freebsd-wasm32-0.35.3.tgz",
+ "integrity": "sha512-lUxcqWIj2wMQ9BrwNjngcr1gWUr5xgaGThBRqPPalIC2n67Cqj1uPh8NnA/ZhAg8hUbKl+kVHKwgUIwe6ZYPrg==",
+ "license": "Apache-2.0",
+ "optional": true,
+ "os": [
+ "freebsd"
+ ],
+ "dependencies": {
+ "@img/sharp-wasm32": "0.35.3"
+ },
+ "engines": {
+ "node": ">=20.9.0"
+ },
+ "funding": {
+ "url": "https://opencollective.com/libvips"
}
},
"node_modules/@img/sharp-libvips-darwin-arm64": {
- "version": "1.2.4",
- "resolved": "https://registry.npmjs.org/@img/sharp-libvips-darwin-arm64/-/sharp-libvips-darwin-arm64-1.2.4.tgz",
- "integrity": "sha512-zqjjo7RatFfFoP0MkQ51jfuFZBnVE2pRiaydKJ1G/rHZvnsrHAOcQALIi9sA5co5xenQdTugCvtb1cuf78Vf4g==",
+ "version": "1.3.2",
+ "resolved": "https://registry.npmjs.org/@img/sharp-libvips-darwin-arm64/-/sharp-libvips-darwin-arm64-1.3.2.tgz",
+ "integrity": "sha512-9J6ypZFpQBj4YnePGoq/S38w6nz+vqg5WZLrLGY4YuSemdMq47GMLBPO42MzwdGwpg/agZ7xzZcFHa48xlywfg==",
"cpu": [
"arm64"
],
@@ -1197,9 +1216,9 @@
}
},
"node_modules/@img/sharp-libvips-darwin-x64": {
- "version": "1.2.4",
- "resolved": "https://registry.npmjs.org/@img/sharp-libvips-darwin-x64/-/sharp-libvips-darwin-x64-1.2.4.tgz",
- "integrity": "sha512-1IOd5xfVhlGwX+zXv2N93k0yMONvUlANylbJw1eTah8K/Jtpi15KC+WSiaX/nBmbm2HxRM1gZ0nSdjSsrZbGKg==",
+ "version": "1.3.2",
+ "resolved": "https://registry.npmjs.org/@img/sharp-libvips-darwin-x64/-/sharp-libvips-darwin-x64-1.3.2.tgz",
+ "integrity": "sha512-m2pW1n6cns9VaubNwsZ+c3CRYjxNQWgJ5gPlnL1nbBcpkBvFm6SCFN5o0psFHI8w9n11NKhFkeEDns98tiqbEw==",
"cpu": [
"x64"
],
@@ -1213,9 +1232,9 @@
}
},
"node_modules/@img/sharp-libvips-linux-arm": {
- "version": "1.2.4",
- "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-arm/-/sharp-libvips-linux-arm-1.2.4.tgz",
- "integrity": "sha512-bFI7xcKFELdiNCVov8e44Ia4u2byA+l3XtsAj+Q8tfCwO6BQ8iDojYdvoPMqsKDkuoOo+X6HZA0s0q11ANMQ8A==",
+ "version": "1.3.2",
+ "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-arm/-/sharp-libvips-linux-arm-1.3.2.tgz",
+ "integrity": "sha512-1eMLzy92I4J6rmi4mAT8yC3HxOtniyGELlzGbNMLLeqe052ahFQ0h6LFq+lh5DsDIdYViIDst08abvSbcEdLXQ==",
"cpu": [
"arm"
],
@@ -1229,9 +1248,9 @@
}
},
"node_modules/@img/sharp-libvips-linux-arm64": {
- "version": "1.2.4",
- "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-arm64/-/sharp-libvips-linux-arm64-1.2.4.tgz",
- "integrity": "sha512-excjX8DfsIcJ10x1Kzr4RcWe1edC9PquDRRPx3YVCvQv+U5p7Yin2s32ftzikXojb1PIFc/9Mt28/y+iRklkrw==",
+ "version": "1.3.2",
+ "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-arm64/-/sharp-libvips-linux-arm64-1.3.2.tgz",
+ "integrity": "sha512-dqVSFynCox4C/J8kT16V7SIFAns0IjgLwkvYT7p8LQVmJ5OS5b6tI9IGflxTeuBS//zXeFIUbwt5dwxyZ17cnA==",
"cpu": [
"arm64"
],
@@ -1245,9 +1264,9 @@
}
},
"node_modules/@img/sharp-libvips-linux-ppc64": {
- "version": "1.2.4",
- "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-ppc64/-/sharp-libvips-linux-ppc64-1.2.4.tgz",
- "integrity": "sha512-FMuvGijLDYG6lW+b/UvyilUWu5Ayu+3r2d1S8notiGCIyYU/76eig1UfMmkZ7vwgOrzKzlQbFSuQfgm7GYUPpA==",
+ "version": "1.3.2",
+ "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-ppc64/-/sharp-libvips-linux-ppc64-1.3.2.tgz",
+ "integrity": "sha512-3z0NHDxD6n5I9gc05U1eW1AyRm+Gznzq3naMrthPNqE6oYykcogW0l/jfpJdjYnuNl8R7yI9pNbE1XiUeyq0Aw==",
"cpu": [
"ppc64"
],
@@ -1261,9 +1280,9 @@
}
},
"node_modules/@img/sharp-libvips-linux-riscv64": {
- "version": "1.2.4",
- "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-riscv64/-/sharp-libvips-linux-riscv64-1.2.4.tgz",
- "integrity": "sha512-oVDbcR4zUC0ce82teubSm+x6ETixtKZBh/qbREIOcI3cULzDyb18Sr/Wcyx7NRQeQzOiHTNbZFF1UwPS2scyGA==",
+ "version": "1.3.2",
+ "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-riscv64/-/sharp-libvips-linux-riscv64-1.3.2.tgz",
+ "integrity": "sha512-bsb4rI+NldGOsXuej2r8OdSS8+zXDVaCWxyWrcv6kneTOlgAHtZABRzBBCwdsPiD90J4myNJuHpg6kA20ImW/w==",
"cpu": [
"riscv64"
],
@@ -1277,9 +1296,9 @@
}
},
"node_modules/@img/sharp-libvips-linux-s390x": {
- "version": "1.2.4",
- "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-s390x/-/sharp-libvips-linux-s390x-1.2.4.tgz",
- "integrity": "sha512-qmp9VrzgPgMoGZyPvrQHqk02uyjA0/QrTO26Tqk6l4ZV0MPWIW6LTkqOIov+J1yEu7MbFQaDpwdwJKhbJvuRxQ==",
+ "version": "1.3.2",
+ "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-s390x/-/sharp-libvips-linux-s390x-1.3.2.tgz",
+ "integrity": "sha512-/ABshyj8gCpyIrNXnHn4LorDJ0HHm1VhXPBlxZ8zAtfVPAaSafXPGn+sUSIRiwaSBy0mmFjSjiXI5mkcwdChKQ==",
"cpu": [
"s390x"
],
@@ -1293,9 +1312,9 @@
}
},
"node_modules/@img/sharp-libvips-linux-x64": {
- "version": "1.2.4",
- "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-x64/-/sharp-libvips-linux-x64-1.2.4.tgz",
- "integrity": "sha512-tJxiiLsmHc9Ax1bz3oaOYBURTXGIRDODBqhveVHonrHJ9/+k89qbLl0bcJns+e4t4rvaNBxaEZsFtSfAdquPrw==",
+ "version": "1.3.2",
+ "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-x64/-/sharp-libvips-linux-x64-1.3.2.tgz",
+ "integrity": "sha512-ITPEtgffGJ0S6G9dRyw/366tJQqFRcHWPHhC+Stpg3Z8AEMrDrTr2lhdz4f/Y/HMbRh//7Z5mBzEpVdi62Oc3w==",
"cpu": [
"x64"
],
@@ -1309,9 +1328,9 @@
}
},
"node_modules/@img/sharp-libvips-linuxmusl-arm64": {
- "version": "1.2.4",
- "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linuxmusl-arm64/-/sharp-libvips-linuxmusl-arm64-1.2.4.tgz",
- "integrity": "sha512-FVQHuwx1IIuNow9QAbYUzJ+En8KcVm9Lk5+uGUQJHaZmMECZmOlix9HnH7n1TRkXMS0pGxIJokIVB9SuqZGGXw==",
+ "version": "1.3.2",
+ "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linuxmusl-arm64/-/sharp-libvips-linuxmusl-arm64-1.3.2.tgz",
+ "integrity": "sha512-zE9EdiUzUmg5mDT5a1rk5fYJ6GWPloTwWBYDS14naqHsL+EaMpDj1AWnpLgh3u0YCORv2Tt50wrcrpYqkP97Kw==",
"cpu": [
"arm64"
],
@@ -1325,9 +1344,9 @@
}
},
"node_modules/@img/sharp-libvips-linuxmusl-x64": {
- "version": "1.2.4",
- "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linuxmusl-x64/-/sharp-libvips-linuxmusl-x64-1.2.4.tgz",
- "integrity": "sha512-+LpyBk7L44ZIXwz/VYfglaX/okxezESc6UxDSoyo2Ks6Jxc4Y7sGjpgU9s4PMgqgjj1gZCylTieNamqA1MF7Dg==",
+ "version": "1.3.2",
+ "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linuxmusl-x64/-/sharp-libvips-linuxmusl-x64-1.3.2.tgz",
+ "integrity": "sha512-m0lrLiUt+lBYnCFr8qV/65yMR4E/c7/wf78I5eKTdkEakFAlZ9QlzEM3QIhhAwVeUhLAHLcCq7a7Vszq/oFNZQ==",
"cpu": [
"x64"
],
@@ -1341,9 +1360,9 @@
}
},
"node_modules/@img/sharp-linux-arm": {
- "version": "0.34.5",
- "resolved": "https://registry.npmjs.org/@img/sharp-linux-arm/-/sharp-linux-arm-0.34.5.tgz",
- "integrity": "sha512-9dLqsvwtg1uuXBGZKsxem9595+ujv0sJ6Vi8wcTANSFpwV/GONat5eCkzQo/1O6zRIkh0m/8+5BjrRr7jDUSZw==",
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-linux-arm/-/sharp-linux-arm-0.35.3.tgz",
+ "integrity": "sha512-affVWCTLooy8TSxbDx2qkzuDeaWLNVBA+P//FNBirHsXpP2fuBhk5AuboYUnrDnzoXes8GFjpTx0SBFOCRg+FA==",
"cpu": [
"arm"
],
@@ -1353,19 +1372,19 @@
"linux"
],
"engines": {
- "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+ "node": ">=20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
},
"optionalDependencies": {
- "@img/sharp-libvips-linux-arm": "1.2.4"
+ "@img/sharp-libvips-linux-arm": "1.3.2"
}
},
"node_modules/@img/sharp-linux-arm64": {
- "version": "0.34.5",
- "resolved": "https://registry.npmjs.org/@img/sharp-linux-arm64/-/sharp-linux-arm64-0.34.5.tgz",
- "integrity": "sha512-bKQzaJRY/bkPOXyKx5EVup7qkaojECG6NLYswgktOZjaXecSAeCWiZwwiFf3/Y+O1HrauiE3FVsGxFg8c24rZg==",
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-linux-arm64/-/sharp-linux-arm64-0.35.3.tgz",
+ "integrity": "sha512-QgKDspHPnrU+GQ55XPhGwyhC8acLVOOSyAvo1oVfFmrIXLkDNmGWzAfDZ4xK8oSA1qBQrALcHX0G5UZni/SuFQ==",
"cpu": [
"arm64"
],
@@ -1375,19 +1394,19 @@
"linux"
],
"engines": {
- "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+ "node": ">=20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
},
"optionalDependencies": {
- "@img/sharp-libvips-linux-arm64": "1.2.4"
+ "@img/sharp-libvips-linux-arm64": "1.3.2"
}
},
"node_modules/@img/sharp-linux-ppc64": {
- "version": "0.34.5",
- "resolved": "https://registry.npmjs.org/@img/sharp-linux-ppc64/-/sharp-linux-ppc64-0.34.5.tgz",
- "integrity": "sha512-7zznwNaqW6YtsfrGGDA6BRkISKAAE1Jo0QdpNYXNMHu2+0dTrPflTLNkpc8l7MUP5M16ZJcUvysVWWrMefZquA==",
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-linux-ppc64/-/sharp-linux-ppc64-0.35.3.tgz",
+ "integrity": "sha512-sMd8rDxmpLOwv/7N44klFjOD5DUO7FLdjiXDI0hoxYaf7Ar262dQIEkosE98bps+5HPLtp/EvNqeqQtOycP/IA==",
"cpu": [
"ppc64"
],
@@ -1397,19 +1416,19 @@
"linux"
],
"engines": {
- "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+ "node": ">=20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
},
"optionalDependencies": {
- "@img/sharp-libvips-linux-ppc64": "1.2.4"
+ "@img/sharp-libvips-linux-ppc64": "1.3.2"
}
},
"node_modules/@img/sharp-linux-riscv64": {
- "version": "0.34.5",
- "resolved": "https://registry.npmjs.org/@img/sharp-linux-riscv64/-/sharp-linux-riscv64-0.34.5.tgz",
- "integrity": "sha512-51gJuLPTKa7piYPaVs8GmByo7/U7/7TZOq+cnXJIHZKavIRHAP77e3N2HEl3dgiqdD/w0yUfiJnII77PuDDFdw==",
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-linux-riscv64/-/sharp-linux-riscv64-0.35.3.tgz",
+ "integrity": "sha512-0Eob78yjlYPfL5vMNWAW55l3R9Y6BQS/gOfe0ZcP9mEz9ohhKSt4im1hayiknXgf8AWrFqMvJcKIdmLmEe7yeQ==",
"cpu": [
"riscv64"
],
@@ -1419,19 +1438,19 @@
"linux"
],
"engines": {
- "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+ "node": ">=20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
},
"optionalDependencies": {
- "@img/sharp-libvips-linux-riscv64": "1.2.4"
+ "@img/sharp-libvips-linux-riscv64": "1.3.2"
}
},
"node_modules/@img/sharp-linux-s390x": {
- "version": "0.34.5",
- "resolved": "https://registry.npmjs.org/@img/sharp-linux-s390x/-/sharp-linux-s390x-0.34.5.tgz",
- "integrity": "sha512-nQtCk0PdKfho3eC5MrbQoigJ2gd1CgddUMkabUj+rBevs8tZ2cULOx46E7oyX+04WGfABgIwmMC0VqieTiR4jg==",
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-linux-s390x/-/sharp-linux-s390x-0.35.3.tgz",
+ "integrity": "sha512-KgAxQ0DxpNOq1rG2t5cgTgShJFGSuU7XO45cqC+1NVOuZnP6tlgZRuSYOfNupGkHID0o3cJOsw4DVeJpMovcGw==",
"cpu": [
"s390x"
],
@@ -1441,19 +1460,19 @@
"linux"
],
"engines": {
- "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+ "node": ">=20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
},
"optionalDependencies": {
- "@img/sharp-libvips-linux-s390x": "1.2.4"
+ "@img/sharp-libvips-linux-s390x": "1.3.2"
}
},
"node_modules/@img/sharp-linux-x64": {
- "version": "0.34.5",
- "resolved": "https://registry.npmjs.org/@img/sharp-linux-x64/-/sharp-linux-x64-0.34.5.tgz",
- "integrity": "sha512-MEzd8HPKxVxVenwAa+JRPwEC7QFjoPWuS5NZnBt6B3pu7EG2Ge0id1oLHZpPJdn3OQK+BQDiw9zStiHBTJQQQQ==",
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-linux-x64/-/sharp-linux-x64-0.35.3.tgz",
+ "integrity": "sha512-8pqvxubL2PGdhlPy6GLqzDYMUjyRmKAwKHYKixpdJYBUK7PJ0C029XdsnpFIdgRZG68fZiGdHVWcKPvtiPB4cA==",
"cpu": [
"x64"
],
@@ -1463,19 +1482,19 @@
"linux"
],
"engines": {
- "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+ "node": ">=20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
},
"optionalDependencies": {
- "@img/sharp-libvips-linux-x64": "1.2.4"
+ "@img/sharp-libvips-linux-x64": "1.3.2"
}
},
"node_modules/@img/sharp-linuxmusl-arm64": {
- "version": "0.34.5",
- "resolved": "https://registry.npmjs.org/@img/sharp-linuxmusl-arm64/-/sharp-linuxmusl-arm64-0.34.5.tgz",
- "integrity": "sha512-fprJR6GtRsMt6Kyfq44IsChVZeGN97gTD331weR1ex1c1rypDEABN6Tm2xa1wE6lYb5DdEnk03NZPqA7Id21yg==",
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-linuxmusl-arm64/-/sharp-linuxmusl-arm64-0.35.3.tgz",
+ "integrity": "sha512-Vz0iQjzzcSX3HCbfwFfCSG/9SCIqyO0mH2sXyiHaAYfBk0cRsCWXRyQYX0ovCK/PAQBbTzQ0dsPQHh5MAFL59w==",
"cpu": [
"arm64"
],
@@ -1485,19 +1504,19 @@
"linux"
],
"engines": {
- "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+ "node": ">=20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
},
"optionalDependencies": {
- "@img/sharp-libvips-linuxmusl-arm64": "1.2.4"
+ "@img/sharp-libvips-linuxmusl-arm64": "1.3.2"
}
},
"node_modules/@img/sharp-linuxmusl-x64": {
- "version": "0.34.5",
- "resolved": "https://registry.npmjs.org/@img/sharp-linuxmusl-x64/-/sharp-linuxmusl-x64-0.34.5.tgz",
- "integrity": "sha512-Jg8wNT1MUzIvhBFxViqrEhWDGzqymo3sV7z7ZsaWbZNDLXRJZoRGrjulp60YYtV4wfY8VIKcWidjojlLcWrd8Q==",
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-linuxmusl-x64/-/sharp-linuxmusl-x64-0.35.3.tgz",
+ "integrity": "sha512-6O1NPKcDVj9QEdg7Hx549EX8U0rp6yXQERqru6yRN7fGBn32UvIRJUlWnk+8xDCiG76hXVBbX82NZ/ZKr0euIg==",
"cpu": [
"x64"
],
@@ -1507,29 +1526,26 @@
"linux"
],
"engines": {
- "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+ "node": ">=20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
},
"optionalDependencies": {
- "@img/sharp-libvips-linuxmusl-x64": "1.2.4"
+ "@img/sharp-libvips-linuxmusl-x64": "1.3.2"
}
},
"node_modules/@img/sharp-wasm32": {
- "version": "0.34.5",
- "resolved": "https://registry.npmjs.org/@img/sharp-wasm32/-/sharp-wasm32-0.34.5.tgz",
- "integrity": "sha512-OdWTEiVkY2PHwqkbBI8frFxQQFekHaSSkUIJkwzclWZe64O1X4UlUjqqqLaPbUpMOQk6FBu/HtlGXNblIs0huw==",
- "cpu": [
- "wasm32"
- ],
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-wasm32/-/sharp-wasm32-0.35.3.tgz",
+ "integrity": "sha512-cZ0XkcYGpHZkqW6iCkqTcmUC0CD9DhD5d/qeZlZkfRBn6GnHniZXLUo5+9xw8Iv76YE6LQFN9YNBlKREcCG76w==",
"license": "Apache-2.0 AND LGPL-3.0-or-later AND MIT",
"optional": true,
"dependencies": {
- "@emnapi/runtime": "^1.7.0"
+ "@emnapi/runtime": "^1.11.1"
},
"engines": {
- "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+ "node": ">=20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
@@ -1545,10 +1561,29 @@
"tslib": "^2.4.0"
}
},
+ "node_modules/@img/sharp-webcontainers-wasm32": {
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-webcontainers-wasm32/-/sharp-webcontainers-wasm32-0.35.3.tgz",
+ "integrity": "sha512-2rnq7bX3NzeR2T4YWgz8qiG4h3TSdMe+vN1iQXpJleSJ3SM5zQ8Fy2SyyXAWlbxpEZ2Y+Z4u1BePgJEYbSy80Q==",
+ "cpu": [
+ "wasm32"
+ ],
+ "license": "Apache-2.0",
+ "optional": true,
+ "dependencies": {
+ "@img/sharp-wasm32": "0.35.3"
+ },
+ "engines": {
+ "node": ">=20.9.0"
+ },
+ "funding": {
+ "url": "https://opencollective.com/libvips"
+ }
+ },
"node_modules/@img/sharp-win32-arm64": {
- "version": "0.34.5",
- "resolved": "https://registry.npmjs.org/@img/sharp-win32-arm64/-/sharp-win32-arm64-0.34.5.tgz",
- "integrity": "sha512-WQ3AgWCWYSb2yt+IG8mnC6Jdk9Whs7O0gxphblsLvdhSpSTtmu69ZG1Gkb6NuvxsNACwiPV6cNSZNzt0KPsw7g==",
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-win32-arm64/-/sharp-win32-arm64-0.35.3.tgz",
+ "integrity": "sha512-4bPwFdMbeC4JQ8L8LOyWp6nsHcboP5fxkp6iPOXz2Vg49R42TuMs2whkJ5OAP4/Ul035qOzy0AecOF9VOscn4w==",
"cpu": [
"arm64"
],
@@ -1558,16 +1593,16 @@
"win32"
],
"engines": {
- "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+ "node": ">=20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
}
},
"node_modules/@img/sharp-win32-ia32": {
- "version": "0.34.5",
- "resolved": "https://registry.npmjs.org/@img/sharp-win32-ia32/-/sharp-win32-ia32-0.34.5.tgz",
- "integrity": "sha512-FV9m/7NmeCmSHDD5j4+4pNI8Cp3aW+JvLoXcTUo0IqyjSfAZJ8dIUmijx1qaJsIiU+Hosw6xM5KijAWRJCSgNg==",
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-win32-ia32/-/sharp-win32-ia32-0.35.3.tgz",
+ "integrity": "sha512-r53mXsBN6lFUDiST764SvgwUdHAqM4rPAiDzAmf4fLoB6X/rkfyTrLCg6+g17wJJiCmB3JYgHuUldCWUIRFSXw==",
"cpu": [
"ia32"
],
@@ -1577,16 +1612,16 @@
"win32"
],
"engines": {
- "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+ "node": "^20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
}
},
"node_modules/@img/sharp-win32-x64": {
- "version": "0.34.5",
- "resolved": "https://registry.npmjs.org/@img/sharp-win32-x64/-/sharp-win32-x64-0.34.5.tgz",
- "integrity": "sha512-+29YMsqY2/9eFEiW93eqWnuLcWcufowXewwSNIT6UwZdUUCrM3oFjMWH/Z6/TMmb4hlFenmfAVbpWeup2jryCw==",
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/@img/sharp-win32-x64/-/sharp-win32-x64-0.35.3.tgz",
+ "integrity": "sha512-D4y1vNeZrIIJCN+uHaWVtH86B+aCrdMYYjicy9pXHvbGZeGYLLSd3wdVuC37FxVXlU1ARsk84eKWfWMXGYEqvA==",
"cpu": [
"x64"
],
@@ -1596,7 +1631,7 @@
"win32"
],
"engines": {
- "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+ "node": ">=20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
@@ -6136,47 +6171,52 @@
}
},
"node_modules/sharp": {
- "version": "0.34.5",
- "resolved": "https://registry.npmjs.org/sharp/-/sharp-0.34.5.tgz",
- "integrity": "sha512-Ou9I5Ft9WNcCbXrU9cMgPBcCK8LiwLqcbywW3t4oDV37n1pzpuNLsYiAV8eODnjbtQlSDwZ2cUEeQz4E54Hltg==",
- "hasInstallScript": true,
+ "version": "0.35.3",
+ "resolved": "https://registry.npmjs.org/sharp/-/sharp-0.35.3.tgz",
+ "integrity": "sha512-ej0zVHuZGHCiABXcNxeYhpRnPNPAcvbG8RMdBAhDAxLKkCRVSpK3Iyu7qbqw3JMzoj0REeM6f3tJLtVwl0023Q==",
"license": "Apache-2.0",
"dependencies": {
- "@img/colour": "^1.0.0",
+ "@img/colour": "^1.1.0",
"detect-libc": "^2.1.2",
- "semver": "^7.7.3"
+ "semver": "^7.8.5"
},
"engines": {
- "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+ "node": ">=20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
},
"optionalDependencies": {
- "@img/sharp-darwin-arm64": "0.34.5",
- "@img/sharp-darwin-x64": "0.34.5",
- "@img/sharp-libvips-darwin-arm64": "1.2.4",
- "@img/sharp-libvips-darwin-x64": "1.2.4",
- "@img/sharp-libvips-linux-arm": "1.2.4",
- "@img/sharp-libvips-linux-arm64": "1.2.4",
- "@img/sharp-libvips-linux-ppc64": "1.2.4",
- "@img/sharp-libvips-linux-riscv64": "1.2.4",
- "@img/sharp-libvips-linux-s390x": "1.2.4",
- "@img/sharp-libvips-linux-x64": "1.2.4",
- "@img/sharp-libvips-linuxmusl-arm64": "1.2.4",
- "@img/sharp-libvips-linuxmusl-x64": "1.2.4",
- "@img/sharp-linux-arm": "0.34.5",
- "@img/sharp-linux-arm64": "0.34.5",
- "@img/sharp-linux-ppc64": "0.34.5",
- "@img/sharp-linux-riscv64": "0.34.5",
- "@img/sharp-linux-s390x": "0.34.5",
- "@img/sharp-linux-x64": "0.34.5",
- "@img/sharp-linuxmusl-arm64": "0.34.5",
- "@img/sharp-linuxmusl-x64": "0.34.5",
- "@img/sharp-wasm32": "0.34.5",
- "@img/sharp-win32-arm64": "0.34.5",
- "@img/sharp-win32-ia32": "0.34.5",
- "@img/sharp-win32-x64": "0.34.5"
+ "@img/sharp-darwin-arm64": "0.35.3",
+ "@img/sharp-darwin-x64": "0.35.3",
+ "@img/sharp-freebsd-wasm32": "0.35.3",
+ "@img/sharp-libvips-darwin-arm64": "1.3.2",
+ "@img/sharp-libvips-darwin-x64": "1.3.2",
+ "@img/sharp-libvips-linux-arm": "1.3.2",
+ "@img/sharp-libvips-linux-arm64": "1.3.2",
+ "@img/sharp-libvips-linux-ppc64": "1.3.2",
+ "@img/sharp-libvips-linux-riscv64": "1.3.2",
+ "@img/sharp-libvips-linux-s390x": "1.3.2",
+ "@img/sharp-libvips-linux-x64": "1.3.2",
+ "@img/sharp-libvips-linuxmusl-arm64": "1.3.2",
+ "@img/sharp-libvips-linuxmusl-x64": "1.3.2",
+ "@img/sharp-linux-arm": "0.35.3",
+ "@img/sharp-linux-arm64": "0.35.3",
+ "@img/sharp-linux-ppc64": "0.35.3",
+ "@img/sharp-linux-riscv64": "0.35.3",
+ "@img/sharp-linux-s390x": "0.35.3",
+ "@img/sharp-linux-x64": "0.35.3",
+ "@img/sharp-linuxmusl-arm64": "0.35.3",
+ "@img/sharp-linuxmusl-x64": "0.35.3",
+ "@img/sharp-webcontainers-wasm32": "0.35.3",
+ "@img/sharp-win32-arm64": "0.35.3",
+ "@img/sharp-win32-ia32": "0.35.3",
+ "@img/sharp-win32-x64": "0.35.3"
+ },
+ "peerDependenciesMeta": {
+ "@types/node": {
+ "optional": true
+ }
}
},
"node_modules/shiki": {
diff --git a/package.json b/package.json
index ca47397..8117726 100644
--- a/package.json
+++ b/package.json
@@ -8,15 +8,18 @@
"build": "astro build",
"preview": "astro preview",
"astro": "astro",
- "convert": "node scripts/routes.mjs && node scripts/convert.mjs && node scripts/sidebar.mjs",
- "test": "node --test \"scripts/lib/*.test.mjs\""
+ "convert": "node scripts/routes.mjs && node scripts/assets.mjs && node scripts/convert.mjs && node scripts/sidebar.mjs",
+ "test": "node --test \"scripts/lib/*.test.mjs\"",
+ "verify:links": "node scripts/verify-links.mjs",
+ "verify:live": "node scripts/verify-live.mjs",
+ "verify:images": "node scripts/verify-images.mjs"
},
"dependencies": {
"@astrojs/starlight": "^0.41.5",
- "@fontsource-variable/inter": "^5.3.0",
- "@fontsource/fragment-mono": "^5.3.0",
+ "@fontsource/ibm-plex-mono": "^5.3.0",
+ "@fontsource/poppins": "^5.3.0",
"astro": "^7.0.2",
- "sharp": "^0.34.5"
+ "sharp": "^0.35.3"
},
"devDependencies": {
"playwright": "^1.62.0"
diff --git a/public/files/deliveryknowledgebase.csv b/public/files/deliveryknowledgebase.csv
new file mode 100644
index 0000000..49f837b
--- /dev/null
+++ b/public/files/deliveryknowledgebase.csv
@@ -0,0 +1,8 @@
+Do you offer next day delivery?,Our next day delivery costs £8 and takes 1 to 2 days depending on where you live.
+How long will shipping take?,"Our standard delivery takes 2 to 4 business days and is free for all orders. Looking for a higher cadence? You can also choose our next day delivery service, which will get your sneakers to you in under 2 days!"
+My order never arrived?,We're sorry to hear that! You can track your order on the website in the My Account section.
+Do you offer click and collect?,"Unfortunately, we don't currently offer a click and collect service."
+Do I need to sign for my parcel?,"No, you won't have to sign for it."
+Can I select a delivery location?,"Unfortunately , we don't currently offer a click and collect service."
+What are the delivery options?,You can choose between a free standard delivery (2 to 4 business day) or a next day delivery (1 to 2 business day) for £8.
+Have you got free delivery options?,Our standard delivery takes 2 to 4 business days and is free for all orders.
\ No newline at end of file
diff --git a/public/media/knowledge-base-demo.mp4 b/public/media/knowledge-base-demo.mp4
new file mode 100644
index 0000000..b374182
Binary files /dev/null and b/public/media/knowledge-base-demo.mp4 differ
diff --git a/reports/alt-text-todo.md b/reports/alt-text-todo.md
new file mode 100644
index 0000000..ebe2405
--- /dev/null
+++ b/reports/alt-text-todo.md
@@ -0,0 +1,474 @@
+# Images with no alt text
+
+Generated by `node scripts/verify-images.mjs`. Do not edit by hand.
+
+455 images across the documentation ship with an empty `alt` attribute, so a
+screen reader announces nothing for them.
+
+The fix belongs in this repository. `src/content/docs/` is the source of truth and is edited
+by hand: give the image alt text in the markdown — `` — and it
+ships on the next deploy.
+
+The 152 rows with no caption come first: nothing is announced for them at all, and they
+are the ones worth doing first. The remaining 303 sit under a visible caption, reproduced
+below. That caption is already announced, so alt text for those should describe what the
+image *shows* rather than repeat it — duplicating it makes a screen reader read the same
+sentence twice.
+
+| Page | Image | Existing caption |
+|---|---|---|
+| [Getting ready](https://docs.opendialog.ai/getting-started-1/getting-ready) | `https://lh7-rt.googleusercontent.com/docsz/AD_4nXehD4Czg1ekUeRm…` | |
+| [Chat Management Conversation](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/chat-management-conversation) | `image-3-1.png` | |
+| [Welcome Conversation](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/welcome-conversation) | `image-4-1-1.png` | |
+| [Welcome Conversation](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/welcome-conversation) | `image-5-1-1.png` | |
+| [Welcome Conversation](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/welcome-conversation) | `screenshot-2024-11-09-at-11-35-40.png` | |
+| [Topic Conversation](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/topic-conversation) | `screenshot-2024-11-09-at-18-24-23.png` | |
+| [Topic Conversation](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/topic-conversation) | `screenshot-2024-11-09-at-18-23-33.png` | |
+| [Global No Match Conversation](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/global-no-match-conversation) | `screenshot-2024-11-09-at-18-33-30.png` | |
+| [A Process Handling AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent) | `image-560.png` | |
+| [Add a new topic of discussion](https://docs.opendialog.ai/tutorials/add-a-new-topic-of-discussion) | `add-topic-source.png` | |
+| [Add a new topic of discussion](https://docs.opendialog.ai/tutorials/add-a-new-topic-of-discussion) | `images-slidedeck-1-1.png` | |
+| [Add a new topic of discussion](https://docs.opendialog.ai/tutorials/add-a-new-topic-of-discussion) | `images-slidedeck-1-2.png` | |
+| [Add a new topic of discussion](https://docs.opendialog.ai/tutorials/add-a-new-topic-of-discussion) | `images-slidedeck-1-3.png` | |
+| [Add a 3rd party integration](https://docs.opendialog.ai/tutorials/integrate) | `image-542.png` | |
+| [Designing Conversational AI Agents](https://docs.opendialog.ai/core-concepts/the-opendialog-model/designing-conversational-ai-agents) | `turns.png` | |
+| [Designing Conversational AI Agents](https://docs.opendialog.ai/core-concepts/the-opendialog-model/designing-conversational-ai-agents) | `intents.png` | |
+| [Turns and intents](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/scenarios/turns-and-intents) | `1.png` | |
+| [Turns and intents](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/scenarios/turns-and-intents) | `2.png` | |
+| [OpenDialog Conversation Engine](https://docs.opendialog.ai/core-concepts/how-the-conversation-engine-thinks) | `2023-06-20-16-05-02.png` | |
+| [OpenDialog Conversation Engine](https://docs.opendialog.ai/core-concepts/how-the-conversation-engine-thinks) | `2023-06-20-15-55-55.png` | |
+| [OpenDialog Conversation Engine](https://docs.opendialog.ai/core-concepts/how-the-conversation-engine-thinks) | `2023-06-20-15-59-11.png` | |
+| [OpenDialog Conversation Engine](https://docs.opendialog.ai/core-concepts/how-the-conversation-engine-thinks) | `2023-06-20-15-59-35.png` | |
+| [Attributes](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/about-attributes) | `image-532.png` | |
+| [Contextual help](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-help) | `image-84.png` | |
+| [Contextual FAQ](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/the-contextual-faq-pattern) | `faq-turn.png` | |
+| [Openings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings) | `0.png` | |
+| [Openings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings) | `1-1.png` | |
+| [Openings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings) | `2-2.png` | |
+| [Openings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings) | `3-1.png` | |
+| [Openings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings) | `4-1.png` | |
+| [Transactional openings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings/transactional-openings) | `2023-05-04-16-17-09-1.png` | |
+| [Transactional openings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings/transactional-openings) | `2023-05-04-16-23-35-1.png` | |
+| [Transactional openings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings/transactional-openings) | `spaces-it4t0sjdqeqcxi1fucau-uploads-mwtxl3uefl5avnjieqbh-img-69…` | |
+| [Transactional openings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings/transactional-openings) | `spaces-it4t0sjdqeqcxi1fucau-uploads-uk8yzf49ckvtwbfi1qdg-img-69…` | |
+| [Using in OpenDialog](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/authentication/using-in-opendialog) | `image-444.png` | |
+| [Components](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/transfer/components) | `screen-shot-2022-02-17-at-11-15-00-am.png` | |
+| [Components](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/transfer/components) | `https://lh4.googleusercontent.com/-fephlS1GFh1wzSgufd-uu4ThG6VQ…` | |
+| [Components](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/transfer/components) | `https://lh3.googleusercontent.com/t28Gx24JuifHuABQfepGxzNbsNgsh…` | |
+| [Components](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/transfer/components) | `https://lh4.googleusercontent.com/81FVqdrfg4PWunqvKsJWPi6nTzFvk…` | |
+| [Components](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/transfer/components) | `https://lh3.googleusercontent.com/7i5kHbb6tuzuMotTBTN0ZSVd-N4kK…` | |
+| [Components](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/transfer/components) | `https://lh6.googleusercontent.com/PQw7t1nDhx5ulOhyk65r4fsHid7Ph…` | |
+| [Best practices ](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/introduction) | `2023-05-19-19-36-01.png` | |
+| [Outcome: user profile](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/introduction/user-needs/outcome-user-profile) | `2023-05-15-20-27-38.png` | |
+| [NLU modeling](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/introduction/nlu-modeling) | `2023-06-09-16-10-54.png` | |
+| [NLU modeling](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/introduction/nlu-modeling) | `2023-06-09-16-11-08.png` | |
+| [NLU modeling](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/introduction/nlu-modeling) | `2023-06-09-16-11-21.png` | |
+| [Constructing Messages](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/constructing-messages) | `group-10-1.png` | |
+| [Message Conditions](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-conditions) | `2023-05-01-15-15-11-copy-1.png` | |
+| [Message Conditions](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-conditions) | `2023-05-01-15-57-54.png` | |
+| [Messages best practices](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/messages-best-practices) | `2023-05-23-13-10-36.png` | |
+| [Messages best practices](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/messages-best-practices) | `2023-05-23-10-57-47-2.png` | |
+| [Form Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/form-message) | `image-21.png` | |
+| [Location Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/location-message) | `image-529-1.png` | |
+| [Progress Bar Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/meta-messages/progress-bar-message) | `screenshot-2023-12-20-at-14-19-39-1.png` | |
+| [Webchat Interface Settings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/webchat-interface-design/webchat-interface-settings) | `image-2-4.png` | |
+| [Webchat Interface Settings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/webchat-interface-design/webchat-interface-settings) | `image-3-3.png` | |
+| [Amazon Lex interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/amazon-lex-interpreter) | `screenshot-2021-11-01-at-09-22-33.png` | |
+| [Amazon Lex interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/amazon-lex-interpreter) | `screenshot-2021-11-01-at-09-24-03.png` | |
+| [Amazon Lex interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/amazon-lex-interpreter) | `screenshot-2021-11-01-at-09-28-03.png` | |
+| [Amazon Lex interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/amazon-lex-interpreter) | `screenshot-2021-11-01-at-09-32-48.png` | |
+| [Amazon Lex interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/amazon-lex-interpreter) | `screenshot-2021-11-01-at-09-38-44.png` | |
+| [Amazon Lex interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/amazon-lex-interpreter) | `screenshot-2021-11-01-at-09-42-01.png` | |
+| [Amazon Lex interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/amazon-lex-interpreter) | `screenshot-2021-11-01-at-09-42-38-1.png` | |
+| [Microsoft LUIS interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/luis-interpreter) | `luis-app-id.png` | |
+| [Microsoft LUIS interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/luis-interpreter) | `luis-sub-key-app-url.png` | |
+| [Microsoft LUIS interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/luis-interpreter) | `luis-create-intent.png` | |
+| [Microsoft LUIS interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/luis-interpreter) | `luis-utterances.png` | |
+| [Microsoft LUIS interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/luis-interpreter) | `luis-add-to-intent.png` | |
+| [Microsoft LUIS interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/luis-interpreter) | `luis-preview.png` | |
+| [Google Dialogflow](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter) | `image-380.png` | |
+| [Google Dialogflow](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter) | `image-426.png` | |
+| [Google Dialogflow interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-interpreter) | `image-434.png` | |
+| [Google Dialogflow interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-interpreter) | `image-8.png` | |
+| [Google Dialogflow interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-interpreter) | `image-101.png` | |
+| [Google Dialogflow Knowledge Base](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-knowledge-base) | `od-kamau-cloud-opendialog-ai-admin-interpreters-mapping-99-scen…` | |
+| [Google Dialogflow Knowledge Base](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-knowledge-base) | `od-kamau-cloud-opendialog-ai-admin-interpreters-mapping-99-scen…` | |
+| [Google Dialogflow Knowledge Base](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-knowledge-base) | `od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0…` | |
+| [Google Dialogflow Knowledge Base](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-knowledge-base) | `od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0…` | |
+| [Google Dialogflow Knowledge Base](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-knowledge-base) | `od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0…` | |
+| [Google Dialogflow Knowledge Base](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-knowledge-base) | `2023-06-09-15-46-54.png` | |
+| [Google Dialogflow Knowledge Base](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-knowledge-base) | `2023-06-09-15-27-50.png` | |
+| [Google Dialogflow Knowledge Base](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-knowledge-base) | `od-kamau-cloud-opendialog-ai-admin-demo-scenario-0x13c2efa-3.png` | |
+| [Microsoft QnA interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/qna-interpreter) | `qna-new-pair.png` | |
+| [Microsoft QnA interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/qna-interpreter) | `qna-pairs.png` | |
+| [Microsoft QnA interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/qna-interpreter) | `qna-publish.png` | |
+| [Microsoft QnA interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/qna-interpreter) | `qna-interpreter.png` | |
+| [Microsoft QnA interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/qna-interpreter) | `qna-test.png` | |
+| [Microsoft QnA interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/qna-interpreter) | `qna-turn.png` | |
+| [Microsoft QnA interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/qna-interpreter) | `qna-add-to-intent.png` | |
+| [Microsoft QnA interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/qna-interpreter) | `qna-answer-intent.png` | |
+| [Microsoft QnA interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/qna-interpreter) | `qna-message.png` | |
+| [Microsoft QnA interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/qna-interpreter) | `qna-preview.png` | |
+| [Interpreter Orchestration](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/interpreter-orchestration) | `screenshot-2024-03-27-at-08-40-11.png` | |
+| [Interpreter Orchestration](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/interpreter-orchestration) | `group-5-1.png` | |
+| [Interpreter Orchestration](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/interpreter-orchestration) | `screenshot-2024-03-27-at-08-40-11.png` | |
+| [Troubleshooting interpreters](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/troubleshooting-interpreters) | `2023-06-16-07-40-11.png` | |
+| [Troubleshooting interpreters](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/troubleshooting-interpreters) | `2023-06-16-07-40-37-1.png` | |
+| [Troubleshooting interpreters](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/troubleshooting-interpreters) | `2023-06-16-07-44-00-copy.png` | |
+| [Troubleshooting interpreters](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/troubleshooting-interpreters) | `2023-06-16-07-47-08.png` | |
+| [LLM Actions](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions) | `image-614.png` | |
+| [LLM Actions](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions) | `image-615.png` | |
+| [LLM Actions](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions) | `image-621.png` | |
+| [3rd party Integrations in your application](https://docs.opendialog.ai/opendialog-platform/actions) | `2023-05-02-15-20-54.png` | |
+| [Webhook action](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action) | `image-2.png` | |
+| [Webhook action](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action) | `image-1-1.png` | |
+| [Webhook action](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action) | `image-603.png` | |
+| [Webhook action](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action) | `image-604.png` | |
+| [Webhook action](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action) | `image-605.png` | |
+| [Webhook action](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action) | `image-606.png` | |
+| [Webhook action](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action) | `image-607.png` | |
+| [Webhook action](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action) | `image-608.png` | |
+| [Execution logs and troubleshooting](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action/execution-logs-and-troubleshooting) | `image-609.png` | |
+| [Execution logs and troubleshooting](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action/execution-logs-and-troubleshooting) | `screenshot-2025-11-03-at-13-25-37.png` | |
+| [[Deprecated] webhook actions](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action/webhook-action) | `image-536.png` | |
+| [[Deprecated] webhook actions](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action/webhook-action) | `image-540.png` | |
+| [[Deprecated] webhook actions](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action/webhook-action) | `image-541.png` | |
+| [[Deprecated] webhook actions](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action/webhook-action) | `image-542.png` | |
+| [[Deprecated] webhook actions](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action/webhook-action) | `image-543.png` | |
+| [[Deprecated] webhook actions](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action/webhook-action) | `image-544.png` | |
+| [[Deprecated] webhook actions](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action/webhook-action) | `image-545.png` | |
+| [Set Attributes Action](https://docs.opendialog.ai/opendialog-platform/actions/actions-from-library/set-attributes-action) | `image-2-3.png` | |
+| [Set Attributes Action](https://docs.opendialog.ai/opendialog-platform/actions/actions-from-library/set-attributes-action) | `image-1-1-3-1.png` | |
+| [Datetime Action](https://docs.opendialog.ai/opendialog-platform/actions/actions-from-library/datetime-action) | `screenshot-2025-07-11-at-11-59-08.png` | |
+| [Chatwoot](https://docs.opendialog.ai/opendialog-platform/actions/conversation-hand-off/chatwoot) | `https://eucattachment.freshdesk.com/inline/attachment?token=eyJ…` | |
+| [Previewing your application](https://docs.opendialog.ai/opendialog-platform/previewing-your-application) | `preview-attribute.jpg` | |
+| [Additional menu links](https://docs.opendialog.ai/opendialog-platform/additional-menu-links) | `zrzut-ekranu-2025-11-3-o-14-37-53.png` | |
+| [Additional menu links](https://docs.opendialog.ai/opendialog-platform/additional-menu-links) | `zrzut-ekranu-2025-11-3-o-14-48-02.png` | |
+| [Troubleshooting and Common Problems](https://docs.opendialog.ai/opendialog-platform/troubleshooting-and-common-problems) | `2023-06-14-16-31-02.png` | |
+| [Troubleshooting and Common Problems](https://docs.opendialog.ai/opendialog-platform/troubleshooting-and-common-problems) | `2023-06-14-13-08-01-copy.png` | |
+| [WebChat authentication](https://docs.opendialog.ai/developing-with-opendialog/webchat/webchat-authentication) | `untitled.png` | |
+| [[Legacy] External APIs](https://docs.opendialog.ai/developing-with-opendialog/interaction-api) | `image-242.png` | |
+| [Public APIs](https://docs.opendialog.ai/developing-with-opendialog/public-apis) | `image-626.png` | |
+| [Public APIs](https://docs.opendialog.ai/developing-with-opendialog/public-apis) | `image-627.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-627.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `expand-message-demo.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `webhook-auth-demo.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-623.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-622.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `screenshot-2026-01-08-at-15-53-37.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `screenshot-2026-01-08-at-16-33-54.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-624.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-6.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-584.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-585.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-586.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-588.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-575-1.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-1-4.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-2-5.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-3-4.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-574.png` | |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-572.png` | |
+| [Introduction](https://docs.opendialog.ai/) | `1270x760-image-22.png` | Manage LLM prompts and integrate with your application data |
+| [Introduction](https://docs.opendialog.ai/) | `1270x760-image-23.png` | Build RAG services from your own document sources and integrate in your AI Agents |
+| [Introduction](https://docs.opendialog.ai/) | `1270x760-image-24.png` | Use Semantic Classification to identify intents at just the right level for your application |
+| [Introduction](https://docs.opendialog.ai/) | `1270x760-image-26.png` | Design conversations and track every decision with our detailed analytics |
+| [Introduction](https://docs.opendialog.ai/) | `1270x760-image-27.png` | Track what users are saying and where in the conversation they are saying it and use it to improve your application |
+| [Introduction](https://docs.opendialog.ai/) | `1270x760-image-21.png` | Create multiple types of messages, embed widgets and customise with our SDK |
+| [Introduction](https://docs.opendialog.ai/) | `1270x760-image-30.png` | A wealth of widgets to customise your AI Agent and make life easier for your users |
+| [Introduction](https://docs.opendialog.ai/) | `1270x760-image-31.png` | Customise brand and style for your users and customers |
+| [Introduction](https://docs.opendialog.ai/) | `1270x760-image-32.png` | Accessible to AA standards |
+| [Introduction](https://docs.opendialog.ai/) | `1270x760-image-34.png` | With a powerful SDK to customise further |
+| [Introduction](https://docs.opendialog.ai/) | `1270x760-image-28.png` | Integrate with your own applications and flexibly pull data into your AI agent and prompts |
+| [Introduction](https://docs.opendialog.ai/) | `1270x760-image-29.png` | Translation support to launch your AI Agent across multiple locales |
+| [Introduction](https://docs.opendialog.ai/) | `1270x760-image-33.png` | With a unique preview and test environment to help you build with confidence |
+| [Quick Start AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/quick-start-ai-agent) | `image-547.png` | Create Scenario Link |
+| [Quick Start AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/quick-start-ai-agent) | `image-548.png` | Step 1 - Quick Start AI Agent - Provide a name |
+| [Quick Start AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/quick-start-ai-agent) | `image-549.png` | Step 2 - Quick Start AI Agent - Add a knoweldge source |
+| [Quick Start AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/quick-start-ai-agent) | `description.png` | Step 3a - Quick Start AI Agent - Provide a quick description |
+| [Quick Start AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/quick-start-ai-agent) | `vectorise.png` | Quick Start AI Agent - Step 3b - Vectorization |
+| [Quick Start AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/quick-start-ai-agent) | `ai-agent-completed.png` | Quick Start AI Agent - Step 3c - Completed |
+| [Quick Start AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/quick-start-ai-agent) | `test-agent.png` | Quick Start AI Agent - Ready to be Tested! |
+| [The "Start from Scratch" AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent) | `image-2-1-1.png` | Create Scenario Link |
+| [The "Start from Scratch" AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent) | `start-from-scratch-scenario.png` | Start from Scratch Scenario |
+| [The "Start from Scratch" AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent) | `image-5-1.png` | The Start From Scratch Conversations and Flows |
+| [Welcome Conversation](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/welcome-conversation) | `welcome-conversation.png` | Welcome Conversation |
+| [Welcome Conversation](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/welcome-conversation) | `welcome-scene.png` | Welcome Scene |
+| [Welcome Conversation](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/welcome-conversation) | `welcome-turn.png` | Welcome Turn |
+| [Topic Conversation](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/topic-conversation) | `image-6-1.png` | The Topic Conversation |
+| [Topic Conversation](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/topic-conversation) | `screenshot-2024-11-09-at-18-28-28.png` | The Topic Conversation |
+| [Global No Match Conversation](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/global-no-match-conversation) | `screenshot-2024-11-09-at-18-35-20-1.png` | The No Match turn with a virtual intent |
+| [Supporting LLM Actions](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/supporting-llm-actions) | `screenshot-2024-11-09-at-18-43-42.png` | LLM Actions of the "Start from Scratch" scenario |
+| [Semantic Classifier: Query Classifier](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/semantic-classifier-query-classifier) | `image-546.png` | The "Start From Scratch" semantic classifier |
+| [A Process Handling AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent) | `image-551.png` | Appointment booking process |
+| [A Process Handling AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent) | `image-552.png` | Moving from a Topic Conversation to the Appointment Booking Conversation |
+| [A Process Handling AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent) | `image-553.png` | The sample step scene |
+| [A Process Handling AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent) | `image-554.png` | The Step Introduction Turn |
+| [A Process Handling AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent) | `image-556.png` | First step of OpenDialog appointment booking |
+| [A Process Handling AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent) | `image-559.png` | Continue or Complete moves us to New Scene |
+| [A Process Handling AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent) | `intent-and-virtual-intents.png` | Virtual intents |
+| [A Process Handling AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent) | `image-561.png` | Answering a question and then return to the doctor choice |
+| [A Process Handling AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent) | `image-562.png` | Virtual intent on QuestionResponse that forces the conversation engine to behave as if the user asked about doctor choice |
+| [A Process Handling AI Agent](https://docs.opendialog.ai/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent) | `image-563.png` | AskAboutDoctor routing intent |
+| [Add a new topic of discussion](https://docs.opendialog.ai/tutorials/add-a-new-topic-of-discussion) | `opendialog-model.png` | Breakdown of the OpenDialog model |
+| [Add a new topic of discussion](https://docs.opendialog.ai/tutorials/add-a-new-topic-of-discussion) | `images-slidedeck-1.png` | Duplicating a scene. |
+| [Use knowledge sources via RAG](https://docs.opendialog.ai/tutorials/use-knowledge-sources-via-rag) | `rag-overview.png` | From RAG to responses |
+| [Use knowledge sources via RAG](https://docs.opendialog.ai/tutorials/use-knowledge-sources-via-rag) | `rag-diagram.png` | Overview of adding and using a knowledge service |
+| [Use knowledge sources via RAG](https://docs.opendialog.ai/tutorials/use-knowledge-sources-via-rag) | `image-613.png` | Creating a vector topic |
+| [Adding a structured conversation](https://docs.opendialog.ai/tutorials/adding-a-structured-conversation) | `image-553.png` | A template scene with it's different turn components |
+| [Add a 3rd party integration](https://docs.opendialog.ai/tutorials/integrate) | `opendialog-actions-122024.png` | Navigate to the webhook action screen |
+| [Add a 3rd party integration](https://docs.opendialog.ai/tutorials/integrate) | `image-535.png` | A webhook action |
+| [Add a 3rd party integration](https://docs.opendialog.ai/tutorials/integrate) | `image-536.png` | Adding attributes to your action |
+| [Add a 3rd party integration](https://docs.opendialog.ai/tutorials/integrate) | `image-537.png` | Testing a webhook action |
+| [Add a 3rd party integration](https://docs.opendialog.ai/tutorials/integrate) | `opendialog-actions-2.png` | Adding an action to an intent |
+| [Test and tweak your AI Agent](https://docs.opendialog.ai/tutorials/test-and-tweak-your-ai-agent) | `aiagent-testsheet.png` | Example of the setup of an AI Agent test sheet |
+| [Test and tweak your AI Agent](https://docs.opendialog.ai/tutorials/test-and-tweak-your-ai-agent) | `preview-overview.png` | Preview your AI Agent and visualise it's interactions in real time |
+| [Test and tweak your AI Agent](https://docs.opendialog.ai/tutorials/test-and-tweak-your-ai-agent) | `nomatch.png` | No classified intent got matched, and therefor the NoMatch intent gets triggered |
+| [Test and tweak your AI Agent](https://docs.opendialog.ai/tutorials/test-and-tweak-your-ai-agent) | `no-messages-passing-conditions.png` | A conversation that has a failing message due to conditions |
+| [Publish your AI Agent](https://docs.opendialog.ai/tutorials/publish-your-ai-agent) | `create-new-alias.png` | Create a new alias by giving it a name and attributing a scenario |
+| [OpenDialog Approach](https://docs.opendialog.ai/core-concepts/the-opendialog-model) | `2b.png` | Combining conversation design with explicit reasoning and GenAI |
+| [Designing Conversational AI Agents](https://docs.opendialog.ai/core-concepts/the-opendialog-model/designing-conversational-ai-agents) | `3b.png` | High-level overview of the OpenDialog Framework |
+| [Designing Conversational AI Agents](https://docs.opendialog.ai/core-concepts/the-opendialog-model/designing-conversational-ai-agents) | `5b.png` | The OpenDialog Reasoning Cycle |
+| [Designing Conversational AI Agents](https://docs.opendialog.ai/core-concepts/the-opendialog-model/designing-conversational-ai-agents) | `l3-levels-1.png` | Levels of the OpenDialog framework |
+| [Designing Conversational AI Agents](https://docs.opendialog.ai/core-concepts/the-opendialog-model/designing-conversational-ai-agents) | `design-scenario-1.png` | Creating a Scenario in OpenDialog |
+| [Designing Conversational AI Agents](https://docs.opendialog.ai/core-concepts/the-opendialog-model/designing-conversational-ai-agents) | `design-conversation-1.png` | Conversations within an OpenDialog scenario. |
+| [Designing Conversational AI Agents](https://docs.opendialog.ai/core-concepts/the-opendialog-model/designing-conversational-ai-agents) | `scenes.png` | Scenes in OpenDialog conversations |
+| [Designing Conversational AI Agents](https://docs.opendialog.ai/core-concepts/the-opendialog-model/designing-conversational-ai-agents) | `putting-it-all-together-1.png` | Overview of the components in the OpenDialog model |
+| [OpenDialog Platform](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace) | `od-workspacedashboard.png` | The Workspace Dashboard is your go-to starting point to create & manage your applications. |
+| [OpenDialog Platform](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace) | `od-workspacenavigation.png` | Switching to another workspace or adding a new workspace |
+| [OpenDialog Platform](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace) | `od-workspacecreatenew.png` | Use the workspace dropdown to create a new workspace |
+| [Scenarios](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/scenarios) | `screenshot-2023-05-26-at-12-51-54.png` | Access the scenario overview through the left-hand menu or via the Manage Scenarios button. |
+| [Scenarios](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/scenarios) | `screenshot-2023-05-26-at-12-59-19.png` | Create a new scenario via the 'Create new scenario' button or import an existing scenario via a .json file |
+| [Scenarios](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/scenarios) | `2023-05-01-16-32-21.png` | Example of Scenario functionality |
+| [Scenarios](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/scenarios) | `screenshot-2023-05-26-at-13-05-41.png` | Import scenario option at the top of the main Scenario Overview area. |
+| [Scenarios](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/scenarios) | `2023-05-18-14-54-46.png` | Scenario settings in the conversation designer |
+| [Conversations](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/scenarios/conversations) | `2023-05-18-15-08-12.png` | Conversation settings |
+| [Conversations](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/scenarios/conversations) | `2023-05-18-15-09-06.png` | Conversation settings expanded |
+| [Scenes](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/scenarios/scenes) | `2023-05-18-15-18-42.png` | Scenes settings |
+| [Turns and intents](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/scenarios/turns-and-intents) | `2023-05-18-15-25-33.png` | Turns settings |
+| [Turns and intents](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/scenarios/turns-and-intents) | `2023-05-18-15-29-56.png` | Intents in turns |
+| [Turns and intents](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/scenarios/turns-and-intents) | `2023-05-18-15-38-33.png` | Intent settings |
+| [Language Services](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/language-services) | `od-workspacedashboard.png` | Access the language services section from the Workspace Dashboard |
+| [Managing Users](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/opendialog-account-management/create-and-manage-users) | `screenshot-2025-07-11-at-17-09-31.png` | The user creation screen |
+| [Managing Users](https://docs.opendialog.ai/core-concepts/the-opendialog-workspace/opendialog-account-management/create-and-manage-users) | `screenshot-2025-07-11-at-16-48-00.png` | The user editing screen |
+| [Attributes](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/about-attributes) | `image-530-1.png` | Using a collection attribute in messages |
+| [Attributes](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/about-attributes) | `image-531.png` | Outcome of collection attribute in chat. |
+| [Attribute Management](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/attribute-management) | `screenshot-2024-02-27-at-09-18-27.png` | OpenDialog Attribute Management lets you create new attributes on a need-to-have basis throughout the conversation engine. |
+| [Attribute Management](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/attribute-management) | `group-2-1.png` | The attribute input field can be accessed within the advanced intent settings section in conversation designer sidebar. |
+| [Attribute Management](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/attribute-management) | `group-1-1.png` | The attribute management input field can be accessed under the custom conditions section of the conversation designer sidebar. |
+| [Attribute Management](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/attribute-management) | `group-3-1.png` | The attribute input field can be accessed within the message editor section of the conversation designer |
+| [Attribute Management](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/attribute-management) | `group-4.png` | Click the 'Create new attribute' button to create a new attribute for your scenario. |
+| [Attribute Management](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/attribute-management) | `screenshot-2024-02-27-at-11-22-29.png` | Click the button at the bottom of the drop down field to create a new attribute. |
+| [Attribute Management](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/attribute-management) | `screenshot-2024-02-27-at-11-26-11.png` | Click the button at the bottom of the drop down field to create a new attribute within the message editor. |
+| [Attribute Management](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/attribute-management) | `screenshot-2024-02-27-at-11-22-41.png` | Use the 'Add new attribute' modal to create a new dynamic attribute for your scenario. |
+| [Attribute Management](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/attribute-management) | `screenshot-2024-02-27-at-11-21-09.png` | Start typing your chosen attribute into the text field to bring up the attribute dropdown selection. |
+| [Attribute Management](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/attribute-management) | `screenshot-2024-02-27-at-12-58-47.png` | Click the information icon button on the right hand side of the input field to find out further information about an attribute. |
+| [Attribute Management](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/attribute-management) | `screenshot-2024-02-27-at-11-24-56.png` | Open a curly brace to activate the attribute management input field within the message editor. |
+| [Conditions and operators](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/conditions-and-operators) | `image-565.png` | Conditions And operator |
+| [Conditions and operators](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/conditions-and-operators) | `image-567.png` | Conditions Or operator |
+| [Conditions and operators](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/conditions-and-operators) | `image-569.png` | Message Template conditions OR operator |
+| [Conversation Design](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design) | `2023-05-01-10-54-09.png` | Conversation Designer interface |
+| [Conversation Design](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design) | `search-scenario-view.png` | Search across Intents and Messages using the search functionality in the main scenario menu |
+| [Conversation Design](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design) | `search-message.png` | Type a query in the search bar and get an immediate list of the conversational components you can click on to edit |
+| [Restart](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-restart-chat-end) | `2023-11-09-18-52-09.png` | Toggle for Restart button in settings |
+| [Restart](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-restart-chat-end) | `2023-11-09-18-53-48.png` | Restart icon in user interface |
+| [Restart](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-restart-chat-end) | `2023-11-09-18-48-53.png` | intent.core.restart in the Trigger conversation |
+| [End chat](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-restart-chat-end-1) | `2023-11-09-19-07-11.png` | End chat toggle in interface settings |
+| [End chat](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-restart-chat-end-1) | `2023-11-09-19-08-09-1.png` | End chat link in user interface |
+| [Contextual and Global No Match](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-no-match-pattern) | `2023-11-09-18-41-49.png` | Global no match turn with intents from custom template |
+| [Contextual and Global No Match](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-no-match-pattern) | `2023-11-09-18-39-04.png` | Intents in no match turn |
+| [Contextual FAQ](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/the-contextual-faq-pattern) | `faq-interface-turns.png` | Package Bot FAQ Welcome Scene |
+| [Contextual FAQ](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/the-contextual-faq-pattern) | `2023-06-30-15-33-50.png` | Screenshot showing XML for DialogFlow KB |
+| [Transactional openings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings/transactional-openings) | `2023-05-04-15-58-27-1.png` | lowes.com |
+| [Assistant personality](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/introduction/assistant-personality) | `2023-05-15-20-24-57.png` | Sample assistant tone profile |
+| [Sample dialogs](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/introduction/sample-dialogs) | `2023-05-15-20-34-34.png` | Example of a sample dialog |
+| [Conversation structure](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/introduction/conversation-structure) | `2023-05-17-07-54-16.png` | Extract of a diagram |
+| [Conversation structure](https://docs.opendialog.ai/opendialog-platform/conversation-designer/conversation-design/introduction/conversation-structure) | `2023-05-17-07-53-21.png` | Extract with conversations and scenes |
+| [Message editor](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-editor) | `designoption-notexpanded.png` | Design option - not expanded |
+| [Message editor](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-editor) | `group-24.png` | Design option - expanded |
+| [Message editor](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-editor) | `group-25.png` | How to find the message editor |
+| [Message editor](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-editor) | `group-26.png` | Search across Intents and Messaes using the search functionality in the main scenario menu |
+| [Message editor](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-editor) | `screenshot-2024-06-05-at-15-36-41.png` | Enter your search query in the search bar that appears when selecting Search in the main scenario menu |
+| [Message editor](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-editor) | `group-27.png` | Message catalog |
+| [Message editor](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-editor) | `group-28.png` | Multiple messages associated with a single intent |
+| [Message editor](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-editor) | `screenshot-2025-03-06-at-11-09-33-1.png` | Edit Message screen |
+| [Constructing Messages](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/constructing-messages) | `image-1-2.png` | Individual message screen to design your message |
+| [Constructing Messages](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/constructing-messages) | `2023-05-23-13-09-37.png` | All text in a single message |
+| [Constructing Messages](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/constructing-messages) | `screenshot-2024-06-05-at-13-47-08.png` | Text divided up in smaller chunks for readability |
+| [Constructing Messages](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/constructing-messages) | `2023-05-23-10-57-47-5.png` | Example screen and content |
+| [Message Conditions](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-conditions) | `2023-05-01-14-35-48.png` | Example of messages with conditions |
+| [Messages best practices](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/messages-best-practices) | `2023-05-23-13-09-37.png` | All text in a single message |
+| [Messages best practices](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/messages-best-practices) | `2023-05-23-10-57-47-5.png` | Example screen and content |
+| [Subsequent Messages - Virtual Intents](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/subsequent-messages-virtual-intents) | `2023-05-23-14-09-08.png` | 3 pieces of information in a single app intent |
+| [Subsequent Messages - Virtual Intents](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/subsequent-messages-virtual-intents) | `2023-05-23-14-14-16.png` | Information the assistant shares with the user - no user interaction |
+| [Subsequent Messages - Virtual Intents](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/subsequent-messages-virtual-intents) | `2023-05-23-14-19-32.png` | App intent that uses a virtual intent |
+| [Subsequent Messages - Virtual Intents](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/subsequent-messages-virtual-intents) | `2023-05-23-14-21-42.png` | User intent |
+| [Using Attributes in Messages](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/using-attributes-in-messages) | `2023-05-01-16-43-02.png` | Edit Message screen |
+| [Using Attributes in Messages](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/using-attributes-in-messages) | `group-3-1.png` | The attribute input field can be accessed within the message editor section of the conversation designer |
+| [Using Markdown in messages](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/using-markdown-in-messages) | `image-571.png` | You can add your Markdown formatted content directly in the message editor |
+| [Text Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/text-message) | `screenshot-2024-06-04-at-10-14-39.png` | Example of a text message in action |
+| [Text Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/text-message) | `group-2-2.png` | Where to find the text block button |
+| [Text Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/text-message) | `group-3-1-1.png` | Where to find the custom messages button and XML for text messages |
+| [Image Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/image-message) | `screenshot-2024-06-04-at-10-18-10.png` | Example of an image block message |
+| [Image Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/image-message) | `group-4-1.png` | How to create an image message in the no-code image message block |
+| [Image Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/image-message) | `group-5-2.png` | How to create an image message in the custom message block |
+| [Button Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/button-message) | `group-6-1.png` | How to create a button message in the no-code button message block |
+| [Button Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/button-message) | `group-7-1-1.png` | How to create a button message in the custom message block |
+| [Date Picker Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/date-picker-message) | `screenshot-2024-06-04-at-10-31-07.png` | Users are prompted with a clickable input box. |
+| [Date Picker Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/date-picker-message) | `screenshot-2024-06-04-at-10-31-14.png` | When clicked, a calendar appears |
+| [Date Picker Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/date-picker-message) | `pick-a-time.png` | Pick a time |
+| [Date Picker Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/date-picker-message) | `pick-a-date-and-time.png` | Pick a date and time |
+| [Date Picker Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/date-picker-message) | `pick-a-year-and-month.png` | Pick a month and year |
+| [Date Picker Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/date-picker-message) | `pick-a-year.png` | Pick a year |
+| [Date Picker Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/date-picker-message) | `group-8-1.png` | How to create a date picker message in the custom message block |
+| [Audio Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/audio-message) | `screenshot-2024-06-04-at-10-38-15.png` | Audio messages can be played and paused using the play and pause button to the left and downloaded using the button to the right of each audio message directly within in the chat window. |
+| [Audio Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/audio-message) | `group-9.png` | How to create an audio message in the custom message block |
+| [Form Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/form-message) | `group-10-2.png` | How to create a form message in the no-code form message block |
+| [Form Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/form-message) | `image-590.png` | Deciding how to populate your form message dropdown |
+| [Form Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/form-message) | `image-592.png` | Adding static options to your FormMessage dropdown |
+| [Form Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/form-message) | `image-593.png` | Adding dynamic data to FormMessage dropdown |
+| [Form Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/form-message) | `image-596.png` | Searching a dropdown in a form message |
+| [Form Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/form-message) | `image-595.png` | Sorting your options alphabetically, including priority options |
+| [Form Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/form-message) | `group-11-1.png` | How to create a form message in the custom message block |
+| [Full Page Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/full-page-message) | `group-12.png` | How to create a full page rich message in the custom message editor |
+| [Full Page Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/full-page-message) | `group-13.png` | How to create a full page form message in the custom message editor |
+| [Conversation Handover message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/conversation-handover-message) | `group-14.png` | How to create a conversation handover message in the no code message editor |
+| [Conversation Handover message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/conversation-handover-message) | `group-15.png` | How to create a conversation handover message in the XML snippet |
+| [Autocomplete Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/autocomplete-message) | `group-1-1-1.png` | Where to find the custom messages button and XML for Autocomplete messages |
+| [Address Autocomplete Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/address-autocomplete-message) | `group-30.png` | How to create an address autocomplete message via a custom message |
+| [List Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/list-message) | `screenshot-2024-04-29-at-07-48-11.png` | Example of a list message |
+| [List Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/list-message) | `group-16.png` | How to create a list message via the custom message editor |
+| [Rich Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/rich-message) | `screenshot-2024-04-28-at-10-15-32.png` | Example of a rich message |
+| [Rich Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/rich-message) | `group-17.png` | How to create a rich message via the custom message editor |
+| [Location Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/location-message) | `screenshot-2024-06-04-at-11-07-11.png` | A user can click the button at the bottom to open a map |
+| [Location Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/location-message) | `screenshot-2024-06-04-at-11-08-49.png` | Example of the map view where a user can select their location |
+| [Location Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/location-message) | `location.png` | An example of a message when a user has submitted their location |
+| [Location Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/location-message) | `group-19.png` | How to create a location message in the custom message block |
+| [Location Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/location-message) | `image-529.png` | Creating an attribute of type attribute |
+| [E-Sign Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/e-sign-message) | `screenshot-2024-06-04-at-11-25-53.png` | Here is where the user can input their signature |
+| [E-Sign Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/e-sign-message) | `screenshot-2024-06-04-at-11-26-02.png` | An example of a user signature that's been inputted |
+| [E-Sign Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/e-sign-message) | `e-sign.png` | An example of a signature that has been submitted |
+| [E-Sign Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/e-sign-message) | `group-20.png` | How to create an e-sign message in the custom message block |
+| [File Upload Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/file-upload-message) | `screenshot-2024-06-04-at-11-03-22.png` | An example of a file upload message in use |
+| [File Upload Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/file-upload-message) | `group-18.png` | How to create a file upload message in the custom message block |
+| [Progress Bar Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/meta-messages/progress-bar-message) | `group-21.png` | How to create a progress bar message in the custom message block |
+| [Attribute Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/attribute-message) | `image-4-3.png` | How to create an attribute message in custom message block |
+| [Twilio Content Template Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/twilio-content-template-message) | `1000008688.jpg` | An example of Call to Action template |
+| [Twilio Content Template Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/twilio-content-template-message) | `1000008687.jpg` | An example of Quick Reply template |
+| [Twilio Content Template Message](https://docs.opendialog.ai/opendialog-platform/conversation-designer/message-design/message-types/twilio-content-template-message) | `image-577.png` | How to create Twilio Content Template Message in the custom message block |
+| [Webchat Interface Settings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/webchat-interface-design/webchat-interface-settings) | `image-583.png` | Save your settings changes using the save button |
+| [Webchat Interface Settings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/webchat-interface-design/webchat-interface-settings) | `image-578.png` | Security Settings tab |
+| [Webchat Interface Settings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/webchat-interface-design/webchat-interface-settings) | `image-579.png` | Anonymous Authentication |
+| [Webchat Interface Settings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/webchat-interface-design/webchat-interface-settings) | `image-581.png` | Cross Site Request Forgery Settings |
+| [Webchat Interface Settings](https://docs.opendialog.ai/opendialog-platform/conversation-designer/webchat-interface-design/webchat-interface-settings) | `image-582.png` | Cross Origin Resource Sharing Settings |
+| [Webchat Controls](https://docs.opendialog.ai/opendialog-platform/conversation-designer/webchat-interface-design/webchat-controls) | `group-7-1.png` | Where to find the minimise button - right top hand corner |
+| [Webchat Controls](https://docs.opendialog.ai/opendialog-platform/conversation-designer/webchat-interface-design/webchat-controls) | `group-5.png` | Where to find the main menu button - right top hand corner |
+| [Webchat Controls](https://docs.opendialog.ai/opendialog-platform/conversation-designer/webchat-interface-design/webchat-controls) | `screenshot-2024-04-25-at-22-56-32.png` | Example of the expanded main menu from within the header controls |
+| [Webchat Controls](https://docs.opendialog.ai/opendialog-platform/conversation-designer/webchat-interface-design/webchat-controls) | `group-8.png` | Where to find the speech to text button - bottom left hand corner |
+| [Webchat Controls](https://docs.opendialog.ai/opendialog-platform/conversation-designer/webchat-interface-design/webchat-controls) | `group-11.png` | Where to locate the CTA button |
+| [Semantic Intent Classifier](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier) | `screencapture-semantic-classifiers-cloud-dev1-engineering-opend…` | Providing additional prompt information will better support the operation of your language service |
+| [OpenAI](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/openai) | `screenshot-2024-07-08-at-18-05-09.png` | Setting up an OpenAI integration via OpenDialog |
+| [OpenAI](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/openai) | `screenshot-2024-07-08-at-18-21-46.png` | Use the "Create an LLM action" button to set up a new OpenAI integration |
+| [Azure](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/azure) | `screenshot-2024-07-08-at-18-05-09.png` | Setting up an OpenAI integration via OpenDialog |
+| [Azure](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/azure) | `screenshot-2024-07-08-at-18-21-46.png` | Use the "Create an LLM action" button to set up a new OpenAI integration |
+| [Google Gemini](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/google-gemini) | `screenshot-2024-07-08-at-18-05-09.png` | Setting up an OpenAI integration via OpenDialog |
+| [Google Gemini](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/google-gemini) | `screenshot-2024-07-08-at-18-21-46.png` | Use the "Create an LLM action" button to set up a new OpenAI integration |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `image-1-1-2.png` | Access the ability to add a RAG service via the Language Services feature |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `rag-settings-use.png` | Access the RAG service settings components via the left-hand menu |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `image-1-1-2-1.png` | The topics overview provides you with an overview of your different topics, and the ability to manage them |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `3.png` | Overview of the steps within OpenDialog to setup and use a RAG service |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `image-2-2-1.png` | From the Language Services dashboard, view your created RAG services or create a new one |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `image-3-2.png` | RAG service setup page |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `image-6-2.png` | Select the 'Add topic' button from the top right hand corner of your screen |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `image-5-2.png` | Provide a name, description to your topic and create it by clicking on the create topic button |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `select-source-type.png` | Add your information sources to a topic using the 'Add source' dropdown |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `url-2.png` | From the URL uploader modal you can start to add in your URL's in the 'URL Source' field |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `url-1.png` | Select URL from the topic source dropdown menu |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `url-3.png` | Here you have the option to input any exclusion ID's and Classes for your URL source(s) |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `url-4.png` | Click the 'Upload source' button to add your URL's to your topic |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `pic-2.png` | Select 'Document' from the topic source dropdown menu |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `pic-3.png` | The document upload modal |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `pic-4.png` | Once you're happy with your uploaded documents, click 'Upload source' |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `pic-5.png` | Once you have uploaded your document, you can see it in your topic sources table |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `rag-vectorisation.png` | Select your topic sources to start vectorisation |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `screenshot-2024-08-12-at-14-26-34.png` | Testing your knowledge service using the test panel |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `2-1-2.png` | Syntax structure of a knowledge string |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `rag-llmactions.png` | Using the AboutCompany RAG service in an LLM action |
+| [Retrieval Augmented Generation](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation) | `rag-response.png` | Reference your generated response via the output attribute |
+| [Interpreters](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters) | `2023-05-02-12-11-35.png` | Interpreters overview page |
+| [Interpreters](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters) | `2023-05-02-12-11-15.png` | Adding a new interpreter page |
+| [OpenAI interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/openai-interpreter) | `screenshot-2024-01-09-at-09-56-45.png` | The API keys screen in OpenAI. |
+| [OpenAI interpreter](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/openai-interpreter) | `screenshot-2024-01-09-at-09-58-23.png` | Creating an OpenAI interpreter in OpenDialog. |
+| [LLM Actions](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions) | `llmaction-setup-1.png` | Initial LLM Action set up, where you can choose a name, description, your preferred LLM engine and model |
+| [LLM Actions](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions) | `llmaction-basicprompt-config.png` | Configure a system prompt that can be sent as instructions to the LLM |
+| [LLM Actions](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions) | `llmaction-basicprompt-config-with-attributes.png` | A prompt containing attributes |
+| [LLM Actions](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions) | `llmactions-advancedsettings.png` | Configure your LLM action in more detail using advanced settings |
+| [LLM Actions](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions) | `llmactions-attributesforreuse-1.png` | Specify attributes and use them within message design |
+| [LLM Actions](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions) | `llmactions-attributesforreuse-2-in-messages.png` | Add attributes in messages, and use an LLM to continue the conversation |
+| [LLM Actions](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions) | `llmactions-safeguarding.png` | Create safer LLM actions using OpenDialogs safeguarding tools and features |
+| [LLM Actions](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions) | `llmactions-testpanel.png` | The test panel will display what is sent to the LLM (Inputs), and what in turn is received from the LLM in return (Outputs) |
+| [LLM Actions](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions) | `image-618.png` | Files selected, but not uploaded |
+| [LLM Actions](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions) | `image-619.png` | 2 files uploaded and ready to go |
+| [LLM Actions](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions) | `llmactions-testpanel.png` | When an LLM test is run, all outputs will be shown in the 'Outputs' section in the test panel window |
+| [OpenAI](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/openai) | `screenshot-2024-07-08-at-18-05-09.png` | Setting up an OpenAI integration via OpenDialog |
+| [OpenAI](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/openai) | `screenshot-2024-07-08-at-18-21-46.png` | Use the "Create an LLM action" button to set up a new OpenAI integration |
+| [OpenAI](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/openai) | `screenshot-2024-07-08-at-18-25-21.png` | Select the desired intent in the designer and click "Add conditions, actions & attributes" to reveal the Action section |
+| [OpenAI](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/openai) | `screenshot-2024-07-09-at-09-52-58-1.png` | Create a text message using the LLM's response by using the 6 attribute |
+| [Azure OpenAI](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/azure-openai) | `screenshot-2024-07-08-at-18-30-02.png` | Setting up an Azure OpenAI integration via OpenDialog |
+| [Azure OpenAI](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/azure-openai) | `screenshot-2024-07-08-at-18-21-46.png` | Use the "Create an LLM action" button to set up a new Azure OpenAI integration |
+| [Azure OpenAI](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/azure-openai) | `screenshot-2024-07-08-at-18-25-21.png` | Select the desired intent in the designer and click "Add conditions, actions & attributes" to reveal the Action section |
+| [Azure OpenAI](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/azure-openai) | `screenshot-2024-07-09-at-09-52-58.png` | Create a text message using the LLM's response by using the 4 attribute |
+| [LLM Action Analytics](https://docs.opendialog.ai/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/llm-action-analytics) | `image-530.png` | Aggregate and Detail LLM Action log data |
+| [3rd party Integrations in your application](https://docs.opendialog.ai/opendialog-platform/actions) | `2023-05-02-15-28-26.png` | Edit or create action page |
+| [3rd party Integrations in your application](https://docs.opendialog.ai/opendialog-platform/actions) | `2023-05-02-15-33-04.png` | Add Action in the Advanced Settings |
+| [3rd party Integrations in your application](https://docs.opendialog.ai/opendialog-platform/actions) | `2023-05-02-15-32-45.png` | Adding an action to an intent |
+| [Webhook action](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action) | `image-2-1.png` | New webhook page |
+| [Webhook action](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action) | `image-3.png` | Example of basic configurations of webhook action |
+| [Webhook action](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action) | `image-4.png` | Example of headers configuration of webhook action |
+| [Webhook action](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action) | `image-5.png` | Example of payload configuration for webhook action |
+| [Webhook action](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action) | `image-601.png` | Example of response configuration for webhook action |
+| [Webhook action](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action) | `image-602.png` | Use testing panel on the left to run a test for your webhook |
+| [Using JMESPath expressions](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action/using-jmespath-expressions) | `image-611.png` | Example of using JMESPath expression in your output attributes mapping |
+| [[Deprecated] webhook actions](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action/webhook-action) | `image-535.png` | A webhook action |
+| [[Deprecated] webhook actions](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action/webhook-action) | `image-537.png` | Testing a webhook action |
+| [[Deprecated] webhook actions](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action/webhook-action) | `image-538.png` | Activating an action. |
+| [[Deprecated] webhook actions](https://docs.opendialog.ai/opendialog-platform/actions/webhook-action/webhook-action) | `image-539.png` | Adding an action to an intent. |
+| [Freshdesk Action](https://docs.opendialog.ai/opendialog-platform/actions/actions-from-library/freshdesk-action) | `screenshot-2023-05-31-at-16-18-00.png` | Select the action library to add pre-defined actions like the Freshdesk action |
+| [Freshdesk Action](https://docs.opendialog.ai/opendialog-platform/actions/actions-from-library/freshdesk-action) | `screenshot-2023-06-01-at-10-05-01.png` | Freshdesk action setup in the central pane, guidance and action testing in the right-hand pane. |
+| [Freshdesk Action](https://docs.opendialog.ai/opendialog-platform/actions/actions-from-library/freshdesk-action) | `image-597.png` | Test your action using test action pane |
+| [Freshdesk Action](https://docs.opendialog.ai/opendialog-platform/actions/actions-from-library/freshdesk-action) | `screenshot-2023-06-02-at-10-02-49.png` | Activate your action to use it in your scenario |
+| [Send to Email Action](https://docs.opendialog.ai/opendialog-platform/actions/actions-from-library/send-to-email-action) | `screenshot-2023-05-31-at-16-18-00.png` | Select the action library to add pre-defined actions like the send to email action |
+| [Send to Email Action](https://docs.opendialog.ai/opendialog-platform/actions/actions-from-library/send-to-email-action) | `2023-11-10-14-20-10.png` | Send to email action |
+| [Send to Email Action](https://docs.opendialog.ai/opendialog-platform/actions/actions-from-library/send-to-email-action) | `2023-11-10-14-24-27.png` | Send to email details |
+| [Send to Email Action](https://docs.opendialog.ai/opendialog-platform/actions/actions-from-library/send-to-email-action) | `2023-11-10-14-27-21.png` | Activate the action |
+| [Send to Email Action](https://docs.opendialog.ai/opendialog-platform/actions/actions-from-library/send-to-email-action) | `2023-11-10-14-29-11.png` | Add conditions, actions and attributes |
+| [Send to Email Action](https://docs.opendialog.ai/opendialog-platform/actions/actions-from-library/send-to-email-action) | `2023-11-10-14-29-36.png` | Select the action from the dropdown list |
+| [Conversation Hand-off](https://docs.opendialog.ai/opendialog-platform/actions/conversation-hand-off) | `chatwoot-handover.png` | Setting up a Chatwoot integration via OpenDialog |
+| [Chatwoot](https://docs.opendialog.ai/opendialog-platform/actions/conversation-hand-off/chatwoot) | `chatwoot-handover.png` | Setting up a Chatwoot integration via OpenDialog |
+| [Chatwoot](https://docs.opendialog.ai/opendialog-platform/actions/conversation-hand-off/chatwoot) | `screenshot-2023-07-28-at-16-26-42.png` | Use the Create new Handoff button to set up a new Handoff integration |
+| [Chatwoot](https://docs.opendialog.ai/opendialog-platform/actions/conversation-hand-off/chatwoot) | `screenshot-2023-10-25-at-12-13-26.png` | Update your Chatwoot inbox Webhook URL to be able to receive messages |
+| [Previewing your application](https://docs.opendialog.ai/opendialog-platform/previewing-your-application) | `preview-sidebar.jpg` | Default conversation design view |
+| [Previewing your application](https://docs.opendialog.ai/opendialog-platform/previewing-your-application) | `preview-main-1.jpg` | Preview screen |
+| [Previewing your application](https://docs.opendialog.ai/opendialog-platform/previewing-your-application) | `preview-considered-path.jpg` | Considered Path |
+| [Previewing your application](https://docs.opendialog.ai/opendialog-platform/previewing-your-application) | `preview-selected-path.jpg` | Selected Path |
+| [Launching your application](https://docs.opendialog.ai/opendialog-platform/launching-your-application) | `2023-05-02-09-13-40.png` | Interface settings screen with open embed code window |
+| [Launching your application](https://docs.opendialog.ai/opendialog-platform/launching-your-application) | `screenshot-2023-05-26-111039.png` | The Alias creation UI |
+| [Monitoring your application](https://docs.opendialog.ai/opendialog-platform/monitoring-your-application) | `screenshot-2024-09-26-at-10-28-52.png` | The OpenDialog Analyse dashboard gives you an overview of the latest interactions with your application and a bird-eye overview of project usage over time. |
+| [Monitoring your application](https://docs.opendialog.ai/opendialog-platform/monitoring-your-application) | `group-2-3.png` | You can find Analyse, in the Test section of your scenario menu. |
+| [Monitoring your application](https://docs.opendialog.ai/opendialog-platform/monitoring-your-application) | `screenshot-2024-09-26-at-10-32-32.png` | Expanded view of project use over the course of a week |
+| [Monitoring your application](https://docs.opendialog.ai/opendialog-platform/monitoring-your-application) | `screenshot-2024-10-01-at-15-31-13.png` | List of interaction logs |
+| [Monitoring your application](https://docs.opendialog.ai/opendialog-platform/monitoring-your-application) | `screenshot-2024-10-01-at-15-31-33.png` | List of message logs |
+| [Monitoring your application](https://docs.opendialog.ai/opendialog-platform/monitoring-your-application) | `screenshot-2024-10-01-at-15-32-22.png` | By using the breadcrumb filter, you can narrow down you search by conversation, scene, turn and intent |
+| [Monitoring your application](https://docs.opendialog.ai/opendialog-platform/monitoring-your-application) | `created.png` | Detailed conversation log, including user information, conversational history, conversational flow visualization, and conversational logic. |
+| [Translating your application](https://docs.opendialog.ai/opendialog-platform/translating-your-application) | `translate-languageselection.png` | OpenDialog Translate lets you auto-translate and share your content strings as a spreadsheet with your translators. |
+| [Translating your application](https://docs.opendialog.ai/opendialog-platform/translating-your-application) | `screenshot-2023-05-11-at-14-33-04.png` | The Translate dashboard can be accessed via the main scenario menu. |
+| [Translating your application](https://docs.opendialog.ai/opendialog-platform/translating-your-application) | `screenshot-2023-05-11-at-13-01-33.png` | Export your content strings for translation directly from the Scenario Overview page |
+| [Translating your application](https://docs.opendialog.ai/opendialog-platform/translating-your-application) | `screenshot-2023-05-11-at-13-11-46.png` | Use the 'Export scenario' button to start the Translate process. |
+| [Translating your application](https://docs.opendialog.ai/opendialog-platform/translating-your-application) | `screenshot-2023-05-11-at-13-12-57.png` | The export scenario for translation modal allows you to activate an automated translation service. |
+| [Translating your application](https://docs.opendialog.ai/opendialog-platform/translating-your-application) | `screenshot-2023-05-11-at-18-20-26.png` | .csv file after export |
+| [Translating your application](https://docs.opendialog.ai/opendialog-platform/translating-your-application) | `screenshot-2023-05-11-at-14-52-54.png` | The language cards in the 'Your translations' sections reflect the status of the completeness of your translations. |
+| [Translating your application](https://docs.opendialog.ai/opendialog-platform/translating-your-application) | `screenshot-2023-05-11-at-14-54-32.png` | Preview set to English for this scenario by default |
+| [Translating your application](https://docs.opendialog.ai/opendialog-platform/translating-your-application) | `screenshot-2023-05-11-at-14-54-46.png` | The same scenario with Preview set to French |
+| [[Legacy] External APIs](https://docs.opendialog.ai/developing-with-opendialog/interaction-api) | `2022-09-21-16-47-08.png` | API Bearer Token Access |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `image-4-1.png` | Capacity tracker for vectorisation quotas |
+| [Release Notes](https://docs.opendialog.ai/release-notes/release-notes) | `new-waiting-time-1.gif` | OpenDialog's interactive wait time indicator |
diff --git a/reports/inherited-broken-links.json b/reports/inherited-broken-links.json
new file mode 100644
index 0000000..dcdf607
--- /dev/null
+++ b/reports/inherited-broken-links.json
@@ -0,0 +1,32 @@
+{
+ "note": "Content defects inherited from GitBook, present in source/ and broken on GitBook too. The no-editing-prose rule forbids fixing them here; they are logged in MIGRATION-NOTES.md for the docs team. verify-links.mjs treats these as known, fails on anything new, and fails on any entry that is no longer broken so the list cannot rot.",
+ "links": [
+ { "from": "/", "href": "/broken/pages/2lcI5UfFruOL0M8VSp3d" },
+ { "from": "/", "href": "/broken/pages/EVpERlszmNSb5PDKaprI" },
+ { "from": "/", "href": "/broken/pages/-M_drTg0DF70xMVqRlyG" },
+ { "from": "/core-concepts/the-opendialog-workspace", "href": "/broken/pages/QXiLofFtrSva3tSBJilT" },
+ { "from": "/release-notes/release-notes", "href": "/broken/pages/Yh2t7P90PzNprbtTVwtP" },
+ { "from": "/release-notes/release-notes", "href": "/broken/pages/-MQM33QbO3LxSgzz40Lm" },
+ { "from": "/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions", "href": "/broken/pages/h1Nv4EMKFW0n10de3P6a" },
+ { "from": "/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/recommendations", "href": "/broken/pages/EMMG991zfA7rFesrsyIP" },
+ { "from": "/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/openai-interpreter", "href": "/broken/pages/ctW05MISDAG5zCohAvji" }
+ ],
+ "anchors": [
+ "/opendialog-platform/monitoring-your-application#message-table",
+ "/opendialog-platform/conversation-designer/message-design/using-attributes-in-messages#available-filters",
+ "/opendialog-platform/conversation-designer/message-design/message-editor#message-types",
+ "/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier#attributes-and-values",
+ "/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions#user-utterance-response-exclusion-list",
+ "/core-concepts/contexts-and-attributes/about-attributes#multiple-value-attribute-types-collections-and-composites",
+ "/opendialog-platform/conversation-designer/message-design/message-types/address-autocomplete-message#properties",
+ "/opendialog-platform/conversation-designer/message-design/message-types/attribute-message#what-is-a-list-message-3",
+ "/opendialog-platform/conversation-designer/message-design/message-types/button-message#properties",
+ "/opendialog-platform/conversation-designer/message-design/message-types/conversation-handover-message#properties",
+ "/opendialog-platform/conversation-designer/message-design/message-types/date-picker-message#when-to-use-date-picker-messages",
+ "/opendialog-platform/conversation-designer/message-design/message-types/e-sign-message#properties",
+ "/opendialog-platform/conversation-designer/message-design/message-types/form-message#properties",
+ "/opendialog-platform/conversation-designer/message-design/message-types/full-page-message#properties",
+ "/opendialog-platform/conversation-designer/message-design/message-types/location-message#properties",
+ "/opendialog-platform/conversation-designer/message-design/message-types/rich-message#via-the-no-code-text-message-in-message-editor"
+ ]
+}
diff --git a/scripts/assets.mjs b/scripts/assets.mjs
new file mode 100644
index 0000000..694de6c
--- /dev/null
+++ b/scripts/assets.mjs
@@ -0,0 +1,292 @@
+/**
+ * Copies and encodes the referenced GitBook assets into src/assets/ and public/, slugified, and
+ * records what each became in asset-map.json.
+ *
+ * Still images are resized to a width ceiling and, below a colour-count threshold,
+ * palette-quantised; the source format is always preserved, since a `.jpg` file holding PNG bytes
+ * is a content/extension mismatch. A GIF at or above GIF_VIDEO_THRESHOLD is re-encoded to MP4;
+ * smaller GIFs and other files are copied unchanged. A content-hash cache skips re-encoding an
+ * asset whose bytes have not changed since the last run.
+ *
+ * The copy set is derived from source/ alone — never from src/content/docs — because
+ * convert.mjs consumes this map to emit its paths and would otherwise need itself first.
+ *
+ * Reproducible: output paths derive from sorted filenames, sharp's encoders are deterministic for
+ * fixed parameters, ffmpeg is run with bitexact flags so it is too, and the cache keys on content
+ * hash rather than mtime, so a run against the same source/ tree always produces byte-identical
+ * files and an identical asset-map.json.
+ */
+import { execFileSync } from 'node:child_process';
+import { createHash } from 'node:crypto';
+import { existsSync, mkdirSync, readFileSync, readdirSync, rmSync, statSync, writeFileSync } from 'node:fs';
+import { dirname, join, resolve } from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+import sharp from 'sharp';
+
+import { assetRefsInFile } from './lib/asset-refs.mjs';
+import { assignSlugs, planAsset, slugify, MAX_WIDTH, QUANTISE_MAX_COLOURS } from './lib/asset-plan.mjs';
+
+const root = resolve(dirname(fileURLToPath(import.meta.url)), '..');
+const SOURCE_ASSETS = `${root}/source/.gitbook/assets`;
+const MAP = `${root}/asset-map.json`;
+
+const DESTINATIONS = {
+ 'src/assets': { dir: `${root}/src/assets`, reference: (slug) => `~/assets/${slug}` },
+ 'public/media': { dir: `${root}/public/media`, reference: (slug) => `/media/${slug}` },
+ 'public/files': { dir: `${root}/public/files`, reference: (slug) => `/files/${slug}` },
+};
+
+/** kind has always determined destination one-to-one (see planAsset), so an older map entry
+ * written before the `destination` field existed can still be placed correctly. */
+const DESTINATION_FOR_KIND = { image: 'src/assets', video: 'public/media', file: 'public/files' };
+
+const walk = (dir) =>
+ readdirSync(dir, { withFileTypes: true }).flatMap((entry) =>
+ entry.isDirectory() ? walk(join(dir, entry.name)) : [join(dir, entry.name)]
+ );
+
+const STILL_IMAGE = /\.(?:png|jpe?g|webp)$/i;
+const PNG = /\.png$/i;
+const JPEG = /\.jpe?g$/i;
+const WEBP = /\.webp$/i;
+
+/** Resizes a still image to the width ceiling, re-encoding it in its own source format so the
+ * output extension always matches its content. Never enlarges. */
+async function resizeImage(buffer, name) {
+ const pipeline = sharp(buffer).resize({ width: MAX_WIDTH, withoutEnlargement: true });
+ if (JPEG.test(name)) return pipeline.jpeg({ quality: 90 }).toBuffer();
+ if (WEBP.test(name)) return pipeline.webp().toBuffer();
+ return pipeline.png({ compressionLevel: 9 }).toBuffer();
+}
+
+/**
+ * Unique RGB values in a decoded image, stopping once the quantisation threshold is exceeded.
+ *
+ * Must be called on the RESIZED image, never the original and never a downsample: unique colours
+ * scale with pixel count, so a threshold calibrated on a smaller image admits far more files than
+ * intended. An earlier draft of the design measured at 400px and projected 84.6 MiB against a
+ * 60 MB gate.
+ *
+ * Asserts on the channel count rather than computing a meaningless result: a greyscale decode has
+ * one channel, and reading three components per pixel while stepping by one would read across
+ * pixel boundaries.
+ */
+async function countColours(buffer) {
+ const { data, info } = await sharp(buffer).raw().toBuffer({ resolveWithObject: true });
+ if (info.channels < 3) {
+ throw new Error(`countColours: need at least 3 channels (RGB) to count colours, got ${info.channels}`);
+ }
+ const seen = new Set();
+ for (let i = 0; i < data.length; i += info.channels) {
+ seen.add((data[i] << 16) | (data[i + 1] << 8) | data[i + 2]);
+ if (seen.size > QUANTISE_MAX_COLOURS) return seen.size;
+ }
+ return seen.size;
+}
+
+/**
+ * Re-encodes an animated GIF to MP4, reading straight from source/ since ffmpeg takes a path
+ * rather than a buffer.
+ *
+ * -movflags +faststart puts the index first so the browser can start playing before the file has
+ * fully downloaded. yuv420p and the even-dimension scale filter are what Safari requires.
+ *
+ * -flags:v +bitexact and -map_metadata -1, together with the fixed encode parameters below and a
+ * pinned ffmpeg version, strip encoder version strings, timestamps and other metadata libx264/the
+ * MP4 muxer would otherwise embed, which would otherwise make two encodes of the same input differ
+ * byte-for-byte and break the content-hash cache's guarantee that the same source/ tree always
+ * produces identical output.
+ */
+function encodeVideo(from, to) {
+ execFileSync('ffmpeg', [
+ '-y', '-loglevel', 'error',
+ '-i', from,
+ '-movflags', '+faststart',
+ '-pix_fmt', 'yuv420p',
+ '-vf', 'scale=trunc(iw/2)*2:trunc(ih/2)*2',
+ '-c:v', 'libx264', '-crf', '23', '-preset', 'slow', '-an',
+ '-flags:v', '+bitexact',
+ '-map_metadata', '-1',
+ to,
+ ]);
+}
+
+/**
+ * Palette-quantises a resized PNG, keeping the result only when it is actually smaller.
+ *
+ * Palette is a PNG concept. This must only ever be called with a PNG buffer — calling it on a
+ * JPEG or WebP source would silently rewrite the file to PNG bytes under an unchanged extension.
+ */
+async function quantise(resized) {
+ const quantised = await sharp(resized).png({ palette: true, compressionLevel: 9 }).toBuffer();
+ return quantised.length < resized.length ? quantised : resized;
+}
+
+/**
+ * The assets convert.mjs will reference: everything in source/, covers included.
+ *
+ * Covers were subtracted here while <LinkCard> had no image slot and conversion discarded
+ * them, so copying them would have shipped images nothing rendered. src/components/
+ * CoverCard.astro now renders them, so they are referenced again and must be copied. The
+ * cover hrefs are still counted, because that count is an invariant of its own.
+ */
+function copySet() {
+ const names = new Set();
+ let coverHrefs = 0;
+ const files = walk(`${root}/source`).filter((f) => /\.mdx?$/.test(f)).sort();
+ for (const file of files) {
+ const { all: refs, covers } = assetRefsInFile(readFileSync(file, 'utf8'));
+ coverHrefs += covers.length;
+ for (const name of refs) names.add(name);
+ }
+ const all = new Set(names);
+ const copy = [...all].sort();
+ return { all, copy, coverHrefs };
+}
+
+const { all, copy, coverHrefs } = copySet();
+
+const missing = [...all].filter((name) => !existsSync(join(SOURCE_ASSETS, name))).sort();
+if (missing.length) {
+ throw new Error(`referenced assets absent from source/.gitbook/assets: ${missing.join(', ')}`);
+}
+
+const slugs = assignSlugs(copy);
+const collisions = copy.filter((name) => slugs.get(name) !== slugify(name)).length;
+
+for (const { dir } of Object.values(DESTINATIONS)) mkdirSync(dir, { recursive: true });
+
+const previous = existsSync(MAP) ? JSON.parse(readFileSync(MAP, 'utf8')).assets : {};
+let encoded = 0;
+let reused = 0;
+
+const assets = {};
+for (const name of [...copy].sort()) {
+ const from = join(SOURCE_ASSETS, name);
+ const source = readFileSync(from);
+ const hash = createHash('sha256').update(source).digest('hex');
+ const slug = slugs.get(name);
+ const still = STILL_IMAGE.test(name);
+
+ // A still image's plan needs a colour count, which needs the resize. Everything else can be
+ // planned immediately, and only those can change extension.
+ const early = still ? null : planAsset({ filename: name, bytes: source.length, colours: null });
+ const finalSlug = early?.treatment === 'encode-video' ? slug.replace(/\.gif$/i, '.mp4') : slug;
+
+ // The cache keys on content hash, slug and destination only — it does not, and cannot, key on
+ // MAX_WIDTH, QUANTISE_MAX_COLOURS or GIF_VIDEO_THRESHOLD. Changing one of those constants and
+ // re-running still hits this cache for every unchanged source file, so the new value silently
+ // never takes effect: delete asset-map.json before the next run whenever an encode constant
+ // changes.
+ const cached = previous[name];
+ if (
+ cached &&
+ cached.hash === hash &&
+ cached.slug === finalSlug &&
+ cached.destination in DESTINATIONS &&
+ existsSync(join(DESTINATIONS[cached.destination].dir, cached.slug))
+ ) {
+ assets[name] = cached;
+ reused++;
+ continue;
+ }
+
+ let plan = early;
+ let output = source;
+ if (still) {
+ const resized = await resizeImage(source, name);
+ plan = planAsset({ filename: name, bytes: source.length, colours: await countColours(resized) });
+ output = plan.treatment === 'resize-quantise' && PNG.test(name) ? await quantise(resized) : resized;
+ if (output.length > source.length) output = source;
+ }
+
+ const destination = DESTINATIONS[plan.destination];
+ const target = join(destination.dir, finalSlug);
+ if (plan.treatment === 'encode-video') encodeVideo(from, target);
+ else writeFileSync(target, output);
+ encoded++;
+
+ assets[name] = {
+ slug: finalSlug,
+ kind: plan.kind,
+ destination: plan.destination,
+ reference: destination.reference(finalSlug),
+ hash,
+ };
+}
+
+/**
+ * Removes what a prior run wrote for an asset that no longer exists in this run's copy set.
+ *
+ * Driven by the previous map's entries, never by listing the destination directories: those
+ * directories are not script-owned (src/assets holds the site logo, unrelated to any asset entry)
+ * and a listing-based sweep would delete anything it does not recognise, logo included. The map
+ * is the only record of what this script has ever written, so it is the only safe source for
+ * what this script may delete.
+ *
+ * Keyed on the (destination, slug) pair, not the slug alone: the same slug can move destination
+ * between runs (a GIF crossing GIF_VIDEO_THRESHOLD keeps its filename but switches between
+ * src/assets and public/media), and a slug claimed in its new destination must not be read as
+ * covering the stale copy left behind in its old one.
+ *
+ * An entry that predates the `destination` field is placed via DESTINATION_FOR_KIND rather than
+ * skipped: kind has always determined destination one-to-one, so the derivation is exact, not a
+ * guess, and skipping such entries would let their stale files sit unswept forever.
+ */
+const destinationKeyFor = (asset) => asset.destination ?? DESTINATION_FOR_KIND[asset.kind];
+const claimed = new Set(Object.values(assets).map((asset) => `${destinationKeyFor(asset)}/${asset.slug}`));
+for (const asset of Object.values(previous)) {
+ const destinationKey = destinationKeyFor(asset);
+ if (claimed.has(`${destinationKey}/${asset.slug}`)) continue;
+ rmSync(join(DESTINATIONS[destinationKey].dir, asset.slug), { force: true });
+}
+
+writeFileSync(MAP, `${JSON.stringify({ generated: 'scripts/assets.mjs', assets }, null, 2)}\n`);
+
+const bytesIn = (dir) =>
+ existsSync(dir) ? walk(dir).reduce((total, f) => total + statSync(f).size, 0) : 0;
+const MIB = 1024 * 1024;
+const srcAssets = bytesIn(DESTINATIONS['src/assets'].dir);
+const largest = walk(DESTINATIONS['src/assets'].dir)
+ .concat(walk(DESTINATIONS['public/media'].dir), walk(DESTINATIONS['public/files'].dir))
+ .reduce((max, f) => Math.max(max, statSync(f).size), 0);
+
+const EXPECTED = {
+ references: 509,
+ coverHrefs: 13,
+ // 509, not 500: the 9 covers referenced nowhere else are copied again now that
+ // CoverCard renders them. Four are photographic PNGs the pipeline preserves as PNG,
+ // which is what takes src/assets from 32.0 to 48.4 MiB against the 60 MB gate.
+ copySet: 509,
+ mapEntries: 509,
+ slugCollisions: 0,
+};
+const stats = {
+ references: all.size,
+ coverHrefs,
+ copySet: copy.length,
+ mapEntries: Object.keys(assets).length,
+ slugCollisions: collisions,
+};
+
+let failed = false;
+for (const [key, expected] of Object.entries(EXPECTED)) {
+ const ok = stats[key] === expected;
+ if (!ok) failed = true;
+ console.log(`${ok ? 'ok ' : 'FAIL'} ${key.padEnd(18)} ${stats[key]}${ok ? '' : ` (expected ${expected})`}`);
+}
+const underGate = srcAssets < 60_000_000;
+const underCap = largest < 25 * MIB;
+console.log(`${underGate ? 'ok ' : 'FAIL'} ${'src/assets size'.padEnd(18)} ${(srcAssets / MIB).toFixed(1)} MiB`);
+console.log(`${underCap ? 'ok ' : 'FAIL'} ${'largest file'.padEnd(18)} ${(largest / MIB).toFixed(1)} MiB`);
+if (!underGate || !underCap) failed = true;
+
+console.log(` ${'encoded'.padEnd(18)} ${encoded}`);
+console.log(` ${'reused from cache'.padEnd(18)} ${reused}`);
+
+console.log(`\nwrote ${Object.keys(assets).length} assets and asset-map.json`);
+if (failed) {
+ console.error('\nA count diverged. The script is wrong — do not adjust the expectation.');
+ process.exit(1);
+}
diff --git a/scripts/convert.mjs b/scripts/convert.mjs
index a945891..0e15bc7 100644
--- a/scripts/convert.mjs
+++ b/scripts/convert.mjs
@@ -9,11 +9,12 @@
* non-zero on any divergence, in the same spirit as routes.mjs checking itself against the
* live sitemap snapshot.
*/
-import { mkdirSync, readFileSync, rmSync, writeFileSync } from 'node:fs';
+import { existsSync, mkdirSync, readFileSync, rmSync, writeFileSync } from 'node:fs';
import { dirname, resolve } from 'node:path';
import { fileURLToPath } from 'node:url';
import { emitFrontmatter, parseFrontmatter, takeTitle } from './lib/frontmatter.mjs';
+import { convertEmoji, countEmoji, countUnknownShortcodes } from './lib/emoji.mjs';
import { convertFigures, reflowImageDiv, rewriteAssetRefs } from './lib/figures.mjs';
import {
convertCode,
@@ -35,6 +36,10 @@ const OUT = `${root}/src/content/docs`;
const routeMap = JSON.parse(readFileSync(`${root}/route-map.json`, 'utf8'));
const routes = new Map(routeMap.map((r) => [r.source, r]));
+const assetMap = existsSync(`${root}/asset-map.json`)
+ ? JSON.parse(readFileSync(`${root}/asset-map.json`, 'utf8')).assets
+ : null;
+
/** Counts occurrences of `pattern` in prose only, ignoring anything inside a fenced block. */
function countInProse(text, pattern) {
const prose = [];
@@ -45,8 +50,8 @@ function countInProse(text, pattern) {
return (prose.join('\n').match(pattern) || []).length;
}
-/** Matches one <LinkCard ...> or <Card ...> element, never <CardGrid>. */
-const CARD_ELEMENT = /<(?:LinkCard|Card)(?=[ >])/g;
+/** Matches one <LinkCard>, <CoverCard> or <Card> element, never <CardGrid>. */
+const CARD_ELEMENT = /<(?:LinkCard|CoverCard|Card)(?=[ >])/g;
/** Counts <LinkCard>/<Card> elements present in `text`, for measuring what each pass added. */
function countCards(text) {
@@ -115,11 +120,15 @@ const stats = {
steps: 0,
cardGrids: 0,
images: 0,
- droppedCovers: 0,
+ emoji: 0,
+ covers: 0,
survivingBlocks: 0,
survivingEntities: 0,
survivingImgTags: 0,
survivingBraces: 0,
+ survivingShortcodes: 0,
+ assetRefs: 0,
+ survivingAssetPaths: 0,
};
const COMPONENTS = [
@@ -135,14 +144,21 @@ for (const route of routeMap) {
const raw = readFileSync(`${root}/source/${route.source}`, 'utf8');
const { data, body } = parseFrontmatter(raw);
const meta = titles.get(route.source);
- const ctx = { source: route.source, routes, titles };
+ const ctx = { source: route.source, routes, titles, assets: assetMap };
- stats.droppedCovers += countDroppedCovers(body);
+ stats.covers += countDroppedCovers(body);
let text = takeTitle(body).body;
+
+ // Before anything escapes underscores on the way to MDX, so shortcodes are still in the
+ // plain form GitBook wrote.
+ stats.emoji += countEmoji(text);
+ text = convertEmoji(text);
+ stats.survivingShortcodes += countUnknownShortcodes(text);
+
text = convertCode(text);
text = convertHints(text);
- text = convertFile(text);
+ text = convertFile(text, ctx);
const beforeContentRef = countCards(text);
text = convertContentRefs(text, ctx);
@@ -152,25 +168,30 @@ for (const route of routeMap) {
text = convertCardTables(text, ctx);
stats.cardTableCards += countCards(text) - beforeCardTable;
- text = convertEmbeds(text);
text = convertSteppers(text);
text = convertColumns(text);
text = reflowImageDiv(text);
- text = convertFigures(text);
- text = rewriteAssetRefs(text);
+ text = convertFigures(text, ctx);
+ text = rewriteAssetRefs(text, ctx);
+ // After the figure passes: an embed emits a <figure class="od-embed"> wrapping a
+ // <div>, and both reflowImageDiv and convertFigures reject markup of that shape rather
+ // than degrading it. Neither pass has anything to do with an embed.
+ text = convertEmbeds(text);
text = stripEntities(text);
text = rewriteLinks(text, ctx);
const used = COMPONENTS.filter(([marker]) => text.includes(marker)).map(([, name]) => name);
- const hasEmbed = text.includes('<Embed ');
- const isMdx = used.length > 0 || hasEmbed;
+ const hasCoverCard = text.includes('<CoverCard ');
+ const isMdx = used.length > 0 || hasCoverCard;
if (isMdx) {
text = unwrapPreCode(text);
text = normaliseForMdx(text);
const imports = [];
- if (used.length) imports.push(`import { ${[...new Set(used)].sort().join(', ')} } from '@astrojs/starlight/components';`);
- if (hasEmbed) imports.push("import Embed from '~/components/Embed.astro';");
+ if (used.length) {
+ imports.push(`import { ${[...new Set(used)].sort().join(', ')} } from '@astrojs/starlight/components';`);
+ }
+ if (hasCoverCard) imports.push("import CoverCard from '~/components/CoverCard.astro';");
text = `\n${imports.join('\n')}\n${text}`;
}
@@ -182,7 +203,8 @@ for (const route of routeMap) {
stats.files++;
if (isMdx) stats.mdx++;
stats.asides += (output.match(/^:::(note|tip|caution|danger)/gm) || []).length;
- stats.embeds += (output.match(/<Embed /g) || []).length;
+ // Either spelling: normaliseForMdx rewrites class to className on .mdx pages.
+ stats.embeds += (output.match(/<figure class(?:Name)?="od-embed">/g) || []).length;
stats.cardGrids += (output.match(/<CardGrid>/g) || []).length;
stats.steps += (output.match(/^\d+\. /gm) || []).length;
stats.images += (output.match(/!\[/g) || []).length;
@@ -191,24 +213,62 @@ for (const route of routeMap) {
stats.survivingEntities += countInProse(output, / /g);
stats.survivingImgTags += countInProse(output, /<img/g);
if (isMdx) stats.survivingBraces += countUnescapedBraces(output);
+
+ stats.assetRefs += (output.match(/~\/assets\/[^\s)>"]+/g) || []).length;
+ for (const [, ref] of output.matchAll(/~\/assets\/([^\s)>"]+)/g)) {
+ if (!existsSync(`${root}/src/assets/${ref}`)) {
+ throw new Error(`${route.source}: emitted asset does not exist: src/assets/${ref}`);
+ }
+ }
+ // Matches both a quoted attribute (<video src="/media/…">) and a markdown-link destination
+ // ([name](/files/…)), in one pass so a reference cannot be counted under both alternatives.
+ for (const match of output.matchAll(/"\/(media|files)\/([^"]+)"|\(<?\/(media|files)\/([^)>]+)>?\)/g)) {
+ const dir = match[1] ?? match[3];
+ const ref = match[2] ?? match[4];
+ stats.assetRefs++;
+ if (!existsSync(`${root}/public/${dir}/${ref}`)) {
+ throw new Error(`${route.source}: emitted asset does not exist: public/${dir}/${ref}`);
+ }
+ }
+
+ // Every asset target rewritten above resolves through asset-map.json. Nothing rewrites a plain
+ // markdown *link* to a .gitbook/assets path — extractTargets/rewriteLinks treats it as a page
+ // link and skips it, rewriteAssetRefs and convertFigures only match image syntax — so this is
+ // the one shape that would ship a dead relative path with astro build still green. Asserted
+ // only when assetMap is non-null: in the no-map fallback every reference is deliberately still
+ // a /.gitbook/assets/ placeholder (see assetPath in figures.mjs), so this would always fail.
+ stats.survivingAssetPaths += (output.match(/\.gitbook\/assets\//g) || []).length;
+
if (/hidden:/.test(output.split('---')[1] ?? '')) throw new Error(`${route.source}: hidden survived`);
}
const EXPECTED = {
files: 204,
- mdx: 46,
+ // Down from 46: an <iframe> is not a Starlight component, so an embed no longer
+ // promotes a page to .mdx. Only pages using LinkCard, Card, CardGrid or Steps do.
+ mdx: 18,
asides: 258,
contentRefCards: 51,
cardTableCards: 41,
embeds: 36,
cardGrids: 9,
- images: 529,
- droppedCovers: 13,
+ // Markdown-image occurrences across the corpus, not distinct assets — most of the 498
+ // image-kind entries in asset-map.json are referenced more than once. This is one less than
+ // the full occurrence count, because the corpus's sole video-kind asset (Knowledge Base
+ // Demo.gif) renders as a <video> element rather than a markdown image.
+ images: 528,
+ // No longer dropped: CoverCard renders them. The count is unchanged.
+ covers: 13,
+ // Four distinct GitBook shortcodes across three pages. A sync introducing a fifth
+ // moves this and must be adjudicated, not adjusted away.
+ emoji: 5,
survivingBlocks: 0,
survivingEntities: 0,
survivingImgTags: 0,
survivingBraces: 0,
+ survivingShortcodes: 0,
};
+if (assetMap) EXPECTED.survivingAssetPaths = 0;
let failed = false;
for (const [key, expected] of Object.entries(EXPECTED)) {
@@ -220,6 +280,7 @@ for (const [key, expected] of Object.entries(EXPECTED)) {
// Informational, not asserted: the corpus contains ordinary numbered lists too, so a
// "^\d+\. " count cannot isolate the 15 stepper steps. Task 6 checks those by eye.
console.log(` ${'ordered list items'.padEnd(20)} ${stats.steps}`);
+console.log(` ${'asset references'.padEnd(20)} ${stats.assetRefs}`);
console.log(`\nwrote ${stats.files} pages to src/content/docs`);
if (failed) {
diff --git a/scripts/lib/alt-audit.mjs b/scripts/lib/alt-audit.mjs
new file mode 100644
index 0000000..a093fa4
--- /dev/null
+++ b/scripts/lib/alt-audit.mjs
@@ -0,0 +1,68 @@
+/**
+ * Finds the images that ship with no text alternative, and the caption each one already has.
+ *
+ * Reads the authored content under src/content/docs/, which is the source of truth and the
+ * thing actually built: a work list drawn from anywhere else describes a site that is not
+ * being served. The rows name what a writer edits — the `~/assets/…` filename and the
+ * caption already beneath the image — not a hashed build artefact.
+ *
+ * Deriving alt from the caption was considered and rejected: most of these already sit under
+ * a caption that is announced, so copying it into alt makes a screen reader read the same
+ * sentence twice, and the ones with no caption — the images announced as nothing at all —
+ * would still have nothing. Alt must say what the image shows; the caption labels it.
+ */
+import { protectCode } from './segments.mjs';
+
+/** A markdown image: ``, destination possibly carrying a title. */
+const CONTENT_IMAGE = /!\[([^\]]*)\]\(([^)]*)\)/g;
+/** The bare filename an `~/assets/…` reference names, ignoring any title after the path. */
+const ASSET = /^~\/assets\/(\S+)/;
+
+/**
+ * What to call the image in the work list: the bare filename for a local asset, the URL for
+ * one still hotlinked from a third party. Markdown's backslash escapes are undone so the
+ * name matches what the page actually requests.
+ */
+function assetName(destination) {
+ const target = destination.trim().replace(/^<|>$/g, '').split(/\s+/)[0];
+ if (!target) return null;
+ const local = target.match(ASSET);
+ return (local ? local[1] : target).replace(/\\([_*()[\]\-.])/g, '$1');
+}
+
+/** A paragraph whose sole content is emphasis, which is how a caption reaches the build. */
+const EMPHASIS_ONLY = /^_([^_]+)_$|^\*([^*]+)\*$/;
+
+/** The caption a block carries, or '' when it is not a caption paragraph. */
+function captionOf(block) {
+ const emphasis = block.match(EMPHASIS_ONLY);
+ return emphasis ? (emphasis[1] ?? emphasis[2]) : '';
+}
+
+/** Every image in an authored page that ships with an empty alt, in document order. */
+export function emptyAltImages(text) {
+ const found = [];
+ // A fence masks to a single token line, which leaves the blank-line structure the caption
+ // pairing reads intact while taking example markup out of the count.
+ protectCode(text, (masked) => {
+ collect(masked, found);
+ return masked;
+ });
+ return found;
+}
+
+function collect(text, found) {
+ const blocks = text.split(/\n\s*\n/).map((block) => block.trim());
+ blocks.forEach((block, index) => {
+ const images = [...block.matchAll(CONTENT_IMAGE)];
+ // Only an image standing alone in its paragraph is paired with the caption beneath it,
+ // the same inference rehype-figures makes.
+ const alone = images.length === 1 && block === images[0][0];
+ const caption = alone ? captionOf(blocks[index + 1] ?? '') : '';
+ for (const [, alt, destination] of images) {
+ if (alt) continue;
+ const asset = assetName(destination);
+ if (asset) found.push({ asset, caption });
+ }
+ });
+}
diff --git a/scripts/lib/alt-audit.test.mjs b/scripts/lib/alt-audit.test.mjs
new file mode 100644
index 0000000..894f470
--- /dev/null
+++ b/scripts/lib/alt-audit.test.mjs
@@ -0,0 +1,65 @@
+import { test } from 'node:test';
+import assert from 'node:assert/strict';
+import { emptyAltImages } from './alt-audit.mjs';
+
+test('an image with no alt text is reported with its asset name', () => {
+ assert.deepEqual(emptyAltImages(''), [
+ { asset: 'image-547.png', caption: '' },
+ ]);
+});
+
+// convert.mjs carries GitBook's image width through as a markdown title, so the destination
+// is not always the bare path. Missing this form would name an asset that does not exist.
+test('a width title after the path is not part of the asset name', () => {
+ assert.deepEqual(emptyAltImages(''), [
+ { asset: 'image-623.png', caption: '' },
+ ]);
+});
+
+// rehype-figures pairs an image with the emphasis-only paragraph beneath it into a
+// <figure>/<figcaption>. The audit must read the same pairing or it will report a caption
+// the reader cannot see, or miss one they can.
+test('an emphasis paragraph beneath the image is its caption', () => {
+ const md = '\n\n_Create Scenario Link_\n';
+ assert.deepEqual(emptyAltImages(md), [{ asset: 'a.png', caption: 'Create Scenario Link' }]);
+});
+
+// Documentation about markdown contains markdown. An example inside a fence ships as text,
+// never as an <img>, so counting it would put a row in the work list with nothing to fix.
+test('an image inside a code fence is not a real image', () => {
+ const md = '```md\n\n```\n';
+ assert.deepEqual(emptyAltImages(md), []);
+});
+
+test('an image that already carries alt text is not reported', () => {
+ assert.deepEqual(emptyAltImages(''), []);
+});
+
+// Seven images on three pages are still hotlinked from googleusercontent and freshdesk. They
+// ship with an empty alt exactly as the local ones do, so leaving them out understates the
+// work and puts the row count permanently at odds with the build.
+test('a remotely hosted image with no alt text is reported', () => {
+ assert.deepEqual(emptyAltImages(''), [
+ { asset: 'https://example.com/x.png', caption: '' },
+ ]);
+});
+
+// GitBook laid figures out in a row inside a wrapper div, which convert.mjs reflows into one
+// paragraph holding several images. rehype-figures does not caption those, so neither may this.
+test('images sharing a paragraph take no caption', () => {
+ const md = '\n\n\n_Not their caption_\n';
+ assert.deepEqual(emptyAltImages(md), [
+ { asset: 'c.png', caption: '' },
+ { asset: 'd.png', caption: '' },
+ ]);
+});
+
+test('a paragraph that merely contains emphasis is not a caption', () => {
+ const md = '\n\nSee _the guide_ for more.\n';
+ assert.deepEqual(emptyAltImages(md), [{ asset: 'e.png', caption: '' }]);
+});
+
+test('an asterisk-emphasised caption is read the same as an underscored one', () => {
+ const md = '\n\n*Star caption*\n';
+ assert.deepEqual(emptyAltImages(md), [{ asset: 'f.png', caption: 'Star caption' }]);
+});
diff --git a/scripts/lib/asset-plan.mjs b/scripts/lib/asset-plan.mjs
new file mode 100644
index 0000000..1f0f79c
--- /dev/null
+++ b/scripts/lib/asset-plan.mjs
@@ -0,0 +1,87 @@
+/**
+ * Decides what each asset is called and how it is encoded. Pure: no filesystem, no decoding.
+ *
+ * Kept separate from assets.mjs so every naming and treatment decision is unit-testable
+ * without an image on disk.
+ */
+
+/** Width ceiling. Images are never enlarged. */
+export const MAX_WIDTH = 2000;
+
+/**
+ * Palette quantisation is applied only at or below this many unique colours in the resized
+ * image. Photographs and gradients band visibly at 256 colours; flat UI screenshots do not.
+ * Measured across the 505 referenced PNG/JPEG files: p50 5,643, p95 17,549, max 454,752.
+ *
+ * The count must be taken on the resized image. Unique colours scale with pixel count, so a
+ * threshold calibrated on a downsample admits far more images than intended.
+ */
+export const QUANTISE_MAX_COLOURS = 32768;
+
+/** A GIF at or above this size becomes an MP4. The two small corpus GIFs sit far below it. */
+export const GIF_VIDEO_THRESHOLD = 1024 * 1024;
+
+const STILL = /\.(?:png|jpe?g|webp)$/i;
+const GIF = /\.gif$/i;
+
+/** Filesystem-safe, URL-safe name: lowercase, single hyphens, original extension. */
+export function slugify(filename) {
+ const dot = filename.lastIndexOf('.');
+ const stem = dot > 0 ? filename.slice(0, dot) : filename;
+ const ext = dot > 0 ? filename.slice(dot).toLowerCase() : '';
+ const slug = stem
+ .toLowerCase()
+ .replace(/[^a-z0-9]+/g, '-')
+ .replace(/^-+|-+$/g, '');
+ if (!slug) throw new Error(`asset name slugifies to nothing: ${filename}`);
+ return `${slug}${ext}`;
+}
+
+/**
+ * Maps every original filename to a unique slug.
+ *
+ * Input is sorted internally so a collision suffix depends on the names alone, never on the
+ * order the caller happened to read the directory in — the run must be reproducible.
+ */
+export function assignSlugs(filenames) {
+ const taken = new Set();
+ const result = new Map();
+ for (const filename of [...filenames].sort()) {
+ const base = slugify(filename);
+ let slug = base;
+ if (taken.has(slug)) {
+ const dot = base.lastIndexOf('.');
+ const stem = dot > 0 ? base.slice(0, dot) : base;
+ const ext = dot > 0 ? base.slice(dot) : '';
+ let n = 2;
+ while (taken.has(`${stem}-${n}${ext}`)) n++;
+ slug = `${stem}-${n}${ext}`;
+ }
+ taken.add(slug);
+ result.set(filename, slug);
+ }
+ return result;
+}
+
+/** Where an asset goes and how it is encoded. `colours` is null for anything not a still image. */
+export function planAsset({ filename, bytes, colours }) {
+ if (STILL.test(filename)) {
+ if (colours === null || colours === undefined) {
+ throw new Error(`planAsset: still image needs a colour count: ${filename}`);
+ }
+ return {
+ kind: 'image',
+ destination: 'src/assets',
+ treatment: colours <= QUANTISE_MAX_COLOURS ? 'resize-quantise' : 'resize-only',
+ };
+ }
+ if (GIF.test(filename)) {
+ if (!Number.isFinite(bytes) || bytes < 0) {
+ throw new Error(`planAsset: gif needs a valid byte count: ${filename}`);
+ }
+ return bytes >= GIF_VIDEO_THRESHOLD
+ ? { kind: 'video', destination: 'public/media', treatment: 'encode-video' }
+ : { kind: 'image', destination: 'src/assets', treatment: 'copy' };
+ }
+ return { kind: 'file', destination: 'public/files', treatment: 'copy' };
+}
diff --git a/scripts/lib/asset-plan.test.mjs b/scripts/lib/asset-plan.test.mjs
new file mode 100644
index 0000000..5b62d0d
--- /dev/null
+++ b/scripts/lib/asset-plan.test.mjs
@@ -0,0 +1,80 @@
+import { test } from 'node:test';
+import assert from 'node:assert/strict';
+import {
+ assignSlugs,
+ planAsset,
+ slugify,
+ GIF_VIDEO_THRESHOLD,
+ MAX_WIDTH,
+ QUANTISE_MAX_COLOURS,
+} from './asset-plan.mjs';
+
+test('slugify lowercases and collapses non-alphanumeric runs', () => {
+ assert.equal(slugify('Screenshot 2024-07-09 at 09.52.58.png'), 'screenshot-2024-07-09-at-09-52-58.png');
+ assert.equal(slugify('image (149).png'), 'image-149.png');
+ assert.equal(slugify('2023-05-04_16-17-09 (1).png'), '2023-05-04-16-17-09-1.png');
+});
+
+test('slugify keeps the digits inside GitBook re-upload suffixes distinct', () => {
+ assert.notEqual(
+ slugify('Screenshot 2024-07-09 at 09.52.58.png'),
+ slugify('Screenshot 2024-07-09 at 09.52.58 (1).png')
+ );
+});
+
+test('slugify lowercases the extension and trims stray separators', () => {
+ assert.equal(slugify('Zrzut ekranu 2025-11-3 o 14.48.02.PNG'), 'zrzut-ekranu-2025-11-3-o-14-48-02.png');
+ assert.equal(slugify(' spaced .png'), 'spaced.png');
+});
+
+test('assignSlugs returns one slug per input and is order independent', () => {
+ const names = ['b.png', 'a.png'];
+ const forward = assignSlugs(names);
+ const reverse = assignSlugs([...names].reverse());
+ assert.deepEqual([...forward.entries()].sort(), [...reverse.entries()].sort());
+ assert.equal(forward.size, 2);
+});
+
+test('assignSlugs suffixes a collision deterministically by sorted original name', () => {
+ const map = assignSlugs(['Photo B.png', 'photo-b.png']);
+ assert.equal(map.get('Photo B.png'), 'photo-b.png');
+ assert.equal(map.get('photo-b.png'), 'photo-b-2.png');
+});
+
+test('a low-colour still image is resized and quantised', () => {
+ const plan = planAsset({ filename: 'a.png', bytes: 500000, colours: 3000 });
+ assert.deepEqual(plan, { kind: 'image', destination: 'src/assets', treatment: 'resize-quantise' });
+});
+
+test('a colour-rich still image is resized but kept full colour', () => {
+ const plan = planAsset({ filename: 'a.png', bytes: 500000, colours: QUANTISE_MAX_COLOURS + 1 });
+ assert.deepEqual(plan, { kind: 'image', destination: 'src/assets', treatment: 'resize-only' });
+});
+
+test('a small gif is copied byte-for-byte so its animation survives', () => {
+ const plan = planAsset({ filename: 'spin.gif', bytes: 150000, colours: null });
+ assert.deepEqual(plan, { kind: 'image', destination: 'src/assets', treatment: 'copy' });
+});
+
+test('a large gif becomes a video in public/media', () => {
+ const plan = planAsset({ filename: 'demo.gif', bytes: GIF_VIDEO_THRESHOLD + 1, colours: null });
+ assert.deepEqual(plan, { kind: 'video', destination: 'public/media', treatment: 'encode-video' });
+});
+
+test('a gif with a missing or malformed byte count throws instead of silently becoming a copy', () => {
+ assert.throws(() => planAsset({ filename: 'x.gif', bytes: undefined, colours: null }));
+ assert.throws(() => planAsset({ filename: 'x.gif', bytes: null, colours: null }));
+ assert.throws(() => planAsset({ filename: 'x.gif', bytes: NaN, colours: null }));
+ assert.throws(() => planAsset({ filename: 'x.gif', bytes: -1, colours: null }));
+});
+
+test('a non-image is copied to public/files', () => {
+ const plan = planAsset({ filename: 'data.csv', bytes: 1027, colours: null });
+ assert.deepEqual(plan, { kind: 'file', destination: 'public/files', treatment: 'copy' });
+});
+
+test('the exported thresholds are the measured values', () => {
+ assert.equal(MAX_WIDTH, 2000);
+ assert.equal(QUANTISE_MAX_COLOURS, 32768);
+ assert.equal(GIF_VIDEO_THRESHOLD, 1048576);
+});
diff --git a/scripts/lib/asset-refs.mjs b/scripts/lib/asset-refs.mjs
new file mode 100644
index 0000000..f7e8714
--- /dev/null
+++ b/scripts/lib/asset-refs.mjs
@@ -0,0 +1,63 @@
+/**
+ * Finds every .gitbook/assets reference in a source file, and which of them are card covers.
+ *
+ * Destinations come from links.mjs's scanner rather than a regex: 1,056 asset filenames
+ * contain parentheses and `\]\(([^)]+)\)` truncates at the first one.
+ */
+import { protectCode } from './segments.mjs';
+import { extractTargets } from './links.mjs';
+import { coverTargets } from './link-cards.mjs';
+
+export const ASSET_SRC = /\.gitbook\/assets\/(.*)$/;
+/**
+ * Matches any double-quoted src="…" or href="…" text, regardless of surrounding markup.
+ *
+ * This is also the only thing that finds a GitBook `{% file src="…" %}` block's asset — there
+ * is no dedicated pattern for that construct, because its `src="…"` attribute is textually
+ * indistinguishable from an HTML one. A `{% file %}` block written with single quotes, or any
+ * other attribute syntax, would not match this regex and its asset would silently disappear
+ * from `all` with no error. Anyone changing GitBook's file-block syntax must check this regex.
+ */
+const ATTR = /(?:src|href)="([^"]*)"/g;
+
+/**
+ * Unescapes a captured .gitbook/assets path segment into the bare filename it names.
+ *
+ * This is the rule the asset map's keys are built from: assets.mjs derives each key by running
+ * a source reference through this exact function, and figures.mjs's assetPath must resolve a
+ * name the same way when it looks a key up, so the rule lives here once rather than as two
+ * copies that could drift apart.
+ */
+export function unescapeAssetName(raw) {
+ const name = raw.replace(/\\([_()*[\]\-.])/g, '$1');
+ try {
+ return decodeURIComponent(name);
+ } catch {
+ throw new Error(`asset reference is not valid percent-encoding: ${raw}`);
+ }
+}
+
+/** Bare asset filename from a destination, or null when the destination is not an asset. */
+function assetName(destination) {
+ const clean = destination.trim();
+ if (/^https?:/i.test(clean)) return null;
+ const match = clean.match(ASSET_SRC);
+ if (!match) return null;
+ return unescapeAssetName(match[1]);
+}
+
+/** Every asset reference in `text`, and the subset that are data-card-cover hrefs. */
+export function assetRefsInFile(text) {
+ const all = [];
+ const push = (destination) => {
+ const name = assetName(destination);
+ if (name) all.push(name);
+ };
+ protectCode(text, (masked) => {
+ for (const { target } of extractTargets(masked)) push(target);
+ for (const [, value] of masked.matchAll(ATTR)) push(value);
+ return masked;
+ });
+ const covers = coverTargets(text).map(assetName).filter(Boolean);
+ return { all, covers };
+}
diff --git a/scripts/lib/asset-refs.test.mjs b/scripts/lib/asset-refs.test.mjs
new file mode 100644
index 0000000..8ee538c
--- /dev/null
+++ b/scripts/lib/asset-refs.test.mjs
@@ -0,0 +1,78 @@
+import { test } from 'node:test';
+import assert from 'node:assert/strict';
+import { assetRefsInFile } from './asset-refs.mjs';
+
+test('finds a plain markdown image', () => {
+ const { all } = assetRefsInFile('');
+ assert.deepEqual(all, ['one.png']);
+});
+
+test('finds an angle-bracketed destination containing spaces and parens', () => {
+ const { all } = assetRefsInFile('.png>)');
+ assert.deepEqual(all, ['image (149).png']);
+});
+
+test('does not truncate an unbracketed destination containing parens', () => {
+ const { all } = assetRefsInFile('.png)');
+ assert.deepEqual(all, ['putting it all together (1).png']);
+});
+
+test('undoes markdown backslash escapes', () => {
+ const { all } = assetRefsInFile('.png>)');
+ assert.deepEqual(all, ['2023-05-04_16-17-09 (1).png']);
+});
+
+test('decodes percent-encoded spaces', () => {
+ const { all } = assetRefsInFile('');
+ assert.deepEqual(all, ['a b.png']);
+});
+
+test('finds raw HTML src and href references', () => {
+ const text = '<img src="../.gitbook/assets/raw.png"><a href="../.gitbook/assets/doc.csv">d</a>';
+ assert.deepEqual(assetRefsInFile(text).all, ['raw.png', 'doc.csv']);
+});
+
+// This is generic ATTR coverage, not a dedicated file-block pattern: a {% file %} block's
+// asset is found only because its src="…" attribute happens to read like an HTML one. See
+// the ATTR comment in asset-refs.mjs.
+test('finds a GitBook file block via its src="…" attribute', () => {
+ const { all } = assetRefsInFile('{% file src="../.gitbook/assets/data.csv" %}');
+ assert.deepEqual(all, ['data.csv']);
+});
+
+test('ignores references inside a fenced block', () => {
+ const text = ['```md', '', '```'].join('\n');
+ assert.deepEqual(assetRefsInFile(text).all, []);
+});
+
+test('ignores remote URLs and non-asset links', () => {
+ const text = ' [x](../other/page.md)';
+ assert.deepEqual(assetRefsInFile(text).all, []);
+});
+
+test('reports cover targets separately and also within all', () => {
+ const text = [
+ '<table data-view="cards" data-card-cover="true">',
+ '<tbody><tr><td><a href="../.gitbook/assets/cover.png">c</a></td><td>Body</td></tr></tbody>',
+ '</table>',
+ ].join('\n');
+ const { all, covers } = assetRefsInFile(text);
+ assert.deepEqual(covers, ['cover.png']);
+ assert.deepEqual(all, ['cover.png']);
+});
+
+test('preserves a duplicate reference when the same asset is both a card cover and a figure', () => {
+ const text = [
+ '<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead>',
+ '<tbody><tr><td>Project usage</td><td><a href=".gitbook/assets/Screenshot 2024-09-26 at 10.32.32.png">Screenshot 2024-09-26 at 10.32.32.png</a></td></tr></tbody>',
+ '</table>',
+ '',
+ '<figure><img src=".gitbook/assets/Screenshot 2024-09-26 at 10.32.32.png" alt=""><figcaption><p>Expanded view</p></figcaption></figure>',
+ ].join('\n');
+ const { all, covers } = assetRefsInFile(text);
+ assert.deepEqual(all, [
+ 'Screenshot 2024-09-26 at 10.32.32.png',
+ 'Screenshot 2024-09-26 at 10.32.32.png',
+ ]);
+ assert.deepEqual(covers, ['Screenshot 2024-09-26 at 10.32.32.png']);
+});
diff --git a/scripts/lib/dist-links.mjs b/scripts/lib/dist-links.mjs
new file mode 100644
index 0000000..7b23f2a
--- /dev/null
+++ b/scripts/lib/dist-links.mjs
@@ -0,0 +1,44 @@
+/**
+ * Reads the links, in-page anchors and element ids out of a built page.
+ *
+ * The built output is the only honest place to check a link: convert.mjs rewrites relative
+ * .md links, rehype rewrites headings into slugs, and Starlight adds navigation of its own,
+ * so a check against source/ would measure something no reader ever loads.
+ *
+ * Every internal href Starlight emits is root-relative or a bare fragment — measured across
+ * all 205 pages — but relative destinations resolve correctly anyway, so a future component
+ * that emits one is handled rather than silently skipped.
+ */
+const ANCHOR = /<a\b[^>]*\shref="([^"]*)"/g;
+const ID = /\sid="([^"]*)"/g;
+const OFF_SITE = /^(?:[a-z][a-z0-9+.-]*:|\/\/)/i;
+
+/** The URL a built file is served at, with no trailing slash. */
+export function pageUrl(relativePath) {
+ const url = `/${relativePath.replace(/(?:^|\/)index\.html$/, '').replace(/\.html$/, '')}`;
+ return url.replace(/\/$/, '') || '/';
+}
+
+/** Every href on the page, in document order. */
+export function extractHrefs(html) {
+ return [...html.matchAll(ANCHOR)].map((m) => m[1]);
+}
+
+/** Every element id on the page. */
+export function extractIds(html) {
+ return new Set([...html.matchAll(ID)].map((m) => m[1]));
+}
+
+/**
+ * Where an href found on `fromUrl` points, or null when it leaves the site.
+ *
+ * The fragment is decoded because an id attribute holds the decoded character while the href
+ * holds it percent-encoded, and comparing the two raw would report a working anchor as broken.
+ */
+export function resolveHref(fromUrl, href) {
+ if (!href || OFF_SITE.test(href)) return null;
+ const [target, ...rest] = href.split('#');
+ const hash = rest.join('#');
+ const path = target === '' ? fromUrl : new URL(target, `https://site${fromUrl}`).pathname;
+ return { path: path.replace(/\/$/, '') || '/', hash: hash ? decodeURIComponent(hash) : '' };
+}
diff --git a/scripts/lib/dist-links.test.mjs b/scripts/lib/dist-links.test.mjs
new file mode 100644
index 0000000..a5575e4
--- /dev/null
+++ b/scripts/lib/dist-links.test.mjs
@@ -0,0 +1,48 @@
+import { test } from 'node:test';
+import assert from 'node:assert/strict';
+import { pageUrl, extractHrefs, extractIds, resolveHref } from './dist-links.mjs';
+
+test('a page directory maps to its URL without a trailing slash', () => {
+ assert.equal(pageUrl('core-concepts/interpreters/index.html'), '/core-concepts/interpreters');
+});
+
+test('the root index maps to /', () => {
+ assert.equal(pageUrl('index.html'), '/');
+});
+
+test('a standalone html file keeps its own name', () => {
+ assert.equal(pageUrl('404.html'), '/404');
+});
+
+test('hrefs are read regardless of the attributes around them', () => {
+ const html = '<a class="x" href="/a">A</a><a href="/b" data-y>B</a>';
+ assert.deepEqual(extractHrefs(html), ['/a', '/b']);
+});
+
+test('ids are collected from any element', () => {
+ const ids = extractIds('<h2 id="one">x</h2><div id="two"></div>');
+ assert.deepEqual([...ids].sort(), ['one', 'two']);
+});
+
+test('a root-relative href resolves to itself', () => {
+ assert.deepEqual(resolveHref('/a/b', '/c/d'), { path: '/c/d', hash: '' });
+});
+
+test('a fragment-only href resolves to the page it sits on', () => {
+ assert.deepEqual(resolveHref('/a/b', '#section'), { path: '/a/b', hash: 'section' });
+});
+
+test('a trailing slash is normalised away so both spellings compare equal', () => {
+ assert.deepEqual(resolveHref('/a/b', '/c/'), { path: '/c', hash: '' });
+});
+
+test('a percent-encoded fragment is decoded to match the id it names', () => {
+ assert.deepEqual(resolveHref('/a', '/b#caf%C3%A9'), { path: '/b', hash: 'café' });
+});
+
+test('external and non-http schemes are skipped', () => {
+ assert.equal(resolveHref('/a', 'https://example.com'), null);
+ assert.equal(resolveHref('/a', 'mailto:x@example.com'), null);
+ assert.equal(resolveHref('/a', '//example.com/x'), null);
+ assert.equal(resolveHref('/a', ''), null);
+});
diff --git a/scripts/lib/emoji.mjs b/scripts/lib/emoji.mjs
new file mode 100644
index 0000000..76e5952
--- /dev/null
+++ b/scripts/lib/emoji.mjs
@@ -0,0 +1,68 @@
+/**
+ * Renders GitBook's emoji shortcodes as the characters they stand for.
+ *
+ * GitBook renders `:white_check_mark:` as ✅; Starlight has no shortcode support, so the
+ * literal text reached the page — measured on the live site, `:heavy_plus_sign: Adding a
+ * new user` renders there as `➕ Adding a new user`.
+ *
+ * The corpus uses exactly four shortcodes across five occurrences on three pages, so they
+ * are mapped by hand rather than by pulling in a full emoji table. convert.mjs asserts
+ * both the number converted and that none is left behind, so a GitBook sync that
+ * introduces a fifth shortcode fails the run rather than shipping literal text.
+ *
+ * Two shapes of text must not be mistaken for a shortcode: a time or ratio like 12:30:45,
+ * and Starlight's own `:::note` aside markers. Requiring a leading letter excludes the
+ * first, and requiring a closing colon on the same run excludes the second.
+ */
+import { protectCode } from './segments.mjs';
+
+/** The shortcodes this corpus uses, and the characters GitBook renders for them. */
+export const EMOJI = {
+ heavy_plus_sign: '➕',
+ tada: '🎉',
+ white_check_mark: '✅',
+ x: '❌',
+};
+
+/** A shortcode, tolerating the backslash escapes convert.mjs adds to underscores. */
+const SHORTCODE = /:([a-z0-9_+\\-]{1,40}):/g;
+
+/** Strips markdown escaping so `white\_check\_mark` looks up as `white_check_mark`. */
+const unescapeName = (name) => name.replace(/\\/g, '');
+
+export function convertEmoji(text) {
+ return protectCode(text, (masked) =>
+ masked.replace(SHORTCODE, (whole, name) => EMOJI[unescapeName(name)] ?? whole)
+ );
+}
+
+/** Shortcodes this map can render, as they appear before conversion. */
+export function countEmoji(text) {
+ let count = 0;
+ protectCode(text, (masked) => {
+ for (const match of masked.matchAll(SHORTCODE)) {
+ if (EMOJI[unescapeName(match[1])]) count++;
+ }
+ return masked;
+ });
+ return count;
+}
+
+/**
+ * Shortcodes left over after conversion — ones this map cannot render.
+ *
+ * Deliberately conservative: a leading letter and at least three characters, so neither
+ * `12:30:45` nor a stray `:2:` is counted.
+ */
+const UNKNOWN = /:([a-z][a-z0-9_+\\-]{2,39}):/g;
+
+export function countUnknownShortcodes(text) {
+ let count = 0;
+ protectCode(text, (masked) => {
+ for (const match of masked.matchAll(UNKNOWN)) {
+ if (!EMOJI[unescapeName(match[1])]) count++;
+ }
+ return masked;
+ });
+ return count;
+}
diff --git a/scripts/lib/emoji.test.mjs b/scripts/lib/emoji.test.mjs
new file mode 100644
index 0000000..810a689
--- /dev/null
+++ b/scripts/lib/emoji.test.mjs
@@ -0,0 +1,66 @@
+import { test } from 'node:test';
+import assert from 'node:assert/strict';
+import { EMOJI, convertEmoji, countEmoji, countUnknownShortcodes } from './emoji.mjs';
+
+test('a known shortcode becomes its character', () => {
+ assert.equal(convertEmoji(':tada: Released'), '🎉 Released');
+ assert.equal(convertEmoji('Do :white_check_mark:'), 'Do ✅');
+ assert.equal(convertEmoji(':x: Do not'), '❌ Do not');
+ assert.equal(convertEmoji(':heavy_plus_sign: Adding a user'), '➕ Adding a user');
+});
+
+test('a markdown-escaped underscore is still recognised', () => {
+ // convert.mjs escapes underscores on the way to MDX, so the shortcode can reach this
+ // transform in either form depending on ordering.
+ assert.equal(convertEmoji(':white\\_check\\_mark: Do'), '✅ Do');
+});
+
+test('an unknown shortcode is left untouched', () => {
+ assert.equal(convertEmoji(':rocket: ship it'), ':rocket: ship it');
+});
+
+test('shortcodes inside a fenced code block are left alone', () => {
+ const fence = '```\n:tada:\n```';
+ assert.equal(convertEmoji(fence), fence);
+});
+
+test('shortcodes inside inline code are left alone', () => {
+ assert.equal(convertEmoji('use `:tada:` here'), 'use `:tada:` here');
+});
+
+test('a time or ratio is not mistaken for a shortcode', () => {
+ assert.equal(convertEmoji('at 12:30:45 and a 3:2:1 ratio'), 'at 12:30:45 and a 3:2:1 ratio');
+});
+
+test('a URL is not mistaken for a shortcode', () => {
+ assert.equal(convertEmoji('see https://example.com:8080/a'), 'see https://example.com:8080/a');
+});
+
+test('an aside marker is not mistaken for a shortcode', () => {
+ assert.equal(convertEmoji(':::note\nBody\n:::'), ':::note\nBody\n:::');
+});
+
+test('countUnknownShortcodes finds a shortcode this map cannot render', () => {
+ assert.equal(countUnknownShortcodes(':rocket: ship'), 1);
+ assert.equal(countUnknownShortcodes('🎉 already converted'), 0);
+ assert.equal(countUnknownShortcodes('at 12:30:45'), 0);
+ assert.equal(countUnknownShortcodes(':::note\nx\n:::'), 0);
+});
+
+test('countUnknownShortcodes ignores code', () => {
+ assert.equal(countUnknownShortcodes('```\n:rocket:\n```'), 0);
+});
+
+test('countEmoji counts only shortcodes this map can render', () => {
+ assert.equal(countEmoji(':tada: and :x: and :rocket:'), 2);
+ assert.equal(countEmoji(':white\\_check\\_mark:'), 1);
+ assert.equal(countEmoji('```\n:tada:\n```'), 0);
+ assert.equal(countEmoji('nothing here'), 0);
+});
+
+test('every mapped shortcode maps to a non-empty character', () => {
+ for (const [name, char] of Object.entries(EMOJI)) {
+ assert.ok(char.length > 0, `${name} has no character`);
+ assert.ok(!/^[a-z:]/.test(char), `${name} maps to something that looks like text`);
+ }
+});
diff --git a/scripts/lib/figures.mjs b/scripts/lib/figures.mjs
index ddce5bd..16725d1 100644
--- a/scripts/lib/figures.mjs
+++ b/scripts/lib/figures.mjs
@@ -4,34 +4,85 @@
* Raw <img> in markdown bypasses Astro's image pipeline entirely, which would ship 541 MB of
* screenshots unoptimised. This is the highest-value transformation in the migration.
*
- * Paths are emitted root-absolute. Assets do not reach src/assets/ until Phase 3, and Astro
- * treats an unresolvable *relative* image path as a fatal build error, whereas a leading "/"
- * is read as a public/ path and left alone. assets.mjs rewrites these in Phase 3.
+ * Paths resolve through asset-map.json, written by assets.mjs, which maps each original
+ * .gitbook/assets filename to where the physical file ended up. Without that map — a checkout
+ * where assets.mjs has never run — a root-absolute placeholder is emitted instead, so the build
+ * stays green: Astro treats an unresolvable *relative* image path as a fatal build error,
+ * whereas a leading "/" is read as a public/ path and left alone.
*/
+import { ASSET_SRC, unescapeAssetName } from './asset-refs.mjs';
import { protectCode } from './segments.mjs';
-const NEEDS_ANGLE = /[ ()]/;
-const FIGURE = /<figure>\s*<img\s+([^>]*?)>\s*(?:<figcaption>([\s\S]*?)<\/figcaption>)?\s*<\/figure>/g;
+export const NEEDS_ANGLE = /[ ()]/;
+export const FIGURE = /<figure>\s*<img\s+([^>]*?)>\s*(?:<figcaption>([\s\S]*?)<\/figcaption>)?\s*<\/figure>/g;
const BARE_IMG = /<img\s+([^>]*?)>/g;
-const ASSET_IMAGE = /!\[([^\]]*)\]\((<[^>]*>|[^)]*(?:\([^)]*\)[^)]*)*)\)/g;
+export const ASSET_IMAGE = /!\[([^\]]*)\]\((<[^>]*>|[^)]*(?:\([^)]*\)[^)]*)*)\)/g;
-/** Rewrites any .gitbook/assets reference to its root-absolute form. Remote URLs pass through. */
-export function assetPath(src) {
+/** The bare, unescaped filename a .gitbook/assets reference names, or null if it is not one. */
+function assetName(src) {
+ const match = src.match(ASSET_SRC);
+ return match ? unescapeAssetName(match[1]) : null;
+}
+
+/**
+ * Resolves a .gitbook/assets reference to its final form.
+ *
+ * With an asset map, returns what assets.mjs produced. Without one — a checkout where Phase 3
+ * has never run — returns the root-absolute placeholder, so the build stays green. A reference
+ * absent from a map that does exist is a real inconsistency between the two generators and
+ * throws.
+ */
+export function assetPath(src, assets) {
if (/^https?:/i.test(src)) return src;
- const match = src.match(/\.gitbook\/assets\/(.*)$/);
- return match ? `/.gitbook/assets/${match[1]}` : src;
+ const match = src.match(ASSET_SRC);
+ if (!match) return src;
+ if (!assets) return `/.gitbook/assets/${match[1]}`;
+ const name = unescapeAssetName(match[1]);
+ const entry = assets[name];
+ if (!entry) throw new Error(`asset not in asset-map.json: ${name}`);
+ return entry.reference;
}
-/** Renders a markdown image, bracketing the path only when it would break link parsing. */
-function image(alt, src) {
- const path = assetPath(src);
- return ` ? `<${path}>` : path})`;
+const VIDEO_CONTAINER = /\.(?:mp4|webm)$/i;
+
+/**
+ * A GitBook `width` attribute as an integer pixel string, or null.
+ *
+ * GitBook only ever writes integer pixel widths. Anything else is a shape this converter
+ * has not seen, and carrying a value the rehype plugin cannot use would leave a stray
+ * tooltip on the image, so it is dropped rather than guessed at.
+ */
+function widthOf(attrs) {
+ return attrs.match(/\bwidth="(\d+)"/)?.[1] ?? null;
+}
+
+/**
+ * Renders an asset reference: an image, or a video element for an asset that became one.
+ *
+ * A width rides in the markdown title slot. Markdown has nowhere else to put one, and the
+ * alternatives are worse: a raw <img> would bypass astro:assets, and a wrapper <div> is
+ * block markup that breaks the enclosing list for the one width-bearing figure that sits
+ * inside a list item. scripts/lib/rehype-image-width.mjs turns the title into a width and
+ * removes it, so no title reaches the page.
+ */
+function image(alt, src, assets, width) {
+ const entry = assets ? assets[assetName(src)] : null;
+ const path = assetPath(src, assets);
+ if (entry?.kind === 'video') {
+ if (!VIDEO_CONTAINER.test(path)) {
+ throw new Error(`image: kind is "video" but reference is not a video container: ${path}`);
+ }
+ const ariaLabel = alt ? ` aria-label="${alt}"` : '';
+ return `<video autoplay loop muted playsinline${ariaLabel} src="${path}"></video>`;
+ }
+ const dest = NEEDS_ANGLE.test(path) ? `<${path}>` : path;
+ return `![${alt}](${dest}${width ? ` "${width}"` : ''})`;
}
/** Plain-text form of a <figcaption>, keeping <code> spans as backticks since GitBook's export
* uses them to mark an attribute name inline; every other tag carries no information the
* italic caption needs. */
-function captionText(caption) {
+export function captionText(caption) {
return (caption ?? '')
.replace(/<code>([\s\S]*?)<\/code>/g, '`$1`')
.replace(/<[^>]*>/g, '')
@@ -55,7 +106,8 @@ function captionText(caption) {
* 430 figures sit inside a list item (troubleshooting-interpreters.md, about-attributes.md),
* where a column-0 caption line closes the enclosing list at that point in the document.
*/
-export function convertFigures(text) {
+export function convertFigures(text, ctx) {
+ const assets = ctx?.assets ?? null;
return protectCode(text, (masked) => {
const converted = masked
.replace(FIGURE, (_, attrs, caption, offset, full) => {
@@ -65,12 +117,13 @@ export function convertFigures(text) {
const src = attrs.match(/src="([^"]*)"/)?.[1] ?? '';
const alt = attrs.match(/alt="([^"]*)"/)?.[1] ?? '';
const cap = captionText(caption);
- return cap ? `${image(alt, src)}\n\n${indent}*${cap}*` : image(alt, src);
+ const rendered = image(alt, src, assets, widthOf(attrs));
+ return cap ? `${rendered}\n\n${indent}*${cap}*` : rendered;
})
.replace(BARE_IMG, (whole, attrs) => {
const src = attrs.match(/src="([^"]*)"/)?.[1];
if (!src) throw new Error(`convertFigures: <img> with no src attribute: ${whole}`);
- return image(attrs.match(/alt="([^"]*)"/)?.[1] ?? '', src);
+ return image(attrs.match(/alt="([^"]*)"/)?.[1] ?? '', src, assets, widthOf(attrs));
});
if (converted.includes('<figure') || converted.includes('<figcaption')) {
throw new Error('convertFigures: a <figure> block did not match the expected one-image shape');
@@ -117,12 +170,13 @@ export function reflowImageDiv(text) {
}
/** Normalises the paths of markdown images that were already in the source. */
-export function rewriteAssetRefs(text) {
+export function rewriteAssetRefs(text, ctx) {
+ const assets = ctx?.assets ?? null;
return protectCode(text, (masked) =>
masked.replace(ASSET_IMAGE, (whole, alt, dest) => {
const src = dest.startsWith('<') ? dest.slice(1, -1) : dest;
if (!/\.gitbook\/assets\//.test(src)) return whole;
- return image(alt, src);
+ return image(alt, src, assets);
})
);
}
diff --git a/scripts/lib/figures.test.mjs b/scripts/lib/figures.test.mjs
index ffb67ea..f7988b6 100644
--- a/scripts/lib/figures.test.mjs
+++ b/scripts/lib/figures.test.mjs
@@ -29,6 +29,43 @@ test('a figure with an empty caption emits only the image', () => {
);
});
+test("an img's width is carried through as the markdown title", () => {
+ // Markdown has nowhere to put a width. The title slot is the only channel that
+ // survives into the HTML without introducing block markup, which matters because one
+ // width-bearing figure sits inside a list item where a wrapper div would break the
+ // list. rehype-image-width turns it into a style and strips it.
+ assert.equal(
+ convertFigures('<figure><img src=".gitbook/assets/a.png" alt="" width="375"></figure>'),
+ ''
+ );
+});
+
+test('a width is carried alongside an angle-bracketed path and a caption', () => {
+ assert.equal(
+ convertFigures(
+ '<figure><img src=".gitbook/assets/a b.png" alt="Alt" width="188">' +
+ '<figcaption><p>Cap</p></figcaption></figure>'
+ ),
+ '\n\n*Cap*'
+ );
+});
+
+test('an img with no width emits no title', () => {
+ assert.equal(
+ convertFigures('<figure><img src=".gitbook/assets/a.png" alt=""></figure>'),
+ ''
+ );
+});
+
+test('a non-numeric width is ignored rather than emitted as a title', () => {
+ // GitBook only ever writes integer pixel widths; anything else would be a shape this
+ // converter has not seen, and a bogus title is worse than no width.
+ assert.equal(
+ convertFigures('<figure><img src=".gitbook/assets/a.png" alt="" width="100%"></figure>'),
+ ''
+ );
+});
+
test('alt text is preserved and never invented', () => {
assert.equal(
convertFigures('<figure><img src=".gitbook/assets/a.png" alt="A diagram"><figcaption></figcaption></figure>'),
@@ -170,6 +207,69 @@ test('a div inside a fence is left as literal text', () => {
assert.equal(reflowImageDiv(input), input);
});
+const ASSETS = {
+ 'one.png': { slug: 'one.png', kind: 'image', reference: '~/assets/one.png', hash: 'x' },
+ 'demo.gif': { slug: 'demo.mp4', kind: 'video', reference: '/media/demo.mp4', hash: 'y' },
+ 'data.csv': { slug: 'data.csv', kind: 'file', reference: '/files/data.csv', hash: 'z' },
+};
+
+test('a mapped image emits the alias reference', () => {
+ const out = convertFigures('<figure><img src="../.gitbook/assets/one.png" alt="A"></figure>', { assets: ASSETS });
+ assert.equal(out.trim(), '');
+});
+
+test('a mapped video emits a video element, not an image', () => {
+ const out = convertFigures('<figure><img src="../.gitbook/assets/demo.gif" alt="A demo"></figure>', { assets: ASSETS });
+ assert.match(out, /<video[^>]*autoplay[^>]*loop[^>]*muted[^>]*playsinline/);
+ assert.match(out, /src="\/media\/demo\.mp4"/);
+ assert.doesNotMatch(out, /!\[/);
+});
+
+test('a mapped video carries its alt text forward as an aria-label', () => {
+ const out = convertFigures('<figure><img src="../.gitbook/assets/demo.gif" alt="A demo"></figure>', { assets: ASSETS });
+ assert.match(out, /aria-label="A demo"/);
+});
+
+test('a mapped video with no alt text emits no empty aria-label', () => {
+ const out = convertFigures('<figure><img src="../.gitbook/assets/demo.gif" alt=""></figure>', { assets: ASSETS });
+ assert.doesNotMatch(out, /aria-label/);
+});
+
+test('a video kind mapped to an mp4 reference is accepted', () => {
+ const assets = { 'demo.gif': { slug: 'demo.mp4', kind: 'video', reference: '/media/demo.mp4', hash: 'y' } };
+ assert.doesNotThrow(() =>
+ convertFigures('<figure><img src="../.gitbook/assets/demo.gif" alt=""></figure>', { assets })
+ );
+});
+
+test('a video kind mapped to a gif reference throws rather than emitting an unplayable video', () => {
+ const assets = { 'demo.gif': { slug: 'demo.gif', kind: 'video', reference: '/media/demo.gif', hash: 'y' } };
+ assert.throws(
+ () => convertFigures('<figure><img src="../.gitbook/assets/demo.gif" alt=""></figure>', { assets }),
+ /kind is "video" but reference is not a video container/
+ );
+});
+
+test('with no map at all the placeholder form is kept', () => {
+ const out = convertFigures('<figure><img src="../.gitbook/assets/one.png" alt="A"></figure>', { assets: null });
+ assert.equal(out.trim(), '');
+});
+
+test('a reference missing from an existing map throws', () => {
+ assert.throws(
+ () => convertFigures('<figure><img src="../.gitbook/assets/gone.png" alt=""></figure>', { assets: ASSETS }),
+ /gone\.png/
+ );
+});
+
+test('rewriteAssetRefs maps an existing markdown image', () => {
+ assert.equal(rewriteAssetRefs('', { assets: ASSETS }), '');
+});
+
+test('a remote image is untouched whether or not a map exists', () => {
+ assert.equal(rewriteAssetRefs('', { assets: ASSETS }), '');
+});
+
test('reflowImageDiv followed by convertFigures pairs each caption with its own image', () => {
// End-to-end regression for the bug the review found: date-picker-message.md's shape is
// exactly three figures on one line inside one div.
diff --git a/scripts/lib/gitbook-blocks.mjs b/scripts/lib/gitbook-blocks.mjs
index a00cf4c..4d9223e 100644
--- a/scripts/lib/gitbook-blocks.mjs
+++ b/scripts/lib/gitbook-blocks.mjs
@@ -3,6 +3,7 @@
*
* Hints, code and file blocks need no component, so a file containing only these stays .md.
*/
+import { assetPath, NEEDS_ANGLE } from './figures.mjs';
import { mapLines, protectCode } from './segments.mjs';
const ASIDE = { info: 'note', success: 'tip', warning: 'caution', danger: 'danger' };
@@ -65,13 +66,16 @@ export function convertHints(text) {
});
}
-/** Turns the single {% file %} block into a markdown link to a Phase 3 asset placeholder. */
-export function convertFile(text) {
+/** Turns the single {% file %} block into a markdown link to the asset it resolves to. */
+export function convertFile(text, ctx) {
+ const assets = ctx?.assets ?? null;
return mapLines(text, (line) => {
const match = line.match(/^[ \t]*\{%\s*file\s+src="([^"]+)"\s*%\}[ \t]*$/);
if (!match) return line;
const name = match[1].split('/').pop();
- return `[${name}](</.gitbook/assets/${name}>)`;
+ if (!assets) return `[${name}](</.gitbook/assets/${name}>)`;
+ const path = assetPath(match[1], assets);
+ return `[${name}](${NEEDS_ANGLE.test(path) ? `<${path}>` : path})`;
});
}
@@ -114,9 +118,50 @@ function attribute(value) {
* — and is therefore promoted to .mdx regardless — fails to build. A `[url](url)` link is
* unambiguous in both .md and .mdx and reads the same on the page.
*/
-function renderEmbed(url, title) {
- if (!isVideoEmbed(url)) return `[${url}](${url})`;
- return title ? `<Embed url="${url}" title="${attribute(title)}" />` : `<Embed url="${url}" />`;
+/**
+ * Maps a share URL to its embeddable form. isVideoEmbed decides which shapes get here.
+ */
+function embedSrc(url) {
+ const parsed = new URL(url);
+ const host = parsed.hostname.replace(/^www\./, '');
+ if (host === 'youtu.be') return `https://www.youtube-nocookie.com/embed/${parsed.pathname.slice(1)}`;
+ if (host === 'youtube.com') return `https://www.youtube-nocookie.com/embed/${parsed.searchParams.get('v')}`;
+ return url.replace('/share/', '/embed/').split('?')[0];
+}
+
+/**
+ * Renders a video embed as raw HTML rather than a Starlight component.
+ *
+ * An <iframe> is not a Starlight component, so CLAUDE.md's rule — promote to .mdx only
+ * when a component is genuinely required — was never met by an embed. Emitting a component
+ * promoted 28 pages to .mdx for no other reason, and MDX parses a raw <pre> as JSX with
+ * markdown children: on progress-bar-message that silently stripped the snippet's
+ * indentation and turned its straight quotes into curly ones, breaking an XML sample
+ * readers copy. The same markup in a .md file is passed through untouched.
+ *
+ * The iframe is closed rather than self-closed so the markup parses as both HTML and MDX,
+ * since two pages keep an embed alongside a component they do genuinely need.
+ *
+ * Every emitted line carries the indentation of the block it replaces. A block-level
+ * element at column 0 closes any enclosing list, and 7 embeds on
+ * ai-agent-creation-overview sit inside list items within a {% stepper %} — Starlight's
+ * <Steps> requires its content to be a single <ol> and rejects the page outright when one
+ * breaks out. This is the same hazard figures.mjs handles for captions.
+ */
+function renderEmbed(url, title, indent = '') {
+ if (!isVideoEmbed(url)) return `${indent}[${url}](${url})`;
+ const label = attribute(title || 'Embedded video');
+ const lines = [
+ `<figure class="od-embed">`,
+ `<div class="od-embed-frame">`,
+ `<iframe src="${embedSrc(url)}" title="${label}" loading="lazy" ` +
+ `allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" ` +
+ `allowfullscreen></iframe>`,
+ `</div>`,
+ ...(title ? [`<figcaption>${attribute(title)}</figcaption>`] : []),
+ `</figure>`,
+ ];
+ return lines.map((line) => `${indent}${line}`).join('\n');
}
/**
@@ -131,10 +176,13 @@ export function convertEmbeds(text) {
return protectCode(text, (masked) =>
masked
.replace(
- /^[ \t]*\{%\s*embed\s+url="([^"]+)"[^%]*%\}\n([\s\S]*?)\n[ \t]*\{%\s*endembed\s*%\}[ \t]*$/gm,
- (_, url, caption) => renderEmbed(url, caption.replace(/\s+/g, ' ').trim())
+ /^([ \t]*)\{%\s*embed\s+url="([^"]+)"[^%]*%\}\n([\s\S]*?)\n[ \t]*\{%\s*endembed\s*%\}[ \t]*$/gm,
+ (_, indent, url, caption) => renderEmbed(url, caption.replace(/\s+/g, ' ').trim(), indent)
+ )
+ .replace(
+ /^([ \t]*)\{%\s*embed\s+url="([^"]+)"[^%]*%\}[ \t]*$/gm,
+ (_, indent, url) => renderEmbed(url, '', indent)
)
- .replace(/^[ \t]*\{%\s*embed\s+url="([^"]+)"[^%]*%\}[ \t]*$/gm, (_, url) => renderEmbed(url, ''))
);
}
diff --git a/scripts/lib/gitbook-blocks.test.mjs b/scripts/lib/gitbook-blocks.test.mjs
index 2e893d5..ec44c58 100644
--- a/scripts/lib/gitbook-blocks.test.mjs
+++ b/scripts/lib/gitbook-blocks.test.mjs
@@ -71,6 +71,35 @@ test('convertFile becomes a link whose text is the basename', () => {
);
});
+test('with no map at all convertFile keeps the placeholder form', () => {
+ assert.equal(
+ convertFile('{% file src="../../.gitbook/assets/DeliveryKnowledgeBase.csv" %}', { assets: null }),
+ '[DeliveryKnowledgeBase.csv](</.gitbook/assets/DeliveryKnowledgeBase.csv>)'
+ );
+});
+
+test('a mapped file block emits the map reference, unwrapped when it needs no angle brackets', () => {
+ const assets = {
+ 'DeliveryKnowledgeBase.csv': {
+ slug: 'deliveryknowledgebase.csv',
+ kind: 'file',
+ reference: '/files/deliveryknowledgebase.csv',
+ hash: 'z',
+ },
+ };
+ assert.equal(
+ convertFile('{% file src="../../.gitbook/assets/DeliveryKnowledgeBase.csv" %}', { assets }),
+ '[DeliveryKnowledgeBase.csv](/files/deliveryknowledgebase.csv)'
+ );
+});
+
+test('a file block missing from an existing map throws', () => {
+ assert.throws(
+ () => convertFile('{% file src="../../.gitbook/assets/gone.csv" %}', { assets: {} }),
+ /gone\.csv/
+ );
+});
+
test('an end-of-line entity is stripped, not turned into a trailing space', () => {
// "word " -> "word " would be a markdown hard break the live site does not render.
assert.equal(stripEntities('Put a JSON payload here. '), 'Put a JSON payload here.');
@@ -103,25 +132,42 @@ test('an unrecognised hint style throws rather than falling back to note', () =>
);
});
-test('a self-closing embed becomes an Embed element', () => {
- assert.equal(
- convertEmbeds('{% embed url="https://youtu.be/RhUc_mgkNl8" %}'),
- '<Embed url="https://youtu.be/RhUc_mgkNl8" />'
- );
+test('a self-closing embed becomes a raw iframe figure, needing no component', () => {
+ const out = convertEmbeds('{% embed url="https://youtu.be/RhUc_mgkNl8" %}');
+ assert.match(out, /^<figure class="od-embed">/);
+ assert.match(out, /src="https:\/\/www\.youtube-nocookie\.com\/embed\/RhUc_mgkNl8"/);
+ assert.match(out, /<\/iframe>/, 'the iframe is closed rather than self-closed, so it parses as both HTML and MDX');
+ assert.equal(/<figcaption/.test(out), false, 'no caption was given');
+ assert.equal(out.includes('<Embed'), false);
});
-test('an embed with a caption passes it as title', () => {
- assert.equal(
- convertEmbeds('{% embed url="https://www.loom.com/share/abc" %}\nBuilding an agent\n{% endembed %}'),
- '<Embed url="https://www.loom.com/share/abc" title="Building an agent" />'
- );
+test('an embed with a caption renders it as a figcaption and the iframe title', () => {
+ const out = convertEmbeds('{% embed url="https://www.loom.com/share/abc" %}\nBuilding an agent\n{% endembed %}');
+ assert.match(out, /src="https:\/\/www\.loom\.com\/embed\/abc"/);
+ assert.match(out, /title="Building an agent"/);
+ assert.match(out, /<figcaption>Building an agent<\/figcaption>/);
});
-test('a caption containing a double quote is escaped for the attribute', () => {
- assert.equal(
- convertEmbeds('{% embed url="https://youtu.be/x" %}\nThe "best" way\n{% endembed %}'),
- '<Embed url="https://youtu.be/x" title="The "best" way" />'
- );
+test('an uncaptioned embed still carries an accessible iframe title', () => {
+ const out = convertEmbeds('{% embed url="https://youtu.be/x" %}');
+ assert.match(out, /title="Embedded video"/);
+});
+
+test('a loom share URL keeps only its id, dropping any query string', () => {
+ const out = convertEmbeds('{% embed url="https://www.loom.com/share/abc?sid=123" %}');
+ assert.match(out, /src="https:\/\/www\.loom\.com\/embed\/abc"/);
+});
+
+test('a youtube watch URL becomes its nocookie embed form', () => {
+ const out = convertEmbeds('{% embed url="https://www.youtube.com/watch?v=abc123" %}');
+ assert.match(out, /src="https:\/\/www\.youtube-nocookie\.com\/embed\/abc123"/);
+});
+
+test('a caption containing a double quote is escaped in both places it appears', () => {
+ const out = convertEmbeds('{% embed url="https://youtu.be/x" %}\nThe "best" way\n{% endembed %}');
+ assert.match(out, /title="The "best" way"/);
+ assert.match(out, /<figcaption>The "best" way<\/figcaption>/);
+ assert.equal(out.includes('"best"'), false);
});
test('a non-video embed becomes a plain link and needs no component', () => {
@@ -146,7 +192,23 @@ test('a youtube.com/watch URL with no v parameter is not an embeddable shape', (
assert.equal(isVideoEmbed('https://www.youtube.com/watch'), false);
});
-test('a loom.com URL not in /share/ form becomes a plain link, not an Embed', () => {
+test('an embed inside a list item keeps that indentation', () => {
+ // Emitted at column 0 the figure closes the enclosing list, which on
+ // ai-agent-creation-overview breaks <Steps> — it requires a single <ol> child.
+ const out = convertEmbeds(' {% embed url="https://youtu.be/x" %}');
+ for (const line of out.split('\n')) {
+ assert.match(line, /^ \S/, `line not indented: ${JSON.stringify(line)}`);
+ }
+});
+
+test('an indented non-video embed keeps its indentation too', () => {
+ assert.equal(
+ convertEmbeds(' {% embed url="https://webaim.org/x" %}'),
+ ' [https://webaim.org/x](https://webaim.org/x)'
+ );
+});
+
+test('a loom.com URL not in /share/ form becomes a plain link, not an embed', () => {
assert.equal(
convertEmbeds('{% embed url="https://www.loom.com/embed/abc" %}'),
'[https://www.loom.com/embed/abc](https://www.loom.com/embed/abc)'
diff --git a/scripts/lib/light-theme.mjs b/scripts/lib/light-theme.mjs
new file mode 100644
index 0000000..6125c41
--- /dev/null
+++ b/scripts/lib/light-theme.mjs
@@ -0,0 +1,25 @@
+/**
+ * Pins the colour scheme to light in the served bytes.
+ *
+ * Starlight hard-codes `data-theme="dark"` on <html> in its own Page.astro and relies on an
+ * inline script to correct it, so a reader with JavaScript disabled gets the dark theme on a
+ * site that ships light-only, as GitBook's did. Rewriting the attribute in the emitted HTML
+ * puts the right value in the bytes Cloudflare serves without copying Starlight's 126-line
+ * Page component, which would drift silently on every upgrade with nothing to signal it.
+ *
+ * ThemeProvider's inline script stays: `astro:build:done` does not run under `astro dev`, so
+ * the script is what keeps the dev server light, and it holds up Starlight's
+ * `StarlightThemeProvider.updatePickers` contract.
+ */
+const HTML_TAG = /<html\b[^>]*>/;
+const DARK = 'data-theme="dark"';
+
+/** The page with its <html> tag pinned to light. Throws on any tag that is not the expected shape. */
+export function pinLightTheme(html) {
+ const tag = html.match(HTML_TAG);
+ if (!tag) throw new Error('pinLightTheme: no <html> tag');
+ if (!tag[0].includes(DARK)) {
+ throw new Error(`pinLightTheme: <html> does not carry ${DARK}: ${tag[0]}`);
+ }
+ return html.replace(HTML_TAG, (found) => found.replace(DARK, 'data-theme="light"'));
+}
diff --git a/scripts/lib/light-theme.test.mjs b/scripts/lib/light-theme.test.mjs
new file mode 100644
index 0000000..0da2c3b
--- /dev/null
+++ b/scripts/lib/light-theme.test.mjs
@@ -0,0 +1,37 @@
+import { test } from 'node:test';
+import assert from 'node:assert/strict';
+import { pinLightTheme } from './light-theme.mjs';
+
+const page = (htmlTag) => `<!DOCTYPE html>${htmlTag}<head></head><body>x</body></html>`;
+
+test('the dark attribute Starlight hard-codes becomes light', () => {
+ const out = pinLightTheme(page('<html lang="en" dir="ltr" data-theme="dark">'));
+ assert.match(out, /<html lang="en" dir="ltr" data-theme="light">/);
+});
+
+test('the other attributes on the tag are left alone', () => {
+ const out = pinLightTheme(page('<html lang="en" data-theme="dark" data-has-toc data-has-sidebar class="a">'));
+ assert.match(out, /<html lang="en" data-theme="light" data-has-toc data-has-sidebar class="a">/);
+});
+
+test('the rest of the document is untouched', () => {
+ const body = '<body><p>data-theme="dark"</p></body>';
+ const out = pinLightTheme(`<html data-theme="dark">${body}</html>`);
+ assert.equal(out.includes(body), true);
+});
+
+// Starlight could stop hard-coding the attribute, or rename it, on any upgrade. Silently
+// shipping the dark default to every reader without JavaScript is worse than a failed build,
+// so an unexpected tag is rejected rather than passed through — the same guard convertFigures
+// applies to a <figure> it does not recognise.
+test('a page with no data-theme attribute is rejected', () => {
+ assert.throws(() => pinLightTheme(page('<html lang="en">')), /data-theme="dark"/);
+});
+
+test('a page already pinned to light is rejected', () => {
+ assert.throws(() => pinLightTheme(page('<html data-theme="light">')), /data-theme="dark"/);
+});
+
+test('a document with no html tag is rejected', () => {
+ assert.throws(() => pinLightTheme('<body>x</body>'), /no <html> tag/);
+});
diff --git a/scripts/lib/link-cards.mjs b/scripts/lib/link-cards.mjs
index 5306f57..eec3938 100644
--- a/scripts/lib/link-cards.mjs
+++ b/scripts/lib/link-cards.mjs
@@ -5,6 +5,7 @@
* Both need route-map.json: a content-ref's inner link text is a raw filename, and GitBook
* substitutes the target page's title at render time.
*/
+import { ASSET_SRC, unescapeAssetName } from './asset-refs.mjs';
import { mapLines, protectCode } from './segments.mjs';
import { resolveSource } from './links.mjs';
@@ -21,6 +22,19 @@ function linkCard({ title, description, href }) {
return `<LinkCard ${parts.join(' ')} />`;
}
+/**
+ * Builds one CoverCard element — a LinkCard that also shows the row's cover image.
+ *
+ * The cover is passed as a /src/assets path rather than the `~/assets` alias, because
+ * CoverCard resolves it through import.meta.glob, which keys on the real path.
+ */
+function coverCard({ title, description, href, cover }) {
+ const parts = [`title="${attribute(title)}"`];
+ if (description) parts.push(`description="${attribute(description)}"`);
+ parts.push(`href="${href}"`, `cover="${cover}"`);
+ return `<CoverCard ${parts.join(' ')} />`;
+}
+
/**
* Builds one Card element for a row with no link target. `body` paragraphs become the
* element's children rather than an attribute, since Card (unlike LinkCard) has no
@@ -188,7 +202,9 @@ export function convertCardTables(text, ctx) {
`${ctx.source}: card "${title.text}" has a link target and ${body.length} body cells — LinkCard can only show one as its description`
);
}
- cards.push(linkCard({ title: title.text, description: body[0]?.text, href: hrefFor(target, ctx) }));
+ const cover = coverFor(cell, ctx);
+ const card = { title: title.text, description: body[0]?.text, href: hrefFor(target, ctx) };
+ cards.push(cover ? coverCard({ ...card, cover }) : linkCard(card));
} else {
cards.push(card({ title: title.text, body: body.map((c) => c.text) }));
}
@@ -202,19 +218,47 @@ export function convertCardTables(text, ctx) {
}
/**
- * Counts data-card-cover image references lost in conversion, for the Phase 3 handoff.
+ * The row's cover image as a /src/assets path, or null when it has none.
*
- * Also run under protectCode, for the same reason as convertCardTables: a card-table shown as a
- * code sample inside a fence must not be counted as a real, converting table.
+ * Resolved through asset-map.json, so the path is the slugified name assets.mjs actually
+ * wrote. Without a map — a checkout where assets.mjs has never run — no cover is emitted
+ * rather than a path that resolves to nothing, matching how figures.mjs degrades.
*/
-export function countDroppedCovers(text) {
- let total = 0;
+function coverFor(cell, ctx) {
+ for (const c of cell) {
+ const href = (c.match(/<a href="([^"]*\.(?:png|jpe?g|gif|svg|webp))"/i) ?? [])[1];
+ if (!href) continue;
+ const match = href.trim().match(ASSET_SRC);
+ const name = match ? unescapeAssetName(match[1]) : null;
+ const entry = name && ctx?.assets ? ctx.assets[name] : null;
+ if (!entry) return null;
+ return entry.reference.replace(/^~\//, '/src/');
+ }
+ return null;
+}
+
+/**
+ * Every data-card-cover image href in `text`, in document order.
+ *
+ * Card covers have no <LinkCard> equivalent, so conversion discards them. Phase 3 subtracts
+ * these from the asset copy set so a cover referenced nowhere else is not copied into
+ * src/assets/, where nothing would render it.
+ */
+export function coverTargets(text) {
+ const found = [];
protectCode(text, (masked) => {
for (const [table] of masked.matchAll(CARD_TABLE)) {
if (!/data-card-cover/.test(table)) continue;
- total += [...table.matchAll(/<a href="[^"]*\.(?:png|jpe?g|gif|svg|webp)"/gi)].length;
+ for (const [, href] of table.matchAll(/<a href="([^"]*\.(?:png|jpe?g|gif|svg|webp))"/gi)) {
+ found.push(href);
+ }
}
return masked;
});
- return total;
+ return found;
+}
+
+/** Counts data-card-cover image references lost in conversion, for the Phase 3 handoff. */
+export function countDroppedCovers(text) {
+ return coverTargets(text).length;
}
diff --git a/scripts/lib/link-cards.test.mjs b/scripts/lib/link-cards.test.mjs
index bfd0aeb..a8de7fd 100644
--- a/scripts/lib/link-cards.test.mjs
+++ b/scripts/lib/link-cards.test.mjs
@@ -1,6 +1,6 @@
import { test } from 'node:test';
import assert from 'node:assert/strict';
-import { convertCardTables, convertContentRefs, countDroppedCovers } from './link-cards.mjs';
+import { convertCardTables, convertContentRefs, countDroppedCovers, coverTargets } from './link-cards.mjs';
const routes = new Map([
['a/text-message.md', { url: '/design/text-message' }],
@@ -193,3 +193,94 @@ test('countDroppedCovers ignores a card-table shown as a code sample inside a fe
'```';
assert.equal(countDroppedCovers(input), 0);
});
+
+test('coverTargets returns each cover href in document order', () => {
+ const text = [
+ '<table data-view="cards" data-card-cover="true">',
+ '<tbody>',
+ '<tr><td><a href="../.gitbook/assets/one.png">one</a></td><td>Body</td></tr>',
+ '<tr><td><a href="../.gitbook/assets/two (1).png">two</a></td><td>Body</td></tr>',
+ '</tbody>',
+ '</table>',
+ ].join('\n');
+ assert.deepEqual(coverTargets(text), [
+ '../.gitbook/assets/one.png',
+ '../.gitbook/assets/two (1).png',
+ ]);
+});
+
+test('coverTargets ignores tables without a cover column', () => {
+ const text = '<table data-view="cards"><tbody><tr><td><a href="../.gitbook/assets/a.png">a</a></td></tr></tbody></table>';
+ assert.deepEqual(coverTargets(text), []);
+});
+
+test('coverTargets ignores a card table inside a fenced block', () => {
+ const text = [
+ '```html',
+ '<table data-view="cards" data-card-cover="true">',
+ '<tr><td><a href="../.gitbook/assets/fenced.png">x</a></td></tr>',
+ '</table>',
+ '```',
+ ].join('\n');
+ assert.deepEqual(coverTargets(text), []);
+});
+
+test('countDroppedCovers reports the same number of targets', () => {
+ const text = [
+ '<table data-view="cards" data-card-cover="true">',
+ '<tbody>',
+ '<tr><td><a href="../.gitbook/assets/one.png">one</a></td><td>Body</td></tr>',
+ '<tr><td><a href="../.gitbook/assets/two.png">two</a></td><td>Body</td></tr>',
+ '</tbody>',
+ '</table>',
+ ].join('\n');
+ assert.equal(countDroppedCovers(text), coverTargets(text).length);
+ assert.equal(countDroppedCovers(text), 2);
+});
+
+test('a card row with a cover becomes a CoverCard carrying the built asset path', () => {
+ const assets = { 'OD-basicmodel.png': { slug: 'od-basicmodel.png', reference: '~/assets/od-basicmodel.png' } };
+ const ctx = {
+ source: 'a/README.md',
+ routes: new Map([['a/b.md', { url: '/b' }]]),
+ titles: new Map(),
+ assets,
+ };
+ const table =
+ '<table data-view="cards"><thead><tr><th></th><th></th>' +
+ '<th data-hidden data-card-target data-type="content-ref"></th>' +
+ '<th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr>' +
+ '<td><a href="b.md"><strong>Model</strong></a></td><td>A description.</td>' +
+ '<td><a href="b.md">b</a></td>' +
+ '<td><a href="../.gitbook/assets/OD-basicmodel.png">OD-basicmodel.png</a></td>' +
+ '</tr></tbody></table>';
+ const out = convertCardTables(table, ctx);
+ assert.match(out, /<CoverCard /);
+ assert.match(out, /cover="\/src\/assets\/od-basicmodel\.png"/);
+ assert.match(out, /href="\/b"/);
+ assert.match(out, /title="Model"/);
+ assert.equal(out.includes('<LinkCard'), false);
+});
+
+test('a card row with no cover stays a LinkCard', () => {
+ const ctx = { source: 'a/README.md', routes: new Map([['a/b.md', { url: '/b' }]]), titles: new Map(), assets: {} };
+ const table =
+ '<table data-view="cards"><tbody><tr>' +
+ '<td><a href="b.md"><strong>Model</strong></a></td><td>A description.</td>' +
+ '</tr></tbody></table>';
+ const out = convertCardTables(table, ctx);
+ assert.match(out, /<LinkCard /);
+ assert.equal(out.includes('<CoverCard'), false);
+});
+
+test('without an asset map no cover is emitted, rather than a path that resolves to nothing', () => {
+ const ctx = { source: 'a/README.md', routes: new Map([['a/b.md', { url: '/b' }]]), titles: new Map(), assets: null };
+ const table =
+ '<table data-view="cards"><tbody><tr>' +
+ '<td><a href="b.md"><strong>Model</strong></a></td><td>Desc.</td>' +
+ '<td><a href="../.gitbook/assets/OD-basicmodel.png">x.png</a></td>' +
+ '</tr></tbody></table>';
+ const out = convertCardTables(table, ctx);
+ assert.equal(out.includes('<CoverCard'), false);
+ assert.match(out, /<LinkCard /);
+});
diff --git a/scripts/lib/links.mjs b/scripts/lib/links.mjs
index c2e6eb6..4675ff6 100644
--- a/scripts/lib/links.mjs
+++ b/scripts/lib/links.mjs
@@ -62,23 +62,45 @@ export function resolveSource(fromSource, target) {
return path.posix.normalize(joined).replace(/^(\.\.\/)+/, '');
}
-/** Rewrites every internal page link in `text` to its route URL. Throws on any that misses. */
+/** A raw HTML anchor's href. GitBook's export leaves these inside table cells. */
+const HTML_HREF = /(<a\b[^>]*?\bhref=")([^"]*)(")/gi;
+
+/**
+ * Rewrites every internal page link in `text` to its route URL. Throws on any that misses.
+ *
+ * Covers both markdown links and raw HTML anchors. The corpus carries relative `.md` links
+ * in both forms, and handling only the first shipped
+ * `<a href="button-message.md">Button Message</a>` on twilio-content-template-message as a
+ * 404 — the same page links the same target correctly two lines further down, in markdown.
+ * A link inside a code fence is left alone by protectCode, so an HTML sample showing an
+ * anchor is not rewritten.
+ */
export function rewriteLinks(text, { source, routes }) {
+ const routeFor = (target) => {
+ const resolved = resolveSource(source, target);
+ if (resolved === null) return null;
+ const route = routes.get(resolved);
+ if (!route) {
+ throw new Error(`${source}: link target does not resolve to a page: ${target} -> ${resolved}`);
+ }
+ const anchor = target.includes('#') ? target.slice(target.indexOf('#')) : '';
+ return `${route.url}${anchor}`;
+ };
+
return protectCode(text, (masked) => {
let out = '';
let cursor = 0;
for (const { start, end, target, angled } of extractTargets(masked)) {
- const resolved = resolveSource(source, target);
- if (resolved === null) continue;
- const route = routes.get(resolved);
- if (!route) {
- throw new Error(`${source}: link target does not resolve to a page: ${target} -> ${resolved}`);
- }
- const anchor = target.includes('#') ? target.slice(target.indexOf('#')) : '';
- const url = `${route.url}${anchor}`;
+ const url = routeFor(target);
+ if (url === null) continue;
out += masked.slice(cursor, start) + (angled ? `<${url}>` : url);
cursor = end;
}
- return out + masked.slice(cursor);
+ const withMarkdown = out + masked.slice(cursor);
+
+ return withMarkdown.replace(HTML_HREF, (whole, open, href, close) => {
+ const url = routeFor(href);
+ return url === null ? whole : `${open}${url}${close}`;
+ });
});
}
diff --git a/scripts/lib/links.test.mjs b/scripts/lib/links.test.mjs
index 9865f6e..db3b709 100644
--- a/scripts/lib/links.test.mjs
+++ b/scripts/lib/links.test.mjs
@@ -86,3 +86,39 @@ test('rewriteLinks leaves asset references untouched for Phase 3', () => {
test('rewriteLinks throws, naming file and target, on an unresolved page link', () => {
assert.throws(() => rewriteLinks('[Q](missing.md)', ctx), /a\/start\.md.*missing\.md/s);
});
+
+test('a relative .md link inside a raw HTML anchor is rewritten too', () => {
+ // twilio-content-template-message carries its Button Message link as a raw <a> inside an
+ // HTML table cell. rewriteLinks only ever handled markdown links, so this one shipped as
+ // href="button-message.md" and 404'd, even though the page exists.
+ const ctx = {
+ source: 'a/b.md',
+ routes: new Map([['a/button-message.md', { url: '/msg/button-message' }]]),
+ };
+ assert.equal(
+ rewriteLinks('See <a href="button-message.md">Button Message</a>.', ctx),
+ 'See <a href="/msg/button-message">Button Message</a>.'
+ );
+});
+
+test('an anchor fragment on a raw HTML link is preserved', () => {
+ const ctx = { source: 'a/b.md', routes: new Map([['a/c.md', { url: '/c' }]]) };
+ assert.equal(
+ rewriteLinks('<a href="c.md#part-two">x</a>', ctx),
+ '<a href="/c#part-two">x</a>'
+ );
+});
+
+test('a raw HTML anchor to an external URL or in-page anchor is left alone', () => {
+ const ctx = { source: 'a/b.md', routes: new Map() };
+ const external = '<a href="https://example.com">x</a>';
+ const inPage = '<a href="#what-is-a-list-message">x</a>';
+ assert.equal(rewriteLinks(external, ctx), external);
+ assert.equal(rewriteLinks(inPage, ctx), inPage);
+});
+
+test('a raw HTML anchor inside a fenced code block is left alone', () => {
+ const ctx = { source: 'a/b.md', routes: new Map([['a/c.md', { url: '/c' }]]) };
+ const fence = '```html\n<a href="c.md">x</a>\n```';
+ assert.equal(rewriteLinks(fence, ctx), fence);
+});
diff --git a/scripts/lib/rehype-figures.mjs b/scripts/lib/rehype-figures.mjs
new file mode 100644
index 0000000..b0aae44
--- /dev/null
+++ b/scripts/lib/rehype-figures.mjs
@@ -0,0 +1,90 @@
+/**
+ * Pairs an image with the caption paragraph beneath it into a <figure>/<figcaption>.
+ *
+ * Markdown has no figure syntax, so scripts/lib/figures.mjs emits a GitBook <figcaption>
+ * as an italic paragraph following the image. That leaves two separate blocks, which is
+ * wrong in two ways: the caption carries no relationship to its image for a screen reader,
+ * and inside GitBook's image wrapper divs — which lay figures out in a row — the caption
+ * becomes a flex item of its own, taking width from the row and forcing it to wrap.
+ *
+ * Pairing is inferred rather than marked, because markdown offers no channel to mark it.
+ * That inference is exact on this corpus: the source holds 329 figures with a non-empty
+ * caption, and the generated markdown holds exactly 329 italic-only paragraphs directly
+ * following an image. The one further italic-only paragraph is authored prose that
+ * follows no image and is left alone. A caption is only ever taken from a paragraph whose
+ * sole content is emphasis, immediately after a paragraph whose sole content is an image.
+ *
+ * The 101 figures whose caption is empty emit the image alone and stay a plain paragraph:
+ * a <figure> with nothing to caption would add markup without adding meaning.
+ *
+ * The wrapping <em> is dropped and its children kept, because GitBook sets its captions
+ * in roman, not italic; the italics were only ever markdown's way of carrying them.
+ */
+
+/** Element children, ignoring the whitespace text nodes between block elements. */
+function elementChildren(node) {
+ return (node.children ?? []).filter(
+ (child) => child.type !== 'text' || child.value.trim() !== ''
+ );
+}
+
+/** The single element a node contains, or null if it holds anything else. */
+function soleElement(node, tagName) {
+ const children = elementChildren(node);
+ if (children.length !== 1) return null;
+ const [only] = children;
+ return only.type === 'element' && only.tagName === tagName ? only : null;
+}
+
+export function rehypeFigures() {
+ return (tree) => {
+ const visit = (node) => {
+ const children = node.children;
+ if (Array.isArray(children)) {
+ const out = [];
+ for (let i = 0; i < children.length; i++) {
+ const current = children[i];
+
+ const image = current.type === 'element' && current.tagName === 'p'
+ ? soleElement(current, 'img')
+ : null;
+
+ if (image) {
+ // Look past whitespace for the next element, which may be the caption.
+ let next = i + 1;
+ while (next < children.length && children[next].type === 'text' && children[next].value.trim() === '') {
+ next++;
+ }
+ const sibling = children[next];
+ const emphasis = sibling && sibling.type === 'element' && sibling.tagName === 'p'
+ ? soleElement(sibling, 'em')
+ : null;
+
+ if (emphasis) {
+ // The figure takes the image's width. A caption is usually longer than the
+ // thumbnail above it, so otherwise the figure's intrinsic width is the
+ // caption's, and a row of four 188px images no longer fits its container.
+ const width = /(?:^|;)(width:\d+px)/.exec(image.properties?.style ?? '')?.[1];
+ out.push({
+ type: 'element',
+ tagName: 'figure',
+ properties: width ? { style: width } : {},
+ children: [
+ image,
+ { type: 'element', tagName: 'figcaption', properties: {}, children: emphasis.children },
+ ],
+ });
+ i = next;
+ continue;
+ }
+ }
+
+ visit(current);
+ out.push(current);
+ }
+ node.children = out;
+ }
+ };
+ visit(tree);
+ };
+}
diff --git a/scripts/lib/rehype-figures.test.mjs b/scripts/lib/rehype-figures.test.mjs
new file mode 100644
index 0000000..e124895
--- /dev/null
+++ b/scripts/lib/rehype-figures.test.mjs
@@ -0,0 +1,95 @@
+import { test } from 'node:test';
+import assert from 'node:assert/strict';
+import { rehypeFigures } from './rehype-figures.mjs';
+
+const el = (tagName, children = [], properties = {}) => ({ type: 'element', tagName, properties, children });
+const text = (value) => ({ type: 'text', value });
+const img = (props = { src: '/a.png' }) => el('img', [], props);
+const root = (...children) => ({ type: 'root', properties: {}, children });
+
+const run = (tree) => {
+ rehypeFigures()(tree);
+ return tree;
+};
+
+test('an image paragraph followed by an italic paragraph becomes a figure', () => {
+ const tree = run(root(el('p', [img()]), text('\n'), el('p', [el('em', [text('A caption')])])));
+ assert.equal(tree.children.length, 1);
+ const [figure] = tree.children;
+ assert.equal(figure.tagName, 'figure');
+ assert.equal(figure.children[0].tagName, 'img');
+ assert.equal(figure.children[1].tagName, 'figcaption');
+ assert.deepEqual(figure.children[1].children, [text('A caption')]);
+});
+
+test('the caption keeps its inline markup but loses the wrapping emphasis', () => {
+ const caption = el('em', [text('See '), el('code', [text('attr')])]);
+ const tree = run(root(el('p', [img()]), el('p', [caption])));
+ const figcaption = tree.children[0].children[1];
+ assert.equal(figcaption.children.length, 2);
+ assert.equal(figcaption.children[1].tagName, 'code');
+ assert.equal(figcaption.children.some((c) => c.tagName === 'em'), false);
+});
+
+test('an image with no caption is left as it was', () => {
+ const tree = run(root(el('p', [img()]), el('p', [text('Ordinary prose')])));
+ assert.equal(tree.children.length, 2);
+ assert.equal(tree.children[0].tagName, 'p');
+});
+
+test('an italic paragraph not preceded by an image is left alone', () => {
+ const tree = run(root(el('p', [text('prose')]), el('p', [el('em', [text('emphasis')])])));
+ assert.equal(tree.children.length, 2);
+ assert.equal(tree.children.every((c) => c.tagName === 'p'), true);
+});
+
+test('a paragraph holding an image plus other text is not a figure', () => {
+ const tree = run(root(el('p', [img(), text(' trailing')]), el('p', [el('em', [text('c')])])));
+ assert.equal(tree.children.length, 2);
+ assert.equal(tree.children[0].tagName, 'p');
+});
+
+test('an italic paragraph with trailing text is not treated as a caption', () => {
+ const tree = run(root(el('p', [img()]), el('p', [el('em', [text('c')]), text(' and more')])));
+ assert.equal(tree.children.length, 2);
+});
+
+test('figures are found inside a wrapper div', () => {
+ const div = el('div', [el('p', [img()]), el('p', [el('em', [text('cap')])])]);
+ const tree = run(root(div));
+ assert.equal(div.children.length, 1);
+ assert.equal(div.children[0].tagName, 'figure');
+});
+
+test('consecutive image and caption pairs each become their own figure', () => {
+ const tree = run(
+ root(
+ el('p', [img({ src: '/a.png' })]),
+ el('p', [el('em', [text('one')])]),
+ el('p', [img({ src: '/b.png' })]),
+ el('p', [el('em', [text('two')])])
+ )
+ );
+ assert.equal(tree.children.length, 2);
+ assert.deepEqual(tree.children.map((c) => c.tagName), ['figure', 'figure']);
+ assert.equal(tree.children[1].children[1].children[0].value, 'two');
+});
+
+test("the figure takes the image's width so the caption cannot widen the row", () => {
+ // A caption is usually longer than a small thumbnail, so without this the figure's
+ // intrinsic width is the caption's and a row of four 188px images no longer fits.
+ const tree = run(
+ root(el('p', [img({ src: '/a.png', style: 'width:188px' })]), el('p', [el('em', [text('A fairly long caption')])]))
+ );
+ assert.equal(tree.children[0].properties.style, 'width:188px');
+});
+
+test('a figure whose image has no width gets none', () => {
+ const tree = run(root(el('p', [img()]), el('p', [el('em', [text('c')])])));
+ assert.equal(tree.children[0].properties.style, undefined);
+});
+
+test('an image whose paragraph carries a link is left alone', () => {
+ const tree = run(root(el('p', [el('a', [img()])]), el('p', [el('em', [text('c')])])));
+ assert.equal(tree.children[0].tagName, 'p');
+});
diff --git a/scripts/lib/rehype-image-width.mjs b/scripts/lib/rehype-image-width.mjs
new file mode 100644
index 0000000..828bd67
--- /dev/null
+++ b/scripts/lib/rehype-image-width.mjs
@@ -0,0 +1,40 @@
+/**
+ * Applies the per-image widths GitBook authored, which markdown cannot carry.
+ *
+ * 64 `<img width="...">` attributes across the corpus set an image's display width — 21
+ * inside the wrapper divs that lay figures out in a row, 43 on standalone figures. GitBook
+ * honours all of them; without this an image the author sized to 188px renders at the full
+ * content width, and one 1118x1670 screenshot renders 720x1075.
+ *
+ * scripts/lib/figures.mjs writes the width into the markdown title slot, the only channel
+ * markdown offers that survives into the HTML without introducing block markup. A raw <img>
+ * would bypass astro:assets and ship the image unoptimised; a wrapper <div> is block markup
+ * and would break the enclosing list for the one width-bearing figure that sits inside a
+ * list item. This plugin turns that title into an inline width and removes it, so no title
+ * reaches the page and nothing shows a stray tooltip.
+ *
+ * Only an all-digit, positive title is consumed. A title of any other shape is left alone,
+ * so a genuine tooltip is never eaten.
+ */
+
+/** Walks every element in a hast tree. */
+function visitElements(node, fn) {
+ if (node.type === 'element') fn(node);
+ for (const child of node.children ?? []) visitElements(child, fn);
+}
+
+export function rehypeImageWidth() {
+ return (tree) => {
+ visitElements(tree, (node) => {
+ if (node.tagName !== 'img') return;
+ const { title } = node.properties ?? {};
+ if (typeof title !== 'string' || !/^\d+$/.test(title)) return;
+ const width = Number(title);
+ if (!Number.isInteger(width) || width <= 0) return;
+
+ delete node.properties.title;
+ const existing = node.properties.style;
+ node.properties.style = existing ? `${existing};width:${width}px` : `width:${width}px`;
+ });
+ };
+}
diff --git a/scripts/lib/rehype-image-width.test.mjs b/scripts/lib/rehype-image-width.test.mjs
new file mode 100644
index 0000000..c15648a
--- /dev/null
+++ b/scripts/lib/rehype-image-width.test.mjs
@@ -0,0 +1,58 @@
+import { test } from 'node:test';
+import assert from 'node:assert/strict';
+import { rehypeImageWidth } from './rehype-image-width.mjs';
+
+/** Minimal hast helpers — enough to exercise the plugin without pulling in a parser. */
+const img = (properties) => ({ type: 'element', tagName: 'img', properties, children: [] });
+const tree = (...children) => ({ type: 'root', children });
+
+const run = (node) => {
+ rehypeImageWidth()(node);
+ return node;
+};
+
+test('a numeric title becomes a width and the title is removed', () => {
+ const node = img({ src: '/a.png', alt: '', title: '375' });
+ run(tree(node));
+ assert.equal(node.properties.title, undefined);
+ assert.equal(node.properties.style, 'width:375px');
+});
+
+test('an existing style is preserved and the width appended', () => {
+ const node = img({ src: '/a.png', title: '188', style: 'border:0' });
+ run(tree(node));
+ assert.equal(node.properties.style, 'border:0;width:188px');
+});
+
+test('a non-numeric title is left alone as a real title', () => {
+ const node = img({ src: '/a.png', title: 'A real tooltip' });
+ run(tree(node));
+ assert.equal(node.properties.title, 'A real tooltip');
+ assert.equal(node.properties.style, undefined);
+});
+
+test('an image with no title is untouched', () => {
+ const node = img({ src: '/a.png', alt: 'x' });
+ run(tree(node));
+ assert.deepEqual(node.properties, { src: '/a.png', alt: 'x' });
+});
+
+test('a title on a non-image element is left alone', () => {
+ const node = { type: 'element', tagName: 'a', properties: { href: '/x', title: '375' }, children: [] };
+ run(tree(node));
+ assert.equal(node.properties.title, '375');
+ assert.equal(node.properties.style, undefined);
+});
+
+test('nested images are reached', () => {
+ const node = img({ src: '/a.png', title: '200' });
+ run(tree({ type: 'element', tagName: 'p', properties: {}, children: [node] }));
+ assert.equal(node.properties.style, 'width:200px');
+});
+
+test('a zero or negative width is treated as a real title, not a width', () => {
+ const zero = img({ src: '/a.png', title: '0' });
+ run(tree(zero));
+ assert.equal(zero.properties.title, '0');
+ assert.equal(zero.properties.style, undefined);
+});
diff --git a/scripts/lib/sidebar-tree.mjs b/scripts/lib/sidebar-tree.mjs
index 996a7be..2c78a80 100644
--- a/scripts/lib/sidebar-tree.mjs
+++ b/scripts/lib/sidebar-tree.mjs
@@ -30,11 +30,17 @@ export function buildSidebar(entries, slugFor) {
}
// A node with children becomes a group. Starlight cannot link a group, so the page keeps
- // its own entry as that group's first item, carrying the same label.
+ // its own entry as that group's first item, carrying the same label; the Sidebar override
+ // promotes that first item into the group's own row rather than repeating it.
+ //
+ // Nested groups start collapsed. Starlight opens a collapsed group when it contains the
+ // current page, so the nav opens along the path to the page being read and nothing else —
+ // GitBook's behaviour. Sections are deliberately left expanded, as they are there.
const shape = (node) =>
node.children.length
? {
label: node.label,
+ collapsed: true,
items: [{ label: node.label, slug: node.slug }, ...node.children.map(shape)],
}
: { label: node.label, slug: node.slug };
diff --git a/scripts/lib/sidebar-tree.test.mjs b/scripts/lib/sidebar-tree.test.mjs
index 1128fce..d8f691d 100644
--- a/scripts/lib/sidebar-tree.test.mjs
+++ b/scripts/lib/sidebar-tree.test.mjs
@@ -23,6 +23,7 @@ test('a parent page becomes a group whose first item is the page itself', () =>
items: [
{
label: 'Message design',
+ collapsed: true,
items: [
{ label: 'Message design', slug: 'design' },
{ label: 'Text message', slug: 'design/text' },
@@ -42,6 +43,7 @@ test('nesting continues to arbitrary depth', () => {
const [group] = buildSidebar(entries, slugFor);
assert.deepEqual(group.items[0].items[1], {
label: 'B',
+ collapsed: true,
items: [
{ label: 'B', slug: 'a/b' },
{ label: 'C', slug: 'a/b/c' },
@@ -49,6 +51,25 @@ test('nesting continues to arbitrary depth', () => {
});
});
+test('a nested group starts collapsed, a section does not', () => {
+ const entries = [
+ { depth: 0, label: 'Message design', source: 'design/README.md', section },
+ { depth: 2, label: 'Text message', source: 'design/text.md', section },
+ ];
+ const [group] = buildSidebar(entries, slugFor);
+ // Starlight opens a collapsed group when it holds the current page, so collapsing
+ // nested groups leaves the nav open exactly along the path to the page being read —
+ // which is what GitBook shows. Sections stay expanded there, so they are left alone.
+ assert.equal(group.collapsed, undefined);
+ assert.equal(group.items[0].collapsed, true);
+});
+
+test('a leaf carries no collapsed flag', () => {
+ const entries = [{ depth: 0, label: 'Model', source: 'model.md', section }];
+ const [group] = buildSidebar(entries, slugFor);
+ assert.equal('collapsed' in group.items[0], false);
+});
+
test('the root README becomes the empty slug', () => {
const entries = [{ depth: 0, label: 'Introduction', source: 'README.md', section }];
assert.deepEqual(buildSidebar(entries, slugFor)[0].items, [{ label: 'Introduction', slug: '' }]);
diff --git a/scripts/sidebar.mjs b/scripts/sidebar.mjs
index 7198f0c..6f8675a 100644
--- a/scripts/sidebar.mjs
+++ b/scripts/sidebar.mjs
@@ -28,12 +28,21 @@ const slugFor = (source) => {
const entries = parseSummary(readFileSync(`${root}/source/SUMMARY.md`, 'utf8'));
const sidebar = buildSidebar(entries, slugFor);
-// A leaf page is one nav row. A parent page is two: the group header (unlinkable, so it
-// repeats the page as the group's first item) plus that first item itself. Top-level
-// sections are structural buckets, not pages, so they never add a row for themselves.
+// A parent page appears twice in this data: once as the group and once as that group's
+// first item, because a Starlight group cannot carry a link. src/components/
+// SidebarSublist.astro folds the two back into a single clickable row, so the rendered
+// nav is one row per page. Both numbers are reported: a gap between them that is not the
+// parent-page count means the two sides have drifted apart. Top-level sections are
+// structural buckets, not pages, and never add a row for themselves.
const countItems = (items) =>
items.reduce((total, item) => total + 1 + (item.items ? countItems(item.items) : 0), 0);
const count = (groups) => groups.reduce((total, group) => total + countItems(group.items), 0);
+const countParents = (items) =>
+ items.reduce(
+ (total, item) => total + (item.items ? 1 + countParents(item.items) : 0),
+ 0
+ );
+const parents = sidebar.reduce((total, group) => total + countParents(group.items), 0);
writeFileSync(
OUT,
@@ -42,7 +51,8 @@ writeFileSync(
);
console.log(`sections : ${sidebar.length}`);
-console.log(`nav entries : ${count(sidebar)}`);
+console.log(`data entries : ${count(sidebar)} (${parents} parent pages counted twice)`);
+console.log(`rendered rows: ${count(sidebar) - parents}`);
console.log(`wrote ${OUT}`);
if (entries.length !== 204) {
diff --git a/scripts/verify-images.mjs b/scripts/verify-images.mjs
new file mode 100644
index 0000000..00ecc15
--- /dev/null
+++ b/scripts/verify-images.mjs
@@ -0,0 +1,137 @@
+/**
+ * Checks every image in the built site and writes the alt-text work list.
+ *
+ * Blocking: every <img> carries an alt attribute, and every <img> src resolves to a file the
+ * build actually emitted. That is the brief's Phase 5 image check, done against the bytes on
+ * disk rather than over the network.
+ *
+ * Reporting: the 455 content images that ship with an empty alt, written to
+ * reports/alt-text-todo.md for the docs team to fill in. Rows are read from the authored
+ * pages under src/content/docs/, which is both the source of truth and what a writer edits,
+ * and the row count is checked against the built output: a work list that has drifted from
+ * what ships would read as complete work while describing a site nobody is serving.
+ */
+import { existsSync, mkdirSync, readdirSync, readFileSync, writeFileSync } from 'node:fs';
+import { dirname, resolve } from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { emptyAltImages } from './lib/alt-audit.mjs';
+
+const root = resolve(dirname(fileURLToPath(import.meta.url)), '..');
+const DIST = `${root}/dist`;
+const OUT = `${root}/reports/alt-text-todo.md`;
+
+if (!existsSync(DIST)) {
+ console.error('dist/ not found — run `npm run build` first');
+ process.exit(1);
+}
+
+const routes = JSON.parse(readFileSync(`${root}/route-map.json`, 'utf8'));
+
+// --- the built site -------------------------------------------------------
+
+const files = readdirSync(DIST, { recursive: true })
+ .map(String)
+ .filter((f) => f.endsWith('.html'));
+
+let images = 0;
+const noAltAttribute = [];
+const missingFiles = [];
+let emptyAltInBuild = 0;
+let coverImages = 0;
+
+for (const file of files) {
+ const html = readFileSync(`${DIST}/${file}`, 'utf8');
+ const main = html.match(/<main\b[\s\S]*?<\/main>/)?.[0] ?? '';
+ const covers = [...main.matchAll(/<a\b[^>]*cover-card[\s\S]*?<\/a>/g)].map((m) => m[0]).join('');
+ const coverTags = new Set([...covers.matchAll(/<img\b[^>]*>/g)].map((m) => m[0]));
+ for (const [tag] of html.matchAll(/<img\b[^>]*>/g)) {
+ images++;
+ const value = tag.match(/\balt="([^"]*)"/);
+ // Astro serialises alt="" as a bare `alt`, which is present-and-empty, not missing.
+ if (!value && !/\balt(?=[\s>])/.test(tag)) noAltAttribute.push(`${file}: ${tag.slice(0, 120)}`);
+ const src = tag.match(/\bsrc="([^"]*)"/)?.[1];
+ if (src?.startsWith('/') && !existsSync(`${DIST}${src.split('?')[0]}`)) {
+ missingFiles.push(`${file}: ${src}`);
+ }
+ if (!main.includes(tag)) continue; // page chrome: the logo
+ if (coverTags.has(tag)) { coverImages++; continue; }
+ if (!value?.[1]) emptyAltInBuild++;
+ }
+}
+
+// --- the work list --------------------------------------------------------
+
+const found = [];
+for (const route of routes) {
+ const page = [`${root}/src/content/docs/${route.target}`, `${root}/src/content/docs/${route.target}x`]
+ .find((path) => existsSync(path));
+ if (!page) continue;
+ for (const image of emptyAltImages(readFileSync(page, 'utf8'))) {
+ found.push({ url: route.url, title: route.title, ...image });
+ }
+}
+
+// Uncaptioned first: those images are announced as nothing at all, while a captioned one at
+// least has text beside it. Document order is kept within each group.
+const rows = [...found.filter((r) => !r.caption), ...found.filter((r) => r.caption)];
+const withCaption = rows.filter((r) => r.caption).length;
+
+const escapePipes = (s) => s.replace(/\|/g, '\\|');
+/** Hotlinked third-party images carry 200-character URLs that would make the table unreadable. */
+const shorten = (s) => (s.length > 64 ? `${s.slice(0, 63)}…` : s);
+
+const report = [
+ '# Images with no alt text',
+ '',
+ 'Generated by `node scripts/verify-images.mjs`. Do not edit by hand.',
+ '',
+ `${rows.length} images across the documentation ship with an empty \`alt\` attribute, so a`,
+ 'screen reader announces nothing for them.',
+ '',
+ 'The fix belongs in this repository. `src/content/docs/` is the source of truth and is edited',
+ 'by hand: give the image alt text in the markdown — `` — and it',
+ 'ships on the next deploy.',
+ '',
+ `The ${rows.length - withCaption} rows with no caption come first: nothing is announced for them at all, and they`,
+ `are the ones worth doing first. The remaining ${withCaption} sit under a visible caption, reproduced`,
+ 'below. That caption is already announced, so alt text for those should describe what the',
+ 'image *shows* rather than repeat it — duplicating it makes a screen reader read the same',
+ 'sentence twice.',
+ '',
+ '| Page | Image | Existing caption |',
+ '|---|---|---|',
+ ...rows.map((r) => `| [${escapePipes(r.title)}](https://docs.opendialog.ai${r.url}) | \`${escapePipes(shorten(r.asset))}\` | ${escapePipes(r.caption)} |`),
+ '',
+].join('\n');
+
+mkdirSync(dirname(OUT), { recursive: true });
+writeFileSync(OUT, report);
+
+// --- results --------------------------------------------------------------
+
+console.log(`built images : ${images}`);
+console.log(`no alt attribute : ${noAltAttribute.length}`);
+console.log(`src with no file : ${missingFiles.length}`);
+console.log(`cover images : ${coverImages}`);
+console.log(`empty alt in build : ${emptyAltInBuild}`);
+console.log(`work-list rows : ${rows.length} (${withCaption} with a caption)`);
+console.log(`\nwrote ${OUT}`);
+
+for (const [label, list] of [
+ ['\nImages with no alt attribute at all:', noAltAttribute],
+ ['\nImages whose src the build did not emit:', missingFiles],
+]) {
+ if (!list.length) continue;
+ console.error(label);
+ for (const item of list) console.error(` ${item}`);
+}
+
+if (rows.length !== emptyAltInBuild) {
+ console.error(
+ `\nThe work list has ${rows.length} rows but the build ships ${emptyAltInBuild} empty-alt` +
+ ' content images. The report describes a site that is not being served.'
+ );
+}
+
+if (noAltAttribute.length || missingFiles.length || rows.length !== emptyAltInBuild) process.exit(1);
+console.log('\nimage check: OK');
diff --git a/scripts/verify-links.mjs b/scripts/verify-links.mjs
new file mode 100644
index 0000000..76862bf
--- /dev/null
+++ b/scripts/verify-links.mjs
@@ -0,0 +1,95 @@
+/**
+ * Checks every internal link and in-page anchor in the built site.
+ *
+ * Gates on regressions, not on absolute health: 25 of the defects it finds came across from
+ * GitBook, are present in source/, and cannot be fixed here without editing documentation
+ * prose. Those live in reports/inherited-broken-links.json. Anything outside that inventory
+ * fails the run, and so does an inventory entry that is no longer broken, so the list cannot
+ * quietly rot into an excuse.
+ *
+ * A link target is a page when the build emitted HTML for it, and a file when the build
+ * emitted anything else at that path — the one CSV and the one MP4 are linked from prose and
+ * are real destinations, not broken pages.
+ */
+import { existsSync, readdirSync, readFileSync } from 'node:fs';
+import { dirname, resolve } from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { extractHrefs, extractIds, pageUrl, resolveHref } from './lib/dist-links.mjs';
+
+const root = resolve(dirname(fileURLToPath(import.meta.url)), '..');
+const DIST = `${root}/dist`;
+const INVENTORY = `${root}/reports/inherited-broken-links.json`;
+
+if (!existsSync(DIST)) {
+ console.error('dist/ not found — run `npm run build` first');
+ process.exit(1);
+}
+
+const inventory = JSON.parse(readFileSync(INVENTORY, 'utf8'));
+const knownLinks = new Set(inventory.links.map((l) => `${l.from} -> ${l.href}`));
+const knownAnchors = new Set(inventory.anchors);
+
+const files = readdirSync(DIST, { recursive: true })
+ .map(String)
+ .filter((f) => f.endsWith('.html'));
+
+const pages = new Map();
+for (const file of files) {
+ const html = readFileSync(`${DIST}/${file}`, 'utf8');
+ pages.set(pageUrl(file), {
+ html,
+ main: html.match(/<main\b[\s\S]*?<\/main>/)?.[0] ?? '',
+ ids: extractIds(html),
+ });
+}
+
+const stats = { links: 0, anchors: 0 };
+const brokenLinks = [];
+const brokenAnchors = [];
+const hitLinks = new Set();
+const hitAnchors = new Set();
+
+for (const [url, page] of pages) {
+ for (const href of extractHrefs(page.main)) {
+ const dest = resolveHref(url, href);
+ if (!dest) continue;
+ stats.links++;
+ if (dest.hash) stats.anchors++;
+ const target = pages.get(dest.path);
+ if (!target) {
+ // Not a page. A real file the build emitted — the CSV, the MP4 — is a valid destination.
+ if (existsSync(`${DIST}${dest.path}`)) continue;
+ const key = `${url} -> ${href}`;
+ knownLinks.has(key) ? hitLinks.add(key) : brokenLinks.push(key);
+ continue;
+ }
+ if (!dest.hash || target.ids.has(dest.hash)) continue;
+ const key = `${dest.path}#${dest.hash}`;
+ knownAnchors.has(key) ? hitAnchors.add(key) : brokenAnchors.push(`${url} -> ${href}`);
+ }
+}
+
+const staleLinks = [...knownLinks].filter((k) => !hitLinks.has(k));
+const staleAnchors = [...knownAnchors].filter((k) => !hitAnchors.has(k));
+
+console.log(`pages : ${pages.size}`);
+console.log(`content links : ${stats.links}`);
+console.log(`content anchors : ${stats.anchors}`);
+console.log(`inherited defects : ${hitLinks.size} links, ${hitAnchors.size} anchors`);
+console.log(`new broken links : ${brokenLinks.length}`);
+console.log(`new broken anchors : ${brokenAnchors.length}`);
+
+for (const [label, list] of [
+ ['\nInternal links with no target:', brokenLinks],
+ ['\nAnchors with no matching id:', brokenAnchors],
+ ['\nInventory entries that now resolve — remove them:', [...staleLinks, ...staleAnchors]],
+]) {
+ if (!list.length) continue;
+ console.error(label);
+ for (const item of list) console.error(` ${item}`);
+}
+
+if (brokenLinks.length || brokenAnchors.length || staleLinks.length || staleAnchors.length) {
+ process.exit(1);
+}
+console.log('\nlink check: OK');
diff --git a/scripts/verify-live.mjs b/scripts/verify-live.mjs
new file mode 100644
index 0000000..8a85f43
--- /dev/null
+++ b/scripts/verify-live.mjs
@@ -0,0 +1,74 @@
+/**
+ * Fetches every URL the live GitBook sitemap listed and reports anything that is not 200.
+ *
+ * The site is cut over, so this is a check on production traffic rather than a pre-launch
+ * target. GitBook no longer answers on the domain, so reference/sitemap-pages.xml is the only
+ * surviving record of what the URL set was; it is a committed snapshot and is read from disk,
+ * never fetched, so it outlives GitBook.
+ *
+ * The CSV, the MP4 and the sitemap index are checked alongside the pages: none appears in the
+ * sitemap, all three are reachable from prose or from crawlers, and all three would be easy to
+ * lose in an asset-pipeline change without a single page 404ing.
+ *
+ * Usage:
+ * node scripts/verify-live.mjs # https://docs.opendialog.ai
+ * node scripts/verify-live.mjs https://staging.example # any other origin
+ */
+import { readFileSync } from 'node:fs';
+import { dirname, resolve } from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+const root = resolve(dirname(fileURLToPath(import.meta.url)), '..');
+const SITEMAP = `${root}/reference/sitemap-pages.xml`;
+const CONCURRENCY = 8;
+
+const base = (process.argv[2] ?? 'https://docs.opendialog.ai').replace(/\/$/, '');
+
+const paths = [
+ ...[...readFileSync(SITEMAP, 'utf8').matchAll(/<loc>([^<]*)<\/loc>/g)]
+ .map((m) => m[1].replace(/^https:\/\/docs\.opendialog\.ai/, '').replace(/\/$/, ''))
+ .map((p) => p || '/'),
+ '/files/deliveryknowledgebase.csv',
+ '/media/knowledge-base-demo.mp4',
+ '/sitemap-index.xml',
+];
+
+/** Runs `worker` over `items` at a fixed concurrency, preserving input order in the result. */
+async function pooled(items, worker) {
+ const results = new Array(items.length);
+ let next = 0;
+ const runners = Array.from({ length: Math.min(CONCURRENCY, items.length) }, async () => {
+ while (next < items.length) {
+ const i = next++;
+ results[i] = await worker(items[i]);
+ }
+ });
+ await Promise.all(runners);
+ return results;
+}
+
+console.log(`checking ${paths.length} URLs against ${base}\n`);
+
+const results = await pooled(paths, async (path) => {
+ try {
+ const response = await fetch(`${base}${path}`, { redirect: 'manual' });
+ return { path, status: response.status, location: response.headers.get('location') };
+ } catch (error) {
+ return { path, status: 0, error: error.message };
+ }
+});
+
+const failures = results.filter((r) => r.status !== 200);
+
+console.log(`checked : ${results.length}`);
+console.log(`serving 200 : ${results.length - failures.length}`);
+console.log(`not 200 : ${failures.length}`);
+
+if (failures.length) {
+ console.error('\nURLs not serving 200:');
+ for (const f of failures) {
+ console.error(` ${String(f.status).padEnd(4)} ${f.path}${f.location ? ` -> ${f.location}` : ''}${f.error ? ` (${f.error})` : ''}`);
+ }
+ process.exit(1);
+}
+console.log('\nlive check: OK');
diff --git a/src/assets/0.png b/src/assets/0.png
new file mode 100644
index 0000000..9cf0c89
Binary files /dev/null and b/src/assets/0.png differ
diff --git a/src/assets/1-1.png b/src/assets/1-1.png
new file mode 100644
index 0000000..6fc5815
Binary files /dev/null and b/src/assets/1-1.png differ
diff --git a/src/assets/1-3.png b/src/assets/1-3.png
new file mode 100644
index 0000000..eb16348
Binary files /dev/null and b/src/assets/1-3.png differ
diff --git a/src/assets/1.png b/src/assets/1.png
new file mode 100644
index 0000000..8ed28d0
Binary files /dev/null and b/src/assets/1.png differ
diff --git a/src/assets/1000008687.jpg b/src/assets/1000008687.jpg
new file mode 100644
index 0000000..aa48115
Binary files /dev/null and b/src/assets/1000008687.jpg differ
diff --git a/src/assets/1000008688.jpg b/src/assets/1000008688.jpg
new file mode 100644
index 0000000..b8f9f49
Binary files /dev/null and b/src/assets/1000008688.jpg differ
diff --git a/src/assets/1270x760-image-20.png b/src/assets/1270x760-image-20.png
new file mode 100644
index 0000000..8d41ed5
Binary files /dev/null and b/src/assets/1270x760-image-20.png differ
diff --git a/src/assets/1270x760-image-21.png b/src/assets/1270x760-image-21.png
new file mode 100644
index 0000000..de0a639
Binary files /dev/null and b/src/assets/1270x760-image-21.png differ
diff --git a/src/assets/1270x760-image-22.png b/src/assets/1270x760-image-22.png
new file mode 100644
index 0000000..5e15565
Binary files /dev/null and b/src/assets/1270x760-image-22.png differ
diff --git a/src/assets/1270x760-image-23.png b/src/assets/1270x760-image-23.png
new file mode 100644
index 0000000..38f03c9
Binary files /dev/null and b/src/assets/1270x760-image-23.png differ
diff --git a/src/assets/1270x760-image-24.png b/src/assets/1270x760-image-24.png
new file mode 100644
index 0000000..c377c15
Binary files /dev/null and b/src/assets/1270x760-image-24.png differ
diff --git a/src/assets/1270x760-image-26.png b/src/assets/1270x760-image-26.png
new file mode 100644
index 0000000..d1beb1c
Binary files /dev/null and b/src/assets/1270x760-image-26.png differ
diff --git a/src/assets/1270x760-image-27.png b/src/assets/1270x760-image-27.png
new file mode 100644
index 0000000..ea16140
Binary files /dev/null and b/src/assets/1270x760-image-27.png differ
diff --git a/src/assets/1270x760-image-28.png b/src/assets/1270x760-image-28.png
new file mode 100644
index 0000000..4b71ebb
Binary files /dev/null and b/src/assets/1270x760-image-28.png differ
diff --git a/src/assets/1270x760-image-29.png b/src/assets/1270x760-image-29.png
new file mode 100644
index 0000000..29c7f46
Binary files /dev/null and b/src/assets/1270x760-image-29.png differ
diff --git a/src/assets/1270x760-image-30.png b/src/assets/1270x760-image-30.png
new file mode 100644
index 0000000..1307d0c
Binary files /dev/null and b/src/assets/1270x760-image-30.png differ
diff --git a/src/assets/1270x760-image-31.png b/src/assets/1270x760-image-31.png
new file mode 100644
index 0000000..d8ddf51
Binary files /dev/null and b/src/assets/1270x760-image-31.png differ
diff --git a/src/assets/1270x760-image-32.png b/src/assets/1270x760-image-32.png
new file mode 100644
index 0000000..d37f51e
Binary files /dev/null and b/src/assets/1270x760-image-32.png differ
diff --git a/src/assets/1270x760-image-33.png b/src/assets/1270x760-image-33.png
new file mode 100644
index 0000000..877735b
Binary files /dev/null and b/src/assets/1270x760-image-33.png differ
diff --git a/src/assets/1270x760-image-34.png b/src/assets/1270x760-image-34.png
new file mode 100644
index 0000000..fc8c708
Binary files /dev/null and b/src/assets/1270x760-image-34.png differ
diff --git a/src/assets/2-1-2.png b/src/assets/2-1-2.png
new file mode 100644
index 0000000..027d111
Binary files /dev/null and b/src/assets/2-1-2.png differ
diff --git a/src/assets/2-2.png b/src/assets/2-2.png
new file mode 100644
index 0000000..7f48155
Binary files /dev/null and b/src/assets/2-2.png differ
diff --git a/src/assets/2.png b/src/assets/2.png
new file mode 100644
index 0000000..9bdc728
Binary files /dev/null and b/src/assets/2.png differ
diff --git a/src/assets/2021-06-07-17-01-18-1.png b/src/assets/2021-06-07-17-01-18-1.png
new file mode 100644
index 0000000..9327b5f
Binary files /dev/null and b/src/assets/2021-06-07-17-01-18-1.png differ
diff --git a/src/assets/2022-09-21-16-47-08.png b/src/assets/2022-09-21-16-47-08.png
new file mode 100644
index 0000000..a2ae3a8
Binary files /dev/null and b/src/assets/2022-09-21-16-47-08.png differ
diff --git a/src/assets/2023-03-08-16-29-24-1.png b/src/assets/2023-03-08-16-29-24-1.png
new file mode 100644
index 0000000..1889631
Binary files /dev/null and b/src/assets/2023-03-08-16-29-24-1.png differ
diff --git a/src/assets/2023-05-01-10-54-09.png b/src/assets/2023-05-01-10-54-09.png
new file mode 100644
index 0000000..964ae68
Binary files /dev/null and b/src/assets/2023-05-01-10-54-09.png differ
diff --git a/src/assets/2023-05-01-14-35-48.png b/src/assets/2023-05-01-14-35-48.png
new file mode 100644
index 0000000..3e3c4fb
Binary files /dev/null and b/src/assets/2023-05-01-14-35-48.png differ
diff --git a/src/assets/2023-05-01-15-15-11-copy-1.png b/src/assets/2023-05-01-15-15-11-copy-1.png
new file mode 100644
index 0000000..2bc6bda
Binary files /dev/null and b/src/assets/2023-05-01-15-15-11-copy-1.png differ
diff --git a/src/assets/2023-05-01-15-57-54.png b/src/assets/2023-05-01-15-57-54.png
new file mode 100644
index 0000000..7d343ea
Binary files /dev/null and b/src/assets/2023-05-01-15-57-54.png differ
diff --git a/src/assets/2023-05-01-16-32-21.png b/src/assets/2023-05-01-16-32-21.png
new file mode 100644
index 0000000..764426e
Binary files /dev/null and b/src/assets/2023-05-01-16-32-21.png differ
diff --git a/src/assets/2023-05-01-16-43-02.png b/src/assets/2023-05-01-16-43-02.png
new file mode 100644
index 0000000..070fa74
Binary files /dev/null and b/src/assets/2023-05-01-16-43-02.png differ
diff --git a/src/assets/2023-05-02-09-13-40.png b/src/assets/2023-05-02-09-13-40.png
new file mode 100644
index 0000000..20c4ebd
Binary files /dev/null and b/src/assets/2023-05-02-09-13-40.png differ
diff --git a/src/assets/2023-05-02-12-11-15.png b/src/assets/2023-05-02-12-11-15.png
new file mode 100644
index 0000000..f2900cc
Binary files /dev/null and b/src/assets/2023-05-02-12-11-15.png differ
diff --git a/src/assets/2023-05-02-12-11-35.png b/src/assets/2023-05-02-12-11-35.png
new file mode 100644
index 0000000..47f89f9
Binary files /dev/null and b/src/assets/2023-05-02-12-11-35.png differ
diff --git a/src/assets/2023-05-02-15-20-54.png b/src/assets/2023-05-02-15-20-54.png
new file mode 100644
index 0000000..3f737a1
Binary files /dev/null and b/src/assets/2023-05-02-15-20-54.png differ
diff --git a/src/assets/2023-05-02-15-28-26.png b/src/assets/2023-05-02-15-28-26.png
new file mode 100644
index 0000000..7c719e8
Binary files /dev/null and b/src/assets/2023-05-02-15-28-26.png differ
diff --git a/src/assets/2023-05-02-15-32-45.png b/src/assets/2023-05-02-15-32-45.png
new file mode 100644
index 0000000..a7da657
Binary files /dev/null and b/src/assets/2023-05-02-15-32-45.png differ
diff --git a/src/assets/2023-05-02-15-33-04.png b/src/assets/2023-05-02-15-33-04.png
new file mode 100644
index 0000000..5a9abfe
Binary files /dev/null and b/src/assets/2023-05-02-15-33-04.png differ
diff --git a/src/assets/2023-05-04-15-58-27-1.png b/src/assets/2023-05-04-15-58-27-1.png
new file mode 100644
index 0000000..5f2e7d0
Binary files /dev/null and b/src/assets/2023-05-04-15-58-27-1.png differ
diff --git a/src/assets/2023-05-04-16-17-09-1.png b/src/assets/2023-05-04-16-17-09-1.png
new file mode 100644
index 0000000..d69fe04
Binary files /dev/null and b/src/assets/2023-05-04-16-17-09-1.png differ
diff --git a/src/assets/2023-05-04-16-23-35-1.png b/src/assets/2023-05-04-16-23-35-1.png
new file mode 100644
index 0000000..1d6ca1c
Binary files /dev/null and b/src/assets/2023-05-04-16-23-35-1.png differ
diff --git a/src/assets/2023-05-15-20-24-57.png b/src/assets/2023-05-15-20-24-57.png
new file mode 100644
index 0000000..7c6cffd
Binary files /dev/null and b/src/assets/2023-05-15-20-24-57.png differ
diff --git a/src/assets/2023-05-15-20-27-38.png b/src/assets/2023-05-15-20-27-38.png
new file mode 100644
index 0000000..294a734
Binary files /dev/null and b/src/assets/2023-05-15-20-27-38.png differ
diff --git a/src/assets/2023-05-15-20-34-34.png b/src/assets/2023-05-15-20-34-34.png
new file mode 100644
index 0000000..e59250d
Binary files /dev/null and b/src/assets/2023-05-15-20-34-34.png differ
diff --git a/src/assets/2023-05-17-07-53-21.png b/src/assets/2023-05-17-07-53-21.png
new file mode 100644
index 0000000..90a0698
Binary files /dev/null and b/src/assets/2023-05-17-07-53-21.png differ
diff --git a/src/assets/2023-05-17-07-54-16.png b/src/assets/2023-05-17-07-54-16.png
new file mode 100644
index 0000000..7c0a421
Binary files /dev/null and b/src/assets/2023-05-17-07-54-16.png differ
diff --git a/src/assets/2023-05-18-14-54-46.png b/src/assets/2023-05-18-14-54-46.png
new file mode 100644
index 0000000..a327292
Binary files /dev/null and b/src/assets/2023-05-18-14-54-46.png differ
diff --git a/src/assets/2023-05-18-15-08-12.png b/src/assets/2023-05-18-15-08-12.png
new file mode 100644
index 0000000..1aa9f84
Binary files /dev/null and b/src/assets/2023-05-18-15-08-12.png differ
diff --git a/src/assets/2023-05-18-15-09-06.png b/src/assets/2023-05-18-15-09-06.png
new file mode 100644
index 0000000..03b0c2e
Binary files /dev/null and b/src/assets/2023-05-18-15-09-06.png differ
diff --git a/src/assets/2023-05-18-15-18-42.png b/src/assets/2023-05-18-15-18-42.png
new file mode 100644
index 0000000..77e3f09
Binary files /dev/null and b/src/assets/2023-05-18-15-18-42.png differ
diff --git a/src/assets/2023-05-18-15-25-33.png b/src/assets/2023-05-18-15-25-33.png
new file mode 100644
index 0000000..7d26a17
Binary files /dev/null and b/src/assets/2023-05-18-15-25-33.png differ
diff --git a/src/assets/2023-05-18-15-29-56.png b/src/assets/2023-05-18-15-29-56.png
new file mode 100644
index 0000000..21b1471
Binary files /dev/null and b/src/assets/2023-05-18-15-29-56.png differ
diff --git a/src/assets/2023-05-18-15-38-33.png b/src/assets/2023-05-18-15-38-33.png
new file mode 100644
index 0000000..ccbf223
Binary files /dev/null and b/src/assets/2023-05-18-15-38-33.png differ
diff --git a/src/assets/2023-05-19-19-36-01.png b/src/assets/2023-05-19-19-36-01.png
new file mode 100644
index 0000000..17f7a22
Binary files /dev/null and b/src/assets/2023-05-19-19-36-01.png differ
diff --git a/src/assets/2023-05-23-10-57-47-2.png b/src/assets/2023-05-23-10-57-47-2.png
new file mode 100644
index 0000000..dfc6a57
Binary files /dev/null and b/src/assets/2023-05-23-10-57-47-2.png differ
diff --git a/src/assets/2023-05-23-10-57-47-5.png b/src/assets/2023-05-23-10-57-47-5.png
new file mode 100644
index 0000000..dfc6a57
Binary files /dev/null and b/src/assets/2023-05-23-10-57-47-5.png differ
diff --git a/src/assets/2023-05-23-13-09-37.png b/src/assets/2023-05-23-13-09-37.png
new file mode 100644
index 0000000..0738a37
Binary files /dev/null and b/src/assets/2023-05-23-13-09-37.png differ
diff --git a/src/assets/2023-05-23-13-10-36.png b/src/assets/2023-05-23-13-10-36.png
new file mode 100644
index 0000000..1ecf8a0
Binary files /dev/null and b/src/assets/2023-05-23-13-10-36.png differ
diff --git a/src/assets/2023-05-23-14-09-08.png b/src/assets/2023-05-23-14-09-08.png
new file mode 100644
index 0000000..207bd70
Binary files /dev/null and b/src/assets/2023-05-23-14-09-08.png differ
diff --git a/src/assets/2023-05-23-14-14-16.png b/src/assets/2023-05-23-14-14-16.png
new file mode 100644
index 0000000..2439769
Binary files /dev/null and b/src/assets/2023-05-23-14-14-16.png differ
diff --git a/src/assets/2023-05-23-14-19-32.png b/src/assets/2023-05-23-14-19-32.png
new file mode 100644
index 0000000..85a193d
Binary files /dev/null and b/src/assets/2023-05-23-14-19-32.png differ
diff --git a/src/assets/2023-05-23-14-21-42.png b/src/assets/2023-05-23-14-21-42.png
new file mode 100644
index 0000000..1a2ab03
Binary files /dev/null and b/src/assets/2023-05-23-14-21-42.png differ
diff --git a/src/assets/2023-06-09-15-27-50.png b/src/assets/2023-06-09-15-27-50.png
new file mode 100644
index 0000000..392339c
Binary files /dev/null and b/src/assets/2023-06-09-15-27-50.png differ
diff --git a/src/assets/2023-06-09-15-46-54.png b/src/assets/2023-06-09-15-46-54.png
new file mode 100644
index 0000000..acb07c0
Binary files /dev/null and b/src/assets/2023-06-09-15-46-54.png differ
diff --git a/src/assets/2023-06-09-16-10-54.png b/src/assets/2023-06-09-16-10-54.png
new file mode 100644
index 0000000..182fc17
Binary files /dev/null and b/src/assets/2023-06-09-16-10-54.png differ
diff --git a/src/assets/2023-06-09-16-11-08.png b/src/assets/2023-06-09-16-11-08.png
new file mode 100644
index 0000000..e9ba694
Binary files /dev/null and b/src/assets/2023-06-09-16-11-08.png differ
diff --git a/src/assets/2023-06-09-16-11-21.png b/src/assets/2023-06-09-16-11-21.png
new file mode 100644
index 0000000..96a6b6f
Binary files /dev/null and b/src/assets/2023-06-09-16-11-21.png differ
diff --git a/src/assets/2023-06-14-13-08-01-copy.png b/src/assets/2023-06-14-13-08-01-copy.png
new file mode 100644
index 0000000..147f93a
Binary files /dev/null and b/src/assets/2023-06-14-13-08-01-copy.png differ
diff --git a/src/assets/2023-06-14-16-31-02.png b/src/assets/2023-06-14-16-31-02.png
new file mode 100644
index 0000000..ffd2e07
Binary files /dev/null and b/src/assets/2023-06-14-16-31-02.png differ
diff --git a/src/assets/2023-06-15-14-42-00.png b/src/assets/2023-06-15-14-42-00.png
new file mode 100644
index 0000000..10899e9
Binary files /dev/null and b/src/assets/2023-06-15-14-42-00.png differ
diff --git a/src/assets/2023-06-16-07-32-11.png b/src/assets/2023-06-16-07-32-11.png
new file mode 100644
index 0000000..807d92d
Binary files /dev/null and b/src/assets/2023-06-16-07-32-11.png differ
diff --git a/src/assets/2023-06-16-07-40-11.png b/src/assets/2023-06-16-07-40-11.png
new file mode 100644
index 0000000..620b64f
Binary files /dev/null and b/src/assets/2023-06-16-07-40-11.png differ
diff --git a/src/assets/2023-06-16-07-40-37-1.png b/src/assets/2023-06-16-07-40-37-1.png
new file mode 100644
index 0000000..c17ce2f
Binary files /dev/null and b/src/assets/2023-06-16-07-40-37-1.png differ
diff --git a/src/assets/2023-06-16-07-44-00-copy.png b/src/assets/2023-06-16-07-44-00-copy.png
new file mode 100644
index 0000000..795972c
Binary files /dev/null and b/src/assets/2023-06-16-07-44-00-copy.png differ
diff --git a/src/assets/2023-06-16-07-44-00.png b/src/assets/2023-06-16-07-44-00.png
new file mode 100644
index 0000000..ac3efb9
Binary files /dev/null and b/src/assets/2023-06-16-07-44-00.png differ
diff --git a/src/assets/2023-06-16-07-47-08.png b/src/assets/2023-06-16-07-47-08.png
new file mode 100644
index 0000000..7a12197
Binary files /dev/null and b/src/assets/2023-06-16-07-47-08.png differ
diff --git a/src/assets/2023-06-20-15-55-55.png b/src/assets/2023-06-20-15-55-55.png
new file mode 100644
index 0000000..a06a1c7
Binary files /dev/null and b/src/assets/2023-06-20-15-55-55.png differ
diff --git a/src/assets/2023-06-20-15-59-11.png b/src/assets/2023-06-20-15-59-11.png
new file mode 100644
index 0000000..76c4a8f
Binary files /dev/null and b/src/assets/2023-06-20-15-59-11.png differ
diff --git a/src/assets/2023-06-20-15-59-35.png b/src/assets/2023-06-20-15-59-35.png
new file mode 100644
index 0000000..4b01225
Binary files /dev/null and b/src/assets/2023-06-20-15-59-35.png differ
diff --git a/src/assets/2023-06-20-16-05-02.png b/src/assets/2023-06-20-16-05-02.png
new file mode 100644
index 0000000..0f05d6d
Binary files /dev/null and b/src/assets/2023-06-20-16-05-02.png differ
diff --git a/src/assets/2023-06-30-15-33-50.png b/src/assets/2023-06-30-15-33-50.png
new file mode 100644
index 0000000..e8fe304
Binary files /dev/null and b/src/assets/2023-06-30-15-33-50.png differ
diff --git a/src/assets/2023-11-09-18-39-04.png b/src/assets/2023-11-09-18-39-04.png
new file mode 100644
index 0000000..145352d
Binary files /dev/null and b/src/assets/2023-11-09-18-39-04.png differ
diff --git a/src/assets/2023-11-09-18-41-49.png b/src/assets/2023-11-09-18-41-49.png
new file mode 100644
index 0000000..40679dc
Binary files /dev/null and b/src/assets/2023-11-09-18-41-49.png differ
diff --git a/src/assets/2023-11-09-18-48-53.png b/src/assets/2023-11-09-18-48-53.png
new file mode 100644
index 0000000..899a4a3
Binary files /dev/null and b/src/assets/2023-11-09-18-48-53.png differ
diff --git a/src/assets/2023-11-09-18-52-09.png b/src/assets/2023-11-09-18-52-09.png
new file mode 100644
index 0000000..af2fbe1
Binary files /dev/null and b/src/assets/2023-11-09-18-52-09.png differ
diff --git a/src/assets/2023-11-09-18-53-48.png b/src/assets/2023-11-09-18-53-48.png
new file mode 100644
index 0000000..48bda5d
Binary files /dev/null and b/src/assets/2023-11-09-18-53-48.png differ
diff --git a/src/assets/2023-11-09-19-07-11.png b/src/assets/2023-11-09-19-07-11.png
new file mode 100644
index 0000000..cfbddbb
Binary files /dev/null and b/src/assets/2023-11-09-19-07-11.png differ
diff --git a/src/assets/2023-11-09-19-08-09-1.png b/src/assets/2023-11-09-19-08-09-1.png
new file mode 100644
index 0000000..c3485ee
Binary files /dev/null and b/src/assets/2023-11-09-19-08-09-1.png differ
diff --git a/src/assets/2023-11-10-14-20-10.png b/src/assets/2023-11-10-14-20-10.png
new file mode 100644
index 0000000..ceeb820
Binary files /dev/null and b/src/assets/2023-11-10-14-20-10.png differ
diff --git a/src/assets/2023-11-10-14-24-27.png b/src/assets/2023-11-10-14-24-27.png
new file mode 100644
index 0000000..c002c87
Binary files /dev/null and b/src/assets/2023-11-10-14-24-27.png differ
diff --git a/src/assets/2023-11-10-14-27-21.png b/src/assets/2023-11-10-14-27-21.png
new file mode 100644
index 0000000..5b9b081
Binary files /dev/null and b/src/assets/2023-11-10-14-27-21.png differ
diff --git a/src/assets/2023-11-10-14-29-11.png b/src/assets/2023-11-10-14-29-11.png
new file mode 100644
index 0000000..eed51be
Binary files /dev/null and b/src/assets/2023-11-10-14-29-11.png differ
diff --git a/src/assets/2023-11-10-14-29-36.png b/src/assets/2023-11-10-14-29-36.png
new file mode 100644
index 0000000..aa8a502
Binary files /dev/null and b/src/assets/2023-11-10-14-29-36.png differ
diff --git a/src/assets/2b.png b/src/assets/2b.png
new file mode 100644
index 0000000..85f29a8
Binary files /dev/null and b/src/assets/2b.png differ
diff --git a/src/assets/3-1.png b/src/assets/3-1.png
new file mode 100644
index 0000000..81eddf5
Binary files /dev/null and b/src/assets/3-1.png differ
diff --git a/src/assets/3.png b/src/assets/3.png
new file mode 100644
index 0000000..9349ce4
Binary files /dev/null and b/src/assets/3.png differ
diff --git a/src/assets/3b.png b/src/assets/3b.png
new file mode 100644
index 0000000..ccb6fb6
Binary files /dev/null and b/src/assets/3b.png differ
diff --git a/src/assets/4-1.png b/src/assets/4-1.png
new file mode 100644
index 0000000..531078e
Binary files /dev/null and b/src/assets/4-1.png differ
diff --git a/src/assets/5b.png b/src/assets/5b.png
new file mode 100644
index 0000000..bc4eac1
Binary files /dev/null and b/src/assets/5b.png differ
diff --git a/src/assets/actions-landing-page.png b/src/assets/actions-landing-page.png
new file mode 100644
index 0000000..7926049
Binary files /dev/null and b/src/assets/actions-landing-page.png differ
diff --git a/src/assets/add-topic-source.png b/src/assets/add-topic-source.png
new file mode 100644
index 0000000..9de6e7a
Binary files /dev/null and b/src/assets/add-topic-source.png differ
diff --git a/src/assets/ai-agent-completed.png b/src/assets/ai-agent-completed.png
new file mode 100644
index 0000000..3bf7c97
Binary files /dev/null and b/src/assets/ai-agent-completed.png differ
diff --git a/src/assets/aiagent-testsheet.png b/src/assets/aiagent-testsheet.png
new file mode 100644
index 0000000..69c1eb8
Binary files /dev/null and b/src/assets/aiagent-testsheet.png differ
diff --git a/src/assets/alt-tags-1.png b/src/assets/alt-tags-1.png
new file mode 100644
index 0000000..9d6c472
Binary files /dev/null and b/src/assets/alt-tags-1.png differ
diff --git a/src/assets/applicationdesign.png b/src/assets/applicationdesign.png
new file mode 100644
index 0000000..7a49d84
Binary files /dev/null and b/src/assets/applicationdesign.png differ
diff --git a/src/assets/authentication-mtls.png b/src/assets/authentication-mtls.png
new file mode 100644
index 0000000..869d207
Binary files /dev/null and b/src/assets/authentication-mtls.png differ
diff --git a/src/assets/authentication-selection.png b/src/assets/authentication-selection.png
new file mode 100644
index 0000000..0ecb3af
Binary files /dev/null and b/src/assets/authentication-selection.png differ
diff --git a/src/assets/authenticaton-headers.png b/src/assets/authenticaton-headers.png
new file mode 100644
index 0000000..0bc4bec
Binary files /dev/null and b/src/assets/authenticaton-headers.png differ
diff --git a/src/assets/buttons.png b/src/assets/buttons.png
new file mode 100644
index 0000000..6537bb4
Binary files /dev/null and b/src/assets/buttons.png differ
diff --git a/src/assets/certificate-management.png b/src/assets/certificate-management.png
new file mode 100644
index 0000000..a7b13dc
Binary files /dev/null and b/src/assets/certificate-management.png differ
diff --git a/src/assets/chatwoot-handover.png b/src/assets/chatwoot-handover.png
new file mode 100644
index 0000000..fceeda8
Binary files /dev/null and b/src/assets/chatwoot-handover.png differ
diff --git a/src/assets/colour-contrast-2.png b/src/assets/colour-contrast-2.png
new file mode 100644
index 0000000..9a6a312
Binary files /dev/null and b/src/assets/colour-contrast-2.png differ
diff --git a/src/assets/conditions-1.png b/src/assets/conditions-1.png
new file mode 100644
index 0000000..cf951fe
Binary files /dev/null and b/src/assets/conditions-1.png differ
diff --git a/src/assets/create-new-alias.png b/src/assets/create-new-alias.png
new file mode 100644
index 0000000..14c8e8f
Binary files /dev/null and b/src/assets/create-new-alias.png differ
diff --git a/src/assets/created.png b/src/assets/created.png
new file mode 100644
index 0000000..8412c92
Binary files /dev/null and b/src/assets/created.png differ
diff --git a/src/assets/description.png b/src/assets/description.png
new file mode 100644
index 0000000..99c882e
Binary files /dev/null and b/src/assets/description.png differ
diff --git a/src/assets/design-conversation-1.png b/src/assets/design-conversation-1.png
new file mode 100644
index 0000000..03ee3b7
Binary files /dev/null and b/src/assets/design-conversation-1.png differ
diff --git a/src/assets/design-scenario-1.png b/src/assets/design-scenario-1.png
new file mode 100644
index 0000000..c136f85
Binary files /dev/null and b/src/assets/design-scenario-1.png differ
diff --git a/src/assets/designoption-notexpanded.png b/src/assets/designoption-notexpanded.png
new file mode 100644
index 0000000..0a7e4ca
Binary files /dev/null and b/src/assets/designoption-notexpanded.png differ
diff --git a/src/assets/e-sign.png b/src/assets/e-sign.png
new file mode 100644
index 0000000..71b683d
Binary files /dev/null and b/src/assets/e-sign.png differ
diff --git a/src/assets/engineer-maintenancing-ai-systems-2023-11-27-05-12-07-utc.jpg b/src/assets/engineer-maintenancing-ai-systems-2023-11-27-05-12-07-utc.jpg
new file mode 100644
index 0000000..0cbf590
Binary files /dev/null and b/src/assets/engineer-maintenancing-ai-systems-2023-11-27-05-12-07-utc.jpg differ
diff --git a/src/assets/expand-message-demo.png b/src/assets/expand-message-demo.png
new file mode 100644
index 0000000..887a274
Binary files /dev/null and b/src/assets/expand-message-demo.png differ
diff --git a/src/assets/faq-interface-turns.png b/src/assets/faq-interface-turns.png
new file mode 100644
index 0000000..ae51b66
Binary files /dev/null and b/src/assets/faq-interface-turns.png differ
diff --git a/src/assets/faq-turn.png b/src/assets/faq-turn.png
new file mode 100644
index 0000000..8de0026
Binary files /dev/null and b/src/assets/faq-turn.png differ
diff --git a/src/assets/group-1-1-1.png b/src/assets/group-1-1-1.png
new file mode 100644
index 0000000..fdacc5c
Binary files /dev/null and b/src/assets/group-1-1-1.png differ
diff --git a/src/assets/group-1-1.png b/src/assets/group-1-1.png
new file mode 100644
index 0000000..c7e0a57
Binary files /dev/null and b/src/assets/group-1-1.png differ
diff --git a/src/assets/group-10-1.png b/src/assets/group-10-1.png
new file mode 100644
index 0000000..c381dfc
Binary files /dev/null and b/src/assets/group-10-1.png differ
diff --git a/src/assets/group-10-2.png b/src/assets/group-10-2.png
new file mode 100644
index 0000000..8cd92aa
Binary files /dev/null and b/src/assets/group-10-2.png differ
diff --git a/src/assets/group-11-1.png b/src/assets/group-11-1.png
new file mode 100644
index 0000000..5561296
Binary files /dev/null and b/src/assets/group-11-1.png differ
diff --git a/src/assets/group-11.png b/src/assets/group-11.png
new file mode 100644
index 0000000..d6e14d1
Binary files /dev/null and b/src/assets/group-11.png differ
diff --git a/src/assets/group-12.png b/src/assets/group-12.png
new file mode 100644
index 0000000..c56fa6b
Binary files /dev/null and b/src/assets/group-12.png differ
diff --git a/src/assets/group-13.png b/src/assets/group-13.png
new file mode 100644
index 0000000..cddb1bc
Binary files /dev/null and b/src/assets/group-13.png differ
diff --git a/src/assets/group-14.png b/src/assets/group-14.png
new file mode 100644
index 0000000..0bd1bda
Binary files /dev/null and b/src/assets/group-14.png differ
diff --git a/src/assets/group-15.png b/src/assets/group-15.png
new file mode 100644
index 0000000..feb9f64
Binary files /dev/null and b/src/assets/group-15.png differ
diff --git a/src/assets/group-16.png b/src/assets/group-16.png
new file mode 100644
index 0000000..68f2beb
Binary files /dev/null and b/src/assets/group-16.png differ
diff --git a/src/assets/group-17.png b/src/assets/group-17.png
new file mode 100644
index 0000000..9bbddc6
Binary files /dev/null and b/src/assets/group-17.png differ
diff --git a/src/assets/group-18.png b/src/assets/group-18.png
new file mode 100644
index 0000000..54443e8
Binary files /dev/null and b/src/assets/group-18.png differ
diff --git a/src/assets/group-19.png b/src/assets/group-19.png
new file mode 100644
index 0000000..9d7bc9d
Binary files /dev/null and b/src/assets/group-19.png differ
diff --git a/src/assets/group-2-1.png b/src/assets/group-2-1.png
new file mode 100644
index 0000000..1d4bb9a
Binary files /dev/null and b/src/assets/group-2-1.png differ
diff --git a/src/assets/group-2-2.png b/src/assets/group-2-2.png
new file mode 100644
index 0000000..6550109
Binary files /dev/null and b/src/assets/group-2-2.png differ
diff --git a/src/assets/group-2-3.png b/src/assets/group-2-3.png
new file mode 100644
index 0000000..b7c5467
Binary files /dev/null and b/src/assets/group-2-3.png differ
diff --git a/src/assets/group-20.png b/src/assets/group-20.png
new file mode 100644
index 0000000..c42cc31
Binary files /dev/null and b/src/assets/group-20.png differ
diff --git a/src/assets/group-21.png b/src/assets/group-21.png
new file mode 100644
index 0000000..6cfa236
Binary files /dev/null and b/src/assets/group-21.png differ
diff --git a/src/assets/group-24.png b/src/assets/group-24.png
new file mode 100644
index 0000000..e979108
Binary files /dev/null and b/src/assets/group-24.png differ
diff --git a/src/assets/group-25.png b/src/assets/group-25.png
new file mode 100644
index 0000000..ce1b392
Binary files /dev/null and b/src/assets/group-25.png differ
diff --git a/src/assets/group-26.png b/src/assets/group-26.png
new file mode 100644
index 0000000..161bcda
Binary files /dev/null and b/src/assets/group-26.png differ
diff --git a/src/assets/group-27.png b/src/assets/group-27.png
new file mode 100644
index 0000000..7740dc4
Binary files /dev/null and b/src/assets/group-27.png differ
diff --git a/src/assets/group-28.png b/src/assets/group-28.png
new file mode 100644
index 0000000..80ee1b0
Binary files /dev/null and b/src/assets/group-28.png differ
diff --git a/src/assets/group-3-1-1.png b/src/assets/group-3-1-1.png
new file mode 100644
index 0000000..769fce2
Binary files /dev/null and b/src/assets/group-3-1-1.png differ
diff --git a/src/assets/group-3-1.png b/src/assets/group-3-1.png
new file mode 100644
index 0000000..f0eb391
Binary files /dev/null and b/src/assets/group-3-1.png differ
diff --git a/src/assets/group-30.png b/src/assets/group-30.png
new file mode 100644
index 0000000..544bf19
Binary files /dev/null and b/src/assets/group-30.png differ
diff --git a/src/assets/group-4-1.png b/src/assets/group-4-1.png
new file mode 100644
index 0000000..775e34e
Binary files /dev/null and b/src/assets/group-4-1.png differ
diff --git a/src/assets/group-4.png b/src/assets/group-4.png
new file mode 100644
index 0000000..1299328
Binary files /dev/null and b/src/assets/group-4.png differ
diff --git a/src/assets/group-5-1.png b/src/assets/group-5-1.png
new file mode 100644
index 0000000..38c5625
Binary files /dev/null and b/src/assets/group-5-1.png differ
diff --git a/src/assets/group-5-2.png b/src/assets/group-5-2.png
new file mode 100644
index 0000000..92499d5
Binary files /dev/null and b/src/assets/group-5-2.png differ
diff --git a/src/assets/group-5.png b/src/assets/group-5.png
new file mode 100644
index 0000000..ce6e4d2
Binary files /dev/null and b/src/assets/group-5.png differ
diff --git a/src/assets/group-6-1.png b/src/assets/group-6-1.png
new file mode 100644
index 0000000..48d938f
Binary files /dev/null and b/src/assets/group-6-1.png differ
diff --git a/src/assets/group-7-1-1.png b/src/assets/group-7-1-1.png
new file mode 100644
index 0000000..d4b2224
Binary files /dev/null and b/src/assets/group-7-1-1.png differ
diff --git a/src/assets/group-7-1.png b/src/assets/group-7-1.png
new file mode 100644
index 0000000..6081391
Binary files /dev/null and b/src/assets/group-7-1.png differ
diff --git a/src/assets/group-8-1.png b/src/assets/group-8-1.png
new file mode 100644
index 0000000..8ea89a0
Binary files /dev/null and b/src/assets/group-8-1.png differ
diff --git a/src/assets/group-8.png b/src/assets/group-8.png
new file mode 100644
index 0000000..5674267
Binary files /dev/null and b/src/assets/group-8.png differ
diff --git a/src/assets/group-9.png b/src/assets/group-9.png
new file mode 100644
index 0000000..68cc8df
Binary files /dev/null and b/src/assets/group-9.png differ
diff --git a/src/assets/image-1-1-1-1-1.png b/src/assets/image-1-1-1-1-1.png
new file mode 100644
index 0000000..a8e1304
Binary files /dev/null and b/src/assets/image-1-1-1-1-1.png differ
diff --git a/src/assets/image-1-1-2-1.png b/src/assets/image-1-1-2-1.png
new file mode 100644
index 0000000..5fa3a5a
Binary files /dev/null and b/src/assets/image-1-1-2-1.png differ
diff --git a/src/assets/image-1-1-2.png b/src/assets/image-1-1-2.png
new file mode 100644
index 0000000..0916912
Binary files /dev/null and b/src/assets/image-1-1-2.png differ
diff --git a/src/assets/image-1-1-3-1.png b/src/assets/image-1-1-3-1.png
new file mode 100644
index 0000000..c7ae872
Binary files /dev/null and b/src/assets/image-1-1-3-1.png differ
diff --git a/src/assets/image-1-1.png b/src/assets/image-1-1.png
new file mode 100644
index 0000000..56f07f0
Binary files /dev/null and b/src/assets/image-1-1.png differ
diff --git a/src/assets/image-1-2.png b/src/assets/image-1-2.png
new file mode 100644
index 0000000..5fbb081
Binary files /dev/null and b/src/assets/image-1-2.png differ
diff --git a/src/assets/image-1-4.png b/src/assets/image-1-4.png
new file mode 100644
index 0000000..6bda942
Binary files /dev/null and b/src/assets/image-1-4.png differ
diff --git a/src/assets/image-101.png b/src/assets/image-101.png
new file mode 100644
index 0000000..b8a274a
Binary files /dev/null and b/src/assets/image-101.png differ
diff --git a/src/assets/image-149.png b/src/assets/image-149.png
new file mode 100644
index 0000000..354eb8f
Binary files /dev/null and b/src/assets/image-149.png differ
diff --git a/src/assets/image-192.png b/src/assets/image-192.png
new file mode 100644
index 0000000..14dda58
Binary files /dev/null and b/src/assets/image-192.png differ
diff --git a/src/assets/image-2-1-1.png b/src/assets/image-2-1-1.png
new file mode 100644
index 0000000..246c7a9
Binary files /dev/null and b/src/assets/image-2-1-1.png differ
diff --git a/src/assets/image-2-1.png b/src/assets/image-2-1.png
new file mode 100644
index 0000000..a1a57cc
Binary files /dev/null and b/src/assets/image-2-1.png differ
diff --git a/src/assets/image-2-2-1.png b/src/assets/image-2-2-1.png
new file mode 100644
index 0000000..17e11a6
Binary files /dev/null and b/src/assets/image-2-2-1.png differ
diff --git a/src/assets/image-2-3.png b/src/assets/image-2-3.png
new file mode 100644
index 0000000..e6b063e
Binary files /dev/null and b/src/assets/image-2-3.png differ
diff --git a/src/assets/image-2-4.png b/src/assets/image-2-4.png
new file mode 100644
index 0000000..4b8d5b7
Binary files /dev/null and b/src/assets/image-2-4.png differ
diff --git a/src/assets/image-2-5.png b/src/assets/image-2-5.png
new file mode 100644
index 0000000..9757b7f
Binary files /dev/null and b/src/assets/image-2-5.png differ
diff --git a/src/assets/image-2.png b/src/assets/image-2.png
new file mode 100644
index 0000000..31aaacd
Binary files /dev/null and b/src/assets/image-2.png differ
diff --git a/src/assets/image-21.png b/src/assets/image-21.png
new file mode 100644
index 0000000..53ad5d8
Binary files /dev/null and b/src/assets/image-21.png differ
diff --git a/src/assets/image-242.png b/src/assets/image-242.png
new file mode 100644
index 0000000..b59c161
Binary files /dev/null and b/src/assets/image-242.png differ
diff --git a/src/assets/image-248.png b/src/assets/image-248.png
new file mode 100644
index 0000000..7ba601a
Binary files /dev/null and b/src/assets/image-248.png differ
diff --git a/src/assets/image-254.png b/src/assets/image-254.png
new file mode 100644
index 0000000..cafa8a3
Binary files /dev/null and b/src/assets/image-254.png differ
diff --git a/src/assets/image-256.png b/src/assets/image-256.png
new file mode 100644
index 0000000..42e82d9
Binary files /dev/null and b/src/assets/image-256.png differ
diff --git a/src/assets/image-263.png b/src/assets/image-263.png
new file mode 100644
index 0000000..37d90b2
Binary files /dev/null and b/src/assets/image-263.png differ
diff --git a/src/assets/image-279.png b/src/assets/image-279.png
new file mode 100644
index 0000000..9742535
Binary files /dev/null and b/src/assets/image-279.png differ
diff --git a/src/assets/image-281.png b/src/assets/image-281.png
new file mode 100644
index 0000000..1adf025
Binary files /dev/null and b/src/assets/image-281.png differ
diff --git a/src/assets/image-282.png b/src/assets/image-282.png
new file mode 100644
index 0000000..a98c7f1
Binary files /dev/null and b/src/assets/image-282.png differ
diff --git a/src/assets/image-285.png b/src/assets/image-285.png
new file mode 100644
index 0000000..f551ce0
Binary files /dev/null and b/src/assets/image-285.png differ
diff --git a/src/assets/image-3-1.png b/src/assets/image-3-1.png
new file mode 100644
index 0000000..682546c
Binary files /dev/null and b/src/assets/image-3-1.png differ
diff --git a/src/assets/image-3-2.png b/src/assets/image-3-2.png
new file mode 100644
index 0000000..ab6854f
Binary files /dev/null and b/src/assets/image-3-2.png differ
diff --git a/src/assets/image-3-3.png b/src/assets/image-3-3.png
new file mode 100644
index 0000000..2857836
Binary files /dev/null and b/src/assets/image-3-3.png differ
diff --git a/src/assets/image-3-4.png b/src/assets/image-3-4.png
new file mode 100644
index 0000000..fb41dda
Binary files /dev/null and b/src/assets/image-3-4.png differ
diff --git a/src/assets/image-3.png b/src/assets/image-3.png
new file mode 100644
index 0000000..015fab2
Binary files /dev/null and b/src/assets/image-3.png differ
diff --git a/src/assets/image-33.png b/src/assets/image-33.png
new file mode 100644
index 0000000..8852967
Binary files /dev/null and b/src/assets/image-33.png differ
diff --git a/src/assets/image-339.png b/src/assets/image-339.png
new file mode 100644
index 0000000..35af0c8
Binary files /dev/null and b/src/assets/image-339.png differ
diff --git a/src/assets/image-380.png b/src/assets/image-380.png
new file mode 100644
index 0000000..77d1cc9
Binary files /dev/null and b/src/assets/image-380.png differ
diff --git a/src/assets/image-386.png b/src/assets/image-386.png
new file mode 100644
index 0000000..315d15a
Binary files /dev/null and b/src/assets/image-386.png differ
diff --git a/src/assets/image-394.png b/src/assets/image-394.png
new file mode 100644
index 0000000..3cae592
Binary files /dev/null and b/src/assets/image-394.png differ
diff --git a/src/assets/image-4-1-1.png b/src/assets/image-4-1-1.png
new file mode 100644
index 0000000..5676a54
Binary files /dev/null and b/src/assets/image-4-1-1.png differ
diff --git a/src/assets/image-4-1.png b/src/assets/image-4-1.png
new file mode 100644
index 0000000..ff9de0d
Binary files /dev/null and b/src/assets/image-4-1.png differ
diff --git a/src/assets/image-4-3.png b/src/assets/image-4-3.png
new file mode 100644
index 0000000..22fb4f5
Binary files /dev/null and b/src/assets/image-4-3.png differ
diff --git a/src/assets/image-4.png b/src/assets/image-4.png
new file mode 100644
index 0000000..ecc7ffb
Binary files /dev/null and b/src/assets/image-4.png differ
diff --git a/src/assets/image-40.png b/src/assets/image-40.png
new file mode 100644
index 0000000..0fea32b
Binary files /dev/null and b/src/assets/image-40.png differ
diff --git a/src/assets/image-403.png b/src/assets/image-403.png
new file mode 100644
index 0000000..ead1387
Binary files /dev/null and b/src/assets/image-403.png differ
diff --git a/src/assets/image-408.png b/src/assets/image-408.png
new file mode 100644
index 0000000..911c222
Binary files /dev/null and b/src/assets/image-408.png differ
diff --git a/src/assets/image-414.png b/src/assets/image-414.png
new file mode 100644
index 0000000..df1820b
Binary files /dev/null and b/src/assets/image-414.png differ
diff --git a/src/assets/image-426.png b/src/assets/image-426.png
new file mode 100644
index 0000000..6530861
Binary files /dev/null and b/src/assets/image-426.png differ
diff --git a/src/assets/image-428.png b/src/assets/image-428.png
new file mode 100644
index 0000000..d494e7a
Binary files /dev/null and b/src/assets/image-428.png differ
diff --git a/src/assets/image-434.png b/src/assets/image-434.png
new file mode 100644
index 0000000..6cc0415
Binary files /dev/null and b/src/assets/image-434.png differ
diff --git a/src/assets/image-436.png b/src/assets/image-436.png
new file mode 100644
index 0000000..ee50418
Binary files /dev/null and b/src/assets/image-436.png differ
diff --git a/src/assets/image-444.png b/src/assets/image-444.png
new file mode 100644
index 0000000..c1502dd
Binary files /dev/null and b/src/assets/image-444.png differ
diff --git a/src/assets/image-459.png b/src/assets/image-459.png
new file mode 100644
index 0000000..1c93f4d
Binary files /dev/null and b/src/assets/image-459.png differ
diff --git a/src/assets/image-5-1-1.png b/src/assets/image-5-1-1.png
new file mode 100644
index 0000000..393445b
Binary files /dev/null and b/src/assets/image-5-1-1.png differ
diff --git a/src/assets/image-5-1.png b/src/assets/image-5-1.png
new file mode 100644
index 0000000..9223a84
Binary files /dev/null and b/src/assets/image-5-1.png differ
diff --git a/src/assets/image-5-2.png b/src/assets/image-5-2.png
new file mode 100644
index 0000000..6b1ea0d
Binary files /dev/null and b/src/assets/image-5-2.png differ
diff --git a/src/assets/image-5.png b/src/assets/image-5.png
new file mode 100644
index 0000000..ed671d6
Binary files /dev/null and b/src/assets/image-5.png differ
diff --git a/src/assets/image-514.png b/src/assets/image-514.png
new file mode 100644
index 0000000..1ead405
Binary files /dev/null and b/src/assets/image-514.png differ
diff --git a/src/assets/image-528.png b/src/assets/image-528.png
new file mode 100644
index 0000000..fb57521
Binary files /dev/null and b/src/assets/image-528.png differ
diff --git a/src/assets/image-529-1.png b/src/assets/image-529-1.png
new file mode 100644
index 0000000..0424b73
Binary files /dev/null and b/src/assets/image-529-1.png differ
diff --git a/src/assets/image-529.png b/src/assets/image-529.png
new file mode 100644
index 0000000..1c3025b
Binary files /dev/null and b/src/assets/image-529.png differ
diff --git a/src/assets/image-530-1.png b/src/assets/image-530-1.png
new file mode 100644
index 0000000..5edd081
Binary files /dev/null and b/src/assets/image-530-1.png differ
diff --git a/src/assets/image-530.png b/src/assets/image-530.png
new file mode 100644
index 0000000..dd59ea8
Binary files /dev/null and b/src/assets/image-530.png differ
diff --git a/src/assets/image-531.png b/src/assets/image-531.png
new file mode 100644
index 0000000..d06c003
Binary files /dev/null and b/src/assets/image-531.png differ
diff --git a/src/assets/image-532.png b/src/assets/image-532.png
new file mode 100644
index 0000000..09aa7ab
Binary files /dev/null and b/src/assets/image-532.png differ
diff --git a/src/assets/image-535.png b/src/assets/image-535.png
new file mode 100644
index 0000000..6a7545c
Binary files /dev/null and b/src/assets/image-535.png differ
diff --git a/src/assets/image-536.png b/src/assets/image-536.png
new file mode 100644
index 0000000..c0f081d
Binary files /dev/null and b/src/assets/image-536.png differ
diff --git a/src/assets/image-537.png b/src/assets/image-537.png
new file mode 100644
index 0000000..ab0d47c
Binary files /dev/null and b/src/assets/image-537.png differ
diff --git a/src/assets/image-538.png b/src/assets/image-538.png
new file mode 100644
index 0000000..b8b1e05
Binary files /dev/null and b/src/assets/image-538.png differ
diff --git a/src/assets/image-539.png b/src/assets/image-539.png
new file mode 100644
index 0000000..60d6fc6
Binary files /dev/null and b/src/assets/image-539.png differ
diff --git a/src/assets/image-540.png b/src/assets/image-540.png
new file mode 100644
index 0000000..9926c43
Binary files /dev/null and b/src/assets/image-540.png differ
diff --git a/src/assets/image-541.png b/src/assets/image-541.png
new file mode 100644
index 0000000..c05cf6c
Binary files /dev/null and b/src/assets/image-541.png differ
diff --git a/src/assets/image-542.png b/src/assets/image-542.png
new file mode 100644
index 0000000..7ea04ff
Binary files /dev/null and b/src/assets/image-542.png differ
diff --git a/src/assets/image-543.png b/src/assets/image-543.png
new file mode 100644
index 0000000..130943e
Binary files /dev/null and b/src/assets/image-543.png differ
diff --git a/src/assets/image-544.png b/src/assets/image-544.png
new file mode 100644
index 0000000..f87f093
Binary files /dev/null and b/src/assets/image-544.png differ
diff --git a/src/assets/image-545.png b/src/assets/image-545.png
new file mode 100644
index 0000000..783f290
Binary files /dev/null and b/src/assets/image-545.png differ
diff --git a/src/assets/image-546.png b/src/assets/image-546.png
new file mode 100644
index 0000000..84a47ee
Binary files /dev/null and b/src/assets/image-546.png differ
diff --git a/src/assets/image-547.png b/src/assets/image-547.png
new file mode 100644
index 0000000..d5f7b27
Binary files /dev/null and b/src/assets/image-547.png differ
diff --git a/src/assets/image-548.png b/src/assets/image-548.png
new file mode 100644
index 0000000..5f45488
Binary files /dev/null and b/src/assets/image-548.png differ
diff --git a/src/assets/image-549.png b/src/assets/image-549.png
new file mode 100644
index 0000000..0237807
Binary files /dev/null and b/src/assets/image-549.png differ
diff --git a/src/assets/image-55.png b/src/assets/image-55.png
new file mode 100644
index 0000000..9cb3ad5
Binary files /dev/null and b/src/assets/image-55.png differ
diff --git a/src/assets/image-551.png b/src/assets/image-551.png
new file mode 100644
index 0000000..a538378
Binary files /dev/null and b/src/assets/image-551.png differ
diff --git a/src/assets/image-552.png b/src/assets/image-552.png
new file mode 100644
index 0000000..51f60af
Binary files /dev/null and b/src/assets/image-552.png differ
diff --git a/src/assets/image-553.png b/src/assets/image-553.png
new file mode 100644
index 0000000..6416e0f
Binary files /dev/null and b/src/assets/image-553.png differ
diff --git a/src/assets/image-554.png b/src/assets/image-554.png
new file mode 100644
index 0000000..e36c87c
Binary files /dev/null and b/src/assets/image-554.png differ
diff --git a/src/assets/image-556.png b/src/assets/image-556.png
new file mode 100644
index 0000000..82347e6
Binary files /dev/null and b/src/assets/image-556.png differ
diff --git a/src/assets/image-559.png b/src/assets/image-559.png
new file mode 100644
index 0000000..0b95c4f
Binary files /dev/null and b/src/assets/image-559.png differ
diff --git a/src/assets/image-560.png b/src/assets/image-560.png
new file mode 100644
index 0000000..bdd577e
Binary files /dev/null and b/src/assets/image-560.png differ
diff --git a/src/assets/image-561.png b/src/assets/image-561.png
new file mode 100644
index 0000000..8c52b92
Binary files /dev/null and b/src/assets/image-561.png differ
diff --git a/src/assets/image-562.png b/src/assets/image-562.png
new file mode 100644
index 0000000..e9df910
Binary files /dev/null and b/src/assets/image-562.png differ
diff --git a/src/assets/image-563.png b/src/assets/image-563.png
new file mode 100644
index 0000000..65d9353
Binary files /dev/null and b/src/assets/image-563.png differ
diff --git a/src/assets/image-565.png b/src/assets/image-565.png
new file mode 100644
index 0000000..becdd15
Binary files /dev/null and b/src/assets/image-565.png differ
diff --git a/src/assets/image-567.png b/src/assets/image-567.png
new file mode 100644
index 0000000..fbd2d18
Binary files /dev/null and b/src/assets/image-567.png differ
diff --git a/src/assets/image-569.png b/src/assets/image-569.png
new file mode 100644
index 0000000..f4ea902
Binary files /dev/null and b/src/assets/image-569.png differ
diff --git a/src/assets/image-571.png b/src/assets/image-571.png
new file mode 100644
index 0000000..f841763
Binary files /dev/null and b/src/assets/image-571.png differ
diff --git a/src/assets/image-572.png b/src/assets/image-572.png
new file mode 100644
index 0000000..391f000
Binary files /dev/null and b/src/assets/image-572.png differ
diff --git a/src/assets/image-574.png b/src/assets/image-574.png
new file mode 100644
index 0000000..0fa4142
Binary files /dev/null and b/src/assets/image-574.png differ
diff --git a/src/assets/image-575-1.png b/src/assets/image-575-1.png
new file mode 100644
index 0000000..203aa8b
Binary files /dev/null and b/src/assets/image-575-1.png differ
diff --git a/src/assets/image-577.png b/src/assets/image-577.png
new file mode 100644
index 0000000..824b361
Binary files /dev/null and b/src/assets/image-577.png differ
diff --git a/src/assets/image-578.png b/src/assets/image-578.png
new file mode 100644
index 0000000..b1d05e0
Binary files /dev/null and b/src/assets/image-578.png differ
diff --git a/src/assets/image-579.png b/src/assets/image-579.png
new file mode 100644
index 0000000..9b2340e
Binary files /dev/null and b/src/assets/image-579.png differ
diff --git a/src/assets/image-581.png b/src/assets/image-581.png
new file mode 100644
index 0000000..c0f5090
Binary files /dev/null and b/src/assets/image-581.png differ
diff --git a/src/assets/image-582.png b/src/assets/image-582.png
new file mode 100644
index 0000000..46b4530
Binary files /dev/null and b/src/assets/image-582.png differ
diff --git a/src/assets/image-583.png b/src/assets/image-583.png
new file mode 100644
index 0000000..e3bc715
Binary files /dev/null and b/src/assets/image-583.png differ
diff --git a/src/assets/image-584.png b/src/assets/image-584.png
new file mode 100644
index 0000000..1b833bd
Binary files /dev/null and b/src/assets/image-584.png differ
diff --git a/src/assets/image-585.png b/src/assets/image-585.png
new file mode 100644
index 0000000..961b3f3
Binary files /dev/null and b/src/assets/image-585.png differ
diff --git a/src/assets/image-586.png b/src/assets/image-586.png
new file mode 100644
index 0000000..96677d4
Binary files /dev/null and b/src/assets/image-586.png differ
diff --git a/src/assets/image-588.png b/src/assets/image-588.png
new file mode 100644
index 0000000..b080493
Binary files /dev/null and b/src/assets/image-588.png differ
diff --git a/src/assets/image-590.png b/src/assets/image-590.png
new file mode 100644
index 0000000..6445433
Binary files /dev/null and b/src/assets/image-590.png differ
diff --git a/src/assets/image-592.png b/src/assets/image-592.png
new file mode 100644
index 0000000..861a748
Binary files /dev/null and b/src/assets/image-592.png differ
diff --git a/src/assets/image-593.png b/src/assets/image-593.png
new file mode 100644
index 0000000..324b146
Binary files /dev/null and b/src/assets/image-593.png differ
diff --git a/src/assets/image-594.png b/src/assets/image-594.png
new file mode 100644
index 0000000..02d36ef
Binary files /dev/null and b/src/assets/image-594.png differ
diff --git a/src/assets/image-595.png b/src/assets/image-595.png
new file mode 100644
index 0000000..c106025
Binary files /dev/null and b/src/assets/image-595.png differ
diff --git a/src/assets/image-596.png b/src/assets/image-596.png
new file mode 100644
index 0000000..52dbdcd
Binary files /dev/null and b/src/assets/image-596.png differ
diff --git a/src/assets/image-597.png b/src/assets/image-597.png
new file mode 100644
index 0000000..994a90f
Binary files /dev/null and b/src/assets/image-597.png differ
diff --git a/src/assets/image-6-1.png b/src/assets/image-6-1.png
new file mode 100644
index 0000000..df78583
Binary files /dev/null and b/src/assets/image-6-1.png differ
diff --git a/src/assets/image-6-2.png b/src/assets/image-6-2.png
new file mode 100644
index 0000000..537b0c0
Binary files /dev/null and b/src/assets/image-6-2.png differ
diff --git a/src/assets/image-6.png b/src/assets/image-6.png
new file mode 100644
index 0000000..b37cc8c
Binary files /dev/null and b/src/assets/image-6.png differ
diff --git a/src/assets/image-601.png b/src/assets/image-601.png
new file mode 100644
index 0000000..f5345b4
Binary files /dev/null and b/src/assets/image-601.png differ
diff --git a/src/assets/image-602.png b/src/assets/image-602.png
new file mode 100644
index 0000000..19fe38e
Binary files /dev/null and b/src/assets/image-602.png differ
diff --git a/src/assets/image-603.png b/src/assets/image-603.png
new file mode 100644
index 0000000..936dc55
Binary files /dev/null and b/src/assets/image-603.png differ
diff --git a/src/assets/image-604.png b/src/assets/image-604.png
new file mode 100644
index 0000000..e0d4a5e
Binary files /dev/null and b/src/assets/image-604.png differ
diff --git a/src/assets/image-605.png b/src/assets/image-605.png
new file mode 100644
index 0000000..a1777c1
Binary files /dev/null and b/src/assets/image-605.png differ
diff --git a/src/assets/image-606.png b/src/assets/image-606.png
new file mode 100644
index 0000000..b6f4c1a
Binary files /dev/null and b/src/assets/image-606.png differ
diff --git a/src/assets/image-607.png b/src/assets/image-607.png
new file mode 100644
index 0000000..509a56e
Binary files /dev/null and b/src/assets/image-607.png differ
diff --git a/src/assets/image-608.png b/src/assets/image-608.png
new file mode 100644
index 0000000..ee2cbd8
Binary files /dev/null and b/src/assets/image-608.png differ
diff --git a/src/assets/image-609.png b/src/assets/image-609.png
new file mode 100644
index 0000000..178354d
Binary files /dev/null and b/src/assets/image-609.png differ
diff --git a/src/assets/image-611.png b/src/assets/image-611.png
new file mode 100644
index 0000000..d31f058
Binary files /dev/null and b/src/assets/image-611.png differ
diff --git a/src/assets/image-612.png b/src/assets/image-612.png
new file mode 100644
index 0000000..cf2f44b
Binary files /dev/null and b/src/assets/image-612.png differ
diff --git a/src/assets/image-613.png b/src/assets/image-613.png
new file mode 100644
index 0000000..d316554
Binary files /dev/null and b/src/assets/image-613.png differ
diff --git a/src/assets/image-614.png b/src/assets/image-614.png
new file mode 100644
index 0000000..b0521e1
Binary files /dev/null and b/src/assets/image-614.png differ
diff --git a/src/assets/image-615.png b/src/assets/image-615.png
new file mode 100644
index 0000000..a523a7c
Binary files /dev/null and b/src/assets/image-615.png differ
diff --git a/src/assets/image-618.png b/src/assets/image-618.png
new file mode 100644
index 0000000..ce005c2
Binary files /dev/null and b/src/assets/image-618.png differ
diff --git a/src/assets/image-619.png b/src/assets/image-619.png
new file mode 100644
index 0000000..880c668
Binary files /dev/null and b/src/assets/image-619.png differ
diff --git a/src/assets/image-621.png b/src/assets/image-621.png
new file mode 100644
index 0000000..a126a4b
Binary files /dev/null and b/src/assets/image-621.png differ
diff --git a/src/assets/image-622.png b/src/assets/image-622.png
new file mode 100644
index 0000000..4265a44
Binary files /dev/null and b/src/assets/image-622.png differ
diff --git a/src/assets/image-623.png b/src/assets/image-623.png
new file mode 100644
index 0000000..09b54a7
Binary files /dev/null and b/src/assets/image-623.png differ
diff --git a/src/assets/image-624.png b/src/assets/image-624.png
new file mode 100644
index 0000000..5d4a1eb
Binary files /dev/null and b/src/assets/image-624.png differ
diff --git a/src/assets/image-626.png b/src/assets/image-626.png
new file mode 100644
index 0000000..f0ed797
Binary files /dev/null and b/src/assets/image-626.png differ
diff --git a/src/assets/image-627.png b/src/assets/image-627.png
new file mode 100644
index 0000000..d37d43b
Binary files /dev/null and b/src/assets/image-627.png differ
diff --git a/src/assets/image-8.png b/src/assets/image-8.png
new file mode 100644
index 0000000..4d25e6f
Binary files /dev/null and b/src/assets/image-8.png differ
diff --git a/src/assets/image-81.png b/src/assets/image-81.png
new file mode 100644
index 0000000..5f32531
Binary files /dev/null and b/src/assets/image-81.png differ
diff --git a/src/assets/image-84.png b/src/assets/image-84.png
new file mode 100644
index 0000000..3776c4c
Binary files /dev/null and b/src/assets/image-84.png differ
diff --git a/src/assets/image-89.png b/src/assets/image-89.png
new file mode 100644
index 0000000..3c4d7f4
Binary files /dev/null and b/src/assets/image-89.png differ
diff --git a/src/assets/image-91.png b/src/assets/image-91.png
new file mode 100644
index 0000000..7fc8a35
Binary files /dev/null and b/src/assets/image-91.png differ
diff --git a/src/assets/images-in-text-1.png b/src/assets/images-in-text-1.png
new file mode 100644
index 0000000..a4e0b45
Binary files /dev/null and b/src/assets/images-in-text-1.png differ
diff --git a/src/assets/images-slidedeck-1-1.png b/src/assets/images-slidedeck-1-1.png
new file mode 100644
index 0000000..605549b
Binary files /dev/null and b/src/assets/images-slidedeck-1-1.png differ
diff --git a/src/assets/images-slidedeck-1-2.png b/src/assets/images-slidedeck-1-2.png
new file mode 100644
index 0000000..4dcaa83
Binary files /dev/null and b/src/assets/images-slidedeck-1-2.png differ
diff --git a/src/assets/images-slidedeck-1-3.png b/src/assets/images-slidedeck-1-3.png
new file mode 100644
index 0000000..de9cdbf
Binary files /dev/null and b/src/assets/images-slidedeck-1-3.png differ
diff --git a/src/assets/images-slidedeck-1.png b/src/assets/images-slidedeck-1.png
new file mode 100644
index 0000000..8521322
Binary files /dev/null and b/src/assets/images-slidedeck-1.png differ
diff --git a/src/assets/inclusive-3.png b/src/assets/inclusive-3.png
new file mode 100644
index 0000000..63c0f9c
Binary files /dev/null and b/src/assets/inclusive-3.png differ
diff --git a/src/assets/intent-and-virtual-intents.png b/src/assets/intent-and-virtual-intents.png
new file mode 100644
index 0000000..3c0c7ab
Binary files /dev/null and b/src/assets/intent-and-virtual-intents.png differ
diff --git a/src/assets/intents.png b/src/assets/intents.png
new file mode 100644
index 0000000..223bb64
Binary files /dev/null and b/src/assets/intents.png differ
diff --git a/src/assets/interface-elements.png b/src/assets/interface-elements.png
new file mode 100644
index 0000000..160ce45
Binary files /dev/null and b/src/assets/interface-elements.png differ
diff --git a/src/assets/l3-levels-1.png b/src/assets/l3-levels-1.png
new file mode 100644
index 0000000..30bc100
Binary files /dev/null and b/src/assets/l3-levels-1.png differ
diff --git a/src/assets/legoblocks.png b/src/assets/legoblocks.png
new file mode 100644
index 0000000..0977b65
Binary files /dev/null and b/src/assets/legoblocks.png differ
diff --git a/src/assets/llmaction-basicprompt-config-with-attributes.png b/src/assets/llmaction-basicprompt-config-with-attributes.png
new file mode 100644
index 0000000..8852b5d
Binary files /dev/null and b/src/assets/llmaction-basicprompt-config-with-attributes.png differ
diff --git a/src/assets/llmaction-basicprompt-config.png b/src/assets/llmaction-basicprompt-config.png
new file mode 100644
index 0000000..021bb08
Binary files /dev/null and b/src/assets/llmaction-basicprompt-config.png differ
diff --git a/src/assets/llmaction-setup-1.png b/src/assets/llmaction-setup-1.png
new file mode 100644
index 0000000..07cb8e5
Binary files /dev/null and b/src/assets/llmaction-setup-1.png differ
diff --git a/src/assets/llmactions-advancedsettings.png b/src/assets/llmactions-advancedsettings.png
new file mode 100644
index 0000000..9161477
Binary files /dev/null and b/src/assets/llmactions-advancedsettings.png differ
diff --git a/src/assets/llmactions-attributesforreuse-1.png b/src/assets/llmactions-attributesforreuse-1.png
new file mode 100644
index 0000000..66bcd4b
Binary files /dev/null and b/src/assets/llmactions-attributesforreuse-1.png differ
diff --git a/src/assets/llmactions-attributesforreuse-2-in-messages.png b/src/assets/llmactions-attributesforreuse-2-in-messages.png
new file mode 100644
index 0000000..2802f55
Binary files /dev/null and b/src/assets/llmactions-attributesforreuse-2-in-messages.png differ
diff --git a/src/assets/llmactions-safeguarding.png b/src/assets/llmactions-safeguarding.png
new file mode 100644
index 0000000..4bbb588
Binary files /dev/null and b/src/assets/llmactions-safeguarding.png differ
diff --git a/src/assets/llmactions-testpanel.png b/src/assets/llmactions-testpanel.png
new file mode 100644
index 0000000..7260b24
Binary files /dev/null and b/src/assets/llmactions-testpanel.png differ
diff --git a/src/assets/location.png b/src/assets/location.png
new file mode 100644
index 0000000..d078fc2
Binary files /dev/null and b/src/assets/location.png differ
diff --git a/src/assets/luis-add-to-intent.png b/src/assets/luis-add-to-intent.png
new file mode 100644
index 0000000..32f9871
Binary files /dev/null and b/src/assets/luis-add-to-intent.png differ
diff --git a/src/assets/luis-app-id.png b/src/assets/luis-app-id.png
new file mode 100644
index 0000000..46cdbca
Binary files /dev/null and b/src/assets/luis-app-id.png differ
diff --git a/src/assets/luis-create-intent.png b/src/assets/luis-create-intent.png
new file mode 100644
index 0000000..b9b343f
Binary files /dev/null and b/src/assets/luis-create-intent.png differ
diff --git a/src/assets/luis-intent-entity.png b/src/assets/luis-intent-entity.png
new file mode 100644
index 0000000..f2aac0d
Binary files /dev/null and b/src/assets/luis-intent-entity.png differ
diff --git a/src/assets/luis-interpreter-entity.png b/src/assets/luis-interpreter-entity.png
new file mode 100644
index 0000000..642c138
Binary files /dev/null and b/src/assets/luis-interpreter-entity.png differ
diff --git a/src/assets/luis-interpreter.png b/src/assets/luis-interpreter.png
new file mode 100644
index 0000000..ff1c93f
Binary files /dev/null and b/src/assets/luis-interpreter.png differ
diff --git a/src/assets/luis-preview.png b/src/assets/luis-preview.png
new file mode 100644
index 0000000..96cf123
Binary files /dev/null and b/src/assets/luis-preview.png differ
diff --git a/src/assets/luis-sub-key-app-url.png b/src/assets/luis-sub-key-app-url.png
new file mode 100644
index 0000000..c1c69a3
Binary files /dev/null and b/src/assets/luis-sub-key-app-url.png differ
diff --git a/src/assets/luis-test.png b/src/assets/luis-test.png
new file mode 100644
index 0000000..fd6ed84
Binary files /dev/null and b/src/assets/luis-test.png differ
diff --git a/src/assets/luis-utterances.png b/src/assets/luis-utterances.png
new file mode 100644
index 0000000..b77d982
Binary files /dev/null and b/src/assets/luis-utterances.png differ
diff --git a/src/assets/new-waiting-time-1.gif b/src/assets/new-waiting-time-1.gif
new file mode 100644
index 0000000..81ad31b
Binary files /dev/null and b/src/assets/new-waiting-time-1.gif differ
diff --git a/src/assets/no-messages-passing-conditions.png b/src/assets/no-messages-passing-conditions.png
new file mode 100644
index 0000000..8545adb
Binary files /dev/null and b/src/assets/no-messages-passing-conditions.png differ
diff --git a/src/assets/nomatch.png b/src/assets/nomatch.png
new file mode 100644
index 0000000..1d333b1
Binary files /dev/null and b/src/assets/nomatch.png differ
diff --git a/src/assets/null-alt-tag-1.png b/src/assets/null-alt-tag-1.png
new file mode 100644
index 0000000..6455558
Binary files /dev/null and b/src/assets/null-alt-tag-1.png differ
diff --git a/src/assets/oauth2-config.png b/src/assets/oauth2-config.png
new file mode 100644
index 0000000..f1bd1f9
Binary files /dev/null and b/src/assets/oauth2-config.png differ
diff --git a/src/assets/od-basicmodel.png b/src/assets/od-basicmodel.png
new file mode 100644
index 0000000..b451a44
Binary files /dev/null and b/src/assets/od-basicmodel.png differ
diff --git a/src/assets/od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0x13c2efd-scenario-0x13c2efa-1.png b/src/assets/od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0x13c2efd-scenario-0x13c2efa-1.png
new file mode 100644
index 0000000..68dfc6a
Binary files /dev/null and b/src/assets/od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0x13c2efd-scenario-0x13c2efa-1.png differ
diff --git a/src/assets/od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0x13c2efd-scenario-0x13c2efa-7.png b/src/assets/od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0x13c2efd-scenario-0x13c2efa-7.png
new file mode 100644
index 0000000..dbde160
Binary files /dev/null and b/src/assets/od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0x13c2efd-scenario-0x13c2efa-7.png differ
diff --git a/src/assets/od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0x13c2efd-scenario-0x13c2efa-8.png b/src/assets/od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0x13c2efd-scenario-0x13c2efa-8.png
new file mode 100644
index 0000000..7ae2799
Binary files /dev/null and b/src/assets/od-kamau-cloud-opendialog-ai-admin-conversation-builder-scene-0x13c2efd-scenario-0x13c2efa-8.png differ
diff --git a/src/assets/od-kamau-cloud-opendialog-ai-admin-demo-scenario-0x13c2efa-3.png b/src/assets/od-kamau-cloud-opendialog-ai-admin-demo-scenario-0x13c2efa-3.png
new file mode 100644
index 0000000..f8cf47c
Binary files /dev/null and b/src/assets/od-kamau-cloud-opendialog-ai-admin-demo-scenario-0x13c2efa-3.png differ
diff --git a/src/assets/od-kamau-cloud-opendialog-ai-admin-interpreters-mapping-99-scenario-0x13c2efa-1.png b/src/assets/od-kamau-cloud-opendialog-ai-admin-interpreters-mapping-99-scenario-0x13c2efa-1.png
new file mode 100644
index 0000000..c342424
Binary files /dev/null and b/src/assets/od-kamau-cloud-opendialog-ai-admin-interpreters-mapping-99-scenario-0x13c2efa-1.png differ
diff --git a/src/assets/od-kamau-cloud-opendialog-ai-admin-interpreters-mapping-99-scenario-0x13c2efa.png b/src/assets/od-kamau-cloud-opendialog-ai-admin-interpreters-mapping-99-scenario-0x13c2efa.png
new file mode 100644
index 0000000..7141643
Binary files /dev/null and b/src/assets/od-kamau-cloud-opendialog-ai-admin-interpreters-mapping-99-scenario-0x13c2efa.png differ
diff --git a/src/assets/od-workspacecreatenew.png b/src/assets/od-workspacecreatenew.png
new file mode 100644
index 0000000..1ad879e
Binary files /dev/null and b/src/assets/od-workspacecreatenew.png differ
diff --git a/src/assets/od-workspacedashboard.png b/src/assets/od-workspacedashboard.png
new file mode 100644
index 0000000..b4fe9d2
Binary files /dev/null and b/src/assets/od-workspacedashboard.png differ
diff --git a/src/assets/od-workspacenavigation.png b/src/assets/od-workspacenavigation.png
new file mode 100644
index 0000000..03fc772
Binary files /dev/null and b/src/assets/od-workspacenavigation.png differ
diff --git a/src/assets/opendialog-actions-122024.png b/src/assets/opendialog-actions-122024.png
new file mode 100644
index 0000000..2fbfefc
Binary files /dev/null and b/src/assets/opendialog-actions-122024.png differ
diff --git a/src/assets/opendialog-actions-2.png b/src/assets/opendialog-actions-2.png
new file mode 100644
index 0000000..4cbcf4c
Binary files /dev/null and b/src/assets/opendialog-actions-2.png differ
diff --git a/src/assets/opendialog-model.png b/src/assets/opendialog-model.png
new file mode 100644
index 0000000..89ade18
Binary files /dev/null and b/src/assets/opendialog-model.png differ
diff --git a/src/assets/personalisation.png b/src/assets/personalisation.png
new file mode 100644
index 0000000..73ac943
Binary files /dev/null and b/src/assets/personalisation.png differ
diff --git a/src/assets/pic-2.png b/src/assets/pic-2.png
new file mode 100644
index 0000000..b9ac320
Binary files /dev/null and b/src/assets/pic-2.png differ
diff --git a/src/assets/pic-3.png b/src/assets/pic-3.png
new file mode 100644
index 0000000..f3bfdd8
Binary files /dev/null and b/src/assets/pic-3.png differ
diff --git a/src/assets/pic-4.png b/src/assets/pic-4.png
new file mode 100644
index 0000000..fec49d3
Binary files /dev/null and b/src/assets/pic-4.png differ
diff --git a/src/assets/pic-5.png b/src/assets/pic-5.png
new file mode 100644
index 0000000..1a99f2c
Binary files /dev/null and b/src/assets/pic-5.png differ
diff --git a/src/assets/pick-a-date-and-time.png b/src/assets/pick-a-date-and-time.png
new file mode 100644
index 0000000..f17baba
Binary files /dev/null and b/src/assets/pick-a-date-and-time.png differ
diff --git a/src/assets/pick-a-time.png b/src/assets/pick-a-time.png
new file mode 100644
index 0000000..7920011
Binary files /dev/null and b/src/assets/pick-a-time.png differ
diff --git a/src/assets/pick-a-year-and-month.png b/src/assets/pick-a-year-and-month.png
new file mode 100644
index 0000000..5a58c76
Binary files /dev/null and b/src/assets/pick-a-year-and-month.png differ
diff --git a/src/assets/pick-a-year.png b/src/assets/pick-a-year.png
new file mode 100644
index 0000000..5485861
Binary files /dev/null and b/src/assets/pick-a-year.png differ
diff --git a/src/assets/placeholders-1.png b/src/assets/placeholders-1.png
new file mode 100644
index 0000000..3dc0bbb
Binary files /dev/null and b/src/assets/placeholders-1.png differ
diff --git a/src/assets/preview-attribute.jpg b/src/assets/preview-attribute.jpg
new file mode 100644
index 0000000..a3fb96e
Binary files /dev/null and b/src/assets/preview-attribute.jpg differ
diff --git a/src/assets/preview-considered-path.jpg b/src/assets/preview-considered-path.jpg
new file mode 100644
index 0000000..d156e33
Binary files /dev/null and b/src/assets/preview-considered-path.jpg differ
diff --git a/src/assets/preview-main-1.jpg b/src/assets/preview-main-1.jpg
new file mode 100644
index 0000000..3db6a96
Binary files /dev/null and b/src/assets/preview-main-1.jpg differ
diff --git a/src/assets/preview-overview.png b/src/assets/preview-overview.png
new file mode 100644
index 0000000..37844f6
Binary files /dev/null and b/src/assets/preview-overview.png differ
diff --git a/src/assets/preview-selected-path.jpg b/src/assets/preview-selected-path.jpg
new file mode 100644
index 0000000..6d13acb
Binary files /dev/null and b/src/assets/preview-selected-path.jpg differ
diff --git a/src/assets/preview-sidebar.jpg b/src/assets/preview-sidebar.jpg
new file mode 100644
index 0000000..161ee77
Binary files /dev/null and b/src/assets/preview-sidebar.jpg differ
diff --git a/src/assets/putting-it-all-together-1.png b/src/assets/putting-it-all-together-1.png
new file mode 100644
index 0000000..d9c92e1
Binary files /dev/null and b/src/assets/putting-it-all-together-1.png differ
diff --git a/src/assets/qna-add-to-intent.png b/src/assets/qna-add-to-intent.png
new file mode 100644
index 0000000..b9c74b6
Binary files /dev/null and b/src/assets/qna-add-to-intent.png differ
diff --git a/src/assets/qna-answer-intent.png b/src/assets/qna-answer-intent.png
new file mode 100644
index 0000000..a369779
Binary files /dev/null and b/src/assets/qna-answer-intent.png differ
diff --git a/src/assets/qna-interpreter.png b/src/assets/qna-interpreter.png
new file mode 100644
index 0000000..a6add83
Binary files /dev/null and b/src/assets/qna-interpreter.png differ
diff --git a/src/assets/qna-message.png b/src/assets/qna-message.png
new file mode 100644
index 0000000..899e26c
Binary files /dev/null and b/src/assets/qna-message.png differ
diff --git a/src/assets/qna-new-pair.png b/src/assets/qna-new-pair.png
new file mode 100644
index 0000000..7bf5de3
Binary files /dev/null and b/src/assets/qna-new-pair.png differ
diff --git a/src/assets/qna-pairs.png b/src/assets/qna-pairs.png
new file mode 100644
index 0000000..185d638
Binary files /dev/null and b/src/assets/qna-pairs.png differ
diff --git a/src/assets/qna-preview.png b/src/assets/qna-preview.png
new file mode 100644
index 0000000..c32aefe
Binary files /dev/null and b/src/assets/qna-preview.png differ
diff --git a/src/assets/qna-publish.png b/src/assets/qna-publish.png
new file mode 100644
index 0000000..8605c42
Binary files /dev/null and b/src/assets/qna-publish.png differ
diff --git a/src/assets/qna-test.png b/src/assets/qna-test.png
new file mode 100644
index 0000000..0ab7d96
Binary files /dev/null and b/src/assets/qna-test.png differ
diff --git a/src/assets/qna-turn.png b/src/assets/qna-turn.png
new file mode 100644
index 0000000..7a976a5
Binary files /dev/null and b/src/assets/qna-turn.png differ
diff --git a/src/assets/rag-diagram.png b/src/assets/rag-diagram.png
new file mode 100644
index 0000000..41a9636
Binary files /dev/null and b/src/assets/rag-diagram.png differ
diff --git a/src/assets/rag-llmactions.png b/src/assets/rag-llmactions.png
new file mode 100644
index 0000000..b7738e0
Binary files /dev/null and b/src/assets/rag-llmactions.png differ
diff --git a/src/assets/rag-overview.png b/src/assets/rag-overview.png
new file mode 100644
index 0000000..f0072b1
Binary files /dev/null and b/src/assets/rag-overview.png differ
diff --git a/src/assets/rag-response.png b/src/assets/rag-response.png
new file mode 100644
index 0000000..e2bd1a6
Binary files /dev/null and b/src/assets/rag-response.png differ
diff --git a/src/assets/rag-settings-use.png b/src/assets/rag-settings-use.png
new file mode 100644
index 0000000..c750fe2
Binary files /dev/null and b/src/assets/rag-settings-use.png differ
diff --git a/src/assets/rag-vectorisation.png b/src/assets/rag-vectorisation.png
new file mode 100644
index 0000000..5abaf23
Binary files /dev/null and b/src/assets/rag-vectorisation.png differ
diff --git a/src/assets/scenes.png b/src/assets/scenes.png
new file mode 100644
index 0000000..d047895
Binary files /dev/null and b/src/assets/scenes.png differ
diff --git a/src/assets/screen-shot-2022-02-17-at-11-15-00-am.png b/src/assets/screen-shot-2022-02-17-at-11-15-00-am.png
new file mode 100644
index 0000000..4abef4f
Binary files /dev/null and b/src/assets/screen-shot-2022-02-17-at-11-15-00-am.png differ
diff --git a/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-interpreters-configure-1125899907000034-2024-09-05-09-59-52.png b/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-interpreters-configure-1125899907000034-2024-09-05-09-59-52.png
new file mode 100644
index 0000000..181ab68
Binary files /dev/null and b/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-interpreters-configure-1125899907000034-2024-09-05-09-59-52.png differ
diff --git a/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-language-services-type-2024-09-05-09-54-57.png b/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-language-services-type-2024-09-05-09-54-57.png
new file mode 100644
index 0000000..91bc890
Binary files /dev/null and b/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-language-services-type-2024-09-05-09-54-57.png differ
diff --git a/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09-54-06.png b/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09-54-06.png
new file mode 100644
index 0000000..0c99d7c
Binary files /dev/null and b/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09-54-06.png differ
diff --git a/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09-57-33.png b/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09-57-33.png
new file mode 100644
index 0000000..1d2cffa
Binary files /dev/null and b/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09-57-33.png differ
diff --git a/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09-58-09.png b/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09-58-09.png
new file mode 100644
index 0000000..6f91648
Binary files /dev/null and b/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-intents-2024-09-05-09-58-09.png differ
diff --git a/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-prompt-2024-09-05-09-58-53.png b/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-prompt-2024-09-05-09-58-53.png
new file mode 100644
index 0000000..299d232
Binary files /dev/null and b/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-2251799814000009-prompt-2024-09-05-09-58-53.png differ
diff --git a/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-new-2024-09-05-09-56-18.png b/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-new-2024-09-05-09-56-18.png
new file mode 100644
index 0000000..affcb1d
Binary files /dev/null and b/src/assets/screencapture-semantic-classifiers-cloud-dev1-engineering-opendialog-app-admin-semantic-classifiers-new-2024-09-05-09-56-18.png differ
diff --git a/src/assets/screenshot-2021-11-01-at-09-19-03.png b/src/assets/screenshot-2021-11-01-at-09-19-03.png
new file mode 100644
index 0000000..8e3faac
Binary files /dev/null and b/src/assets/screenshot-2021-11-01-at-09-19-03.png differ
diff --git a/src/assets/screenshot-2021-11-01-at-09-22-33.png b/src/assets/screenshot-2021-11-01-at-09-22-33.png
new file mode 100644
index 0000000..164513d
Binary files /dev/null and b/src/assets/screenshot-2021-11-01-at-09-22-33.png differ
diff --git a/src/assets/screenshot-2021-11-01-at-09-24-03.png b/src/assets/screenshot-2021-11-01-at-09-24-03.png
new file mode 100644
index 0000000..133f086
Binary files /dev/null and b/src/assets/screenshot-2021-11-01-at-09-24-03.png differ
diff --git a/src/assets/screenshot-2021-11-01-at-09-28-03.png b/src/assets/screenshot-2021-11-01-at-09-28-03.png
new file mode 100644
index 0000000..3b5b784
Binary files /dev/null and b/src/assets/screenshot-2021-11-01-at-09-28-03.png differ
diff --git a/src/assets/screenshot-2021-11-01-at-09-32-48.png b/src/assets/screenshot-2021-11-01-at-09-32-48.png
new file mode 100644
index 0000000..40ce070
Binary files /dev/null and b/src/assets/screenshot-2021-11-01-at-09-32-48.png differ
diff --git a/src/assets/screenshot-2021-11-01-at-09-38-44.png b/src/assets/screenshot-2021-11-01-at-09-38-44.png
new file mode 100644
index 0000000..a5b4926
Binary files /dev/null and b/src/assets/screenshot-2021-11-01-at-09-38-44.png differ
diff --git a/src/assets/screenshot-2021-11-01-at-09-42-01.png b/src/assets/screenshot-2021-11-01-at-09-42-01.png
new file mode 100644
index 0000000..1c9bc79
Binary files /dev/null and b/src/assets/screenshot-2021-11-01-at-09-42-01.png differ
diff --git a/src/assets/screenshot-2021-11-01-at-09-42-38-1.png b/src/assets/screenshot-2021-11-01-at-09-42-38-1.png
new file mode 100644
index 0000000..9184f5b
Binary files /dev/null and b/src/assets/screenshot-2021-11-01-at-09-42-38-1.png differ
diff --git a/src/assets/screenshot-2023-05-11-at-13-01-33.png b/src/assets/screenshot-2023-05-11-at-13-01-33.png
new file mode 100644
index 0000000..25fa4fd
Binary files /dev/null and b/src/assets/screenshot-2023-05-11-at-13-01-33.png differ
diff --git a/src/assets/screenshot-2023-05-11-at-13-11-46.png b/src/assets/screenshot-2023-05-11-at-13-11-46.png
new file mode 100644
index 0000000..f93256c
Binary files /dev/null and b/src/assets/screenshot-2023-05-11-at-13-11-46.png differ
diff --git a/src/assets/screenshot-2023-05-11-at-13-12-57.png b/src/assets/screenshot-2023-05-11-at-13-12-57.png
new file mode 100644
index 0000000..86f3a82
Binary files /dev/null and b/src/assets/screenshot-2023-05-11-at-13-12-57.png differ
diff --git a/src/assets/screenshot-2023-05-11-at-14-33-04.png b/src/assets/screenshot-2023-05-11-at-14-33-04.png
new file mode 100644
index 0000000..a064894
Binary files /dev/null and b/src/assets/screenshot-2023-05-11-at-14-33-04.png differ
diff --git a/src/assets/screenshot-2023-05-11-at-14-52-54.png b/src/assets/screenshot-2023-05-11-at-14-52-54.png
new file mode 100644
index 0000000..4b474ca
Binary files /dev/null and b/src/assets/screenshot-2023-05-11-at-14-52-54.png differ
diff --git a/src/assets/screenshot-2023-05-11-at-14-54-32.png b/src/assets/screenshot-2023-05-11-at-14-54-32.png
new file mode 100644
index 0000000..a417183
Binary files /dev/null and b/src/assets/screenshot-2023-05-11-at-14-54-32.png differ
diff --git a/src/assets/screenshot-2023-05-11-at-14-54-46.png b/src/assets/screenshot-2023-05-11-at-14-54-46.png
new file mode 100644
index 0000000..02d1e70
Binary files /dev/null and b/src/assets/screenshot-2023-05-11-at-14-54-46.png differ
diff --git a/src/assets/screenshot-2023-05-11-at-18-20-26.png b/src/assets/screenshot-2023-05-11-at-18-20-26.png
new file mode 100644
index 0000000..4956fad
Binary files /dev/null and b/src/assets/screenshot-2023-05-11-at-18-20-26.png differ
diff --git a/src/assets/screenshot-2023-05-26-110829.png b/src/assets/screenshot-2023-05-26-110829.png
new file mode 100644
index 0000000..84fc24e
Binary files /dev/null and b/src/assets/screenshot-2023-05-26-110829.png differ
diff --git a/src/assets/screenshot-2023-05-26-111039.png b/src/assets/screenshot-2023-05-26-111039.png
new file mode 100644
index 0000000..435a29d
Binary files /dev/null and b/src/assets/screenshot-2023-05-26-111039.png differ
diff --git a/src/assets/screenshot-2023-05-26-at-12-51-54.png b/src/assets/screenshot-2023-05-26-at-12-51-54.png
new file mode 100644
index 0000000..39f5d30
Binary files /dev/null and b/src/assets/screenshot-2023-05-26-at-12-51-54.png differ
diff --git a/src/assets/screenshot-2023-05-26-at-12-59-19.png b/src/assets/screenshot-2023-05-26-at-12-59-19.png
new file mode 100644
index 0000000..e1a6e05
Binary files /dev/null and b/src/assets/screenshot-2023-05-26-at-12-59-19.png differ
diff --git a/src/assets/screenshot-2023-05-26-at-13-05-41.png b/src/assets/screenshot-2023-05-26-at-13-05-41.png
new file mode 100644
index 0000000..bcbac89
Binary files /dev/null and b/src/assets/screenshot-2023-05-26-at-13-05-41.png differ
diff --git a/src/assets/screenshot-2023-05-26-at-14-16-37.png b/src/assets/screenshot-2023-05-26-at-14-16-37.png
new file mode 100644
index 0000000..62147f0
Binary files /dev/null and b/src/assets/screenshot-2023-05-26-at-14-16-37.png differ
diff --git a/src/assets/screenshot-2023-05-31-at-16-18-00.png b/src/assets/screenshot-2023-05-31-at-16-18-00.png
new file mode 100644
index 0000000..8397000
Binary files /dev/null and b/src/assets/screenshot-2023-05-31-at-16-18-00.png differ
diff --git a/src/assets/screenshot-2023-06-01-at-10-05-01.png b/src/assets/screenshot-2023-06-01-at-10-05-01.png
new file mode 100644
index 0000000..b66a9bb
Binary files /dev/null and b/src/assets/screenshot-2023-06-01-at-10-05-01.png differ
diff --git a/src/assets/screenshot-2023-06-02-at-10-02-49.png b/src/assets/screenshot-2023-06-02-at-10-02-49.png
new file mode 100644
index 0000000..b4e96a0
Binary files /dev/null and b/src/assets/screenshot-2023-06-02-at-10-02-49.png differ
diff --git a/src/assets/screenshot-2023-07-28-at-16-26-42.png b/src/assets/screenshot-2023-07-28-at-16-26-42.png
new file mode 100644
index 0000000..576fabc
Binary files /dev/null and b/src/assets/screenshot-2023-07-28-at-16-26-42.png differ
diff --git a/src/assets/screenshot-2023-10-25-at-12-13-26.png b/src/assets/screenshot-2023-10-25-at-12-13-26.png
new file mode 100644
index 0000000..5f5b774
Binary files /dev/null and b/src/assets/screenshot-2023-10-25-at-12-13-26.png differ
diff --git a/src/assets/screenshot-2023-12-20-at-14-19-39-1.png b/src/assets/screenshot-2023-12-20-at-14-19-39-1.png
new file mode 100644
index 0000000..2e407a4
Binary files /dev/null and b/src/assets/screenshot-2023-12-20-at-14-19-39-1.png differ
diff --git a/src/assets/screenshot-2024-01-09-at-09-56-45.png b/src/assets/screenshot-2024-01-09-at-09-56-45.png
new file mode 100644
index 0000000..da6f621
Binary files /dev/null and b/src/assets/screenshot-2024-01-09-at-09-56-45.png differ
diff --git a/src/assets/screenshot-2024-01-09-at-09-58-23.png b/src/assets/screenshot-2024-01-09-at-09-58-23.png
new file mode 100644
index 0000000..45c9794
Binary files /dev/null and b/src/assets/screenshot-2024-01-09-at-09-58-23.png differ
diff --git a/src/assets/screenshot-2024-02-27-at-09-18-27.png b/src/assets/screenshot-2024-02-27-at-09-18-27.png
new file mode 100644
index 0000000..80950d0
Binary files /dev/null and b/src/assets/screenshot-2024-02-27-at-09-18-27.png differ
diff --git a/src/assets/screenshot-2024-02-27-at-11-21-09.png b/src/assets/screenshot-2024-02-27-at-11-21-09.png
new file mode 100644
index 0000000..b616eb6
Binary files /dev/null and b/src/assets/screenshot-2024-02-27-at-11-21-09.png differ
diff --git a/src/assets/screenshot-2024-02-27-at-11-22-29.png b/src/assets/screenshot-2024-02-27-at-11-22-29.png
new file mode 100644
index 0000000..f19434e
Binary files /dev/null and b/src/assets/screenshot-2024-02-27-at-11-22-29.png differ
diff --git a/src/assets/screenshot-2024-02-27-at-11-22-41.png b/src/assets/screenshot-2024-02-27-at-11-22-41.png
new file mode 100644
index 0000000..39d35b5
Binary files /dev/null and b/src/assets/screenshot-2024-02-27-at-11-22-41.png differ
diff --git a/src/assets/screenshot-2024-02-27-at-11-24-56.png b/src/assets/screenshot-2024-02-27-at-11-24-56.png
new file mode 100644
index 0000000..2a4dbbe
Binary files /dev/null and b/src/assets/screenshot-2024-02-27-at-11-24-56.png differ
diff --git a/src/assets/screenshot-2024-02-27-at-11-26-11.png b/src/assets/screenshot-2024-02-27-at-11-26-11.png
new file mode 100644
index 0000000..f5b93e9
Binary files /dev/null and b/src/assets/screenshot-2024-02-27-at-11-26-11.png differ
diff --git a/src/assets/screenshot-2024-02-27-at-12-58-47.png b/src/assets/screenshot-2024-02-27-at-12-58-47.png
new file mode 100644
index 0000000..27af7ef
Binary files /dev/null and b/src/assets/screenshot-2024-02-27-at-12-58-47.png differ
diff --git a/src/assets/screenshot-2024-03-27-at-08-40-11.png b/src/assets/screenshot-2024-03-27-at-08-40-11.png
new file mode 100644
index 0000000..1568212
Binary files /dev/null and b/src/assets/screenshot-2024-03-27-at-08-40-11.png differ
diff --git a/src/assets/screenshot-2024-04-25-at-22-56-32.png b/src/assets/screenshot-2024-04-25-at-22-56-32.png
new file mode 100644
index 0000000..018ecf1
Binary files /dev/null and b/src/assets/screenshot-2024-04-25-at-22-56-32.png differ
diff --git a/src/assets/screenshot-2024-04-28-at-10-15-32.png b/src/assets/screenshot-2024-04-28-at-10-15-32.png
new file mode 100644
index 0000000..45195be
Binary files /dev/null and b/src/assets/screenshot-2024-04-28-at-10-15-32.png differ
diff --git a/src/assets/screenshot-2024-04-29-at-07-48-11.png b/src/assets/screenshot-2024-04-29-at-07-48-11.png
new file mode 100644
index 0000000..8bbab72
Binary files /dev/null and b/src/assets/screenshot-2024-04-29-at-07-48-11.png differ
diff --git a/src/assets/screenshot-2024-06-04-at-10-14-39.png b/src/assets/screenshot-2024-06-04-at-10-14-39.png
new file mode 100644
index 0000000..3765c5a
Binary files /dev/null and b/src/assets/screenshot-2024-06-04-at-10-14-39.png differ
diff --git a/src/assets/screenshot-2024-06-04-at-10-18-10.png b/src/assets/screenshot-2024-06-04-at-10-18-10.png
new file mode 100644
index 0000000..30312ee
Binary files /dev/null and b/src/assets/screenshot-2024-06-04-at-10-18-10.png differ
diff --git a/src/assets/screenshot-2024-06-04-at-10-31-07.png b/src/assets/screenshot-2024-06-04-at-10-31-07.png
new file mode 100644
index 0000000..b58027a
Binary files /dev/null and b/src/assets/screenshot-2024-06-04-at-10-31-07.png differ
diff --git a/src/assets/screenshot-2024-06-04-at-10-31-14.png b/src/assets/screenshot-2024-06-04-at-10-31-14.png
new file mode 100644
index 0000000..469fb3b
Binary files /dev/null and b/src/assets/screenshot-2024-06-04-at-10-31-14.png differ
diff --git a/src/assets/screenshot-2024-06-04-at-10-38-15.png b/src/assets/screenshot-2024-06-04-at-10-38-15.png
new file mode 100644
index 0000000..31c494d
Binary files /dev/null and b/src/assets/screenshot-2024-06-04-at-10-38-15.png differ
diff --git a/src/assets/screenshot-2024-06-04-at-11-03-22.png b/src/assets/screenshot-2024-06-04-at-11-03-22.png
new file mode 100644
index 0000000..89d6104
Binary files /dev/null and b/src/assets/screenshot-2024-06-04-at-11-03-22.png differ
diff --git a/src/assets/screenshot-2024-06-04-at-11-07-11.png b/src/assets/screenshot-2024-06-04-at-11-07-11.png
new file mode 100644
index 0000000..5cd8f07
Binary files /dev/null and b/src/assets/screenshot-2024-06-04-at-11-07-11.png differ
diff --git a/src/assets/screenshot-2024-06-04-at-11-08-49.png b/src/assets/screenshot-2024-06-04-at-11-08-49.png
new file mode 100644
index 0000000..1b5a05c
Binary files /dev/null and b/src/assets/screenshot-2024-06-04-at-11-08-49.png differ
diff --git a/src/assets/screenshot-2024-06-04-at-11-25-53.png b/src/assets/screenshot-2024-06-04-at-11-25-53.png
new file mode 100644
index 0000000..1119c2f
Binary files /dev/null and b/src/assets/screenshot-2024-06-04-at-11-25-53.png differ
diff --git a/src/assets/screenshot-2024-06-04-at-11-26-02.png b/src/assets/screenshot-2024-06-04-at-11-26-02.png
new file mode 100644
index 0000000..b964515
Binary files /dev/null and b/src/assets/screenshot-2024-06-04-at-11-26-02.png differ
diff --git a/src/assets/screenshot-2024-06-05-at-13-47-08.png b/src/assets/screenshot-2024-06-05-at-13-47-08.png
new file mode 100644
index 0000000..5c4b917
Binary files /dev/null and b/src/assets/screenshot-2024-06-05-at-13-47-08.png differ
diff --git a/src/assets/screenshot-2024-06-05-at-15-36-41.png b/src/assets/screenshot-2024-06-05-at-15-36-41.png
new file mode 100644
index 0000000..29c2240
Binary files /dev/null and b/src/assets/screenshot-2024-06-05-at-15-36-41.png differ
diff --git a/src/assets/screenshot-2024-07-08-at-18-05-09.png b/src/assets/screenshot-2024-07-08-at-18-05-09.png
new file mode 100644
index 0000000..388fa2c
Binary files /dev/null and b/src/assets/screenshot-2024-07-08-at-18-05-09.png differ
diff --git a/src/assets/screenshot-2024-07-08-at-18-21-46.png b/src/assets/screenshot-2024-07-08-at-18-21-46.png
new file mode 100644
index 0000000..c1035aa
Binary files /dev/null and b/src/assets/screenshot-2024-07-08-at-18-21-46.png differ
diff --git a/src/assets/screenshot-2024-07-08-at-18-25-21.png b/src/assets/screenshot-2024-07-08-at-18-25-21.png
new file mode 100644
index 0000000..63878b3
Binary files /dev/null and b/src/assets/screenshot-2024-07-08-at-18-25-21.png differ
diff --git a/src/assets/screenshot-2024-07-08-at-18-30-02.png b/src/assets/screenshot-2024-07-08-at-18-30-02.png
new file mode 100644
index 0000000..58292e8
Binary files /dev/null and b/src/assets/screenshot-2024-07-08-at-18-30-02.png differ
diff --git a/src/assets/screenshot-2024-07-09-at-09-52-58-1.png b/src/assets/screenshot-2024-07-09-at-09-52-58-1.png
new file mode 100644
index 0000000..c6ceb57
Binary files /dev/null and b/src/assets/screenshot-2024-07-09-at-09-52-58-1.png differ
diff --git a/src/assets/screenshot-2024-07-09-at-09-52-58.png b/src/assets/screenshot-2024-07-09-at-09-52-58.png
new file mode 100644
index 0000000..c6ceb57
Binary files /dev/null and b/src/assets/screenshot-2024-07-09-at-09-52-58.png differ
diff --git a/src/assets/screenshot-2024-08-12-at-14-26-34.png b/src/assets/screenshot-2024-08-12-at-14-26-34.png
new file mode 100644
index 0000000..53cd8b4
Binary files /dev/null and b/src/assets/screenshot-2024-08-12-at-14-26-34.png differ
diff --git a/src/assets/screenshot-2024-08-23-at-15-30-55.png b/src/assets/screenshot-2024-08-23-at-15-30-55.png
new file mode 100644
index 0000000..5d4ad83
Binary files /dev/null and b/src/assets/screenshot-2024-08-23-at-15-30-55.png differ
diff --git a/src/assets/screenshot-2024-08-23-at-15-40-04.png b/src/assets/screenshot-2024-08-23-at-15-40-04.png
new file mode 100644
index 0000000..acc2722
Binary files /dev/null and b/src/assets/screenshot-2024-08-23-at-15-40-04.png differ
diff --git a/src/assets/screenshot-2024-09-03-at-13-04-59.png b/src/assets/screenshot-2024-09-03-at-13-04-59.png
new file mode 100644
index 0000000..4015511
Binary files /dev/null and b/src/assets/screenshot-2024-09-03-at-13-04-59.png differ
diff --git a/src/assets/screenshot-2024-09-26-at-10-28-52.png b/src/assets/screenshot-2024-09-26-at-10-28-52.png
new file mode 100644
index 0000000..f6e825a
Binary files /dev/null and b/src/assets/screenshot-2024-09-26-at-10-28-52.png differ
diff --git a/src/assets/screenshot-2024-09-26-at-10-32-32.png b/src/assets/screenshot-2024-09-26-at-10-32-32.png
new file mode 100644
index 0000000..c2b9db3
Binary files /dev/null and b/src/assets/screenshot-2024-09-26-at-10-32-32.png differ
diff --git a/src/assets/screenshot-2024-09-26-at-10-38-51.png b/src/assets/screenshot-2024-09-26-at-10-38-51.png
new file mode 100644
index 0000000..e32c9fc
Binary files /dev/null and b/src/assets/screenshot-2024-09-26-at-10-38-51.png differ
diff --git a/src/assets/screenshot-2024-10-01-at-15-28-40.png b/src/assets/screenshot-2024-10-01-at-15-28-40.png
new file mode 100644
index 0000000..35bdff3
Binary files /dev/null and b/src/assets/screenshot-2024-10-01-at-15-28-40.png differ
diff --git a/src/assets/screenshot-2024-10-01-at-15-31-13.png b/src/assets/screenshot-2024-10-01-at-15-31-13.png
new file mode 100644
index 0000000..4fe4398
Binary files /dev/null and b/src/assets/screenshot-2024-10-01-at-15-31-13.png differ
diff --git a/src/assets/screenshot-2024-10-01-at-15-31-33.png b/src/assets/screenshot-2024-10-01-at-15-31-33.png
new file mode 100644
index 0000000..0c3cda0
Binary files /dev/null and b/src/assets/screenshot-2024-10-01-at-15-31-33.png differ
diff --git a/src/assets/screenshot-2024-10-01-at-15-32-22.png b/src/assets/screenshot-2024-10-01-at-15-32-22.png
new file mode 100644
index 0000000..6a3ac83
Binary files /dev/null and b/src/assets/screenshot-2024-10-01-at-15-32-22.png differ
diff --git a/src/assets/screenshot-2024-11-09-at-11-35-40.png b/src/assets/screenshot-2024-11-09-at-11-35-40.png
new file mode 100644
index 0000000..152e2f6
Binary files /dev/null and b/src/assets/screenshot-2024-11-09-at-11-35-40.png differ
diff --git a/src/assets/screenshot-2024-11-09-at-18-23-33.png b/src/assets/screenshot-2024-11-09-at-18-23-33.png
new file mode 100644
index 0000000..ea3d1c1
Binary files /dev/null and b/src/assets/screenshot-2024-11-09-at-18-23-33.png differ
diff --git a/src/assets/screenshot-2024-11-09-at-18-24-23.png b/src/assets/screenshot-2024-11-09-at-18-24-23.png
new file mode 100644
index 0000000..521393a
Binary files /dev/null and b/src/assets/screenshot-2024-11-09-at-18-24-23.png differ
diff --git a/src/assets/screenshot-2024-11-09-at-18-28-28.png b/src/assets/screenshot-2024-11-09-at-18-28-28.png
new file mode 100644
index 0000000..9934a24
Binary files /dev/null and b/src/assets/screenshot-2024-11-09-at-18-28-28.png differ
diff --git a/src/assets/screenshot-2024-11-09-at-18-33-30.png b/src/assets/screenshot-2024-11-09-at-18-33-30.png
new file mode 100644
index 0000000..9f3d159
Binary files /dev/null and b/src/assets/screenshot-2024-11-09-at-18-33-30.png differ
diff --git a/src/assets/screenshot-2024-11-09-at-18-35-20-1.png b/src/assets/screenshot-2024-11-09-at-18-35-20-1.png
new file mode 100644
index 0000000..d7b49ac
Binary files /dev/null and b/src/assets/screenshot-2024-11-09-at-18-35-20-1.png differ
diff --git a/src/assets/screenshot-2024-11-09-at-18-43-42.png b/src/assets/screenshot-2024-11-09-at-18-43-42.png
new file mode 100644
index 0000000..6c66452
Binary files /dev/null and b/src/assets/screenshot-2024-11-09-at-18-43-42.png differ
diff --git a/src/assets/screenshot-2024-11-29-at-14-07-49.png b/src/assets/screenshot-2024-11-29-at-14-07-49.png
new file mode 100644
index 0000000..035e7a1
Binary files /dev/null and b/src/assets/screenshot-2024-11-29-at-14-07-49.png differ
diff --git a/src/assets/screenshot-2025-03-06-at-11-09-33-1.png b/src/assets/screenshot-2025-03-06-at-11-09-33-1.png
new file mode 100644
index 0000000..8107c9d
Binary files /dev/null and b/src/assets/screenshot-2025-03-06-at-11-09-33-1.png differ
diff --git a/src/assets/screenshot-2025-07-11-at-11-59-08.png b/src/assets/screenshot-2025-07-11-at-11-59-08.png
new file mode 100644
index 0000000..f5db896
Binary files /dev/null and b/src/assets/screenshot-2025-07-11-at-11-59-08.png differ
diff --git a/src/assets/screenshot-2025-07-11-at-16-48-00.png b/src/assets/screenshot-2025-07-11-at-16-48-00.png
new file mode 100644
index 0000000..e494c48
Binary files /dev/null and b/src/assets/screenshot-2025-07-11-at-16-48-00.png differ
diff --git a/src/assets/screenshot-2025-07-11-at-17-09-31.png b/src/assets/screenshot-2025-07-11-at-17-09-31.png
new file mode 100644
index 0000000..e634890
Binary files /dev/null and b/src/assets/screenshot-2025-07-11-at-17-09-31.png differ
diff --git a/src/assets/screenshot-2025-11-03-at-13-25-37.png b/src/assets/screenshot-2025-11-03-at-13-25-37.png
new file mode 100644
index 0000000..bf743f3
Binary files /dev/null and b/src/assets/screenshot-2025-11-03-at-13-25-37.png differ
diff --git a/src/assets/screenshot-2026-01-08-at-15-53-37.png b/src/assets/screenshot-2026-01-08-at-15-53-37.png
new file mode 100644
index 0000000..6adc1b6
Binary files /dev/null and b/src/assets/screenshot-2026-01-08-at-15-53-37.png differ
diff --git a/src/assets/screenshot-2026-01-08-at-16-33-54.png b/src/assets/screenshot-2026-01-08-at-16-33-54.png
new file mode 100644
index 0000000..17a7f96
Binary files /dev/null and b/src/assets/screenshot-2026-01-08-at-16-33-54.png differ
diff --git a/src/assets/search-message.png b/src/assets/search-message.png
new file mode 100644
index 0000000..eb7cba0
Binary files /dev/null and b/src/assets/search-message.png differ
diff --git a/src/assets/search-scenario-view.png b/src/assets/search-scenario-view.png
new file mode 100644
index 0000000..81f00f9
Binary files /dev/null and b/src/assets/search-scenario-view.png differ
diff --git a/src/assets/secret-managemnet.png b/src/assets/secret-managemnet.png
new file mode 100644
index 0000000..84e828f
Binary files /dev/null and b/src/assets/secret-managemnet.png differ
diff --git a/src/assets/select-source-type.png b/src/assets/select-source-type.png
new file mode 100644
index 0000000..66c3b70
Binary files /dev/null and b/src/assets/select-source-type.png differ
diff --git a/src/assets/sensory-2.png b/src/assets/sensory-2.png
new file mode 100644
index 0000000..20a7b00
Binary files /dev/null and b/src/assets/sensory-2.png differ
diff --git a/src/assets/smiley-flash-1.gif b/src/assets/smiley-flash-1.gif
new file mode 100644
index 0000000..27e57b0
Binary files /dev/null and b/src/assets/smiley-flash-1.gif differ
diff --git a/src/assets/spaces-it4t0sjdqeqcxi1fucau-uploads-mwtxl3uefl5avnjieqbh-img-6998.webp b/src/assets/spaces-it4t0sjdqeqcxi1fucau-uploads-mwtxl3uefl5avnjieqbh-img-6998.webp
new file mode 100644
index 0000000..2adc51a
Binary files /dev/null and b/src/assets/spaces-it4t0sjdqeqcxi1fucau-uploads-mwtxl3uefl5avnjieqbh-img-6998.webp differ
diff --git a/src/assets/spaces-it4t0sjdqeqcxi1fucau-uploads-uk8yzf49ckvtwbfi1qdg-img-6996-1.webp b/src/assets/spaces-it4t0sjdqeqcxi1fucau-uploads-uk8yzf49ckvtwbfi1qdg-img-6996-1.webp
new file mode 100644
index 0000000..139823f
Binary files /dev/null and b/src/assets/spaces-it4t0sjdqeqcxi1fucau-uploads-uk8yzf49ckvtwbfi1qdg-img-6996-1.webp differ
diff --git a/src/assets/start-from-scratch-scenario.png b/src/assets/start-from-scratch-scenario.png
new file mode 100644
index 0000000..6fe186f
Binary files /dev/null and b/src/assets/start-from-scratch-scenario.png differ
diff --git a/src/assets/test-agent.png b/src/assets/test-agent.png
new file mode 100644
index 0000000..c7e6c0e
Binary files /dev/null and b/src/assets/test-agent.png differ
diff --git a/src/assets/text.png b/src/assets/text.png
new file mode 100644
index 0000000..866ab3c
Binary files /dev/null and b/src/assets/text.png differ
diff --git a/src/assets/translate-languageselection.png b/src/assets/translate-languageselection.png
new file mode 100644
index 0000000..47be0c3
Binary files /dev/null and b/src/assets/translate-languageselection.png differ
diff --git a/src/assets/turns.png b/src/assets/turns.png
new file mode 100644
index 0000000..9af0e6d
Binary files /dev/null and b/src/assets/turns.png differ
diff --git a/src/assets/untitled.png b/src/assets/untitled.png
new file mode 100644
index 0000000..2fbace3
Binary files /dev/null and b/src/assets/untitled.png differ
diff --git a/src/assets/url-1.png b/src/assets/url-1.png
new file mode 100644
index 0000000..c9f94f2
Binary files /dev/null and b/src/assets/url-1.png differ
diff --git a/src/assets/url-2.png b/src/assets/url-2.png
new file mode 100644
index 0000000..af629db
Binary files /dev/null and b/src/assets/url-2.png differ
diff --git a/src/assets/url-3.png b/src/assets/url-3.png
new file mode 100644
index 0000000..3da1b2a
Binary files /dev/null and b/src/assets/url-3.png differ
diff --git a/src/assets/url-4.png b/src/assets/url-4.png
new file mode 100644
index 0000000..0273558
Binary files /dev/null and b/src/assets/url-4.png differ
diff --git a/src/assets/usinglanguageservice.png b/src/assets/usinglanguageservice.png
new file mode 100644
index 0000000..5b384fa
Binary files /dev/null and b/src/assets/usinglanguageservice.png differ
diff --git a/src/assets/vectorise.png b/src/assets/vectorise.png
new file mode 100644
index 0000000..3b8de47
Binary files /dev/null and b/src/assets/vectorise.png differ
diff --git a/src/assets/webhook-auth-demo.png b/src/assets/webhook-auth-demo.png
new file mode 100644
index 0000000..c0294fb
Binary files /dev/null and b/src/assets/webhook-auth-demo.png differ
diff --git a/src/assets/welcome-conversation.png b/src/assets/welcome-conversation.png
new file mode 100644
index 0000000..7369d6d
Binary files /dev/null and b/src/assets/welcome-conversation.png differ
diff --git a/src/assets/welcome-scene.png b/src/assets/welcome-scene.png
new file mode 100644
index 0000000..d8a5668
Binary files /dev/null and b/src/assets/welcome-scene.png differ
diff --git a/src/assets/welcome-turn.png b/src/assets/welcome-turn.png
new file mode 100644
index 0000000..b30b0f7
Binary files /dev/null and b/src/assets/welcome-turn.png differ
diff --git a/src/assets/zrzut-ekranu-2025-11-3-o-14-37-53.png b/src/assets/zrzut-ekranu-2025-11-3-o-14-37-53.png
new file mode 100644
index 0000000..49645f0
Binary files /dev/null and b/src/assets/zrzut-ekranu-2025-11-3-o-14-37-53.png differ
diff --git a/src/assets/zrzut-ekranu-2025-11-3-o-14-48-02.png b/src/assets/zrzut-ekranu-2025-11-3-o-14-48-02.png
new file mode 100644
index 0000000..90d8e8e
Binary files /dev/null and b/src/assets/zrzut-ekranu-2025-11-3-o-14-48-02.png differ
diff --git a/src/components/CoverCard.astro b/src/components/CoverCard.astro
new file mode 100644
index 0000000..b22fe53
--- /dev/null
+++ b/src/components/CoverCard.astro
@@ -0,0 +1,85 @@
+---
+/**
+ * A card with a cover image, as GitBook renders a `data-card-cover` card table.
+ *
+ * Starlight's <LinkCard> has no image slot, so conversion used to discard the cover and
+ * emit a plain card — 13 references across 4 pages, pointing at 10 distinct assets.
+ *
+ * The image is resolved through import.meta.glob rather than taken as a path, so it goes
+ * through astro:assets and is optimised. The glob is lazy: only the covers actually
+ * referenced are bundled, not all 509 assets. An unresolvable cover throws rather than
+ * rendering a broken card, which is how the rest of this pipeline treats a reference it
+ * cannot satisfy.
+ */
+import { Image } from 'astro:assets';
+
+interface Props {
+ title: string;
+ description?: string;
+ href: string;
+ cover: string;
+}
+
+const { title, description, href, cover } = Astro.props;
+
+const covers = import.meta.glob<{ default: ImageMetadata }>(
+ '/src/assets/**/*.{png,jpg,jpeg,webp,avif}'
+);
+
+const load = covers[cover];
+if (!load) throw new Error(`CoverCard: no asset at ${cover}`);
+const image = (await load()).default;
+---
+
+<a class="od-cover-card" href={href}>
+ <Image class="od-cover-image" src={image} alt="" widths={[371, 742]} sizes="371px" />
+ <span class="od-cover-body">
+ <span class="od-cover-title">{title}</span>
+ {description && <span class="od-cover-description">{description}</span>}
+ </span>
+</a>
+
+<style>
+ /*
+ * GitBook's covers render at 371x208 with object-fit: cover, two to a row, above the
+ * title and description. Unlayered so the anchor reset beats starlight.content.
+ */
+ .od-cover-card {
+ display: flex;
+ flex-direction: column;
+ border: 1px solid var(--sl-color-gray-5);
+ border-radius: 0.5rem;
+ overflow: hidden;
+ text-decoration: none;
+ color: inherit;
+ height: 100%;
+ }
+
+ .od-cover-card:hover {
+ border-color: var(--sl-color-gray-4);
+ }
+
+ .od-cover-image {
+ width: 100%;
+ aspect-ratio: 371 / 208;
+ object-fit: cover;
+ display: block;
+ }
+
+ .od-cover-body {
+ display: flex;
+ flex-direction: column;
+ gap: 0.5rem;
+ padding: 1rem;
+ }
+
+ .od-cover-title {
+ font-weight: 600;
+ color: var(--sl-color-text-accent);
+ }
+
+ .od-cover-description {
+ font-size: var(--sl-text-sm);
+ color: var(--sl-color-gray-3);
+ }
+</style>
diff --git a/src/components/Embed.astro b/src/components/Embed.astro
deleted file mode 100644
index 82e64ad..0000000
--- a/src/components/Embed.astro
+++ /dev/null
@@ -1,76 +0,0 @@
----
-/**
- * Renders a Loom or YouTube video in a lazily-loaded 16:9 iframe.
- *
- * GitBook's {% embed %} shows a caption under the video; `title` reproduces that and doubles
- * as the iframe's accessible name.
- */
-interface Props {
- url: string;
- title?: string;
-}
-
-const { url, title } = Astro.props;
-
-/**
- * Maps a share URL to its embeddable form.
- *
- * scripts/lib/gitbook-blocks.mjs's isVideoEmbed decides which URLs reach this component at
- * all, accepting only the shapes handled below. Keep the two in sync.
- */
-function embedSrc(raw: string): string | null {
- const parsed = new URL(raw);
- const host = parsed.hostname.replace(/^www\./, '');
- if (host === 'youtu.be') return `https://www.youtube-nocookie.com/embed/${parsed.pathname.slice(1)}`;
- if (host === 'youtube.com') {
- const id = parsed.searchParams.get('v');
- return id ? `https://www.youtube-nocookie.com/embed/${id}` : null;
- }
- if (host === 'loom.com') return raw.replace('/share/', '/embed/').split('?')[0];
- return null;
-}
-
-const src = embedSrc(url);
----
-
-{
- src ? (
- <figure class="od-embed">
- <div class="od-embed-frame">
- <iframe
- src={src}
- title={title ?? 'Embedded video'}
- loading="lazy"
- allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
- allowfullscreen
- />
- </div>
- {title && <figcaption>{title}</figcaption>}
- </figure>
- ) : (
- <p><a href={url}>{title ?? url}</a></p>
- )
-}
-
-<style>
- .od-embed {
- margin: 1.5rem 0;
- }
- .od-embed-frame {
- aspect-ratio: 16 / 9;
- border-radius: 0.5rem;
- overflow: hidden;
- border: 1px solid var(--sl-color-gray-5);
- }
- .od-embed-frame iframe {
- width: 100%;
- height: 100%;
- border: 0;
- display: block;
- }
- .od-embed figcaption {
- margin-top: 0.5rem;
- font-size: var(--sl-text-sm);
- color: var(--sl-color-gray-3);
- }
-</style>
diff --git a/src/components/Header.astro b/src/components/Header.astro
new file mode 100644
index 0000000..2cade89
--- /dev/null
+++ b/src/components/Header.astro
@@ -0,0 +1,117 @@
+---
+/**
+ * Site header, ordered as GitBook orders it.
+ *
+ * Starlight's own header is a three-column grid — title, search, then a right-hand
+ * group of social icons and the theme and language selects — with the search column
+ * width computed to line up with the content column. GitBook runs title on the left
+ * and `opendialog.ai`, the "Talk to an expert" call to action and search together on
+ * the right, and aligns none of them to the content column, so that calc has nothing
+ * to preserve here and a flex row replaces it.
+ *
+ * The links sit in their own wrapper rather than beside search because Starlight
+ * hides the right-hand group below the `md` breakpoint while search stays visible;
+ * putting search in that wrapper would hide it on mobile.
+ */
+import config from 'virtual:starlight/user-config';
+
+import Search from 'virtual:starlight/components/Search';
+import SiteTitle from 'virtual:starlight/components/SiteTitle';
+
+/**
+ * Render the `Search` component if Pagefind is enabled or the default search component has been overridden.
+ */
+const shouldRenderSearch =
+ config.pagefind || config.components.Search !== '@astrojs/starlight/components/Search.astro';
+---
+
+<div class="header">
+ <div class="title-wrapper sl-flex">
+ <SiteTitle />
+ </div>
+
+ <div class="sl-flex right-group">
+ <div class="sl-hidden md:sl-flex print:hidden header-links">
+ <a href="https://opendialog.ai/">opendialog.ai</a>
+ <a class="cta" href="https://opendialog.ai/talk-to-expert/">Talk to an expert</a>
+ </div>
+
+ <div class="sl-flex print:hidden search-wrapper">
+ {shouldRenderSearch && <Search />}
+ </div>
+ </div>
+</div>
+
+<style>
+ /*
+ * Unlayered, so these win over the Starlight header rules they replace, which live
+ * in starlight.core. The selectors are scoped to this component and reach nothing
+ * else.
+ */
+ .header {
+ display: flex;
+ align-items: center;
+ gap: var(--sl-nav-gap);
+ height: 100%;
+ }
+
+ .title-wrapper {
+ /* Prevent long titles overflowing and covering the search and menu buttons on narrow viewports. */
+ overflow: clip;
+ /* Avoid clipping focus ring around link inside title wrapper. */
+ padding: 0.25rem;
+ margin: -0.25rem;
+ min-width: 0;
+ }
+
+ /* Pushes the links and search to the right edge, leaving the title on the left. */
+ .right-group {
+ margin-inline-start: auto;
+ align-items: center;
+ gap: 1.5rem;
+ min-width: 0;
+ }
+
+ .header-links {
+ align-items: center;
+ gap: 1.5rem;
+ font-size: var(--sl-text-sm);
+ /* Poppins' normal line-height is 25px at 14px, which makes the call to action
+ 43px tall against GitBook's 39. GitBook sets 20px. */
+ line-height: 1.25rem;
+ }
+
+ .header-links a {
+ color: var(--sl-color-gray-3);
+ text-decoration: none;
+ white-space: nowrap;
+ }
+
+ .header-links a:hover,
+ .header-links a:focus-visible {
+ color: var(--sl-color-white);
+ }
+
+ /*
+ * GitBook's call to action is a quiet outlined button, not a filled brand-blue
+ * one: white fill, 1px hairline, 12px radius, 8/16 padding.
+ */
+ .header-links .cta {
+ padding: 0.5rem 1rem;
+ border: 1px solid var(--sl-color-gray-5);
+ border-radius: 0.75rem;
+ background-color: var(--sl-color-bg);
+ }
+
+ .header-links .cta:hover,
+ .header-links .cta:focus-visible {
+ border-color: var(--sl-color-gray-4);
+ }
+
+ /* Without a bound, Starlight's search button grows to fill the flex row. */
+ .search-wrapper {
+ flex: 0 1 auto;
+ min-width: 0;
+ max-width: 16rem;
+ }
+</style>
diff --git a/src/components/MobileMenuFooter.astro b/src/components/MobileMenuFooter.astro
new file mode 100644
index 0000000..ddcf9c9
--- /dev/null
+++ b/src/components/MobileMenuFooter.astro
@@ -0,0 +1,11 @@
+---
+/**
+ * Renders nothing: everything this footer holds has been removed.
+ *
+ * Starlight's version carries the social icons, the theme select and the language
+ * select. The site declares no social links, ships light-only so ThemeSelect is
+ * blank, and is single-locale so LanguageSelect renders nothing — leaving an empty
+ * strip that still drew its own border-top and padding at the foot of the mobile
+ * menu, 17px tall, where GitBook shows nothing at all.
+ */
+---
diff --git a/src/components/PageTitle.astro b/src/components/PageTitle.astro
index af43abc..8ef8bab 100644
--- a/src/components/PageTitle.astro
+++ b/src/components/PageTitle.astro
@@ -1,37 +1,169 @@
---
/**
- * Renders the frontmatter description beneath the page title.
+ * Renders the section breadcrumb above the page title and the frontmatter
+ * description beneath it.
*
* GitBook shows a page's description as visible lead text under the heading. Starlight
* uses it only for <meta name="description">, so without this override 71 pages lose
* content the reader can currently see.
+ *
+ * The breadcrumb is the chain of ancestor groups from the section down to the
+ * immediate parent, excluding the page itself — one entry for a page sitting directly
+ * in a section, two for a nested one. Every entry is a link, as on GitBook.
+ *
+ * Targets are resolved to the first page inside each group rather than to a section
+ * URL. GitBook links its top-level crumb to paths like /core-concepts, which are not
+ * pages: it 307-redirects them to the section's first page (/core-concepts →
+ * /core-concepts/the-opendialog-model, /getting-started-1 → /). Those paths are in
+ * neither the live sitemap nor route-map.json, so reproducing them here would add a
+ * broken internal link. Pointing straight at the redirect target reaches the same page
+ * without the hop, which is the same reasoning behind `trailingSlash: 'never'`.
+ *
+ * One rule covers both levels because scripts/lib/sidebar-tree.mjs makes a parent
+ * page the first item of its own group, so "the first link in this group" is the
+ * parent's own page for an intermediate group and the section's first page for a
+ * top-level one.
*/
// Starlight's PAGE_TITLE_ID is not reachable from a public export subpath, so the value
// is inlined. It must stay '_top': the table of contents' "Overview" entry links to #_top.
const PAGE_TITLE_ID = '_top';
const { title, description } = Astro.locals.starlightRoute.entry.data;
+const { sidebar } = Astro.locals.starlightRoute;
+
+/** The first link inside a group, depth-first: the page that group header stands for. */
+function firstLink(entries) {
+ for (const entry of entries) {
+ if (entry.type === 'link') return entry;
+ const nested = firstLink(entry.entries);
+ if (nested) return nested;
+ }
+ return undefined;
+}
+
+/** The groups enclosing the current page, outermost first. */
+function ancestors(entries, chain = []) {
+ for (const entry of entries) {
+ if (entry.type === 'link') {
+ if (entry.isCurrent) return chain;
+ continue;
+ }
+ const found = ancestors(entry.entries, [...chain, entry]);
+ if (found) return found;
+ }
+ return undefined;
+}
+
+const crumbs = (ancestors(sidebar) ?? [])
+ .map((group, depth) => {
+ const link = firstLink(group.entries);
+ if (!link) return undefined;
+ // An intermediate group *is* a page, and GitBook omits that crumb when it is
+ // the page being viewed rather than linking it to itself. A top-level section
+ // is a structural bucket and never a page, so it always shows — GitBook keeps
+ // "GETTING STARTED" on / even though its target redirects back to /. Where the
+ // section's first page is the current page, the crumb renders as plain text so
+ // it still orients the reader without being a link to here.
+ if (depth > 0 && link.isCurrent) return undefined;
+ return { label: group.label, href: link.href, isHere: link.isCurrent };
+ })
+ .filter(Boolean);
---
+{
+ crumbs.length > 0 && (
+ <nav class="breadcrumb" aria-label="Breadcrumb">
+ <ol>
+ {crumbs.map((crumb) => (
+ <li>
+ {crumb.isHere ? <span>{crumb.label}</span> : <a href={crumb.href}>{crumb.label}</a>}
+ <svg
+ class="separator"
+ aria-hidden="true"
+ viewBox="0 0 8 8"
+ width="8"
+ height="8"
+ fill="none"
+ stroke="currentColor"
+ stroke-width="1.5"
+ stroke-linecap="round"
+ stroke-linejoin="round"
+ >
+ <path d="M2.5 1 5.5 4 2.5 7" />
+ </svg>
+ </li>
+ ))}
+ </ol>
+ </nav>
+ )
+}
+
<h1 id={PAGE_TITLE_ID}>{title}</h1>
{description && <p class="page-description">{description}</p>}
<style>
- @layer starlight.core {
- h1 {
- margin-top: 1rem;
- font-size: var(--sl-text-h1);
- line-height: var(--sl-line-height-headings);
- font-weight: 600;
- color: var(--sl-color-white);
- }
+ /*
+ * Unlayered, so these win over the Starlight rules they replace, which live in
+ * starlight.core. The selectors are scoped to this component and reach nothing else.
+ */
+ .breadcrumb {
+ margin-top: 1rem;
+ /* --sl-text-xs is 13px; GitBook sets 12px. */
+ font-size: 0.75rem;
+ line-height: 1.25rem;
+ }
- .page-description {
- margin-top: 0.75rem;
- font-size: var(--sl-text-lg);
- line-height: 1.6;
- color: var(--sl-color-gray-3);
- text-wrap: pretty;
- }
+ .breadcrumb ol {
+ display: flex;
+ flex-wrap: wrap;
+ align-items: center;
+ gap: 0.5rem;
+ list-style: none;
+ padding: 0;
+ margin: 0;
+ }
+
+ .breadcrumb li {
+ display: flex;
+ align-items: center;
+ gap: 0.5rem;
+ }
+
+ .breadcrumb a {
+ color: var(--sl-color-text-accent);
+ text-decoration: none;
+ }
+
+ .breadcrumb a:hover,
+ .breadcrumb a:focus-visible {
+ text-decoration: underline;
+ }
+
+ /* The trailing chevron would dangle after the last crumb. */
+ .breadcrumb li:last-child .separator {
+ display: none;
+ }
+
+ .separator {
+ color: var(--sl-color-gray-4);
+ flex-shrink: 0;
+ }
+
+ /* GitBook sets the page title heavier than the rest of the scale: 700 against 600. */
+ h1 {
+ margin-top: 0.75rem;
+ font-size: var(--sl-text-h1);
+ line-height: 1.25;
+ letter-spacing: -0.025em;
+ font-weight: 700;
+ color: var(--sl-color-white);
+ }
+
+ .page-description {
+ margin-top: 0.75rem;
+ font-size: var(--sl-text-lg);
+ line-height: 1.6;
+ color: var(--sl-color-gray-3);
+ text-wrap: pretty;
}
</style>
diff --git a/src/components/Sidebar.astro b/src/components/Sidebar.astro
new file mode 100644
index 0000000..34f3b31
--- /dev/null
+++ b/src/components/Sidebar.astro
@@ -0,0 +1,26 @@
+---
+/**
+ * Sidebar, wired to the local sublist that renders parent pages as linkable rows.
+ *
+ * This exists only because `SidebarSublist` is not an overridable component — the
+ * `components` schema accepts Sidebar but not SidebarSublist, and Starlight's own
+ * Sidebar imports it by relative path rather than through the virtual module. Naming
+ * SidebarSublist in astro.config.mjs is accepted and silently does nothing. Overriding
+ * Sidebar is the supported way to reach it.
+ *
+ * Otherwise identical to Starlight's own Sidebar.
+ */
+import MobileMenuFooter from 'virtual:starlight/components/MobileMenuFooter';
+import SidebarPersister from '@astrojs/starlight/components/SidebarPersister.astro';
+import SidebarSublist from './SidebarSublist.astro';
+
+const { sidebar } = Astro.locals.starlightRoute;
+---
+
+<SidebarPersister>
+ <SidebarSublist sublist={sidebar} />
+</SidebarPersister>
+
+<div class="md:sl-hidden">
+ <MobileMenuFooter />
+</div>
diff --git a/src/components/SidebarSublist.astro b/src/components/SidebarSublist.astro
new file mode 100644
index 0000000..061e886
--- /dev/null
+++ b/src/components/SidebarSublist.astro
@@ -0,0 +1,286 @@
+---
+/**
+ * Sidebar list that renders a parent page as one clickable, expandable row.
+ *
+ * Starlight sidebar groups cannot be links — SidebarGroupSchema is label / translations
+ * / badge / collapsed, with `attrs: z.never()` — so scripts/lib/sidebar-tree.mjs gives a
+ * page that also has children a group whose first item is that page, repeating the
+ * label. That is correct data but renders as 41 duplicated rows, 245 in total against
+ * GitBook's 204.
+ *
+ * This promotes that first item into the group's own row: the label becomes a link and
+ * the caret beside it toggles the group, which is what GitBook shows. The duplicate is
+ * then dropped from the children.
+ *
+ * The rule keys on the first entry being a link carrying the group's own label, which is
+ * exactly how sidebar-tree.mjs marks a parent page. Sections do not match it — their
+ * first entry is the section's first page under a different label — so they keep
+ * rendering as plain, unlinked headers, which is also what GitBook does.
+ *
+ * Styles are carried over from Starlight's own SidebarSublist, since overriding a
+ * component replaces its scoped styles too.
+ */
+import { Icon, Badge } from '@astrojs/starlight/components';
+import SidebarRestorePoint from '@astrojs/starlight/components/SidebarRestorePoint.astro';
+
+interface Props {
+ sublist: any[];
+ nested?: boolean;
+}
+
+const { sublist, nested } = Astro.props;
+
+/** Every link beneath these entries, ignoring grouping. */
+function flatten(entries: any[]): any[] {
+ return entries.flatMap((entry) => (entry.type === 'group' ? flatten(entry.entries) : entry));
+}
+
+/**
+ * The page a group stands for, if it has one: sidebar-tree.mjs places it first and gives
+ * it the group's label.
+ */
+function ownPage(group: any) {
+ const first = group.entries[0];
+ return first && first.type === 'link' && first.label === group.label ? first : undefined;
+}
+
+const items = sublist.map((entry) => {
+ if (entry.type === 'link') return { entry, group: false as const };
+ // Only nested groups stand for a page. A top-level entry is a section, which is a
+ // structural bucket, and GitBook renders those as plain unlinked headers. Without
+ // this gate the "Release Notes" section promotes itself, because its label happens
+ // to equal its only page's label — a coincidence, not the parent-page structure.
+ const own = nested ? ownPage(entry) : undefined;
+ return {
+ entry,
+ group: true as const,
+ own,
+ children: own ? entry.entries.slice(1) : entry.entries,
+ // Starlight's own rule: a collapsed group still opens when it holds the current
+ // page, so the nav opens along the path to the page being read.
+ open: flatten(entry.entries).some((i: any) => i.isCurrent) || !entry.collapsed,
+ };
+});
+---
+
+<ul class:list={{ 'top-level': !nested }}>
+ {
+ items.map((item) =>
+ !item.group ? (
+ <li>
+ <a
+ href={item.entry.href}
+ aria-current={item.entry.isCurrent ? 'page' : undefined}
+ class:list={[item.entry.attrs.class]}
+ {...item.entry.attrs}
+ >
+ <span>{item.entry.label}</span>
+ {item.entry.badge && (
+ <Badge
+ variant={item.entry.badge.variant}
+ class={item.entry.badge.class}
+ text={item.entry.badge.text}
+ />
+ )}
+ </a>
+ </li>
+ ) : (
+ <li>
+ <details open={item.open}>
+ <summary class:list={{ linked: !!item.own }}>
+ {item.own ? (
+ <a
+ class="group-link"
+ href={item.own.href}
+ aria-current={item.own.isCurrent ? 'page' : undefined}
+ >
+ {item.entry.label}
+ </a>
+ ) : (
+ <span class="group-label">
+ <span class="section-label">{item.entry.label}</span>
+ </span>
+ )}
+ {item.entry.badge && (
+ <Badge
+ variant={item.entry.badge.variant}
+ class={item.entry.badge.class}
+ text={item.entry.badge.text}
+ />
+ )}
+ <Icon name="right-caret" class="caret" size="1.25rem" />
+ </summary>
+ <SidebarRestorePoint />
+ <Astro.self sublist={item.children} nested />
+ </details>
+ </li>
+ )
+ )
+ }
+</ul>
+
+<script>
+ // A click on a group's label must navigate without also toggling the group. The
+ // event would otherwise bubble to the enclosing <summary>, whose default action
+ // collapses it, and SidebarPersister would carry that collapsed state across the
+ // navigation — so landing on a parent page would hide the children beneath it.
+ // stopPropagation leaves the link's own navigation untouched.
+ for (const link of document.querySelectorAll('.group-link')) {
+ link.addEventListener('click', (event) => event.stopPropagation());
+ }
+</script>
+
+<style>
+ /*
+ * Unlayered, so these win over the Starlight sidebar rules they replace, which live
+ * in starlight.core. The selectors are scoped to this component and reach nothing
+ * else.
+ */
+ ul {
+ --sl-sidebar-item-padding-inline: 0.5rem;
+ list-style: none;
+ padding: 0;
+ }
+
+ li {
+ overflow-wrap: anywhere;
+ }
+
+ /* GitBook indents each level by 21px: 8 of margin, 12 of padding, 1 of rule. */
+ ul ul {
+ margin-inline-start: var(--sl-sidebar-item-padding-inline);
+ padding-inline-start: 0.75rem;
+ }
+
+ /*
+ * The hairline runs down the list, not each row, so it is unbroken between siblings —
+ * and only from the second level down. A section's own items sit flush against the
+ * section header on GitBook, with no rule beside them.
+ */
+ ul ul ul {
+ border-inline-start: 1px solid var(--sl-color-hairline-light);
+ }
+
+ /*
+ * Section header. Starlight renders these at 16px/600 in the heading colour,
+ * which reads as a second title; GitBook sets 12px/600 uppercase with 0.025em
+ * tracking. The transform matters beyond case: two of the six sections are
+ * title-case in SUMMARY.md, and GitBook uppercases them in CSS rather than in
+ * the source, so this keeps the labels untouched and still renders them alike.
+ */
+ .section-label {
+ font-size: 0.75rem;
+ font-weight: 600;
+ line-height: 1rem;
+ letter-spacing: 0.025em;
+ text-transform: uppercase;
+ color: var(--sl-color-white);
+ }
+
+ /* Rows sit on a 34px pitch: 32 tall with a 2px gap. */
+ li + li {
+ margin-top: 2px;
+ }
+
+ .top-level > li + li {
+ margin-top: 1.5rem;
+ }
+
+ summary {
+ display: flex;
+ align-items: center;
+ justify-content: space-between;
+ padding: 0.2em var(--sl-sidebar-item-padding-inline);
+ line-height: 1.4;
+ cursor: pointer;
+ user-select: none;
+ }
+ summary::marker,
+ summary::-webkit-details-marker {
+ display: none;
+ }
+
+ /*
+ * A linked group drops the summary's own padding so the link can carry it and
+ * fill the row, giving the whole label a hit area and hover state rather than a
+ * strip of it. The caret stays outside the link, so clicking it toggles the group
+ * instead of navigating.
+ */
+ summary.linked {
+ padding-block: 0;
+ padding-inline: 0;
+ }
+
+ .group-link {
+ flex: 1;
+ min-width: 0;
+ }
+
+ .caret {
+ transition: transform 0.2s ease-in-out;
+ flex-shrink: 0;
+ }
+ :global([dir='rtl']) .caret {
+ transform: rotateZ(180deg);
+ }
+ [open] > summary .caret {
+ transform: rotateZ(90deg);
+ }
+
+ /*
+ * Every nav row, leaf or group header, is the same: GitBook draws no distinction
+ * between them. 14px/400 in a muted grey against Starlight's --sl-color-gray-2,
+ * on a 32px row.
+ */
+ a,
+ .group-link {
+ display: block;
+ border-radius: 0.25rem;
+ text-decoration: none;
+ color: var(--sl-color-gray-3);
+ font-size: 0.875rem;
+ font-weight: 400;
+ line-height: 1.25rem;
+ padding: 6px var(--sl-sidebar-item-padding-inline);
+ }
+
+ a:hover,
+ a:focus,
+ .group-link:hover,
+ .group-link:focus-visible {
+ color: var(--sl-color-white);
+ }
+
+ /*
+ * GitBook marks the current page with weight and colour alone. Starlight fills
+ * the row with the accent, which against a fully saturated brand blue reads as a
+ * heavy solid block.
+ */
+ [aria-current='page'],
+ [aria-current='page']:hover,
+ [aria-current='page']:focus {
+ font-weight: 600;
+ color: var(--sl-color-text-accent);
+ background-color: transparent;
+ position: relative;
+ }
+
+ /*
+ * GitBook turns the rule beside the current row brand blue. It is drawn on the row
+ * rather than on the list so that a parent page being current does not colour the
+ * rule down its entire subtree.
+ */
+ ul ul [aria-current='page']::before {
+ content: '';
+ position: absolute;
+ inset-block: 0;
+ inset-inline-start: calc(-0.75rem - 1px);
+ width: 1px;
+ background-color: var(--sl-color-text-accent);
+ }
+
+ a > *:not(:last-child),
+ .group-label > *:not(:last-child) {
+ margin-inline-end: 0.25em;
+ }
+</style>
diff --git a/src/components/ThemeProvider.astro b/src/components/ThemeProvider.astro
new file mode 100644
index 0000000..09fbd01
--- /dev/null
+++ b/src/components/ThemeProvider.astro
@@ -0,0 +1,20 @@
+---
+/**
+ * Pins the colour scheme to light.
+ *
+ * Starlight's own provider reads localStorage and prefers-color-scheme and sets
+ * `data-theme` accordingly. Starlight treats dark as the :root default and light as
+ * `[data-theme='light']`, so the attribute has to be set to light rather than simply
+ * left off.
+ *
+ * `StarlightThemeProvider.updatePickers` is kept as a no-op: ThemeSelect renders
+ * nothing here, but the global is part of Starlight's inline contract and anything
+ * still calling it should not throw.
+ */
+---
+
+{/* Inlined rather than bundled so the theme is set before first paint. */}
+<script is:inline>
+ document.documentElement.dataset.theme = 'light';
+ window.StarlightThemeProvider = { updatePickers() {} };
+</script>
diff --git a/src/components/ThemeSelect.astro b/src/components/ThemeSelect.astro
new file mode 100644
index 0000000..f089618
--- /dev/null
+++ b/src/components/ThemeSelect.astro
@@ -0,0 +1,13 @@
+---
+/**
+ * Renders nothing: the site ships light-only.
+ *
+ * The GitBook site this replaces is light-only — its <html> carries a hard-coded
+ * `light` class, there is no switcher and no theme key in localStorage — so a theme
+ * control would be a feature the docs have never had, arriving on cutover day.
+ *
+ * Starlight renders this component in both Header and MobileMenuFooter, so blanking
+ * it here covers the mobile menu as well as the header. `ThemeProvider` pins the
+ * theme itself; the dark tokens stay in custom.css so this is reversible.
+ */
+---
diff --git a/src/content/docs/core-concepts/contexts-and-attributes/about-attributes/index.mdx b/src/content/docs/core-concepts/contexts-and-attributes/about-attributes/index.mdx
index 5310a4a..773e2be 100644
--- a/src/content/docs/core-concepts/contexts-and-attributes/about-attributes/index.mdx
+++ b/src/content/docs/core-concepts/contexts-and-attributes/about-attributes/index.mdx
@@ -54,19 +54,19 @@ If an attribute type is not defined it will default to string.
* Example: Assume you have a collection of names called `FavouriteNames` . The structure would be `["Asterix", "Obelix", "Getafix"]` and you can access them through `FavouriteNames[0]` which would return Asterix, etc.
* In a message you could access it as shown below
-  (1).png>)
+ 
*Using a collection attribute in messages*
and this would provide the output
-.png>)
+
*Outcome of collection attribute in chat.*
Typically you would set the values of a collection attribute through an Action API call but you could also set it explicitly through the chat test panel to test the above example
-.png>)
+
* **Boolean Collection**: Allows for multiple True/False statements to be included in the attribute. (Small size "True" and Cotton "True". Therefore, the boolean\[] attribute's value is "True").
* **Decimal Collection**: A collection of decimals.
diff --git a/src/content/docs/core-concepts/contexts-and-attributes/attribute-management/index.md b/src/content/docs/core-concepts/contexts-and-attributes/attribute-management/index.md
index 6d0ddb3..7bc27c0 100644
--- a/src/content/docs/core-concepts/contexts-and-attributes/attribute-management/index.md
+++ b/src/content/docs/core-concepts/contexts-and-attributes/attribute-management/index.md
@@ -5,7 +5,7 @@ description: Use OpenDialog Attribute Management to create new attributes throug
This section outlines how to personalise your conversation through the use of existing attributes, and how to create new attributes throughout the conversation engine.
-
+
*OpenDialog Attribute Management lets you create new attributes on a need-to-have basis throughout the conversation engine.*
@@ -42,7 +42,7 @@ The Attribute Management function can be found in the sidebar of the conversatio
### Intents
-.png>)
+
*The attribute input field can be accessed within the advanced intent settings section in conversation designer sidebar.*
@@ -57,7 +57,7 @@ To access the Attribute Management feature within the intents sidebar for a give
### Conditions
-.png>)
+
*The attribute management input field can be accessed under the custom conditions section of the conversation designer sidebar.*
@@ -71,7 +71,7 @@ To access the Attribute Management feature within the conditions sidebar for a g
### Message editor
-.png>)
+
*The attribute input field can be accessed within the message editor section of the conversation designer*
@@ -104,19 +104,19 @@ A <mark style="color:purple;">**dynamic attribute**</mark> is an attribute that
If the attribute you want to use doesn't exist within a scenario, you can add a new attribute to the list. Within the conversation designer sidebar, there are two ways to do this. The first is simply to click the 'Create new attribute' button that is located underneath the text input field. This will take you straight to the attribute creation section.
-
+
*Click the 'Create new attribute' button to create a new attribute for your scenario.*
The second way to create a new attribute is through the drop down itself. If you aren't sure whether the attribute you want has been created or not, you can go ahead and type it into the input field anyway. If the attribute isn't in existence, a "no results found" symbol will pop up. From here, you can click the button at the bottom of the drop-down field to bring up the create attribute section.
-
+
*Click the button at the bottom of the drop down field to create a new attribute.*
This functionality is also the same within the message editor. See the image below for an example:
-
+
*Click the button at the bottom of the drop down field to create a new attribute within the message editor.*
@@ -129,7 +129,7 @@ Once you have selected to create a new attribute, the attribute creation modal w
Once you are happy with all of the completed fields, you can click the 'Save attribute' button at the bottom of the modal, or simply press enter. Once this is done, your attribute will be saved and added to the list of existing attributes for your scenario. This attribute can now be accessed via the drop-down list and used throughout your conversations.
-
+
*Use the 'Add new attribute' modal to create a new dynamic attribute for your scenario.*
@@ -139,19 +139,19 @@ To add an existing attribute within the conditions panel, find the input field u
Once you have found your chosen attribute, simply click on the item within the list.
-
+
*Start typing your chosen attribute into the text field to bring up the attribute dropdown selection.*
Once you have selected your attribute, you can click the information icon button on the right-hand side of the input field to find out further information about the attribute that you have chosen. For example, the attribute type, value, and description.
-
+
*Click the information icon button on the right hand side of the input field to find out further information about an attribute.*
An attribute can also be selected within the message editor. To do this, navigate to the message you want to edit, click within the text block, or add a new text block if there isn't already one there. To add a new attribute, open the drop-down menu by opening a curly brace `{` . From here, you can start typing an attribute name, which will bring up the list of attributes to choose from. Once you have found your chosen attribute, either click on the item within the list or press enter.
-
+
*Open a curly brace to activate the attribute management input field within the message editor.*
diff --git a/src/content/docs/core-concepts/contexts-and-attributes/conditions-and-operators/index.mdx b/src/content/docs/core-concepts/contexts-and-attributes/conditions-and-operators/index.mdx
index bccac66..fbeba22 100644
--- a/src/content/docs/core-concepts/contexts-and-attributes/conditions-and-operators/index.mdx
+++ b/src/content/docs/core-concepts/contexts-and-attributes/conditions-and-operators/index.mdx
@@ -133,19 +133,19 @@ Let’s consider an example with two conditions for a Conversation Object: `user
* **And Operator**: If the operator is set to **And**, the chained conditions will be true only when _both_ conditions are met. For instance, the object will be considered valid only if both `user_name` and `user_email` are set.
-.png>)
+
*Conditions And operator*
* **Or Operator**: When the operator is set to **Or**, the chained condition will be true if _either_ of the conditions is met. In this case, the object will be valid if either `user_name` or `user_email` is set.
-.png>)
+
*Conditions Or operator*
The above also applies to Message Templates.<br />
-.png>)
+
*Message Template conditions OR operator*
diff --git a/src/content/docs/core-concepts/contexts-and-attributes/secret-context/index.mdx b/src/content/docs/core-concepts/contexts-and-attributes/secret-context/index.mdx
index 919c3bc..dee1007 100644
--- a/src/content/docs/core-concepts/contexts-and-attributes/secret-context/index.mdx
+++ b/src/content/docs/core-concepts/contexts-and-attributes/secret-context/index.mdx
@@ -24,7 +24,7 @@ The Secret Context is different from the [Global Context](/core-concepts/context
You can manage secrets through the OpenDialog admin interface. Navigate to the Secret Management page (accessed from the 3 dot menu by your username in the sidebar) to view, create, and manage your secrets.
-
+
*The Secret Management page shows all your stored secrets and certificates*
@@ -94,7 +94,7 @@ Certificates are for storing client certificates used in mTLS authentication. Op
</Steps>
-
+
*Certificate detail view showing extracted metadata*
diff --git a/src/content/docs/core-concepts/how-the-conversation-engine-thinks/index.md b/src/content/docs/core-concepts/how-the-conversation-engine-thinks/index.md
index ea67e55..3eed040 100644
--- a/src/content/docs/core-concepts/how-the-conversation-engine-thinks/index.md
+++ b/src/content/docs/core-concepts/how-the-conversation-engine-thinks/index.md
@@ -16,7 +16,7 @@ Components can be both open and starting.
Because of these rules, it is very important for a designer to consider the behavior for any component.
-
+
## Conversation engine at the start of an interaction
@@ -32,7 +32,7 @@ When there are multiple available user intents in your conversation design, the
First, the conversation engine will run the interpreter associated with each available user intent in the conversation design. The interpreter will take the user's input and will attempt to match an intent with it. If the _interpreted_ intent name matches the _expected_ intent name in the conversation design, then we will continue with the intent. If the interpretation does not match, or provides no interpreted intents, then we will discard the expected intent from consideration.
-
+
*There are two available user intents in this conversational position.*
@@ -44,7 +44,7 @@ If both interpreters were to return intents that match, then the conversation en
As [Semantic Intent Classifiers](/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier) allow you to define intents and sub-intents, it is more likely that interpreters using your classifier will match more than one intent. To ensure that you do not need to carefully order intents in the Designer, Semantic Intent Classifiers return their intents with a priority ranking. Sub-intents are ranked the highest priority, as they are more specific and granular. Whereas intents are ranked as a lower priority, as they are general and broad.
-
+
*There are two available user intents in this conversational position.*
@@ -54,19 +54,19 @@ Using the example from the screenshot above, let's presume that both intents are
1. If the matching user intent defines a transition, the engine will follow that transition.
-
+
2. If there is no transition, look for a matching app response intent within the turn.
-
+
3. If there is no transition and no response intent is present in the turn, the engine will look for a next intent in another turn within the same scene.
-
+
-
+
4. If an intent has the completing behavior: after this intent is executed we go back up to the scenario level.
5. If none of the rules in this section apply, then a no match is triggered, either local or global (scenario level).
diff --git a/src/content/docs/core-concepts/the-opendialog-model/designing-conversational-ai-agents/index.md b/src/content/docs/core-concepts/the-opendialog-model/designing-conversational-ai-agents/index.md
index d457c5f..8a43df7 100644
--- a/src/content/docs/core-concepts/the-opendialog-model/designing-conversational-ai-agents/index.md
+++ b/src/content/docs/core-concepts/the-opendialog-model/designing-conversational-ai-agents/index.md
@@ -12,13 +12,13 @@ A conversation design needs to be able to manipulate and reason about all of the
The OpenDialog approach directly supports you in designing across these elements and combining them in a number of different ways.
-
+
*High-level overview of the OpenDialog Framework*
The diagram below illustrates the key components at a high-level. When user input comes in we classify it (through Semantic Classifiers) in order to have an understanding of what the user is trying to say and then we contextualise it based on the state of the overall business process we are support, the specific type of conversation we are having and what we know abot the user. We can then reason about where the conversation should transition next before we go ahead and generate a response for the user. This reasoning cycle is illustrated below.
-
+
*The OpenDialog Reasoning Cycle*
@@ -30,7 +30,7 @@ The OpenDialog conversation framework enables much of the flexibility that the p
The different levels of the framework are:
-
+
*Levels of the OpenDialog framework*
@@ -40,7 +40,7 @@ When we start an OpenDialog application we start with a **Scenario.** This holds
A scenario is the highest level in the OpenDialog framework. It encompasses the set of functionalities that make up all the conversational application. For example your scenario might be a Pizza Order activity, an Insurance Claim activity or a Customer Support activity.
-
+
*Creating a Scenario in OpenDialog*
@@ -48,7 +48,7 @@ A scenario is the highest level in the OpenDialog framework. It encompasses the
Within a Scenario your AI agent and the user will have conversations. A conversation refers to communication for specific goals. Conversations can be viewed as steps in the customer journey, or conversations to be had. Examples: a welcome conversation, a payment and delivery conversation.
-
+
*Conversations within an OpenDialog scenario.*
@@ -56,7 +56,7 @@ Within a Scenario your AI agent and the user will have conversations. A conversa
Conversations then are further split into scenes. A scene deals with a specific stage, aspect or subgoal of a conversation. It is a middle layer in the model that allows for much flexibility in building out conversations. Example: a payment conversation can include a scene to enter payment data, a scene to confirm paument and a scene to finalize payment. A delivery conversation can include a scene to collect delivery details such as the address.
-
+
*Scenes in OpenDialog conversations*
@@ -64,7 +64,7 @@ Conversations then are further split into scenes. A scene deals with a specific
In a turn the user and application exchange specific information or intents. Example: the scene to collect a delivery address can have two turns: a turn to collect the address details and a turn to confirm the address details that were collected.
-
+
## Intents
@@ -72,11 +72,11 @@ A turn consists of intents. An intent holds the message and its meaning. An inte
This is where you can connect what we said at the start about desiging a space where the agent _and_ the user are represented. We have intents _both_ for the app (our AI agent) and the user.
-
+
## To summarize
-.png>)
+
*Overview of the components in the OpenDialog model*
diff --git a/src/content/docs/core-concepts/the-opendialog-model/index.mdx b/src/content/docs/core-concepts/the-opendialog-model/index.mdx
index e59c19b..c142c34 100644
--- a/src/content/docs/core-concepts/the-opendialog-model/index.mdx
+++ b/src/content/docs/core-concepts/the-opendialog-model/index.mdx
@@ -16,7 +16,7 @@ To achieve this three ingredients are necessary.
In the best of Venn diagram traditions - we illustrate below that _sweet spot_ OpenDialog is after, where human-led design and machine driven rules and prediction (or generation) come together to provide a positive experience for the user.
-
+
*Combining conversation design with explicit reasoning and GenAI*
diff --git a/src/content/docs/core-concepts/the-opendialog-workspace/index.md b/src/content/docs/core-concepts/the-opendialog-workspace/index.md
index 8592f7f..4f69296 100644
--- a/src/content/docs/core-concepts/the-opendialog-workspace/index.md
+++ b/src/content/docs/core-concepts/the-opendialog-workspace/index.md
@@ -8,7 +8,7 @@ The first thing you see when you login to OpenDialog is the workspace.
The workspace is the starting point for accessing the main OpenDialog functionalities: [scenarios](/broken/pages/QXiLofFtrSva3tSBJilT) for setting up your Conversational AI application , [language services](/core-concepts/the-opendialog-workspace/language-services) to configure language capabilities available to use in your different scenarios, and your [account management](/core-concepts/the-opendialog-workspace/opendialog-account-management).
-
+
*The Workspace Dashboard is your go-to starting point to create & manage your applications.*
@@ -18,7 +18,7 @@ Most OpenDialog features are presented in two to three sections : the main menu
When logging into your OpenDialog workspace, you are presented with the Workspace Dashboard. From here you can use the main menu to navigate to the different areas of the product, or switch to a different workspace you have access to.
-
+
*Switching to another workspace or adding a new workspace*
@@ -39,6 +39,6 @@ If you wish to create a new workspace, you can do so directly from the workspace
* Congratulations 🙌🏻 , you now have an additional workspace!
:::
-
+
*Use the workspace dropdown to create a new workspace*
diff --git a/src/content/docs/core-concepts/the-opendialog-workspace/language-services/index.mdx b/src/content/docs/core-concepts/the-opendialog-workspace/language-services/index.mdx
index 97bbc04..0ef4c34 100644
--- a/src/content/docs/core-concepts/the-opendialog-workspace/language-services/index.mdx
+++ b/src/content/docs/core-concepts/the-opendialog-workspace/language-services/index.mdx
@@ -2,7 +2,8 @@
title: Language Services
---
-import { CardGrid, LinkCard } from '@astrojs/starlight/components';
+import { CardGrid } from '@astrojs/starlight/components';
+import CoverCard from '~/components/CoverCard.astro';
## What is a Language Service?
@@ -36,7 +37,7 @@ _For example : "When are you open until", "When do you close" = OpeningHoursInte
You can access the language services section of the platform directly from the [Workspace Dashboard](/core-concepts/the-opendialog-workspace).
-
+
*Access the language services section from the Workspace Dashboard*
@@ -53,8 +54,8 @@ You can access the language services section of the platform directly from the [
Read more about our different language services and how to use them:
<CardGrid>
- <LinkCard title="Leveraging Generative AI" description="Learn how to use OpenDialog's language services to create custom ready-to-use language capabilities" href="/opendialog-platform/interpreters-and-natural-language-understanding" />
- <LinkCard title="Using language services" description="Add a language service to your scenario to interpret what end-users input into your conversational application." href="/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/using-a-language-service-interpreter" />
+ <CoverCard title="Leveraging Generative AI" description="Learn how to use OpenDialog's language services to create custom ready-to-use language capabilities" href="/opendialog-platform/interpreters-and-natural-language-understanding" cover="/src/assets/engineer-maintenancing-ai-systems-2023-11-27-05-12-07-utc.jpg" />
+ <CoverCard title="Using language services" description="Add a language service to your scenario to interpret what end-users input into your conversational application." href="/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/using-a-language-service-interpreter" cover="/src/assets/usinglanguageservice.png" />
</CardGrid>
[^1]:
diff --git a/src/content/docs/core-concepts/the-opendialog-workspace/opendialog-account-management/create-and-manage-users/index.md b/src/content/docs/core-concepts/the-opendialog-workspace/opendialog-account-management/create-and-manage-users/index.md
index 2bdf0e2..923953a 100644
--- a/src/content/docs/core-concepts/the-opendialog-workspace/opendialog-account-management/create-and-manage-users/index.md
+++ b/src/content/docs/core-concepts/the-opendialog-workspace/opendialog-account-management/create-and-manage-users/index.md
@@ -4,7 +4,7 @@ title: Managing Users
Welcome to user management in OpenDialog! This guide shows you how to add and manage team members in your workspace. Your workspace starts with one user account, and you can easily add more team members as needed.
-### :heavy\_plus\_sign: Adding a new user
+### ➕ Adding a new user
To enable your team members to access the workspace, you will have to add them as users on your OpenDialog account.
@@ -14,7 +14,7 @@ Users are added to the workspace, not to a specific scenario.
To do this, click on your name, the three dots next to it, and then click on User Management. Once there, click the Create button at the top right, complete the form, and click Create.
-
+
*The user creation screen*
@@ -30,7 +30,7 @@ Once you've set up the new user account, you need to notify the user directly si
To update user details, such as to change their [role](/core-concepts/the-opendialog-workspace/opendialog-account-management/create-and-manage-users#role-based-access-control), go to the User Management page within the application and click the pencil icon next to the user you want to edit. From this screen you can amend the user's name and their role.
-
+
*The user editing screen*
@@ -38,7 +38,7 @@ To update user details, such as to change their [role](/core-concepts/the-opendi
To remove a user from your instance, go to the User Management page within the application and click 'X' next to the user you want to remove. Then, click 'Yes' on the pop-up, and the user will be removed.
-.png>)
+
OpenDialog uses a role-based access control system to manage access within workspaces. This system ensures that users have access only to the tools and information they need, based on their assigned roles.
diff --git a/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/conversations/index.md b/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/conversations/index.md
index 9925bec..275be4e 100644
--- a/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/conversations/index.md
+++ b/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/conversations/index.md
@@ -8,13 +8,13 @@ Conversations represent the high-level goals or states of our scenario.
Settings include a conversation name, whether the conversation exhibits starting behavior, and selecting the default interpreter to use.
-
+
*Conversation settings*
Clicking "Add new condition" opens the New Condition area:
-
+
*Conversation settings expanded*
diff --git a/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/index.mdx b/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/index.mdx
index 410936d..ce3592f 100644
--- a/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/index.mdx
+++ b/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/index.mdx
@@ -2,7 +2,8 @@
title: Scenarios
---
-import { CardGrid, LinkCard } from '@astrojs/starlight/components';
+import { CardGrid } from '@astrojs/starlight/components';
+import CoverCard from '~/components/CoverCard.astro';
## What is a scenario?
@@ -14,7 +15,7 @@ Each workspace holds one or more scenarios. You can access the Scenario overview
You can also do so by accessing the Scenario overview through the dedicated button 'Manage scenarios'.
-
+
*Access the scenario overview through the left-hand menu or via the Manage Scenarios button.*
@@ -26,7 +27,7 @@ You can also do so by accessing the Scenario overview through the dedicated butt
Create a new scenario using the main area's 'Create Scenario' button.
-
+
*Create a new scenario via the 'Create new scenario' button or import an existing scenario via a .json file*
@@ -42,7 +43,7 @@ When you export a scenario, an email is sent to your registered email address in
Duplicating and exporting may take a few minutes; you will be emailed when the resulting file is ready.
-
+
*Example of Scenario functionality*
@@ -50,7 +51,7 @@ Duplicating and exporting may take a few minutes; you will be emailed when the r
To import a scenario, you will need access to a .json file that you will upload during import. For example, you may have received a .json file as an export from another workspace or as an email attachment.
-
+
*Import scenario option at the top of the main Scenario Overview area.*
@@ -66,13 +67,13 @@ Active scenarios are available to be used in chat interfaces, while draft scenar
You can edit the Scenario name, description, set a preferred interpreter (which will act as the default interpreter throughout the scenario) and also set conditions. Setting a condition on a scenario is relevant in a multi-agent architecture, where conditions on scenarios identify a scenario for consideration.
-
+
*Scenario settings in the conversation designer*
## How to design your scenario
<CardGrid>
- <LinkCard title="The OpenDialog model" description="Take a deepdive into the underpinning model for OpenDialog applications." href="/core-concepts/the-opendialog-model" />
- <LinkCard title="Designing your application" description="Create a new scenario from a template or from scratch using OpenDialog's model and best practices." href="/opendialog-platform/conversation-designer" />
+ <CoverCard title="The OpenDialog model" description="Take a deepdive into the underpinning model for OpenDialog applications." href="/core-concepts/the-opendialog-model" cover="/src/assets/od-basicmodel.png" />
+ <CoverCard title="Designing your application" description="Create a new scenario from a template or from scratch using OpenDialog's model and best practices." href="/opendialog-platform/conversation-designer" cover="/src/assets/applicationdesign.png" />
</CardGrid>
diff --git a/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/scenes/index.md b/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/scenes/index.md
index 848fe16..d1024f0 100644
--- a/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/scenes/index.md
+++ b/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/scenes/index.md
@@ -8,7 +8,7 @@ Settings include a scene name, whether the scene exhibits starting behavior, and
Clicking "Add new condition" opens the New Condition area.
-
+
*Scenes settings*
diff --git a/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/turns-and-intents/index.md b/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/turns-and-intents/index.md
index 4b153eb..1a488f6 100644
--- a/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/turns-and-intents/index.md
+++ b/src/content/docs/core-concepts/the-opendialog-workspace/scenarios/turns-and-intents/index.md
@@ -8,7 +8,7 @@ Settings include a turn name, whether the turn exhibits starting and/or open beh
Clicking "Add new condition" opens the New Condition area.
-
+
*Turns settings*
@@ -24,7 +24,7 @@ Turns contain a set of Response and Request intents. You can decide which partic
If the intent has a request intent followed by a response intent: when the request intent is evaluated, the engine will look if there is a response intent in the same turn, and execute that.
-
+
*Intents in turns*
@@ -37,7 +37,7 @@ It is acceptable to have multiple intents in the list of request or response int
## Intent settings
-
+
*Intent settings*
@@ -70,9 +70,9 @@ Actions can have output attributes, typically set up for webhook or LLM actions.
<div>
-
+
-
+
</div>
diff --git a/src/content/docs/developing-with-opendialog/interaction-api/index.md b/src/content/docs/developing-with-opendialog/interaction-api/index.md
index 413752b..7de7bdf 100644
--- a/src/content/docs/developing-with-opendialog/interaction-api/index.md
+++ b/src/content/docs/developing-with-opendialog/interaction-api/index.md
@@ -94,8 +94,8 @@ To access the API you will need a bearer token associated with a user account in
To access your bearer token visit the Identity & Security page - accessible by clicking on your username in the bottom left-hand corner.
-.png>)
+
-
+
*API Bearer Token Access*
diff --git a/src/content/docs/developing-with-opendialog/public-apis/index.md b/src/content/docs/developing-with-opendialog/public-apis/index.md
index dff702e..7decd3e 100644
--- a/src/content/docs/developing-with-opendialog/public-apis/index.md
+++ b/src/content/docs/developing-with-opendialog/public-apis/index.md
@@ -24,11 +24,11 @@ To access your bearer token visit the Identity & Security page - accessible by c
<div align="left">
-.png>)
+
</div>
-.png>)
+
**Important Security Notes:**
diff --git a/src/content/docs/developing-with-opendialog/webchat/webchat-authentication/index.md b/src/content/docs/developing-with-opendialog/webchat/webchat-authentication/index.md
index 5ff364f..c3face3 100644
--- a/src/content/docs/developing-with-opendialog/webchat/webchat-authentication/index.md
+++ b/src/content/docs/developing-with-opendialog/webchat/webchat-authentication/index.md
@@ -62,7 +62,7 @@ New users have not used the scenario before and have no chat history or data in
Returning users are users who have been seen before and have a conversational history, but they reached the end of their last conversation. Technically, this means they reached an intent that has the ‘completing’ behavior. This can be set on the intent edit page:
-
+
When a returning user visits the WebChat widget again, the `chat_open` event is sent as for new users with the `intent.core.welcome` callback ID
diff --git a/src/content/docs/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent/index.md b/src/content/docs/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent/index.md
index 3ce4c42..4e081e7 100644
--- a/src/content/docs/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent/index.md
+++ b/src/content/docs/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent/index.md
@@ -37,7 +37,7 @@ In OpenDialog we suggest representing the overall Goal as a Conversation while e
So an Appointment Booking Conversation for a doctor would look something like this:
-.png>)
+
*Appointment booking process*
@@ -49,7 +49,7 @@ Name your scenes in easy to understand, human friendly ways so that you can easi
Worth noting that in the Topic Conversation we have a specific Topic, called Book An Appointment which will detect if the user is asking to book an appointment which will direct them to the Appointment Booking Conversation.
-.png>)
+
*Moving from a Topic Conversation to the Appointment Booking Conversation*
@@ -67,7 +67,7 @@ There is no specifically wrong or right answer. These are design choices based o
Every scene in the Appointment Booking Conversation (or every step in our Process) follows the same pattern. Let's example that Pattern here:
-.png>)
+
*The sample step scene*
@@ -75,7 +75,7 @@ Every scene in the Appointment Booking Conversation (or every step in our Proces
There is one **starting turn** called _Step Introduction_. The purpose of this turn is to setup the scene for our user and explain the sub-goal. It will present the user with an appropriate welcome to the step and explain what we are trying to achieve.
-.png>)
+
*The Step Introduction Turn*
@@ -99,7 +99,7 @@ We will start with the _Continue or Complete Step_ turn.
Imagine the following dialog:
-.png>)
+
*First step of OpenDialog appointment booking*
@@ -109,7 +109,7 @@ The purpose of the Continue or Complete Step is to define what happens if the us
For example, consider the following interaction:
-.png>)
+
*Continue or Complete moves us to New Scene*
@@ -121,7 +121,7 @@ There are two reasoning steps that led us to this outcome - we fist acknowledge
The conversation engine interpreted `"sure buddy let's go ahead"` as a Confirm intent (using a Semantic Classifier). That Confirm intent had an APP response within the turn as shown below.
-.png>)
+
Since the user confirmed we then provide a response, which is `"Great, let's get started"`.
@@ -149,7 +149,7 @@ Virtual intents are useful for a number of reasons:
Virtual intents are supported in the Analyse view of a conversation and in the conversation player in Conversation Design so you can always see what the impact of this intent injection will be.
:::
-
+
*Virtual intents*
@@ -169,11 +169,11 @@ This is a local No Match (`intent.core.TurnNoMatch`) that will be selected if th
The Question intent will match to general questions and statements based on the definition of our semantic classifier. We can then connect it to an appropriate LLM action to answer the question. We can also decide to refocus the user on the goal through another virtual intent.
-.png>)
+
*Answering a question and then return to the doctor choice*
-.png>)
+
*Virtual intent on QuestionResponse that forces the conversation engine to behave as if the user asked about doctor choice*
@@ -183,7 +183,7 @@ The configuration above shoes that after we've provided a response to the questi
This intent is in our Routing turn and transitions us back to the top of the same scene we are in which will, in turn, re-present the doctor choice widget. This enables us to reuse the exact same design and makes it more scalable moving forward as we can easily make different choices or introduce other steps by intervening at just the right point.
-.png>)
+
*AskAboutDoctor routing intent*
diff --git a/src/content/docs/getting-started-1/quick-start-ai-agents/quick-start-ai-agent/index.mdx b/src/content/docs/getting-started-1/quick-start-ai-agents/quick-start-ai-agent/index.md
similarity index 74%
rename from src/content/docs/getting-started-1/quick-start-ai-agents/quick-start-ai-agent/index.mdx
rename to src/content/docs/getting-started-1/quick-start-ai-agents/quick-start-ai-agent/index.md
index d07d775..0c47ded 100644
--- a/src/content/docs/getting-started-1/quick-start-ai-agents/quick-start-ai-agent/index.mdx
+++ b/src/content/docs/getting-started-1/quick-start-ai-agents/quick-start-ai-agent/index.md
@@ -3,14 +3,11 @@ title: Quick Start AI Agent
description: The OpenDialog Quick Start AI Agent
---
-import Embed from '~/components/Embed.astro';
-
-
The Quick Start AI Agent is an optimised journey that really simplifies the process of creating an AI Agent. It is the fastest way to get up and running with OpenDialog.
You will get taken to the Quick Start AI Agent process when you first login to OpenDialog or you can fire it up the by visiting Create Scenario and then click on "Get Started Now"
-.png>)
+
*Create Scenario Link*
@@ -22,13 +19,18 @@ Behind the scenes OpenDialog configures a complete AI Agent scenario that you ca
-<Embed url="https://youtu.be/RhUc_mgkNl8" title="Building a Quickstart AI Agent in no time!" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.youtube-nocookie.com/embed/RhUc_mgkNl8" title="Building a Quickstart AI Agent in no time!" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+<figcaption>Building a Quickstart AI Agent in no time!</figcaption>
+</figure>
## Step by step guide
### Step 1 - Provide a name
-.png>)
+
*Step 1 - Quick Start AI Agent - Provide a name*
@@ -36,7 +38,7 @@ Behind the scenes OpenDialog configures a complete AI Agent scenario that you ca
### Step 2 - Add a knowledge source
-.png>)
+
*Step 2 - Quick Start AI Agent - Add a knoweldge source*
@@ -46,17 +48,17 @@ Behind the scenes OpenDialog configures a complete AI Agent scenario that you ca
If you upload your own knowledge source you will be asked to provide a quick description
-
+
*Step 3a - Quick Start AI Agent - Provide a quick description*
With that in place you can hit vectorise and your AI Agent will be created
-
+
*Quick Start AI Agent - Step 3b - Vectorization*
-
+
*Quick Start AI Agent - Step 3c - Completed*
@@ -66,7 +68,7 @@ With that in place you can hit vectorise and your AI Agent will be created
By clicking on preview you will be directed to your AI Agent and you can test it out
-
+
*Quick Start AI Agent - Ready to be Tested!*
diff --git a/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/chat-management-conversation/index.md b/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/chat-management-conversation/index.md
index 7e7355a..6bf1559 100644
--- a/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/chat-management-conversation/index.md
+++ b/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/chat-management-conversation/index.md
@@ -3,7 +3,7 @@ title: Chat Management Conversation
description: The Chat Management Conversation of the Start from Scratch Scenario
---
- (1).png>)
+
The Chat Management conversation is a _Starting_ conversation. It contains scenes, turn and intents that handle chat management functionality. The green dots on top of the Scenes indicate that all of these Scenes also have the _Starting_ behavior. Finally, the turns within the scenes are also _Starting_ turns.
diff --git a/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/global-no-match-conversation/index.md b/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/global-no-match-conversation/index.md
index c0f0b17..7a65520 100644
--- a/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/global-no-match-conversation/index.md
+++ b/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/global-no-match-conversation/index.md
@@ -9,13 +9,13 @@ A No Match is "issued" by the OpenDialog Engine when no interpreted has found a
Keep in mind that the Topics conversation has its own No Match scene.
-
+
When the No Match intent is matched 😉 we reply with a NoMatchResponse that uses an LLM Action - the No Match Response Generation action to generate an appropriate message.
Immediately afterwards we issue the `intent.core.restart` intent as a [virtual intent.](/opendialog-platform/conversation-designer/message-design/subsequent-messages-virtual-intents) This will enable us to force a restart of the conversation.
-.png>)
+
*The No Match turn with a virtual intent*
diff --git a/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/index.mdx b/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/index.mdx
index 4d70f70..ffe2244 100644
--- a/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/index.mdx
+++ b/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/index.mdx
@@ -14,13 +14,13 @@ You can create a start from scratch scenario by visiting the Create Scenario Pag
<div align="left">
- (1) (1).png>)
+
*Create Scenario Link*
</div>
-
+
*Start from Scratch Scenario*
@@ -28,7 +28,7 @@ You can create a start from scratch scenario by visiting the Create Scenario Pag
- (1).png>)
+
*The Start From Scratch Conversations and Flows*
diff --git a/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/semantic-classifier-query-classifier/index.md b/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/semantic-classifier-query-classifier/index.md
index 799dab4..ad92546 100644
--- a/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/semantic-classifier-query-classifier/index.md
+++ b/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/semantic-classifier-query-classifier/index.md
@@ -3,7 +3,7 @@ title: 'Semantic Classifier: Query Classifier'
description: The Semantic Classifier used by the "Start from Scratch" Scenario
---
-.png>)
+
*The "Start From Scratch" semantic classifier*
diff --git a/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/supporting-llm-actions/index.md b/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/supporting-llm-actions/index.md
index f8c8f66..99f0078 100644
--- a/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/supporting-llm-actions/index.md
+++ b/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/supporting-llm-actions/index.md
@@ -5,7 +5,7 @@ description: The LLM Actions used by the "Start from Scratch" scenario
To support fluid conversation exchange the "Start from Scratch" scenario uses a number of LLM Actions that can form a solid basis / template for your own LLM Actions.
-
+
*LLM Actions of the "Start from Scratch" scenario*
diff --git a/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/topic-conversation/index.md b/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/topic-conversation/index.md
index 0dcff01..3ecebf6 100644
--- a/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/topic-conversation/index.md
+++ b/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/topic-conversation/index.md
@@ -5,7 +5,7 @@ description: The Topic Conversation of the Start From Scratch Scenario
The Topic conversation is the more complex conversation in this Scenario as it lays out the structure to deal with a number of different generic topics in a fluid conversational way.
- (1).png>)
+
*The Topic Conversation*
@@ -13,15 +13,15 @@ Every Scene in the Topic Conversation follows the same pattern.
1. All Scenes have the _starting_ behavior. So once we are in the Topic Conversation we consider all Scenes.
2. Each Scene has one or more Turns that are also _starting._
-3.  Each Turn starts with a user Intent that corresponds to an Intent of the Query Classifier Semantic Classifier.
+3.  Each Turn starts with a user Intent that corresponds to an Intent of the Query Classifier Semantic Classifier.
4. Each Turn then also has a response intent.
-5.  Once we've responded to the user we redirect the context to the start of the Topic Conversation once more so the cycle can repeat.
+5.  Once we've responded to the user we redirect the context to the start of the Topic Conversation once more so the cycle can repeat.
6. Most APP intents have a dynamic response generated using an LLM action.
What this patterns allow us to do is move between the different scenes on every user query with flexibility since after every response we go back to the "top" of the Topics conversation.
In addition, the Topic Conversation has a No Match Scene that means we can capture anything that our Query Classifier has not interpreted contextuall and deal with it in the Topic Conversation.
-
+
*The Topic Conversation*
diff --git a/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/welcome-conversation/index.md b/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/welcome-conversation/index.md
index 7f79837..cbc3181 100644
--- a/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/welcome-conversation/index.md
+++ b/src/content/docs/getting-started-1/quick-start-ai-agents/the-start-from-scratch-ai-agent/welcome-conversation/index.md
@@ -3,30 +3,30 @@ title: Welcome Conversation
description: The Welcome Conversation of the Start from Scratch Scenario
---
-
+
*Welcome Conversation*
Users are directed to the Welcome Conversation from the Chat Management conversation, and then the Conversation Engine will select the Welcome Scene as it is the only _Starting_ scene (as indicated by the green dot).
-
+
*Welcome Scene*
The Welcome Scene has just one _Starting_ Turn - the Welcome Turn - with an APP message that will send an appropriate Welcome Message for the user.
-
+
*Welcome Turn*
The WelcomeResponse Message is a static message - you can customise it by editing it directly or turn it into a dynamic message by using an LLM action on the intent to generate a relevant welcome message.
- (1) (1).png>)
+
If you visit the Preview section of the bot (under Test) you will see this message appear in WebChat. The `intent.core.welcome` intent was the incoming user intent (triggered automatically by the fact that WebChat loaded on the page). That intent (containted in the Chat Management conversation) then transitions the context to the Welcome Conversation where the OpenDialog Engine identified one possible response - the `WelcomeResponse` - which the associated message.
- (1) (1).png>)
+
The WelcomeResponse intent then transitions us to the Topic Conversation where we are waiting for a message from the user. You can see the transition under "Transition to" in the WelcomeResponse intent.
-
+
diff --git a/src/content/docs/index.mdx b/src/content/docs/index.mdx
index 403ef7b..dac469f 100644
--- a/src/content/docs/index.mdx
+++ b/src/content/docs/index.mdx
@@ -4,7 +4,7 @@ title: Introduction
import { CardGrid, LinkCard } from '@astrojs/starlight/components';
-.png>)
+
*OpenDialog: AI Agent Management System*
@@ -41,55 +41,55 @@ _Visit_ [_https://opendialog.ai/opendialog-ai-accelerator-program/_](https://ope
## OpenDialog Features
-.png>)
+
*Manage LLM prompts and integrate with your application data*
-.png>)
+
*Build RAG services from your own document sources and integrate in your AI Agents*
-.png>)
+
*Use Semantic Classification to identify intents at just the right level for your application*
-.png>)
+
*Design conversations and track every decision with our detailed analytics*
-.png>)
+
*Track what users are saying and where in the conversation they are saying it and use it to improve your application*
-.png>)
+
*Create multiple types of messages, embed widgets and customise with our SDK*
-.png>)
+
*A wealth of widgets to customise your AI Agent and make life easier for your users*
-.png>)
+
*Customise brand and style for your users and customers*
-.png>)
+
*Accessible to AA standards*
-.png>)
+
*With a powerful SDK to customise further*
-.png>)
+
*Integrate with your own applications and flexibly pull data into your AI agent and prompts*
-.png>)
+
*Translation support to launch your AI Agent across multiple locales*
-.png>)
+
*With a unique preview and test environment to help you build with confidence*
diff --git a/src/content/docs/opendialog-platform/actions/actions-from-library/datetime-action/index.mdx b/src/content/docs/opendialog-platform/actions/actions-from-library/datetime-action/index.md
similarity index 86%
rename from src/content/docs/opendialog-platform/actions/actions-from-library/datetime-action/index.mdx
rename to src/content/docs/opendialog-platform/actions/actions-from-library/datetime-action/index.md
index 8844cc0..700df1f 100644
--- a/src/content/docs/opendialog-platform/actions/actions-from-library/datetime-action/index.mdx
+++ b/src/content/docs/opendialog-platform/actions/actions-from-library/datetime-action/index.md
@@ -2,8 +2,6 @@
title: Datetime Action
---
-import Embed from '~/components/Embed.astro';
-
The Datetime action allows you to create and update timestamp attributes.
:::note
@@ -12,7 +10,11 @@ Any new timestamp attributes that you create and/or reference with this action t
### Video
-<Embed url="https://www.loom.com/share/118848be202d465ab443e13a1ae46c15?sid=a0309590-8db2-4528-ae40-997941a2d189" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/118848be202d465ab443e13a1ae46c15" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
### Fields
@@ -22,7 +24,7 @@ The action can be configured by three fields:
* `base`: This is an optional field. If it is provided it should be an attribute reference to another timestamp attribute that you want to use, e.g. `{first_seen}`. If it is not provided it will default to the current time at the time of evaluation.
* `modifier`: This is an optional field. If it is provided it should be a representation of how you would like to update the base, or current, time, e.g. `+1 week`. See below for a [list of further examples](/opendialog-platform/actions/actions-from-library/datetime-action#modifier-examples). If it is not provided the base timestamp will not be amended.
-
+
### Usecases
diff --git a/src/content/docs/opendialog-platform/actions/actions-from-library/freshdesk-action/index.mdx b/src/content/docs/opendialog-platform/actions/actions-from-library/freshdesk-action/index.md
similarity index 81%
rename from src/content/docs/opendialog-platform/actions/actions-from-library/freshdesk-action/index.mdx
rename to src/content/docs/opendialog-platform/actions/actions-from-library/freshdesk-action/index.md
index 17a2287..c11e1f5 100644
--- a/src/content/docs/opendialog-platform/actions/actions-from-library/freshdesk-action/index.mdx
+++ b/src/content/docs/opendialog-platform/actions/actions-from-library/freshdesk-action/index.md
@@ -2,8 +2,6 @@
title: Freshdesk Action
---
-import Embed from '~/components/Embed.astro';
-
### The basics
The Freshdesk action lets you set up a connection between OpenDialog and your Freshdesk ticketing system, which you can then in turn use within your conversation design.
@@ -33,7 +31,7 @@ Some use cases can't be treated through an automated interaction. This is the c
Freshdesk actions allow you to integrate your Freshdesk ticketing system into your OpenDialog scenario; you can therefore find it under our product's Integrate section.
-
+
*Select the action library to add pre-defined actions like the Freshdesk action*
@@ -51,19 +49,24 @@ Use the 'Add action from library' button.
The Freshdesk Action has three main components: the action setup, the action testing, and project usage.
-
+
*Freshdesk action setup in the central pane, guidance and action testing in the right-hand pane.*
-The <mark style={{ color: 'purple' }}>**action setup**</mark> happens in the central pane of the actions screen. It is divided into three separate spaces: naming your action, adding your account details (see [What you'll need](/opendialog-platform/actions/actions-from-library/freshdesk-action#what-youll-need) for more details), setting the ticket information, and, finally, tags to categorize your requests in Freshdesk.
+The <mark style="color:purple;">**action setup**</mark> happens in the central pane of the actions screen. It is divided into three separate spaces: naming your action, adding your account details (see [What you'll need](/opendialog-platform/actions/actions-from-library/freshdesk-action#what-youll-need) for more details), setting the ticket information, and, finally, tags to categorize your requests in Freshdesk.
-The <mark style={{ color: 'purple' }}>**action testing**</mark> becomes available in the right-hand pane once all the settings above have been completed.
+The <mark style="color:purple;">**action testing**</mark> becomes available in the right-hand pane once all the settings above have been completed.
-You can start <mark style={{ color: 'purple' }}>**using the action in your project**</mark> by adding it to the intent of your choice. More information about this [here](/opendialog-platform/actions).
+You can start <mark style="color:purple;">**using the action in your project**</mark> by adding it to the intent of your choice. More information about this [here](/opendialog-platform/actions).
### How to use
-<Embed url="https://youtu.be/XCaMVMtFvIc" title="Learn how to create and test a Freshdesk action" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.youtube-nocookie.com/embed/XCaMVMtFvIc" title="Learn how to create and test a Freshdesk action" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+<figcaption>Learn how to create and test a Freshdesk action</figcaption>
+</figure>
#### Create the Freshdesk action
@@ -92,7 +95,7 @@ You can test your action using the test pane on the right-hand side of the actio
To test your action, add dummy test data to the JSON snippet then click on the ‘Run action test’ button.
-.png>)
+
*Test your action using test action pane*
@@ -104,7 +107,7 @@ These output attributes will be stored against the user context, and you can now
To start using the Freshdesk action in your scenario, you need to make sure that it is activated by sliding the toggle on the Action Card to active.
-
+
*Activate your action to use it in your scenario*
diff --git a/src/content/docs/opendialog-platform/actions/actions-from-library/send-to-email-action/index.md b/src/content/docs/opendialog-platform/actions/actions-from-library/send-to-email-action/index.md
index 3315bd6..bf99f68 100644
--- a/src/content/docs/opendialog-platform/actions/actions-from-library/send-to-email-action/index.md
+++ b/src/content/docs/opendialog-platform/actions/actions-from-library/send-to-email-action/index.md
@@ -12,7 +12,7 @@ All you need to set this up is an email address to send the email to. Note that
### Where to find
-
+
*Select the action library to add pre-defined actions like the send to email action*
@@ -32,7 +32,7 @@ Once you click on "Add from action library", give the action a name of your choi
Select "Send to Email".
-
+
*Send to email action*
@@ -40,7 +40,7 @@ Add an email address, subject line and body.
You can use attributes in your message. Do make sure these attributes have values, e.g. you can set attribute values in buttons, or attribute values may be passed on through integrations. For more on attributes and values, visit the [Contexts and attributes](/core-concepts/contexts-and-attributes) section.
-
+
*Send to email details*
@@ -48,7 +48,7 @@ Save the action.
Activate the action.
-
+
*Activate the action*
@@ -60,13 +60,13 @@ In the designer, go to the intent that you want to action to be triggered from.
Click on "Add .. actions, ..." at the bottom of the component pane.
-
+
*Add conditions, actions and attributes*
Select the action from the dropdown.
-
+
*Select the action from the dropdown list*
diff --git a/src/content/docs/opendialog-platform/actions/actions-from-library/set-attributes-action/index.md b/src/content/docs/opendialog-platform/actions/actions-from-library/set-attributes-action/index.md
index 2c88c10..230bf9c 100644
--- a/src/content/docs/opendialog-platform/actions/actions-from-library/set-attributes-action/index.md
+++ b/src/content/docs/opendialog-platform/actions/actions-from-library/set-attributes-action/index.md
@@ -11,7 +11,7 @@ There are a number of reasons you may want to explicitly set some attribute valu
The Set Attributes action is available through the Custom Actions Component ID dropdown.
- (3).png>)
+
It is configured by configuring it's JSON structure.
@@ -19,4 +19,4 @@ The attribute value map identifies the name of the attribute and the value it sh
The example below shows how we would set the value of two attributes starter\_bot\_global\_no\_match\_count and starter\_bot\_chat\_started to specific values within the User context.
- (1) (3) (1).png>)
+
diff --git a/src/content/docs/opendialog-platform/actions/conversation-hand-off/chatwoot/index.md b/src/content/docs/opendialog-platform/actions/conversation-hand-off/chatwoot/index.md
index 4412d82..b9e5ab8 100644
--- a/src/content/docs/opendialog-platform/actions/conversation-hand-off/chatwoot/index.md
+++ b/src/content/docs/opendialog-platform/actions/conversation-hand-off/chatwoot/index.md
@@ -7,7 +7,7 @@ description: This section outlines how you can set up a handoff to live agents u
Conversation Handoff allows you to set up an integration with an external messaging system, for example, Chatwoot. You can therefore find it under the Integrate section of a specific scenario. Once you select 'Create a new Handoff' you will then have the opportunity to create the Handoff of your choice. Select Chatwoot to start setting up your Chatwoot integration.
-
+
*Setting up a Chatwoot integration via OpenDialog*
@@ -28,7 +28,7 @@ Once you are set up with an account on Chatwoot for your business, you will need
To set up your Chatwoot handoff, go to the Integrate section, and select Conv. handover from the menu. Use the Create New Handoff button to set up a new Handoff.
-
+
*Use the Create new Handoff button to set up a new Handoff integration*
@@ -55,7 +55,7 @@ To do so, go to Chatwoot, the Inbox you have referenced in OpenDialog, and its s
For example: example-workspace.cloud.opendialog.ai/incoming-chatwoot.
-
+
*Update your Chatwoot inbox Webhook URL to be able to receive messages*
diff --git a/src/content/docs/opendialog-platform/actions/conversation-hand-off/index.md b/src/content/docs/opendialog-platform/actions/conversation-hand-off/index.md
index ac099aa..bc12f01 100644
--- a/src/content/docs/opendialog-platform/actions/conversation-hand-off/index.md
+++ b/src/content/docs/opendialog-platform/actions/conversation-hand-off/index.md
@@ -7,7 +7,7 @@ description: OpenDialog now allows you to set up a seamless handover to other sy
Conversation Handoff allows you to set up an integration with an external messaging system, for example, Chatwoot. You can therefore find it under the Integrate section of a specific scenario. Once you select 'Create a new Handoff' you will then have the opportunity to create the Handoff of your choice. Select Chatwoot to start setting up your Chatwoot integration.
-
+
*Setting up a Chatwoot integration via OpenDialog*
diff --git a/src/content/docs/opendialog-platform/actions/index.mdx b/src/content/docs/opendialog-platform/actions/index.mdx
index 854d0fa..56d7a74 100644
--- a/src/content/docs/opendialog-platform/actions/index.mdx
+++ b/src/content/docs/opendialog-platform/actions/index.mdx
@@ -18,13 +18,13 @@ In this section we describe webhook actions and prebuilt actions. For reasoning
Actions are listed and can be added in the Integrate menu.
-
+
Each action requires a unique name, and attributes. The number of attributes can vary, and it is not mandatory to have both input and output attributes. Input attributes are sent from OpenDialog to the external data source. Output attributes are sent from the external data source to OpenDialog.
Each action type may have additional fields that are unique to that action type. For example, the webhook action requires a URL. Please see the relevant sub-section for further guidance on the specific action type you are using.
-
+
*Edit or create action page*
@@ -34,13 +34,13 @@ After you've saved your new action, make sure to activate it by sliding its togg
Once an action is created and activated, it can be added to an intent. To add an action or check any actions that have already been added, click "Add Action" in the Advanced Settings in the Component Setup pane.
-
+
*Add Action in the Advanced Settings*
To add an action, select an action from the dropdown list and save attributes to a context. Mapping the input and output attributes informs the action of where to find the input attributes and where to store the output attributes. If a mapping isn't provided for an output attribute, OpenDialog will by default store it in the `user` context.
-
+
*Adding an action to an intent*
diff --git a/src/content/docs/opendialog-platform/actions/webhook-action/execution-logs-and-troubleshooting/index.md b/src/content/docs/opendialog-platform/actions/webhook-action/execution-logs-and-troubleshooting/index.md
index e1faa4c..db942c2 100644
--- a/src/content/docs/opendialog-platform/actions/webhook-action/execution-logs-and-troubleshooting/index.md
+++ b/src/content/docs/opendialog-platform/actions/webhook-action/execution-logs-and-troubleshooting/index.md
@@ -6,7 +6,7 @@ You can view the execution logs for your webhook action in several ways..
## Using 3-dots menu on the action card
-.png>)
+
* **Aggregate Log Data**: Returns a CSV file that provides aggregated statistics across all your action runs.:
* Successful Runs
@@ -32,6 +32,6 @@ You can view the execution logs for your webhook action in several ways..
## Using request visualizer
-
+
In the preview or request logs, navigate to the selected path section to view all executed actions. For webhook actions, a new link allows you to download the action log, which contains the same information as the detailed log data from action card's 3-dot menu, containing log only for this particular execution.
diff --git a/src/content/docs/opendialog-platform/actions/webhook-action/index.mdx b/src/content/docs/opendialog-platform/actions/webhook-action/index.mdx
index 0b7cb8f..0cc4ddc 100644
--- a/src/content/docs/opendialog-platform/actions/webhook-action/index.mdx
+++ b/src/content/docs/opendialog-platform/actions/webhook-action/index.mdx
@@ -14,9 +14,9 @@ You can create new webhook action by visiting your scenario -> Integreate -> Act
<div>
-.png>)
+
- (1).png>)
+
</div>
@@ -24,7 +24,7 @@ You can create new webhook action by visiting your scenario -> Integreate -> Act
### Overview
- (1).png>)
+
*New webhook page*
@@ -39,7 +39,7 @@ You can create new webhook action by visiting your scenario -> Integreate -> Act
### Basic configuration
-.png>)
+
*Example of basic configurations of webhook action*
@@ -58,7 +58,7 @@ You can create new webhook action by visiting your scenario -> Integreate -> Act
### Headers configuration
-.png>)
+
*Example of headers configuration of webhook action*
@@ -66,7 +66,7 @@ Configure key-value pairs for your headers. Value field also supports the OD att
### Request configuration
-.png>)
+
*Example of payload configuration for webhook action*
@@ -75,7 +75,7 @@ Put a JSON payload which should be sent with your request.
OD attribute syntax is supported, but you have to put them in double-quotes.
<CardGrid>
-:white\_check\_mark: Do
+✅ Do
```json
{
@@ -85,7 +85,7 @@ OD attribute syntax is supported, but you have to put them in double-quotes.
-:x: Don't
+❌ Don't
```
{
@@ -98,7 +98,7 @@ Attribute types are preserved when the action is executing, so your number, bool
### Response configuration
-.png>)
+
*Example of response configuration for webhook action*
@@ -145,7 +145,7 @@ You can store the whole response as a string by toggling "Store raw response" an
### Testing your webhook
-.png>)
+
*Use testing panel on the left to run a test for your webhook*
@@ -153,13 +153,13 @@ Once you fill in your action name, URL, and HTTP method, the testing panel will
**Inputs block**
-.png>)
+
Any input attributes in the URL, headers, and request body sections will become available to fill in. These temporary values will be used during your tests.
**Outputs & Attributes block**
-.png>)
+
You can see if your action worked as expected in the Outputs section. A green check will indicate if the action was executed successfully, and the response status code will be displayed next to it. In the Attributes section, you will see three default output attributes plus any output attributes you've defined in the "Response" tab:
@@ -171,9 +171,9 @@ You can see if your action worked as expected in the Outputs section. A green ch
<div>
-.png>)
+
-.png>)
+
</div>
@@ -185,7 +185,7 @@ Use the pop-out icon next to the "Response" section to view this in a full-page
Webhook V2 Actions support three authentication methods: **Header Authentication**, **Mutual TLS (mTLS)**, and **OAuth2 Client Credentials**. Authentication is configured per webhook action, within the action configuration itself.
-
+
*Select an authentication method for your webhook action*
@@ -202,7 +202,7 @@ Header Authentication lets you build dynamic authentication headers for your web
Both blocks support the full OD attribute syntax, including `_auth` context references, `_webhook` context references (for request body or URL), and standard user/global/secret attributes.
-
+
*Header Authentication configuration*
@@ -259,7 +259,7 @@ Variables in the `variables` block can reference other variables defined in the
mTLS authentication establishes a two-way TLS handshake between OpenDialog and your API. You provide a client certificate which is presented to the server during the TLS negotiation.
-
+
*mTLS Authentication configuration*
@@ -289,7 +289,7 @@ To learn how to upload certificates and create secrets, see the [Secret Context]
OAuth2 Client Credentials authentication is designed for server-to-server integrations where your webhook needs to authenticate with an OAuth2-protected API. It implements the [OAuth2 Client Credentials Grant](https://datatracker.ietf.org/doc/html/rfc6749#section-4.4), which exchanges a client ID and client secret for an access token.
-
+
*OAuth2 Client Credentials configuration*
@@ -331,10 +331,10 @@ Scope: api.read api.write
Once you've saved your webhook action, it will appear on the "Actions" page. For convenience, a small chip with the HTTP method will be displayed in the bottom-left corner of the action card. Legacy webhook actions will be displayed with the subtitle "Legacy Webhook Action" and can be used as usual.
-.png>)
+
Attach your webhook action as usual to an intent in the conversation designer.
-.png>)
+
When the conversation reaches this intent, all your defined actions will be executed.
diff --git a/src/content/docs/opendialog-platform/actions/webhook-action/using-jmespath-expressions/index.md b/src/content/docs/opendialog-platform/actions/webhook-action/using-jmespath-expressions/index.md
index 4db0713..df396d1 100644
--- a/src/content/docs/opendialog-platform/actions/webhook-action/using-jmespath-expressions/index.md
+++ b/src/content/docs/opendialog-platform/actions/webhook-action/using-jmespath-expressions/index.md
@@ -4,7 +4,7 @@ title: Using JMESPath expressions
Use **JMESPath expressions** to map and transform JSON response from webhook action into the desired data structure.
-.png>)
+
*Example of using JMESPath expression in your output attributes mapping*
diff --git a/src/content/docs/opendialog-platform/actions/webhook-action/webhook-action/index.md b/src/content/docs/opendialog-platform/actions/webhook-action/webhook-action/index.md
index 1d6bf18..3bbac79 100644
--- a/src/content/docs/opendialog-platform/actions/webhook-action/webhook-action/index.md
+++ b/src/content/docs/opendialog-platform/actions/webhook-action/webhook-action/index.md
@@ -14,7 +14,7 @@ For some more details around the data structures you can use please see the [Int
Once you have a service that provides the desired functionality, you'll want to create a new webhook by following the action creation steps and set the action's URL to be the URL of your service.
-.png>)
+
### Headers
@@ -36,7 +36,7 @@ First, let's create a test action in OpenDialog and set the webhook endpoint to
The url we are using is `https://af7df53c-9871-40de-a454-31d5cf2d6237.mock.pstmn.io /your-webhook-endpoint`
-.png>)
+
*A webhook action*
@@ -46,7 +46,7 @@ Now, we can set up the **input attributes.** This is the information we will be
In the **Headers** section you can setup and authentication token required and you can also send headers that include conversation attributes such as the user's ID.
:::
-.png>)
+
Ok, so we've setup a `first_name` and `last_name` as input attributes and indicated that we expect a `full_name` as an output attribute (i.e. the result of our action).
@@ -56,7 +56,7 @@ The webhook action is _permissive_ in that it will accept input attributes that
Now, we can test our action by click on the Test Action Using JSON button.
-.png>)
+
*Testing a webhook action*
@@ -64,13 +64,13 @@ We will get the preset response from the mock Postman server.
Now, we can activate our action to make it available in a scenario.
-.png>)
+
*Activating an action.*
Finally, we can add the action to a specific intent so that it is run whenever that intent is selected.
-.png>)
+
*Adding an action to an intent.*
@@ -80,19 +80,19 @@ Before testing it out let's setup the WelcomeResponse message to use the results
1. Click on Edit Messages.
-.png>)
+
2. Click on the WelcomeResponse edit button
-.png>)
+
3. We are going to add a text block to our message that greets the user.
-.png>)
+
4. Now if we visit the preview section we will see that we are extracting the information from the action and using it to greet the user.
-.png>)
+
Well done! You've created your first action using the Webhook action in OpenDialog.
@@ -104,10 +104,10 @@ Every action automatically generates a boolean attribute (true/false) based on t
We can see the value of this attribute in our user context.
-.png>)
+
We can check for the value of this attribute in our conditions before we use the output of the attribute.
For example, we could have two messages one used when `webhook_test_action_success` is true and one for false.
-.png>)
+
diff --git a/src/content/docs/opendialog-platform/additional-menu-links/index.md b/src/content/docs/opendialog-platform/additional-menu-links/index.md
index f372d51..f8eac20 100644
--- a/src/content/docs/opendialog-platform/additional-menu-links/index.md
+++ b/src/content/docs/opendialog-platform/additional-menu-links/index.md
@@ -7,7 +7,7 @@ description: You can optionally add some links for your customers to your Web Ch
While creating your Web Chat instance based on the Embed code, you can uncomment the `additionalMenuLinks` exemplary section and edit it to add custom links to the menu. Provide objects with url and title for each link, and add as many entries as you need.
-
+
### Web Chat
@@ -15,6 +15,6 @@ In your Web Chat instance, you can check the link(s) in the "3-dots" menu and se
<div data-full-width="false">
-
+
</div>
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/authentication/using-in-opendialog/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/authentication/using-in-opendialog/index.md
index cd0d8e8..1a86d6f 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/authentication/using-in-opendialog/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/authentication/using-in-opendialog/index.md
@@ -10,7 +10,7 @@ In OpenDialog, there are two primary places you are likely to put a supporting p
The figure below provides an example of how such a scenario-wide authentication could be handled. Within the Welcome Conversation we have two scenes - one which welcomes the user if they are already authenticated and one which leads them to an Accounting Linking conversation (or an Info conversation for help) if they need to authenticate.
-.png>)
+
If, however, authentication is required only for a specific conversation within the overall scenario, then the authentication could live as a scene within that conversation. This approach is the just-in-time approach to authentication.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-help/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-help/index.md
index b991024..e6a9e58 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-help/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-help/index.md
@@ -25,20 +25,20 @@ While this pattern can be powerful, it may not always be possible to reuse a gen
Focusing on a reusable pattern, consider the following scene:
-.png>)
+
This scene gathers profile information from the user. We anticipate that the user may ask for help so we create a help turn that contains utterances such as: "help", "I require assistance", "what am I supposed to do", etc. The response within the Help turn can be highly contextualized since we know that we are in the Gather Profile Info scene.
The Turn Help has two intents:
-.png>)
+
The configuration for the "request help" intent from the user looks like this.
-.png>)
+
The response intent from the bot can now provide help relevant to the context.
-.png>)
+
The NLU interpreter intent and entities to cover help must be set up as well to make this work.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-no-match-pattern/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-no-match-pattern/index.md
index dde063d..83855b0 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-no-match-pattern/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-no-match-pattern/index.md
@@ -29,7 +29,7 @@ An example:
The conversation engine is built to accommodate no match where we define it, e.g. at the turn, scene, conversation or global level. When a user intent can not be matched to any turn in a scene, the conversation engine looks for a turn with the intent.core.TurnNoMatch intent. If this intent is not defined in any turn within a scene, the engine will look for a scene with an intent.core.SceneNoMatch intent. If this intent is not defined, the engine looks for a conversation with an intent.core.ConversationNoMatch intent. And if this intent is not defined, the engine will look for a global intent.core.NoMatch intent as a last resort. This global intent is defined by default in the custom template provided in the platform when creating a new scenario and is shown in the screenshot below.
-
+
*Global no match turn with intents from custom template*
@@ -39,10 +39,10 @@ In practice, the most common places in a scenario where you would define no matc
The screenshot below shows an example of a no match turn in a scene.
-.png>)
+
Per the screenshot below, within a no match turn, the user intent captures the user utterance and the app intent provides information and a way to continue the conversation.
-
+
*Intents in no match turn*
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-restart-chat-end-1/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-restart-chat-end-1/index.md
index 7ea0d44..d21a981 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-restart-chat-end-1/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-restart-chat-end-1/index.md
@@ -5,11 +5,11 @@ description: This pattern allows the user to end the chat.
This functionality is not activated by default; it must be activated in the Interface Settings page:
-
+
*End chat toggle in interface settings*
-.png>)
+
*End chat link in user interface*
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-restart-chat-end/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-restart-chat-end/index.md
index fe6f21c..505a760 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-restart-chat-end/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/contextual-restart-chat-end/index.md
@@ -5,11 +5,11 @@ description: This pattern allows the user to restart the interaction.
This functionality is not activated by default; it must be activated in the Interface Settings page
-
+
*Toggle for Restart button in settings*
-
+
*Restart icon in user interface*
@@ -17,7 +17,7 @@ If the user clicks the **Restart** button at any point during the conversation,
If none of these are found, the global intent.core.restart is executed. This intent is provided by default in the Trigger conversation (see screenshot)
-
+
*intent.core.restart in the Trigger conversation*
@@ -31,13 +31,13 @@ Consider a scene in which we are trying to gather information about a user. Our
This is what a scene for this might look like:<br>
-.png>)
+
The turn named `Scene Restart` can have the NLU to capture the user utterance indicating they made a mistake, and transitioning them back to the top of this scene.
In this case, if the user restarts the flow at any point in this scene, we would want to route them back to the `Get Name Turn`(that is the first turn in this scene). To do so the scene restart intent transitions to the Get Name turn.
-.png>)
+
:::tip
Notice the intent is named `intent.core.SceneRestart` as we want to capture all restarts within this scene
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/the-contextual-faq-pattern/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/the-contextual-faq-pattern/index.md
index ad1e319..d9d26ac 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/the-contextual-faq-pattern/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/building-robust-assistants/the-contextual-faq-pattern/index.md
@@ -33,13 +33,13 @@ _Note: as an example, the screenshots in this section illustrate adding an FAQ t
We add an FAQ turn to the scene:
-
+
*Package Bot FAQ Welcome Scene*
The FAQ turn consists of a user intent to capture the user's question and an app intent that shares the FAQ answer with the user and contains the re-prompt.
-
+
Depending on the NLU service provider, the name of the intents may be predetermined. For instance, when using DialogFlow KB, the user intent name is "intent.dialoflow.faq".
@@ -47,7 +47,7 @@ The app intent must contain a specific reference. This reference is also depende
The screenshot below shows and example of a reprompt ("Do you have any other questions..."). The reprompt helps to move the conversation forward and can be designed to fit your needs. In this case, the system asks whether the user wants to ask another question. An alternative could be to ask the original system question again.
-
+
*Screenshot showing XML for DialogFlow KB*
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings/index.md
index 1b0d6e1..f16a0a9 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings/index.md
@@ -116,23 +116,23 @@ Lowe's is a home improvement store. The automated assistant opening contains the
Numbers refer to the numbered list above.
-
+
Lowes.com
Okta's OktaBot uses a more transactional style. The bot greets the user. The self-identification is more implicit in the header and above the prompt. The bot goes straight into authentication to then show the relevant options.
-.png>) .png>)
+ 
Erica is the assistant for Bank of America. Erica is integrated in the mobile app, and has been featured for a number of years, so the need for self-identification is less of a priority.
Erica greats the user, and since the assistant is integrated in the app, access to the first name is available for personalization.
-Next Erica actually shows "new insights": a list of things that may interest me as a user, before showing the options .png>)
+Next Erica actually shows "new insights": a list of things that may interest me as a user, before showing the options 
**More examples**
-.png>)
+
Variants of a generic example with a greeting and options:
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings/transactional-openings/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings/transactional-openings/index.md
index b6960b7..aeb4463 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings/transactional-openings/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/openings/transactional-openings/index.md
@@ -30,13 +30,13 @@ Lowe's is a home improvement store. The automated assistant opening contains the
Numbers refer to the numbered list above.
-.png>)
+
*lowes.com*
Okta's OktaBot uses a more transactional style. The bot greets the user. The self-identification is more implicit in the header and above the prompt. The bot goes straight into authentication to then show the relevant options.
-.png>) .png>)
+ 
@@ -46,7 +46,7 @@ Erica greats the user, and since the assistant is integrated in the app, access
Next Erica actually shows "new insights": a list of things that may interest me as a user, before showing the options.
- .webp>)
+ 
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/transfer/components/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/transfer/components/index.md
index b27cd2a..138a112 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/transfer/components/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/conversational-patterns/transfer/components/index.md
@@ -33,7 +33,7 @@ When initiating a transfer pattern, there are some common steps.
When a transfer is initiated, there may not be any agents available immediately. In this case, the user is put in a queue, and would benefit from clear communication on how long they are likely to have to wait and their position in the queue. This can help manage expectations. Transparency is key to user satisfaction, and “time-fillers” might help too. The Liz bot shows one example of how to handle waiting:
-
+
This example shows estimated waiting time, position in the queue, and even offers the user the option of filing a ticket as an alternative to continuing to wait.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/index.md
index 0e01a28..e118ebd 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/index.md
@@ -6,7 +6,7 @@ The Design functionality includes the Conversation designer and Messages editor.
When you click on a scenario in the scenario list in your workspace (as shown in the previous page), the scenario opens by default in the Conversation Design tab.
-
+
*Conversation Designer interface*
@@ -14,7 +14,7 @@ Conversation designers spend a lot of their time in the Conversation Designer pu
The Conversation Design interface includes 3 panes with a number of controls and access to platform functionality in the sidebar:
-
+
*Details of the Conversation Designer interface*
@@ -24,11 +24,11 @@ You can access the 'Search' functionality in the main scenario menu, which searc
<div>
-
+
*Search across Intents and Messages using the search functionality in the main scenario menu*
-
+
*Type a query in the search bar and get an immediate list of the conversational components you can click on to edit*
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/assistant-personality/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/assistant-personality/index.md
index 46475ad..4b79ca6 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/assistant-personality/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/assistant-personality/index.md
@@ -44,7 +44,7 @@ Per Nielsen Norman Group (see references): “... different tones of voice on a
Personality and tone can remain abstract concepts unless we translate that into actual language examples. A voice chart gathers the personality and tone information, and makes us think about details such as the vocabulary, grammar and verbosity that will reflect the personality and tone.
-
+
*Sample assistant tone profile*
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/conversation-structure/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/conversation-structure/index.md
index 8a64034..2d78325 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/conversation-structure/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/conversation-structure/index.md
@@ -10,13 +10,13 @@ This step is the "glue" between the work we've done so far to inform the design,
As an example, consider the following diagram:
-
+
*Extract of a diagram*
Mapping this to conversations and scenes could look like this:
-
+
*Extract with conversations and scenes*
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/index.md
index 6604739..d81f0fa 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/index.md
@@ -22,7 +22,7 @@ Following this process ensures that the conversational experience is engaging an
We will review each step of the process in detail in the next pages.
-
+
## Role of LLMs
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/nlu-modeling/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/nlu-modeling/index.md
index d0d8105..b1ac53f 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/nlu-modeling/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/nlu-modeling/index.md
@@ -16,8 +16,8 @@ For instance, if we want sample utterances in the domain of "getting more inform
The example below shows that the incremental yield is not always a guarantee; in this case adding the online aspect did not yield significantly more value. However, it is important to continue to experiment with prompts as the yield can vary greatly depending on the specific use case. The prompts in the examples below as only an illustration.
-
+
-
+
-
+
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/sample-dialogs/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/sample-dialogs/index.md
index 7898520..63182a9 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/sample-dialogs/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/sample-dialogs/index.md
@@ -10,7 +10,7 @@ Create one or several sample dialogs based on the use case to help you get start
Here's an example of a sample dialog:
-
+
*Example of a sample dialog*
diff --git a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/user-needs/outcome-user-profile/index.md b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/user-needs/outcome-user-profile/index.md
index bb576d4..df1acda 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/user-needs/outcome-user-profile/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/conversation-design/introduction/user-needs/outcome-user-profile/index.md
@@ -6,6 +6,6 @@ The outcome of any primary and secondary research needs to be analyzed and summa
Here is an example of a user profile.
-
+
Depending on the complexity of the user interaction with a product, it may be useful to summarize other insights, in addition to the user profile. A live handoff of this information from the UX research team to the designers is preferable.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/designing-accessible-chatbots/index.md b/src/content/docs/opendialog-platform/conversation-designer/designing-accessible-chatbots/index.md
index 044dc79..33c71a7 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/designing-accessible-chatbots/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/designing-accessible-chatbots/index.md
@@ -14,7 +14,7 @@ To make this easier, we have collated a list of _do's and don'ts_ to help you bu
### **Always use a sans-serif typeface in your chatbot.**
-
+
A sans-serif font such as Arial, Helvetica or Tahoma provides maximum readability to your customers. Fonts like Times New Roman, Garamond, or a custom/bespoke font will provide poor legibility (especially for those with visual impairments) and should be avoided.
@@ -22,25 +22,25 @@ A sans-serif font such as Arial, Helvetica or Tahoma provides maximum readabilit
### **All images require an alt tag, excluding** [**those that are decorative**](https://www.w3.org/WAI/tutorials/images/decorative/)**.**
-.png>)
+
When creating an alt tag, it's best practice to describe the information, not the picture. For example, the alt text for an image of a person typing on a computer could be "Woman optimizing website for SEO" or "Woman researching free blogging platforms," depending on the topic of the conversation. This means screen readers can provide context to customers who may not be able to perceive the image clearly.
### **There are also times when an alt tag is not required.**
-.png>)
+
In this example, the image provides no meaningful information and can be considered 'decorative'. Therefore, **you do not need to add an alt tag**. Open Dialog will automatically add a 'Null' state, meaning assistive technologies will ignore announcing the alt tag, ensuring you are compliant.
### **Avoid flashing images**
-.gif>)
+
If you choose to use gifs or moving images, avoid those that flash or appear to strobe in any way to ensure you maintain AA accessibility standards. If the image is pertinent to the conversation (i.e. isn't classed as decorative) ensure you also include an alt tag.
### **Avoid text in images where possible, and use alt tags when not**
-.png>)
+
Where possible text burned into images (i.e. when an image is saved with text as part of the pixel data) should be avoided. There may be times when it's not possible to avoid this. In such cases, use the alt tag to describe the information.
@@ -50,7 +50,7 @@ This is also true if you are using images with graphs or pictorial information,
### **Abide by AA colour contrast specifications**
-.png>)
+
Choosing the right colour contrast levels can be tricky, as there are layers to this level of compliance. The most important elements such as text, buttons and other information should be a minimum of 4.5:1 contrast level.
@@ -82,7 +82,7 @@ It's also good practice to review your chatbot in greyscale to ensure any action
### **Avoid generic buttons and link labels**
-
+
Button labels should describe what the customer can expect if they click them. Using a generic phrase like 'See more' or 'Discover now' is inaccessible, and doesn't give customers any context over what they can expect.
@@ -92,7 +92,7 @@ Lastly, you should also avoid adding bare URLs such as www.google.co.uk as the b
### Use example content within placeholder text
-.png>)
+
When used sparingly (placeholders are not essential for accessibility compliance) placeholder text can be beneficial for customers.
@@ -118,7 +118,7 @@ Use _emojis_ sparingly, and include them at the end of sentences to avoid breaki
## Message speed
- (1) (1) (1) (1).png>)
+
Showing too many messages too quickly can be difficult for some customers to keep track of and comprehend, specifically if English is not their first language. It's better to slow things down a little and give them some space to read.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/inclusive-design-and-conversation-design/index.md b/src/content/docs/opendialog-platform/conversation-designer/inclusive-design-and-conversation-design/index.md
index f8ea4fc..1510666 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/inclusive-design-and-conversation-design/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/inclusive-design-and-conversation-design/index.md
@@ -14,7 +14,7 @@ We often design with the needs of the many in mind and forget to include the nee
'Solve for one, and extend to many'.
-.png>)
+
## Empathising with your customers
@@ -44,7 +44,7 @@ Developing design solutions with this approach in mind means more people will be
You may feel the need to think about edge cases and scenarios that may affect 0.1% of your customers. While this is good practice, instead, it's best to think about it from a kinetics perspective and consider how your customers interact with society and the world around them.
-.png>)
+
#### **It's worth considering:**
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/constructing-messages/index.md b/src/content/docs/opendialog-platform/conversation-designer/message-design/constructing-messages/index.md
index f0906ae..114a9dd 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/constructing-messages/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/constructing-messages/index.md
@@ -13,7 +13,7 @@ To design your message, click on any message block(s) to add those to the design
Each block can be deleted, duplicated, or reordered using the relevant icons.
- (2).png>)
+
*Individual message screen to design your message*
@@ -48,7 +48,7 @@ As a general rule for setting up messages with multiple blocks, it is always bes
Within every message type, there is also a drag-and-drop feature for you to use.
-.png>)
+
To access the drag-and-drop feature, go to the top left corner of any message block and click on the icon with six dots.
@@ -83,11 +83,11 @@ Notice the difference between the following screens:
<div align="left">
-
+
*All text in a single message*
-
+
*Text divided up in smaller chunks for readability*
@@ -106,7 +106,7 @@ A rule of thumb in a typical OpenDialog assistant is to limit the text in a sing
* 9 lines with buttons, ideally in 3 or 4 chunks
* Consider that on average, each line holds about 30 - 35 characters, or 5 to 6 words of average length (based on an average word length in English of 4.7 characters per word).
-.png>)
+
*Example screen and content*
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/index.mdx
index 1dc6a58..620a1d4 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/index.mdx
@@ -3,6 +3,7 @@ title: Message Design
---
import { CardGrid, LinkCard } from '@astrojs/starlight/components';
+import CoverCard from '~/components/CoverCard.astro';
Keep your conversational application ahead of the curve and drive quicker user adoption and user retention using visual cues and suggestions in a hybrid user interface, combining conversational and well-known graphical user interface patterns. This reduces cognitive load, allowing users to focus on their goals, thanks to a personalized, adaptive interface.
@@ -15,9 +16,9 @@ OpenDialog's low-code [Message edito](/opendialog-platform/conversation-designer
OpenDialog's modular approach to messages allows you to take advantage of rich UI components, surface specific messages on your terms and personalize them to make them relevant to specific users or use cases. Check out the following sections to take your conversational application from simple question answering to a truly personalised hybrid experience :
<CardGrid>
- <LinkCard title="Tailor the user experience" description="Master the art of crafting powerful messages tailored to your specific needs, combining OpenDialog's diverse range of message types to their fullest potential." href="/opendialog-platform/conversation-designer/message-design/constructing-messages" />
- <LinkCard title="Surface relevant messages" description="Take advantage of OpenDialog's unique approach, using conditions to surface relevant messages at the right moment in the conversation." href="/opendialog-platform/conversation-designer/message-design/message-conditions" />
- <LinkCard title="Personalize the messages" description="OpenDialog's attribute system will allow you to taylor your messages using these variables to surface personalised information." href="/opendialog-platform/conversation-designer/message-design/using-attributes-in-messages" />
+ <CoverCard title="Tailor the user experience" description="Master the art of crafting powerful messages tailored to your specific needs, combining OpenDialog's diverse range of message types to their fullest potential." href="/opendialog-platform/conversation-designer/message-design/constructing-messages" cover="/src/assets/legoblocks.png" />
+ <CoverCard title="Surface relevant messages" description="Take advantage of OpenDialog's unique approach, using conditions to surface relevant messages at the right moment in the conversation." href="/opendialog-platform/conversation-designer/message-design/message-conditions" cover="/src/assets/conditions-1.png" />
+ <CoverCard title="Personalize the messages" description="OpenDialog's attribute system will allow you to taylor your messages using these variables to surface personalised information." href="/opendialog-platform/conversation-designer/message-design/using-attributes-in-messages" cover="/src/assets/personalisation.png" />
</CardGrid>
## A diverse and rich set of message types
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-conditions/index.md b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-conditions/index.md
index d935ea6..428c9ad 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-conditions/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-conditions/index.md
@@ -6,13 +6,13 @@ title: Message Conditions
Message conditions can be defined by clicking on Conditions in the Layout and adding context, attribute and other details. More information about context and attributes is a available in the next page on Attributes in Messages.
-.png>)
+
-
+
We define conditions so that the system can evaluate which message to use. In the image below, two messages are associated with the intent called intent.app.WelcomeUser. The message called intent.app.WelcomeNewUser gets used when the user is not an existing customer. If they are, the message intent.app.WelcomeExistingUser is used. Existing\_customer is an attribute of the user context. More information about using attributes in messages can be found in the next page, "Attributes in messages".
-
+
*Example of messages with conditions*
@@ -20,10 +20,10 @@ Continuing our example above, where we want to show different messages to users
For our example, then we would set the 'Attribute' to `seconds_since_last_seen` , 'Context' to `user`, 'Operation' to `Equals` and the 'Value' to '`0`' - meaning only show this message if the user has not been seen yet.
-.png>)
+
Where as for the returning user, we would change the 'Operation' to be `Greater than`. Meaning only show this message if the user has been seen before.
-.png>)
+
Conditions are really powerful for enabling personalised experiences for users. The key functionality that drives Conditions are Attributes and you find out more about them [here](/core-concepts/contexts-and-attributes/conditions-and-operators).
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-editor/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-editor/index.mdx
index 4798f7a..25d58ad 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-editor/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-editor/index.mdx
@@ -3,7 +3,8 @@ title: Message editor
description: The Message editor gives us access to the messages in the scenario and allows us to add, edit and delete messages.
---
-import { CardGrid, LinkCard } from '@astrojs/starlight/components';
+import { CardGrid } from '@astrojs/starlight/components';
+import CoverCard from '~/components/CoverCard.astro';
## Finding the message editor
@@ -14,13 +15,13 @@ There are two ways to access messages:
<div align="left">
-
+
*Design option - not expanded*
</div>
-
+
*Design option - expanded*
@@ -34,7 +35,7 @@ There are two ways to access messages:
**Option 2:** From within the Conversation designer, navigate to the Message editor by clicking on the message icon in a Scenario, Conversation, Scene, Turn or Intent. This will take you directly to the messages related to the conversational component you are on (scenario, conversation, scene, turn or intent)
-
+
*How to find the message editor*
@@ -59,19 +60,19 @@ Our search functionality allows you to edit a specific word, sentence, or messag
You can access the 'Search' functionality in the main scenario menu, which searches for content throughout Intents and Messages.
-
+
*Search across Intents and Messaes using the search functionality in the main scenario menu*
To search for a specific message, click on the 'Search' item in the main scenario menu, and the search modal will appear right in the middle of your workspace. Then, enter your query in the search bar, and the modal will display the results instantly.
-
+
*Enter your search query in the search bar that appears when selecting Search in the main scenario menu*
By clicking on the appropriate search result from the list, you'll be directed to the chosen component, giving you the opportunity to edit the selected message with ease.
-
+
*Message catalog*
@@ -92,7 +93,7 @@ Note that the displayed messages in the message catalog are the sample message y
In the intent list, click the Edit icon for an existing message or click "Add a new message". An existing message can also be copied or deleted:
-
+
*Multiple messages associated with a single intent*
@@ -116,7 +117,7 @@ The following options are available in the Edit Message screen:
* "Hide the avatar for this message" will ensure that Webchat doesn't display the avatar alongside the message.
* "Exclude markdown code from attribute filling" will ensure that any curly-braces `{}`included inside [markdown code blocks](http://commonmark.org/help/) (single or triple back ticks) will not be used in attribute filling. By default OpenDialog will presume any curly braces are being used as [attribute syntax](/opendialog-platform/conversation-designer/message-design/using-attributes-in-messages) and attempt to fill it's value, this behaviour excludes markdown code from being filled. This behaviour is useful if you need to use curly braces for things such as code snippets within your messages.
-.png>)
+
*Edit Message screen*
@@ -186,7 +187,7 @@ The following message types support expandable attributes:
OpenDialog's modular approach to messages allows you to take advantage of rich UI components, surface specific messages on your terms and personalize them to make them relevant to specific users or use cases. Check out the following sections to take your conversational application from simple question answering to a truly personalised hybrid experience :
<CardGrid>
- <LinkCard title="Tailor the user experience" description="Master the art of crafting powerful messages tailored to your specific needs, utilising OpenDialog's diverse range of message types to their fullest potential." href="/opendialog-platform/conversation-designer/message-design/constructing-messages" />
- <LinkCard title="Surface relevant messages" description="Take advantage of OpenDialog's unique approach, using conditions to surface relevant messages at the right moment in the conversation." href="/opendialog-platform/conversation-designer/message-design/message-conditions" />
- <LinkCard title="Personalize the messages" description="OpenDialog's attribute system will allow you to taylor your messages using these variables to surface personalised information." href="/opendialog-platform/conversation-designer/message-design/using-attributes-in-messages" />
+ <CoverCard title="Tailor the user experience" description="Master the art of crafting powerful messages tailored to your specific needs, utilising OpenDialog's diverse range of message types to their fullest potential." href="/opendialog-platform/conversation-designer/message-design/constructing-messages" cover="/src/assets/legoblocks.png" />
+ <CoverCard title="Surface relevant messages" description="Take advantage of OpenDialog's unique approach, using conditions to surface relevant messages at the right moment in the conversation." href="/opendialog-platform/conversation-designer/message-design/message-conditions" cover="/src/assets/conditions-1.png" />
+ <CoverCard title="Personalize the messages" description="OpenDialog's attribute system will allow you to taylor your messages using these variables to surface personalised information." href="/opendialog-platform/conversation-designer/message-design/using-attributes-in-messages" cover="/src/assets/personalisation.png" />
</CardGrid>
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/address-autocomplete-message/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/address-autocomplete-message/index.md
similarity index 94%
rename from src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/address-autocomplete-message/index.mdx
rename to src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/address-autocomplete-message/index.md
index 273bb60..cceae75 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/address-autocomplete-message/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/address-autocomplete-message/index.md
@@ -3,9 +3,6 @@ title: Address Autocomplete Message
description: This page describes where to use and find an address autocomplete message type
---
-import Embed from '~/components/Embed.astro';
-
-
## What is an address autocomplete message?
An address autocomplete message type in a chatbot is a feature that assists users in quickly entering their address information by providing real-time suggestions as they type. This type of message aims to enhance the user experience by reducing the amount of typing required and ensuring more accurate address entries.
@@ -26,7 +23,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
Fill in the template with the [properties](/opendialog-platform/conversation-designer/message-design/message-types/address-autocomplete-message#properties) of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
-
+
*How to create an address autocomplete message via a custom message*
@@ -70,7 +67,11 @@ Fill in the template with the [properties](/opendialog-platform/conversation-des
## How to use an address autocomplete message
-<Embed url="https://www.loom.com/share/e48ff649b6fa4c5884492a25739390f9" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/e48ff649b6fa4c5884492a25739390f9" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
:::tip
**Saving a message:** Always remember to hit 'Save Message' before closing or navigating away from the edit screen.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/attribute-message/index.md b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/attribute-message/index.md
index 573e93b..7ef2ed4 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/attribute-message/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/attribute-message/index.md
@@ -15,7 +15,7 @@ You want to use attribute message when you don't know exact message structure wh
Navigate to the [Message Editor](https://docs.opendialog.ai/~/changes/BlkAxgfqkBZsmUnZLd8K/opendialog-platform/conversation-designer/message-design/message-editor) and create a _Custom Message._ Copy the [XML snippet](/opendialog-platform/conversation-designer/message-design/message-types/attribute-message#what-is-a-list-message-3) at the bottom of this page into the black box, or select `attribute-message` from the dropdown.
- (3).png>)
+
*How to create an attribute message in custom message block*
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/audio-message/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/audio-message/index.md
similarity index 91%
rename from src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/audio-message/index.mdx
rename to src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/audio-message/index.md
index fd2a063..770e725 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/audio-message/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/audio-message/index.md
@@ -3,9 +3,6 @@ title: Audio Message
description: This page describes where to use and find an audio message type
---
-import Embed from '~/components/Embed.astro';
-
-
## What is an audio message?
An audio message involves sending a sound file to the user as part of the conversation. This type of message can be an effective way to convey information, emotions, or instructions in a manner that text or images might not achieve as effectively.
@@ -22,7 +19,7 @@ Audio messages have many applications:
<div align="left">
-
+
*Audio messages can be played and paused using the play and pause button to the left and downloaded using the button to the right of each audio message directly within in the chat window.*
@@ -36,7 +33,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
Fill in the template with the [properties ](/opendialog-platform/conversation-designer/message-design/message-types/audio-message#properties)of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
-
+
*How to create an audio message in the custom message block*
@@ -75,7 +72,11 @@ If you change your mind and select a different message type after generating the
## How to use an audio message
-<Embed url="https://www.loom.com/share/b68beddac70c4e4ba22273403712f552?sid=185748d0-927d-4b75-b530-61731a267f08" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/b68beddac70c4e4ba22273403712f552" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
:::tip
**Saving a message:** Always remember to hit 'Save Message' before closing or navigating away from the edit screen.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/autocomplete-message/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/autocomplete-message/index.md
similarity index 94%
rename from src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/autocomplete-message/index.mdx
rename to src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/autocomplete-message/index.md
index 293bae6..1091883 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/autocomplete-message/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/autocomplete-message/index.md
@@ -3,9 +3,6 @@ title: Autocomplete Message
description: This page describes where to use and find an autocomplete message type
---
-import Embed from '~/components/Embed.astro';
-
-
## What is an autocomplete message?
Autocomplete messages allow us to capture accurate and form valid data from users efficiently. These messages can perform automatic look-ups based on partial user inputs.
@@ -24,7 +21,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
Fill in the template with the [properties](/opendialog-platform/conversation-designer/message-design/message-types/autocomplete-message#properties) of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
- (1).png>)
+
*Where to find the custom messages button and XML for Autocomplete messages*
@@ -108,7 +105,11 @@ If you change your mind and select a different message type after generating the
## How to use an autocomplete message
-<Embed url="https://www.loom.com/share/86b21a17ceb34aa09c2159d04078e951?sid=ce0f5e97-9b94-41eb-a678-2fda64dabb8f" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/86b21a17ceb34aa09c2159d04078e951" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
:::tip
**Saving a message:** Always remember to hit 'Save Message' before closing or navigating away from the edit screen.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/button-message/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/button-message/index.md
similarity index 95%
rename from src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/button-message/index.mdx
rename to src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/button-message/index.md
index 8306fd6..4f9e88c 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/button-message/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/button-message/index.md
@@ -3,14 +3,11 @@ title: Button Message
description: This page describes where to use and find a button block message type
---
-import Embed from '~/components/Embed.astro';
-
-
## What is a button message?
You can add only one button message type to each message, however, within that you can add as many different buttons as you require. You can do this by clicking on the ＋ next to the button entry you require the button to appear afterwards. Right now you can not reorder the buttons, so they need to be added in the order you want them to appear.
-.png>)
+
## When to use a button message
@@ -22,7 +19,7 @@ Buttons are useful for many different reasons. They give you the opportunity to
Navigate to the [Message Editor](/opendialog-platform/conversation-designer/message-design/message-editor) and create a button block by clicking the _Add button block_ icon in the Layout section.
-.png>)
+
*How to create a button message in the no-code button message block*
@@ -42,7 +39,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
Fill in the template with the [properties](/opendialog-platform/conversation-designer/message-design/message-types/button-message#properties) of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
- (1).png>)
+
*How to create a button message in the custom message block*
@@ -211,17 +208,17 @@ Within the button block, you can add some plain text (_if you've not already use
* **Button text:** This is the text that is visible on the button
* **Button functionality:** This is the action that you would like the button to perform on click e.g. open an external URL or transition the user to another intent.
-.png>)
+
### **Button functionality**
Let's focus on transitioning to another intent _(Simulate user intent)_ as this action will likely be what you'll be wanting to perform most. There are two options here, either; locate an intent that you've already created from the drop-down or create a new intent.
-.png>)
+
To create a new one, you need to open the Conversation where the new intent needs to be located, click on 'Create new intent...' and then add the name and finally select the Scene then Turn it should live in (you can also create Scenes and Turns if required). Remember to click on ✔ to save before closing.
-.png>)
+
:::note
**Reminder:** If you've created a new intent etc. Remember to go back into the Designer after you've saved the message to fine tune the settings of your new Intent, Scene and Turn. You will need to add behaviours, conditions and/or transitions.
@@ -239,7 +236,7 @@ Button values are added in the `Advanced settings` dropdown for buttons with the
When a user clicks a button, by default the value will be saved to the user context for use later (_this can be altered by modifying an_ [_intent's advanced settings_](/core-concepts/the-opendialog-workspace/scenarios/turns-and-intents#intent-settings))
-.png>)
+
### **Button behaviours**
@@ -248,7 +245,11 @@ For the button message type, you can select a number of advanced behaviours depe
* **Override user input field - show buttons as main interaction mode:** This option will hide the text input within Webchat and show the buttons as the main interaction at the bottom.
* **Allow continued interaction throughout the conversation:** This option will allow users to continue to interact with the buttons even if they have moved on from that part of the conversation. This is really useful for FAQ style chatbots.
-<Embed url="https://www.loom.com/share/d5b595a7c9d2416e8f6abd214511ac26?sid=b04c2a11-4868-400c-b8c2-42349025dd41" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/d5b595a7c9d2416e8f6abd214511ac26" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
:::tip
**Saves Message:** Always remember to hit 'Save Message' before closing or navigating away from the edit screen
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/conversation-handover-message/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/conversation-handover-message/index.md
similarity index 92%
rename from src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/conversation-handover-message/index.mdx
rename to src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/conversation-handover-message/index.md
index 8799b91..2abefa0 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/conversation-handover-message/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/conversation-handover-message/index.md
@@ -3,9 +3,6 @@ title: Conversation Handover message
description: This page describes where to use and find a conversation handover message type
---
-import Embed from '~/components/Embed.astro';
-
-
## What is a conversation handover message?
In OpenDialog webchat, using a conversation handover message means that new messages sent by the user are not sent to the `incoming/webchat` endpoint, but are handled by an external system.
@@ -20,7 +17,7 @@ Conversation handover messages are intended to be used to inform OpenDialog that
### Via the no-code conversation handover message in Message Editor
-
+
*How to create a conversation handover message in the no code message editor*
@@ -40,7 +37,7 @@ From here you can fill out the text you want your message to initially read, lin
### Via the custom message in Message Editor
-
+
*How to create a conversation handover message in the XML snippet*
@@ -71,7 +68,11 @@ Fill in the template with the [properties ](/opendialog-platform/conversation-de
## How to use a conversation handover message
-<Embed url="https://www.loom.com/share/606e24e270bb42cea53a68c2203059c7?sid=2d4ccbdb-35d4-44fe-9a61-3b1bd876b1d1" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/606e24e270bb42cea53a68c2203059c7" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
:::tip
**Saving a message:** Always remember to hit 'Save Message' before closing or navigating away from the edit screen.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/date-picker-message/index.md b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/date-picker-message/index.md
index 1bd36cf..7f6b538 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/date-picker-message/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/date-picker-message/index.md
@@ -9,11 +9,11 @@ Date picker messages allow the user to choose a date from a graphical calendar i
<div align="center" data-full-width="true">
-
+
*Users are prompted with a clickable input box.*
-
+
*When clicked, a calendar appears*
@@ -23,19 +23,19 @@ As well as being able to just pick the date, the date picker message also has ot
<div>
-
+
*Pick a time*
-
+
*Pick a date and time*
-
+
*Pick a month and year*
-
+
*Pick a year*
@@ -63,7 +63,7 @@ Date picker messages are set up by following two steps:
### 1. Creating a date picker message on an application intent
-.png>)
+
*How to create a date picker message in the custom message block*
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/e-sign-message/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/e-sign-message/index.md
similarity index 88%
rename from src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/e-sign-message/index.mdx
rename to src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/e-sign-message/index.md
index 1577756..282cf15 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/e-sign-message/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/e-sign-message/index.md
@@ -3,24 +3,21 @@ title: E-Sign Message
description: This page describes where to use and find a e-sign message type
---
-import Embed from '~/components/Embed.astro';
-
-
## What is an e-sign message?
An e-sign message can be used within your OpenDialog chatbot to collect and gather signatures from your users. Users can input their signature and then send it over, to be stored by you and used in the future.
<div>
-
+
*Here is where the user can input their signature*
-
+
*An example of a user signature that's been inputted*
-
+
*An example of a signature that has been submitted*
@@ -38,7 +35,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
Fill in the template with the [properties](/opendialog-platform/conversation-designer/message-design/message-types/e-sign-message#properties) of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
-
+
*How to create an e-sign message in the custom message block*
@@ -76,7 +73,11 @@ Fill in the template with the [properties](/opendialog-platform/conversation-des
## How to use e-sign messages
-<Embed url="https://www.loom.com/share/45f79a718bf840aa8cddf5b0e62fcb9e?sid=1ad5760c-3545-45fe-a0e8-51cb9b089dab" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/45f79a718bf840aa8cddf5b0e62fcb9e" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
:::tip
**Saving a message:** Always remember to hit 'Save Message' before closing or navigating away from the edit screen.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/file-upload-message/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/file-upload-message/index.md
similarity index 93%
rename from src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/file-upload-message/index.mdx
rename to src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/file-upload-message/index.md
index 2c884c5..2c104a2 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/file-upload-message/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/file-upload-message/index.md
@@ -3,9 +3,6 @@ title: File Upload Message
description: This page describes where to use and find a file upload block message type
---
-import Embed from '~/components/Embed.astro';
-
-
## What is a file upload message?
File upload messages allow us to submit more than one file at a time in multiple different formats.
@@ -16,7 +13,7 @@ File upload messages are best used when submitting documentation such as proof o
Parameters such as file type, file size and the number of files that can be uploaded are all defined by the designer.
-
+
*An example of a file upload message in use*
@@ -28,7 +25,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
Fill in the template with the [properties](/opendialog-platform/conversation-designer/message-design/message-types/file-upload-message#properties) of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
-
+
*How to create a file upload message in the custom message block*
@@ -90,7 +87,11 @@ If you change your mind and select a different message type after generating the
## How to use a file upload message
-<Embed url="https://www.loom.com/share/b244bd98b24e46d6bda9de97e5d8c3ab?sid=98ef4b9c-dd03-488c-8327-c66c6477d16c" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/b244bd98b24e46d6bda9de97e5d8c3ab" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
:::tip
**Saving a message:** Always remember to hit 'Save Message' before closing or navigating away from the edit screen.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/form-message/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/form-message/index.md
similarity index 94%
rename from src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/form-message/index.mdx
rename to src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/form-message/index.md
index 1be6aac..b7a37e4 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/form-message/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/form-message/index.md
@@ -3,9 +3,6 @@ title: Form Message
description: This page describes where to use and find a form block message type
---
-import Embed from '~/components/Embed.astro';
-
-
## What is a form message?
The form message lets you create more complicated message inputs that are great for capturing structured information about the user use as addresses or full names.
@@ -29,7 +26,7 @@ There are many different situations in which a form message would be used within
Navigate to the [Message Editor](/opendialog-platform/conversation-designer/message-design/message-editor) and create a form block by clicking the _Add form block_ icon in the Layout section.
-.png>)
+
*How to create a form message in the no-code form message block*
@@ -39,17 +36,17 @@ When creating a form message in the Message Editor, there are two ways to provid
By clicking on _-Select-_, you can choose how you want to populate your dropdown.
-.png>)
+
*Deciding how to populate your form message dropdown*
If you decide to do this manually, you can simply type the name of the option, and hit the '+' button to add the option. Your options will appear underneath the input box, and also in the preview tab on the right hand side.
-.png>)
+
*Adding static options to your FormMessage dropdown*
-.png>)
+
*Adding dynamic data to FormMessage dropdown*
@@ -61,7 +58,7 @@ We support a range of attribute types from the following list:
* `IntegerColelctionAttribute` e.g. \[1, 2, 3]
* `FloatCollectionAttribute` e.g. \[1.1, 1.2, 1.3]
* `ArrayDataAttribute` (aka 'List') e.g. \["Any set of values", "that you like", \["even nested ones"]]
-* `JSONInferredCompositeAttribute` e.g. \{ "1": "Unemployed", "2": "Employed"\}
+* `JSONInferredCompositeAttribute` e.g. { "1": "Unemployed", "2": "Employed"}
The only unsupported type is:
@@ -69,7 +66,7 @@ The only unsupported type is:
**Key/Value Mapping**: For large option sets, use `JSONInferredCompositeAttribute` to show user-friendly labels while storing corresponding IDs or codes. Users see the "value" (e.g., "Software Engineer") but your system stores the "key" (e.g., "SE001").
-.png>)
+
Once you've specified your data or data source, you will see a toggle to enable sorting of your dropdown options. When enabled, they will be alphabetically sorted from A-Z (A at the top, Z at the bottom) to make it simpler to scroll through the different options, or jump to a specific start letter.
@@ -77,7 +74,7 @@ Once you've specified your data or data source, you will see a toggle to enable
Once your form message is built, testing it in preview will show the form and let you type to search. You can search a form select regardless of the number of options within it.
-.png>)
+
*Searching a dropdown in a form message*
@@ -85,7 +82,7 @@ If you choose to sort your options alphabetically, users will be provided with a
**Priority Options**: Symbols, numbers, and special characters sort to the top—prefix important options with "\*" or other characters to keep them visible at the start of the list.
-.png>)
+
*Sorting your options alphabetically, including priority options*
@@ -95,7 +92,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
Fill in the template with the [properties ](/opendialog-platform/conversation-designer/message-design/message-types/form-message#properties)of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
-.png>)
+
*How to create a form message in the custom message block*
@@ -161,7 +158,7 @@ Additionally, we have an `<alphabetical></alphabetical>` tag to control whether
The `email` element type acts just like a `text` element, but on submission, is validated to ensure it is formatted like an email address
-.png>)
+
This form message example was created with the following XML:
@@ -205,7 +202,12 @@ This form message example was created with the following XML:
## How to use a form message?
-<Embed url="https://www.loom.com/share/d83919130d5743b5a9bc7b3763bdf62c?sid=be885a0c-4e12-476a-99d4-0c48cd036407" title="A video example of how to use a form message" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/d83919130d5743b5a9bc7b3763bdf62c" title="A video example of how to use a form message" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+<figcaption>A video example of how to use a form message</figcaption>
+</figure>
:::tip
**Saves Message:** Always remember to hit 'Save Message' before closing or navigating away from the edit screen
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/full-page-message/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/full-page-message/index.md
similarity index 93%
rename from src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/full-page-message/index.mdx
rename to src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/full-page-message/index.md
index d9352e5..950d1df 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/full-page-message/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/full-page-message/index.md
@@ -3,9 +3,6 @@ title: Full Page Message
description: This page describes where to use and find a full page message type
---
-import Embed from '~/components/Embed.astro';
-
-
## What is a full page message?
When full page messages are received, they will take over the entire chatbot screen (depending on what is supported by each platform)
@@ -30,7 +27,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
Fill in the template with the [properties ](/opendialog-platform/conversation-designer/message-design/message-types/full-page-message#properties)of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
-
+
*How to create a full page rich message in the custom message editor*
@@ -51,7 +48,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
Fill in the template with the [properties ](/opendialog-platform/conversation-designer/message-design/message-types/full-page-message#properties)of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
-
+
*How to create a full page form message in the custom message editor*
@@ -139,7 +136,12 @@ The cancel button can be added to a form message with the following mark up:
## How to use a full page message
-<Embed url="https://www.loom.com/share/77515c9f87f64b4a90864ba7c03f3e1a?sid=86a2e4c1-6b7b-4141-9f51-f3013796e8c6" title="A video demonstration of how to use a full page message" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/77515c9f87f64b4a90864ba7c03f3e1a" title="A video demonstration of how to use a full page message" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+<figcaption>A video demonstration of how to use a full page message</figcaption>
+</figure>
## How to construct a full page message
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/image-message/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/image-message/index.md
similarity index 92%
rename from src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/image-message/index.mdx
rename to src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/image-message/index.md
index f76ce79..e298de9 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/image-message/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/image-message/index.md
@@ -3,14 +3,11 @@ title: Image Message
description: This page describes where to use and find an image message type
---
-import Embed from '~/components/Embed.astro';
-
-
## What is an image message?
With image messages we can display an image in the chat window with an optional embedded clickable link. An image message involves sending an image to the user as part of the interaction. An image message consists of a visual element—such as a photograph, illustration, graphic, or screenshot—delivered within a chatbot conversation. Images can convey information quickly and effectively, often more so than text alone.
-
+
*Example of an image block message*
@@ -28,7 +25,7 @@ Optionally, you can add a link in the _URL_ field. This will allow users to be r
Navigate to the [Message Editor](/opendialog-platform/conversation-designer/message-design/message-editor) and create an image block by clicking the _Add image block_ icon in the Layout section.
-.png>)
+
*How to create an image message in the no-code image message block*
@@ -48,7 +45,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
Fill in the template with the [properties ](/opendialog-platform/conversation-designer/message-design/message-types/image-message#properties)of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
-.png>)
+
*How to create an image message in the custom message block*
@@ -99,7 +96,11 @@ If you change your mind and select a different message type after generating the
## How to use an image message
-<Embed url="https://www.loom.com/share/674637e1927d4d9b902e12d51ca302cc?sid=b44c6386-9bd7-4c85-b054-1b7d1a89fcd8" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/674637e1927d4d9b902e12d51ca302cc" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
:::tip
**Saving a message:** Always remember to hit 'Save Message' before closing or navigating away from the edit screen.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/list-message/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/list-message/index.md
similarity index 91%
rename from src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/list-message/index.mdx
rename to src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/list-message/index.md
index 70d78a9..83dc09d 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/list-message/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/list-message/index.md
@@ -3,9 +3,6 @@ title: List Message
description: List messages allow for multiple messages to be combined into a single message for the user that is displayed as a carousel that users can scroll between. These are good for displaying multiple search
---
-import Embed from '~/components/Embed.astro';
-
-
## What is a list message?
List messages allow for multiple messages to be combined into a single message for the user that is displayed as a carousel that users can scroll between. These are good for displaying multiple search.
@@ -16,7 +13,7 @@ A list message is a message that essentially looks like a carousel. Within this
A carousel list message in your OpenDialog chatbot can be quite useful for various purposes. For example, if you're running an e-commerce chatbot, a carousel can display multiple products at once, allowing users to browse through a selection and choose what interests them. They add visual interest to the conversation, making interactions more engaging and intuitive for users.
-
+
*Example of a list message*
@@ -28,7 +25,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
Fill in the template with the [properties ](/opendialog-platform/conversation-designer/message-design/message-types/list-message#properties)of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
-
+
*How to create a list message via the custom message editor*
@@ -63,7 +60,11 @@ If you change your mind and select a different message type after generating the
## How to use a list message
-<Embed url="https://www.loom.com/share/0d749f8e4b224eb49d052b4d46f197f0?sid=5555dcef-eaa6-4ab6-a05d-9dc6aba6f3f5" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/0d749f8e4b224eb49d052b4d46f197f0" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
:::caution
**Saving a message:** Always remember to hit 'Save Message' before closing or navigating away from the edit screen.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/location-message/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/location-message/index.md
similarity index 90%
rename from src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/location-message/index.mdx
rename to src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/location-message/index.md
index a4147e8..a9016e4 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/location-message/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/location-message/index.md
@@ -3,24 +3,21 @@ title: Location Message
description: This page describes where to use and find a location message type
---
-import Embed from '~/components/Embed.astro';
-
-
## What is a location message?
A location message is a message type that allows you to ask the user for their location. The user will then be able to open up a map and submit their location, or drag the map to whatever location they want to submit
<div align="center" data-full-width="false">
-
+
*A user can click the button at the bottom to open a map*
-
+
*Example of the map view where a user can select their location*
-
+
*An example of a message when a user has submitted their location*
@@ -38,7 +35,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
Fill in the template with the [properties](/opendialog-platform/conversation-designer/message-design/message-types/location-message#properties) of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
-
+
*How to create a location message in the custom message block*
@@ -74,7 +71,11 @@ If you do not register this new attribute first, this will cause the message to
## How to use location messages
-<Embed url="https://www.loom.com/share/3fed628c713c4bae97111edb4e11bb29?sid=a9d2f7ad-0f18-42db-9a1d-1e97c4be594c" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/3fed628c713c4bae97111edb4e11bb29" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
:::tip
**Saving a message:** Always remember to hit 'Save Message' before closing or navigating away from the edit screen.
@@ -84,7 +85,7 @@ If you do not register this new attribute first, this will cause the message to
Location information is stored in an attribute of type Location. If you haven't configured a new attributes then you could use a built-in attribute called Location (which is also of type Location). Alternative you can create a new attribute and set the type to Location.
-.png>)
+
*Creating an attribute of type attribute*
@@ -114,7 +115,7 @@ Ok - we have your new address as {user.new_address['formatted_address']}.
Is this correct?
```
- (1).png>)
+
Please pay attention to how _formatted\_address_ is enclosed in single quotes and square brackets. You can access any of the components of the address in the same way.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/meta-messages/progress-bar-message/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/meta-messages/progress-bar-message/index.md
similarity index 87%
rename from src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/meta-messages/progress-bar-message/index.mdx
rename to src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/meta-messages/progress-bar-message/index.md
index 2c34695..4ad1f70 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/meta-messages/progress-bar-message/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/meta-messages/progress-bar-message/index.md
@@ -3,9 +3,6 @@ title: Progress Bar Message
description: This page describes where to use and find a progress bar message type
---
-import Embed from '~/components/Embed.astro';
-
-
## What is a progress bar message
Progress bar messages can give the user a sense of how far they have advanced through the interaction.
@@ -16,7 +13,7 @@ For some interactions it is important to give the user information about the con
This can be especially useful for conversations that involve answering a longer string of questions when we are collecting data from the user or for tasks that are made up of multiple steps e.g. giving identifying information, then filling out a form and finally uploading documents.
-.png>)
+
## How to create a progress bar message
@@ -26,7 +23,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
Fill in the template with the [properties](/opendialog-platform/conversation-designer/message-design/message-types/meta-messages/progress-bar-message#properties) of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
-
+
*How to create a progress bar message in the custom message block*
@@ -45,12 +42,11 @@ Fill in the template with the [properties](/opendialog-platform/conversation-des
So, for example, the snippet below would show that the Claim Process is 10% complete.
-<pre>
-<meta-message>
+<pre><code><meta-message>
<data name="progressPercent">10%</data>
<data name="progressText">Claim Process Completion</data>
-<strong></meta-message></strong>
-</pre>
+<strong></meta-message>
+</strong></code></pre>
#### Properties
@@ -64,7 +60,11 @@ If you change your mind and select a different message type after generating the
## How to use a progress bar message
-<Embed url="https://www.loom.com/share/6b9e1179b4504ea282e8663c5574cde6?sid=cabd2202-3893-477b-87ab-5354c4f47238" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/6b9e1179b4504ea282e8663c5574cde6" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
:::tip
**Saving a message:** Always remember to hit 'Save Message' before closing or navigating away from the edit screen.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/rich-message/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/rich-message/index.md
similarity index 95%
rename from src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/rich-message/index.mdx
rename to src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/rich-message/index.md
index 8ddd2ed..43eb290 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/rich-message/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/rich-message/index.md
@@ -3,9 +3,6 @@ title: Rich Message
description: This page describes where to use and find a rich message type
---
-import Embed from '~/components/Embed.astro';
-
-
## What is a rich message?
A rich message is a card type message that can include lots of different multimedia elements such as titles, text, images, links and more.
@@ -24,7 +21,7 @@ Rich messages allow for more control around message content and how it is displa
* Image
* Buttons
-
+
*Example of a rich message*
@@ -36,7 +33,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
Fill in the template with the [properties ](/opendialog-platform/conversation-designer/message-design/message-types/rich-message#properties)of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
-
+
*How to create a rich message via the custom message editor*
@@ -106,7 +103,11 @@ If you change your mind and select a different message type after generating the
## How to use a rich message
-<Embed url="https://www.loom.com/share/b982f37b775b4f26bd571ce56d6b93f2?sid=c7d68bdc-fbed-4935-ba03-7e7267367347" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/b982f37b775b4f26bd571ce56d6b93f2" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
:::tip
**Saving a message:** Always remember to hit 'Save Message' before closing or navigating away from the edit screen.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/text-message/index.mdx b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/text-message/index.md
similarity index 93%
rename from src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/text-message/index.mdx
rename to src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/text-message/index.md
index da531c1..b4f01fd 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/text-message/index.mdx
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/text-message/index.md
@@ -3,9 +3,6 @@ title: Text Message
description: This page describes where to use and find a text message type
---
-import Embed from '~/components/Embed.astro';
-
-
## What is a text message?
A text message is a plain message with only text and is the primary message block we use to communicate with the user. It conveys information plainly conversationally and can also be used as a preamble to user choices using buttons, forms, and other message types.
@@ -22,7 +19,7 @@ _For example, separating out informative messages from the actionable question i
For more information on best practices for constructing messages, you can check out the [Constructing Messages ](/opendialog-platform/conversation-designer/message-design/constructing-messages)section of this documentation.
:::
-
+
*Example of a text message in action*
@@ -40,7 +37,7 @@ Text messages can display scripted information defined directly via the message
Navigate to the [Message Editor](/opendialog-platform/conversation-designer/message-design/message-editor) and create a text block by clicking the _Add text block_ icon in the Layout section. You can add as many text blocks to your message as required.
-.png>)
+
*Where to find the text block button*
@@ -64,7 +61,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
Fill in the template with the [properties ](/opendialog-platform/conversation-designer/message-design/message-types/text-message#properties)of your particular message and when you are happy with it make sure to save your message and test it in the Test Preview chat window.
- (1).png>)
+
*Where to find the custom messages button and XML for text messages*
@@ -122,7 +119,12 @@ If you change your mind and select a different message type after generating the
## How to use a text message
-<Embed url="https://www.loom.com/share/af079d5a9e654cfba90bedbcc935df9e?sid=197ce241-73b2-4a9a-8bee-db8f1125c039" title="A video demonstration on how to use" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/af079d5a9e654cfba90bedbcc935df9e" title="A video demonstration on how to use" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+<figcaption>A video demonstration on how to use</figcaption>
+</figure>
:::tip
**Saving a message:** Always remember to hit 'Save Message' before closing or navigating away from the edit screen.
@@ -132,9 +134,9 @@ If you change your mind and select a different message type after generating the
You can use a text message to display the responses from a large language model in your text message.
-To do so, you can reference the attribute that contains the LLM response in the text message block as follows : \{attribute\_name\}
+To do so, you can reference the attribute that contains the LLM response in the text message block as follows : {attribute\_name}
-_For example, \{llm\_response\}_
+_For example, {llm\_response}_
This requires you to configure the attribute the LLM response will get stored to. For more information on attributes, check out our [Attribute Management](/core-concepts/contexts-and-attributes/attributes) section.
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/twilio-content-template-message/index.md b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/twilio-content-template-message/index.md
index a6e0f42..7b75547 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/twilio-content-template-message/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/message-types/twilio-content-template-message/index.md
@@ -11,11 +11,11 @@ This message holds a reference to the Twilio Content Template that is used to re
<div>
-
+
*An example of Call to Action template*
-
+
*An example of Quick Reply template*
@@ -37,7 +37,7 @@ You should use a Twilio Content Template Message when you want to create a multi
Navigate to the [Message Editor](/opendialog-platform/conversation-designer/message-design/message-editor) and create a Custom Message. Copy the [XML snippet](/opendialog-platform/conversation-designer/message-design/message-types/twilio-content-template-message#xml-snippet) at the bottom of this page into the black box, or select `twilio-content-template-message` from the drop down, and your chat message will appear in the Preview panel.
-.png>)
+
*How to create Twilio Content Template Message in the custom message block*
@@ -69,7 +69,7 @@ Navigate to the [Message Editor](/opendialog-platform/conversation-designer/mess
| ----------- | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `sid` | string | The unique identifier of the Twilio Content Template to use for rendering. Required if `name` is not present. |
| `name` | string | The name of the Twilio Content Template to use for rendering. Required if `sid` is not present. |
-| `variables` | object | <p>A collection of variables to pass to the template for rendering.<br>In this example, <code>body</code> is a parameter of the message body.<br><code>button_1_text</code> is the text of the first button.<br><code>button_1_value</code> is the value of the button when clicked. Similar to Open Dialog's <a href="button-message.md">Button Message</a>, it can be a callback to an intent.<br>This field is optional, but variables number must match the number of parameters that you have defined in the Twilio content template.</p> |
+| `variables` | object | <p>A collection of variables to pass to the template for rendering.<br>In this example, <code>body</code> is a parameter of the message body.<br><code>button_1_text</code> is the text of the first button.<br><code>button_1_value</code> is the value of the button when clicked. Similar to Open Dialog's <a href="/opendialog-platform/conversation-designer/message-design/message-types/button-message">Button Message</a>, it can be a callback to an intent.<br>This field is optional, but variables number must match the number of parameters that you have defined in the Twilio content template.</p> |
### Supported Twilio Content Templates Types
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/messages-best-practices/index.md b/src/content/docs/opendialog-platform/conversation-designer/message-design/messages-best-practices/index.md
index 1e6cce8..c56aa58 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/messages-best-practices/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/messages-best-practices/index.md
@@ -10,11 +10,11 @@ It helps legibility if the information is provided in multiple messages (all wit
Notice the difference between the following screens:
-
+
*All text in a single message*
- .png>)
+ 
## Words per app turn
@@ -27,7 +27,7 @@ A rule of thumb in a typical OpenDialog assistant is to limit the text in a sing
* 9 lines with buttons, ideally in 3 or 4 chunks
* Consider that on average, each line holds about 30 - 35 characters, or 5 to 6 words of average length (based on an average word length in English of 4.7 characters per word).
-.png>)
+
*Example screen and content*
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/subsequent-messages-virtual-intents/index.md b/src/content/docs/opendialog-platform/conversation-designer/message-design/subsequent-messages-virtual-intents/index.md
index 171066c..8896372 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/subsequent-messages-virtual-intents/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/subsequent-messages-virtual-intents/index.md
@@ -4,7 +4,7 @@ title: Subsequent Messages - Virtual Intents
It is possible to share a number of messages in a single app intent, and [it is recommended to chunk content into bite-size pieces for legibility](/opendialog-platform/conversation-designer/message-design/messages-best-practices).
-
+
*3 pieces of information in a single app intent*
@@ -12,7 +12,7 @@ However, in some cases the information shared with the user does not all logical
-
+
*Information the assistant shares with the user - no user interaction*
@@ -20,13 +20,13 @@ The above would seem to violate the app - user - app -... order that must be adh
The app intent indicates in the component pane that they want to use a virtual intent.
-
+
*App intent that uses a virtual intent*
The user intent looks and feels just like any other user intent, and transitions to the next app intent.
-
+
*User intent*
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/using-attributes-in-messages/index.md b/src/content/docs/opendialog-platform/conversation-designer/message-design/using-attributes-in-messages/index.md
index 040712c..6877875 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/using-attributes-in-messages/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/using-attributes-in-messages/index.md
@@ -4,7 +4,7 @@ title: Using Attributes in Messages
Attributes can be used in any message to customize the content. For example, the user's name can be added in the welcome message to personalize the experience.
-
+
*Edit Message screen*
@@ -22,7 +22,7 @@ Note - If the attribute has no value or does not exist in the context given, the
### Message editor
-.png>)
+
*The attribute input field can be accessed within the message editor section of the conversation designer*
diff --git a/src/content/docs/opendialog-platform/conversation-designer/message-design/using-markdown-in-messages/index.md b/src/content/docs/opendialog-platform/conversation-designer/message-design/using-markdown-in-messages/index.md
index 146a3cb..fbdae59 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/message-design/using-markdown-in-messages/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/message-design/using-markdown-in-messages/index.md
@@ -4,7 +4,7 @@ title: Using Markdown in messages
In order to add richness and enhance our end users' experience when using the WebChat interface, it is possible to use Markdown within message types that have a significant text component. The currently supported message types are: Text, Button, Form and Rich. OpenDialog supports all the [basic features](https://www.markdownguide.org/basic-syntax/#overview) of the Markdown syntax, as well as [tables](https://www.markdownguide.org/extended-syntax/#tables) and [fenced code blocks](https://www.markdownguide.org/extended-syntax/#fenced-code-blocks).
-.png>)
+
*You can add your Markdown formatted content directly in the message editor*
diff --git a/src/content/docs/opendialog-platform/conversation-designer/webchat-interface-design/webchat-controls/index.md b/src/content/docs/opendialog-platform/conversation-designer/webchat-interface-design/webchat-controls/index.md
index d497d16..feabadd 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/webchat-interface-design/webchat-controls/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/webchat-interface-design/webchat-controls/index.md
@@ -15,7 +15,7 @@ Within the top header of every chat bot, there is a variety of different control
-.png>)
+
*Where to find the minimise button - right top hand corner*
@@ -25,7 +25,7 @@ To do this, locate the minimise icon in the top right corner, and click it once
### Main Menu<br>
-
+
*Where to find the main menu button - right top hand corner*
@@ -40,7 +40,7 @@ To locate the main menu controls, find the 3 dots icon in the left hand corner.
-
+
*Example of the expanded main menu from within the header controls*
@@ -48,7 +48,7 @@ To locate the main menu controls, find the 3 dots icon in the left hand corner.
-
+
*Where to find the speech to text button - bottom left hand corner*
@@ -60,7 +60,7 @@ To access this feature, find the microphone button in the bottom left corner. Cl
-
+
*Where to locate the CTA button*
diff --git a/src/content/docs/opendialog-platform/conversation-designer/webchat-interface-design/webchat-interface-settings/index.md b/src/content/docs/opendialog-platform/conversation-designer/webchat-interface-design/webchat-interface-settings/index.md
index bf87586..13a8c93 100644
--- a/src/content/docs/opendialog-platform/conversation-designer/webchat-interface-design/webchat-interface-settings/index.md
+++ b/src/content/docs/opendialog-platform/conversation-designer/webchat-interface-design/webchat-interface-settings/index.md
@@ -9,7 +9,7 @@ The settings are currently GLOBAL and will affect all scenarios you have created
Any changes made to the fields are not saved until you click on the 'Save Settings' button at the top of the screen
-.png>)
+
*Save your settings changes using the save button*
@@ -19,7 +19,7 @@ The settings are broadly split into 4 settings that affect different elements wi
### General
-
+
Here you can configure some overall settings for the widget:
@@ -33,7 +33,7 @@ Here you can configure some overall settings for the widget:
\- _Timing_ configures the length of time (in milliseconds) that the typing indicator should be shown for each message.\
\- You can control whether you want to show the typing indicator between each message block in the individual message toggling option _Hide Typing Indicator between messages_.\
\- _Show the typing indicator on message send_ controls whether to show the typing indicator at all.\
-\- _Typing Indicator_ can be either "Animation", which will show three dancing dots ( (4).png>)), or "Animation with feedback text", which will show spinning dots with feedback text ( (3).png>))
+\- _Typing Indicator_ can be either "Animation", which will show three dancing dots (), or "Animation with feedback text", which will show spinning dots with feedback text ()
You can configure the text and color of dots for "Animation with feedback text" in the embed code after you publish your scenario. Add the general key to your window.openDialogSettings object with the property typingIndicatorSettings. For this, you would need to specify:
@@ -64,7 +64,7 @@ You can configure the text and color of dots for "Animation with feedback text"
### CSS
-.png>)
+
Here you can upload custom CSS files to completely customise the chat widget. There are 2 files you can add:
@@ -74,7 +74,7 @@ Here you can upload custom CSS files to completely customise the chat widget. Th
### Layout Settings
-.png>)
+
Here you can adjust the colours used in the bot from the chat window itself to the messages and buttons.
@@ -84,19 +84,19 @@ Here you can adjust the colours used in the bot from the chat window itself to t
### Conversational History Settings
-.png>)
+
Here, you can control whether the interface shows a user their previous chat history on load, and if so, how many messages to show. You can test how this behaves by using the preview section and **refreshing** the page on your browser rather than clicking the 'Refresh Scenario' button as this will generate a new user.
## Security Settings
-.png>)
+
*Security Settings tab*
### Anonymous Authentication
-.png>)
+
*Anonymous Authentication*
@@ -110,7 +110,7 @@ When this feature is enabled, users must not be assigned pre-set user ID's (such
### Cross site request forgery (CSRF)
-.png>)
+
*Cross Site Request Forgery Settings*
@@ -120,7 +120,7 @@ This means that SDK implementations will need to ensure that the a custom subdom
### Cross origin resource sharing (CORS)
-.png>)
+
*Cross Origin Resource Sharing Settings*
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/amazon-lex-interpreter/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/amazon-lex-interpreter/index.md
index c1a6a15..5703367 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/amazon-lex-interpreter/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/amazon-lex-interpreter/index.md
@@ -12,7 +12,7 @@ To use Amazon Lex, you'll need an [Amazon Web Services](https://aws.amazon.com/)
First you'll need to create the Lex interpreter in OpenDialog. On the "Interpreters Setup" page, select "Add new interpreter". Here you'll need to choose a unique name for the interpreter and select the Lex type.
-
+
You'll see that you need to enter some settings in order to configure the interpreter. The following sections will details how to collect this information.
@@ -24,7 +24,7 @@ In order to expose access to a Lex bot, you'll need to create a user account via
In the AWS admin panel, search for "IAM" and select the returned result. You are now in the IAM dashboard panel. From the left hand menu, under the "Access management" heading, select "Users". From here select the blue "Add users" button.
-
+
From here you will need to configure the new user. Choose a user name of your choice (perhaps "OpenDialogLexUser"), and select the credential type as "Access key - Programmatic access". Then select the blue "Next: Permissions" button.
@@ -38,7 +38,7 @@ On this final screen you can review the user configuration. When you're ready, c
Now that you've created your IAM user for Lex, select the new user from the "Users" table. On this screen, under the "Summary" heading there are multiple tabs. Select the tab titled "Security credentials". In this tab, under the "Access keys" heading, we can manage access keys for our IAM user. This is where we will create and find the first two pieces of data that OpenDialog requires: the key and the secret.
-
+
Click "Create access key". A modal will appear which contains a table with your key ID and secret key. The value under "Access key ID" should be pasted into the "Key" field in OpenDialog, and the "Secret access key" should be pasted into the "Secret" field.
@@ -58,7 +58,7 @@ On this screen you can configure the language of the bot. Use the "Select langua
Once your bot is created, you'll be automatically redirected to a screen for editing an intent. From OpenDialog to validate that the integration has been configured correctly, you'll need to set up at least one intent. To do this, you can re-purpose the intent you're currently viewing. If you'd like to come back to this later, all you'll need to do is add a single sample utterance. Under "Sample utterances", enter a sample utterance (such as "hello lex") and click "Add utterance".
-
+
For further details on setting up intents, see the [Lex documentation](https://docs.aws.amazon.com/lexv2/latest/dg/build-intents.html). Once you've set up the intent, click "Save Intent" and then "Build". The build process may take a few minutes, you'll know it's complete when you see a green "Successfully built..." message at the top of the screen.
@@ -80,7 +80,7 @@ You've now collected all the details required for the Lex interpreter.
Now that the interpreter is configured to integrate with our Lex bot, it can be tested via the "Check Interpreter Setup" in the bottom right. Enter an utterance such as "hello lex" (or whatever sample utterance(s) you entered for the intent earlier) and you should see that it was interpreted as the expected intent. It's useful to note the confidence percentage here, as this will be used shortly.
-
+
If the test returns an error, please review the Lex settings that you used to configure the interpreter.
@@ -96,7 +96,7 @@ The following steps presume that that you are working with the default conversat
In your scenario, locate the "Welcome Turn" within the "Welcome Conversation". By default this turn includes a single application request intent, and a single user response intent which matches the user clicking the default "OK" button. Add a second user response intent here to match the `newIntent` intent that was trained in Lex.
-
+
It's important to note that the confidence level for the intent should be less than what was returned in our test. If Lex interprets an intent with a confidence lower than our threshold, OpenDialog will disregard it.
@@ -108,10 +108,10 @@ Now that the interpreter is set on the intent, everything is in place see the Le
After the webchat widget loads, if you send a message such as "hello lex" (or whatever sample utterance(s) you entered for the intent earlier), you should see that the welcome message is re-sent to you. This means that OpenDialog successfully interpreted and matched the new Lex intent (if it didn't you'll get a no match error message).
-
+
To the right, under "Context" and "User" you should see some new attributes that begin with "lex\_". These attributes provide you with data about any slot elicitation or intent confirmation that might be configured in Lex. In OpenDialog, an intent is modeled as a single user utterance, and any slot filling is performed by subsequent intents. Therefore if you'd like to make use of Lex's slot elicitation or intent confirmation, you will need to query these Lex attributes via [OpenDialog conditions](https://docs.opendialog.ai/developing-with-opendialog/conditions).
-.png>)
+
Well done, you've now got your Lex bot integrated with your conversational application.
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-interpreter/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-interpreter/index.md
index 9d30490..3194b8c 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-interpreter/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-interpreter/index.md
@@ -6,11 +6,11 @@ title: Google Dialogflow interpreter
We can now create an interpreter in OpenDialog that will connect to that Dialogflow agent. On the "Interpreters Setup" page, select "Add new interpreter". Here you'll need to choose a unique name for the interpreter, enter the relevant language code, set your environment and paste your JSON key that we had just created in the previous step.
-.png>)
+
Once you've filled in the details you will be able to run a connectivity test to ensure that the API key is working correctly.
-.png>)
+
With a success message in place you are ready to start using intents in your conversation design.
@@ -18,7 +18,7 @@ With a success message in place you are ready to start using intents in your con
The Dialogflow management screen allows us to map Intents and/or Entities between OpenDialog and Dialogflow. What this means is that you can say things such as the intent calls "Example Intent" in OpenDialog should be compared with the intent called "Another Intent" in Dialogflow.
-.png>)
+
This makes it simpler to reuse preexisting intents or entities without having to rename things.
@@ -26,7 +26,7 @@ This makes it simpler to reuse preexisting intents or entities without having to
The last step is to activate our interpreter so that we can use it from within scenarios.
-.png>)
+
## Using the interpreter for an intent
@@ -34,26 +34,26 @@ Ok - let's try out our new NLU interpreter!
We will create two intents in Dialogflow. One for "I need help" and one for "I have a question".
-.png>)
+
The intents just have some example phrases associated with them and nothing else. We will handle the rest from within OpenDialog.
We will create a new scenario and add two open turns in the Welcome Scene, with each turn handling one of the intents.
-.png>)
+
-.png>)
+
The request intent from the user is set to use the Interpreter that we just created and we've set the confidence level to 60%.
The message is attached to the response intent.
-.png>)
+
## Preview
A quick try in our WebChat widget shows that our intent is being interpreter successfully by Dialogflow and providing a response.
-.png>)
+
Now that we know how to handle intents using Dialogflow as an NLU interpreter let's take a look at how to use Dialogflow knowledge base to handle FAQ queries in our next section.
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-knowledge-base/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-knowledge-base/index.md
index ccfe922..7c80092 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-knowledge-base/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/google-dialogflow-knowledge-base/index.md
@@ -10,15 +10,15 @@ Follow more detailed instructions in the [knowledge bases how-to](https://cloud.
For this particular example, we'll create a delivery knowledge base. Navigate to the Knowledge Bases in Dialogflow and create a knowledge base that is a FAQ knowledge type. You may use the document attached below as your knowledge base for your delivery related questions and answers. Once you have uploaded the CSV and added a response, your Delivery knowledge base should be similar to the one shown below.
-[DeliveryKnowledgeBase.csv](</.gitbook/assets/DeliveryKnowledgeBase.csv>)
+[DeliveryKnowledgeBase.csv](/files/deliveryknowledgebase.csv)
-
+<video autoplay loop muted playsinline aria-label="DialogFlow Knowledge Base Demo" src="/media/knowledge-base-demo.mp4"></video>
## Mapping Intents
Now navigate back to the interpreters section in OpenDialog and select the Dialogflow interpreter that you had setup in the previous section. Once selected you will then need to adjust the intent mapping. The incoming user intent name is `intent.dialogflow.faq` and that should be mapped to the knowledge base intent as shown in the figure below. This mapping will convert any `Knowledge.KnowledgeBase.*` intent from Dialogflow intent the `intent.dialogflow.faq` intent in OpenDialog.
-.png>)
+
## Testing the Interpreter
@@ -26,7 +26,7 @@ Now that the interpreter is configured to integrate with the Dialogflow knowledg
<div align="center">
-
+
</div>
@@ -36,33 +36,33 @@ Now that you've configured and tested your Dialogflow interpreter using the Know
You can add an FAQ turn to any scene. In this example we are adding it to the Welcome scene. The welcome scene has a welcome turn with an app welcome message.
-.png>)
+
Create a new turn in the called "FAQ".
-.png>)
+
In this turn you'll create a single user request intent for the question and a single application response intent for the answer.
First add a user request intent to match `intent.dialogflow.faq` (_this is the intent OpenDialog generates when Dialogflow successfully matches a pair_). Your sample utterance can be anything, in this case we use `[faq_question].`
-.png>)
+
It's important to note that the confidence level for the intent should be less than what was returned in our test. If FAQ interprets an intent with a confidence higher than our threshold, OpenDialog will disregard it. A general practice when working with the Dialogflow knowledge base is to set it to about 40%. After you've set up the intent, make sure to save it.
The intent that was just created captures the user's question. Let's now create an intent to return the answer to that question. Create an application response intent in the same turn.
-.png>)
+
After you've saved the response intent, edit the message. Delete the text message and add a custom attribute message.
-
+
Then add`user.dialogflow_message`in your XML snippet within the attribute message tags. By default all attributes are stored in the `user` context, unless they are mapped in [expected attributes](https://docs.opendialog.ai/turns-and-intents#advanced-settings). The attribute `dialogflow_message` is created by OpenDialog and will contain the answer from the matched Dialogflow Knowledge Base pair.
-
+
Make sure to save the message.
@@ -74,4 +74,4 @@ After the webchat widget loads, if you send a message such as "how long will shi
You can keep trying this with other question-answer pairs that were included in your knowledge base.
-.png>)
+
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/index.md
index 4f822e4..bd2c91b 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/dialogflow-interpreter/index.md
@@ -14,18 +14,18 @@ Once you've created an agent follow the instructions here to generate an API key
1. Go to the settings of you Dialogflow agent and click on the project link to go to the Google Cloud project console
-.png>)
+
2\. From within the Google Cloud console project go to the IAM & Admin > Service Accounts.
-.png>)
+
3\. Create a service account and give it the Dialogflow API Admin role. You will need to give it an ID and then grant the Role as shown below.
-.png>)
+
4\. Click on the account just created, head to the Keys tab and create a JSON key which will generate a file and download it to your machine.
-.png>)
+
We will now use this JSON key in our next step when creating our Dialogflow interpreter in OpenDialog.
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/luis-interpreter/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/luis-interpreter/index.md
index 6884616..f4b7513 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/luis-interpreter/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/luis-interpreter/index.md
@@ -12,7 +12,7 @@ Please see [these steps](https://docs.microsoft.com/en-gb/azure/cognitive-servic
You can find the app ID by selecting "Manage" on the "Settings" page under "Application Settings" and "App ID".
-
+
@@ -23,7 +23,7 @@ You can find the app URL and subscription key in the "Manage" section on the "Az
* APP URL is the value next to "Endpoint URL"
* Subscription key next to "Primary Key"
-
+
## Creating the LUIS interpreter
@@ -31,7 +31,7 @@ Now you'll need to create the LUIS interpreter in OpenDialog. On the "Interprete
You'll then be able to input the app URL, app ID and subscription key that were found in the LUIS portal (the other fields can be left as default for now).
-
+
For the moment, you can ignore all the other settings. You can now save the interpreter by clicking on 'save configuration' and train the LUIS application.
@@ -41,7 +41,7 @@ You can train the LUIS application to understand intents from user input, as wel
In your LUIS application select "Build" to get to the intent listing screen, then select "Create" to add a new intent. For this example, add an intent called `intent.app.orderRequest`. This will be trained to understand a product order request from a user.
-
+
Once the intent is created you'll need to provide some training utterances. Add an utterance such as "I want to order cupcakes", along with some others. For each example, type it in the text field under "Example user input" and hit the enter key to add it.
@@ -49,13 +49,13 @@ Once added you'll want to highlight the product name (eg. "Cupcakes") to mark it
On the first time, select "View in entity pane", add a new "product" list entity. Then re-highlight the word, select the "product" entity and add the product name as new sublist.
-
+
This means that when this intent is interpreted, LUIS will attempt to extract the desired product too.
You can add as many training utterances and entities as you like.
-
+
Once you're happy with the training utterances and entities, click "Train" in the top right. The model may take a few seconds or minutes to train. Once it's complete click "Publish" and select the "staging" slot for now. This will make the latest trained version of your application available to OpenDialog.
@@ -67,13 +67,13 @@ In this example, LUIS has been trained to extract an entity called "product"; by
To demonstrate this, the interpreter can be configured to do so by setting up an entity mapping from the LUIS entity named "product" to the OpenDialog attribute "customer\_product". Once you've created the mapping, make sure to save it.
-
+
## Testing the interpreter
Now that the interpreter is configured to integrate with our LUIS application, it can be tested via the "Check Interpreter Setup" in the bottom right. Enter an utterance such as "i want to order cupcakes" and you should see that it was interpreted as the intent trained earlier. It's useful to note the confidence percentage here, as this will be used shortly.
-
+
If it matches the 'None' intent instead, then you'll need to review the training utterances that you provided in the LUIS application and make sure that they cover the utterance you tested. If you make a change in LUIS this will require you to re-train the model and re-publish it to the staging slot.
@@ -91,7 +91,7 @@ Now that you've configured and tested your LUIS interpreter you'll want to make
In your scenario, locate the "Welcome Turn" within the "Welcome Conversation". By default this turn includes a single application request intent, and a single user response intent which matches the user clicking the default "OK" button. Add a second user response intent here to match the `intent.app.orderRequest` intent that was trained in LUIS.
-
+
It's important to note that the confidence level for the intent should be less than what was returned in our test. If LUIS interprets an intent with a confidence lower than our threshold, OpenDialog will disregard it.
@@ -103,7 +103,7 @@ Now that the interpreter is set on the intent, everything is in place see the LU
After the webchat widget loads, if you send a message such as "i want to order cupcakes", you should see that the welcome message is re-sent to you. This means that OpenDialog successfully interpreted and matched the new LUIS intent (if it didn't you'll get a no match error message). To the right, under "Context" and "User" you should see a new "customer\_product" attribute with a value of "cupcakes". You can keep trying this with other entities that you trained LUIS for. Remember that if you update LUIS intents or entities, you'll need to re-train and re-publish the model.
-
+
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/openai-interpreter/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/openai-interpreter/index.md
index 42af346..4be04d1 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/openai-interpreter/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/openai-interpreter/index.md
@@ -10,7 +10,7 @@ This interpreter will return a single intent with the name of `OpenAIPrompt`. It
To use OpenAI's you'll need to [create an account](https://platform.openai.com/) with OpenAI. Once you are signed up, you'll need to [create an API key](https://platform.openai.com/api-keys) via the "API keys" screen. You'll need to keep note of the generated API key for the next step.
-
+
*The API keys screen in OpenAI.*
@@ -18,7 +18,7 @@ To use OpenAI's you'll need to [create an account](https://platform.openai.com/)
In your OpenDialog application, navigate to the desired scenario, and then the "Interpret" screen. Click the blue "Add new interpreter" button to begin creating the new interpreter. You will then see the following screen where you can give the interpreter a name and configure it. You will need to select the OpenAI option under "Interpreter Type".
-
+
*Creating an OpenAI interpreter in OpenDialog.*
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/qna-interpreter/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/qna-interpreter/index.md
index 2efca0a..86f6a61 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/qna-interpreter/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/available-interpreters/qna-interpreter/index.md
@@ -14,11 +14,11 @@ You can train the QnA knowledge base to understand questions from a user, and ma
In your QnA knowledge base select "Add QnA pair" to add a new question and answer pair. For this example, add a question of "What time do you open" with an answer of "We open at 9am Monday to Friday and 10am on Saturday. We are closed on Sundays.".
-
+
You can add as many training pairs as you like.
-
+
Once you're happy with the training pairs, click "Save and train" in the top right. The model may take a few seconds or minutes to train. Once it's complete click "Publish" and publish the knowledge base.
@@ -27,13 +27,13 @@ There are two key credentials to make note of after you publish your knowledge b
1. **APP URL** is the combination of the host URL (next to the "Host:" field) and the endpoint (next to "POST"), it will be something similar to "https://\[your-qna-service].azurewebsites.net/qnamaker/knowledgebases/\[id]/generateAnswer".
2. **Endpoint key** is found after "Authorization: EndpointKey".
-
+
## Create the QnA interpreter
Now you'll need to create the QnA interpreter in OpenDialog. On the "Interpreters Setup" page, select "Add new interpreter". Here you'll need to choose a unique name for the interpreter and select the QnA type. You'll then be able to input the app URL and endpoint key that were found in the previous step.
-
+
You can now save the interpreter.
@@ -41,7 +41,7 @@ You can now save the interpreter.
Now that the interpreter is configured to integrate with the QnA knowledge base, it can be tested via the "Check Interpreter Setup" in the bottom right. Enter an utterance such as "what time do you open in the morning" and you should see that it was interpreted as the intent trained earlier. It's useful to note the confidence percentage here, as this will be used shortly.
-
+
If it matches the 'None' intent instead, then you'll need to review the training pairs that you provided in the QnA knowledge base and make sure that they cover the utterance you tested. If you make a change in QnA this will require you to re-train the model and re-publish it.
@@ -61,19 +61,19 @@ In your scenario, locate the "Welcome Turn" within the "Welcome Conversation". B
Navigate to the "Welcome Scene" and create a new turn in the called "Q\&A".
-
+
In this turn you'll need to create a single user request intent for the question and a single application response intent for the answer.
First add a user request intent to match `intent.core.QnAQuestionMatched` (_this is the intent OpenDialog generates when QnA successfully matches a pair_).
-
+
It's important to note that the confidence level for the intent should be less than what was returned in our test. If Q\&A interprets an intent with a confidence lower than our threshold, OpenDialog will disregard it. After you've set up the intent, make sure to save it.
The intent that was just created captures the user's question, however an intent will also need to be created to return the answer to that question. Next create an application response intent in the same turn.
-
+
After you've saved the response intent, select it and click the yellow messages button in the action bar.
@@ -83,7 +83,7 @@ Click the yellow edit button in the top right of the autogenerated message to ed
At the bottom of the screen, update the text message contents to `{user.qna_answer}`. By default all attributes are stored in the `user` context, unless they are mapped in [expected attributes](https://docs.opendialog.ai/turns-and-intents#advanced-settings). The attribute `qna_answer` is created by OpenDialog and will contain the answer from the matched QnA pair.
-
+
Make sure to save the message.
@@ -95,6 +95,6 @@ After the webchat widget loads, if you send a message such as "what time do you
You can keep trying this with other question-answer pairs that you trained QnA for. Remember that if you update QnA pairs, you'll need to re-train and re-publish the model.
-
+
Well done, you've now got your QnA instance integrated with your conversational application.
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/index.md
index dbdba1d..992afd2 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/index.md
@@ -31,11 +31,11 @@ Additional steps are required to complete the integration set-up between OpenDia
Multiple Interpreters can exist within a single scenario, and each Interpreter can fulfil a different purpose. Every Interpreter you create will be shown as a card on the 'Interpret' landing page.
-
+
*Interpreters overview page*
-
+
*Adding a new interpreter page*
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/interpreter-orchestration/index.mdx b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/interpreter-orchestration/index.md
similarity index 91%
rename from src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/interpreter-orchestration/index.mdx
rename to src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/interpreter-orchestration/index.md
index 58b2be6..fc7bb0b 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/interpreter-orchestration/index.mdx
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/interpreter-orchestration/index.md
@@ -3,10 +3,7 @@ title: Interpreter Orchestration
description: Use OpenDialog Interpreter Orchestration to set a highest priority interpreter at different levels of your conversation.
---
-import Embed from '~/components/Embed.astro';
-
-
-
+
@@ -43,7 +40,7 @@ With Interpreter Orchestration, you can do just this! The prioritisation drop do
The Interpreter Orchestration functionality can be accessed from the side panel of the conversation designer.
-.png>)
+
To access the Interpreter Orchestration feature within the intents sidebar for a given scenario:
@@ -52,7 +49,7 @@ To access the Interpreter Orchestration feature within the intents sidebar for a
* Click 'Interpreter' from the side panel
* Choose the interpreter you would like to prioritise for that scenario
-
+
This functionality can also be accessed from different component levels:
@@ -82,4 +79,8 @@ Through this, the process of intent matching is streamlined, and gives the desig
## How to use - video
-<Embed url="https://www.loom.com/share/ef6e52e9a2194c80bb2b22f04e2aee45?sid=87f3d5f7-b553-410b-a969-13672d8c1002" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/ef6e52e9a2194c80bb2b22f04e2aee45" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/troubleshooting-interpreters/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/troubleshooting-interpreters/index.md
index e0eaf31..115d4c4 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/troubleshooting-interpreters/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/interpreters/troubleshooting-interpreters/index.md
@@ -6,13 +6,13 @@ title: Troubleshooting interpreters
* Make sure that your knowledge base is working in the NLU service. E.g.
-  .png>)
+  
* Test your interpreter setup in OD. Note that success in OD doesn't mean that your knowledge base is working; you must check the previous step as well
- 
+ 
*Run interpreter test in OD*
@@ -20,13 +20,13 @@ title: Troubleshooting interpreters
* Make sure your intent names align and use the names as shown in the image and the documentation. Check that your answer intent has an attribute message per the documentation.
-  
+  
## Troubleshooting
Q: Everything seems to be working but I get an empty answer in my preview.
-
+
*Preview screen showing empty KB answer*
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation/index.md
index c4ad5f5..12c4f9c 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation/index.md
@@ -16,7 +16,7 @@ The OpenDialog RAG service allows you to
-.png>)
+
*Simplified diagram of the Retrieval Augmented Generation process*
@@ -48,7 +48,7 @@ To access the RAG service feature in your workspace:
* Create a new RAG service by using the Create language service button
:::
- (1) (2).png>)
+
*Access the ability to add a RAG service via the Language Services feature*
@@ -62,13 +62,13 @@ In some cases, throughout the product you might find that RAG services are refer
The <mark style="color:purple;">**RAG service settings**</mark> section allows you to name and provide a description for your RAG service to easily recognise it in the Language Services Dashboard. Once it is being used in your applications, you can also visualise the scenarios that are actively using this particular RAG service.
-
+
*Access the RAG service settings components via the left-hand menu*
The <mark style="color:purple;">**Topics**</mark> section allows you to define, manage, edit and test the main semantic topics of your RAG service.
- (1) (2) (1).png>)
+
*The topics overview provides you with an overview of your different topics, and the ability to manage them*
@@ -78,7 +78,7 @@ To action the generation of responses based on your RAG service, you will need t
### Overview
-
+
*Overview of the steps within OpenDialog to setup and use a RAG service*
@@ -108,7 +108,7 @@ A knowledge string is a piece of syntax you will use to reference a specific RAG
#### Basic settings
- (2) (1).png>)
+
*From the Language Services dashboard, view your created RAG services or create a new one*
@@ -121,7 +121,7 @@ A knowledge string is a piece of syntax you will use to reference a specific RAG
* Click 'Create service' button to finish creating your service
:::
- (2).png>)
+
*RAG service setup page*
@@ -149,7 +149,7 @@ Top K refers to the number of top results or items to retrieve during a search o
Once you have created your [RAG ](/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation#rag)service setup, you will get taken to the [Topics](/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation#topics) page. This page will be empty when first creating your service. You can start setting up your topics, by clicking on the Add topic button in the top right corner of the middle panel of your screen.
- (2).png>)
+
*Select the 'Add topic' button from the top right hand corner of your screen*
@@ -163,7 +163,7 @@ Once you have created your [RAG ](/opendialog-platform/interpreters-and-natural-
* This will trigger the 'Add sources' section to appear
:::
- (2).png>)
+
*Provide a name, description to your topic and create it by clicking on the create topic button*
@@ -177,7 +177,7 @@ Once you have created a topic, you can start adding your documents, data and inf
* Select the source type of your data
:::
-
+
*Add your information sources to a topic using the 'Add source' dropdown*
@@ -192,7 +192,7 @@ Once you have selected text, the text upload modal will pop up. From here you ca
* Select 'Upload source' once you are finished
:::
-
+
*From the URL uploader modal you can start to add in your URL's in the 'URL Source' field*
@@ -200,7 +200,7 @@ Once you have selected text, the text upload modal will pop up. From here you ca
To add a URL source, you first need to select the 'URL' option from the topic source drop down menu.
-
+
*Select URL from the topic source dropdown menu*
@@ -208,13 +208,13 @@ Once you have selected 'URL' from the topic source dropdown, the URL upload moda
You also have the option to include exclusion ID's and Classes. These optional fields allow you to select parts of your URL that you would not like to be referenced. Then when your URL source is vectorised, these ID's and Classes will not be included.
-
+
*Here you have the option to input any exclusion ID's and Classes for your URL source(s)*
Once you are happy with the URL\`s selected, you can click the 'Upload source' button to add them to your topic.
-
+
*Click the 'Upload source' button to add your URL's to your topic*
@@ -243,13 +243,13 @@ The types of document that can be uploaded to your topic as a source are:
-
+
*Select 'Document' from the topic source dropdown menu*
Once you have selected Document, the document upload modal will pop up. From here you can either click to upload a document of your choice, or you can drag and drop files onto the modal. You can upload multiple files at once if you wish to.
-
+
*The document upload modal*
@@ -257,11 +257,11 @@ After you have selected the files that you want to upload, you can see them list
Once you are happy with the files selected, you can click the 'Upload source' button to add them to your topic.
-
+
*Once you're happy with your uploaded documents, click 'Upload source'*
-
+
*Once you have uploaded your document, you can see it in your topic sources table*
@@ -286,7 +286,7 @@ Your topic sources now need to be converted to their numerical representation, u
-
+
*Select your topic sources to start vectorisation*
@@ -308,7 +308,7 @@ Once you have vectorised your different topic sources for a given topic, you can
* View results - scroll down to see the full results
:::
-
+
*Testing your knowledge service using the test panel*
@@ -316,7 +316,7 @@ Once you have vectorised your different topic sources for a given topic, you can
You can use your RAG service in your AI application by referencing it through a [knowledge string](/opendialog-platform/interpreters-and-natural-language-understanding/language-services/retrieval-augmented-generation#knowledge-strings) in other services, like LLM Actions. In order to do so, you need to retrieve or construct the relevant knowledge strings.
- (2).png>)
+
*Syntax structure of a knowledge string*
@@ -363,7 +363,7 @@ In order to use the knowledge from within a specific RAG service to generate res
For more information on LLM actions, please check the [**LLM Actions**](/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions) section of the documentation.
:::
-
+
*Using the AboutCompany RAG service in an LLM action*
@@ -419,6 +419,6 @@ Your LLM action's response based on the RAG knowledge will be stored against an
-
+
*Reference your generated response via the output attribute*
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/azure/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/azure/index.md
index 3f51be4..cc2f3e2 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/azure/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/azure/index.md
@@ -6,7 +6,7 @@ title: Azure
Semantic Intent Classifiers allow you to integrate with a large language model provider, for example, Azure OpenAI, in order to allow your scenario to understand user input. It can be found under the Language Services section of your OpenDialog Workspace. Once you select 'Create new service' and subsequently 'Semantic Intent Classifier' you will then have the opportunity to create it. Select Azure OpenAI to start setting up your Azure OpenAI integration.
-
+
*Setting up an OpenAI integration via OpenDialog*
@@ -30,7 +30,7 @@ To configure your Azure OpenAI LLM action you will need to provide the following
To set up your Azure OpenAI Semantic Intent Classifier, navigate to "Language services". Use the "Create new service" button to begin creating a new Language service. Next select the "Semantic Intent Classifier type".
-
+
*Use the "Create an LLM action" button to set up a new OpenAI integration*
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/google-gemini/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/google-gemini/index.md
index ac762b2..0bd3f87 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/google-gemini/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/google-gemini/index.md
@@ -6,7 +6,7 @@ title: Google Gemini
Semantic Intent Classifiers allow you to integrate with a large language model provider, for example, Google Gemini, in order to allow your scenario to understand user input. It can be found under the Language Services section of your OpenDialog Workspace. Once you select 'Create new service' and subsequently 'Semantic Intent Classifier' you will then have the opportunity to create it. Select Google Gemini to start setting up your Gemini integration.
-
+
*Setting up an OpenAI integration via OpenDialog*
@@ -30,7 +30,7 @@ To configure your Google Gemini Semantic Intent Classifier you will need to prov
To set up your Google Gemini Semantic Intent Classifier, navigate to "Language services". Use the "Create new service" button to begin creating a new Language service. Next select the "Semantic Intent Classifier type".
-
+
*Use the "Create an LLM action" button to set up a new OpenAI integration*
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/index.mdx b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/index.md
similarity index 92%
rename from src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/index.mdx
rename to src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/index.md
index 33e3282..5ae7d95 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/index.mdx
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/index.md
@@ -3,14 +3,11 @@ title: Semantic Intent Classifier
description: OpenDialog's Semantic Intent Classifier provides a quick and easy way to enable natural language input within your bot, allowing you to interpret user utterances without training phrases.
---
-import Embed from '~/components/Embed.astro';
-
-
Interpreting a user's utterance is an important part of conversation design. It ensures your bot can understand what a user has said in natural language, understand whether it is a question about 'Policy' or 'Making a claim', and accurately match an intent. Conversations are non-linear and context-driven, meaning effective intent management and matching is integral to great conversation design.
[Try the OpenDialog digital concierge](https://opendialog.ai/opendialog-digital-concierge/)
-
+
*Classify intents and sub intents with an LLM using our Semantic intent classifier*
@@ -42,7 +39,7 @@ You can configure and test your Semantic Intent Classifier using our test panel
To create a Semantic Intent Classifier, first, add it as a Language Service from the Workspace Dashboard.
-
+
*You can begin creating a Semantic intent classifier from the Language services landing page*
@@ -117,7 +114,11 @@ A Semantic Intent Classifier Language Service has 4 main components:
### Overview
-<Embed url="https://www.loom.com/share/ad624135bb6c4747b4811e50f09a31ff" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/ad624135bb6c4747b4811e50f09a31ff" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
### Vocabulary
@@ -137,7 +138,7 @@ A question or statement that provides instructions to an AI system to generate a
To get started, create a Semantic Intent Classifier Language Service.
-
+
*Create a Semantic intent classifier and select your configuration settings*
@@ -198,7 +199,7 @@ If you change the name of a Language Service you are currently using, you will a
With your Language Service configured, you can begin creating Intents and sub-intents.
-
+
*Create intents, add sub intents and test as you go*
@@ -213,7 +214,7 @@ You can create an Intent and sub intents simultaneously by clicking '+ Add sub I
Every intent you create will be represented in a list, from latest to first created, and provide tools to let you manage your intents with ease.
-
+
*Editing and managing your intents is simple, quick and easy*
@@ -235,7 +236,7 @@ A persistent test panel is present in both the intent creation screen, and promp
OpenDialog also allows you to provide additional prompt information alongside your intents and their classification instructions. Within your prompt, you can also include `{attributes}`, define their values, and include custom output attributes.
-
+
*Providing additional prompt information will better support the operation of your language service*
@@ -277,7 +278,7 @@ The prompt configuration area also allows you to create Custom output attributes
After configuring your Language Service, Intents and Prompt, it's time to add an Interpreter to link your Language Service to a scenario.
-
+
*Create an interpreter, and select the Semantic intent classifier language service*
@@ -357,7 +358,7 @@ If this list is complete, you are ready to go.
Your Semantic Intent Classifier must be added to a `USER` intent within the conversation designer, by navigating through the corresponding conversation, scene, turn and intent where you wish to add it.
-
+
*Add your completed Semantic intent classifier to a user intent within the conversation designer*
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/openai/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/openai/index.md
index 3392402..1418109 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/openai/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/language-services/semantic-intent-classifier/openai/index.md
@@ -6,7 +6,7 @@ title: OpenAI
Semantic Intent Classifiers allow you to integrate with a large language model provider, for example, OpenAI, in order to allow your scenario to understand user input. It can be found under the Language Services section of your OpenDialog Workspace. Once you select 'Create new service' and subsequently 'Semantic Intent Classifier' you will then have the opportunity to create it. Select OpenAI to start setting up your OpenAI integration.
-
+
*Setting up an OpenAI integration via OpenDialog*
@@ -28,7 +28,7 @@ If you are using your own credentials, unselect 'OpenDialog managed' and provide
To set up your OpenAI Semantic Intent Classifier, navigate to "Language services". Use the "Create new service" button to begin creating a new Language service. Next select the "Semantic Intent Classifier type".
-
+
*Use the "Create an LLM action" button to set up a new OpenAI integration*
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/azure-openai/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/azure-openai/index.md
index 9b7b404..4856ed9 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/azure-openai/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/azure-openai/index.md
@@ -7,7 +7,7 @@ description: This section outlines how you can set up a LLM action using Azure O
LLM Actions allow you to integrate with a large language model provider, for example, Azure OpenAI. It can be found under the Integrate section of a specific scenario. Once you select 'Create an LLM action' you will then have the opportunity to create the LLM action of your choice. Select Azure OpenAI to start setting up your OpenAI integration.
-
+
*Setting up an Azure OpenAI integration via OpenDialog*
@@ -45,7 +45,7 @@ OpenDialog validates that the referenced secret exists when you save the configu
To set up your Azure OpenAI LLM action, navigate to "Integrate", and select "LLM Actions" from the menu. Use the "Create an LLM action" button to set up a new LLM action.
-
+
*Use the "Create an LLM action" button to set up a new Azure OpenAI integration*
@@ -55,7 +55,7 @@ After providing a name and a description for your LLM action, select "Azure Open
To use your Azure OpenAI LLM action in your scenario, you can add it to an intent in the Designer.
-
+
*Select the desired intent in the designer and click "Add conditions, actions & attributes" to reveal the Action section*
@@ -63,7 +63,7 @@ When your scenario matches this intent, the prompts will be sent to the LLM and
To display the LLM's response text in your scenario, you will need to use the `llm_response` attribute (or any other desired output attributes) within a [message](/opendialog-platform/conversation-designer/message-design/message-editor). Within a message, create a new text block, set the text to `{llm_response}` and click "Save Message".
-
+
*Create a text message using the LLM's response by using the `llm_response` attribute*
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/index.mdx b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/index.md
similarity index 92%
rename from src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/index.mdx
rename to src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/index.md
index edc4772..2e5fb68 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/index.mdx
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/index.md
@@ -3,14 +3,11 @@ title: LLM Actions
description: An LLM Action enables you to use LLMs to perform reasoning, generate text and feed that information back into your scenario in order to influence the next steps of the conversation.
---
-import Embed from '~/components/Embed.astro';
-
-
Using LLM Actions you have more fine-grained control over when and how to involve an LLM in your conversation since actions can be performed _after_ a user intent has been interpreted (by an OpenDialog interpreter) or _before_ a bot message was sent to the user. This enables you to influence the context of the conversation as best required by your scenario.
This section will help you to understand what an LLM action is, and how to configure and use it within your conversation.
-
+
*Generate content using specific instructions or perform reasoning that can inform decision-making within the conversation flow*
@@ -48,7 +45,7 @@ Amend and configure the behaviour of your LLM action using the test panel, ensur
LLM actions are an additional integration to the conversation designer and can be found under 'Integrate' within the sidebar menu.
-
+
*You can find LLM Actions under 'Integrate' in the sidebar menu*
@@ -64,7 +61,11 @@ To access LLM actions:
## How to use
-<Embed url="https://www.loom.com/share/c6cac1069fbf4596824e80448de4630b" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.loom.com/embed/c6cac1069fbf4596824e80448de4630b" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
## Structure
@@ -77,7 +78,7 @@ LLM Actions have two main components:
Within the settings area, you can configure your engine, enter your prompt, apply any advanced settings and enter any safeguarding considerations.
-.png>)
+
*Initial LLM Action set up, where you can choose a name, description, your preferred LLM engine and model*
@@ -108,7 +109,7 @@ Each requires a slightly different configuration.
:::danger
Note - you will need to enter the model used for Azure OpenAI, and this needs to match the deployment in Azure. If the model you entered does not match, you will get an error message when testing your action configuration\
\
-.png>)
+
:::
#### When using a custom configuration
@@ -138,7 +139,7 @@ Within prompt configuration you will see two main areas:
Use the system prompt to specify how the LLM should respond. When creating a prompt, always ensure it is clear, specific, and concise. Provide context, avoid ambiguity, and define the desired output format.
-
+
*Configure a system prompt that can be sent as instructions to the LLM*
@@ -148,11 +149,11 @@ _"You are a helpful car insurance assistant. The user will provide questions or
It is also possible to include [attributes](/core-concepts/contexts-and-attributes/about-attributes) within your system, for example:
-_"You are a helpful car insurance assistant. The user will provide questions or statements related to car insurance claims, and you will categorise their input. The user's vehicle is a \{vehicle\_type\}. Output whether the user is asking to make a claim (make\_claim), asking about the status of a claim (claim\_status) or an FAQ about a claim (claim\_faq). If none of the above, return an empty string."_
+_"You are a helpful car insurance assistant. The user will provide questions or statements related to car insurance claims, and you will categorise their input. The user's vehicle is a {vehicle\_type}. Output whether the user is asking to make a claim (make\_claim), asking about the status of a claim (claim\_status) or an FAQ about a claim (claim\_faq). If none of the above, return an empty string."_
-
+
*A prompt containing attributes*
@@ -203,13 +204,13 @@ Setting a higher temperature will provide less probable words, leading to more v
This area allows you to configure specific aspects of your LLM’s behaviour. You can find these within the advanced expandable section under 'Prompt configuration'. OpenDialog automatically provides a default setting for most options, however you can adjust them to your preference, and see immediate cause and effect using the testing panel.
-
+
*Configure your LLM action in more detail using advanced settings*
#### **User prompt**
-The user prompt field allows you to provide a custom user prompt to the LLM. By default this field will contain `{utterance_text}` which means that the LLM will receive whatever text the user enters into Webchat. A custom user prompt allows you to constrain what is received by the LLM. You may choose to use attributes to provide a bespoke input, such as _"I work \{distance\}km away from my house"_. These attributes can be retrieved from form messages, button messages, interpreters or other actions. You can also choose to remove the user prompt completely. This means that no user input is sent to the LLM (besides any attributes in the system prompt). This can be useful if you want to generate text based solely on pre-defined instructions in your system prompt.
+The user prompt field allows you to provide a custom user prompt to the LLM. By default this field will contain `{utterance_text}` which means that the LLM will receive whatever text the user enters into Webchat. A custom user prompt allows you to constrain what is received by the LLM. You may choose to use attributes to provide a bespoke input, such as _"I work {distance}km away from my house"_. These attributes can be retrieved from form messages, button messages, interpreters or other actions. You can also choose to remove the user prompt completely. This means that no user input is sent to the LLM (besides any attributes in the system prompt). This can be useful if you want to generate text based solely on pre-defined instructions in your system prompt.
:::note
When a user prompt is specified in the advanced section, the user utterance within the test panel is replaced with the user prompt you entered.
@@ -219,13 +220,13 @@ When a user prompt is specified in the advanced section, the user utterance with
By defining output attributes, the LLM will be prompted to return data for each attribute. This allows you to retrieve granular data alongside standard response text. Each output attribute can also be coupled with an optional instruction. This instruction specifies how the LLM should attempt to populate the attribute. Any populated output attributes will be displayed in the testing panel after running a test of the action.
-
+
*Specify attributes and use them within message design*
Output attributes are incredibly useful, and can be used to affect the conversational flow via conditions.
-
+
*Add attributes in messages, and use an LLM to continue the conversation*
@@ -250,19 +251,19 @@ _The factors to consider here:_
Then we set some output attributes, for example:
-_\{can\_insure\_string\} either yes, no, unknown or unrelated_
+_{can\_insure\_string} either yes, no, unknown or unrelated_
-_\{follow\_up\_question\} if you need more info, this is what we should ask the user_
+_{follow\_up\_question} if you need more info, this is what we should ask the user_
-With these output attributes created and their values defined, we can now configure messages based on the circumstances of the user's application. If they can be insured, we can redirect to \{can\_insure\_string\}. If we need more information, we can redirect to the \{follow\_up\_question\} to gather more information.
+With these output attributes created and their values defined, we can now configure messages based on the circumstances of the user's application. If they can be insured, we can redirect to {can\_insure\_string}. If we need more information, we can redirect to the {follow\_up\_question} to gather more information.
</details>
-With these output attributes created and their values defined, we can now configure messages based on the circumstances of the users application. If they can be insured, we can redirect to \{can\_insure\_string\}. If we need more information, we can redirect to the \{follow\_up\_question\} to gather more information.
+With these output attributes created and their values defined, we can now configure messages based on the circumstances of the users application. If they can be insured, we can redirect to {can\_insure\_string}. If we need more information, we can redirect to the {follow\_up\_question} to gather more information.
-.png>)
+
#### File Attribute
@@ -323,7 +324,7 @@ LLMs can sometimes be unpredictable without careful consideration. We highly rec
At OpenDialog, the safety of both our customers and your users is paramount; therefore, our LLM actions provide safeguarding tools to help meet both the criteria of your business and the expectations of your customers.
-
+
*Create safer LLM actions using OpenDialogs safeguarding tools and features*
@@ -351,7 +352,7 @@ Please note that the utterances and words added to the exclusion lists are consi
When creating your LLM action, the test panel will allow you to try the action, and see both the Inputs and the Outputs within a test. It's a great indicator of what you can expect from your action and provides a safe space to change and iterate the behaviour of your action. It's also worth noting that testing response text and attributes are not guaranteed to be the same when used in your scenario due to the inherent non-determinism of LLMs.
-
+
*The test panel will display what is sent to the LLM (Inputs), and what in turn is received from the LLM in return (Outputs)*
@@ -378,7 +379,7 @@ Any attributes that have had a manual value entered will no longer appear with a
#### Testing LLM Actions with Files
-.png>)
+
*Files selected, but not uploaded*
@@ -388,7 +389,7 @@ Once the files have been uploaded, they will appear in the list of uploaded file
Once all selected files have been uploaded, the `Run LLM Test` button will become active again, and you can run a test along with the uploaded files, simulating user uploaded files.
-.png>)
+
*2 files uploaded and ready to go*
@@ -396,7 +397,7 @@ Once all selected files have been uploaded, the `Run LLM Test` button will becom
This area shows the information received from the LLM based on the input data.
-
+
*When an LLM test is run, all outputs will be shown in the 'Outputs' section in the test panel window*
@@ -438,7 +439,7 @@ Token calculation varies based on the LLM you use and the specific model selecte
If files were uploaded and sent in the test, that will be indicated in the inspector, showing the name and type of file included along with the name of the file attribute referenced
-.png>)
+
## Frequently asked questions
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/llm-action-analytics/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/llm-action-analytics/index.md
index 5518f4f..7f4bd70 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/llm-action-analytics/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/llm-action-analytics/index.md
@@ -4,7 +4,7 @@ title: LLM Action Analytics
Every LLM Action is logged and you can download those Logs directly from the action.
-.png>)
+
*Aggregate and Detail LLM Action log data*
diff --git a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/openai/index.md b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/openai/index.md
index 1a5ce51..d0755ee 100644
--- a/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/openai/index.md
+++ b/src/content/docs/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions/openai/index.md
@@ -7,7 +7,7 @@ description: This section outlines how you can set up an LLM action using OpenAI
LLM Actions allow you to integrate with a large language model provider, for example, OpenAI. It can be found under the Integrate section of a specific scenario. Once you select 'Create an LLM action' you will then have the opportunity to create the LLM action of your choice. Select OpenAI to start setting up your OpenAI integration.
-
+
*Setting up an OpenAI integration via OpenDialog*
@@ -44,7 +44,7 @@ OpenDialog validates that the referenced secret exists when you save the configu
To set up your OpenAI LLM action, navigate to "Integrate", and select "LLM Actions" from the menu. Use the "Create an LLM action" button to set up a new LLM action.
-
+
*Use the "Create an LLM action" button to set up a new OpenAI integration*
@@ -54,7 +54,7 @@ After providing a name and a description for your LLM action, select "Open AI" a
To use your OpenAI LLM action in your scenario, you can add it to an intent in the Designer.
-
+
*Select the desired intent in the designer and click "Add conditions, actions & attributes" to reveal the Action section*
@@ -62,7 +62,7 @@ When your scenario matches this intent, your LLM prompts will be sent to the lan
To display the LLM's response text in your scenario, you will need to use the `llm_response` attribute (or any other desired output attributes) within a [message](/opendialog-platform/conversation-designer/message-design/message-editor). Within a message, create a new text block, set the text to `{llm_response}` and click "Save Message".
-.png>)
+
*Create a text message using the LLM's response by using the `llm_response` attribute*
diff --git a/src/content/docs/opendialog-platform/launching-your-application/index.mdx b/src/content/docs/opendialog-platform/launching-your-application/index.md
similarity index 88%
rename from src/content/docs/opendialog-platform/launching-your-application/index.mdx
rename to src/content/docs/opendialog-platform/launching-your-application/index.md
index 4ee7e15..05c050f 100644
--- a/src/content/docs/opendialog-platform/launching-your-application/index.mdx
+++ b/src/content/docs/opendialog-platform/launching-your-application/index.md
@@ -2,17 +2,15 @@
title: Launching your application
---
-import Embed from '~/components/Embed.astro';
-
## Publishing a single scenario to WebChat
To launch your conversational application using the OpenDialog WebChat on your website or application, start by activating the scenario. To do so, go to the 'Scenarios' page and click on the slider to set it to 'active'.
-.png>)
+
Next, go to Interface Settings under the Publish menu and click "Get embed code". Copy the embed code.
-
+
*Interface settings screen with open embed code window*
@@ -34,13 +32,18 @@ OpenDialog Aliases allow you to create a single point of reference for your WebC
An alias can map to any given scenario and therefore exists on the Workspace level. You can access the Aliases functionality from the Workspace Dashboard by expanding the 'Scenarios' drop down menu, where you can then find 'Aliases' in the Menu.
-
+
*Access the Alias functionality via the Workspace Menu*
### How it works
-<Embed url="https://youtu.be/k57nEd_ruWQ" title="How to use Aliases in the OpenDialog Product" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.youtube-nocookie.com/embed/k57nEd_ruWQ" title="How to use Aliases in the OpenDialog Product" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+<figcaption>How to use Aliases in the OpenDialog Product</figcaption>
+</figure>
#### Creating an alias
@@ -48,7 +51,7 @@ To create an Alias you need an Alias name and a scenario.
The Alias name must follow certain rules: only lowercase letters can be used, and spaces must be replaced with underscores (\_). No numbers, symbols, or uppercase letters are allowed.
-
+
*The Alias creation UI*
@@ -60,7 +63,7 @@ Once the Alias is created, an embedded WebChat code is created and provided.
Once an Alias is created it appears in the Alias tab of the workspace. To edit, click into the Alias, change the linked scenario, and click the "Update Alias" button.
-
+
*The Alias updating UI*
diff --git a/src/content/docs/opendialog-platform/monitoring-your-application/index.mdx b/src/content/docs/opendialog-platform/monitoring-your-application/index.mdx
index ab23357..ba6eec1 100644
--- a/src/content/docs/opendialog-platform/monitoring-your-application/index.mdx
+++ b/src/content/docs/opendialog-platform/monitoring-your-application/index.mdx
@@ -3,14 +3,15 @@ title: Monitoring your application
description: Use the OpenDialog Analyse feature to make informed decisions about the past, present and future of your conversational application.
---
-import { CardGrid, LinkCard } from '@astrojs/starlight/components';
+import { CardGrid } from '@astrojs/starlight/components';
+import CoverCard from '~/components/CoverCard.astro';
This section explains how to track user interactions with your conversational application and identify trends in project usage.
The OpenDialog Analyse dashboard provides a comprehensive view of recent interactions, a log of the latest messages, and a high-level summary of usage patterns over time.
-
+
*The OpenDialog Analyse dashboard gives you an overview of the latest interactions with your application and a bird-eye overview of project usage over time.*
@@ -49,7 +50,7 @@ By visualising usage trends, you can see the evident uptake or downturn in the n
Analyse allows you to explore how your application has been performing. It is, therefore, part of the testing suite of a given scenario.
-.png>)
+
*You can find Analyse, in the Test section of your scenario menu.*
@@ -69,9 +70,9 @@ To use the Analyse feature within OpenDialog, navigate to the 'Analyse' dashboar
Analyse has three main components: project usage, interaction logs, and message log table:
<CardGrid>
- <LinkCard title="Project usage" description="The project usage graph shows both the number of users and the number of requests for any given date or range of dates. It can also be expanded for a more focused and in-depth visualisation." href="/opendialog-platform/monitoring-your-application#project-usage" />
- <LinkCard title="Interaction logs" description="The interaction logs are listed and filtered by date, with the most recent appearing at the top. Each interaction log can be expanded to review specific conversations." href="/opendialog-platform/monitoring-your-application#interaction-logs" />
- <LinkCard title="Message log table" description="The message logs are listed and filtered by date, with the most recent appearing at the top. Messages can also be filtered by Conversation, Scene, Turn and Intent to find specific results." href="/opendialog-platform/monitoring-your-application#message-table" />
+ <CoverCard title="Project usage" description="The project usage graph shows both the number of users and the number of requests for any given date or range of dates. It can also be expanded for a more focused and in-depth visualisation." href="/opendialog-platform/monitoring-your-application#project-usage" cover="/src/assets/screenshot-2024-09-26-at-10-32-32.png" />
+ <CoverCard title="Interaction logs" description="The interaction logs are listed and filtered by date, with the most recent appearing at the top. Each interaction log can be expanded to review specific conversations." href="/opendialog-platform/monitoring-your-application#interaction-logs" cover="/src/assets/screenshot-2024-10-01-at-15-28-40.png" />
+ <CoverCard title="Message log table" description="The message logs are listed and filtered by date, with the most recent appearing at the top. Messages can also be filtered by Conversation, Scene, Turn and Intent to find specific results." href="/opendialog-platform/monitoring-your-application#message-table" cover="/src/assets/screenshot-2024-09-26-at-10-38-51.png" />
</CardGrid>
## **How to use**
@@ -80,7 +81,7 @@ Analyse has three main components: project usage, interaction logs, and message
The project usage functionality allows you to visualise project usage trends over time.
-
+
*Expanded view of project use over the course of a week*
@@ -96,7 +97,7 @@ The list of interaction logs allow you to visualise a list of conversations had
In addition, you can use the date picker on the top of the screen to select conversations for a specific date range, or search the interaction log for a specific user-ID thanks to the user-ID search field in the top right corner.
-
+
*List of interaction logs*
@@ -112,7 +113,7 @@ You can click through each item in the interaction log list to visualise its det
### Message log table
-
+
*List of message logs*
@@ -176,7 +177,7 @@ Displays the actual content of the message, either from the user or the system.
#### **Filtering Messages**
-
+
*By using the breadcrumb filter, you can narrow down you search by conversation, scene, turn and intent*
@@ -210,7 +211,7 @@ The detailed conversational logs for each item in the interaction logs are compo
* The conversational flow visualisation
* The conversational logic logs
-
+
*Detailed conversation log, including user information, conversational history, conversational flow visualization, and conversational logic.*
diff --git a/src/content/docs/opendialog-platform/previewing-your-application/index.md b/src/content/docs/opendialog-platform/previewing-your-application/index.md
index 395d264..2fbe889 100644
--- a/src/content/docs/opendialog-platform/previewing-your-application/index.md
+++ b/src/content/docs/opendialog-platform/previewing-your-application/index.md
@@ -4,7 +4,7 @@ title: Previewing your application
Within OpenDialog you can preview any Webchat application so you can test and validate the conversational experience before deploying your application.
-
+
*Default conversation design view*
@@ -12,7 +12,7 @@ In the sidebar, hover on Test and click on Preview to interact with the preview
### Functionality
-.jpg>)
+
*Preview screen*
@@ -34,11 +34,11 @@ The preview console panel includes:
When clicking in the Considered Path, a larger version of the considered path is displayed, and an option to view the selected path (circles with green border), the non-selected paths (circles with red border) and an explanation for both selected and rejected paths.
-
+
*Considered Path*
-
+
*Selected Path*
@@ -59,6 +59,6 @@ To test this within the preview, for a returning user, we would type in `seconds
* **Search & Filter:** Easily search for attributes or their values within the context.
* **Attribute Details:** Hover over any attribute to view detailed information.
-
+
Note: in general no further action needs to be taken to set the custom attribute. Specifically for `seconds_since_last_seen` we need to refresh the whole page. Do not click Refresh Scenario as this resets the entire context, including the value we just defined.
diff --git a/src/content/docs/opendialog-platform/translating-your-application/index.md b/src/content/docs/opendialog-platform/translating-your-application/index.md
index 20a0337..b7c3f0d 100644
--- a/src/content/docs/opendialog-platform/translating-your-application/index.md
+++ b/src/content/docs/opendialog-platform/translating-your-application/index.md
@@ -9,7 +9,7 @@ OpenDialog Translate is currently in Alpha release. If translation is something
This section outlines how to translate your conversational application's content and how to update your conversational application accordingly.
-
+
*OpenDialog Translate lets you auto-translate and share your content strings as a spreadsheet with your translators.*
@@ -45,7 +45,7 @@ By viewing the number of missing strings for each language, you get a clear unde
Translate allows you to manage your content for multilingual use in your conversational application. In addition, the Translate feature provides a Multilingual Dashboard to manage translation workflows and status. It is, therefore, a separate section in the scenario menu.
-
+
*The Translate dashboard can be accessed via the main scenario menu.*
@@ -63,7 +63,7 @@ If you are familiar with Translate, you can also directly start using the Transl
* Click on the three-dotted menu in the Scenario Card
* Start the translation process by selecting 'Export for translation'
-
+
*Export your content strings for translation directly from the Scenario Overview page*
@@ -91,7 +91,7 @@ A <mark style="color:purple;">**target language**</mark> is one of the languages
You first need to export your original content for translation. The content will be exported to a .csv file and sent to the email address you use to log in to OpenDialog.
-
+
*Use the 'Export scenario' button to start the Translate process.*
@@ -105,7 +105,7 @@ The export modal has a checkbox that allows you to activate auto-translate for y
The auto-translate service will add an automatic translation of all your content strings to the exported file.
-
+
*The export scenario for translation modal allows you to activate an automated translation service.*
@@ -115,7 +115,7 @@ When you are happy with your choices, you can confirm your export by clicking th
Head on over to your email inbox, where you will find the exported .csv file. You can find an example of what this looks like below.
-
+
*.csv file after export*
@@ -141,7 +141,7 @@ The Translate dashboard provides an understanding, at a glance, of the completen
This is indicated in the language cards by the ratio of translated items to translatable items, the percentage ratio and the color of the progress bar.
-
+
*The language cards in the 'Your translations' sections reflect the status of the completeness of your translations.*
@@ -151,11 +151,11 @@ Once you have imported your translation files, you can start testing your conver
To do so, expand the Test section in the main scenario menu, and select Preview. You will notice that a drop down is now available at the top of the Preview screen, allowing you to select the language you wish to test the bot in.
-
+
*Preview set to English for this scenario by default*
-
+
*The same scenario with Preview set to French*
diff --git a/src/content/docs/opendialog-platform/troubleshooting-and-common-problems/index.md b/src/content/docs/opendialog-platform/troubleshooting-and-common-problems/index.md
index ac0cd64..f8f07bd 100644
--- a/src/content/docs/opendialog-platform/troubleshooting-and-common-problems/index.md
+++ b/src/content/docs/opendialog-platform/troubleshooting-and-common-problems/index.md
@@ -4,7 +4,7 @@ title: Troubleshooting and Common Problems
Q: I get a "check your behavior" error in the player
-
+
A: Check that you don't have two of the same type of intents following one another, e.g. an app intent followed by an app intent.
@@ -12,7 +12,7 @@ Check that your components have the correct behavior, e.g. starting and open beh
Q: I created my intent in the conversation designer but I can't find it when I'm in a button block.
-
+
A: Check that you defined the intent as a user intent. App intents won't show up since the button requires a user intent.
@@ -28,6 +28,6 @@ U: Confirm \[user clicks confirm. The system moves to the user intent that is in
A: Ok, great.... \[from the user intent, the system moves to the next app intent through the typical mechanisms (e.g. intent in same turn, transition, ...).
-
+
*Details of the button block and selection of user intent for each button*
diff --git a/src/content/docs/release-notes/release-notes/index.mdx b/src/content/docs/release-notes/release-notes/index.mdx
index 3202947..77ec894 100644
--- a/src/content/docs/release-notes/release-notes/index.mdx
+++ b/src/content/docs/release-notes/release-notes/index.mdx
@@ -4,7 +4,6 @@ description: Learn about our product's newest updates and enhancements that will
---
import { LinkCard } from '@astrojs/starlight/components';
-import Embed from '~/components/Embed.astro';
## August 2026
@@ -145,13 +144,13 @@ We've updated our internal authentication mechanism. You can now create more tha
For more information, see our [Public APIs documentation](/developing-with-opendialog/public-apis).
-.png>)
+
#### <mark style={{ color: 'purple' }}>Expandable messages for better user experience</mark>
Introducing expandable messages in webchat! You can now configure text messages to display with an "See more.." option, allowing users to see a preview initially and then expand to read the full content when needed. This is particularly useful for longer messages, helping keep your chat interface clean while still providing access to detailed information when users need it.
-
+
For more information, see our [Text Message](/opendialog-platform/conversation-designer/message-design/message-types/text-message) page.
@@ -164,7 +163,7 @@ We've significantly enhanced our webhook action security with new authentication
These improvements give you more control over how OpenDialog securely communicates with your external services.
-
+
Check our [documentation on attribute filters](/core-concepts/contexts-and-attributes/attribute-filters) for newly available filters.
@@ -188,7 +187,7 @@ Small note that you can use any type of file with Gemini. For Claude and OpenAI
In addition, we've added nice UI to our testing panel to make file upload experience even more smoother.
-.png>)
+
Note: For file upload in LLM actions, contact us at [hello@opendialog.ai](mailto:hello@opendialog.ai) to enable this feature on demand.
@@ -207,9 +206,9 @@ This new release includes numerous technical improvements to ensure OpenDialog o
<div>
-.png>)
+
-
+
</div>
@@ -233,9 +232,9 @@ Read more in [our docs here](/developing-with-opendialog/public-apis/knowledge-s
<div>
-
+
-.png>)
+
</div>
@@ -254,7 +253,7 @@ For more details - check out [our documentation](/tutorials/use-knowledge-source
#### <mark style={{ color: 'purple' }}>New webhook action</mark>
-.png>)
+
#### New Features and Updates
@@ -304,7 +303,7 @@ For more information, look at [our documentation here](/core-concepts/the-opendi
We now have a brand new security tab for webchat interface settings which allows you to fine-tune your security requirements to validate anonymous access to the webchat, CSRF settings and specify authorized domains from which webchat should be accessible.
-.png>)
+
#### <mark style={{ color: 'purple' }}>Whatsapp and SMS integration</mark>
@@ -318,11 +317,11 @@ _Note_: currently this feature is available on-demand, so if you want to try it
<div align="left">
-.png>)
+
-.png>)
+
-.png>)
+
</div>
@@ -369,7 +368,7 @@ We made our scenario visualizer in preview and analyse a bit more convenient and
* More information about run actions;
* Actions and conditions are now clickable and take you to where they are defined
- (1).png>)
+
#### <mark style={{ color: 'purple' }}>Improvements</mark>
@@ -389,15 +388,15 @@ We made our scenario visualizer in preview and analyse a bit more convenient and
To enhance clarity regarding conditions and actions tied to specific intent within Conversation Designer, we are rolling out an update that will visibly mark intent cards when they contain associated action or condition. Additionally, we've incorporated straightforward edit links directly on the interface of each intent card for immediate access to thisi elements:
- (4).png>)
+
- (5).png>)
+
#### <mark style={{ color: 'purple' }}>Security updates</mark>
This release includes several important security updates. One of them being a stricter password policy. If your current password does not meet new strength criteria, upon next login you'll be prompted to reset it in accordance with these updated guidelines:
- (4).png>)
+
#### <mark style={{ color: 'purple' }}>Improvements</mark>
@@ -415,7 +414,7 @@ This release includes several important security updates. One of them being a st
The first update for this month is a new sidebar item "Tutorials" featuring various how-to guides. We've added this enhancement to improve your learning experience, allowing you to access our learning videos, documentation links, and additional resources all in one convenient place.
-.png>)
+
#### <mark style={{ color: 'purple' }}>API for pre-populating user context for full-page webchat</mark>
@@ -444,7 +443,7 @@ Setting custom attributes to test specific paths of your conversation has also b
For more information, please [see the docs](/opendialog-platform/previewing-your-application).
-.png>)
+
#### <mark style={{ color: 'purple' }}>Improvements</mark>
@@ -477,7 +476,7 @@ We are wrapping up this year with some user experience improvements and clearing
We are delighted to present a tracker for your vectorisation usage restrictions. Each Topic page now features a progress bar that shows the number of jobs currently in progress and updates each time you add new items to the queue until you reach the quota. This should help you better understand how many jobs you can have per topic at any given time.
- (1).png>)
+
*Capacity tracker for vectorisation quotas*
@@ -498,7 +497,7 @@ Does it sometimes feel like it takes ages for the AI Agent to reply and you are
**Introducing...OpenDialog's interactive wait time indicator.**
-.gif>)
+
*OpenDialog's interactive wait time indicator*
@@ -626,7 +625,7 @@ We've been busy tidying up our product and making a lot of improvements and bug
* Allow free input for standart autocomplete
* Support for cancel functionality for different message types
-And much more :tada:
+And much more 🎉
## June 2024
@@ -636,7 +635,7 @@ And much more :tada:
* Added [new location attribute](https://docs.opendialog.ai/core-concepts/contexts-and-attributes/about-attributes#location-attribute)
* Added support for GPT-4o model
-Plus various bugfixes and improvements :tada:
+Plus various bugfixes and improvements 🎉
## May 2024
@@ -720,7 +719,11 @@ Notable updates:
## December 2023 - Proxima
-<Embed url="https://youtu.be/KTIIq9DsEbc?si=5JJLEcE9F6xIdZWE" />
+<figure className="od-embed">
+<div className="od-embed-frame">
+<iframe src="https://www.youtube-nocookie.com/embed/KTIIq9DsEbc" title="Embedded video" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+</figure>
#### <mark style={{ color: 'purple' }}>New Features</mark>
diff --git a/src/content/docs/tutorials/add-a-new-topic-of-discussion/index.mdx b/src/content/docs/tutorials/add-a-new-topic-of-discussion/index.md
similarity index 94%
rename from src/content/docs/tutorials/add-a-new-topic-of-discussion/index.mdx
rename to src/content/docs/tutorials/add-a-new-topic-of-discussion/index.md
index 791cae2..d7ff54b 100644
--- a/src/content/docs/tutorials/add-a-new-topic-of-discussion/index.mdx
+++ b/src/content/docs/tutorials/add-a-new-topic-of-discussion/index.md
@@ -3,9 +3,6 @@ title: Adding a new topic of discussion
description: Let's expand your AI Agent's capabilities by introducing a new topic of discussion.
---
-import Embed from '~/components/Embed.astro';
-
-
## Introduction
Adding new topics of discussion allows your AI agent to answer questions and engage in conversations beyond the initial scope, creating a more dynamic and comprehensive user experience. Let’s walk through the process of adding a new topic to your AI agent.
@@ -18,11 +15,16 @@ So that an AI Agent can correctly handle a new topic of discussion, we must make
* Contextualise the user query & advance the conversation process : this happens via the Conversation Design
* Generate a relevant response, statically or dynamically based on a knowledge source: this happens through a combination of a RAG service, LLM Actions and Message Design.
-
+
## **See it in action**
-<Embed url="https://youtu.be/v6wBulsRa4o" title="Tutorial video on how to add a new topic of discussion" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.youtube-nocookie.com/embed/v6wBulsRa4o" title="Tutorial video on how to add a new topic of discussion" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+<figcaption>Tutorial video on how to add a new topic of discussion</figcaption>
+</figure>
## **Step-by-step guide**
@@ -84,7 +86,7 @@ With the new intent in place in the semantic classifier, it’s time to set up h
Now is a good time to explore the OpenDialog conversation engine model in a bit more detail.
-
+
*Breakdown of the OpenDialog model*
@@ -146,21 +148,21 @@ Now let’s look at how to add an additional topic to your free-from conversatio
To set up your new topic of discussion, we are going to use this pre-existing scene as a template and copy it. Now, let’s duplicate this topic’s scene to create a base for your new topic, for example “AboutCompany”.
-
+
*Duplicating a scene.*
We are now going to customise the duplicated scene to match your new topic of discussion. This customization ensures the AI Agent responds in context, providing relevant answers to questions about the company.
-.png>)
+
Navigating downward in the architecture of your AI Agent, you will also need to update the name and description settings for your turn, so they reflect that these are related to your new topic of discussion.
-.png>)
+
Once the turn level is edited, it is now time to update the intent for your new topic of discussion. This is where the rubber hits the road as we need to ensure the conversation design matches up with the semantic classification. You do this by updating the language service intent that the interpreter references in the intent settings panel of your conversation design. This will allow the AI Agent to process and respond to queries in the desired way.
-.png>)
+
#### **Responding to a user query : Message Design**
diff --git a/src/content/docs/tutorials/adding-a-structured-conversation/index.mdx b/src/content/docs/tutorials/adding-a-structured-conversation/index.md
similarity index 96%
rename from src/content/docs/tutorials/adding-a-structured-conversation/index.mdx
rename to src/content/docs/tutorials/adding-a-structured-conversation/index.md
index 6d79f7a..c47642f 100644
--- a/src/content/docs/tutorials/adding-a-structured-conversation/index.mdx
+++ b/src/content/docs/tutorials/adding-a-structured-conversation/index.md
@@ -3,9 +3,6 @@ title: Adding a structured conversation
description: Let's add a structured conversation flow to your AI Agent.
---
-import Embed from '~/components/Embed.astro';
-
-
Now that your AI Agent has become proficient at handling different topics of discussion, let's see how we can add a more structured type of conversation in the mix.
:::note
@@ -26,7 +23,12 @@ To do this, we will need to :
-<Embed url="https://youtu.be/ZA7xgNQDYGk" title="Add a structured conversation thanks to OpenDialog's unique model" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.youtube-nocookie.com/embed/ZA7xgNQDYGk" title="Add a structured conversation thanks to OpenDialog's unique model" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+<figcaption>Add a structured conversation thanks to OpenDialog's unique model</figcaption>
+</figure>
## Step-by-step guide
@@ -85,7 +87,7 @@ A scene for a process conversation contains the following components:
* The expected user requests - represented in respective **response turns** each - led by primary USER intents
* Supporting turns - led by secondary USER intents (including Help, TalktoHuman, NoMatch, etc.)
-.png>)
+
*A template scene with it's different turn components*
@@ -256,4 +258,4 @@ Wait a minute! Now that the process is in place, we still need to link it up to
That's it - your are all set. Now, when the BookAppointment topic will be matched through semantic classification, the AI Agent will transition to the BookAppointment process rather than providing a one-off response.
-<br />
+<br>
diff --git a/src/content/docs/tutorials/ai-agent-creation-overview/index.mdx b/src/content/docs/tutorials/ai-agent-creation-overview/index.mdx
index 3288a3e..cc7394c 100644
--- a/src/content/docs/tutorials/ai-agent-creation-overview/index.mdx
+++ b/src/content/docs/tutorials/ai-agent-creation-overview/index.mdx
@@ -4,7 +4,6 @@ description: Learn how to create a fully functional AI Agent including semantic
---
import { Steps } from '@astrojs/starlight/components';
-import Embed from '~/components/Embed.astro';
Follow the steps in the video tutorials below to create your AI Agent one step at a time, or click the links to read through the detailed instructions of each section.
@@ -17,7 +16,12 @@ Follow the steps in the video tutorials below to create your AI Agent one step a
- <Embed url="https://youtu.be/RhUc_mgkNl8?si=KoR5D0KO6rPIJ2LL" title="Get started with a Quickstart AI Agent" />
+ <figure className="od-embed">
+ <div className="od-embed-frame">
+ <iframe src="https://www.youtube-nocookie.com/embed/RhUc_mgkNl8" title="Get started with a Quickstart AI Agent" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+ </div>
+ <figcaption>Get started with a Quickstart AI Agent</figcaption>
+ </figure>
2. ### [Add a new topic of discussion](/tutorials/add-a-new-topic-of-discussion)
@@ -26,7 +30,12 @@ Follow the steps in the video tutorials below to create your AI Agent one step a
- <Embed url="https://youtu.be/v6wBulsRa4o?si=y75reHmgUXuX-ZEV" title="Add a new topic of discussion" />
+ <figure className="od-embed">
+ <div className="od-embed-frame">
+ <iframe src="https://www.youtube-nocookie.com/embed/v6wBulsRa4o" title="Add a new topic of discussion" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+ </div>
+ <figcaption>Add a new topic of discussion</figcaption>
+ </figure>
3. ### [Add & use knowledge sources via RAG](/tutorials/use-knowledge-sources-via-rag)
@@ -35,7 +44,12 @@ Follow the steps in the video tutorials below to create your AI Agent one step a
- <Embed url="https://youtu.be/EwM5A6QNEFA" title="Add a knowledge source & use it in your conversation design" />
+ <figure className="od-embed">
+ <div className="od-embed-frame">
+ <iframe src="https://www.youtube-nocookie.com/embed/EwM5A6QNEFA" title="Add a knowledge source & use it in your conversation design" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+ </div>
+ <figcaption>Add a knowledge source & use it in your conversation design</figcaption>
+ </figure>
4. ### [Add a structured process conversation](/getting-started-1/quick-start-ai-agents/a-process-handling-ai-agent)
@@ -44,7 +58,12 @@ Follow the steps in the video tutorials below to create your AI Agent one step a
- <Embed url="https://youtu.be/ZA7xgNQDYGk" title="Easily add a structured conversation thanks to OpenDialog's scalable model." />
+ <figure className="od-embed">
+ <div className="od-embed-frame">
+ <iframe src="https://www.youtube-nocookie.com/embed/ZA7xgNQDYGk" title="Easily add a structured conversation thanks to OpenDialog's scalable model." loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+ </div>
+ <figcaption>Easily add a structured conversation thanks to OpenDialog's scalable model.</figcaption>
+ </figure>
5. ### [Add a 3rd party integration](/tutorials/integrate)
@@ -53,7 +72,12 @@ Follow the steps in the video tutorials below to create your AI Agent one step a
- <Embed url="https://youtu.be/aseZ5oHG1IQ" title="Add a 3rd party integration" />
+ <figure className="od-embed">
+ <div className="od-embed-frame">
+ <iframe src="https://www.youtube-nocookie.com/embed/aseZ5oHG1IQ" title="Add a 3rd party integration" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+ </div>
+ <figcaption>Add a 3rd party integration</figcaption>
+ </figure>
6. ### [Test and tweak your AI agent](/tutorials/test-and-tweak-your-ai-agent)
@@ -62,7 +86,12 @@ Follow the steps in the video tutorials below to create your AI Agent one step a
- <Embed url="https://youtu.be/OP8V9e3K3u8" title="Follow along to go through the different steps to debug your AI Agent's experience" />
+ <figure className="od-embed">
+ <div className="od-embed-frame">
+ <iframe src="https://www.youtube-nocookie.com/embed/OP8V9e3K3u8" title="Follow along to go through the different steps to debug your AI Agent's experience" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+ </div>
+ <figcaption>Follow along to go through the different steps to debug your AI Agent's experience</figcaption>
+ </figure>
7. ### [Publish your AI agent](/tutorials/publish-your-ai-agent)
@@ -71,6 +100,11 @@ Follow the steps in the video tutorials below to create your AI Agent one step a
- <Embed url="https://youtu.be/CnL88dIvqQE?si=MFun5aJuUWU5ozqr" title="Publish your AI Agent walkthrough" />
+ <figure className="od-embed">
+ <div className="od-embed-frame">
+ <iframe src="https://www.youtube-nocookie.com/embed/CnL88dIvqQE" title="Publish your AI Agent walkthrough" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+ </div>
+ <figcaption>Publish your AI Agent walkthrough</figcaption>
+ </figure>
</Steps>
diff --git a/src/content/docs/tutorials/integrate/index.mdx b/src/content/docs/tutorials/integrate/index.md
similarity index 91%
rename from src/content/docs/tutorials/integrate/index.mdx
rename to src/content/docs/tutorials/integrate/index.md
index 4e7396e..a72226d 100644
--- a/src/content/docs/tutorials/integrate/index.mdx
+++ b/src/content/docs/tutorials/integrate/index.md
@@ -3,9 +3,6 @@ title: Add a 3rd party integration
description: Let's enhance your AI Agent with access to 3rd party data.
---
-import Embed from '~/components/Embed.astro';
-
-
## Introduction
Throughout the course of a conversation, we may want to communicate with systems outside of OpenDialog to send or receive data. This may be as simple as a "ping" to a URL representing a milestone in the user's journey, or an integration with an external data source which takes some input data from the conversation, and outputs some new data to return to the conversation.
@@ -32,7 +29,12 @@ For some more details around the data structures you can use please see the [Int
-<Embed url="https://youtu.be/aseZ5oHG1IQ?si=nn7YIbOVNQJdDiZr" title="A step by step guide to add an integration between OpenDialog and a 3rd party application" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.youtube-nocookie.com/embed/aseZ5oHG1IQ" title="A step by step guide to add an integration between OpenDialog and a 3rd party application" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+<figcaption>A step by step guide to add an integration between OpenDialog and a 3rd party application</figcaption>
+</figure>
## Step by step guide
@@ -48,7 +50,7 @@ Once you have a service that provides the desired functionality, it's time to cr
* Click on Create a new webhook integration
:::
-
+
*Navigate to the webhook action screen*
@@ -69,7 +71,7 @@ _For this tutorial, we will be using a mock webhook example, available through P
`https://af7df53c-9871-40de-a454-31d5cf2d6237.mock.pstmn.io/your-webhook-endpoint`
:::
-.png>)
+
*A webhook action*
@@ -86,7 +88,7 @@ Now, we can set up the input and output attributes we want to send and retrieve
For more information on attributes, check out the documentation on attributes [here](/core-concepts/contexts-and-attributes/about-attributes).
-.png>)
+
*Adding attributes to your action*
@@ -126,7 +128,7 @@ Using the examples as listed in the instructions - the action we have set up wil
Now, we can test our action by providing values against the input attributes, and check the result the webhook action comes back with.
-.png>)
+
*Testing a webhook action*
@@ -175,7 +177,7 @@ To execute the action at a particular moment in the conversation, we need to add
With your action set up and your intent selected, let's set them up to work together!
-
+
*Adding an action to an intent*
@@ -204,13 +206,13 @@ You can use the value of output attributes from your action in your messages, to
* Click the Edit icon on the message card
* Locate the text block
* Locate the place in your message where you want to add the information from output attribute
-* Type an opening curly brace \{ to access the attribute autocomplete field
+* Type an opening curly brace { to access the attribute autocomplete field
* Start typing the name of your output attribute, for example full\_name
* Select the desired attribute from the dropdown, in our case: full\_name
* Scroll back up to the top of the page
* Click “Save Message”
:::
-.png>)
+
You have now succesfullly added an integration to your scenario, and used it's output in your messages!
diff --git a/src/content/docs/tutorials/publish-your-ai-agent/index.mdx b/src/content/docs/tutorials/publish-your-ai-agent/index.md
similarity index 91%
rename from src/content/docs/tutorials/publish-your-ai-agent/index.mdx
rename to src/content/docs/tutorials/publish-your-ai-agent/index.md
index 2ab4e10..90b83f8 100644
--- a/src/content/docs/tutorials/publish-your-ai-agent/index.mdx
+++ b/src/content/docs/tutorials/publish-your-ai-agent/index.md
@@ -3,9 +3,6 @@ title: Publish your AI Agent
description: Ready to launch your AI Agent?
---
-import Embed from '~/components/Embed.astro';
-
-
## Introduction
Now that you’ve built and refined your AI agent, it’s time to publish it on your website and let it engage with your users. OpenDialog makes this a simple two-step process using aliases, allowing you to easily manage and update your webchat without needing to change the underlying code.
@@ -18,7 +15,12 @@ In OpenDialog, an alias acts as a reference point for your WebChat widget. This
## See it in action
-<Embed url="https://youtu.be/CnL88dIvqQE?si=HXxwZWjhCD8RHY_b" title="Publishing an AI Agent" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.youtube-nocookie.com/embed/CnL88dIvqQE" title="Publishing an AI Agent" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+<figcaption>Publishing an AI Agent</figcaption>
+</figure>
@@ -35,7 +37,7 @@ In OpenDialog, an alias acts as a reference point for your WebChat widget. This
* Click on ‘Create new alias’
:::
-
+
*Create a new alias by giving it a name and attributing a scenario*
diff --git a/src/content/docs/tutorials/test-and-tweak-your-ai-agent/index.mdx b/src/content/docs/tutorials/test-and-tweak-your-ai-agent/index.md
similarity index 95%
rename from src/content/docs/tutorials/test-and-tweak-your-ai-agent/index.mdx
rename to src/content/docs/tutorials/test-and-tweak-your-ai-agent/index.md
index 9761520..0b4a0a0 100644
--- a/src/content/docs/tutorials/test-and-tweak-your-ai-agent/index.mdx
+++ b/src/content/docs/tutorials/test-and-tweak-your-ai-agent/index.md
@@ -3,9 +3,6 @@ title: Test and tweak your AI Agent
description: Your AI Agent is almost ready to launch! Before you publish it, let’s make sure it’s optimised for the best user experience.
---
-import Embed from '~/components/Embed.astro';
-
-
## Introduction
While building out your AI agent, you have set up a number of components along the way that all contribute to it's success.
@@ -21,7 +18,12 @@ There are a few types of tests that you will want to run before launching your A
## See it in action
-<Embed url="https://youtu.be/OP8V9e3K3u8" title="Follow along to debug your AI Agent, step by step" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.youtube-nocookie.com/embed/OP8V9e3K3u8" title="Follow along to debug your AI Agent, step by step" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+<figcaption>Follow along to debug your AI Agent, step by step</figcaption>
+</figure>
## Step-by-step guide
@@ -38,7 +40,7 @@ In order to gain systematic improvements through quality assurance testing, ther
#### Example structure of a test sheet:
-
+
*Example of the setup of an AI Agent test sheet*
@@ -54,7 +56,7 @@ First and foremost, you will want to test your AI Agent as a whole in an experie
* View your AI Agent loading in the bottom left-hand corner of the central panel of your screen.
:::
-
+
*Preview your AI Agent and visualise it's interactions in real time*
@@ -70,7 +72,7 @@ Here is a quick overview of some of the primary issues you could encounter:
### **No-match**
-
+
*No classified intent got matched, and therefor the NoMatch intent gets triggered*
@@ -130,7 +132,7 @@ Once you have identified the issue with the semantic classification, you can sta
### **No messages found with passing conditions**
-
+
*A conversation that has a failing message due to conditions*
diff --git a/src/content/docs/tutorials/use-knowledge-sources-via-rag/index.mdx b/src/content/docs/tutorials/use-knowledge-sources-via-rag/index.md
similarity index 92%
rename from src/content/docs/tutorials/use-knowledge-sources-via-rag/index.mdx
rename to src/content/docs/tutorials/use-knowledge-sources-via-rag/index.md
index d83e2a5..a3434e8 100644
--- a/src/content/docs/tutorials/use-knowledge-sources-via-rag/index.mdx
+++ b/src/content/docs/tutorials/use-knowledge-sources-via-rag/index.md
@@ -3,9 +3,6 @@ title: Use knowledge sources via RAG
description: Let's enhance your AI Agent's knowledge with Retrieval Augmented Generation.
---
-import Embed from '~/components/Embed.astro';
-
-
## Introduction
Now, we obviously want our AI Agent to provide more relevant and precise information to our users than just the static response you provided as an example.
@@ -17,17 +14,22 @@ If you want to use dynamic responses, you will need to take a few additional ste
* Indicate to the AI Agent when to generate the response by referencing the LLM action on the correct response intent
* Adapt the AI Agent’s message to use the generated content by referencing the LLM action through an attribute in the message editor.
-
+
*From RAG to responses*
## **See it in action**
-<Embed url="https://youtu.be/EwM5A6QNEFA?si=P2rDWvVacyWi835k" title="Follow this video to add and use a knowledge source for RAG" />
+<figure class="od-embed">
+<div class="od-embed-frame">
+<iframe src="https://www.youtube-nocookie.com/embed/EwM5A6QNEFA" title="Follow this video to add and use a knowledge source for RAG" loading="lazy" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>
+<figcaption>Follow this video to add and use a knowledge source for RAG</figcaption>
+</figure>
## **Step by step guide**
-
+
*Overview of adding and using a knowledge service*
@@ -56,7 +58,7 @@ OpenDialog provides the ability to choose from multiple source types depending o
* Document: Upload relevant documents.
* Text: Manually enter text as a knowledge source.
-.png>)
+
*Creating a vector topic*
@@ -66,7 +68,7 @@ OpenDialog provides the ability to choose from multiple source types depending o
> Static topics are ideal when the AI Agent needs access to the **entire, unmodified document**, such as schemas (XSD/JSON), API specifications, or configuration templates.
-.png>)
+
*Creating a static topic*
@@ -169,7 +171,7 @@ In order to use your new knowledge source in a response, you will need to accomp
Once in the LLM Actions overview, you’ll see prebuilt actions like “Topic Response Generator”, for example, which were automatically created to generate responses for your primary topic. We will be using this LLM action as a basis for our new LLM Action.
-Let’s have a look at what this “Topic Response Generator” LLM action looks like.<br />
+Let’s have a look at what this “Topic Response Generator” LLM action looks like.<br>
:::tip
**View a pre-existing LLM Action**
@@ -184,15 +186,15 @@ An LLM action is made up of 3 main components:
2 - the **prompt configuration** that provides the LLM with instructions, under the prompt configuration tab, and further settings that allow you to determine how the LLM response will be referenced thanks to output attributes.
-3 - **guardrails** to constrain the LLM responses and configure their safety settings, under the safeguarding tab.<br />
+3 - **guardrails** to constrain the LLM responses and configure their safety settings, under the safeguarding tab.<br>
In this initial guide, we are not going to dig any deeper into the preconfigured prompt configuration just yet. All you need to remember for now is that:
* A knowledge source gets referenced in prompt instructions using a knowledge string
* The knowledge string is used in the prompt instructions in a specific knowledge sections, indicated as follows: \<knowledge>
-* The LLM response that comes back when the action is run is saved in OpenDialog under an output attribute which by default is the \{llm\_response\} attribute
+* The LLM response that comes back when the action is run is saved in OpenDialog under an output attribute which by default is the {llm\_response} attribute
-For more information on how to structure prompt instructions for LLM Actions, you can take [a look at our further documentation](/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions).<br />
+For more information on how to structure prompt instructions for LLM Actions, you can take [a look at our further documentation](/opendialog-platform/interpreters-and-natural-language-understanding/llm-actions).<br>
For this initial setup, we will use the same configuration as the ‘Topic Response Generation’ LLM Action.
@@ -208,7 +210,7 @@ For this initial setup, we will use the same configuration as the ‘Topic Respo
Now let’s taylor our new LLM action and provide it with instructions to reference our newly setup knowledge source.
-👉🏻 You will also need the knowledge string you put aside earlier.<br />
+👉🏻 You will also need the knowledge string you put aside earlier.<br>
:::tip
**Editing an LLM Action**
@@ -221,7 +223,7 @@ Now let’s taylor our new LLM action and provide it with instructions to refere
_(\*) The same configuration of the LLM Action you have duplicated will apply. When selecting the OpenAI engine, the correct configuration will already be selected. You can use an OpenDialog-managed account, or use your own account credentials._
-Now, we are going to update the prompt instructions in order to adapt to the additional knowledge source you have just added. <br />
+Now, we are going to update the prompt instructions in order to adapt to the additional knowledge source you have just added. <br>
:::tip
**Updating prompt instructions**
@@ -262,7 +264,7 @@ You are all set! When your scenario matches this intent, your LLM prompts will b
### **Adapting the message: the LLM response attribute**
-To display the LLM's response text in your scenario, we will need to update its message in the message editor, to reference the \{llm\_response\} attribute. Remember, this is the attribute where the LLM’s response generated by your LLM action gets stored in OpenDialog.
+To display the LLM's response text in your scenario, we will need to update its message in the message editor, to reference the {llm\_response} attribute. Remember, this is the attribute where the LLM’s response generated by your LLM action gets stored in OpenDialog.
:::tip
**Updating your message to use the dynamically generated response**
@@ -272,7 +274,7 @@ To display the LLM's response text in your scenario, we will need to update its
* Click the Edit icon on the message card
* Locate the text block
* Delete the static message in the text block
-* Type an opening curly brace \{ to access the attribute autocomplete field
+* Type an opening curly brace { to access the attribute autocomplete field
* Start typing llm…
* Select the desired attribute from the dropdown, in our case: llm\_response
* Scroll back up to the top of the page
@@ -285,4 +287,4 @@ Your new knowledge source is now ready, and the AI Agent is set to generate info
Your additional topic is now live! With these steps, you can empower your AI Agent to handle a wider range of user questions while maintaining a smooth, relevant conversation flow. To add more additional topics, go back to the top of this guide, rinse and repeat!
-<br />
+<br>
diff --git a/src/sidebar.generated.mjs b/src/sidebar.generated.mjs
index 3285ebb..7dca877 100644
--- a/src/sidebar.generated.mjs
+++ b/src/sidebar.generated.mjs
@@ -17,6 +17,7 @@ export default [
},
{
"label": "Quick Start AI Agents",
+ "collapsed": true,
"items": [
{
"label": "Quick Start AI Agents",
@@ -28,6 +29,7 @@ export default [
},
{
"label": "The \"Start from Scratch\" AI Agent",
+ "collapsed": true,
"items": [
{
"label": "The \"Start from Scratch\" AI Agent",
@@ -105,6 +107,7 @@ export default [
"items": [
{
"label": "OpenDialog Approach",
+ "collapsed": true,
"items": [
{
"label": "OpenDialog Approach",
@@ -118,6 +121,7 @@ export default [
},
{
"label": "OpenDialog Platform",
+ "collapsed": true,
"items": [
{
"label": "OpenDialog Platform",
@@ -125,6 +129,7 @@ export default [
},
{
"label": "Scenarios",
+ "collapsed": true,
"items": [
{
"label": "Scenarios",
@@ -150,6 +155,7 @@ export default [
},
{
"label": "OpenDialog Account Management",
+ "collapsed": true,
"items": [
{
"label": "OpenDialog Account Management",
@@ -177,6 +183,7 @@ export default [
},
{
"label": "Contexts and attributes",
+ "collapsed": true,
"items": [
{
"label": "Contexts and attributes",
@@ -219,6 +226,7 @@ export default [
"items": [
{
"label": "Designing your application",
+ "collapsed": true,
"items": [
{
"label": "Designing your application",
@@ -226,6 +234,7 @@ export default [
},
{
"label": "Conversation Design",
+ "collapsed": true,
"items": [
{
"label": "Conversation Design",
@@ -233,6 +242,7 @@ export default [
},
{
"label": "Conversational Patterns",
+ "collapsed": true,
"items": [
{
"label": "Conversational Patterns",
@@ -244,6 +254,7 @@ export default [
},
{
"label": "Building robust assistants",
+ "collapsed": true,
"items": [
{
"label": "Building robust assistants",
@@ -273,6 +284,7 @@ export default [
},
{
"label": "Openings",
+ "collapsed": true,
"items": [
{
"label": "Openings",
@@ -294,6 +306,7 @@ export default [
},
{
"label": "Authentication",
+ "collapsed": true,
"items": [
{
"label": "Authentication",
@@ -315,6 +328,7 @@ export default [
},
{
"label": "Information collection",
+ "collapsed": true,
"items": [
{
"label": "Information collection",
@@ -340,6 +354,7 @@ export default [
},
{
"label": "Recommendations",
+ "collapsed": true,
"items": [
{
"label": "Recommendations",
@@ -361,6 +376,7 @@ export default [
},
{
"label": "Extended telling",
+ "collapsed": true,
"items": [
{
"label": "Extended telling",
@@ -382,6 +398,7 @@ export default [
},
{
"label": "Repair",
+ "collapsed": true,
"items": [
{
"label": "Repair",
@@ -407,6 +424,7 @@ export default [
},
{
"label": "Transfer",
+ "collapsed": true,
"items": [
{
"label": "Transfer",
@@ -428,6 +446,7 @@ export default [
},
{
"label": "Closing",
+ "collapsed": true,
"items": [
{
"label": "Closing",
@@ -455,6 +474,7 @@ export default [
},
{
"label": "Best practices ",
+ "collapsed": true,
"items": [
{
"label": "Best practices ",
@@ -474,6 +494,7 @@ export default [
},
{
"label": "User needs",
+ "collapsed": true,
"items": [
{
"label": "User needs",
@@ -519,6 +540,7 @@ export default [
},
{
"label": "The team",
+ "collapsed": true,
"items": [
{
"label": "The team",
@@ -540,6 +562,7 @@ export default [
},
{
"label": "Message Design",
+ "collapsed": true,
"items": [
{
"label": "Message Design",
@@ -575,6 +598,7 @@ export default [
},
{
"label": "Message Types",
+ "collapsed": true,
"items": [
{
"label": "Message Types",
@@ -642,6 +666,7 @@ export default [
},
{
"label": "Meta Messages",
+ "collapsed": true,
"items": [
{
"label": "Meta Messages",
@@ -667,6 +692,7 @@ export default [
},
{
"label": "Webchat Interface design",
+ "collapsed": true,
"items": [
{
"label": "Webchat Interface design",
@@ -694,6 +720,7 @@ export default [
},
{
"label": "Leveraging Generative AI",
+ "collapsed": true,
"items": [
{
"label": "Leveraging Generative AI",
@@ -701,6 +728,7 @@ export default [
},
{
"label": "Language Services",
+ "collapsed": true,
"items": [
{
"label": "Language Services",
@@ -708,6 +736,7 @@ export default [
},
{
"label": "Semantic Intent Classifier",
+ "collapsed": true,
"items": [
{
"label": "Semantic Intent Classifier",
@@ -743,6 +772,7 @@ export default [
},
{
"label": "Interpreters",
+ "collapsed": true,
"items": [
{
"label": "Interpreters",
@@ -750,6 +780,7 @@ export default [
},
{
"label": "Available interpreters",
+ "collapsed": true,
"items": [
{
"label": "Available interpreters",
@@ -769,6 +800,7 @@ export default [
},
{
"label": "Google Dialogflow",
+ "collapsed": true,
"items": [
{
"label": "Google Dialogflow",
@@ -810,6 +842,7 @@ export default [
},
{
"label": "LLM Actions",
+ "collapsed": true,
"items": [
{
"label": "LLM Actions",
@@ -841,6 +874,7 @@ export default [
},
{
"label": "3rd party Integrations in your application",
+ "collapsed": true,
"items": [
{
"label": "3rd party Integrations in your application",
@@ -848,6 +882,7 @@ export default [
},
{
"label": "Webhook action",
+ "collapsed": true,
"items": [
{
"label": "Webhook action",
@@ -863,6 +898,7 @@ export default [
},
{
"label": "[Deprecated] webhook actions",
+ "collapsed": true,
"items": [
{
"label": "[Deprecated] webhook actions",
@@ -878,6 +914,7 @@ export default [
},
{
"label": "Actions from library",
+ "collapsed": true,
"items": [
{
"label": "Actions from library",
@@ -903,6 +940,7 @@ export default [
},
{
"label": "Conversation Hand-off",
+ "collapsed": true,
"items": [
{
"label": "Conversation Hand-off",
@@ -959,6 +997,7 @@ export default [
},
{
"label": "WebChat",
+ "collapsed": true,
"items": [
{
"label": "WebChat",
@@ -986,6 +1025,7 @@ export default [
},
{
"label": "SDK",
+ "collapsed": true,
"items": [
{
"label": "SDK",
@@ -1013,6 +1053,7 @@ export default [
},
{
"label": "Public APIs",
+ "collapsed": true,
"items": [
{
"label": "Public APIs",
diff --git a/src/styles/custom.css b/src/styles/custom.css
index 6536133..07322a3 100644
--- a/src/styles/custom.css
+++ b/src/styles/custom.css
@@ -1,9 +1,26 @@
+/*
+ * Starlight's cascade layer order, restated.
+ *
+ * Starlight declares this in style/layers.css, but a layer's priority is fixed by where
+ * it FIRST appears, and Astro bundles this file ahead of Starlight's own stylesheets.
+ * Opening `@layer starlight.core` below without restating the order therefore registered
+ * starlight.core as the first — and so lowest-priority — layer, dropping it beneath
+ * starlight.reset. The reset's `* { margin: 0 }` then silently won against every margin
+ * Starlight sets in core: the search dialog's centring, the page title and description
+ * spacing, sidebar row gaps, and the 1.5rem rhythm between content blocks.
+ *
+ * This must stay the first statement in this file.
+ */
+@layer starlight.base, starlight.reset, starlight.core, starlight.content, starlight.components,
+ starlight.utils;
+
/*
* OpenDialog brand tokens for Starlight.
*
- * Colours and fonts are taken from opendialog.ai, not invented. The accent is the
- * brand blue #0023ff — hsl(232, 100%, 50%). Starlight's own default accent sits at
- * hue 234, so the brand blue is already close to the theme's tuned defaults.
+ * Colours are taken from opendialog.ai, not invented; the typefaces are taken from
+ * the GitBook docs site this replaces, which serves Poppins and IBM Plex Mono. The
+ * accent is the brand blue #0023ff — hsl(232, 100%, 50%). Starlight's own default
+ * accent sits at hue 234, so the brand blue is already close to the theme's defaults.
*
* The grey ramp keeps Starlight's lightness values, which are tuned for contrast,
* and shifts only hue and saturation onto OpenDialog's blue-tinted greys
@@ -12,12 +29,23 @@
* Starlight treats dark as the :root default and light as [data-theme='light'].
*/
-@import '@fontsource-variable/inter';
-@import '@fontsource/fragment-mono';
+/*
+ * Poppins and IBM Plex Mono are the faces the GitBook docs site serves. Only the
+ * latin subset is imported: the corpus uses 27 non-ASCII codepoints and every one
+ * is either inside latin's range or an emoji that falls back to the system face,
+ * exactly as it does on GitBook. Poppins also ships Devanagari, which nothing here
+ * needs. The corpus contains no bold italic, so 700-italic is not imported.
+ */
+@import '@fontsource/poppins/latin-400.css';
+@import '@fontsource/poppins/latin-400-italic.css';
+@import '@fontsource/poppins/latin-600.css';
+@import '@fontsource/poppins/latin-700.css';
+@import '@fontsource/ibm-plex-mono/latin-400.css';
+@import '@fontsource/ibm-plex-mono/latin-600.css';
:root {
- --sl-font: 'Inter Variable', 'Inter', sans-serif;
- --sl-font-mono: 'Fragment Mono', ui-monospace, monospace;
+ --sl-font: 'Poppins', sans-serif;
+ --sl-font-mono: 'IBM Plex Mono', ui-monospace, monospace;
/* Accent — dark mode. #0023ff is too dark against a dark background, so the
mid tone is lifted while the hue is held at the brand value. */
@@ -72,6 +100,250 @@
}
}
+/*
+ * GitBook's image wrapper divs.
+ *
+ * GitBook lays a wrapper div's figures out in a row: 12px gap, centred, each image at the
+ * width its author set, all shrinking together when the row would otherwise overflow.
+ * Starlight stacks them, because markdown.css sets `display: block` on every image in
+ * content. 13 of the 19 wrappers hold more than one figure — 31 images across 9 pages —
+ * and one of them rendered a 188px thumbnail at 720x1075.
+ *
+ * Having no class is what identifies these: every div Starlight emits into content has one
+ * (sl-heading-wrapper, card-grid, expressive-code). `:has(img)` then excludes the only
+ * other classless div in the corpus, the webchat SDK's mount point.
+ *
+ * `align="left"` means left, as on GitBook; a wrapper without it centres. Unlayered
+ * because the paragraph reset has to beat starlight.content, which outranks
+ * starlight.core.
+ */
+.sl-markdown-content div:not([class]):has(img) {
+ display: flex;
+ flex-wrap: wrap;
+ align-items: flex-start;
+ justify-content: center;
+ gap: 0.75rem;
+}
+
+/*
+ * Above the mobile breakpoint a row that would overflow shrinks rather than wrapping,
+ * which is what GitBook does — its row of four 188px figures renders at 187.25 apiece
+ * rather than breaking to a second line. Below it, wrapping is the sane behaviour.
+ */
+@media (min-width: 50rem) {
+ .sl-markdown-content div:not([class]):has(img) {
+ flex-wrap: nowrap;
+ }
+}
+
+.sl-markdown-content div[align='left']:has(img) {
+ justify-content: flex-start;
+}
+
+/* Each figure — or bare image paragraph, where there is no caption — is one row item. */
+.sl-markdown-content div:not([class]):has(img) > p,
+.sl-markdown-content div:not([class]):has(img) > figure {
+ margin: 0;
+ min-width: 0;
+ flex: 0 1 auto;
+}
+
+/*
+ * An image the author sized keeps that width; an unsized one takes whatever is left,
+ * which is how GitBook fills a row mixing the two — a 374px figure beside an unsized one
+ * renders as 371 and 371 there. Only rehype-image-width sets a style attribute, so its
+ * absence is what marks an image as unsized.
+ */
+.sl-markdown-content div:not([class]):has(img) > p:has(img:not([style])),
+.sl-markdown-content div:not([class]):has(img) > figure:has(img:not([style])) {
+ flex: 1 1 0;
+}
+
+/*
+ * Figure captions.
+ *
+ * rehype-figures pairs each image with the caption beneath it. Markdown could only carry
+ * a caption as emphasis, so Starlight renders it as body-sized italic text aligned left;
+ * GitBook sets 12px, centred, roman, in a muted grey. Unlayered to beat starlight.content.
+ */
+.sl-markdown-content figure {
+ margin: 1.5rem 0;
+}
+
+.sl-markdown-content figcaption {
+ margin-top: 0.5rem;
+ font-size: 0.75rem;
+ line-height: 1rem;
+ text-align: center;
+ color: var(--sl-color-gray-3);
+}
+
+/*
+ * Video embeds.
+ *
+ * convert.mjs emits these as raw HTML rather than a component: an <iframe> is not a
+ * Starlight component, and requiring one promoted 28 pages to .mdx, where a raw <pre> is
+ * parsed as JSX and silently loses its indentation and straight quotes. These styles came
+ * from the component that used to render them.
+ */
+.sl-markdown-content .od-embed-frame {
+ aspect-ratio: 16 / 9;
+ border-radius: 0.5rem;
+ overflow: hidden;
+ border: 1px solid var(--sl-color-gray-5);
+}
+
+.sl-markdown-content .od-embed-frame iframe {
+ width: 100%;
+ height: 100%;
+ border: 0;
+ display: block;
+}
+
+/*
+ * Heading scale.
+ *
+ * Starlight's headings run about 17% larger than GitBook's and carry no tracking:
+ * 42/35 against 36/30 at h1/h2. GitBook's scale, measured, is 36/30/24/20 with
+ * -0.025em on h1 and -0.0125em on h2 through h4, and line-heights of 1.25, 1.2,
+ * 1.333 and 1.4. Only h2, h3 and h4 occur in the corpus — 425, 427 and 343 of them,
+ * no h1 and no h5 or h6 — so the h1 values live in PageTitle.astro, which owns the
+ * only h1 on any page.
+ *
+ * --sl-text-h5 is left alone: asides.css uses it for the aside title, and 258 hint
+ * blocks depend on it.
+ *
+ * Unlayered because Starlight re-declares these tokens inside a media query at
+ * props.css:180 to enlarge headings on wide screens, and styles markdown headings
+ * from a later layer than starlight.core.
+ */
+:root {
+ --sl-text-h1: 2.25rem;
+ --sl-text-h2: 1.875rem;
+ --sl-text-h3: 1.5rem;
+ --sl-text-h4: 1.25rem;
+}
+
+.sl-markdown-content :is(h2, h3, h4):not(:where(.not-content *)) {
+ letter-spacing: -0.0125em;
+}
+
+.sl-markdown-content h2:not(:where(.not-content *)) {
+ line-height: 1.2;
+}
+
+.sl-markdown-content h3:not(:where(.not-content *)) {
+ /* Absolute rather than a 4/3 ratio, which lands on 31.9999px. Safe because the
+ size above is absolute too. */
+ line-height: 2rem;
+}
+
+.sl-markdown-content h4:not(:where(.not-content *)) {
+ line-height: 1.4;
+}
+
+/*
+ * A heading that is itself a link — the corpus authors several, such as "User
+ * Experience" on getting-started-1/getting-ready — renders in Starlight's link blue
+ * with an underline, which reads as a mis-styled heading. GitBook renders it in the
+ * heading colour, undecorated. The hover underline is added rather than measured, so
+ * the link stays discoverable without changing how the heading rests.
+ */
+.sl-markdown-content :is(h1, h2, h3, h4, h5, h6) a:not(:where(.not-content *)) {
+ color: inherit;
+ text-decoration: none;
+}
+
+.sl-markdown-content :is(h1, h2, h3, h4, h5, h6) a:hover:not(:where(.not-content *)),
+.sl-markdown-content :is(h1, h2, h3, h4, h5, h6) a:focus-visible:not(:where(.not-content *)) {
+ text-decoration: underline;
+}
+
+/*
+ * Page shell.
+ *
+ * GitBook constrains its layout to a 1440px box centred in the viewport with 32px of
+ * inner padding, while the header band itself stays full-bleed. Measured at a 1920
+ * viewport: the sidebar starts at 265 and the table of contents ends at 1641, which
+ * is 1440 minus the two 32px pads. Starlight's frame is full-bleed throughout, so on
+ * a wide monitor the nav sits hard against the left edge and the right third is dead
+ * space.
+ *
+ * A single inset feeds the header padding, the fixed sidebar and the main frame, so
+ * the three cannot drift apart. It is computed from 100vw, which includes the
+ * scrollbar, so the shell lands half a scrollbar-width left of true centre — around
+ * 7px against a gutter of 233px at 1920.
+ *
+ * Below 50rem Starlight collapses to one column with a slide-over sidebar, and an
+ * inset would only fight it, so this starts at Starlight's own breakpoint. The
+ * selectors carry extra specificity because Astro compiles Starlight's rules with a
+ * scope class.
+ */
+:root {
+ --od-shell-max: 90rem;
+ --od-shell-pad: 2rem;
+ --od-shell-inset: max(
+ var(--od-shell-pad),
+ calc((100vw - var(--od-shell-max)) / 2 + var(--od-shell-pad))
+ );
+}
+
+@media (min-width: 50rem) {
+ @layer starlight.core {
+ .page > header.header {
+ padding-inline: var(--od-shell-inset);
+ }
+
+ .page .sidebar .sidebar-pane {
+ inset-inline-start: var(--od-shell-inset);
+ }
+
+ .page > .main-frame {
+ padding-inline-start: calc(var(--sl-content-inline-start) + var(--od-shell-inset));
+ padding-inline-end: var(--od-shell-inset);
+ }
+ }
+}
+
+/*
+ * Site title and logo.
+ *
+ * Starlight styles the title with --sl-color-text-accent at --sl-text-h4, which
+ * renders it as 24px brand blue. GitBook sets it in near-black at 18px/600 with
+ * -0.025em tracking, alongside a 32px logo. --sl-color-white is the darkest text
+ * colour in light mode and the lightest in dark, so it tracks the page heading
+ * rather than pinning a foreign hex. That lands on rgb(18, 20, 33) against GitBook's
+ * rgb(28, 29, 32) — a touch darker and bluer, indistinguishable at 18px.
+ *
+ * Selectors are scoped through .header deliberately: Astro compiles Starlight's own
+ * rules to `.site-title.astro-<hash>`, so a bare `.site-title` loses the cascade.
+ */
+@layer starlight.core {
+ .header .site-title {
+ gap: 0.75rem;
+ font-size: 1.125rem;
+ letter-spacing: -0.025em;
+ color: var(--sl-color-white);
+ }
+
+ .header .site-title img {
+ height: 2rem;
+ }
+
+}
+
+/*
+ * GitBook ships some code samples as literal <pre> markup rather than as a fenced
+ * code block. Those never reach Expressive Code, and Starlight's code styling is
+ * scoped to fenced blocks, so without this they fall back to the browser's default
+ * monospace while every other code block on the site renders in IBM Plex Mono.
+ * `:not(.not-content *)` is Starlight's own marker for content it does not style,
+ * and keeps this clear of Expressive Code's frames.
+ */
+.sl-markdown-content pre:not(.not-content *) {
+ font-family: var(--sl-font-mono);
+}
+
/*
* GitBook's <mark> elements survive conversion as raw HTML. Starlight has no
* default styling for them, so they need a rule here or they inherit the browser