@aglyn/aglyn 1.0.0-beta.271 → 1.0.0-beta.272

package/src/lib/app-utils/docs-index.generated.js

@@ -1269,7 +1269,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Start a new site with AI',
         heading: 'How do you want to start?',
         anchor: '#how-do-you-want-to-start',
-        text: 'The first step asks for the site\'s Site name and Subdomain, its free address on Aglyn. The subdomain follows the name until you change it, and is checked as you type: if it is taken, the field says so and offers available ones to pick. Then it offers two cards:\n- Start from the starter site gives the site a ready-made home page with a header, footer and contact form, live at its address, for you to edit.\n- Start with AI (marked Recommended) asks the questions below and builds the site for you. On the Free plan the card says how many pages a Free start makes.\nNo site exists until you choose. Start from the starter site and Skip (in the bar at the top) create the site with the starter home page and open it. Plan my site creates the site and starts planning it. The close control and the Escape key create nothing: the window closes and no site is made. If you have typed or picked something, the window first asks Leave without your answers?, because what you typed is not saved. Once the site is being planned, closing only closes the window; the job carries on.\nIf your role cannot create sites, or your plan has no site left, Create site says so before asking anything. Plan my site checks that planning can start before it creates the site. If it cannot, the window says why and no site is made. On the Free plan, a start that may need more credits than you have left asks first, and the site is created only once you choose. If planning still cannot start after the site is created, the window says why; leaving then gives that site the starter home page, so it is never left empty.'
+        text: 'The first step asks for the site\'s Site name and Subdomain, its free address on Aglyn. The subdomain follows the name until you change it, and is checked as you type: if it is taken, the field says so and offers available ones to pick. Then it offers two cards:\n- Start from the starter site gives the site a ready-made home page with a header, footer and contact form, live at its address, for you to edit.\n- Start with AI (marked Recommended) asks the questions below and builds the site for you. On the Free plan the card says how many pages a Free start makes.\nBring my site (rolling out, not yet available) is a third card for moving the website you have now into Aglyn. See Bring my site.\nNo site exists until you choose. Start from the starter site and Skip (in the bar at the top) create the site with the starter home page and open it. Plan my site creates the site and starts planning it. The close control and the Escape key create nothing: the window closes and no site is made. If you have typed or picked something, the window first asks Leave without your answers?, because what you typed is not saved. Once the site is being planned, closing only closes the window; the job carries on.\nIf your role cannot create sites, or your plan has no site left, Create site says so before asking anything. Plan my site checks that planning can start before it creates the site. If it cannot, the window says why and no site is made. On the Free plan, a start that may need more credits than you have left asks first, and the site is created only once you choose. If planning still cannot start after the site is created, the window says why; leaving then gives that site the starter home page, so it is never left empty.'
     },
     {
         path: '/ai/start-with-ai',
@@ -1297,7 +1297,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Start a new site with AI',
         heading: 'Style',
         anchor: '#style',
-        text: 'The Style step shows each style as a card with a picture: an example home page of that kind of site, drawn in its style, each with a photo. A photographer\'s opens on a gallery, a café\'s on its heading centered over a photo of the café with its menu under it, an online store\'s on two photos of what it sells, a blog\'s on a centered heading above a wide photo, an events site\'s on its dates beside two photos of the day and a real estate site\'s on a card over a photo of a home, so you can see each style\'s colors, fonts, buttons and corners, and the shape of its pages, before you pick. The picked card is outlined in color and carries a check. See each style\'s layout. Pick for me comes first and is chosen unless you choose another. It names the style your first answer suggests, such as From your answer: Home services & trades. The style decides how the site looks and which pages it usually has: an online store, a portfolio, a restaurant, a blog and so on. Each site gets its own variation, so two sites with the same style still look different, and yours will not match the picture exactly. See Looks and themes for AI sites.\nMore details here: a Brand color, picked from the colors shown. It becomes your site\'s main color, kept readable everywhere it is used. Let the style choose leaves it to the style.'
+        text: 'The Style step shows each style as a card with a picture: an example home page of that kind of site, drawn in its style, each with a photo. A photographer\'s opens on a gallery, a café\'s on its heading centered over a photo of the café with its menu under it, an online store\'s on two photos of what it sells, a blog\'s on a centered heading above a wide photo, an events site\'s on its dates beside two photos of the day and a real estate site\'s on a card over a photo of a home, so you can see each style\'s colors, fonts, buttons and corners, and the shape of its pages, before you pick. The picked card is outlined in color and carries a check. See each style\'s layout. Pick for me comes first and is chosen unless you choose another. It names the style your first answer suggests, such as From your answer: Home services & trades. The style decides how the site looks and which pages it usually has: an online store, a portfolio, a restaurant, a blog and so on. Each site gets its own variation, so two sites with the same style still look different, and yours will not match the picture exactly. See Looks and themes for AI sites.\nMore details here: a Brand color, picked from the colors shown. It becomes your site\'s main color, kept readable everywhere it is used. Let the style choose leaves it to the style.\nSites you like {#sites-you-like}\nSites you like (rolling out, not yet available) is an optional block under the style cards. Type the address of a website whose look you like, such as https://example.com, in Site 1. A paid plan can name up to three sites. On the Free plan, Site 2 and Site 3 are shown but cannot be used, with the reason and an Upgrade link.\nAglyn AI takes only how those sites are laid out and styled: the order of their sections, their spacing and header, their color'
     },
     {
         path: '/ai/start-with-ai',
@@ -1325,7 +1325,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Start a new site with AI',
         heading: 'What gets built',
         anchor: '#what-gets-built',
-        text: 'Plan my site starts the job straight away. A guided start has no plan to approve. It builds, in this order:\n1. A look: a base theme, colors, fonts and the style of buttons, cards and forms, made for your kind of site. See Looks and themes.\n2. A header and footer, as the layout every page sits in, with a link to each page. The footer shows the phone and email you gave, as links that call and write.\n3. A contact form, saved on the Forms page, routed the way you chose, and placed on the page that needs it.\n4. Your first posts or products, when the site is a blog or, on paid plans, a store. See A store from the start and A blog from the start. Your first events, when your business holds them and your workspace has the Event Calendar add-on. See Events from the start.\n5. Your pages, each with its sections, its address and its own search title and description. A home page opens with a hero and has several bands below it, such as services, about, social proof and a closing call to action. Photos come from your media library or a stock photo, and every photo gets a description for screen readers and search engines. The page with your contact form also shows the phone and email you gave.\n6. A welcome email draft, if you asked for one.\n7. Publishing: see Published, and found by search engines.\nContact details are never made up. A phone number, email, address or opening hours appear only when you gave them on the Details step or entered them in your site settings.'
+        text: 'Plan my site starts the job straight away. A guided start has no plan to approve. It builds, in this order:\n1. A look: a base theme, colors, fonts and the style of buttons, cards and forms, made for your kind of site. See Looks and themes.\n2. A header and footer, as the layout every page sits in, with a link to each page. The footer shows the phone and email you gave, as links that call and write.\n3. A contact form, saved on the Forms page, routed the way you chose, and placed on the page that needs it.\n4. Your first posts or products, when the site is a blog or, on paid plans, a store. See A store from the start and A blog from the start. Your first events, when your business holds them and your workspace has the Event Calendar add-on. See Events from the start.\n5. Your pages, each with its sections, its address and its own search title and description. A home page opens with a hero and has several bands below it, such as services, about, social proof and a closing call to action. Photos come from your media library or a stock photo, and every photo gets a description for screen readers and search engines. The page with your contact form also shows the phone and email you gave. A list a page shows, such as your packages or your questions and answers, is kept as a dataset on plans that include datasets. It is shared with this site only, so you edit it on the Data page, and it is deleted with the site if you delete the site.\n6. A welcome email draft, if you asked for one.\n7. Publishing: see Published, and found by search engines.\nContact details are never made up. A phone number, email, address or opening hours appear only when you gave them on the Details step or entered them in your site settings.'
     },
     {
         path: '/ai/start-with-ai',
@@ -7541,7 +7541,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Datasets & Dynamic Content',
         heading: 'Who a dataset is shared with',
         anchor: '#who-a-dataset-is-shared-with',
-        text: 'Datasets belong to the workspace, not to a single site, so one dataset can drive pages on every site you run. When that isn\'t what you want, the Sharing control on each dataset decides which sites can see it:\n- All sites — everyone in the workspace, on every site.\n- Selected sites… — pick the sites that share it, up to 30.\nWhere a new dataset starts depends on where you create it and on your workspace\'s Default sharing for new datasets, the setting at the top of the organization Data page (new media files have a default of their own, on the workspace Media page):\n- Created on a site\'s Data page — it follows that setting. Set to All sites, the dataset starts on All sites. Set to Only the site they were created in, it starts shared with that site alone, and its control reads Selected sites… with just that site picked.\n- Created on the organization Data page — it starts on All sites whatever the setting says, because there is no site to limit it to.\n- Installed from the Marketplace, or created through the REST API — it starts on All sites too. Both act for the whole organization, not for one site.\nDefault sharing for new datasets {#default-dataset-sharing}\nDefault sharing for new datasets, at the top of the organization Data page, decides what a dataset created on a site\'s Data page starts shared with: All sites, or only that site. Only workspace owners and admins can change it.\nThe setting only decides where a new dataset starts. It changes nothing that already exists, and you can widen or narrow any dataset afterwards.\nA dataset with no sharing stored is visible to no site; its control reads Not shared with any site until you choose one of the two.\nThis matters most for agencies. If you run three internal sites alongside twelve client sites, your rate card can be shared '
+        text: 'Datasets belong to the workspace, not to a single site, so one dataset can drive pages on every site you run. When that isn\'t what you want, the Sharing control on each dataset decides which sites can see it:\n- All sites — everyone in the workspace, on every site.\n- Selected sites… — pick the sites that share it, up to 30.\nWhere a new dataset starts depends on where you create it and on your workspace\'s Default sharing for new datasets, the setting at the top of the organization Data page (new media files have a default of their own, on the workspace Media page):\n- Created on a site\'s Data page — it follows that setting. Set to All sites, the dataset starts on All sites. Set to Only the site they were created in, it starts shared with that site alone, and its control reads Selected sites… with just that site picked.\n- Created on the organization Data page — it starts on All sites whatever the setting says, because there is no site to limit it to.\n- Installed from the Marketplace, or created through the REST API — it starts on All sites too. Both act for the whole organization, not for one site.\n- Made by Aglyn AI for a site — for example the lists a guided start builds, such as your packages or FAQs — it starts shared with that site alone, whatever the setting says, because it was made for that site. Share it with more sites from its Sharing control.\nDefault sharing for new datasets {#default-dataset-sharing}\nDefault sharing for new datasets, at the top of the organization Data page, decides what a dataset created on a site\'s Data page starts shared with: All sites, or only that site. Only workspace owners and admins can change it.\nThe setting only decides where a new dataset starts. It changes nothing that already exists, and you can widen or narrow any dataset afterwa'
     },
     {
         path: '/content-and-data/datasets/overview',
@@ -9795,7 +9795,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'The console tour',
         heading: 'The Sites list',
         anchor: '#the-sites-list',
-        text: 'All Sites is the front door of a workspace: one card per site, for the workspace currently selected in the switcher, in name order. A site you can reach in another organization isn\'t missing — it\'s behind the workspace switcher.\nEach card carries:\n- The site\'s display name as the title, with its hostname underneath as the subheader — the custom domain when the site has one, otherwise its name.aglyn.app address. Both are also listed inside the card, as Aglyn Domain and Custom Domain.\n- A status pill (below).\n- Visit, which opens the live site in a new tab, and Manage, which opens that site\'s dashboard in the console.\nAbove the cards are a Search box and a Filters button — the same controls a table\'s toolbar has, over the cards. Search finds a site by the start of any word of its name, its slug (the name in name.aglyn.app) or its custom domain: harbor, bakery and shop.harbor all find Harbor Bakery at shop.harbor-bakery.com. Filters narrows the cards by Custom domain (Connected or None) and by the day a site was Created — is, after, on or after, before or on or before a day. Each filter in force shows as a chip above the cards; remove a chip to drop it. A filter on the created date lists the cards newest first instead of by name.\nThe search and the filters are answered by the query that reads the cards, across every site you have in the workspace, not only the cards on screen. The cards come twelve at a time; Load more adds the next twelve that match. The site count opposite the heading always counts every site. Status, plan, owner and the last-updated date are not filters: a site\'s status can change with no save at all (a timed suspension ends on its own), and a site doesn\'t store its plan, owner or template. See Filter and search a list.\nA site card {#a-site-card}\nEach c'
+        text: 'All Sites is the front door of a workspace: one card per site, for the workspace currently selected in the switcher, with the sites you pinned first and the rest in name order. A site you can reach in another organization isn\'t missing — it\'s behind the workspace switcher.\nEach card carries:\n- The site\'s display name as the title, with its hostname underneath as the subheader — the custom domain when the site has one, otherwise its name.aglyn.app address. Both are also listed inside the card, as Aglyn Domain and Custom Domain.\n- A status pill (below).\n- A pin, beside the pill. Pinned sites lead the list in the order you pinned them, and the site switcher in the top bar lists them first too. You can pin up to five sites in each workspace; pinning a sixth asks which one it replaces. Your pins are yours alone, and they follow you to every device you sign in on.\n- Visit, which opens the live site in a new tab, and Manage, which opens that site\'s dashboard in the console.\nAbove the cards are a Search box and a Filters button — the same controls a table\'s toolbar has, over the cards. Search finds a site by the start of any word of its name, its slug (the name in name.aglyn.app) or its custom domain: harbor, bakery and shop.harbor all find Harbor Bakery at shop.harbor-bakery.com. Filters narrows the cards by Custom domain (Connected or None) and by the day a site was Created — is, after, on or after, before or on or before a day. Each filter in force shows as a chip above the cards; remove a chip to drop it. A filter on the created date lists the cards newest first instead of by name. While a search or a filter is in force, pinned sites don\'t jump to the top: they sit where the list puts them, with their pin showing.\nThe search and the filters are answered by the query that re'
     },
     {
         path: '/getting-started/console-tour',
@@ -11853,7 +11853,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Downgrading, canceling & your data',
         heading: 'Deleting a single site',
         anchor: '#deleting-a-single-site',
-        text: 'To remove just one site (not the whole organization), open the site\'s Admin → Danger zone and use Delete site. A site admin types the site name to confirm, and it\'s deleted immediately — its pages, media, and settings are permanently removed and its address stops resolving. Unlike an organization deletion there\'s no hold, so export a backup first (Setup → Backup & restore) if you might want it back. Your other sites and the organization are unaffected.\nA site in a consent group can\'t be deleted while it\'s in the group, because the group\'s other sites honor the unsubscribes it holds. Remove it from the group first, which copies those opt-outs to the sites that stay, then delete it. The same applies while a consent group change that includes the site is still finishing.'
+        text: 'To remove just one site (not the whole organization), open the site\'s Admin → Danger zone and use Delete site. A site admin types the site name to confirm, and it\'s deleted immediately — its pages, media, and settings are permanently removed and its address stops resolving. Unlike an organization deletion there\'s no hold, so export a backup first (Setup → Backup & restore) if you might want it back. Your other sites and the organization are unaffected.\nDeleting a site also deletes what is the site\'s own:\n- Datasets shared with this site only, with all their records. The Delete site card lists them, with how many records each holds, before you confirm. A dataset the site shares with other sites stays, and the site is removed from its sharing. A dataset shared with All sites isn\'t affected.\n- The site\'s AI jobs, AI insights and Assist conversations.\nTo keep a dataset, share it with another site, or with All sites, from its Sharing control on the Data page before you delete the site.\nA site in a consent group can\'t be deleted while it\'s in the group, because the group\'s other sites honor the unsubscribes it holds. Remove it from the group first, which copies those opt-outs to the sites that stay, then delete it. The same applies while a consent group change that includes the site is still finishing.'
     },
     {
         path: '/workspace-and-billing/billing-and-plans/downgrading-and-canceling',