@aglyn/aglyn 1.14.0 → 1.15.1
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/buy-now-pay-later.d.ts +45 -0
- package/src/lib/app-utils/buy-now-pay-later.js +68 -0
- package/src/lib/app-utils/buy-now-pay-later.js.map +1 -0
- package/src/lib/app-utils/contexts.d.ts +1 -0
- package/src/lib/app-utils/contexts.js +1 -0
- package/src/lib/app-utils/contexts.js.map +1 -1
- package/src/lib/app-utils/docs-help-sections.generated.js +6 -3
- package/src/lib/app-utils/docs-help-sections.generated.js.map +1 -1
- package/src/lib/app-utils/docs-help.generated.d.ts +6 -6
- package/src/lib/app-utils/docs-help.generated.js +14 -1
- package/src/lib/app-utils/docs-help.generated.js.map +1 -1
- package/src/lib/app-utils/docs-index.generated.js +20 -20
- package/src/lib/app-utils/docs-index.generated.js.map +1 -1
- package/src/lib/app-utils/entity-picker-context.d.ts +6 -0
- package/src/lib/app-utils/entity-picker-context.js.map +1 -1
- package/src/lib/app-utils/host-status.js +1 -1
- package/src/lib/app-utils/host-status.js.map +1 -1
- package/src/lib/app-utils/org-role-grants.js +1 -1
- package/src/lib/app-utils/org-role-grants.js.map +1 -1
- package/src/lib/app-utils/page-header-record-context.d.ts +15 -0
- package/src/lib/app-utils/page-header-record-context.js +13 -4
- package/src/lib/app-utils/page-header-record-context.js.map +1 -1
- package/src/lib/app-utils/plan-entitlements.d.ts +125 -46
- package/src/lib/app-utils/plan-entitlements.js +118 -49
- package/src/lib/app-utils/plan-entitlements.js.map +1 -1
- package/src/lib/app-utils/plugin-bundle-checks.d.ts +14 -2
- package/src/lib/app-utils/plugin-bundle-checks.js +82 -7
- package/src/lib/app-utils/plugin-bundle-checks.js.map +1 -1
- package/src/lib/app-utils/plugin-connection-editor.d.ts +48 -0
- package/src/lib/app-utils/plugin-connection-editor.js +46 -0
- package/src/lib/app-utils/plugin-connection-editor.js.map +1 -0
- package/src/lib/app-utils/plugin-connection-record.d.ts +42 -0
- package/src/lib/app-utils/plugin-connection-record.js +48 -0
- package/src/lib/app-utils/plugin-connection-record.js.map +1 -0
- package/src/lib/app-utils/plugin-connection-records-context.d.ts +23 -0
- package/src/lib/app-utils/plugin-connection-records-context.js +29 -0
- package/src/lib/app-utils/plugin-connection-records-context.js.map +1 -0
- package/src/lib/app-utils/plugin-connection-records.d.ts +42 -0
- package/src/lib/app-utils/plugin-connection-records.js +56 -0
- package/src/lib/app-utils/plugin-connection-records.js.map +1 -0
- package/src/lib/app-utils/plugin-connections.d.ts +320 -0
- package/src/lib/app-utils/plugin-connections.js +895 -0
- package/src/lib/app-utils/plugin-connections.js.map +1 -0
- package/src/lib/app-utils/plugin-elements.d.ts +104 -0
- package/src/lib/app-utils/plugin-elements.js +128 -0
- package/src/lib/app-utils/plugin-elements.js.map +1 -0
- package/src/lib/app-utils/plugin-manifest.d.ts +20 -75
- package/src/lib/app-utils/plugin-manifest.js +65 -100
- package/src/lib/app-utils/plugin-manifest.js.map +1 -1
- package/src/lib/app-utils/realm-elements-context.d.ts +16 -0
- package/src/lib/app-utils/realm-elements-context.js +16 -0
- package/src/lib/app-utils/realm-elements-context.js.map +1 -1
- package/src/lib/app-utils/realm-host-surface.generated.js +1 -0
- package/src/lib/app-utils/realm-host-surface.generated.js.map +1 -1
- package/src/lib/app-utils/release-flags.d.ts +1 -1
- package/src/lib/app-utils/release-flags.js +35 -0
- package/src/lib/app-utils/release-flags.js.map +1 -1
- package/src/lib/app-utils/server.d.ts +1 -0
- package/src/lib/app-utils/server.js +2 -0
- package/src/lib/app-utils/server.js.map +1 -1
- package/src/lib/app-utils/site-context.d.ts +9 -0
- package/src/lib/app-utils/site-context.js.map +1 -1
- package/src/lib/app-utils/site-starter.d.ts +6 -0
- package/src/lib/app-utils/site-starter.js +15 -0
- package/src/lib/app-utils/site-starter.js.map +1 -1
- package/src/lib/plugin-manager/feature-plugins.d.ts +25 -0
- package/src/lib/plugin-manager/feature-plugins.js +10 -0
- package/src/lib/plugin-manager/feature-plugins.js.map +1 -1
- package/src/lib/plugin-manager/first-party-plugins.generated.js +12 -0
- package/src/lib/plugin-manager/first-party-plugins.generated.js.map +1 -1
- package/src/lib/plugin-manager/index.d.ts +1 -0
- package/src/lib/plugin-manager/index.js +1 -0
- package/src/lib/plugin-manager/index.js.map +1 -1
- package/src/lib/plugin-manager/plugin-artifact-inventory.d.ts +5 -0
- package/src/lib/plugin-manager/plugin-artifact-inventory.js.map +1 -1
- package/src/lib/plugin-manager/plugin-record-lists.d.ts +18 -0
- package/src/lib/plugin-manager/plugin-record-lists.js +13 -0
- package/src/lib/plugin-manager/plugin-record-lists.js.map +1 -1
- package/src/lib/plugin-manager/plugin-site-csp.d.ts +36 -0
- package/src/lib/plugin-manager/plugin-site-csp.js +50 -1
- package/src/lib/plugin-manager/plugin-site-csp.js.map +1 -1
- package/src/lib/plugin-manager/realm-host-aglyn.generated.js +61 -59
- package/src/lib/plugin-manager/realm-host-aglyn.generated.js.map +1 -1
- package/src/lib/plugin-manager/site-page-enricher-services.d.ts +35 -0
- package/src/lib/plugin-manager/site-page-enricher-services.js +35 -0
- package/src/lib/plugin-manager/site-page-enricher-services.js.map +1 -0
- package/src/lib/plugin-manager/site-page-hooks.js +16 -3
- package/src/lib/plugin-manager/site-page-hooks.js.map +1 -1
- package/src/lib/plugin-manager/video-embed-provider.d.ts +28 -0
- package/src/lib/plugin-manager/video-embed-provider.js +21 -0
- package/src/lib/plugin-manager/video-embed-provider.js.map +1 -1
- package/src/lib/plugin-manager/video-embed-providers.generated.js +3 -1
- package/src/lib/plugin-manager/video-embed-providers.generated.js.map +1 -1
|
@@ -555,7 +555,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
555
555
|
title: 'Bring my site',
|
|
556
556
|
heading: 'Keep my site or improve it',
|
|
557
557
|
anchor: '#keep-or-improve',
|
|
558
|
-
text: 'Before you choose Read my site, choose how your new site should look under How should your new site look?:\n- Keep my site keeps your pages laid out as they are, in your site\'s colors, buttons and fonts. Aglyn tidies spacing, type and color so every page reads well. Every word stays as you wrote it.\n- Improve it, chosen unless you pick otherwise, has Aglyn AI redesign each page with your pictures, menus and forms, in a theme built around your brand. Every page and section, every picture, icon, button and heading, your forms, videos and menus all come across, in your brand\'s colors and fonts.\nUnder Improve it, Also improve my wording is on unless you switch it off. Aglyn AI rewrites the headings, paragraphs and buttons of your main pages so they read better. Every name, price, number, date, address, phone number and email stays exactly as you wrote it, and quotes, policy pages, tables and forms keep every word. Pages of a collection, such as blog posts, and your header and footer keep every word too, and so do the names on your cards, your plans and prices, your figures and badges, the small labels above your headings, your fine print and any sentence with a link in it. A line Aglyn AI cannot reword without changing a fact keeps the words you wrote. Improving the wording uses more AI credits, and the switch says how many before you start a wave.\nYou can change it before each wave. Your import\'s page says how the next wave will be built, for example How your new site looks: Keep my site. Choose Change, pick again, then start the wave. A wave that is already in is never redrawn. Each wave\'s heading says how it was built, for example Main pages · Keep my site or Main pages · Improved.\nAn import started before this choice existed is built as Keep my site
|
|
558
|
+
text: 'Before you choose Read my site, choose how your new site should look under How should your new site look?:\n- Keep my site keeps your pages laid out as they are, in your site\'s colors, buttons and fonts. Aglyn tidies spacing, type and color so every page reads well. Every word stays as you wrote it.\n- Improve it, chosen unless you pick otherwise, has Aglyn AI redesign each page with your pictures, menus and forms, in a theme built around your brand. Every page and section, every picture, icon, button and heading, your forms, videos and menus all come across, in your brand\'s colors and fonts.\nUnder Improve it, Also improve my wording is on unless you switch it off. Aglyn AI rewrites the headings, paragraphs and buttons of your main pages so they read better. Every name, price, number, date, address, phone number and email stays exactly as you wrote it, and quotes, policy pages, tables and forms keep every word. Pages of a collection, such as blog posts, and your header and footer keep every word too, and so do the names on your cards, your plans and prices, your figures and badges, the small labels above your headings, your fine print and any sentence with a link in it. A line Aglyn AI cannot reword without changing a fact keeps the words you wrote. Improving the wording uses more AI credits, and the switch says how many before you start a wave.\nYou can change it before each wave. Your import\'s page says how the next wave will be built, for example How your new site looks: Keep my site. Choose Change, pick again, then start the wave. A wave that is already in is never redrawn. Each wave\'s heading says how it was built, for example Main pages · Keep my site or Main pages · Improved.\nAn import started before this choice existed is built as Keep my site.\nA planned, rewritten'
|
|
559
559
|
},
|
|
560
560
|
{
|
|
561
561
|
path: '/ai/bring-my-site',
|
|
@@ -1332,7 +1332,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
1332
1332
|
title: 'Looks and themes for AI sites',
|
|
1333
1333
|
heading: 'An AI starter\'s look',
|
|
1334
1334
|
anchor: '#an-ai-starters-look',
|
|
1335
|
-
text: 'AI starters are rolling out, and your workspace may not have them yet. When you start from an AI starter, its style arrives chosen on the Style step
|
|
1335
|
+
text: 'AI starters are rolling out, and your workspace may not have them yet. When you start from an AI starter, its style arrives chosen on the Style step. Its card says which starter it came from and what its look is set in, such as Set in Bootstrap with Fraunces and Inter; pick another style to change it. The Style line on Review says the same. Its brand color arrives picked under More details on the same step, as Chosen color.\nYour site then wears the look the starter shows: its built-in base theme, its fonts, and its page background, corners and buttons, in your brand color. The rest of the look, such as its cards and how its pages move, is chosen within the style as for any start. If you gave sites you like, the starter\'s look comes first, and what those sites suggest fills in the rest.\nTo change it, choose another style card. The starter\'s base theme and fonts go with it, and your site gets that style\'s own look. Choose the starter\'s card again to have them back. Choose another brand color, or Let the style choose, to change the color.'
|
|
1336
1336
|
},
|
|
1337
1337
|
{
|
|
1338
1338
|
path: '/ai/site-looks',
|
|
@@ -1381,7 +1381,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
1381
1381
|
title: 'Start a new site with AI',
|
|
1382
1382
|
heading: 'Start from an AI starter',
|
|
1383
1383
|
anchor: '#start-from-an-ai-starter',
|
|
1384
|
-
text: 'AI starters are rolling out, and your workspace may not have them yet. Where they are on, Start from a starter site opens Choose your starter, and its AI starters tab lists starters Aglyn AI writes your pages from. An AI starter is a set of answers and a look for one kind of site, never ready-made pages.\n1. On the first step, name your site and choose its address, then choose Start from a starter site.\n2. Choose the AI starters tab and pick a starter.\n3. Choose Continue.\nStart your site opens on Your site with its questions filled in from the starter, and says so above the first question. The starter\'s style is chosen on the Style step, and its card says which starter it came from. Its brand color is picked under that step\'s More details, as Chosen color. When the starter says what the site is for, that answer is filled in too. Otherwise you say it, as you would for any start. Change any answer you like, then choose Plan my site on Review. It works as always: it creates the site, then plans, writes and publishes its pages for your business.\nA starter with a price is bought before its answers are shown. Picking one says its price, with Buy and continue, and Continue waits until it is yours. Nothing is created until Plan my site, so closing the window before then leaves nothing behind. If the site is created and its pages cannot be planned, leaving gives it the starter\'s own pages, so it is never left empty.'
|
|
1384
|
+
text: 'AI starters are rolling out, and your workspace may not have them yet. Where they are on, Start from a starter site opens Choose your starter, and its AI starters tab lists starters Aglyn AI writes your pages from. An AI starter is a set of answers and a look for one kind of site, never ready-made pages.\n1. On the first step, name your site and choose its address, then choose Start from a starter site.\n2. Choose the AI starters tab and pick a starter.\n3. Choose Continue.\nStart your site opens on Your site with its questions filled in from the starter, and says so above the first question. The starter\'s style is chosen on the Style step, and its card says which starter it came from and the look it is set in. Its brand color is picked under that step\'s More details, as Chosen color. When the starter says what the site is for, that answer is filled in too. Otherwise you say it, as you would for any start. Change any answer you like, then choose Plan my site on Review. It works as always: it creates the site, then plans, writes and publishes its pages for your business.\nA starter with a price is bought before its answers are shown. Picking one says its price, with Buy and continue, and Continue waits until it is yours. Nothing is created until Plan my site, so closing the window before then leaves nothing behind. If the site is created and its pages cannot be planned, leaving gives it the starter\'s own pages, so it is never left empty.'
|
|
1385
1385
|
},
|
|
1386
1386
|
{
|
|
1387
1387
|
path: '/ai/start-with-ai',
|
|
@@ -2774,7 +2774,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
2774
2774
|
title: 'Video',
|
|
2775
2775
|
heading: 'A video hosted on Wistia, YouTube or Vimeo',
|
|
2776
2776
|
anchor: '#video-wistia',
|
|
2777
|
-
text: 'Paste the video\'s link into Video source. Each host\'s usual links work:\n- Wistia: the address of the video\'s page in your Wistia account, or its embed link.\n- YouTube: the video\'s page, a Short, a live video, its embed link, or the youtu.be link from Share.\n- Vimeo: the video\'s page, the same video in a channel, group or showcase, or its embed link. An unlisted Vimeo video does not play this way: its link carries a private part the player needs, so make the video public on Vimeo first.\nA link to a channel, a playlist or a search names no single video, so the element treats it as an ordinary link and plays nothing.\nThen pick a Poster image from your media library. The poster becomes a play button, and the host\'s player loads only when a visitor presses it, so someone who never presses play never contacts the host, unless you turn on Load the player with the page (below). The player opens in the lightbox when Open in a lightbox is on, and in place of the poster when it is off. Without a poster the element asks for one instead of loading the player.\nEach host\'s player brings its own controls. In the lightbox, Esc closes it until you move into the player; from inside the player, Shift+Tab reaches the close button. Type the running time into Duration (seconds), because a hosted video\'s link does not carry it.\nHow each host\'s player treats your visitors:\n- Wistia records a viewing only for a visitor whose analytics consent your site has on record, and plays with its tracking off for everyone else.\n- YouTube always plays in its privacy-enhanced player (youtube-nocookie.com), for every visitor.\n- Vimeo always plays with its do-not-track option on, for every visitor.\nTurn on Load the player with the page for a page
|
|
2777
|
+
text: 'Paste the video\'s link into Video source. Each host\'s usual links work:\n- Wistia: the address of the video\'s page in your Wistia account, or its embed link.\n- YouTube: the video\'s page, a Short, a live video, its embed link, or the youtu.be link from Share.\n- Vimeo: the video\'s page, the same video in a channel, group or showcase, or its embed link. An unlisted Vimeo video does not play this way: its link carries a private part the player needs, so make the video public on Vimeo first.\nA link to a channel, a playlist or a search names no single video, so the element treats it as an ordinary link and plays nothing.\nThen pick a Poster image from your media library. The poster becomes a play button, and the host\'s player loads only when a visitor presses it, so someone who never presses play never contacts the host, unless you turn on Load the player with the page (below). The player opens in the lightbox when Open in a lightbox is on, and in place of the poster when it is off. Without a poster the element asks for one instead of loading the player, except where a YouTube video shows YouTube\'s own thumbnail.\nEach host\'s player brings its own controls. In the lightbox, Esc closes it until you move into the player; from inside the player, Shift+Tab reaches the close button. Type the running time into Duration (seconds), because a hosted video\'s link does not carry it.\nHow each host\'s player treats your visitors:\n- Wistia records a viewing only for a visitor whose analytics consent your site has on record, and plays with its tracking off for everyone else.\n- YouTube always plays in its privacy-enhanced player (youtube-nocookie.com), for every visitor.\n- Vimeo always plays with its do-not-track option on, for every visitor.\nTurn on Load the player with the page for a page whos'
|
|
2778
2778
|
},
|
|
2779
2779
|
{
|
|
2780
2780
|
path: '/building-sites/besigner/video',
|
|
@@ -4083,7 +4083,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
4083
4083
|
title: 'Maintenance mode',
|
|
4084
4084
|
heading: 'Turn it on',
|
|
4085
4085
|
anchor: '#turn-it-on',
|
|
4086
|
-
text: '1. Open Admin → Error pages for the site — the same card that assigns your error pages. The switch takes every page of the site offline for every visitor, so the Admin area takes the Manage site settings permission, which a site\'s admins hold by default.\n2. Switch on Maintenance mode — show the 503 page at every address. It confirms with "Maintenance mode on — visitors see the 503 page".\n3. Visitors now see your 503 error page on every path.\n4. When you\'re done, switch it back off and the site returns.\nIf you haven\'t assigned a 503 · Maintenance page, maintenance mode still works — but visitors get Aglyn\'s plain built-in notice ("This site is undergoing maintenance. Please check back shortly.") rather than anything on-brand. Design and assign the 503 first.'
|
|
4086
|
+
text: '1. Open Admin → Error pages for the site — the same card that assigns your error pages. The switch takes every page of the site offline for every visitor, so the Admin area takes the Manage site settings permission, which a site\'s admins hold by default.\n2. Switch on Maintenance mode — show visitors the 503 page at every address. It confirms with "Maintenance mode on — visitors see the 503 page".\n3. Visitors now see your 503 error page on every path.\n4. When you\'re done, switch it back off and the site returns.\nIf you haven\'t assigned a 503 · Maintenance page, maintenance mode still works — but visitors get Aglyn\'s plain built-in notice ("This site is undergoing maintenance. Please check back shortly.") rather than anything on-brand. Design and assign the 503 first.'
|
|
4087
4087
|
},
|
|
4088
4088
|
{
|
|
4089
4089
|
path: '/building-sites/site-protection/maintenance-mode',
|
|
@@ -4804,7 +4804,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
4804
4804
|
title: 'Product catalog',
|
|
4805
4805
|
heading: 'Billing modes and subscriptions',
|
|
4806
4806
|
anchor: '#billing-modes-and-subscriptions',
|
|
4807
|
-
text: 'Each product\'s Billing setting picks how buyers pay:\n- One-time purchase (default) — a normal order.\n- Monthly / Yearly subscription — buyers subscribe instead of buying once; the product page prices as $X/mo or $X/yr, the buy button reads Subscribe, and an optional free trial (in days) can precede the first charge. An active subscription is what members-only content checks.\n- Both — buyer chooses — the product page shows a one-time / subscribe toggle (same price either way, at the interval you pick) and defaults to one-time. The choice is validated server-side against the product: a one-time sale here is a plain order, while the subscribe choice creates a recurring subscription exactly like a subscription-only product.\nSelling subscriptions (including the subscribe side of Both) requires a plan with recurring billing (Pro and up). Subscription billing applies to the product page\'s direct checkout — cart checkouts always charge one-time.\nWhether a subscription moves stock follows the product\'s Type. A physical subscription decrements one unit per paid cycle — the first charge and every renewal each create an order on the Subscription channel and take the box off the shelf, so the stock field stays live and low-stock alerts apply. A digital or service subscription never moves stock, and the stock field is disabled there; any number already saved is kept and shown, but it does not cap subscribers and will not change on its own. A saved 0 still stops new subscribers, so clear it (Clear stock on the notice in the editor) if that is not what you want. On a Both product the stock field stays live, because the one-time sales do decrement it.'
|
|
4807
|
+
text: 'Each product\'s Billing setting picks how buyers pay:\n- One-time purchase (default) — a normal order.\n- Monthly / Yearly subscription — buyers subscribe instead of buying once; the product page prices as $X/mo or $X/yr, the buy button reads Subscribe, and an optional free trial (in days) can precede the first charge. An active subscription is what members-only content checks.\n- Both — buyer chooses — the product page shows a one-time / subscribe toggle (same price either way, at the interval you pick) and defaults to one-time. The choice is validated server-side against the product: a one-time sale here is a plain order, while the subscribe choice creates a recurring subscription exactly like a subscription-only product.\nSelling subscriptions (including the subscribe side of Both) requires a plan with recurring billing (Pro and up). Subscription billing applies to the product page\'s direct checkout — cart checkouts always charge one-time.\nWhether a subscription moves stock follows the product\'s Type. A physical subscription decrements one unit per paid cycle — the first charge and every renewal each create an order on the Subscription channel and take the box off the shelf, so the stock field stays live and low-stock alerts apply. A digital or service subscription never moves stock, and the stock field is disabled there; any number already saved is kept and shown, but it does not cap subscribers and will not change on its own. A saved 0 still stops new subscribers, so clear it (Clear stock on the notice in the editor) if that is not what you want. On a Both product the stock field stays live, because the one-time sales do decrement it.\nYour subscribers {#subscriptions-list}\nProducts → Subscriptions lists every subscription on the site, newest first. Filter it by status: '
|
|
4808
4808
|
},
|
|
4809
4809
|
{
|
|
4810
4810
|
path: '/commerce-and-bookings/commerce/catalog',
|
|
@@ -5294,7 +5294,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
5294
5294
|
title: 'Fulfillment, returns and webhooks',
|
|
5295
5295
|
heading: 'Invoices and packing slips',
|
|
5296
5296
|
anchor: '#invoices',
|
|
5297
|
-
text: 'Invoice in the order\'s dialog has three choices:\n- Print invoice opens the order as a bill, ready to print: your business name, the date, who it is billed and shipped to, each line with its unit price, the subtotal, discount, shipping, tax and total, and anything refunded. Your store\'s receipt footer and terms address print at the foot.\n- Download PDF saves the same invoice as a PDF file in your site\'s look: your logo and contact details at the top, a band in your site\'s primary color, the invoice number, the order date and whether it is paid, then the lines and totals. A paid quote\'s invoice works the same way, with Included beside anything included at no charge.\n- Send invoice emails the invoice to your customer, with the PDF attached. See Send an invoice.\nThe PDF takes your logo and contact details from your site\'s settings, and its colors from your site\'s theme. Downloading it takes the Manage orders permission.\nSend an invoice {#send-invoice}\nSend invoice opens a short form: To (your customer\'s email, filled in from the order), Subject and Message. Your message is shown at the top of the email, in your words. The email goes out in your site\'s look, from your site, with the invoice attached as a PDF. Replies go to your site\'s contact email, or to you when the site has none.\nWhat the email says depends on whether the order is paid:\n- Unpaid: "Invoice #1042 from" your business, the invoice number, its date, the total and what is due, and a Pay button. The button opens the invoice on your own site, where your customer pays it by card. The same link is printed on the PDF.\n- Paid: the same invoice, marked paid on the day it was paid, for your customer\'s records. It has no button.\nOnce it\'s
|
|
5297
|
+
text: 'Invoice in the order\'s dialog has three choices:\n- Print invoice opens the order as a bill, ready to print: your business name, the date, who it is billed and shipped to, each line with its unit price, the subtotal, discount, shipping, tax and total, and anything refunded. Your store\'s receipt footer and terms address print at the foot.\n- Download PDF saves the same invoice as a PDF file in your site\'s look: your logo and contact details at the top, a band in your site\'s primary color, the invoice number, the order date and whether it is paid, then the lines and totals. A paid quote\'s invoice works the same way, with Included beside anything included at no charge.\n- Send invoice emails the invoice to your customer, with the PDF attached. See Send an invoice.\nThe PDF takes your logo and contact details from your site\'s settings, and its colors from your site\'s theme. Downloading it takes the Manage orders permission.\nSend an invoice {#send-invoice}\nSend invoice opens a short form: To (your customer\'s email, filled in from the order), Subject and Message. Your message is shown at the top of the email, in your words. The email goes out in your site\'s look, from your site, with the invoice attached as a PDF. Replies go to your site\'s contact email, or to you when the site has none.\nWhat the email says depends on whether the order is paid:\n- Unpaid: "Invoice #1042 from" your business, the invoice number, its date, the total and what is due, and a Pay button. The button opens the invoice on your own site, where your customer pays it by card or wallet, never buy-now-pay-later (processing is 2.9% + 30¢, see Payment methods). The same link is printed on the PDF.\n- Paid: the same invoice, marked paid on the day it was paid, for your customer\'s records. It has no button.\nOnce it\'s'
|
|
5298
5298
|
},
|
|
5299
5299
|
{
|
|
5300
5300
|
path: '/commerce-and-bookings/commerce/orders-and-returns',
|
|
@@ -5364,7 +5364,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
5364
5364
|
title: 'Commerce',
|
|
5365
5365
|
heading: 'Payment methods',
|
|
5366
5366
|
anchor: '#payment-methods',
|
|
5367
|
-
text: 'The Payment methods card, on Products → Payments, chooses what shoppers may pay with besides a card, once your Stripe account is connected on the Payments card. Cards are always on. Every other method is on unless you turn it off, except stablecoins, which you turn on. Stripe shows a method only on orders it suits: the right currency, an amount inside its limits, and a shopper in a country it serves.\n| Method | What the shopper needs | Limits |\n| Apple Pay | Safari on a Mac, iPhone or iPad with a card in Apple Wallet | Same as cards |\n| Google Pay | Chrome or an Android device with a card in Google Pay | Same as cards |\n| Link | A card or bank saved with Link | Same as cards |\n|
|
|
5367
|
+
text: 'The Payment methods card, on Products → Payments, chooses what shoppers may pay with besides a card, once your Stripe account is connected on the Payments card. Cards are always on. Every other method is on unless you turn it off, except stablecoins, which you turn on. Stripe shows a method only on orders it suits: the right currency, an amount inside its limits, and a shopper in a country it serves.\n| Method | What the shopper needs | Limits |\n| Apple Pay | Safari on a Mac, iPhone or iPad with a card in Apple Wallet | Same as cards |\n| Google Pay | Chrome or an Android device with a card in Google Pay | Same as cards |\n| Link | A card or bank saved with Link | Same as cards |\n| Cash App Pay | A US shopper with Cash App | USD only |\n| Amazon Pay | An Amazon account with a saved card | USD only |\n| Stablecoins | A crypto wallet holding USDC or another supported stablecoin | USD only, up to $10,000 |\nThe card only lists the methods the platform offers. A method missing from your card is not available for storefronts yet.\nNo checkout offers buy-now-pay-later. Klarna, Afterpay and Affirm are not offered anywhere a customer pays you: storefront checkout, bookings, reservation deposits, quotes, invoices, draft order links and the register\'s card link. Every method on the card costs Stripe no more than a card does, so the processing passed through on each sale is Stripe\'s card rate, 2.9% + 30¢ (see processing costs).\nAnyone holding Manage orders can read the card; changing it takes Manage payment methods, which a site\'s admins hold by default.\nUntil Stripe is connected, each method you have on reads Connect Stripe first, and a note at the top of the card links to the Payments card above it, where you connect. You can still choose your methods in the meantime; they show at chec'
|
|
5368
5368
|
},
|
|
5369
5369
|
{
|
|
5370
5370
|
path: '/commerce-and-bookings/commerce/overview',
|
|
@@ -5518,7 +5518,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
5518
5518
|
title: 'POS & reservations',
|
|
5519
5519
|
heading: 'Card readers',
|
|
5520
5520
|
anchor: '#card-readers',
|
|
5521
|
-
text: 'A card reader takes card payments at the counter: the customer taps, inserts or swipes, and the reader can ask for a tip. The register works with
|
|
5521
|
+
text: 'A card reader takes card payments at the counter: the customer taps, inserts or swipes, and the reader can ask for a tip. The register works with smart readers: the Touchscreen reader (S700) (and S710) and the Countertop reader (WisePOS E). Card readers are shown only when they are available for your store; when they are not, the POS devices card has no card reader controls and the register has no Card reader button.\nTo add a reader:\n1. On the reader, open Settings and choose Generate pairing code.\n2. In the console, open Products → Point of sale → POS devices and choose Add card reader.\n3. Enter the registration code the reader shows, give the reader a name (such as "Front counter reader") and, optionally, pick the register it belongs to. A reader left on Any register can be used from every register.\n4. The first reader you add asks for the store\'s address — where the reader is used. Stripe sets the reader up for that country.\nEach reader is listed with its register and an Online or Offline status, and can be renamed, moved to another register, or removed. A removed reader has to be registered again with a new code to be used. A reader must be switched on and connected to the internet to take a payment; the register warns you when the selected reader looks offline. See POS hardware for setup notes.\nTrying it in test mode In test mode, add a reader with the code simulated-wpe to get Stripe\'s simulated reader. While a payment waits on it, the register shows Simulate tap to complete it with a test card.'
|
|
5522
5522
|
},
|
|
5523
5523
|
{
|
|
5524
5524
|
path: '/commerce-and-bookings/commerce/pos-and-reservations',
|
|
@@ -5553,7 +5553,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
5553
5553
|
title: 'POS hardware',
|
|
5554
5554
|
heading: '',
|
|
5555
5555
|
anchor: '',
|
|
5556
|
-
text: 'POS hardware\nThe register runs in a browser, so it works on an iPad, an Android tablet, a laptop or a desktop at the counter. This page covers the hardware around it: a card reader, a customer display, a receipt printer, a kitchen printer, the cash drawer, barcode scanners and a label printer.\nPlan availability POS hardware comes with POS, on Pro and above. There is no extra charge for printers, scanners or customer displays.'
|
|
5556
|
+
text: 'POS hardware\nThe register runs in a browser, so it works on an iPad, an Android tablet, a laptop or a desktop at the counter. This page covers the hardware around it: a card reader, a customer display, a receipt printer, a kitchen printer, the cash drawer, barcode scanners and a label printer.\nPlan availability POS hardware comes with POS, on Pro and above. There is no extra charge for printers, scanners or customer displays. You can buy card readers from Aglyn on any plan, and add POS when you set them up.'
|
|
5557
5557
|
},
|
|
5558
5558
|
{
|
|
5559
5559
|
path: '/commerce-and-bookings/commerce/pos-hardware',
|
|
@@ -5567,14 +5567,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
5567
5567
|
title: 'POS hardware',
|
|
5568
5568
|
heading: 'Card readers',
|
|
5569
5569
|
anchor: '#card-readers',
|
|
5570
|
-
text: 'The register takes card-present payments on
|
|
5570
|
+
text: 'The register takes card-present payments on these smart readers:\n| Reader | Notes |\n| Touchscreen reader (S700) / Touchscreen reader, 4G-capable (S710) | Android-based smart reader for the countertop or the hand. |\n| Countertop reader (T600) | Countertop smart reader, on Wi-Fi or on Ethernet with the hub. |\n| Countertop reader (WisePOS E) | Countertop smart reader. |\nThey are smart readers: each one takes payments over its own internet connection, so it does not need to be plugged into or paired by Bluetooth with the device the register runs on. Card readers are shown in the console only when they are available for your store.\nGetting a reader\nReaders take payments through Aglyn\'s Stripe account, which pays your store out, so a reader is registered to your store in Aglyn rather than in a Stripe Dashboard of your own. Any supported reader can be added with the pairing code it shows, including one that was registered somewhere else before: generating a new pairing code on the reader and adding it here moves it to your store.\nWhere the Hardware card is available, you can buy a reader from Aglyn instead and have it shipped to you; see Buy a reader from Aglyn.\nStripe sells its readers through the Terminal hardware shop in the Stripe Dashboard. If you buy one there with a Stripe account of your own, add it here with a fresh pairing code from the reader, as above. Use the pairing code rather than the reader\'s serial number or order number: those two only register a reader to the Stripe account that ordered it.\nSetting one up\n1. Charge the reader and switch it on. Leave it plugged in and on, even when not in use, so it receives software updates.\n2. Connect it to the internet: Wi-Fi from the reader\'s Settings, or Ethernet through the optional dock or hub. Stripe\'s setup guides f'
|
|
5571
5571
|
},
|
|
5572
5572
|
{
|
|
5573
5573
|
path: '/commerce-and-bookings/commerce/pos-hardware',
|
|
5574
5574
|
title: 'POS hardware',
|
|
5575
5575
|
heading: 'Buy a reader from Aglyn',
|
|
5576
5576
|
anchor: '#buy-a-reader-from-aglyn',
|
|
5577
|
-
text: 'Rolling out Buying readers from Aglyn is not yet available on aglyn.com-hosted workspaces. Until it is, no Hardware card appears on Products → Point of sale; buy a reader from Stripe and add it with its pairing code, as in Getting a reader.\nThe Hardware card on Products → Point of sale sells
|
|
5577
|
+
text: 'Rolling out Buying readers from Aglyn is not yet available on aglyn.com-hosted workspaces. Until it is, no Hardware card appears on Products → Point of sale; buy a reader from Stripe and add it with its pairing code, as in Getting a reader.\nThe Hardware card on Products → Point of sale sells card readers and their accessories. Aglyn sets each reader up for you and ships your order to you. Because Aglyn sells it, the reader is ready to take payments through Aglyn.\nWhat\'s on offer\n| Item | What it\'s for |\n| Touchscreen reader, 4G-capable (S710) | Handheld for events and parking lots, on Wi-Fi. 4G is a separate service, billed monthly for each reader, where it\'s offered; see 4G for the S710 reader |\n| Touchscreen reader (S700) | Handheld or countertop reader on Wi-Fi |\n| Countertop reader (T600) | Countertop reader on Wi-Fi, or on Ethernet with the hub |\n| Countertop reader (WisePOS E) | Countertop reader on Wi-Fi |\n| Pocket reader (M2) | Pairs with the Aglyn POS app on your phone or tablet by Bluetooth |\n| Charging docks for the S700/S710, the WisePOS E and the M2, and the M2 mount | Keep a reader charged and in place at the counter |\n| A hub for the S700, S710 and T600 | Connects the reader to Ethernet and power |\n| A case for the S700/S710, and spare cables and chargers | Protect a handheld reader, or replace a lost cable or charger |\nThe card shows only what is available to order, with its price. An item that Aglyn\'s own online store also sells costs the same on the card as on the store\'s product page.\nOn any plan. You can buy readers whatever your plan. A reader takes payments at the register, which comes with the point of sale on Pro and above: registers that ring up sales, card payments on your readers, cash with change due, receipts and shift reports. Until your wo'
|
|
5578
5578
|
},
|
|
5579
5579
|
{
|
|
5580
5580
|
path: '/commerce-and-bookings/commerce/pos-hardware',
|
|
@@ -5896,7 +5896,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
5896
5896
|
title: 'Quotes',
|
|
5897
5897
|
heading: 'How your customer pays',
|
|
5898
5898
|
anchor: '#paying',
|
|
5899
|
-
text: 'Pay charges the quote as you saved it, priced from its items, discount, shipping and tax. Your customer pays on the page itself, or on a Stripe payment page that brings them back to the quote afterward. Their email is filled in from the quote. When the quote charges shipping, they\'re asked where it ships, starting from the quote\'s ship-to. Under Stripe Tax, the tax is worked out from that address when they pay.\nIf you edit the quote while your customer has it open, Pay asks them to reload the page first, so nobody pays for a version they haven\'t seen. Editing a quote, deleting it or replacing its link also closes any payment your customer had started for it.\nPaying needs a connected Stripe account and a decision about sales tax. Until your store has both, the quote page has no Pay button. When Stripe isn\'t ready, the page says your business can\'t take payments online right now and asks the customer to contact you to pay; otherwise it asks them to contact you to pay.\nYou hear about it first, in the console. While Stripe or the sales tax choice stands in the way, a quote\'s editor, its Pay link section, the Send quote form and the Send invoice form say Customers can\'t pay this quote online yet (the Send invoice form says invoice) and name what\'s missing, each with a button to fix it: Open Payments to connect Stripe, Open Taxes to choose how your store handles sales tax, or a reminder to save the quote
|
|
5899
|
+
text: 'Pay charges the quote as you saved it, priced from its items, discount, shipping and tax. Your customer pays on the page itself, or on a Stripe payment page that brings them back to the quote afterward. Their email is filled in from the quote. When the quote charges shipping, they\'re asked where it ships, starting from the quote\'s ship-to. Under Stripe Tax, the tax is worked out from that address when they pay.\nYour customer pays by card, or with a wallet you leave on in Payment methods: Apple Pay, Google Pay, Link, Cash App Pay, Amazon Pay, or stablecoins once you turn them on. A quote never offers Klarna, Afterpay or Affirm, as no checkout does. Its processing is Stripe\'s card rate, 2.9% + 30¢, passed through at cost beside your plan\'s platform fee. An invoice pays the same way.\nIf you edit the quote while your customer has it open, Pay asks them to reload the page first, so nobody pays for a version they haven\'t seen. Editing a quote, deleting it or replacing its link also closes any payment your customer had started for it.\nPaying needs a connected Stripe account and a decision about sales tax. Until your store has both, the quote page has no Pay button. When Stripe isn\'t ready, the page says your business can\'t take payments online right now and asks the customer to contact you to pay; otherwise it asks them to contact you to pay.\nYou hear about it first, in the console. While Stripe or the sales tax choice stands in the way, a quote\'s editor, its Pay link section, the Send quote form and the Send invoice form say Customers can\'t pay this quote online yet (the Send invoice form says invoice) and name what\'s missing, each with a button to fix it: Open Payments to connect Stripe, Open Taxes to choose how your store handles sales tax, or a reminder to save the quote a'
|
|
5900
5900
|
},
|
|
5901
5901
|
{
|
|
5902
5902
|
path: '/commerce-and-bookings/commerce/quotes-and-proofs',
|
|
@@ -8220,7 +8220,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
8220
8220
|
title: 'Datasets & Dynamic Content',
|
|
8221
8221
|
heading: 'Where you manage datasets',
|
|
8222
8222
|
anchor: '#organization-data-page',
|
|
8223
|
-
text: 'The organization Data page manages every dataset in the workspace in one place — create a dataset, edit its schema, add and import records — and sets where new datasets start shared. A site\'s own Data page edits the same datasets, limited to the ones shared with that site.'
|
|
8223
|
+
text: 'The organization Data page manages every dataset in the workspace in one place — create a dataset, edit its schema, add and import records — and sets where new datasets start shared. A site\'s own Data page edits the same datasets, limited to the ones shared with that site. A link to a dataset the site isn\'t shared with opens a note saying so, not the dataset.\nBoth pages list the datasets down the left, one tab each, the way Settings lists its sections:\n- Each tab shows the dataset\'s name and, under it, who it\'s shared with and how many fields it has (Bakery only · 5 fields), so two datasets with the same name are easy to tell apart. Wherever else you pick a dataset (a repeat or form in the page editor, a record page, an automation step, a join collection or a reference field\'s target), two with the same name are told apart the same way: Services · Bakery only, then the field count if that still matches.\n- Search datasets by name above the list narrows it to the names that start with what you type.\n- When there are more than ten, the list is grouped by who each dataset is shared with, and on the organization page a Shared with filter shows only the datasets one site can use. The list scrolls inside its card, and Show more datasets loads the next hundred.\n- Each dataset has its own address (…/data/ ), so you can bookmark or share a link to it.\nThe open dataset fills the right: its name with Add record, Schema, Import, Export and Delete, the facts about it (shared with, fields, records, source and created date), and its records table. Add dataset and Add join collection are at the top of the page.\nChoose View on a record, or the record\'s row, to open it on its own page (…/data/ /records/ ): a link back to its dataset, its record ID and dataset, every field with its value, '
|
|
8224
8224
|
},
|
|
8225
8225
|
{
|
|
8226
8226
|
path: '/content-and-data/datasets/overview',
|
|
@@ -9326,7 +9326,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
9326
9326
|
title: 'Manifests, trust lifecycle & environment',
|
|
9327
9327
|
heading: 'Environment variables',
|
|
9328
9328
|
anchor: '#environment-variables',
|
|
9329
|
-
text: '| Variable | Runtime | Purpose |\n| NEXTPUBLICPLUGINORIGIN | client + server | Dedicated plugin origin: serves /load (sandbox) and /artifacts/... (realm fetches) |\n| PLUGINARTIFACTSBASE | server | Optional server-side artifacts base override |\n| PLUGINARTIFACTSBUCKET | console server | Isolated bucket the publish flow writes to |\n| NEXTPUBLICPLUGINTRUSTPUBLICKEY | client | Ed25519 public key (base64 raw); when set, client realm loads require valid signatures |\n| PLUGINTRUSTPUBLICKEY | server | Same key, server loaders (mandatory there) |\n| PLUGINTRUSTPRIVATEKEY | console server only | Signing key (base64 PKCS8 DER) for the staff sign-plugin route |\n| PLUGINREMOTESERVER | server | enabled turns on remote server bundles (default off everywhere) |\n| PLUGINREMOTESERVERBUNDLES | server | Per-deploy listingId@version allowlist |\n| PLUGINJOBSSECRET | tenant server | Shared secret the scheduler sends to /api/plugins/run-jobs |\n| NEXTPUBLICPLUGINDEVBUNDLES | client, dev only | Unverified localhost bundle loading for the authoring loop; dead code in production builds |\n| PLUGINDEVMANIFESTS | server, dev only | Comma-separated manifest file paths for the dev loop\'s bundles. Compose reads their functionBindings from disk, because a dev bundle has no install to carry them; never read in production builds |'
|
|
9329
|
+
text: '| Variable | Runtime | Purpose |\n| NEXTPUBLICPLUGINORIGIN | client + server | Dedicated plugin origin: serves /load (sandbox) and /artifacts/... (realm fetches) |\n| PLUGINARTIFACTSBASE | server | Optional server-side artifacts base override |\n| PLUGINARTIFACTSBUCKET | console server | Isolated bucket the publish flow writes to |\n| NEXTPUBLICPLUGINTRUSTPUBLICKEY | client | Ed25519 public key (base64 raw); when set, client realm loads require valid signatures |\n| PLUGINTRUSTPUBLICKEY | server | Same key, server loaders (mandatory there) |\n| PLUGINTRUSTPRIVATEKEY | console server only | Signing key (base64 PKCS8 DER) for the staff sign-plugin route |\n| PLUGINREMOTESERVER | server | enabled turns on remote server bundles (default off everywhere) |\n| PLUGINREMOTESERVERBUNDLES | server | Per-deploy listingId@version allowlist |\n| PLUGINJOBSSECRET | tenant server | Shared secret the scheduler sends to /api/plugins/run-jobs |\n| PLUGINCONNECTIONSTOKENKEY | console server only | 32 random bytes, base64 (NEW,OLD to rotate): seals every publisher\'s OAuth app credentials and every site\'s connection tokens. Unset, no declared connection can be connected |\n| NEXTPUBLICPLUGINDEVBUNDLES | client, dev only | Unverified localhost bundle loading for the authoring loop; dead code in production builds |\n| PLUGINDEVMANIFESTS | server, dev only | Comma-separated manifest file paths for the dev loop\'s bundles. Compose reads their functionBindings from disk, because a dev bundle has no install to carry them; never read in production builds |'
|
|
9330
9330
|
},
|
|
9331
9331
|
{
|
|
9332
9332
|
path: '/developers/plugins/reference/manifest-and-envs',
|
|
@@ -10152,7 +10152,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10152
10152
|
title: 'Environment variables',
|
|
10153
10153
|
heading: 'Plugins and the sandbox',
|
|
10154
10154
|
anchor: '#plugins',
|
|
10155
|
-
text: '| Variable | Need | When | Value |\n| PLUGINARTIFACTSBUCKET | Feature | Runtime | The separate GCS bucket holding executable plugin bundles — the code refuses to store executable code in the app bucket. Unset, plugin publishing and artifact serving both answer 501. A bare bucket name. Note the bucket is invisible to the Firebase console; manage it in the Google Cloud console. |\n| PLUGINARTIFACTSBASE | Optional | Runtime | Origin the server-side remote-bundle loader fetches from. Falls back to NEXTPUBLICPLUGINORIGIN. Only relevant with remote server bundles enabled. |\n| NEXTPUBLICPLUGINORIGIN | Feature | Build | Full origin the plugin sandbox iframe and bundles are served from, and the entry added to the CSP frame-src. Must be a different origin from the app — the cross-origin boundary is the sandbox. Unset, realm plugins do not load and installed executable plugins render as nothing, because the CSP has no entry for them. |\n| PLUGINTRUSTPRIVATEKEY | Feature | Runtime | Signs realm trust grants. Base64 PKCS8 DER Ed25519, generated by tools/scripts/generate-plugin-trust-key.mjs. Unset, the grant action answers 501. Console only — never deploy it to a tenant runtime. |\n| PLUGINTRUSTPUBLICKEY | Feature | Runtime | The server-side verification key, base64 raw Ed25519. Required with remote server bundles enabled; unset there, no bundle loads at all — it fails closed rather than degrading to a hash check. |\n| NEXTPUBLICPLUGINTRUSTPUBLICKEY | Feature | Build | The same public key again, for browser-side verification of realm bundles. A mismatch with the server-side name refuses every bundle. |\n| PLUGINJOBSSECRET | Feature | Runtime | See Secrets. |\
|
|
10155
|
+
text: '| Variable | Need | When | Value |\n| PLUGINARTIFACTSBUCKET | Feature | Runtime | The separate GCS bucket holding executable plugin bundles — the code refuses to store executable code in the app bucket. Unset, plugin publishing and artifact serving both answer 501. A bare bucket name. Note the bucket is invisible to the Firebase console; manage it in the Google Cloud console. |\n| PLUGINARTIFACTSBASE | Optional | Runtime | Origin the server-side remote-bundle loader fetches from. Falls back to NEXTPUBLICPLUGINORIGIN. Only relevant with remote server bundles enabled. |\n| NEXTPUBLICPLUGINORIGIN | Feature | Build | Full origin the plugin sandbox iframe and bundles are served from, and the entry added to the CSP frame-src. Must be a different origin from the app — the cross-origin boundary is the sandbox. Unset, realm plugins do not load and installed executable plugins render as nothing, because the CSP has no entry for them. |\n| PLUGINTRUSTPRIVATEKEY | Feature | Runtime | Signs realm trust grants. Base64 PKCS8 DER Ed25519, generated by tools/scripts/generate-plugin-trust-key.mjs. Unset, the grant action answers 501. Console only — never deploy it to a tenant runtime. |\n| PLUGINTRUSTPUBLICKEY | Feature | Runtime | The server-side verification key, base64 raw Ed25519. Required with remote server bundles enabled; unset there, no bundle loads at all — it fails closed rather than degrading to a hash check. |\n| NEXTPUBLICPLUGINTRUSTPUBLICKEY | Feature | Build | The same public key again, for browser-side verification of realm bundles. A mismatch with the server-side name refuses every bundle. |\n| PLUGINJOBSSECRET | Feature | Runtime | See Secrets. |\n| PLUGINCONNECTIONSTOKENKEY | Feature | Runtime | 32 random bytes, base64 — openssl rand -base64 32. Seals every marketplace plugin '
|
|
10156
10156
|
},
|
|
10157
10157
|
{
|
|
10158
10158
|
path: '/developers/self-hosting-environment',
|
|
@@ -10691,7 +10691,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10691
10691
|
title: 'Build & publish a survey',
|
|
10692
10692
|
heading: '1. Create the dataset',
|
|
10693
10693
|
anchor: '#1-create-the-dataset',
|
|
10694
|
-
text: 'Datasets belong to your organization, so every site can share them. Open the organization Data page (or any site\'s Data page — both edit the same data).\n1. Choose Add dataset. In the New dataset dialog give it a Name (say Survey responses) and a comma-separated list of Fields (satisfaction, visit, topics, comments) — at least one, or Create stays disabled. Create it.\n2.
|
|
10694
|
+
text: 'Datasets belong to your organization, so every site can share them. Open the organization Data page (or any site\'s Data page — both edit the same data).\n1. Choose Add dataset. In the New dataset dialog give it a Name (say Survey responses) and a comma-separated list of Fields (satisfaction, visit, topics, comments) — at least one, or Create stays disabled. Create it.\n2. The new dataset opens as its own tab in the Datasets list on the left. Open Schema. The Schema dialog lists each field with its display name, generated field id, and a type chip.\n3. Use Add field / Edit to type the fields properly:\n- satisfaction → type Integer. A form stores every value as text, so the rating lands as "4"; the Data page\'s = filter still matches it as the number 4.\n- visit → type Text (one radio choice).\n- topics → type Text (ticked checkboxes arrive joined with , ).\n- comments → type Text.\n4. Save schema.\nEach field\'s Display name is what you see in dialogs and table headers; the field id next to it (a slug generated once from the display name) is the stable key records store values under — the key {{item.fieldId}} bindings reference, and what the Maps to schema field picker on a form\'s input stores. Renaming the display name later never changes the id.\nModel first A clean schema now makes everything downstream typed: the record editor renders the right input per field and imports are validated. Form submissions are the exception — they are stored as text without validation, so a submitted value can disagree with its field\'s type. See the datasets deep-dive for the full type system.'
|
|
10695
10695
|
},
|
|
10696
10696
|
{
|
|
10697
10697
|
path: '/guides/build-and-publish-a-survey',
|
|
@@ -11104,14 +11104,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
11104
11104
|
title: 'Member accounts',
|
|
11105
11105
|
heading: '3. Design an account page',
|
|
11106
11106
|
anchor: '#3-design-an-account-page',
|
|
11107
|
-
text: 'For a richer home for members, add the Customer account block (found in the Commerce group of the element picker) to a page — conventionally at the slug account, which is where commerce gates point anonymous visitors:\n- Signed out, the block shows sign-in / create-account tabs in place, with your configurable Signed-out heading above.\n- Signed in, it renders the member\'s profile with Sign out, plus sections for Orders (with status chips and tracking), Subscriptions (each with a Manage button that opens the Stripe Billing Portal), Downloads (digital purchases and license keys), and Addresses.\nGive the account page the same chrome as the rest of your site by binding a shared layout: in the page\'s Properties, pick one under Shared layout — the appbar/footer are then maintained once for every bound page (see pages & layouts).'
|
|
11107
|
+
text: 'For a richer home for members, add the Customer account block (found in the Commerce group of the element picker) to a page — conventionally at the slug account, which is where commerce gates point anonymous visitors:\n- Signed out, the block shows sign-in / create-account tabs in place, with your configurable Signed-out heading above.\n- Signed in, it renders the member\'s profile with Sign out, plus sections for Orders (with status chips and tracking), Subscriptions (each with its price, the next date that matters — Renews, Trial ends, Ends after the member cancels, or Ended — a Manage button that opens the Stripe Billing Portal, and Billing history with each paid invoice and a link to Stripe\'s copy), Downloads (digital purchases and license keys), and Addresses.\nGive the account page the same chrome as the rest of your site by binding a shared layout: in the page\'s Properties, pick one under Shared layout — the appbar/footer are then maintained once for every bound page (see pages & layouts).'
|
|
11108
11108
|
},
|
|
11109
11109
|
{
|
|
11110
11110
|
path: '/guides/member-accounts',
|
|
11111
11111
|
title: 'Member accounts',
|
|
11112
11112
|
heading: '4. Gate pages to members',
|
|
11113
11113
|
anchor: '#4-gate-screens-to-members',
|
|
11114
|
-
text: 'To restrict a page: open its version view, and in the Page Access card set Visibility to Members only, then publish. Anonymous visitors get a "This page is for members" prompt with sign-in / create-account links instead of the content (or your designed 401 error page if you\'ve assigned one). The page\'s content is never in the anonymous page source — members fetch it with their session after sign-in.\nFor one-off protection without accounts, use a per-page password instead.\nGate part of a page, not all of it\nThree blocks gate a region instead of a whole page, so one public page can hold both the pitch and the members-only part:\n- Members gate — a container that shows its children only to entitled members. Everyone else sees the Teaser text and a call-to-action button you point wherever joining starts. Required product id names the product whose buyers or subscribers get in; leave it blank to accept any live subscription.\n- Members video — plays one of a product\'s videos for members entitled to that product, and resumes where each member left off. Video number picks which one (the first is 0), and Locked text is what sits over the poster frame for everyone else. The video file is private and every link a member\'s player gets expires, so a link copied out of the page stops working on its own; see Members videos are private files.\n- Member feed — posts only entitled members can see, newest first, with a Heading, Empty text for when there are none, and a cap on how many show. Non-members never receive the posts, not merely a hidden copy of
|
|
11114
|
+
text: 'To restrict a page: open its version view, and in the Page Access card set Visibility to Members only, then publish. Anonymous visitors get a "This page is for members" prompt with sign-in / create-account links instead of the content (or your designed 401 error page if you\'ve assigned one). The page\'s content is never in the anonymous page source — members fetch it with their session after sign-in.\nFor one-off protection without accounts, use a per-page password instead.\nGate part of a page, not all of it\nThree blocks gate a region instead of a whole page, so one public page can hold both the pitch and the members-only part:\n- Members gate — a container that shows its children only to entitled members. Everyone else sees the Teaser text and a call-to-action button you point wherever joining starts. Required product id names the product whose buyers or subscribers get in; leave it blank to accept any live subscription.\n- Members video — plays one of a product\'s videos for members entitled to that product, and resumes where each member left off. Video number picks which one (the first is 0), and Locked text is what sits over the poster frame for everyone else. The video file is private and every link a member\'s player gets expires, so a link copied out of the page stops working on its own; see Members videos are private files. To share one video library across several plans, add the videos to one product and pick the other plans under Members videos are also open to buyers of in that product\'s editor. Buyers and active subscribers of any of them can then watch.\n- Member feed — posts only entitled members can see, newest first, with a Heading, Empty text for when there are none, and a cap on how many show. Non-members never receive the posts, not merely a hidden copy of t'
|
|
11115
11115
|
},
|
|
11116
11116
|
{
|
|
11117
11117
|
path: '/guides/member-accounts',
|
|
@@ -13218,7 +13218,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
13218
13218
|
title: 'Members-only areas',
|
|
13219
13219
|
heading: 'Manage your members',
|
|
13220
13220
|
anchor: '#manage-your-members',
|
|
13221
|
-
text: 'The site\'s Users page lists everyone who signed up on your published site — paged, newest first. The search box finds a member by the start of any word of their name or email address, and Filters in the table\'s toolbar narrows the list by email, name, join date or Status (Active or Suspended). They add up — except that a Name contains filter and a search can\'t stand together, and the list says which it set aside — across every member rather than the page on screen, because the query that reads the list answers them all. The member guide names each filter\'s operators. See Filter and search a list. Click a member to open their detail drawer:\n- Profile — email, display name, join date, and saved addresses.\n- Order history — the member\'s payment records, newest first: order number, status, total, and date, plus the Stripe payment reference and any refunded amount. Order history takes the See orders and webhooks permission, which a site\'s admins and editors hold by default.\n- Subscriptions — active and past storefront subscriptions with their renewal date.\n- Lifetime purchases — everything the member actually paid: charged order totals minus refunds (pending and canceled orders don\'t count).\nSuspend or reactivate a member\nFrom the drawer you can suspend a member (with a confirmation). A suspended member:\n- can no longer sign in on your published site — they see a clear "account suspended" message;\n- is signed out the next time their account page loads;\n- keeps all orders, subscriptions, and history — nothing is deleted.\nReactivate restores access with the member\'s existing password. The member list shows each account\'s Active/Suspended status at a glance.'
|
|
13221
|
+
text: 'The site\'s Users page lists everyone who signed up on your published site — paged, newest first. The search box finds a member by the start of any word of their name or email address, and Filters in the table\'s toolbar narrows the list by email, name, join date or Status (Active or Suspended). They add up — except that a Name contains filter and a search can\'t stand together, and the list says which it set aside — across every member rather than the page on screen, because the query that reads the list answers them all. The member guide names each filter\'s operators. See Filter and search a list. Click a member to open their detail drawer:\n- Profile — email, display name, join date, and saved addresses.\n- Order history — the member\'s payment records, newest first: order number, status, total, and date, plus the Stripe payment reference and any refunded amount. Order history takes the See orders and webhooks permission, which a site\'s admins and editors hold by default.\n- Subscriptions — active and past storefront subscriptions with their renewal date. Like order history, it takes the See orders and webhooks permission.\n- Lifetime purchases — everything the member actually paid: charged order totals minus refunds (pending and canceled orders don\'t count).\nSuspend or reactivate a member\nFrom the drawer you can suspend a member (with a confirmation). A suspended member:\n- can no longer sign in on your published site — they see a clear "account suspended" message;\n- is signed out the next time their account page loads;\n- keeps all orders, subscriptions, and history — nothing is deleted.\nReactivate restores access with the member\'s existing password. The member list shows each account\'s Active/Suspended status at a glance.'
|
|
13222
13222
|
},
|
|
13223
13223
|
{
|
|
13224
13224
|
path: '/workspace-and-billing/teams-and-roles/members-only',
|