@aglyn/aglyn 1.0.0-beta.292 → 1.0.0-beta.293

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

@@ -513,7 +513,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Bring my site',
         heading: '',
         anchor: '',
-        text: 'Bring my site\nBeta Bring my site is in beta. It is available today on every plan that includes it, and it is still changing as we improve it. Beta means you can use it now, while how it reads and rebuilds your pages, and the steps on this page, may still change.\nBring my site moves the website you have now into a new Aglyn site. Aglyn AI reads each of its pages and rewrites it in your new site\'s design, keeping its words, facts and photos. Pages come in a few at a time, in waves. You review each wave before you start the next.\nIt is included on every paid plan. On the Free plan the card is shown but turned off, with a link to upgrade.'
+        text: 'Bring my site\nBeta Bring my site is in beta. It is available today on every plan that includes it, and it is still changing as we improve it. Beta means you can use it now, while how it reads and rebuilds your pages, and the steps on this page, may still change.\nBring my site moves the website you have now into a new Aglyn site. Each page keeps every word as you wrote it and is laid out as your page is: its sections and their backgrounds, its columns, cards, icons, pictures, tables and tabs, drawn with Aglyn\'s own elements in your site\'s look. Pages come in a few at a time, in waves, into your new site\'s preview. You review each wave before you start the next.\nIt is included on every paid plan. On the Free plan the card is shown but turned off, with a link to upgrade.'
     },
     {
         path: '/ai/bring-my-site',
@@ -541,21 +541,21 @@ export const DOCS_SECTION_INDEX = [
         title: 'Bring my site',
         heading: 'Read my site',
         anchor: '#read-my-site',
-        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.\nReading uses no AI credits.\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, and how many more pages could not be read;\n- how many pages your plan includes, how many will be brought in, and in how many waves;\n- if the read ran out of time before it reached every page, a line that says so;\n- each page\'s old address and its address on your new site, and Old page, which opens the page on your current site in a new tab;\n- under Not brought in, every page that was left out and the reason.\nNot brought in {#not-brought-in}\nEach page left out is listed under one of these reasons:\n- Past your plan\'s page count. See plans opens Billing.\n- Turned away by your site\'s bot protection or firewall. See When your site turns AglynBot away.\n- Not reached. The read stopped before it got to the page.\n- No text could be read. The page shows its words only once a browser runs it, so it cannot be brought in yet.\n- Could not be read just now, a'
+        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, price cards, tables and tabs, its pictures where they sit, 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, and how many more pages could not be read;\n- how many pages your plan includes, how many w'
     },
     {
         path: '/ai/bring-my-site',
         title: 'Bring my site',
         heading: 'Waves',
         anchor: '#waves',
-        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: your colors, read from your home page, on one of Aglyn\'s built-in themes, with type in the same style as yours. If you already chose a theme for the new site, it is kept. The first wave also builds your header and footer: your logo, your name, or both, as your current site\'s header shows them, your menu linking your pages, and the address, phone, email and profiles your current header and footer show. 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. Each page is built one of two ways, and the wave\'s row for the page says which:\n- Copied as it is: a page of a collection, such as a blog post or a policy, and any long page. Every heading, paragraph, list and link comes in, in order, laid out in your new site\'s theme.\n- Arranged by Aglyn AI: your main pages. Aglyn AI chooses how each section is laid out, such as its columns and background, and every line keeps the words your page has.\nTo start a wave, choose its Start button, for example Start Main pages. Each wave shows its cost before you start it, and how many of its pages are arranged and how many are copied. A page copied as it is costs far less than a page Aglyn AI arranges. Credits are used as each page is brought in. A page that fail'
+        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'
     },
     {
         path: '/ai/bring-my-site',
         title: 'Bring my site',
         heading: 'Review a wave',
         anchor: '#review-a-wave',
-        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- 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.'
+        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- 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.'
     },
     {
         path: '/ai/bring-my-site',
@@ -569,14 +569,14 @@ export const DOCS_SECTION_INDEX = [
         title: 'Bring my site',
         heading: 'What is never brought in',
         anchor: '#never-brought-in',
-        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 and forms. Scripts, embedded frames and forms are never brought in.\n- Other websites. Only pages on your own domain are read. A page that sends visitors to another website is left out.'
+        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 and forms. Scripts, embedded frames and forms are never brought in. Where your page had a form and your new site already has one saved form, that form is placed where your page had its own.\n- Other websites. Only pages on your own domain are read. A page that sends visitors to another website is left out.'
     },
     {
         path: '/ai/bring-my-site',
         title: 'Bring my site',
         heading: 'When an import waits for you',
         anchor: '#when-an-import-waits',
-        text: '- Verify your site again. A wave starts only while your proof is less than 30 days old. Choose Verify again, prove the site is yours once more, then start the wave again.\n- The day\'s limit. A workspace can start 12 waves a day, counting each time a site is read. Start the wave again the next day.\n- The site could not be read. If robots.txt could not be read, or no page answered, nothing is read. Choose Read the site again once your site is up. If your site\'s bot protection turned AglynBot away, see When your site turns AglynBot away.\n- AglynBot was turned away, or Your home page could not be read. Nothing was planned and no AI credits were used. Fix what the page names, then choose Check again.\n- Out of AI credits. The import pauses. Choose Get more AI credits, then Resume.\nEvery import is also logged for the Trust & Safety team\'s review.'
+        text: '- Verify your site again. A wave starts only while your proof is less than 30 days old. Choose Verify again, prove the site is yours once more, then start the wave again.\n- The day\'s limit. A workspace can start 12 waves a day, counting each time a site is read. Start the wave again the next day.\n- The site could not be read. If robots.txt could not be read, or no page answered, nothing is read. Choose Read the site again once your site is up. If your site\'s bot protection turned AglynBot away, see When your site turns AglynBot away.\n- AglynBot was turned away, or Your home page could not be read. Nothing was planned and no AI credits were used. Fix what the page names, then choose Check again.\n- Out of AI credits. The import pauses. Choose Get more AI credits, then Resume.'
     },
     {
         path: '/ai/bring-my-site',
@@ -919,7 +919,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Generate a website from a prompt',
         heading: 'Starting a new site from a few questions',
         anchor: '#starting-a-new-site-from-a-few-questions',
-        text: 'Create site opens Start your site straight away, before the site exists. Its first step asks the site\'s name and address, and one question: how do you want to start?\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 asks a few questions instead: what kind of site you are creating, who it is for, which of the starter shapes you like, and where your contact form\'s submissions should go. It writes the brief for you and plans the site from it. Back returns to the first question.\nEach answer changes what gets built. Who the site is for is who every page\'s search listing is written for, and who the contact form asks its questions of. Where submissions go is the form\'s routing: the Inbox, or the Inbox and a lead in CRM for every message that carries an email address. You can change that on the form itself afterwards.\nNothing is created until you choose. The starter card and Skip (in the bar at the top on both steps) create the site with the starter home page. 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. Once the site is being planned, closing only closes the window; the job carries on.\nUntil the job publishes its pages, a site that started with AI has no page yet, and its address shows a short coming soon page with the site\'s name, which search engines are asked not to index.\nEvery question, step and button of the guided start is walked through on Start a new site with AI.\nOn the Free plan\nA Free workspace\'s AI start builds one or two pages: the home page and the one page your business most needs, such as services, booking or contact. Paid plans can generate more page'
+        text: 'Create site opens Start your site straight away, before the site exists. Its first step asks the site\'s name and address, and one question: how do you want to start?\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, in a style you choose first.\n- Start with AI asks a few questions instead: what kind of site you are creating, who it is for, which of the starter shapes you like, and where your contact form\'s submissions should go. It writes the brief for you and plans the site from it. Back returns to the first question.\nEach answer changes what gets built. Who the site is for is who every page\'s search listing is written for, and who the contact form asks its questions of. Where submissions go is the form\'s routing: the Inbox, or the Inbox and a lead in CRM for every message that carries an email address. You can change that on the form itself afterwards.\nNothing is created until you choose, and nothing is chosen for you. The starter card asks you to choose a style, and its Create site creates the site with the starter home page in that style. 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. Once the site is being planned, closing only closes the window; the job carries on.\nUntil the job publishes its pages, a site that started with AI has no page yet, and its address shows a short coming soon page with the site\'s name, which search engines are asked not to index.\nEvery question, step and button of the guided start is walked through on Start a new site with AI.\nOn the Free plan\nA Free workspace\'s AI start builds one or two pages: the home page and the one page your business most ne'
     },
     {
         path: '/ai/generate-a-site',
@@ -1304,7 +1304,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Looks and themes for AI sites',
         heading: 'Choose a style',
         anchor: '#choose-a-style',
-        text: 'The Style step of Start your site offers these styles, each as a card with a picture of an example home page of that kind, drawn in its style. Pick for me, first and chosen unless you choose another, uses the style that what you said the site is suggests, and names it.\n| Style | For |\n| Business & services | A local business or service company. The fallback when nothing else fits. |\n| Home services & trades | Roofers, plumbers, electricians, cleaners and other trades. |\n| Law, finance & consulting | Professional practices. |\n| Health & wellness | Clinics, therapists and practitioners. |\n| Restaurant & café | Restaurants, cafés, bakeries and bars. |\n| Online store | A shop that sells products. On a paid plan it adds products. |\n| Portfolio | Showing your work. |\n| Design studio & agency | Studios and agencies. |\n| Photography | Photographers. |\n| Blog & writing | Reading-first pages. On a paid plan it adds posts. |\n| Events & weddings | An event, a venue or a planner. |\n| Fitness & sports | Gyms, trainers, teams and clubs. |\n| Yoga & mindfulness | Studios and teachers. |\n| Beauty & salon | Salons, barbers and spas. |\n| Real estate | Agents and agencies. |\n| Courses & education | Classes, tutors and schools. |\n| Nonprofit & community | Charities, groups and clubs. |\n| Music & bands | Musicians and bands. |\n| Personal & resume | A personal site or a resume. |\n| Landing page | One offer on one focused page. |\n| Coming soon | A placeholder that collects interest. |\nEach card says, in a line, what its look is like. Its picture is one variation of the style; your site gets its own. A style also suggests the pages that kind of site usually has, such as a menu for a restaurant or services for a trade.'
+        text: 'The Style step of Start your site offers these styles, each as a card with a picture of an example home page of that kind, drawn in its style. Nothing is chosen until you pick a card. Pick for me, the first card, uses the style that what you said the site is suggests, and names it.\nThe same styles start the starter site too. Start from the starter site, and Create site when Aglyn AI is not part of your plan, ask you to choose one of them before the site is created; there is no Pick for me there. The starter\'s home page, header and footer then come in that style\'s built-in theme, brand color and fonts, which you can change under Setup → Theme.\n| Style | For |\n| Business & services | A local business or service company. The fallback when nothing else fits. |\n| Home services & trades | Roofers, plumbers, electricians, cleaners and other trades. |\n| Law, finance & consulting | Professional practices. |\n| Health & wellness | Clinics, therapists and practitioners. |\n| Restaurant & café | Restaurants, cafés, bakeries and bars. |\n| Online store | A shop that sells products. On a paid plan it adds products. |\n| Portfolio | Showing your work. |\n| Design studio & agency | Studios and agencies. |\n| Photography | Photographers. |\n| Blog & writing | Reading-first pages. On a paid plan it adds posts. |\n| Events & weddings | An event, a venue or a planner. |\n| Fitness & sports | Gyms, trainers, teams and clubs. |\n| Yoga & mindfulness | Studios and teachers. |\n| Beauty & salon | Salons, barbers and spas. |\n| Real estate | Agents and agencies. |\n| Courses & education | Classes, tutors and schools. |\n| Nonprofit & community | Charities, groups and clubs. |\n| Music & bands | Musicians and bands. |\n| Personal & resume | A personal site or a resume. |\n| Landing page | One offer on one focuse'
     },
     {
         path: '/ai/site-looks',
@@ -1353,14 +1353,14 @@ 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.\nBring my site 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.'
+        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, in a style you choose: it asks you to Choose a style from the same cards as the Style step, without Pick for me, and Create site creates the site once you click one.\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 is a third card for moving the website you have now into Aglyn. See Bring my site.\nNo site exists until you choose, and nothing is chosen for you. Create site, after you choose a style for the starter site, creates the site with the starter home page in that style and opens 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 crea'
     },
     {
         path: '/ai/start-with-ai',
         title: 'Start a new site with AI',
         heading: 'The questions, one at a time',
         anchor: '#the-questions',
-        text: 'Start with AI asks one thing per step. The bar under the title shows where you are: Start, Your site, Audience, Style, Details and Review (on a phone, Step 3 of 6 and a progress bar). Next moves on and Back goes back; your answers are kept either way. Pressing Enter in a text answer is the same as Next. If a step cannot move on, the reason shows under the field and the cursor goes to it. Skip and the close control stay in the bar at the top on every step.\nEvery question step also has More details, a closed section under its answers with optional extras that fit the step. Open it to tell the site more about your business, or leave it closed. Everything in it can be changed later. If something in it cannot be used, Next opens it and says why under the field.'
+        text: 'Start with AI asks one thing per step. The bar under the title shows where you are: Start, Your site, Audience, Style, Details and Review (on a phone, Step 3 of 6 and a progress bar). Next moves on and Back goes back; your answers are kept either way. Pressing Enter in a text answer is the same as Next. If a step cannot move on, the reason shows under the field and the cursor goes to it. The close control stays in the bar at the top on every step.\nEvery question step also has More details, a closed section under its answers with optional extras that fit the step. Open it to tell the site more about your business, or leave it closed. Everything in it can be changed later. If something in it cannot be used, Next opens it and says why under the field.'
     },
     {
         path: '/ai/start-with-ai',
@@ -1381,7 +1381,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.\nSites you like {#sites-you-like}\nSites you like 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 colors, the mood of their type, their '
+        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. Nothing is chosen until you pick a card, and Next waits until you do: it says Choose a style, or Pick for me under the cards. Pick for me comes first and is a card you choose like the others. It names the style your first answer suggests, such as From your answer: Home services & trades, and uses it. 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 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 '
     },
     {
         path: '/ai/start-with-ai',
@@ -4057,6 +4057,13 @@ export const DOCS_SECTION_INDEX = [
         anchor: '#turn-it-on',
         text: '1. Open Admin → Error pages for the site — the same card that assigns your error pages. The switch takes every page of the site offline for every visitor, so the Admin area is limited to site admins.\n2. Switch on Maintenance mode — show the 503 page at every address. It confirms with "Maintenance mode on — visitors see the 503 page".\n3. Visitors now see your 503 error page on every path.\n4. When you\'re done, switch it back off and the site returns.\nIf you haven\'t assigned a 503 · Maintenance page, maintenance mode still works — but visitors get Aglyn\'s plain built-in notice ("This site is undergoing maintenance. Please check back shortly.") rather than anything on-brand. Design and assign the 503 first.'
     },
+    {
+        path: '/building-sites/site-protection/maintenance-mode',
+        title: 'Maintenance mode',
+        heading: 'Search engines and feeds',
+        anchor: '#search-engines-and-feeds',
+        text: 'While maintenance mode is on, every address tells search engines the site is down for a short while and to check back later. They don\'t take your 503 page for your site\'s content, so your pages aren\'t replaced by it in search results. Your site\'s search page and its collection feeds pause too, and come back when you switch maintenance mode off.\nKeep it short on a site that\'s already live. If a site stays unavailable for more than a couple of days, search engines may start dropping its pages.'
+    },
     {
         path: '/building-sites/site-protection/maintenance-mode',
         title: 'Maintenance mode',
@@ -4090,7 +4097,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Make your site private',
         heading: 'Hide the whole site until launch',
         anchor: '#hide-the-whole-site-until-launch',
-        text: 'Maintenance mode is the way to make the whole site private in one step. Every address on the site shows your 503 page to every visitor, including anyone who already has a link, and pages you add later are covered too.\n1. (Optional) Design a 503 · Maintenance page in the Besigner, such as a short "Coming soon" with your logo, and assign it in Admin → Error pages. See custom error pages. Without one, visitors see Aglyn\'s plain built-in notice.\n2. In the same Admin → Error pages card, switch on Maintenance mode — show the 503 page at every address. Only site admins can open the Admin area.\n3. Keep building. You and your team still edit pages, layouts and content in the console and the Besigner as usual. Maintenance mode only changes what the published site shows.\n4. On launch day, switch maintenance mode off. Your pages are live again within about a minute.\nThe 503 page is never offered to search engines, so nothing about the unfinished site gets indexed while maintenance mode is on.\nKeep one page open instead If you\'d rather keep a "coming soon" page open to collect email sign-ups while the rest of the site stays out of search, follow Launch a coming-soon page.'
+        text: 'Maintenance mode is the way to make the whole site private in one step. Every address on the site shows your 503 page to every visitor, including anyone who already has a link, and pages you add later are covered too.\n1. (Optional) Design a 503 · Maintenance page in the Besigner, such as a short "Coming soon" with your logo, and assign it in Admin → Error pages. See custom error pages. Without one, visitors see Aglyn\'s plain built-in notice.\n2. In the same Admin → Error pages card, switch on Maintenance mode — show the 503 page at every address. Only site admins can open the Admin area.\n3. Keep building. You and your team still edit pages, layouts and content in the console and the Besigner as usual. Maintenance mode only changes what the published site shows.\n4. On launch day, switch maintenance mode off. Your pages are live again within about a minute.\nSearch engines are told the site is temporarily unavailable, and the 503 page is never offered to them, so nothing about the unfinished site gets indexed while maintenance mode is on. The site\'s search page and its collection feeds pause too. See Search engines and feeds.\nKeep one page open instead If you\'d rather keep a "coming soon" page open to collect email sign-ups while the rest of the site stays out of search, follow Launch a coming-soon page.'
     },
     {
         path: '/building-sites/site-protection/make-your-site-private',
@@ -4400,6 +4407,76 @@ export const DOCS_SECTION_INDEX = [
         anchor: '#related',
         text: '- Build a blog\n- Templates, blocks & content'
     },
+    {
+        path: '/building-sites/site-templates/site-starters',
+        title: 'Site starters',
+        heading: '',
+        anchor: '',
+        text: 'Site starters\nRolling out Site starters from the marketplace are a release-flagged feature that is not yet available on aglyn.com-hosted workspaces. Until it is switched on for your workspace, Create site asks you to choose a style instead, as Create a site describes.\nA site starter is a ready-made website you create a new site from: its pages, the shared header and footer every page sits in, and its theme. You pick one in Create site, before the site exists, and the site is born with all of it, published.'
+    },
+    {
+        path: '/building-sites/site-templates/site-starters',
+        title: 'Site starters',
+        heading: 'Choose your starter',
+        anchor: '#choose-your-starter',
+        text: '1. Choose Create site on the All Sites page, or in the site switcher in the app bar.\n2. Name your site and choose its address.\n3. When you can use Aglyn AI, Start your site opens first: choose Start from a starter site. Otherwise Create site opens on Choose your starter straight away.\n4. Pick a starter card. Type in Search starters to find one by name, or choose a kind of site (Restaurant & café, Photography, Online store and the rest) to see only those; Every kind shows them all again.\n5. Choose Create site.\nNothing is chosen for you. No card is selected when the window opens, and Create site stays unavailable until you pick one you can create from. Closing the window creates nothing, and Back returns to Start your site as you left it.'
+    },
+    {
+        path: '/building-sites/site-templates/site-starters',
+        title: 'Site starters',
+        heading: 'What a card shows',
+        anchor: '#what-a-card-shows',
+        text: 'Each card shows a picture of the starter\'s home page, its name and who made it, and:\n- its price: Free, or the price you pay for it once;\n- Aglyn on Aglyn\'s own starters;\n- AI on an AI starter;\n- the kind of site it is made for;\n- how many pages it creates.'
+    },
+    {
+        path: '/building-sites/site-templates/site-starters',
+        title: 'Site starters',
+        heading: 'Where starters come from',
+        anchor: '#where-starters-come-from',
+        text: '- Aglyn\'s styles come first: one starter for each of the 21 styles Create site offers, with the same pictures. Picking one gives your site the starter pages in that style\'s look.\n- Then starters from the marketplace, made by publishers. A publisher\'s starter is reviewed by Aglyn before anyone else can see it.'
+    },
+    {
+        path: '/building-sites/site-templates/site-starters',
+        title: 'Site starters',
+        heading: 'Starters and AI starters',
+        anchor: '#starters-and-ai-starters',
+        text: 'Where Start your site is offered, Choose your starter has two tabs:\n- Starters are copied into your new site as they are: their pages, their header and footer, and their theme.\n- AI starters are a starting point for Aglyn AI\'s start, which writes the pages for your business. Creating a site from an AI starter is not available yet: Create site says so, and you can pick a starter from the Starters tab instead.'
+    },
+    {
+        path: '/building-sites/site-templates/site-starters',
+        title: 'Site starters',
+        heading: 'A starter with a price',
+        anchor: '#a-starter-with-a-price',
+        text: 'A card with a price says so when you pick it, with Buy and continue:\n1. Choose Buy and continue. The payment page opens.\n2. Pay. You come back to Create site with the same starter picked and You own this starter beneath the cards.\n3. Choose Create site.\nThe starter belongs to your workspace once it is paid for, so creating another site from it later asks for nothing more. If you come back without paying, the starter is still picked, and Buy and continue is there again. A starter you already own says You own this starter as soon as you pick it.'
+    },
+    {
+        path: '/building-sites/site-templates/site-starters',
+        title: 'Site starters',
+        heading: 'What your site gets',
+        anchor: '#what-your-site-gets',
+        text: '- Its pages, published as soon as the site is created. The console says Your site is live and names the starter it was made from, with View your site and Edit your pages. Turn on Start in preview before you create it to keep the site to your team until you make it public.\n- The shared header and footer every page you add renders inside.\n- Its theme: a built-in theme with the starter\'s brand color and fonts, or the starter\'s own theme, which is added to your site\'s themes named after the starter.\nA starter with more pages than your plan includes cannot be used. Create site says how many pages it has and how many your plan includes, and you can pick another.'
+    },
+    {
+        path: '/building-sites/site-templates/site-starters',
+        title: 'Site starters',
+        heading: 'Make it your own',
+        anchor: '#make-it-your-own',
+        text: 'Everything a starter creates is yours to change. Edit its pages under Pages, and pick another theme or change the colors and fonts under Setup → Theme. Changing them never changes the starter, and later changes to the starter never change your site.'
+    },
+    {
+        path: '/building-sites/site-templates/site-starters',
+        title: 'Site starters',
+        heading: 'Who can use them',
+        anchor: '#who-can-use-them',
+        text: 'Choosing a starter, and buying one, takes the Create sites permission, the same one creating any site does. Without it, Create site tells you so before anything is asked.'
+    },
+    {
+        path: '/building-sites/site-templates/site-starters',
+        title: 'Site starters',
+        heading: 'Related',
+        anchor: '#related',
+        text: '- Create a site\n- Your templates library, for the starter templates every site can use to add pages\n- Start a new site with AI'
+    },
     {
         path: '/building-sites/site-templates/templates-library',
         title: 'Your templates library',
@@ -4459,9 +4536,9 @@ export const DOCS_SECTION_INDEX = [
     {
         path: '/building-sites/site-templates/templates-library',
         title: 'Your templates library',
-        heading: 'First-party starters',
+        heading: 'Starter templates',
         anchor: '#first-party-starters',
-        text: 'Aglyn\'s starter sites (Landing Page, Business, Portfolio, the two Shop starters) are ordinary templates in your library — not a separate, locked-down kind. Every site gets its own copy, so you can open a starter in the besigner, edit it, keep versions of it, and use it to create pages exactly like a template you saved yourself. They carry the Starter badge, and they don\'t count against your plan\'s template allowance.\nA multi-page starter arrives as one template per page (the Shop starters are five), and Start from a template still shows them grouped as one card that creates all of the pages at once.\nYour Templates list groups them the same way: one row per starter, labeled with its page count, and its actions act on all of those pages — Use creates every page, and Delete removes every page. Open the row to see the pages individually; each one is an ordinary template you can edit, use or delete on its own from there.\nBecause your copy is yours, editing a starter is safe: Aglyn will not overwrite it later. Delete one you don\'t want and it stays deleted.'
+        text: 'Aglyn\'s starter templates (Landing Page, Business, Portfolio, the two Shop starters) are ordinary templates in your library — not a separate, locked-down kind. They add pages to a site you already have; to create a new site from a ready-made website, see Site starters. Every site gets its own copy, so you can open a starter in the besigner, edit it, keep versions of it, and use it to create pages exactly like a template you saved yourself. They carry the Starter badge, and they don\'t count against your plan\'s template allowance.\nA multi-page starter arrives as one template per page (the Shop starters are five), and Start from a template still shows them grouped as one card that creates all of the pages at once.\nYour Templates list groups them the same way: one row per starter, labeled with its page count, and its actions act on all of those pages — Use creates every page, and Delete removes every page. Open the row to see the pages individually; each one is an ordinary template you can edit, use or delete on its own from there.\nBecause your copy is yours, editing a starter is safe: Aglyn will not overwrite it later. Delete one you don\'t want and it stays deleted.'
     },
     {
         path: '/building-sites/site-templates/templates-library',
@@ -5728,14 +5805,14 @@ export const DOCS_SECTION_INDEX = [
         title: 'Quotes',
         heading: 'Attach proofs',
         anchor: '#proofs',
-        text: 'A proof shows your customer what they\'re getting before you make it: the canopy with their logo on it, the sign laid out at size. Attach proofs to a saved quote, and your customer sees them on the quote page, where they approve them or ask for changes.\n1. Open the quote and find Proofs in the editor.\n2. Choose Add proof and pick one or more files.\nA proof can be a PNG, JPEG, WebP, GIF, PDF, SVG, AI, EPS, PSD or TIFF file, up to 25 MB each, and a revision holds up to 10. Images show as pictures, and the other files as a chip with the file\'s name and size. Choose a picture or a chip to download the file.\nEvery file is checked before it\'s kept: a file whose contents aren\'t what its name says, or that carries a program, isn\'t taken, and an SVG is stripped of anything that could run. Proofs are kept privately with the quote. Only your team and the holder of the quote\'s link can open them, and never through a public address.\nTo take a proof off, choose Remove under it. You can add and remove proofs until your customer answers. After that, start a new revision to send different proofs.\nAdding or removing a proof changes what your customer sees, so it counts as an edit: a customer who has the page open is asked to look again before they answer or pay.'
+        text: 'A proof shows your customer what they\'re getting before you make it: the canopy with their logo on it, the sign laid out at size. Attach proofs to a saved quote, and your customer sees them on the quote page, where they approve them or ask for changes.\n1. Open the quote and find Proofs in the editor.\n2. Choose Add proof and pick one or more files.\nA proof can be a PNG, JPEG, WebP, GIF, PDF, SVG, AI, EPS, PSD or TIFF file, up to 25 MB each, and a revision holds up to 10. Images show as pictures, and the other files as a chip with the file\'s name and size. Choose a picture or a chip to download the file.\nEvery file is checked before it\'s kept: a file whose contents aren\'t what its name says, or that carries a program, isn\'t taken, and an SVG is stripped of anything that could run. Proofs are kept privately with the quote. Only your team and the holder of the quote\'s link can open them, and never through a public address.\nTo take a proof off, choose Remove under it. You can add and remove proofs until your customer answers. After that, start a new revision to send different proofs.\nProofs, and the files your customer sends with an answer, count toward your workspace\'s storage like files in the media library. Removing a proof or deleting the quote frees the space. A proof that would go past a storage cap you set, or past a full workspace on Free, is refused with the reason, as a media library upload would be. Your customer\'s files are always taken.\nAdding or removing a proof changes what your customer sees, so it counts as an edit: a customer who has the page open is asked to look again before they answer or pay.'
     },
     {
         path: '/commerce-and-bookings/commerce/quotes-and-proofs',
         title: 'Quotes',
         heading: 'What your customer sees of the proofs',
         anchor: '#customer-proofs',
-        text: 'When the current revision has proofs, the quote page shows them under the quote: each image as a picture and every other file as a download. Beside them are two choices:\n- Approve this proof. Your customer types their name and chooses Approve. The quote keeps their name, the time, and the address and browser it came from, as the record of the approval, and moves to Approved.\n- Request changes. Your customer says what should change, and can attach their own artwork: up to 10 files of the same kinds and size as proofs. The quote moves to Changes requested, with their comment and files.\nThe latest answer is the one that counts. A customer who asked for changes can still approve, and one who approved can still ask for changes, which withdraws the approval. The page tells them what they last said.\nYou\'re notified of every answer, in the console and by email, with the quote, the customer, the revision and what they said. The notice opens the quote, and replying to the email reaches your customer.\nA paid quote still shows its proofs, with nothing to press. A link you replaced shows nothing of the quote, proofs included, and takes no answer.'
+        text: 'When the current revision has proofs, the quote page shows them under the quote: each image as a picture and every other file as a download. Beside them are two choices:\n- Approve this proof. Your customer types their name and chooses Approve. The quote keeps their name, the time, and the address and browser it came from, as the record of the approval, and moves to Approved.\n- Request changes. Your customer says what should change, and can attach their own artwork: up to 10 files of the same kinds and size as proofs. The quote moves to Changes requested, with their comment and files. Files they attach and never send are deleted a day later.\nThe latest answer is the one that counts. A customer who asked for changes can still approve, and one who approved can still ask for changes, which withdraws the approval. The page tells them what they last said.\nYou\'re notified of every answer, in the console and by email, as Proof approved or Changes requested, with the quote, the customer, the revision, the quote\'s total and what they said. View quote opens the quote, and replying to the email reaches your customer. These notices follow your settings for order notifications.\nA paid quote still shows its proofs, with nothing to press. A link you replaced shows nothing of the quote, proofs included, and takes no answer.'
     },
     {
         path: '/commerce-and-bookings/commerce/quotes-and-proofs',
@@ -9032,14 +9109,14 @@ export const DOCS_SECTION_INDEX = [
         title: 'Publisher handbook',
         heading: 'Before your first publish',
         anchor: '#before-your-first-publish',
-        text: '1. Publisher profile (Marketplace → Profile) — your handle and display name appear on every listing. Publishing is organization-owned: the listing belongs to your organization, not your personal account.\n2. Publisher agreement — accept it once, on behalf of the organization. It is offered wherever you start a publish, and it is always on Marketplace → Profile. See The publisher agreement.\n3. Plan: publishing requires a Pro plan.\n4. Payouts (paid listings only): complete Stripe Connect onboarding from Marketplace → Payouts. The platform fee is 20% (30% on free plans).\nSet up your public profile {#public-profile}\nThe Public profile card on Marketplace → Profile is your publisher identity: set a handle, display name, bio and logo, then Save profile before you publish. They are shown on everything your organization publishes to the marketplace, and on your publisher page. The same card takes optional support contacts — a support email and URL — and links to your website, GitHub, X and LinkedIn, so buyers know where to ask for help.'
+        text: '1. Publisher profile (Marketplace → Profile) — your handle and display name appear on every listing. Publishing is organization-owned: the listing belongs to your organization, not your personal account.\n2. Publisher agreement — every save in the marketplace asks you to tick I agree to the Marketplace Publisher Agreement above its button first. See The publisher agreement.\n3. Plan: publishing requires a Pro plan.\n4. Payouts (paid listings only): complete Stripe Connect onboarding from Marketplace → Payouts. The platform fee is 20% (30% on free plans).\nSet up your public profile {#public-profile}\nThe Public profile card on Marketplace → Profile is your publisher identity: set a handle, display name, bio and logo, then Save profile before you publish. They are shown on everything your organization publishes to the marketplace, and on your publisher page. The same card takes optional support contacts — a support email and URL — and links to your website, GitHub, X and LinkedIn, so buyers know where to ask for help.'
     },
     {
         path: '/developers/plugins/publishing/publisher-handbook',
         title: 'Publisher handbook',
         heading: 'The publisher agreement',
         anchor: '#the-publisher-agreement',
-        text: 'Your organization — not you personally — is the publishing party, so the organization accepts the Marketplace Publisher Agreement once. Only an owner or admin can accept it, because only they can bind the organization, and we record who accepted it and when.\nYou do not have to go looking for it. When your organization has not accepted the current version, the agreement opens in a dialog wherever you are publishing — the plugin publish page, or the publish dialog for a component, layout, site template, theme, email template or dataset schema — as soon as you open it, and again if you submit without accepting. Accepting there records the same acceptance as Marketplace → Profile does, and the publish you started then goes ahead with everything you filled in. If you are not an owner or admin, the dialog names the people in your organization who can accept it.\nYou can read the agreement in full at aglyn.com/legal/marketplace-publisher-agreement, alongside the rest of the legal center. The version in force is stated at the top of that page, and it is the same string the panel records against your acceptance.\nIt is a different thing from the pre-publish checklist, and they are not interchangeable:\n| | Publisher agreement | Pre-publish checklist |\n| About | The relationship | The bytes in this bundle |\n| Scope | Your organization | One version |\n| Asked | Once, and again when the terms change | Every publish, including a republish of the same version number |\nThe summary shown above the accept button is the part that tends to surprise people later — the license you grant us to host, verify and distribute; what you warrant about each version; that you cannot recall code already installed; that we can disable a version everywhere without notice if it looks dangerous; that review '
+        text: 'Your organization — not you personally — is the publishing party, and the Marketplace Publisher Agreement is the set of terms it publishes under.\nEvery save in the marketplace asks for it. Above the button of every publisher form and dialog there is a box, unticked:\n> ☐ I agree to the Marketplace Publisher Agreement\nThe button stays off until you tick it, and the box is unticked again after each save, so the next save asks again. That covers everything a publisher does in the marketplace:\n- saving your public profile;\n- publishing a plugin, or a new version of one, from the plugin publish page;\n- publishing a component, layout, site template, theme, email template, email starter or dataset schema from its publish dialog;\n- saving a listing in Edit listing — its words, pictures, categories and links;\n- making a plugin private or public, and unpublishing or republishing a listing (each asks first, in a small dialog with the same box);\n- asking for the Verified badge, or withdrawing the ask.\nInstalling or buying from the marketplace is not a publisher save, and the Terms of Service cover it instead.\nEach agreement is recorded with your organization: the version you agreed to, who ticked the box, when, which save it was for, and the device\'s address and browser. Marketplace → Profile shows when your organization last agreed and to which version.\nYou can read the agreement in full at aglyn.com/legal/marketplace-publisher-agreement, alongside the rest of the legal center. The version in force is stated at the top of that page, and it is the same string each save records.\nIt is a different thing from the pre-publish checklist, and they are not interchangeable:\n| | Publisher agreement | Pre-publish checklist |\n| About | The relationship | The bytes in this bundle |\n| Scope | Yo'
     },
     {
         path: '/developers/plugins/publishing/publisher-handbook',
@@ -9067,14 +9144,14 @@ export const DOCS_SECTION_INDEX = [
         title: 'Publisher handbook',
         heading: 'Private plugins',
         anchor: '#private-plugins',
-        text: 'Choose Only this organization under Who can install this when you upload, and the listing becomes private: never browsable in the marketplace by anyone, and installable only by your own organization\'s sites. That last part is enforced when the install is requested, not by hiding the page — knowing a private listing\'s id gets a stranger nowhere.\nPrivate changes the audience, not the bar. Your bundle still runs on Aglyn infrastructure and still reaches the host ABI, so it goes through the same queue, the same reviewer checklist, the same static verifier, and the same super-staff signature if it ever needs realm trust. Staff see private submissions in the queue marked Private.\nPrivate plugins are always free, and you find yours under Marketplace → Listings rather than in Browse — View opens the same detail page you install from.\nGoing public later takes no re-review: the bytes were already approved, and who may install them was never part of that approval. It does ask for what any marketplace listing needs first — a description, a README, and a license — via Make public on the Listings row. Going back to private is always available and takes effect immediately.'
+        text: 'Choose Only this organization under Who can install this when you upload, and the listing becomes private: never browsable in the marketplace by anyone, and installable only by your own organization\'s sites. That last part is enforced when the install is requested, not by hiding the page — knowing a private listing\'s id gets a stranger nowhere.\nPrivate changes the audience, not the bar. Your bundle still runs on Aglyn infrastructure and still reaches the host ABI, so it goes through the same queue, the same reviewer checklist, the same static verifier, and the same super-staff signature if it ever needs realm trust. Staff see private submissions in the queue marked Private.\nPrivate plugins are always free, and you find yours under Marketplace → Listings rather than in Browse — View opens the same detail page you install from.\nGoing public later takes no re-review: the bytes were already approved, and who may install them was never part of that approval. It does ask for what any marketplace listing needs first — a description, a README, and a license — via Make public… on the Listings row. Going back to private is always available and takes effect immediately. Either way you confirm it in a small dialog, with the publisher agreement box above its button.'
     },
     {
         path: '/developers/plugins/publishing/publisher-handbook',
         title: 'Publisher handbook',
         heading: 'Authoring your listing',
         anchor: '#authoring-your-listing',
-        text: 'Your listing IS your storefront — it renders on the detail page every buyer sees. Editable at publish time or any time after, no republish needed: open Edit listing on your own listing\'s detail page (the whole page becomes the editor), or use the Edit action on Marketplace → Listings.\n| Field | Guidance |\n| Name | The display name on every browse card and at the top of the detail page; ≤80 chars. A typo here is fixable without republishing — leaving it blank keeps the current name rather than clearing it. |\n| Description | The one-line summary under the name on browse cards; ≤500 chars. |\n| Body (About) | The main docs: what it does, setup, what it adds, data & permissions. Rich-text editor with headings, bold/italic, links, and inline images; ≤20k chars. |\n| Preview image | The hero shown on browse cards and at the top of the detail page — pick it from your media library. |\n| Logo | Square; pick from the media library or paste an https URL. |\n| Screenshots | Up to 6, from the media library or https URLs; the detail page shows a gallery with click-to-zoom. |\n| Categories | Up to 3 from the fixed taxonomy. |\n| License | Short label (e.g. MIT) — listings without one get flagged in review. |\n| Homepage / repository | Public links build trust; reviewers check them. The repository is asked for at publish and required — editing it here changes the listing, not what past versions declared. |\nEdit a listing {#edit-listing}\nSelect Edit listing on your own listing\'s detail page and the page becomes the editor for what buyers see: name, summary, rich-text body and media. Save, and the listing changes at once — no new version, and no new review, because review is about the bundle\'s bytes rather than the words around them.\nYour listings {#your-listings}\nMarketplace → Listings lists '
+        text: 'Your listing IS your storefront — it renders on the detail page every buyer sees. Editable at publish time or any time after, no republish needed: open Edit listing on your own listing\'s detail page (the whole page becomes the editor), or use the Edit action on Marketplace → Listings.\n| Field | Guidance |\n| Name | The display name on every browse card and at the top of the detail page; ≤80 chars. A typo here is fixable without republishing — leaving it blank keeps the current name rather than clearing it. |\n| Description | The one-line summary under the name on browse cards; ≤500 chars. |\n| Body (About) | The main docs: what it does, setup, what it adds, data & permissions. Rich-text editor with headings, bold/italic, links, and inline images; ≤20k chars. |\n| Preview image | The hero shown on browse cards and at the top of the detail page — pick it from your media library. |\n| Logo | Square; pick from the media library or paste an https URL. |\n| Screenshots | Up to 6, from the media library or https URLs; the detail page shows a gallery with click-to-zoom. |\n| Categories | Up to 3 from the fixed taxonomy. |\n| License | Short label (e.g. MIT) — listings without one get flagged in review. |\n| Homepage / repository | Public links build trust; reviewers check them. The repository is asked for at publish and required — editing it here changes the listing, not what past versions declared. |\nEdit a listing {#edit-listing}\nSelect Edit listing on your own listing\'s detail page and the page becomes the editor for what buyers see: name, summary, rich-text body and media. Tick the publisher agreement box above Save listing and save, and the listing changes at once — no new version, and no new review, because review is about the bundle\'s bytes rather than the words around them.\nYour'
     },
     {
         path: '/developers/plugins/publishing/publisher-handbook',
@@ -10439,7 +10516,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Create a site',
         heading: 'Create your first site',
         anchor: '#create-your-first-site',
-        text: '1. Sign in to the console.\n2. Choose Create site on the All Sites page, or in the site switcher in the app bar (top-left). With no workspace yet, Create site on the empty console sets your workspace up first, then opens the same window in it.\n3. Give it a name. Aglyn suggests a subdomain from it and checks that it is free as you type, so the site has a real address from the first moment — you can attach a custom domain later.\nWhen you can use Aglyn AI, Create site opens Start your site, which asks for the name and address and how you want to start: Start from the starter site, or Start with AI, which plans your pages from a few questions — see Start a new site with AI. Nothing is created until you choose: Start from the starter site or Skip creates the site with the starter described below and publishes it at once, and the console says so: Your site is live, with the site\'s address, View your site and Edit your pages. Closing the window creates nothing.\nOtherwise Create site asks for the name and address and creates the site with the starter straight away. The starter is a complete website, published and open to search engines from the first visit:\n- a Home page at the site root with the sections an ordinary business site has — a hero with your site\'s name, what you offer, an about section, a photo gallery, testimonials, frequently asked questions, a call to action and a working contact form. Each section says how to make it yours, and the photos are placeholders to swap for your own under Media;\n- a shared header and footer layout every page you add renders inside, with your site\'s name, search, a light/dark switch and a Contact button. It is the site\'s one shared layout on the Free plan;\n- a theme (colors and fonts) under Setup → Theme, and a title, description and sh'
+        text: '1. Sign in to the console.\n2. Choose Create site on the All Sites page, or in the site switcher in the app bar (top-left). With no workspace yet, Create site on the empty console sets your workspace up first, then opens the same window in it.\n3. Give it a name. Aglyn suggests a subdomain from it and checks that it is free as you type, so the site has a real address from the first moment — you can attach a custom domain later.\nWhen you can use Aglyn AI, Create site opens Start your site, which asks for the name and address and how you want to start: Start from the starter site, or Start with AI, which plans your pages from a few questions — see Start a new site with AI. Nothing is created until you choose, and nothing is chosen for you.\nStart from the starter site asks you to Choose a style first: 21 cards, each with a picture of an example home page in that style — Business & services, Home services & trades, Restaurant & café, Photography and more. No card is selected until you click one, and Create site stays unavailable until you do. Choosing Create site then creates the site with the starter described below, in the style you chose — its built-in theme, brand color and fonts — and publishes it at once. The console says so: Your site is live, with the site\'s address, View your site and Edit your pages. Back returns to the first step, and closing the window creates nothing.\nChoose your starter is rolling out, and your workspace may not have it yet. Where it is on, Start from a starter site (or, without Aglyn AI, Create site itself) opens Choose your starter in place of the style cards: Aglyn\'s styles come first, then starters from the marketplace. A card with a price says so, and you buy it before the site is made. Nothing is chosen for you, Create site waits until you'
     },
     {
         path: '/getting-started/create-a-site',
@@ -11020,7 +11097,7 @@ export const DOCS_SECTION_INDEX = [
         title: 'Build a newsletter sign-up band',
         heading: '6. Build the band as a reusable component',
         anchor: '#6-build-the-band-as-a-reusable-component',
-        text: '1. Open Components → Create Component. Under Where will you use it? choose On pages, name it Newsletter band, and choose Next. Then Edit in Besigner.\n2. Give it two text properties so each page can change the words. Choose File → Properties… → Add property:\n| Name | Type | Label | Default |\n| heading | Text | Heading | Get product updates |\n| description | Text | Description | New features, guides, and early-access news — straight to your inbox. No spam. |\nChoose Save properties.\n3. Build the band from the Choose element picker:\n- a Section: the band itself. Set its Accessible label to Newsletter sign-up so screen readers can find it.\n- inside it, two Typography elements:\n- The first one\'s text is the heading property. Use the text field\'s {} button and pick heading from its Properties group. Set Variant to Heading 4 and Component to h2.\n- The second one\'s text is the description property, picked the same way, with Variant set to Body 1.\nSee Insert a variable.\n- a Form, from the Forms group. Pick Product updates under Form. The band now draws that form\'s field and button, styled as you styled them.\n4. Style the Section:\n- Colors:\n- Background Fill = Linear gradient. Set the Angle to 243, and bind its two color stops to the theme\'s Secondary and Primary colors. See Gradient backgrounds.\n- Text Color = common.white. The heading and copy inside inherit it.\n- Flexbox & Grid: Flex direction column, Align items center, Gap Small.\n- Typography: Text Alignment center.\n- In the spacing ring, Padding: Top and Bottom Huge, Left and Right Medium.\nBecause the gradient\'s stops are theme colors, each site that places the band shows it in that site\'s own colors.\n5. Give the two Typography elements a little polish:\n- The heading: Typography → Font Weight = Bold.\n- The description: Opaci'
+        text: '1. Open Components → Create Component. Under Where will you use it? choose On pages, name it Newsletter band, and choose Next. Then Edit in Besigner.\n2. Give it two text properties so each page can change the words. Choose File → Properties… → Add property:\n| Name | Type | Label | Default |\n| heading | Text | Heading | Get product updates |\n| description | Text | Description | New features, guides, and product news — straight to your inbox. No spam. |\nChoose Save properties.\n3. Build the band from the Choose element picker:\n- a Section: the band itself. Set its Accessible label to Newsletter sign-up so screen readers can find it.\n- inside it, two Typography elements:\n- The first one\'s text is the heading property. Use the text field\'s {} button and pick heading from its Properties group. Set Variant to Heading 4 and Component to h2.\n- The second one\'s text is the description property, picked the same way, with Variant set to Body 1.\nSee Insert a variable.\n- a Form, from the Forms group. Pick Product updates under Form. The band now draws that form\'s field and button, styled as you styled them.\n4. Style the Section:\n- Colors:\n- Background Fill = Linear gradient. Set the Angle to 243, and bind its two color stops to the theme\'s Secondary and Primary colors. See Gradient backgrounds.\n- Text Color = common.white. The heading and copy inside inherit it.\n- Flexbox & Grid: Flex direction column, Align items center, Gap Small.\n- Typography: Text Alignment center.\n- In the spacing ring, Padding: Top and Bottom Huge, Left and Right Medium.\nBecause the gradient\'s stops are theme colors, each site that places the band shows it in that site\'s own colors.\n5. Give the two Typography elements a little polish:\n- The heading: Typography → Font Weight = Bold.\n- The description: Opacity 0.'
     },
     {
         path: '/guides/newsletter-sign-up-band',
@@ -12504,14 +12581,14 @@ export const DOCS_SECTION_INDEX = [
         title: 'Billing & Plans',
         heading: 'Usage meters',
         anchor: '#usage-meters',
-        text: '- The billing page shows meters for every quota — storage, bandwidth, datasets, seats, sends, CRM records (with the contacts, companies and deals beneath the total), one-to-one emails sent today, AI assist credits, workflow and action runs, and more — with redesigned plan cards. Workflow and action runs are one monthly allowance for the whole workspace, so every site\'s runs count against them.\n- Storage is one allowance for the whole workspace too — see storage overage. Storage (organization) shows everything your workspace stores — every site\'s media library and the organization library — out of that allowance, with how much of it the organization library holds. Under each site, Storage on this site lists what that site\'s library holds: its share of the one allowance, not a limit of its own. The Metered usage estimate counts the organization library in the same Storage line; it has no separate allowance.\n- A usage-cap banner appears site-wide at 80% and 100% of a quota, with an upgrade link. Its storage warning is about the whole workspace\'s storage, and says what happens at the allowance on your plan: on a paid plan, extra storage is billed unless you set a storage cap, with a link to Billing → Usage; on Free, new uploads stop until you free up space or upgrade.\n- Org admins also get an in-app notification and an email when sites, pages on a site, storage, datasets, email sends, or bandwidth crosses 75%, 80%, 90% or 100%, so nobody has to be watching the console to find out. Only the highest step reached is sent — usage that jumps from 70% to 95% gets one 90% notice — and each is sent once per crossing: something your workspace has — sites, pages, datasets, stored files and data — is announced when it first reaches a threshold and again only if it drops below and reac'
+        text: '- The billing page shows meters for every quota — storage, bandwidth, datasets, seats, sends, CRM records (with the contacts, companies and deals beneath the total), one-to-one emails sent today, AI assist credits, workflow and action runs, and more — with redesigned plan cards. Workflow and action runs are one monthly allowance for the whole workspace, so every site\'s runs count against them.\n- Storage is one allowance for the whole workspace too — see storage overage. Storage (organization) shows everything your workspace stores — every site\'s media library, the organization library, and the proofs and customer files on quotes and forms — out of that allowance, with how much of it the organization library holds. Under each site, Storage on this site lists what that site\'s library holds: its share of the one allowance, not a limit of its own. The Metered usage estimate counts the organization library in the same Storage line; it has no separate allowance.\n- A usage-cap banner appears site-wide at 80% and 100% of a quota, with an upgrade link. Its storage warning is about the whole workspace\'s storage, and says what happens at the allowance on your plan: on a paid plan, extra storage is billed unless you set a storage cap, with a link to Billing → Usage; on Free, new uploads stop until you free up space or upgrade.\n- Org admins also get an in-app notification and an email when sites, pages on a site, storage, datasets, email sends, or bandwidth crosses 75%, 80%, 90% or 100%, so nobody has to be watching the console to find out. Only the highest step reached is sent — usage that jumps from 70% to 95% gets one 90% notice — and each is sent once per crossing: something your workspace has — sites, pages, datasets, stored files and data — is announced when it first reaches a'
     },
     {
         path: '/workspace-and-billing/billing-and-plans/overview',
         title: 'Billing & Plans',
         heading: 'Storage overage',
         anchor: '#storage-overage',
-        text: 'Your plan includes an amount of storage for each of its sites, and the workspace shares it as one allowance: every site\'s media library and the organization library draw on the same total. On a paid plan, going past it is not a wall:\n- Uploads keep working. You are never stopped from adding files because you reached your included storage.\n- The extra storage is billed on your monthly invoice at our infrastructure cost plus 30%, kept after card fees — the exact per-GB rate is on the pricing page and in Billing → Storage cap.\n- We tell you before it happens. You get an alert as you approach your included storage and another when you cross it, so the invoice is never the first you hear of it. See usage meters.\nIf you would rather uploads stopped\nSet a monthly storage cap on the Storage cap card under Billing → Usage when you would rather new uploads stopped than pay for extra storage past a figure you choose. This is optional and off unless you choose it. Once a month\'s storage overage would pass the amount you set, new uploads are refused and you are never billed above that number.\nYou can change or remove the cap at any time, including while you are over your included allowance. Nothing is ever deleted — a cap only affects new uploads, and removing one takes effect immediately.\nFree plans are never billed for storage On the Free plan there is no storage overage at all. Your included storage is a fixed cap, shared the same way: uploads stop when the workspace reaches it, wherever they are going, nothing is metered, and no amount of usage produces a charge — so there is nothing to cap and nothing to configure. Enterprise storage is a fixed default that an agreement raises, with no overage either: uploads stop there.\nNo surprise bills Two things prevent one, and they work i'
+        text: 'Your plan includes an amount of storage for each of its sites, and the workspace shares it as one allowance: every site\'s media library, the organization library, and the files kept with quotes and forms draw on the same total. On a paid plan, going past it is not a wall:\n- Uploads keep working. You are never stopped from adding files because you reached your included storage.\n- The extra storage is billed on your monthly invoice at our infrastructure cost plus 30%, kept after card fees — the exact per-GB rate is on the pricing page and in Billing → Storage cap.\n- We tell you before it happens. You get an alert as you approach your included storage and another when you cross it, so the invoice is never the first you hear of it. See usage meters.\nIf you would rather uploads stopped\nSet a monthly storage cap on the Storage cap card under Billing → Usage when you would rather new uploads stopped than pay for extra storage past a figure you choose. This is optional and off unless you choose it. Once a month\'s storage overage would pass the amount you set, new uploads are refused and you are never billed above that number.\nYou can change or remove the cap at any time, including while you are over your included allowance. Nothing is ever deleted — a cap only affects new uploads, and removing one takes effect immediately.\nFree plans are never billed for storage On the Free plan there is no storage overage at all. Your included storage is a fixed cap, shared the same way: your uploads stop when the workspace reaches it, wherever they are going, nothing is metered, and no amount of usage produces a charge — so there is nothing to cap and nothing to configure. Enterprise storage is a fixed default that an agreement raises, with no overage either: uploads stop there. Files your cu'
     },
     {
         path: '/workspace-and-billing/billing-and-plans/overview',