@aglyn/aglyn 1.18.0 → 1.19.0
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 +11 -11
- package/src/lib/app-utils/compose-reusable-components.js +7 -3
- package/src/lib/app-utils/compose-reusable-components.js.map +1 -1
- package/src/lib/app-utils/docs-help.generated.d.ts +1 -1
- package/src/lib/app-utils/docs-help.generated.js +1 -0
- package/src/lib/app-utils/docs-help.generated.js.map +1 -1
- package/src/lib/app-utils/docs-index.generated.js +18 -4
- package/src/lib/app-utils/docs-index.generated.js.map +1 -1
- package/src/lib/app-utils/element-motion.js +6 -5
- package/src/lib/app-utils/element-motion.js.map +1 -1
- package/src/lib/app-utils/expand-repeatables.d.ts +23 -3
- package/src/lib/app-utils/expand-repeatables.js +61 -7
- package/src/lib/app-utils/expand-repeatables.js.map +1 -1
- package/src/lib/app-utils/plugin-connection-editor.d.ts +22 -0
- package/src/lib/app-utils/plugin-connection-editor.js.map +1 -1
- package/src/lib/app-utils/plugin-connection-repeat.d.ts +82 -0
- package/src/lib/app-utils/plugin-connection-repeat.js +162 -0
- package/src/lib/app-utils/plugin-connection-repeat.js.map +1 -0
- package/src/lib/app-utils/repeat-sources.d.ts +33 -1
- package/src/lib/app-utils/repeat-sources.js +27 -3
- package/src/lib/app-utils/repeat-sources.js.map +1 -1
- package/src/lib/app-utils/seo-page-facts.js +3 -6
- package/src/lib/app-utils/seo-page-facts.js.map +1 -1
- package/src/lib/plugin-manager/first-party-plugins.generated.d.ts +6 -0
- package/src/lib/plugin-manager/first-party-plugins.generated.js +8 -0
- package/src/lib/plugin-manager/first-party-plugins.generated.js.map +1 -1
- package/src/lib/plugin-manager/repeat-rows.d.ts +20 -2
- package/src/lib/plugin-manager/repeat-rows.js +42 -16
- package/src/lib/plugin-manager/repeat-rows.js.map +1 -1
|
@@ -2375,7 +2375,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
2375
2375
|
title: 'Repeat over data',
|
|
2376
2376
|
heading: '',
|
|
2377
2377
|
anchor: '',
|
|
2378
|
-
text: 'Repeat over data\nAny element on a page can repeat. Point it at a dataset and it renders once per record on the published page, with each copy filled in from that record. A row of cards, a gallery, a team list, a price table — one design, as many copies as you have rows.'
|
|
2378
|
+
text: 'Repeat over data\nAny element on a page can repeat. Point it at a dataset — or at what a connected service last synced — and it renders once per record on the published page, with each copy filled in from that record. A row of cards, a gallery, a team list, a price table — one design, as many copies as you have rows.'
|
|
2379
2379
|
},
|
|
2380
2380
|
{
|
|
2381
2381
|
path: '/building-sites/besigner/repeat',
|
|
@@ -2419,6 +2419,20 @@ export const DOCS_SECTION_INDEX = [
|
|
|
2419
2419
|
anchor: '#what-you-cant-do',
|
|
2420
2420
|
text: '- Repeats don\'t nest. A repeat inside another repeat\'s template renders once inside each copy, using its own record — it does not multiply out.\n- A copy is not a page. Copies share one design by definition. If one record needs to look different, that\'s a condition on the design, not a second design.'
|
|
2421
2421
|
},
|
|
2422
|
+
{
|
|
2423
|
+
path: '/building-sites/besigner/repeat',
|
|
2424
|
+
title: 'Repeat over data',
|
|
2425
|
+
heading: 'Repeat over a connected service',
|
|
2426
|
+
anchor: '#repeat-over-a-connected-service',
|
|
2427
|
+
text: 'A plugin that connects to a service — Google reviews, say — keeps a small copy of what that service last sent: a list of items (each review) and a summary (the overall rating and the number of reviews). Any element can repeat over that copy the same way it repeats over a dataset, so you design the reviews with ordinary elements — a Card, a Stack, Typography, an image, a link — instead of styling one closed block.\n1. Install the plugin and connect it to the service on the site\'s page for that plugin.\n2. Select the element on the canvas and open the Attributes tab.\n3. In Repeat over a connection, pick what to repeat over. Each connection is listed twice, by its name:\n- each item (for example Google: each item) — one copy per item, such as one card per review;\n- summary (for example Google: summary) — one copy holding the summary, such as a "4.8 stars from 120 reviews" header.\nThe picker lists only the connections this site has. On a site with none, it does not appear at all.\nInside the repeating element, Insert binding lists the fields the plugin provides — for example {{item.author}}, {{item.rating}}, {{item.text}}. Dates read as Nov 3, 2026; each date also comes as …Iso (for example {{item.publishedAtIso}}) when you need the exact moment rather than the words.\nFilter, sort and limit work exactly as they do for a dataset: Repeat limit 3 shows the first three reviews, Repeat filter rating >= 4 only the good ones, and Repeat sort publishedAtIso desc the newest first.\nUntil the plugin has synced for the first time, there is nothing to show: a repeat over the items renders no copies, and a repeat over the summary renders none either, so the published page never shows an empty card.'
|
|
2428
|
+
},
|
|
2429
|
+
{
|
|
2430
|
+
path: '/building-sites/besigner/repeat',
|
|
2431
|
+
title: 'Repeat over data',
|
|
2432
|
+
heading: 'Hide part of a copy when a field is empty',
|
|
2433
|
+
anchor: '#hide-part-of-a-copy-when-a-field-is-empty',
|
|
2434
|
+
text: 'Some records fill a field and others don\'t — a review the owner replied to, and one they didn\'t. To draw a block only on the copies that have the value, bind its visibility to the field:\n1. Select the block inside the repeating element (for example a Box holding a "Response from the owner" caption and {{item.reply}}).\n2. In the Attributes tab, set Hide unless to {{item.reply}} (the Insert binding button lists the fields). Every element inside a repeating element has this field.\nEach copy whose review has a reply draws the block; every other copy leaves it out, caption included. Hide when works the other way round: the block is left out of each copy where the field holds a value. Both work the same way inside a repeat over a dataset.\nA field that is empty, false, 0, no or off counts as no value. On the canvas, the copy you edit always shows the block so you can keep designing it; the copies beside it, Preview and the published page leave it out where the record has no value.'
|
|
2435
|
+
},
|
|
2422
2436
|
{
|
|
2423
2437
|
path: '/building-sites/besigner/repeat',
|
|
2424
2438
|
title: 'Repeat over data',
|
|
@@ -12364,7 +12378,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12364
12378
|
title: 'Org automations',
|
|
12365
12379
|
heading: '',
|
|
12366
12380
|
anchor: '',
|
|
12367
|
-
text: 'Org automations\nAn org automation is one automation your organization writes once and runs on the sites it chooses — every site, or the ones you
|
|
12381
|
+
text: 'Org automations\nAn org automation is one automation your organization writes once and runs on the sites it chooses — every site, the ones you pick, or every site except the ones you leave out. Build it at the organization level under Automation → Org automations; each site shows the ones that run on it, and can pause them for itself.\nPlan availability Org automations are built from the actions builder\'s steps, so they are Pro+, like the actions builder, and their runs are metered on the same allowance a site\'s own actions use.'
|
|
12368
12382
|
},
|
|
12369
12383
|
{
|
|
12370
12384
|
path: '/marketing-and-automation/workflows-and-actions/org-automations',
|
|
@@ -12378,7 +12392,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12378
12392
|
title: 'Org automations',
|
|
12379
12393
|
heading: 'Create one',
|
|
12380
12394
|
anchor: '#create-one',
|
|
12381
|
-
text: '1. At the organization level, open Automation → Org automations and choose Add org automation.\n2. Name it and pick the trigger event. Optionally add a filter or conditions — the same ones the actions builder offers.\n3. Choose where it runs on
|
|
12395
|
+
text: '1. At the organization level, open Automation → Org automations and choose Add org automation.\n2. Name it and pick the trigger event. Optionally add a filter or conditions — the same ones the actions builder offers.\n3. Choose where it runs on:\n- All sites — including sites you add later;\n- Selected sites, up to 30 of them — a site you add later doesn\'t get it until you add it here;\n- All sites except… — every site but the ones you tick to leave out, including sites you add later. Leave out at least one site and keep at least one in. A workspace with one site has nothing to leave out, so this choice is switched off there, with the reason.\n4. Add the steps, then save.\nA site you leave out doesn\'t run it and can\'t pause it, because it isn\'t placed there. If that site had paused it, its pause is dropped; put the site back and it starts unpaused.\nTo start from a description instead, choose Create with AI in the card\'s header: Aglyn AI drafts one and opens it in the editor, switched off, for you to place on sites and save. See Automations with AI.\nCreating and editing org automations, including choosing the sites they run on, takes the Manage org automations permission, which a workspace\'s owners, admins and editors have. An organization holds up to 100 of them; deleting one frees its place.\nTriggers\nOrg automations start on what the server records about a person: Form submitted, New lead, Contact created, Contact changed stage, New booking, Member signed up, Member signed in, Deal moved, Deal won, Deal lost and CRM task completed. What each event carries for filters and conditions is listed under the filter field as you pick it.\nPage views and on-page events (clicks, scroll depth, exit intent) are not offered: they belong to one site\'s pages. Build those as actions on the si'
|
|
12382
12396
|
},
|
|
12383
12397
|
{
|
|
12384
12398
|
path: '/marketing-and-automation/workflows-and-actions/org-automations',
|
|
@@ -12392,7 +12406,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12392
12406
|
title: 'Org automations',
|
|
12393
12407
|
heading: 'Waiting, switching off and deleting',
|
|
12394
12408
|
anchor: '#waiting-switching-off-and-deleting',
|
|
12395
|
-
text: 'An org automation can Wait and Wait for something to happen, like an action. A person who is waiting waits on the site their run started on, and continues with the steps as they were when they entered, even if the automation is edited meanwhile.\nSwitching an org automation off, deleting it, taking a site off its placement, or pausing it on a site stops the people waiting inside it on the sites affected, on their next step — the same as switching off an action does.'
|
|
12409
|
+
text: 'An org automation can Wait and Wait for something to happen, like an action. A person who is waiting waits on the site their run started on, and continues with the steps as they were when they entered, even if the automation is edited meanwhile.\nSwitching an org automation off, deleting it, taking a site off its placement (including leaving it out of All sites except…), or pausing it on a site stops the people waiting inside it on the sites affected, on their next step — the same as switching off an action does.'
|
|
12396
12410
|
},
|
|
12397
12411
|
{
|
|
12398
12412
|
path: '/marketing-and-automation/workflows-and-actions/org-automations',
|