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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@aglyn/aglyn",
3
- "version": "1.0.0-beta.275",
3
+ "version": "1.0.0-beta.277",
4
4
  "license": "Apache-2.0",
5
5
  "homepage": "https://aglyn.com",
6
6
  "repository": {
@@ -37,16 +37,16 @@
37
37
  "./package.json": "./package.json"
38
38
  },
39
39
  "dependencies": {
40
- "@aglyn/shared-data-enums": "1.0.0-beta.275",
41
- "@aglyn/shared-data-mdi": "1.0.0-beta.275",
42
- "@aglyn/shared-data-types": "1.0.0-beta.275",
43
- "@aglyn/shared-util-email": "1.0.0-beta.275",
44
- "@aglyn/shared-util-first-touch": "1.0.0-beta.275",
45
- "@aglyn/shared-util-http": "1.0.0-beta.275",
46
- "@aglyn/shared-util-logger": "1.0.0-beta.275",
47
- "@aglyn/shared-util-timestamp": "1.0.0-beta.275",
48
- "@aglyn/shared-util-tools": "1.0.0-beta.275",
49
- "@aglyn/shared-util-vendor": "1.0.0-beta.275",
40
+ "@aglyn/shared-data-enums": "1.0.0-beta.277",
41
+ "@aglyn/shared-data-mdi": "1.0.0-beta.277",
42
+ "@aglyn/shared-data-types": "1.0.0-beta.277",
43
+ "@aglyn/shared-util-email": "1.0.0-beta.277",
44
+ "@aglyn/shared-util-first-touch": "1.0.0-beta.277",
45
+ "@aglyn/shared-util-http": "1.0.0-beta.277",
46
+ "@aglyn/shared-util-logger": "1.0.0-beta.277",
47
+ "@aglyn/shared-util-timestamp": "1.0.0-beta.277",
48
+ "@aglyn/shared-util-tools": "1.0.0-beta.277",
49
+ "@aglyn/shared-util-vendor": "1.0.0-beta.277",
50
50
  "@data-driven-forms/react-form-renderer": "^4.2.0",
51
51
  "@msgpack/msgpack": "^3.1.3",
52
52
  "@types/unist": "^3.0.3",
@@ -3530,7 +3530,7 @@ export const DOCS_SECTION_INDEX = [
3530
3530
  title: 'Pages',
3531
3531
  heading: 'A page\'s detail view',
3532
3532
  anchor: '#page-detail',
3533
- 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.'
3533
+ 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.'
3534
3534
  },
3535
3535
  {
3536
3536
  path: '/building-sites/screens-and-layouts/screens',
@@ -7128,7 +7128,7 @@ export const DOCS_SECTION_INDEX = [
7128
7128
  title: 'Sequences',
7129
7129
  heading: 'Answer a reply',
7130
7130
  anchor: '#answer-a-reply',
7131
- 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- Leaves the sequence where it is. A replied enrollment stays Replied. One still running after an out-of-office keeps its next step, and that step answers in the same thread.\n- Isn\'t one of the sequence\'s emails. It doesn\'t count against the mailbox\'s daily cap, doesn\'t count toward the bounce rate that pauses a mailbox, and isn\'t in the sequence\'s results. The mailbox\'s card counts them on their own, as Answers to replies today.\nThe rules for c'
7131
+ 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'
7132
7132
  },
7133
7133
  {
7134
7134
  path: '/content-and-data/crm/sequences',
@@ -10425,7 +10425,7 @@ export const DOCS_SECTION_INDEX = [
10425
10425
  title: 'Build a newsletter sign-up band',
10426
10426
  heading: '6. Build the band as a reusable component',
10427
10427
  anchor: '#6-build-the-band-as-a-reusable-component',
10428
- 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 '
10428
+ 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'
10429
10429
  },
10430
10430
  {
10431
10431
  path: '/guides/newsletter-sign-up-band',