@aglyn/aglyn 1.2.0 → 1.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +11 -11
- package/src/lib/app-utils/docs-help.generated.d.ts +1 -1
- package/src/lib/app-utils/docs-help.generated.js +2 -0
- package/src/lib/app-utils/docs-help.generated.js.map +1 -1
- package/src/lib/app-utils/docs-index.generated.js +31 -10
- package/src/lib/app-utils/docs-index.generated.js.map +1 -1
- package/src/lib/app-utils/lockdown.js +4 -1
- package/src/lib/app-utils/lockdown.js.map +1 -1
- package/src/lib/app-utils/plan-entitlements.d.ts +5 -0
- package/src/lib/app-utils/plan-entitlements.js +6 -0
- package/src/lib/app-utils/plan-entitlements.js.map +1 -1
- package/src/lib/app-utils/plugin-sale.d.ts +36 -0
- package/src/lib/app-utils/plugin-sale.js +37 -0
- package/src/lib/app-utils/plugin-sale.js.map +1 -0
- package/src/lib/app-utils/site-starter-pick.d.ts +11 -0
- package/src/lib/app-utils/site-starter-pick.js +17 -1
- package/src/lib/app-utils/site-starter-pick.js.map +1 -1
- package/src/lib/app-utils/site-starter-theme.d.ts +28 -1
- package/src/lib/app-utils/site-starter-theme.js +78 -4
- package/src/lib/app-utils/site-starter-theme.js.map +1 -1
- package/src/lib/app-utils/site-styles.d.ts +11 -0
- package/src/lib/app-utils/site-styles.js +11 -0
- package/src/lib/app-utils/site-styles.js.map +1 -1
- package/src/lib/app-utils/site-unavailable.d.ts +22 -2
- package/src/lib/app-utils/site-unavailable.js +19 -3
- package/src/lib/app-utils/site-unavailable.js.map +1 -1
- package/src/lib/plugin-manager/feature-plugins.d.ts +6 -1
- package/src/lib/plugin-manager/feature-plugins.js.map +1 -1
|
@@ -548,7 +548,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
548
548
|
title: 'Bring my site',
|
|
549
549
|
heading: 'Read my site',
|
|
550
550
|
anchor: '#read-my-site',
|
|
551
|
-
text: 'Choose Read my site. Aglyn then:\n- creates your new site, with nothing on it and nothing published;\n- reads your current site as AglynBot, starting with its robots.txt file and its sitemap, then your home page, then every other page, and only on your own domain. Your current site is not changed.\nAglyn reads up to 400 pages. A link to a file, such as a download or a PDF, is not a page, so it is never read as one and never counts toward that number.\nReading uses no AI credits.\nWhat is read. For each page Aglyn reads its words and how your site lays them out: its sections and their background colors, its columns, its cards and the icons on them, its numbered steps, figures, questions and answers, quotes, logo strips,
|
|
551
|
+
text: 'Choose Read my site. Aglyn then:\n- creates your new site, with nothing on it and nothing published;\n- reads your current site as AglynBot, starting with its robots.txt file and its sitemap, then your home page, then every other page, and only on your own domain. Your current site is not changed.\nAglyn reads up to 400 pages. A link to a file, such as a download or a PDF, is not a page, so it is never read as one and never counts toward that number.\nReading uses no AI credits.\nWhat is read. For each page Aglyn reads its words and how your site lays them out: its sections and their background colors, its columns, its cards and the icons on them, its numbered steps, figures, questions and answers, quotes, logo strips, plan cards with their badge, price and button, plan rows, tables and tabs, its pictures where they sit, your forms with their fields and their button, and which links your site shows as buttons. From your home page it also reads your menu, with each dropdown and its entries, the buttons beside it, and your footer\'s columns, profiles and copyright line, plus your site\'s fonts and colors. Your new pages are built from this, with every word as you wrote it.\nYour home page comes first. If AglynBot cannot read your home page, nothing is planned and no AI credits are used. The import waits and says why:\n- AglynBot was turned away means your site\'s bot protection or firewall refused it. See When your site turns AglynBot away.\n- Your home page could not be read means your home page answered with an error or did not answer. Check that your site is up, then choose Check again.\nCheck again reads your site again, and uses no AI credits either.\nWhen it is done, Your site is read shows:\n- what was found, grouped as your Main pages and each collection, such as a blog\'s posts'
|
|
552
552
|
},
|
|
553
553
|
{
|
|
554
554
|
path: '/ai/bring-my-site',
|
|
@@ -562,7 +562,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
562
562
|
title: 'Bring my site',
|
|
563
563
|
heading: 'Review a wave',
|
|
564
564
|
anchor: '#review-a-wave',
|
|
565
|
-
text: 'When a wave is in, its page says so, for example Main pages is in your site\'s preview, and shows:\n- every page of the wave, with Open draft, its old and new address, and Old page to compare it with the page on your current site;\n- how many of the page\'s photos came in, for example 3 of 5 photos, with how many were already in your media library and how many could not be brought in;\n- a page that could not be brought in, with the reason;\n- how many AI credits the wave used.\nIf your site started in preview, each wave\'s pages are published into the preview as the wave comes in. You, your team and Aglyn support can open the site and see them at their addresses, home at your site\'s address. Visitors still see Coming soon. To make the site public, switch Preview off in Admin → Error pages, or choose Make it public on the banner that says your site is in preview.\nIf your site is not in preview, every page is a draft: nothing is published until you publish it.\nOpen your draft pages opens the site\'s Pages list. When you are ready for more, choose the next wave\'s Start button. Nothing starts the next wave except you, unless you chose Start every remaining wave.\nCancel stops the import. The pages already brought in stay where they are: in the preview, or as drafts. Under Every wave, a wave that was running reads stopped, and a wave that had not started reads not started.'
|
|
565
|
+
text: 'When a wave is in, its page says so, for example Main pages is in your site\'s preview, and shows:\n- every page of the wave, with Open draft, its old and new address, and Old page to compare it with the page on your current site;\n- how many of the page\'s photos came in, for example 3 of 5 photos, with how many were already in your media library and how many could not be brought in;\n- a page that could not be brought in, with the reason;\n- a page whose form was rebuilt, with the form\'s name;\n- how many AI credits the wave used.\nIf your site started in preview, each wave\'s pages are published into the preview as the wave comes in. You, your team and Aglyn support can open the site and see them at their addresses, home at your site\'s address. Visitors still see Coming soon. To make the site public, switch Preview off in Admin → Error pages, or choose Make it public on the banner that says your site is in preview.\nIf your site is not in preview, every page is a draft: nothing is published until you publish it.\nOpen your draft pages opens the site\'s Pages list. When you are ready for more, choose the next wave\'s Start button. Nothing starts the next wave except you, unless you chose Start every remaining wave.\nCancel stops the import. The pages already brought in stay where they are: in the preview, or as drafts. Under Every wave, a wave that was running reads stopped, and a wave that had not started reads not started.'
|
|
566
566
|
},
|
|
567
567
|
{
|
|
568
568
|
path: '/ai/bring-my-site',
|
|
@@ -576,14 +576,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
576
576
|
title: 'Bring my site',
|
|
577
577
|
heading: 'What is never brought in',
|
|
578
578
|
anchor: '#never-brought-in',
|
|
579
|
-
text: '- Sign-in pages. A page that asks for a password is left out, and so is a page AglynBot is asked not to read by robots.txt.\n- Code
|
|
579
|
+
text: '- Sign-in pages. A page that asks for a password is left out, and so is a page AglynBot is asked not to read by robots.txt.\n- Code. Scripts and embedded frames are never brought in.\n- Forms that ask for a password or a card number. These are left out. Every other form on your page is rebuilt as a form of your new site, with the same fields, required marks and button, where your page had it. What visitors send lands in your Inbox, a form that asks for an email also asks for marketing consent, and rebuilding a form uses no AI credits. A form your new site already has is placed instead of a second copy. If your plan has no room for another form, the page comes in without it and its row says so. A form can\'t take a file here, so a file upload field is left out and the page\'s row names it.\n- Other websites. Only pages on your own domain are read. A page that sends visitors to another website is left out.'
|
|
580
580
|
},
|
|
581
581
|
{
|
|
582
582
|
path: '/ai/bring-my-site',
|
|
583
583
|
title: 'Bring my site',
|
|
584
584
|
heading: 'When an import waits for you',
|
|
585
585
|
anchor: '#when-an-import-waits',
|
|
586
|
-
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.'
|
|
586
|
+
text: '- Your import stopped before it finished. Something kept a page or a wave from going on. The import says how many pages are not in yet, and everything already brought in is safe. Choose Start for the wave it names and it goes on from where it stopped. If you chose Start every remaining wave, the waves after it keep going too.\n- 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.'
|
|
587
587
|
},
|
|
588
588
|
{
|
|
589
589
|
path: '/ai/bring-my-site',
|
|
@@ -4412,7 +4412,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
4412
4412
|
title: 'Save & share a template',
|
|
4413
4413
|
heading: 'Save your site as a template',
|
|
4414
4414
|
anchor: '#save-your-site-as-a-template',
|
|
4415
|
-
text: 'Saving a whole site is not done from the pages list — it lives in Setup.\n1. Open
|
|
4415
|
+
text: 'Saving a whole site is not done from the pages list — it lives in Setup.\n1. Open Admin → Backup & template for the site and find the Site template card.\n2. Click Publish as template.\n3. Fill in Template name, Description, Category (e.g. Portfolio, Restaurant) and Price (USD, 0 = free), then publish.\nThis captures every published page plus the theme, and publishes it to the marketplace — so it is a share, not a private snapshot. Re-publishing bumps the version. Add a preview image afterwards from Manage → Marketplace.\nSaving a single page instead\nTo reuse one page rather than a whole site, use the ⋮ row menu on the Pages list and choose Save as template. Layouts and Components have the same row action. These save into your own templates library and are not published anywhere until you publish them separately.'
|
|
4416
|
+
},
|
|
4417
|
+
{
|
|
4418
|
+
path: '/building-sites/site-templates/save-a-template',
|
|
4419
|
+
title: 'Save & share a template',
|
|
4420
|
+
heading: 'Publish as a starter',
|
|
4421
|
+
anchor: '#publish-as-a-starter',
|
|
4422
|
+
text: 'Publish as a starter is rolling out, and your workspace may not have it yet. Where it is on, the Site template card also offers Publish as a starter.\nA site starter is a ready-made website people pick in Create site, before their site exists: the new site is born with its pages, its shared header and footer, and its theme. Publishing your site as one:\n1. Open Admin → Backup & template for the site and find the Site template card.\n2. Click Publish as a starter.\n3. Check Listing name and Description, which start as the site\'s name and description, and fill in What kind of site is it? (for example Bakery or Law firm).\n4. Set Price (USD), or leave it empty for a free starter.\n5. Choose its Theme. Nothing is chosen for you, and Publish waits until you choose:\n- This site\'s built-in theme with its brand colors: the built-in theme the site wears, with the brand colors you set over it and its fonts. A site created from the starter can switch to another built-in theme. When your site wears a theme of its own rather than a built-in one, this choice is unavailable and the window says why.\n- The site\'s full theme: every color, font and style your site\'s theme sets. A site created from the starter gets it as one of its themes, named after the starter.\n6. Pick a Closest style if you like: the kind of site your starter is listed under when people choose a starter.\n7. Tick I agree to the Marketplace Publisher Agreement, then click Publish.\nWhat it captures {#what-a-starter-captures}\n- Every published page, as it was last published. A page that was never published is left out. The window says how many pages it captures.\n- The shared header and footer your Home page sits in.\n- The theme you chose.\nYour site itself is unaffected.\nBefore you can publish {#before-you-publish-a-starter}\nThe '
|
|
4416
4423
|
},
|
|
4417
4424
|
{
|
|
4418
4425
|
path: '/building-sites/site-templates/save-a-template',
|
|
@@ -4468,7 +4475,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
4468
4475
|
title: 'Site starters',
|
|
4469
4476
|
heading: 'A starter with a price',
|
|
4470
4477
|
anchor: '#a-starter-with-a-price',
|
|
4471
|
-
text: 'A card with a price says so when you pick it, with Buy and continue:\n1. Choose Buy and continue. The
|
|
4478
|
+
text: 'A card with a price says so when you pick it, with Buy and continue. You pay right there, in Create site:\n1. Choose Buy and continue. The price, the sales tax, the total and the card that will be charged open under the cards. Nothing is charged yet.\n2. Choose Pay. Your workspace\'s card on file is charged, and You own this starter appears beneath the cards. If your bank wants to confirm the payment, its own step opens first.\n3. Choose Create site.\nAn AI starter with a price works the same way, with Continue in place of Create site: its answers are shown only once it is yours.\nIf your workspace has no card on file, the form to add one opens in the same place, and then one for a billing address if there is none: sales tax is calculated from it. Both stay on file for the workspace under Organization → Billing, where you can change them. If the card is declined, nothing is charged: the step says why, with a link to Billing to change the card.\nPaying charges your workspace\'s card, so it takes the Manage billing permission as well as Create sites. Without it you still see the price, the sales tax and the total, but there is no Pay, and the step says someone who manages billing can buy it. Once they have, anyone who can create sites can use the starter.\nThe starter belongs to your workspace once it is paid for, so creating another site from it later asks for nothing more. Cancel charges nothing, and Buy and continue is there again. A starter you already own says You own this starter as soon as you pick it.\nThe receipt is the invoice under Organization → Billing → Invoices. To ask for a refund, contact support, as for any marketplace purchase.'
|
|
4472
4479
|
},
|
|
4473
4480
|
{
|
|
4474
4481
|
path: '/building-sites/site-templates/site-starters',
|
|
@@ -4489,14 +4496,28 @@ export const DOCS_SECTION_INDEX = [
|
|
|
4489
4496
|
title: 'Site starters',
|
|
4490
4497
|
heading: 'Who can use them',
|
|
4491
4498
|
anchor: '#who-can-use-them',
|
|
4492
|
-
text: 'Choosing a starter
|
|
4499
|
+
text: 'Choosing a starter takes the Create sites permission, the same one creating any site does. Without it, Create site tells you so before anything is asked. Paying for one also takes Manage billing, as A starter with a price says.'
|
|
4500
|
+
},
|
|
4501
|
+
{
|
|
4502
|
+
path: '/building-sites/site-templates/site-starters',
|
|
4503
|
+
title: 'Site starters',
|
|
4504
|
+
heading: 'Publishing your own',
|
|
4505
|
+
anchor: '#publishing-your-own',
|
|
4506
|
+
text: 'Any workspace whose plan includes selling on the marketplace can publish one of its sites as a starter, free or with a price: Admin → Backup & template → Publish as a starter. You choose whether it carries your site\'s built-in theme with its brand colors, or your site\'s full theme. A new starter is reviewed before anyone else can see it. Publish as a starter walks through it.'
|
|
4507
|
+
},
|
|
4508
|
+
{
|
|
4509
|
+
path: '/building-sites/site-templates/site-starters',
|
|
4510
|
+
title: 'Site starters',
|
|
4511
|
+
heading: 'In the Aglyn app',
|
|
4512
|
+
anchor: '#in-the-aglyn-app',
|
|
4513
|
+
text: 'Create site in the Aglyn app on iPhone, iPad, Mac and Android lists the same starters, and nothing is chosen for you there either. A free starter, or one your workspace owns, creates your site at once.\nThe app doesn\'t take payment for a starter and doesn\'t ask an AI starter\'s questions. A starter with a price shows it with Buy on the web, and an AI starter shows Continue on the web. Either one opens Create site in the console on that starter, where you finish. You may be asked to sign in there first.\nYou can also publish from the app: Site settings → Backup & template → Publish as a starter, or A site starter on its Publish to the marketplace page.'
|
|
4493
4514
|
},
|
|
4494
4515
|
{
|
|
4495
4516
|
path: '/building-sites/site-templates/site-starters',
|
|
4496
4517
|
title: 'Site starters',
|
|
4497
4518
|
heading: 'Related',
|
|
4498
4519
|
anchor: '#related',
|
|
4499
|
-
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'
|
|
4520
|
+
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\n- Publish as a starter'
|
|
4500
4521
|
},
|
|
4501
4522
|
{
|
|
4502
4523
|
path: '/building-sites/site-templates/templates-library',
|
|
@@ -9200,7 +9221,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
9200
9221
|
title: 'Publisher handbook',
|
|
9201
9222
|
heading: 'How installs work (the buyer side)',
|
|
9202
9223
|
anchor: '#how-installs-work-the-buyer-side',
|
|
9203
|
-
text: 'Browse is a catalog — cards link to the detail page, which is the only place an install happens. The buyer picks targets (all sites, selected sites, or org-wide for plugins), confirms a dialog that names exactly where the install lands, and the pin is written: your exact {version, sha256} pinned to the site or org, the plugin enabled for the workspace, loaded on their next visit. Buyers can uninstall from the listing\'s own detail page (Uninstall, or Uninstall org-wide for an org-scope pin) as well as from Marketplace → Installed — removing the pin and disabling it. Data your plugin created stays, so reinstalls resume cleanly. Paid listings require purchase before install; you see sales in your publisher ledger.\nThe detail page shows two install figures side by side: installs is the cumulative all-time total and only ever grows, while active counts the organizations and sites that currently hold a pin — it goes down when someone uninstalls. A big gap between the two is churn worth investigating.\nThe Install card {#install-card}\nThe Install card on a listing\'s detail page is where an install happens: choose where it lands — all sites, selected sites, or the whole organization for a plugin — then confirm. A paid listing asks for the purchase first, and the same card offers Uninstall (or Uninstall org-wide) once it is installed.\nInstalled from the marketplace {#installed-from-the-marketplace}\nInstalled from the marketplace, on the workspace\'s Plugins page, lists every marketplace item this workspace has installed — org-wide, or the sites it is on — with the version it is pinned to and whether an update is out. Open one to manage that installation; browse the marketplace to add one.\nLicenses {#licenses}\nA purchase licenses
|
|
9224
|
+
text: 'Browse is a catalog — cards link to the detail page, which is the only place an install happens. The buyer picks targets (all sites, selected sites, or org-wide for plugins), confirms a dialog that names exactly where the install lands, and the pin is written: your exact {version, sha256} pinned to the site or org, the plugin enabled for the workspace, loaded on their next visit. Buyers can uninstall from the listing\'s own detail page (Uninstall, or Uninstall org-wide for an org-scope pin) as well as from Marketplace → Installed — removing the pin and disabling it. Data your plugin created stays, so reinstalls resume cleanly. Paid listings require purchase before install; you see sales in your publisher ledger.\nThe detail page shows two install figures side by side: installs is the cumulative all-time total and only ever grows, while active counts the organizations and sites that currently hold a pin — it goes down when someone uninstalls. A big gap between the two is churn worth investigating.\nThe Install card {#install-card}\nThe Install card on a listing\'s detail page is where an install happens: choose where it lands — all sites, selected sites, or the whole organization for a plugin — then confirm. A paid listing asks for the purchase first, paid on that card with the workspace\'s card on file, and the same card offers Uninstall (or Uninstall org-wide) once it is installed.\nInstalled from the marketplace {#installed-from-the-marketplace}\nInstalled from the marketplace, on the workspace\'s Plugins page, lists every marketplace item this workspace has installed — org-wide, or the sites it is on — with the version it is pinned to and whether an update is out. Open one to manage that installation; browse the marketplace to add one.\nLicenses {#licenses}\nA purchase licenses'
|
|
9204
9225
|
},
|
|
9205
9226
|
{
|
|
9206
9227
|
path: '/developers/plugins/publishing/publisher-handbook',
|
|
@@ -10922,7 +10943,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10922
10943
|
title: 'Install your first marketplace item',
|
|
10923
10944
|
heading: 'Step 5 — Install it',
|
|
10924
10945
|
anchor: '#step-5-install',
|
|
10925
|
-
text: 'Press Install (or Buy for $…). A confirmation dialog names the listing, its type, its version, and — in bold — exactly where it\'s going:\n> Install Bookings Pro (plugin, v2.1).\n> This will be installed to all sites.\nRead that bold phrase. It is the last chance to catch a mis-set target, and it is why the dialog exists.\nChoose Install. That\'s it.\nTwo things happen that are worth knowing:\n- The install is version-pinned. You have v2.1 and you keep v2.1 until you deliberately upgrade. A publisher shipping v2.2 tomorrow does not change your sites overnight.\n- A plugin is enabled for the workspace automatically. You don\'t have to go and switch it on after installing.'
|
|
10946
|
+
text: 'Press Install (or Buy for $…). A confirmation dialog names the listing, its type, its version, and — in bold — exactly where it\'s going:\n> Install Bookings Pro (plugin, v2.1).\n> This will be installed to all sites.\nRead that bold phrase. It is the last chance to catch a mis-set target, and it is why the dialog exists.\nChoose Install. That\'s it.\nA paid listing is bought first, and you pay right there on the listing. Buy for $… opens the price, the sales tax, the total and the card that will be charged, under the button. Choose Pay and your workspace\'s card on file is charged. If your bank wants to confirm the payment, its own step opens first. If the workspace has no card or billing address on file, you add them in the same place. If the card is declined, nothing is charged: the step says why, with a link to Billing to change the card. The receipt is the invoice under Organization → Billing → Invoices, and the listing\'s button then reads Install.\nPaying charges the workspace\'s card, so it takes the Manage billing permission. Without it you still see the price, the sales tax and the total, but there is no Pay, and the step says someone who manages billing can buy it.\nTwo things happen that are worth knowing:\n- The install is version-pinned. You have v2.1 and you keep v2.1 until you deliberately upgrade. A publisher shipping v2.2 tomorrow does not change your sites overnight.\n- A plugin is enabled for the workspace automatically. You don\'t have to go and switch it on after installing.'
|
|
10926
10947
|
},
|
|
10927
10948
|
{
|
|
10928
10949
|
path: '/guides/install-your-first-plugin',
|