@aglyn/aglyn 1.4.0 → 1.6.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/business-details.d.ts +93 -0
- package/src/lib/app-utils/business-details.js +145 -0
- package/src/lib/app-utils/business-details.js.map +1 -0
- package/src/lib/app-utils/business-profile.d.ts +20 -3
- package/src/lib/app-utils/business-profile.js +31 -7
- package/src/lib/app-utils/business-profile.js.map +1 -1
- package/src/lib/app-utils/content-authors.d.ts +2 -0
- package/src/lib/app-utils/content-authors.js.map +1 -1
- package/src/lib/app-utils/docs-help-sections.generated.js +0 -1
- package/src/lib/app-utils/docs-help-sections.generated.js.map +1 -1
- package/src/lib/app-utils/docs-help.generated.js +0 -1
- package/src/lib/app-utils/docs-help.generated.js.map +1 -1
- package/src/lib/app-utils/docs-index.generated.js +15 -15
- package/src/lib/app-utils/docs-index.generated.js.map +1 -1
- package/src/lib/app-utils/health-report.d.ts +39 -0
- package/src/lib/app-utils/health-report.js +41 -0
- package/src/lib/app-utils/health-report.js.map +1 -1
- package/src/lib/app-utils/host-tokens.d.ts +53 -11
- package/src/lib/app-utils/host-tokens.js +173 -18
- package/src/lib/app-utils/host-tokens.js.map +1 -1
- package/src/lib/app-utils/site-email-chrome.js +3 -0
- package/src/lib/app-utils/site-email-chrome.js.map +1 -1
- package/src/lib/app-utils/site-entity-json-ld.js +17 -2
- package/src/lib/app-utils/site-entity-json-ld.js.map +1 -1
- package/src/lib/app-utils/weekly-summary.d.ts +15 -4
- package/src/lib/app-utils/weekly-summary.js +76 -21
- package/src/lib/app-utils/weekly-summary.js.map +1 -1
- package/src/lib/plugin-manager/plugin-figures.d.ts +22 -2
- package/src/lib/plugin-manager/plugin-figures.js +5 -0
- package/src/lib/plugin-manager/plugin-figures.js.map +1 -1
|
@@ -394,7 +394,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
394
394
|
title: 'Build from Assist chat',
|
|
395
395
|
heading: 'What one request can build',
|
|
396
396
|
anchor: '#what-it-can-build',
|
|
397
|
-
text: 'One message can ask for any mix of:\n- pages: home, about, services, contact, pricing, a landing page;\n- a header and footer shared by the pages;\n- a form: a contact form, a quote request, a sign-up form;\n- a reusable component: a card or block placed on several pages;\n- an email design, such as a welcome, a reply or an announcement, and an email campaign, drafted and left unsent;\n- a page template for blog posts, products or authors;\n- an automation: when a form is sent, do something;\n- a site function that works out a value, such as a price or a quote, and site variables, such as a
|
|
397
|
+
text: 'One message can ask for any mix of:\n- pages: home, about, services, contact, pricing, a landing page;\n- a header and footer shared by the pages;\n- a form: a contact form, a quote request, a sign-up form;\n- a reusable component: a card or block placed on several pages;\n- an email design, such as a welcome, a reply or an announcement, and an email campaign, drafted and left unsent;\n- a page template for blog posts, products or authors;\n- an automation: when a form is sent, do something;\n- a site function that works out a value, such as a price or a quote, and site variables, such as a launch date kept in one place. Your business\'s name, phone, email, address and social links never need one: pages use them from Business details;\n- products to sell, with a description, tags and options;\n- a booking service visitors can book online, with its length, hours and price;\n- events on the site\'s calendar, each with its date and time, place, description and a cover photo, published so the Event List on your pages shows them. They need the Event Calendar add-on. See Events Calendar;\n- an announcement bar or a popup;\n- an A/B test of a page or of an email\'s subject line;\n- a funnel that counts visits from one step to the next;\n- CRM setup: a deal pipeline with its stages, custom fields on contacts, companies, deals or leads, and new values for a picklist such as lead status or source. These are saved straight to your CRM, as they are when you set them up yourself;\n- a change to a page or layout the site already has, alongside the rest of a request, saved into its draft, which visitors do not see until you publish it. A change to one page on its own needs no plan: see Change a page;\n- redirects: send an old address to a page you have, change where a redirect goes, or stop one, such as '
|
|
398
398
|
},
|
|
399
399
|
{
|
|
400
400
|
path: '/ai/assist-builds',
|
|
@@ -604,28 +604,28 @@ export const DOCS_SECTION_INDEX = [
|
|
|
604
604
|
title: 'Business profile',
|
|
605
605
|
heading: 'Where to edit it',
|
|
606
606
|
anchor: '#where-to-edit-it',
|
|
607
|
-
text: 'Open the site, go to Setup → Business profile. The page has three cards:\n- Business
|
|
607
|
+
text: 'Open the site, go to Setup → Business profile. The page has three cards:\n- Business details: your business name, slogan, phone, email, address and social links, entered once for your pages, emails and search listings alike. See Business details.\n- Business profile: see the Business profile card.\n- What Aglyn AI learned: the preferences it took from edits you applied.'
|
|
608
608
|
},
|
|
609
609
|
{
|
|
610
610
|
path: '/ai/business-profile',
|
|
611
611
|
title: 'Business profile',
|
|
612
612
|
heading: 'The Business profile card',
|
|
613
613
|
anchor: '#the-business-profile-card',
|
|
614
|
-
text: 'The Business profile card holds what Aglyn AI writes for:\n- What the business does, in a sentence or two;\n- Services, one per line, up to 12;\n- Who it is for
|
|
614
|
+
text: 'The Business profile card holds what Aglyn AI writes for:\n- What the business does, in a sentence or two;\n- Services, one per line, up to 12;\n- Who it is for;\n- Tone of voice: Friendly and warm, Professional and clear, Playful and upbeat, Premium and refined, or Plain and direct, and Notes on tone for anything else;\n- Year founded, as four digits, such as 2015. An About page or a "Since" line uses it instead of leaving a gap where the year would go.\nAglyn AI reads it on every job for the site and never replaces what you write here.\nThe area you serve is not on this card: Aglyn AI reads it from Areas served on Setup → SEO → Local business, the one place it is entered.'
|
|
615
615
|
},
|
|
616
616
|
{
|
|
617
617
|
path: '/ai/business-profile',
|
|
618
618
|
title: 'Business profile',
|
|
619
619
|
heading: 'Where the values come from',
|
|
620
620
|
anchor: '#where-the-values-come-from',
|
|
621
|
-
text: 'When a site is started with Aglyn AI, the profile is filled from your answers to the guided start, including the Year founded from More details, and from what the plan wrote about the business. Each field says where its value came from:\n- Your answers when the site was started, or Suggested by Aglyn AI: a suggestion. Edit it and it becomes yours.\n- An empty field that Aglyn AI still has a value for says so: the description in your SEO settings, or the workspace\'s default.\nWhat you type is never replaced. A later job can fill an empty field, but it never overwrites one you wrote, and a field you cleared stays clear.\nWorkspace defaults {#workspace-defaults}\nSettings → Profile has a Business profile defaults card. A site uses those values wherever its own profile is empty, so a workspace that runs many sites for one business writes them once. Only managers can change them. The year founded is set on each site\'s own card.'
|
|
621
|
+
text: 'When a site is started with Aglyn AI, the profile is filled from your answers to the guided start, including the Year founded from More details, and from what the plan wrote about the business. Each field says where its value came from:\n- Your answers when the site was started, or Suggested by Aglyn AI: a suggestion. Edit it and it becomes yours.\n- An empty field that Aglyn AI still has a value for says so: the description in your SEO settings, or the workspace\'s default.\nWhat you type is never replaced. A later job can fill an empty field, but it never overwrites one you wrote, and a field you cleared stays clear.\nWorkspace defaults {#workspace-defaults}\nSettings → Profile has a Business profile defaults card. A site uses those values wherever its own profile is empty, so a workspace that runs many sites for one business writes them once. Only managers can change them. The year founded is set on each site\'s own card. The default Area served is used only by a site whose Areas served on Setup → SEO → Local business is empty.'
|
|
622
622
|
},
|
|
623
623
|
{
|
|
624
624
|
path: '/ai/business-profile',
|
|
625
625
|
title: 'Business profile',
|
|
626
626
|
heading: 'Contact details are never invented',
|
|
627
627
|
anchor: '#contact-details-are-never-invented',
|
|
628
|
-
text: 'The name,
|
|
628
|
+
text: 'The name, email, phone, address and social profiles come only from Business details on Setup → Business profile, and the business type and opening hours from Setup → SEO → Local business, exactly as entered. A detail you have not entered reads Not entered, and Aglyn AI writes the sentence without it instead of making one up or leaving a gap for you to fill. The same goes for prices, reviews and testimonials.'
|
|
629
629
|
},
|
|
630
630
|
{
|
|
631
631
|
path: '/ai/business-profile',
|
|
@@ -1472,7 +1472,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
1472
1472
|
title: 'Start a new site with AI',
|
|
1473
1473
|
heading: 'Your business, for search engines and AI assistants',
|
|
1474
1474
|
anchor: '#business-details',
|
|
1475
|
-
text: 'When the site is published, your answers also fill the site\'s structured data in Setup → SEO, so search engines and AI assistants can tell who runs the site and how to reach you:\n-
|
|
1475
|
+
text: 'When the site is published, your answers also fill the site\'s Business details in Setup → Business profile and its structured data in Setup → SEO, so your pages, search engines and AI assistants can tell who runs the site and how to reach you:\n- Business details: the business\'s phone, email and address, and its social profiles where you gave them.\n- Entity: the business\'s description (with Contact is for set to customer support), and what kind of business it is, from the style you picked (a plumber, a restaurant, a salon), with the areas it serves, its opening hours and its price range. A personal site is published as a person.\n- Entity logo: your site logo, when the site already has one.\n- AI agents: when an assistant should use the site, and how to reach a person there. These open the site\'s guide for AI assistants, so an assistant asked about your business finds what it does, where it works and how to reach you.\nOnly empty fields are filled, so nothing you already entered there is replaced. Change the business details in Setup → Business profile, and the rest in Setup → SEO, at any time.'
|
|
1476
1476
|
},
|
|
1477
1477
|
{
|
|
1478
1478
|
path: '/ai/start-with-ai',
|
|
@@ -2865,7 +2865,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
2865
2865
|
title: 'Bindings, Variables & Functions',
|
|
2866
2866
|
heading: 'Site details',
|
|
2867
2867
|
anchor: '#site-details',
|
|
2868
|
-
text: '{{host.}} tokens name the site itself instead of hard-coding it, so copy stays right when the site is renamed, and a template installed on another site fills in that site\'s details.\n| Token | Fills in |\n| {{host.businessName}} | Setup →
|
|
2868
|
+
text: '{{host.}} tokens name the site itself instead of hard-coding it, so copy stays right when the site is renamed, and a template installed on another site fills in that site\'s details.\n| Token | Fills in |\n| {{host.businessName}} | Business name, from Setup → Business profile → Business details, or the site name when that is empty |\n| {{host.slogan}} | Slogan, from the same card |\n| {{host.logo}} | The site\'s logo, from Setup → Basic details → Site logo |\n| {{host.logoDark}} | The site\'s dark mode logo from the same card, or its logo when it has no dark one |\n| {{host.url}} | The site\'s address — its custom domain when one is connected |\n| {{host.phone}} | Phone, from Setup → Business profile → Business details, as you typed it |\n| {{host.phoneLink}} | The same phone as a link that dials it, such as tel:+15125550100, for a Call button |\n| {{host.supportEmail}} | Email, from the same card |\n| {{host.address}} | The postal address from the same card, on one line |\n| {{host.mainArea}} | The first of Areas served, from Setup → SEO → Local business, by its place name: San Antonio for "San Antonio, TX" |\n| {{host.areasServed}} | Every one of Areas served, in order, separated by commas |\n| {{host.socialLinks}} | The labels of the card\'s Social links |\n| {{host.facebookUrl}} | The address of the site\'s Facebook profile, from its Social links |\n| {{host.instagramUrl}} | Its Instagram profile |\n| {{host.xUrl}} | Its X profile, on x.com or twitter.com |\n| {{host.linkedinUrl}} | Its LinkedIn profile |\n| {{host.youtubeUrl}} | Its YouTube channel |\n| {{host.tiktokUrl}} | Its TikTok profile |\nEach social link variable finds its profile by the link\'s address, not its label, so a link labeled anything at all still counts.\nThe links work in a button\'s or a link\'s External URL: pick Phone li'
|
|
2869
2869
|
},
|
|
2870
2870
|
{
|
|
2871
2871
|
path: '/building-sites/bindings/overview',
|
|
@@ -3012,7 +3012,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
3012
3012
|
title: 'Connect a domain',
|
|
3013
3013
|
heading: 'Registrar quick reference',
|
|
3014
3014
|
anchor: '#registrar-quick-reference',
|
|
3015
|
-
text: 'The exact screen differs by registrar, but you only ever add one record:\nA subdomain (www.example.com, shop.example.com, …):\n| Field | Value |\n| Type | CNAME |\n| Name / Host | www (or the subdomain you\'re connecting) |\n| Value / Target | sites.aglyn.app |\n| TTL | default is fine |\nA bare apex (example.com) — first choice:\n| Field | Value |\n| Type | ALIAS (also called ANAME, or "CNAME flattening") |\n| Name / Host | @ |\n| Value / Target | sites.aglyn.app |\n| TTL | default is fine |\nA bare apex, if your registrar has no ALIAS — fallback:\n| Field | Value |\n| Type | A |\n| Name / Host | @ |\n| Value | 216.198.79.1 |\n| TTL | default is fine |\nAn apex can\'t carry a CNAME (that\'s a DNS rule, not an Aglyn one), which is why it needs one of these two instead. Prefer the ALIAS: it names sites.aglyn.app rather than an address, so your registrar resolves it to wherever Aglyn is serving from at the time, and nothing in your zone has to change if those addresses ever do.\nThe A record is there because plenty of registrars offer no ALIAS/ANAME and no flattening — for those, it is the only way to point an apex, and it verifies exactly the same. Its one cost is that the address is pinned in your zone by hand: keep it in mind if you ever see the domain stop resolving long after it was working.\nCloudflare and other proxies CNAME flattening at the apex works, but leave the record DNS only (gray cloud) until verification succeeds — a proxied record resolves to the proxy\'s addresses, not Aglyn\'s.\
|
|
3015
|
+
text: 'The exact screen differs by registrar, but you only ever add one record:\nA subdomain (www.example.com, shop.example.com, …):\n| Field | Value |\n| Type | CNAME |\n| Name / Host | www (or the subdomain you\'re connecting) |\n| Value / Target | sites.aglyn.app |\n| TTL | default is fine |\nA bare apex (example.com) — first choice:\n| Field | Value |\n| Type | ALIAS (also called ANAME, or "CNAME flattening") |\n| Name / Host | @ |\n| Value / Target | sites.aglyn.app |\n| TTL | default is fine |\nA bare apex, if your registrar has no ALIAS — fallback:\n| Field | Value |\n| Type | A |\n| Name / Host | @ |\n| Value | 216.198.79.1 |\n| TTL | default is fine |\nAn apex can\'t carry a CNAME (that\'s a DNS rule, not an Aglyn one), which is why it needs one of these two instead. Prefer the ALIAS: it names sites.aglyn.app rather than an address, so your registrar resolves it to wherever Aglyn is serving from at the time, and nothing in your zone has to change if those addresses ever do.\nThe A record is there because plenty of registrars offer no ALIAS/ANAME and no flattening — for those, it is the only way to point an apex, and it verifies exactly the same. Its one cost is that the address is pinned in your zone by hand: keep it in mind if you ever see the domain stop resolving long after it was working.\nCloudflare and other proxies CNAME flattening at the apex works, but leave the record DNS only (gray cloud) until verification succeeds — a proxied record resolves to the proxy\'s addresses, not Aglyn\'s.\nAdd both www and the apex Add a record for each, so both addresses reach your site. Connect the one you want as your main address, and Aglyn permanently redirects the other to it, so visitors and search engines see one site. This needs no forwarding at your registrar.'
|
|
3016
3016
|
},
|
|
3017
3017
|
{
|
|
3018
3018
|
path: '/building-sites/custom-domains/connect-a-domain',
|
|
@@ -3880,14 +3880,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
3880
3880
|
title: 'SEO Toolkit',
|
|
3881
3881
|
heading: 'Social cards',
|
|
3882
3882
|
anchor: '#social-cards',
|
|
3883
|
-
text: 'Every published page emits Open Graph and Twitter metadata: title, description, canonical URL, site name, the page\'s language, and — once an image is set — og:image with its og:image:width, og:image:height and og:image:alt.\nWhat each kind of page emits\nSome properties are the same on every page of your site; others describe the one page you are looking at. Both sets are listed here so you can check a page against them.\nOn every page, whatever kind it is:\n| Property | Where it comes from |\n| og:title, og:description | The page\'s search title and description |\n| og:url | The page\'s canonical address, always absolute |\n| og:sitename | Setup → SEO Title, then the
|
|
3883
|
+
text: 'Every published page emits Open Graph and Twitter metadata: title, description, canonical URL, site name, the page\'s language, and — once an image is set — og:image with its og:image:width, og:image:height and og:image:alt.\nWhat each kind of page emits\nSome properties are the same on every page of your site; others describe the one page you are looking at. Both sets are listed here so you can check a page against them.\nOn every page, whatever kind it is:\n| Property | Where it comes from |\n| og:title, og:description | The page\'s search title and description |\n| og:url | The page\'s canonical address, always absolute |\n| og:sitename | Setup → SEO Title, then the Business name from Setup → Business profile, then the site\'s name |\n| og:locale | The page\'s language — its own, then the site\'s default |\n| og:image + width, height, alt | The winning card image, below |\n| twitter:card, title, description, image | The same values as the card above |\n| twitter:site | The X profile in Setup → Business profile → Social links |\nAnd per kind of page:\n| Page | og:type | What it adds |\n| Home, and any other page | website | og:locale:alternate for each language this page is translated into |\n| A collection listing, and a category listing | website | — |\n| A blog or collection entry | article | article:publishedtime, article:modifiedtime, article:author (their author page), article:section (its category), article:tag, and twitter:creator |\n| An author page | profile | profile:username and twitter:creator, from the author\'s own X profile |\nAnything with nothing behind it is left out rather than filled in. A site that has set no name at all publishes no og:sitename; an entry that was never published publishes no article:publishedtime; an author with no X profile is still shown on a card, ju'
|
|
3884
3884
|
},
|
|
3885
3885
|
{
|
|
3886
3886
|
path: '/building-sites/seo/overview',
|
|
3887
3887
|
title: 'SEO Toolkit',
|
|
3888
3888
|
heading: 'Structured data',
|
|
3889
3889
|
anchor: '#structured-data',
|
|
3890
|
-
text: 'Published sites emit JSON-LD, giving search engines and AI assistants rich context about your content.\nEvery page carries two site-wide nodes:\n- a top-level Organization (or Person, or a local business type such as Plumber) describing who publishes the site — the entity an assistant reads when someone asks who you are or how to reach you. It is filled in from Setup → SEO → Entity, and it falls back to your site name and description, so a site that has never touched
|
|
3890
|
+
text: 'Published sites emit JSON-LD, giving search engines and AI assistants rich context about your content.\nEvery page carries two site-wide nodes:\n- a top-level Organization (or Person, or a local business type such as Plumber) describing who publishes the site — the entity an assistant reads when someone asks who you are or how to reach you. It is filled in from Setup → Business profile → Business details and Setup → SEO → Entity, and it falls back to your site name and description, so a site that has never touched either still publishes a named, described entity;\n- a WebSite naming the site and its address, with the language it is published in (inLanguage).\nAnd per kind of page:\n| Page | What it publishes |\n| A collection listing, and a category listing | ItemList of the entries on that page, in their real positions |\n| A blog or collection entry | The article type its collection declares — BlogPosting, NewsArticle, Article — with its headline, cover, dates, byline, section and language |\n| An author page | ProfilePage wrapping the author as a Person or Organization |\n| A product page | Product with its Offer, availability and — where you have reviews — an AggregateRating |\n| Any page more than one level deep | BreadcrumbList naming the trail to it |\n| A page with a FAQ section — a Section whose accessible label names it (FAQ, Frequently asked questions) — holding two or more question-and-answer pairs, as two-line items or accordions | FAQPage listing each question with its answer, the block AI search quotes and FAQ rich results read |\nYour social links, from Setup → Business profile → Business details, are published as the entity\'s sameAs — the property that tells a search engine your site, your LinkedIn page and your X account are all the same organization. You do not h'
|
|
3891
3891
|
},
|
|
3892
3892
|
{
|
|
3893
3893
|
path: '/building-sites/seo/overview',
|
|
@@ -5812,7 +5812,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
5812
5812
|
title: 'Quotes',
|
|
5813
5813
|
heading: 'What your customer gets',
|
|
5814
5814
|
anchor: '#quote-email',
|
|
5815
|
-
text: 'One email in your site\'s look, from your site\'s name, with:\n- Your quote from your business name as its heading, or Your updated quote when it\'s a new revision of a quote you already emailed (the first email you send for a quote, and sending the same revision again, keep Your quote from);\n- your message;\n- the quote number, its revision and its total;\n- the first three proof images, each opening the quote page, and the other proof files by name, to see on the quote page (a WebP image is named rather than shown, because some inboxes can\'t show one);\n- what to do next, and one button:\n- Review and approve while the proof must be approved before paying and isn\'t yet;\n- otherwise View and pay with the total;\n- the quote attached as a PDF, the same one as Download PDF, with the pay link on it.\nThe button opens the quote\'s pay link. Replies go to your site\'s
|
|
5815
|
+
text: 'One email in your site\'s look, from your site\'s name, with:\n- Your quote from your business name as its heading, or Your updated quote when it\'s a new revision of a quote you already emailed (the first email you send for a quote, and sending the same revision again, keep Your quote from);\n- your message;\n- the quote number, its revision and its total;\n- the first three proof images, each opening the quote page, and the other proof files by name, to see on the quote page (a WebP image is named rather than shown, because some inboxes can\'t show one);\n- what to do next, and one button:\n- Review and approve while the proof must be approved before paying and isn\'t yet;\n- otherwise View and pay with the total;\n- the quote attached as a PDF, the same one as Download PDF, with the pay link on it.\nThe button opens the quote\'s pay link. Replies go to the Email in your site\'s Business details, and to your own email when your site has none. The email ends with a line saying so.\nThe email is the Quote email under Emails, where you can change its wording and colors like your other site emails. It can use these tokens:\n| Token | Value |\n| -- | -- |\n| {{quote.number}}, {{quote.revision}}, {{quote.total}} | The quote number, like #1042, its revision, and its total (with "before tax" when Stripe Tax adds the tax at payment) |\n| {{quote.heading}}, {{quote.intro}} | The heading, and one sentence on whether this is a new quote or an updated revision |\n| {{quote.message}} | The message you typed; empty when you typed none |\n| {{quote.proofImages}}, {{quote.proofFiles}} | Up to three proof images, and the other proof files by name |\n| {{quote.nextStep}}, {{quote.buttonLabel}}, {{quote.url}} | What to do next, the button\'s words, and the pay link |\n| {{quote.subject}} | The subject you sent it'
|
|
5816
5816
|
},
|
|
5817
5817
|
{
|
|
5818
5818
|
path: '/commerce-and-bookings/commerce/quotes-and-proofs',
|
|
@@ -6554,7 +6554,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
6554
6554
|
title: 'Waivers',
|
|
6555
6555
|
heading: 'Share it before riders arrive',
|
|
6556
6556
|
anchor: '#share-it-before-riders-arrive',
|
|
6557
|
-
text: 'On the Waivers card, select Share beside a waiver:\n- Copy link gives you a link to send in a confirmation, a text or a post.\n- Download QR code gives you a code to print for the gate, the window or your ticket emails.\nThe link opens on your own site, at /sign-waiver, with your site\'s header and footer: on your custom domain when one is connected, or on your site\'s .aglyn.app address. If you connect a custom domain later, links and QR codes you already handed out still work: your .aglyn.app address sends signers on to it.\nThe page is made for phones. The signer reads the waiver, fills in their name, email, phone and date of birth, ticks the boxes, agrees to sign electronically, and signs with a finger or types their name. They see a confirmation with Download your signed copy (PDF), and a signed copy goes to their email.\nSigning electronically {#signing-electronically}\nBefore the signature, under Signing electronically, the signer ticks a box agreeing to sign electronically, for themselves and any minors they list. The wording says what that covers (this waiver and its signed copy), what they need (a device with a web browser, and a way to open a PDF), that they can sign on paper instead, and that after signing they can ask you for a paper copy at no charge, change the email for their copy, or withdraw their agreement for anything not yet sent, by contacting you. It names your business and how to reach you: the
|
|
6557
|
+
text: 'On the Waivers card, select Share beside a waiver:\n- Copy link gives you a link to send in a confirmation, a text or a post.\n- Download QR code gives you a code to print for the gate, the window or your ticket emails.\nThe link opens on your own site, at /sign-waiver, with your site\'s header and footer: on your custom domain when one is connected, or on your site\'s .aglyn.app address. If you connect a custom domain later, links and QR codes you already handed out still work: your .aglyn.app address sends signers on to it.\nThe page is made for phones. The signer reads the waiver, fills in their name, email, phone and date of birth, ticks the boxes, agrees to sign electronically, and signs with a finger or types their name. They see a confirmation with Download your signed copy (PDF), and a signed copy goes to their email.\nSigning electronically {#signing-electronically}\nBefore the signature, under Signing electronically, the signer ticks a box agreeing to sign electronically, for themselves and any minors they list. The wording says what that covers (this waiver and its signed copy), what they need (a device with a web browser, and a way to open a PDF), that they can sign on paper instead, and that after signing they can ask you for a paper copy at no charge, change the email for their copy, or withdraw their agreement for anything not yet sent, by contacting you. It names your business and how to reach you: the Email and Phone in Business details on Setup → Business profile. The signing page shows the same contact under the waiver\'s title, and the signed copy email repeats it. Add one so signers know how to reach you.\nEach signature keeps the exact words its signer agreed to, with their version. Signatures taken under the earlier wording keep that wording.\nOn the window\''
|
|
6558
6558
|
},
|
|
6559
6559
|
{
|
|
6560
6560
|
path: '/commerce-and-bookings/commerce/waivers',
|
|
@@ -10516,7 +10516,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10516
10516
|
title: 'The console tour',
|
|
10517
10517
|
heading: 'Primary navigation',
|
|
10518
10518
|
anchor: '#primary-navigation',
|
|
10519
|
-
text: 'The tabs across the top of a site are its sections. Some are always present; the rest are contributed by the plugins your workspace has enabled — so two sites, or the same site before and after you enable a plugin, can show different tabs. Don\'t be surprised by a tab strip that doesn\'t match a screenshot exactly.\nThese four are where a new site\'s work happens:\n| Section | What\'s there |\n| Dashboard | The site at a glance — analytics and recent-signup summaries, and the ten most recent activity entries. |\n| Pages | The page hierarchy — create, reorder (drag-and-drop), and open pages. This is where you build; start at Publish your first page. |\n| Media | The media library — folders, images, video, and files. |\n| Setup | Basic details, SEO, tracking, theme, and emails. Each
|
|
10519
|
+
text: 'The tabs across the top of a site are its sections. Some are always present; the rest are contributed by the plugins your workspace has enabled — so two sites, or the same site before and after you enable a plugin, can show different tabs. Don\'t be surprised by a tab strip that doesn\'t match a screenshot exactly.\nThese four are where a new site\'s work happens:\n| Section | What\'s there |\n| Dashboard | The site at a glance — analytics and recent-signup summaries, and the ten most recent activity entries. |\n| Pages | The page hierarchy — create, reorder (drag-and-drop), and open pages. This is where you build; start at Publish your first page. |\n| Media | The media library — folders, images, video, and files. |\n| Setup | Basic details, your business details and profile, SEO, tracking, theme, and emails. Each section has its own address, so you can bookmark or share the exact one. |\nAlongside them, and always present: Layouts and Components (the shared frames and reusable pieces pages are assembled from — see Pages & Layouts), Templates (saved starting points), Content (collections and blog entries), Users (the people who sign in to the site you\'re building, not your own team), and Analytics. Admin appears only if you\'re an owner or admin of the site; it holds per-site plugin settings, the custom domain, the site\'s security lists, the full activity log, and the danger zone.\nSections that come and go Tabs such as Data, Products, Logic, Automation, Inbox, Bookings, Events, Redirects, Marketing and Marketplace are contributed by plugins and appear only where that plugin is enabled for your workspace (they\'re inserted after Analytics). If a section these docs describe isn\'t in your tab strip, that\'s usually why — enable the plugin under Organization → Plugins.\nBilling is not a '
|
|
10520
10520
|
},
|
|
10521
10521
|
{
|
|
10522
10522
|
path: '/getting-started/console-tour',
|
|
@@ -10579,14 +10579,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10579
10579
|
title: 'Create a site',
|
|
10580
10580
|
heading: 'What a site contains',
|
|
10581
10581
|
anchor: '#what-a-site-contains',
|
|
10582
|
-
text: '- Pages & layouts — the pages and the shared frames they render in.\n- Data — the datasets this site can see. Variables and functions are under Logic, and workflows and actions under Automation.\n- Media — images, video, and files, organized in folders.\n- Setup — theme, SEO, tracking, and emails
|
|
10582
|
+
text: '- Pages & layouts — the pages and the shared frames they render in.\n- Data — the datasets this site can see. Variables and functions are under Logic, and workflows and actions under Automation.\n- Media — images, video, and files, organized in folders.\n- Setup — your business details, theme, SEO, tracking, and emails, each in its own section. The Site logo card (Details tab) sets your brand mark: it\'s shown on the live site\'s page-navigation loading overlay — a themed, blurred scrim with a progress bar. Without a logo, the loader shows your site name instead. Add a Dark mode logo too if yours is hard to see on a dark background: visitors browsing in dark mode see it on the loader and error pages, and without one they see the light mode logo.\n- Billing — the plan and usage meters that gate features and quotas.'
|
|
10583
10583
|
},
|
|
10584
10584
|
{
|
|
10585
10585
|
path: '/getting-started/create-a-site',
|
|
10586
10586
|
title: 'Create a site',
|
|
10587
10587
|
heading: 'Your site\'s details',
|
|
10588
10588
|
anchor: '#site-details',
|
|
10589
|
-
text: 'A site\'s
|
|
10589
|
+
text: 'A site\'s details are what it is called, where it is served from, who the business behind it is, and how it presents itself. The cards below are the ones to fill in first.\nBasic details {#basic-details}\nThe Basic details card, under Site Admin → General, names your site, sets its Aglyn address and picks the time zone its dates are read in — fill in a display name and a subdomain, then press Update.\n- Display name — what the site is called in the console. See below.\n- Subdomain — the site\'s address on Aglyn. See below.\n- Time zone — the day a published post is dated on this site. Leave it unset and the site follows your workspace\'s time zone; clear it with the ✕ to go back to that.\nDisplay name {#display-name}\nThe Display name is what the site is called inside the console — the site switcher, breadcrumbs, the Sites list and notifications — up to 30 characters. Visitors can see it too: the loading screen between pages shows it when the site has no logo, and it stands in for your business name until you set one in Business details. The title in a visitor\'s browser tab is your site\'s SEO Title, set under Setup → SEO.\nSubdomain {#subdomain}\nThe Subdomain is your site\'s free address, up to 15 characters, and it works from the moment the site exists. On aglyn.com it is the name in name.aglyn.app. It keeps working after you connect your own domain. Changing it changes that address, so links to the old one stop working.\nBusiness details {#business-details}\nSetup → Business profile opens on the Business details card, the one place your business\'s details are entered. Your pages, your site\'s emails, quotes, invoices and waivers, and your search listings all read them from here, so you type each one once.\n- Business name — the name customers know you by. Leave it empty to use the si'
|
|
10590
10590
|
},
|
|
10591
10591
|
{
|
|
10592
10592
|
path: '/getting-started/create-a-site',
|