@aglyn/aglyn 1.0.0-beta.274 → 1.0.0-beta.277

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

@@ -3530,7 +3530,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Pages',
         heading: 'A page\'s detail view',
         anchor: '#page-detail',
-        text: 'View details opens one page\'s settings without opening its design: its basic details, publishing, who can see it, what links to it, its SEO, versions, traffic and recent activity. Open Besigner at the top of the page is where you change how it looks.\nBasic Details {#basic-details-card}\nThe Basic Details card is the page\'s record: its Page ID, Display name and Description, and when it was created, published and last updated. The published date stays empty until the page goes live. To change the display name or description, use Edit at the top of the detail view.\nUsed by {#used-by}\nThe Used by card finds everything that links to this page before you move, unpublish or delete it: press Find where this is used to scan the published version of every page and layout, every component, the pages nested under this one, and the collections that render their pages through it. Links typed as a plain address rather than picked as a page are not found, because nothing records which page they meant.\nRaw JSON {#raw-json}\nThe Raw JSON card shows the page document exactly as it is stored — a read-only view for developers checking what a page holds. It is closed by default; press the chevron to open it.'
+        text: 'View details opens one page\'s settings without opening its design: its basic details, publishing, who can see it, what links to it, its SEO, versions, traffic and recent activity. Edit in Besigner at the top of the page is where you change how it looks.\nBasic Details {#basic-details-card}\nThe Basic Details card is the page\'s record: its Page ID, Display name and Description, and when it was created, published and last updated. The published date stays empty until the page goes live. To change the display name or description, use the Name & description card.\nName & description {#name-and-description-card}\nThe page\'s Display name is what it is called across the console: the Pages list, the page switcher and search. Its Description is a note about the page. Edit either one in place and choose Save details in the card\'s header. The live page uses them as a fallback too: its title falls back to the display name, and its meta description to the description, wherever the page\'s own SEO leaves them blank.\nUsed by {#used-by}\nThe Used by card finds everything that links to this page before you move, unpublish or delete it: press Find where this is used to scan the published version of every page and layout, every component, the pages nested under this one, and the collections that render their pages through it. Links typed as a plain address rather than picked as a page are not found, because nothing records which page they meant.\nRaw JSON {#raw-json}\nThe Raw JSON card shows the page document exactly as it is stored — a read-only view for developers checking what a page holds. It is closed by default; press the chevron to open it.'
     },
     {
         path: '/building-sites/screens-and-layouts/screens',
@@ -7100,7 +7100,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Sequences',
         heading: 'See one person\'s history',
         anchor: '#person-history',
-        text: 'Select a person\'s row on a sequence\'s Enrollments tab — or focus it and press Enter — to open their page, which shows where they are in the sequence and everything it has done to them. Its address is theirs alone, so you can paste it into a comment or a message to point a teammate at one person. The page has three parts:\n- The header — their name and address, a Lead or Contact chip that opens their CRM record, their status, the step they\'re on and when the next one sends, with the same actions as the row\'s menu. A person held because their mail gateway refused you shows why, and Resume and send sends the email anyway. Under it, five numbers: emails sent, clicks, links followed, scanner clicks (which aren\'t counted) and replies — and, on a sequence that counts opens, their opens, with the machine opens that weren\'t counted beside them.\n- Activity — everything that happened to them; see Their activity.\n- Details — the record behind the enrollment; see Their enrollment\'s details.\nTheir activity {#person-activity}\nThe Activity card lists everything the sequence did to one person, newest first, and Open thread in Gmail opens the conversation in the sending mailbox.\nIt holds when they were enrolled and by whom, each email with its subject as sent (and whether it was their curated copy), each link they followed with the full address and the email it came from, scanner visits with why they were read as a scanner, each open and each machine open with why it wasn\'t counted, replies, bounces with what the receiving server said, holds, pauses, resumes and stops with who did it and why.\nClicks are listed one at a time from the release that added this page. Clicks before it were kept only as a count, the times of the first and last, and the last link followed, so the page shows them '
+        text: 'Select a person\'s row on a sequence\'s Enrollments tab — or focus it and press Enter — to open their page, which shows where they are in the sequence and everything it has done to them. Its address is theirs alone, so you can paste it into a comment or a message to point a teammate at one person. The page has three parts:\n- The header — their name and address, a Lead or Contact chip that opens their CRM record, their status, the step they\'re on and when the next one sends, with the same actions as the row\'s menu. A person who wrote back has Reply in thread as the header\'s button — see Answer a reply. A person held because their mail gateway refused you shows why, and Resume and send sends the email anyway. Under it, five numbers: emails sent, clicks, links followed, scanner clicks (which aren\'t counted) and replies — and, on a sequence that counts opens, their opens, with the machine opens that weren\'t counted beside them.\n- Activity — everything that happened to them; see Their activity.\n- Details — the record behind the enrollment; see Their enrollment\'s details.\nTheir activity {#person-activity}\nThe Activity card lists everything the sequence did to one person, newest first, and Open thread in Gmail opens the conversation in the sending mailbox.\nIt holds when they were enrolled and by whom, each email with its subject as sent (and whether it was their curated copy), each link they followed with the full address and the email it came from, scanner visits with why they were read as a scanner, each open and each machine open with why it wasn\'t counted, each reply and automatic answer with what they wrote, each answer you sent with your words and who sent it, bounces with what the receiving server said, holds, pauses, resumes and stops with who did it and why.\nClicks are '
     },
     {
         path: '/content-and-data/crm/sequences',
@@ -7121,7 +7121,14 @@ export const DOCS_SECTION_INDEX = [
         title: 'Sequences',
         heading: 'What stops a sequence',
         anchor: '#what-stops-a-sequence',
-        text: 'Each connected mailbox is read every 15 minutes for what came back:\n| What happens | What it does |\n| The person replies | Stops the sequence (Replied), files the reply on the contact\'s timeline with a line saying the sequence stopped, and gives the rep the task Reply from their name. |\n| An out-of-office reply | Keeps the sequence going, and moves the next step to at least five business days after the reply. |\n| They ask not to be emailed — a reply such as "no" or "unsubscribe", or, when the sequence adds the mail-client unsubscribe button, that button\'s link or a message to the unsubscribe address | Stops the sequence (Opted out), puts the address on your do-not-contact list, unsubscribes it from the site\'s Sales outreach email, and stops it in every other sequence. |\n| The email hard-bounces | Stops the sequence (Bounced) and puts the address on your do-not-contact list and on the platform\'s suppression list. When the bounce says the recipient\'s mail gateway refused it rather than that the address is unknown, the whole domain goes on the list too, and the enrollment says so. |\n| A check refuses them before the next email — a customer now, a member of your workspace, on a suppression list | Stops the sequence, saying which check. |\n| Their mail gateway refused you twice this month and delivered nothing | Holds the next email (Held — gateway refused this sender twice) until a member selects Resume on the row — see mail gateways. |\n| The mailbox is disconnected or removed, or the member who connected it leaves the organization | Stops the sequences that send from it. |\n| The next email needs something the contact doesn\'t have — a first name for {{contact.firstName}} | Pauses the enrollment, naming what is missing. Fill it in and select Resume. |\nA reply that arrives aft'
+        text: 'Each connected mailbox is read every 15 minutes for what came back:\n| What happens | What it does |\n| The person replies | Stops the sequence (Replied), files the reply on the contact\'s timeline with a line saying the sequence stopped, gives the rep the task Reply from their name, and keeps what they wrote on the enrollment so you can answer it in the thread. |\n| An out-of-office reply | Keeps the sequence going, moves the next step to at least five business days after the reply, and keeps the reply on the enrollment. |\n| They ask not to be emailed — a reply such as "no" or "unsubscribe", or, when the sequence adds the mail-client unsubscribe button, that button\'s link or a message to the unsubscribe address | Stops the sequence (Opted out), puts the address on your do-not-contact list, unsubscribes it from the site\'s Sales outreach email, and stops it in every other sequence. |\n| The email hard-bounces | Stops the sequence (Bounced) and puts the address on your do-not-contact list and on the platform\'s suppression list. When the bounce says the recipient\'s mail gateway refused it rather than that the address is unknown, the whole domain goes on the list too, and the enrollment says so. |\n| A check refuses them before the next email — a customer now, a member of your workspace, on a suppression list | Stops the sequence, saying which check. |\n| Their mail gateway refused you twice this month and delivered nothing | Holds the next email (Held — gateway refused this sender twice) until a member selects Resume on the row — see mail gateways. |\n| The mailbox is disconnected or removed, or the member who connected it leaves the organization | Stops the sequences that send from it. |\n| The next email needs something the contact doesn\'t have — a first name for {{contact.firstN'
+    },
+    {
+        path: '/content-and-data/crm/sequences',
+        title: 'Sequences',
+        heading: 'Answer a reply',
+        anchor: '#answer-a-reply',
+        text: 'When someone writes back — a reply, or an automatic answer such as an out-of-office — answer them from Aglyn, in the same email thread, from the mailbox that wrote to them.\n1. Open the person: select their row on the sequence\'s Enrollments tab, or open their lead or contact in the CRM.\n2. Select Reply in thread. On their enrollment it is the header\'s button, and it is in the row\'s menu on the Enrollments tab. On their lead\'s or contact\'s page it reads Reply in thread from the mailbox\'s address and sits before Send email.\n3. Read what they wrote. The dialog shows the address your answer goes from, who it goes to and its subject — Re: their subject — above the conversation so far: their messages, any earlier answers, and the sequence\'s emails by subject.\n4. Write your answer in Your answer, then select Send answer.\nYour answer:\n- Goes from the enrollment\'s own mailbox, in the same thread — in your Gmail or Outlook and in theirs — as plain text, with their message quoted beneath it. Send email on a CRM record writes a new message from your site\'s sending address instead, which is why a person in a sequence thread is offered Reply in thread first.\n- Is kept with the person. Their page\'s Activity lists it as Answered in the thread, with your words and who sent it, and their CRM record\'s timeline lists it as an email from the mailbox.\n- Carries tracked links, on a sequence that counts link clicks. The links you write become the same short links the sequence\'s emails carry, on your link domain when you\'ve set one up. A click on one shows on the person\'s Activity as From an answer in the thread. The message you\'re answering, quoted beneath yours, is left as they wrote it. On a sequence that doesn\'t count clicks, your links go out as you wrote them.\n- Leaves the sequence where i'
     },
     {
         path: '/content-and-data/crm/sequences',
@@ -10418,7 +10425,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Build a newsletter sign-up band',
         heading: '6. Build the band as a reusable component',
         anchor: '#6-build-the-band-as-a-reusable-component',
-        text: '1. Open Components → Create Component. Under Where will you use it? choose On pages, name it Newsletter band, and choose Next. Then Open Besigner.\n2. Give it two text properties so each page can change the words. Choose File → Properties… → Add property:\n| Name | Type | Label | Default |\n| heading | Text | Heading | Get product updates |\n| description | Text | Description | New features, guides, and early-access news — straight to your inbox. No spam. |\nChoose Save properties.\n3. Build the band from the Choose element picker:\n- a Section: the band itself. Set its Accessible label to Newsletter sign-up so screen readers can find it.\n- inside it, two Typography elements:\n- The first one\'s text is the heading property. Use the text field\'s {} button and pick heading from its Properties group. Set Variant to Heading 4 and Component to h2.\n- The second one\'s text is the description property, picked the same way, with Variant set to Body 1.\nSee Insert a variable.\n- a Form, from the Forms group. Pick Product updates under Form. The band now draws that form\'s field and button, styled as you styled them.\n4. Style the Section:\n- Colors:\n- Background Fill = Linear gradient. Set the Angle to 243, and bind its two color stops to the theme\'s Secondary and Primary colors. See Gradient backgrounds.\n- Text Color = common.white. The heading and copy inside inherit it.\n- Flexbox & Grid: Flex direction column, Align items center, Gap Small.\n- Typography: Text Alignment center.\n- In the spacing ring, Padding: Top and Bottom Huge, Left and Right Medium.\nBecause the gradient\'s stops are theme colors, each site that places the band shows it in that site\'s own colors.\n5. Give the two Typography elements a little polish:\n- The heading: Typography → Font Weight = Bold.\n- The description: Opacity '
+        text: '1. Open Components → Create Component. Under Where will you use it? choose On pages, name it Newsletter band, and choose Next. Then Edit in Besigner.\n2. Give it two text properties so each page can change the words. Choose File → Properties… → Add property:\n| Name | Type | Label | Default |\n| heading | Text | Heading | Get product updates |\n| description | Text | Description | New features, guides, and early-access news — straight to your inbox. No spam. |\nChoose Save properties.\n3. Build the band from the Choose element picker:\n- a Section: the band itself. Set its Accessible label to Newsletter sign-up so screen readers can find it.\n- inside it, two Typography elements:\n- The first one\'s text is the heading property. Use the text field\'s {} button and pick heading from its Properties group. Set Variant to Heading 4 and Component to h2.\n- The second one\'s text is the description property, picked the same way, with Variant set to Body 1.\nSee Insert a variable.\n- a Form, from the Forms group. Pick Product updates under Form. The band now draws that form\'s field and button, styled as you styled them.\n4. Style the Section:\n- Colors:\n- Background Fill = Linear gradient. Set the Angle to 243, and bind its two color stops to the theme\'s Secondary and Primary colors. See Gradient backgrounds.\n- Text Color = common.white. The heading and copy inside inherit it.\n- Flexbox & Grid: Flex direction column, Align items center, Gap Small.\n- Typography: Text Alignment center.\n- In the spacing ring, Padding: Top and Bottom Huge, Left and Right Medium.\nBecause the gradient\'s stops are theme colors, each site that places the band shows it in that site\'s own colors.\n5. Give the two Typography elements a little polish:\n- The heading: Typography → Font Weight = Bold.\n- The description: Opaci'
     },
     {
         path: '/guides/newsletter-sign-up-band',