@aglyn/aglyn 1.7.0 → 1.8.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 CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@aglyn/aglyn",
3
- "version": "1.7.0",
3
+ "version": "1.8.0",
4
4
  "license": "Apache-2.0",
5
5
  "homepage": "https://aglyn.com",
6
6
  "repository": {
@@ -37,16 +37,16 @@
37
37
  "./package.json": "./package.json"
38
38
  },
39
39
  "dependencies": {
40
- "@aglyn/shared-data-enums": "1.7.0",
41
- "@aglyn/shared-data-mdi": "1.7.0",
42
- "@aglyn/shared-data-types": "1.7.0",
43
- "@aglyn/shared-util-email": "1.7.0",
44
- "@aglyn/shared-util-first-touch": "1.7.0",
45
- "@aglyn/shared-util-http": "1.7.0",
46
- "@aglyn/shared-util-logger": "1.7.0",
47
- "@aglyn/shared-util-timestamp": "1.7.0",
48
- "@aglyn/shared-util-tools": "1.7.0",
49
- "@aglyn/shared-util-vendor": "1.7.0",
40
+ "@aglyn/shared-data-enums": "1.8.0",
41
+ "@aglyn/shared-data-mdi": "1.8.0",
42
+ "@aglyn/shared-data-types": "1.8.0",
43
+ "@aglyn/shared-util-email": "1.8.0",
44
+ "@aglyn/shared-util-first-touch": "1.8.0",
45
+ "@aglyn/shared-util-http": "1.8.0",
46
+ "@aglyn/shared-util-logger": "1.8.0",
47
+ "@aglyn/shared-util-timestamp": "1.8.0",
48
+ "@aglyn/shared-util-tools": "1.8.0",
49
+ "@aglyn/shared-util-vendor": "1.8.0",
50
50
  "@data-driven-forms/react-form-renderer": "^4.2.0",
51
51
  "@msgpack/msgpack": "^3.1.3",
52
52
  "@types/unist": "^3.0.3",
@@ -548,35 +548,35 @@ export const DOCS_SECTION_INDEX = [
548
548
  title: 'Bring my site',
549
549
  heading: 'Read my site',
550
550
  anchor: '#read-my-site',
551
- text: 'Choose Read my site. Aglyn then:\n- creates your new site, with nothing on it and nothing published;\n- reads your current site as AglynBot, starting with its robots.txt file and its sitemap, then your home page, then every other page, and only on your own domain. Your current site is not changed.\nAglyn reads up to 400 pages. A link to a file, such as a download or a PDF, is not a page, so it is never read as one and never counts toward that number.\nReading uses no AI credits.\nWhat is read. For each page Aglyn reads its words and how your site lays them out: its sections and their background colors, its columns, its cards and the icons on them, its numbered steps, figures, questions and answers, quotes, logo strips, plan cards with their badge, price and button, plan rows, tables and tabs, its pictures where they sit, your forms with their fields and their button, and which links your site shows as buttons. From your home page it also reads your menu, with each dropdown and its entries, the buttons beside it, and your footer\'s columns, profiles and copyright line, plus your site\'s fonts and colors. Your new pages are built from this, with every word as you wrote it.\nYour home page comes first. If AglynBot cannot read your home page, nothing is planned and no AI credits are used. The import waits and says why:\n- AglynBot was turned away means your site\'s bot protection or firewall refused it. See When your site turns AglynBot away.\n- Your home page could not be read means your home page answered with an error or did not answer. Check that your site is up, then choose Check again.\nCheck again reads your site again, and uses no AI credits either.\nWhen it is done, Your site is read shows:\n- what was found, grouped as your Main pages and each collection, such as a blog\'s posts'
551
+ text: 'Choose Read my site. Aglyn then:\n- creates your new site, with nothing on it and nothing published;\n- reads your current site as AglynBot, starting with its robots.txt file and its sitemap, then your home page, then every other page, and only on your own domain. Your current site is not changed.\nAglyn reads up to 400 pages. A link to a file, such as a download or a PDF, is not a page, so it is never read as one and never counts toward that number.\nReading uses no AI credits.\nWhat is read. For each page Aglyn reads its words and how your site lays them out: its sections and their background colors, its columns, its cards and the icons on them, its numbered steps, figures, questions and answers, quotes, logo strips, plan cards with their badge, price and button, plan rows, tables and tabs, its pictures where they sit, its videos (a film on your page, with its poster, title and description), your forms with their fields and their button, and which links your site shows as buttons. From your home page it also reads your menu, with each dropdown and its entries, the buttons beside it, and your footer\'s columns, profiles and copyright line, plus your site\'s fonts and colors. Your new pages are built from this, with every word as you wrote it.\nYour home page comes first. If AglynBot cannot read your home page, nothing is planned and no AI credits are used. The import waits and says why:\n- AglynBot was turned away means your site\'s bot protection or firewall refused it. See When your site turns AglynBot away.\n- Your home page could not be read means your home page answered with an error or did not answer. Check that your site is up, then choose Check again.\nCheck again reads your site again, and uses no AI credits either.\nWhen it is done, Your site is read shows:\n- what was fou'
552
552
  },
553
553
  {
554
554
  path: '/ai/bring-my-site',
555
555
  title: 'Bring my site',
556
556
  heading: 'Waves',
557
557
  anchor: '#waves',
558
- text: '- The first wave brings in your main pages: home, then the pages in your menu, then your other top-level pages. Before any page, it gives your new site your current site\'s look, on one of Aglyn\'s built-in themes: your buttons\' color as its main color and your links\' color beside it, your pages\' background color, the rounding of your buttons, and your own font when Google Fonts has it, or a font in the same style when it does not. Colors are kept readable, so a color too light for white words is used a shade deeper. If you already chose a theme for the new site, it is kept.\n- Your header and footer come in with the first wave, as your current site shows them: your logo, your name, or both; your menu, each dropdown as a Dropdown Menu or a Mega Menu with its entries, their icons and the line under each; and your buttons, such as Sign in or Start free, going where they go now. Every label stays on one line, and on a screen too narrow for the whole menu it becomes a menu button that opens every menu and button. Your footer keeps its columns and headings, its profiles, its address, phone and email, and its copyright line as written. When your menu can be read, the header and footer use no AI credits. See Menus & navigation to change them later. Your home page\'s title and description become your new site\'s search listing, unless you already changed it.\n- Each later wave brings in up to 10 pages of one collection, for example Blog, 1 of 3.\n- Never past your plan. Your main pages are kept first. If your site has more pages than your plan allows, the last pages of your collections are the ones left out, each listed with Past your plan\'s page count. See plans opens Billing.\nYour words are never rewritten. Every page is laid out as your page is: its sections in their own background'
558
+ text: '- The first wave brings in your main pages: home, then the pages in your menu, then your other top-level pages. Before any page, it gives your new site your current site\'s look, on one of Aglyn\'s built-in themes: your buttons\' color as its main color and your links\' color beside it, the color of the small labels above your headings as its third color, your pages\' background color, the rounding of your buttons, and your own font when Google Fonts has it, or a font in the same style when it does not. Colors are kept readable, so a color too light for white words is used a shade deeper. If you already chose a theme for the new site, it is kept.\n- Your header and footer come in with the first wave, as your current site shows them: your logo, your name, or both; your menu, each dropdown as a Dropdown Menu or a Mega Menu with its entries, their icons and the line under each; and your buttons, such as Sign in or Start free, going where they go now. A large dropdown keeps its columns in the same order, side by side and as wide as yours, with each column\'s heading and words, its featured picture, its light or dark box, and the colored tile behind each icon. Every label stays on one line, and on a screen too narrow for the whole menu it becomes a menu button that opens every menu and button.\n- Your menus open the way they do now. A menu that opens when you point at it opens the same way on a computer, and clicking its name opens that page, as it does on your current site. A menu name with no page of its own opens its menu on a click. A menu that only opens on a click stays that way. In the menu on a phone, tap a menu\'s name to open or close it; every entry and every word of its panel is there. Each menu\'s panel starts hidden until it is shown: select it in the Besigner to work on'
559
559
  },
560
560
  {
561
561
  path: '/ai/bring-my-site',
562
562
  title: 'Bring my site',
563
563
  heading: 'Review a wave',
564
564
  anchor: '#review-a-wave',
565
- text: 'When a wave is in, its page says so, for example Main pages is in your site\'s preview, and shows:\n- every page of the wave, with Open draft, its old and new address, and Old page to compare it with the page on your current site;\n- how many of the page\'s photos came in, for example 3 of 5 photos, with how many were already in your media library and how many could not be brought in;\n- a page that could not be brought in, with the reason;\n- a page whose form was rebuilt, with the form\'s name;\n- how many AI credits the wave used.\nIf your site started in preview, each wave\'s pages are published into the preview as the wave comes in. You, your team and Aglyn support can open the site and see them at their addresses, home at your site\'s address. Visitors still see Coming soon. To make the site public, switch Preview off in Admin → Error pages, or choose Make it public on the banner that says your site is in preview.\nIf your site is not in preview, every page is a draft: nothing is published until you publish it.\nOpen your draft pages opens the site\'s Pages list. When you are ready for more, choose the next wave\'s Start button. Nothing starts the next wave except you, unless you chose Start every remaining wave.\nCancel stops the import. The pages already brought in stay where they are: in the preview, or as drafts. Under Every wave, a wave that was running reads stopped, and a wave that had not started reads not started.'
565
+ text: 'When a wave is in, its page says so, for example Main pages is in your site\'s preview, and shows:\n- every page of the wave, with Open draft, its old and new address, and Old page to compare it with the page on your current site;\n- how many of the page\'s photos came in, for example 3 of 5 photos, with how many were already in your media library and how many could not be brought in;\n- a page that could not be brought in, with the reason;\n- a page whose form was rebuilt, with the form\'s name;\n- a page with a video your old site serves itself, which plays from your old site\'s address, and a page with a video that was left out because it had no poster picture;\n- how many AI credits the wave used.\nIf your site started in preview, each wave\'s pages are published into the preview as the wave comes in. You, your team and Aglyn support can open the site and see them at their addresses, home at your site\'s address. Visitors still see Coming soon. To make the site public, switch Preview off in Admin → Error pages, or choose Make it public on the banner that says your site is in preview.\nIf your site is not in preview, every page is a draft: nothing is published until you publish it.\nOpen your draft pages opens the site\'s Pages list. When you are ready for more, choose the next wave\'s Start button. Nothing starts the next wave except you, unless you chose Start every remaining wave.\nCancel stops the import. The pages already brought in stay where they are: in the preview, or as drafts. Under Every wave, a wave that was running reads stopped, and a wave that had not started reads not started.'
566
566
  },
567
567
  {
568
568
  path: '/ai/bring-my-site',
569
569
  title: 'Bring my site',
570
- heading: 'Photos',
570
+ heading: 'Photos and videos',
571
571
  anchor: '#photos',
572
- text: 'A page\'s photos are copied into your new site\'s media library and placed on that page: on a page copied as it is, each one where your page shows it. The same photo is stored only once, however many pages show it.\nYour logo is copied once, for your header. If it is a drawing (an SVG file), it is saved as a picture. Your home page\'s share image, the one shown when your site is linked, becomes your new site\'s share image unless you already chose one.'
572
+ text: 'A page\'s photos are copied into your new site\'s media library and placed on that page: on a page copied as it is, each one where your page shows it. The same photo is stored only once, however many pages show it.\nA video on your page is placed with the Video element, where your page shows it, and plays from where it plays now:\n- A video on Wistia, YouTube or Vimeo plays in that host\'s player, which loads only when a visitor presses play.\n- A video your old site serves itself plays from your old site\'s address. Its page\'s row says so. To move it, pick the video from your media library on its Video element. So it can play on your new site, the address it plays from is added to Approved media hosts in Admin → Security. Every host on that list can see the IP address of each visitor whose browser plays the video from it.\nIts poster picture, the still a visitor presses, is copied into your media library like any photo, and its title, description, date and running time come with it when your page gives them. A button on your page that plays the video, such as Watch the film, plays it on the new page too. A video on another host is shown as its poster picture, linking to where it plays. A video your page shows without a poster picture is left out, and its page\'s row says so: add it with the Video element and pick a poster for it. A video that plays by itself behind a section\'s words is shown as its poster picture there.\nYour logo is copied once, for your header. If it is a drawing (an SVG file), it is saved as a picture. Your home page\'s share image, the one shown when your site is linked, becomes your new site\'s share image unless you already chose one.'
573
573
  },
574
574
  {
575
575
  path: '/ai/bring-my-site',
576
576
  title: 'Bring my site',
577
577
  heading: 'What is never brought in',
578
578
  anchor: '#never-brought-in',
579
- text: '- Sign-in pages. A page that asks for a password is left out, and so is a page AglynBot is asked not to read by robots.txt.\n- Code. Scripts and embedded frames are never brought in.\n- Forms that ask for a password or a card number. These are left out. Every other form on your page is rebuilt as a form of your new site, with the same fields, required marks and button, where your page had it. What visitors send lands in your Inbox, a form that asks for an email also asks for marketing consent, and rebuilding a form uses no AI credits. A form your new site already has is placed instead of a second copy. If your plan has no room for another form, the page comes in without it and its row says so. A form can\'t take a file here, so a file upload field is left out and the page\'s row names it.\n- Other websites. Only pages on your own domain are read. A page that sends visitors to another website is left out.'
579
+ text: '- Sign-in pages. A page that asks for a password is left out, and so is a page AglynBot is asked not to read by robots.txt.\n- Code. Scripts are never brought in. An embedded video is placed as a video, and any other embedded frame is left out.\n- Forms that ask for a password or a card number. These are left out. Every other form on your page is rebuilt as a form of your new site, with the same fields, required marks and button, where your page had it. What visitors send lands in your Inbox, a form that asks for an email also asks for marketing consent, and rebuilding a form uses no AI credits. A form your new site already has is placed instead of a second copy. If your plan has no room for another form, the page comes in without it and its row says so. A form can\'t take a file here, so a file upload field is left out and the page\'s row names it.\n- Other websites. Only pages on your own domain are read. A page that sends visitors to another website is left out.'
580
580
  },
581
581
  {
582
582
  path: '/ai/bring-my-site',
@@ -2004,7 +2004,7 @@ export const DOCS_SECTION_INDEX = [
2004
2004
  title: 'Interactions & custom HTML',
2005
2005
  heading: 'Play a video',
2006
2006
  anchor: '#play-video-step',
2007
- text: 'When clicked → Play a video does exactly what pressing a Video element\'s poster does, from a button anywhere on the page. Pick the Video as the target.\n- With Open in a lightbox on, the lightbox opens and the film plays.\n- With it off, the film plays in place of the poster.\nNothing is loaded from the video\'s host until the action runs, and a Wistia video follows the same consent rules as a press on its poster. To be sure the film is in view as it starts, put Scroll to element, picking the same Video, before it.'
2007
+ text: 'When clicked → Play a video does exactly what pressing a Video element\'s poster does, from a button anywhere on the page. Pick the Video as the target.\n- With Open in a lightbox on, the lightbox opens and the film plays.\n- With it off, the film plays in place of the poster.\nNothing is loaded from the video\'s host until the action runs, and a Wistia, YouTube or Vimeo video follows the same consent rules as a press on its poster. To be sure the film is in view as it starts, put Scroll to element, picking the same Video, before it.'
2008
2008
  },
2009
2009
  {
2010
2010
  path: '/building-sites/besigner/interactions-and-custom-html',
@@ -2739,7 +2739,7 @@ export const DOCS_SECTION_INDEX = [
2739
2739
  title: 'Video',
2740
2740
  heading: 'Choosing the film',
2741
2741
  anchor: '#video-source',
2742
- text: 'Set a Video source with Browse media. A video from your media library arrives with a poster frame, its running time and its dimensions already filled in — you only need Poster image to override the frame the library picked.\nVideo uploads are paused New video files cannot be uploaded to the media library for now. The Video element can still use any video that is already in your library, or a video hosted on Wistia.\nPicking a video from the media library copies its dimensions onto the element, which reserves the right-shaped box before anything loads and stops the rest of the page shifting when it does. It fills in the duration too, so the only SEO fields left to write are the title, the description and the date.'
2742
+ text: 'Set a Video source with Browse media. A video from your media library arrives with a poster frame, its running time and its dimensions already filled in — you only need Poster image to override the frame the library picked.\nVideo uploads are paused New video files cannot be uploaded to the media library for now. The Video element can still use any video that is already in your library, or a video hosted on Wistia, YouTube or Vimeo.\nPicking a video from the media library copies its dimensions onto the element, which reserves the right-shaped box before anything loads and stops the rest of the page shifting when it does. It fills in the duration too, so the only SEO fields left to write are the title, the description and the date.'
2743
2743
  },
2744
2744
  {
2745
2745
  path: '/building-sites/besigner/video',
@@ -2765,9 +2765,9 @@ export const DOCS_SECTION_INDEX = [
2765
2765
  {
2766
2766
  path: '/building-sites/besigner/video',
2767
2767
  title: 'Video',
2768
- heading: 'A video hosted on Wistia',
2768
+ heading: 'A video hosted on Wistia, YouTube or Vimeo',
2769
2769
  anchor: '#video-wistia',
2770
- text: 'Paste a Wistia media link into Video source: the address of the video\'s page in your Wistia account, or its embed link. Then pick a Poster image from your media library. The poster becomes a play button, and Wistia\'s player loads only when a visitor presses it, so someone who never presses play never contacts Wistia, 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.\nWistia\'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. 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. Type the running time into Duration (seconds), because a Wistia link does not carry it.\nTurn on Load the player with the page for a page whose main content is this one video, such as the entry page of a video collection. Search engines list a video only from a page like that, and they only find a player that is on the page when it loads. With the switch on, Wistia\'s player replaces the poster as soon as the page loads, without starting the video, for each visitor whose analytics consent your site has on record. Everyone else still gets the poster to press, with Wistia\'s tracking off. The player stays in the page even when Open in a lightbox is on. Keep the switch off on your home page, and on any page where the video is secondary.\nWistia\'s player keeps data in the visitor\'s browser from the moment it loads, which is why the switch waits for consent. In the geo-conditional consent mode, a visitor outside the EU, the UK and'
2770
+ 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 whose main content is this one video, such as the entry page of '
2771
2771
  },
2772
2772
  {
2773
2773
  path: '/building-sites/besigner/video',
@@ -4342,7 +4342,7 @@ export const DOCS_SECTION_INDEX = [
4342
4342
  title: 'Build a blog',
4343
4343
  heading: 'Build a video collection',
4344
4344
  anchor: '#video-collection',
4345
- text: 'Give every film a page of its own: a collection whose entries are articles with the film where a post\'s cover image would sit. Search engines list a video from a page that is about that video, and an entry page is exactly that.\nGive each entry its film. In the entry editor, Featured video takes a film from your media library, a video link, or a Wistia link. Picking a library film that has a captured frame also fills an empty Cover image with that frame; a cover you already chose is kept.\nSay how long it runs. Video length (seconds), under the featured video, is the film\'s running time, which a video search result can show beside it. Choosing a film from your media library fills it in from the file. For a video link or a Wistia link, type it yourself: 754 for a film that runs 12 minutes 34 seconds. Leave it blank if you don\'t know it; the page is still listed without one.\nPlace the player on the entry template. Add a Video element where the cover would go and set its fields to the entry\'s tokens, typed or picked with the field\'s {x} button under Entry:\n| Video field | Token |\n| Video source | {{entry.coverVideo}} |\n| Poster image | {{entry.coverImage}} |\n| Video title | {{entry.title}} |\n| Video description | {{entry.excerpt}} |\n| Publication date | {{entry.publishedAt}} |\n| Duration (seconds) | {{entry.coverVideoDuration}} |\nUse {{entry.publishedAt}} for the date, not {{entry.date}}: the date token is written for readers, like 8/9/2026, which a search engine cannot read as a date. See the fields a search result reads.\nKeep list cards to a picture. In the list template\'s Collection Entries card, show each film as an Image bound to {{entry.coverImage}}. Don\'t put a Video element in a card: a list with a player in every card is one page holding many videos, not a page abou'
4345
+ text: 'Give every film a page of its own: a collection whose entries are articles with the film where a post\'s cover image would sit. Search engines list a video from a page that is about that video, and an entry page is exactly that.\nGive each entry its film. In the entry editor, Featured video takes a film from your media library, a video link, or a Wistia, YouTube or Vimeo link. Picking a library film that has a captured frame also fills an empty Cover image with that frame; a cover you already chose is kept.\nSay how long it runs. Video length (seconds), under the featured video, is the film\'s running time, which a video search result can show beside it. Choosing a film from your media library fills it in from the file. For a video link or a Wistia, YouTube or Vimeo link, type it yourself: 754 for a film that runs 12 minutes 34 seconds. Leave it blank if you don\'t know it; the page is still listed without one.\nPlace the player on the entry template. Add a Video element where the cover would go and set its fields to the entry\'s tokens, typed or picked with the field\'s {x} button under Entry:\n| Video field | Token |\n| Video source | {{entry.coverVideo}} |\n| Poster image | {{entry.coverImage}} |\n| Video title | {{entry.title}} |\n| Video description | {{entry.excerpt}} |\n| Publication date | {{entry.publishedAt}} |\n| Duration (seconds) | {{entry.coverVideoDuration}} |\nUse {{entry.publishedAt}} for the date, not {{entry.date}}: the date token is written for readers, like 8/9/2026, which a search engine cannot read as a date. See the fields a search result reads.\nKeep list cards to a picture. In the list template\'s Collection Entries card, show each film as an Image bound to {{entry.coverImage}}. Don\'t put a Video element in a card: a list with a player in every card is one page '
4346
4346
  },
4347
4347
  {
4348
4348
  path: '/building-sites/site-templates/build-a-blog',
@@ -11468,7 +11468,7 @@ export const DOCS_SECTION_INDEX = [
11468
11468
  title: 'Cookie consent',
11469
11469
  heading: 'What needs consent',
11470
11470
  anchor: '#what-needs-consent',
11471
- text: 'Consent-gated — held back unless the visitor\'s recorded state grants analytics:\n- Google Analytics (your configured measurement ID) and every event Aglyn sends to it — see Google Analytics events.\n- Google Tag Manager (your configured container ID). The container is gated the same way and never more loosely, so it cannot be used to install a tag that runs before consent.\n- Core Web Vitals reporting. Page-speed metrics reach your property only through the same tag, and are discarded rather than held if consent is refused while a page is open.\n- Cross-visit A/B test identity: without an analytics grant, experiment variant assignment is remembered only for the visit (sessionStorage) instead of across visits.\n- Funnel visits. On a site with a funnel, each visit\'s steps are tied together by a random id kept in that browser tab\'s session storage, and the id is sent with each step. No step is recorded until the visitor\'s state grants analytics; a refusal deletes the id. See What counts as a visit.\n- Remembering the campaign that last touched a visitor. Reading it on the page they are on needs no grant; keeping it across visits does. See The campaign a visitor came from.\n- A Wistia player loaded with the page — see Videos that load with the page.\n- Advertising storage (adstorage, aduserdata, adpersonalization), on sites that have turned the advertising question on. Where it starts depends on the visitor\'s region, and it is the same split analytics uses:\n- Prior-consent regions. The EU/EEA, the UK, and any visitor whose region cannot be determined see the banner first, and advertising storage is denied until they tick that specific box. Not objecting is never a yes here.\n- Everywhere else. Advertising runs from their first visit, alongside analytics, on the same implied basis — '
11471
+ text: 'Consent-gated — held back unless the visitor\'s recorded state grants analytics:\n- Google Analytics (your configured measurement ID) and every event Aglyn sends to it — see Google Analytics events.\n- Google Tag Manager (your configured container ID). The container is gated the same way and never more loosely, so it cannot be used to install a tag that runs before consent.\n- Core Web Vitals reporting. Page-speed metrics reach your property only through the same tag, and are discarded rather than held if consent is refused while a page is open.\n- Cross-visit A/B test identity: without an analytics grant, experiment variant assignment is remembered only for the visit (sessionStorage) instead of across visits.\n- Funnel visits. On a site with a funnel, each visit\'s steps are tied together by a random id kept in that browser tab\'s session storage, and the id is sent with each step. No step is recorded until the visitor\'s state grants analytics; a refusal deletes the id. See What counts as a visit.\n- Remembering the campaign that last touched a visitor. Reading it on the page they are on needs no grant; keeping it across visits does. See The campaign a visitor came from.\n- A Wistia, YouTube or Vimeo player loaded with the page — see Videos that load with the page.\n- Advertising storage (adstorage, aduserdata, adpersonalization), on sites that have turned the advertising question on. Where it starts depends on the visitor\'s region, and it is the same split analytics uses:\n- Prior-consent regions. The EU/EEA, the UK, and any visitor whose region cannot be determined see the banner first, and advertising storage is denied until they tick that specific box. Not objecting is never a yes here.\n- Everywhere else. Advertising runs from their first visit, alongside analytics, on the sam'
11472
11472
  },
11473
11473
  {
11474
11474
  path: '/marketing-and-automation/analytics/cookie-consent',
@@ -11482,7 +11482,7 @@ export const DOCS_SECTION_INDEX = [
11482
11482
  title: 'Cookie consent',
11483
11483
  heading: 'Videos that load with the page',
11484
11484
  anchor: '#videos-that-load-with-the-page',
11485
- text: 'A Video element with Load the player with the page on is consent-gated like the list above: it puts Wistia\'s player in place of its poster only for a visitor whose recorded state grants analytics, and everyone else gets the poster. The player keeps its own storage inside its frame (wistia and wistia-video-progress-{media id}) as soon as it loads, before anyone presses play. A press loads the player for any visitor, with Wistia\'s do-not-track option unless analytics is granted, and the player keeps the same storage then.'
11485
+ text: 'A Video element with Load the player with the page on is consent-gated like the list above: it puts the video host\'s player (Wistia, YouTube or Vimeo) in place of its poster only for a visitor whose recorded state grants analytics, and everyone else gets the poster. The player keeps its own storage inside its frame as soon as it loads, before anyone presses play; Wistia\'s is wistia and wistia-video-progress-{media id}. A press loads the player for any visitor: Wistia\'s with its do-not-track option unless analytics is granted, YouTube\'s always in its privacy-enhanced player, and Vimeo\'s always with its do-not-track option on. The player keeps its storage then too.'
11486
11486
  },
11487
11487
  {
11488
11488
  path: '/marketing-and-automation/analytics/cookie-consent',
@@ -13162,14 +13162,14 @@ export const DOCS_SECTION_INDEX = [
13162
13162
  title: 'Members-only areas',
13163
13163
  heading: '',
13164
13164
  anchor: '',
13165
- text: 'Members-only areas\nBeyond your team, your site visitors can become members — and you can restrict certain pages to signed-in members only.\nPlan availability Business and above. Members-only pages, gated video, and the content paywall need the content-gating feature; on lower plans (or if a subscription lapses) gated content is not served.'
13165
+ text: 'Members-only areas\nBeyond your team, your site visitors can become members — and you can restrict certain pages to signed-in members only.\nPlan availability Three things here share the word "member", and they are on different plans:\n- Member accounts: signing up, signing in, recovering a password, and the account page with past orders. These work wherever commerce does.\n- Members-only content: members-only pages, gated video and the content paywall. These need the content-gating feature, on Business and above. On a lower plan, or if a subscription lapses, gated content is not served.\n- Recurring billing: subscription products and paid memberships charged on a schedule. Also Business and above.'
13166
13166
  },
13167
13167
  {
13168
13168
  path: '/workspace-and-billing/teams-and-roles/members-only',
13169
13169
  title: 'Members-only areas',
13170
13170
  heading: 'Let visitors sign up',
13171
13171
  anchor: '#let-visitors-sign-up',
13172
- text: 'Enable site membership so visitors can sign in / sign up to your site. New members flow into your CRM automatically.'
13172
+ text: 'Turn on User Accounts for the site so visitors can sign in / sign up. A new site starts with it on; the switch is at Sites → your site → Admin → Plugins (see Member accounts). New members flow into your CRM automatically.'
13173
13173
  },
13174
13174
  {
13175
13175
  path: '/workspace-and-billing/teams-and-roles/members-only',
@@ -13183,7 +13183,7 @@ export const DOCS_SECTION_INDEX = [
13183
13183
  title: 'Members-only areas',
13184
13184
  heading: 'Gate a page',
13185
13185
  anchor: '#gate-a-screen',
13186
- text: '1. Open the page you want to protect.\n2. Mark it members-only.\n3. Publish. Only signed-in members can now view it; everyone else is prompted to sign in.'
13186
+ text: 'Members-only pages are on Business and above.\n1. Open the page you want to protect.\n2. Mark it members-only.\n3. Publish. Only signed-in members can now view it; everyone else is prompted to sign in.'
13187
13187
  },
13188
13188
  {
13189
13189
  path: '/workspace-and-billing/teams-and-roles/members-only',