@aglyn/aglyn 1.20.2 → 1.21.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@aglyn/aglyn",
3
- "version": "1.20.2",
3
+ "version": "1.21.0",
4
4
  "license": "Apache-2.0",
5
5
  "homepage": "https://aglyn.com",
6
6
  "repository": {
@@ -37,16 +37,16 @@
37
37
  "./package.json": "./package.json"
38
38
  },
39
39
  "dependencies": {
40
- "@aglyn/shared-data-enums": "1.20.2",
41
- "@aglyn/shared-data-mdi": "1.20.2",
42
- "@aglyn/shared-data-types": "1.20.2",
43
- "@aglyn/shared-util-email": "1.20.2",
44
- "@aglyn/shared-util-first-touch": "1.20.2",
45
- "@aglyn/shared-util-http": "1.20.2",
46
- "@aglyn/shared-util-logger": "1.20.2",
47
- "@aglyn/shared-util-timestamp": "1.20.2",
48
- "@aglyn/shared-util-tools": "1.20.2",
49
- "@aglyn/shared-util-vendor": "1.20.2",
40
+ "@aglyn/shared-data-enums": "1.21.0",
41
+ "@aglyn/shared-data-mdi": "1.21.0",
42
+ "@aglyn/shared-data-types": "1.21.0",
43
+ "@aglyn/shared-util-email": "1.21.0",
44
+ "@aglyn/shared-util-first-touch": "1.21.0",
45
+ "@aglyn/shared-util-http": "1.21.0",
46
+ "@aglyn/shared-util-logger": "1.21.0",
47
+ "@aglyn/shared-util-timestamp": "1.21.0",
48
+ "@aglyn/shared-util-tools": "1.21.0",
49
+ "@aglyn/shared-util-vendor": "1.21.0",
50
50
  "@data-driven-forms/react-form-renderer": "^4.2.0",
51
51
  "@msgpack/msgpack": "^3.1.3",
52
52
  "@types/unist": "^3.0.3",
@@ -3012,7 +3012,7 @@ export const DOCS_SECTION_INDEX = [
3012
3012
  title: 'Connect a domain',
3013
3013
  heading: 'Steps',
3014
3014
  anchor: '#steps',
3015
- text: '1. In the site\'s Admin page, choose Custom Domain in its navigation. The card explains: "Point your domain at Aglyn, then verify. A subdomain like www uses a CNAME. A bare apex cannot carry a CNAME, so point it at the same hostname with an ALIAS — or use the A record if your registrar has no ALIAS. Any one of these verifies", and lists the records with your domain filled in, each with a line saying when it\'s the right one. Type a bare apex and the ALIAS line comes first; type a subdomain and the CNAME line does.\n2. At your registrar\'s DNS settings, add one of those records — see the quick reference below.\n3. Back in Aglyn, type your domain into the Domain field and press Verify & connect. Aglyn checks DNS from public resolvers and, if the record checks out, connects the domain in the same click.\n4. On success the card confirms "your-domain.com" connected and shows the domain as a green chip. An apex — connected by ALIAS or by A record, since both are checked the same way — gets an extra note: "Apex verified by the addresses it resolves to."\nIf DNS hasn\'t propagated yet, Verify & connect tells you what it found instead — either the record it saw and what it expected, or that no record exists yet — and asks you to try again in a while. Nothing is saved on a failed verify, so re-running it is always safe.'
3015
+ text: '1. In the site\'s Admin page, choose Custom Domain in its navigation. The card explains: "Point your domain at Aglyn, then verify. A subdomain like www uses a CNAME. A bare apex cannot carry a CNAME, so point it at the same hostname with an ALIAS — or use the A record if your registrar has no ALIAS. Any one of these verifies", and lists the records with your domain filled in, each with a line saying when it\'s the right one. Type a bare apex and the ALIAS line comes first; type a subdomain and the CNAME line does.\n2. At your registrar\'s DNS settings, add one of those records — see the quick reference below.\n3. Back in Aglyn, type your domain into the Domain field and press Verify & connect. Aglyn checks DNS from public resolvers and, if the record checks out, connects the domain in the same click.\n4. On success the card confirms "your-domain.com" connected and shows the domain as a green chip. An apex — connected by ALIAS or by A record, since both are checked the same way — gets an extra note: "Apex verified by the addresses it resolves to."\nYour DNS provider may add the record for you If your domain\'s DNS is at a provider that supports Domain Connect, such as Cloudflare, a Connect automatically with your provider button appears under the Domain field. You approve the change at your provider and skip steps 2 and 3. See Connect a domain automatically.\nIf DNS hasn\'t propagated yet, Verify & connect tells you what it found instead — either the record it saw and what it expected, or that no record exists yet — and asks you to try again in a while. Nothing is saved on a failed verify, so re-running it is always safe.'
3016
3016
  },
3017
3017
  {
3018
3018
  path: '/building-sites/custom-domains/connect-a-domain',
@@ -3056,6 +3056,34 @@ export const DOCS_SECTION_INDEX = [
3056
3056
  anchor: '#related',
3057
3057
  text: '- Troubleshoot verification\n- Redirects\n- SEO toolkit'
3058
3058
  },
3059
+ {
3060
+ path: '/building-sites/custom-domains/connect-automatically',
3061
+ title: 'Connect a domain automatically',
3062
+ heading: '',
3063
+ anchor: '',
3064
+ text: 'Connect a domain automatically\nIf you already own a domain, your DNS provider may be able to add Aglyn\'s records for you. It uses Domain Connect, an open standard for exactly this: you approve the change on your provider\'s own page, and there are no records to copy.\nCloudflare, NameSilo, Glauca and Domain Chief support it for Aglyn today. When another provider adds Aglyn, the button appears for its domains on its own, with nothing for you to change.'
3065
+ },
3066
+ {
3067
+ path: '/building-sites/custom-domains/connect-automatically',
3068
+ title: 'Connect a domain automatically',
3069
+ heading: 'Steps',
3070
+ anchor: '#steps',
3071
+ text: '1. In the site\'s Admin page, choose Custom Domain.\n2. Type your domain into the Domain field of the Custom domain card.\n3. If your DNS provider supports it, a button appears under the field: Connect automatically with your provider. Press it.\n4. Your provider opens in a new window. Sign in there and approve the change.\n5. Come back to Aglyn. The card says Waiting for your provider…, then Checking your domain…, and connects the domain as soon as the records answer.\nAglyn never sees your password at your provider: you sign in on the provider\'s own page, and it writes only the records Aglyn\'s template names. For a bare domain like yourbusiness.com, that is the domain and its www address, so both work.\nIf your domain also has an IPv6 (AAAA) record from a previous host, the card warns you under the button. Your provider replaces the domain\'s IPv4 address but leaves that record in place, so delete it while you\'re at your provider. Otherwise visitors on IPv6 keep reaching the old site.'
3072
+ },
3073
+ {
3074
+ path: '/building-sites/custom-domains/connect-automatically',
3075
+ title: 'Connect a domain automatically',
3076
+ heading: 'If there\'s no button',
3077
+ anchor: '#no-button',
3078
+ text: 'Your provider doesn\'t support Domain Connect for this domain, or hasn\'t approved Aglyn\'s template yet. Add the record the card shows instead — see Connect a domain.'
3079
+ },
3080
+ {
3081
+ path: '/building-sites/custom-domains/connect-automatically',
3082
+ title: 'Connect a domain automatically',
3083
+ heading: 'If it doesn\'t finish',
3084
+ anchor: '#problems',
3085
+ text: 'DNS changes can take a little while to reach the internet. If you closed the page, the connection still finishes on its own once the records answer, within 48 hours. If they never do, the card says so; add the records by hand, or try again.'
3086
+ },
3059
3087
  {
3060
3088
  path: '/building-sites/custom-domains/manage-domains',
3061
3089
  title: 'Manage your domains',
@@ -3103,7 +3131,7 @@ export const DOCS_SECTION_INDEX = [
3103
3131
  title: 'Manage your domains',
3104
3132
  heading: 'DNS records',
3105
3133
  anchor: '#dns',
3106
- text: 'DNS records tell the internet where your domain\'s website, email and other services live. You can edit them here for a domain that uses Aglyn\'s nameservers, which a domain bought here does.\n- Press Add record, pick a Type, and fill in its fields: Name (leave it empty for the domain itself, or enter a subdomain like shop), the value, and any fields that type needs, such as Priority for a mail server.\n- Click a record to change or delete it.\n- Records marked Managed by Aglyn are how visitors reach your site at this domain and keep its security certificate working: the address records for the domain itself and www, and any CAA records. They can\'t be changed here, and a new one can\'t be added over them. Disconnect the domain from its site first if you need to.\nIf a domain uses another provider\'s nameservers (common for a domain you just transferred in), the page names them and explains that its records are edited there. There\'s no editor for it here.'
3134
+ text: 'DNS records tell the internet where your domain\'s website, email and other services live. You can edit them here for a domain that uses Aglyn\'s nameservers, which a domain bought here does.\n- Press Add record, pick a Type, and fill in its fields: Name (leave it empty for the domain itself, or enter a subdomain like shop), the value, and any fields that type needs, such as Priority for a mail server.\n- Click a record to change or delete it.\n- Records marked Managed by Aglyn are how visitors reach your site at this domain and keep its security certificate working: the address records for the domain itself and www, and any CAA records. They can\'t be changed here, and a new one can\'t be added over them. Disconnect the domain from its site first if you need to.\nIf a domain uses another provider\'s nameservers (common for a domain you just transferred in), the page names them and explains that its records are edited there. To edit them here instead, a workspace owner or admin can press Use Aglyn\'s nameservers and confirm. Records kept at the old provider stop applying, such as email (MX) records, so note the ones you need first and add them again under DNS records afterwards. The change can take up to 48 hours to reach everyone.'
3107
3135
  },
3108
3136
  {
3109
3137
  path: '/building-sites/custom-domains/manage-domains',
@@ -3124,7 +3152,7 @@ export const DOCS_SECTION_INDEX = [
3124
3152
  title: 'Custom Domains',
3125
3153
  heading: 'Connect a domain',
3126
3154
  anchor: '#connect-a-domain',
3127
- text: '1. In Admin, choose Custom Domain in its navigation.\n2. Add one DNS record at your registrar — a CNAME to sites.aglyn.app for a subdomain, or an ALIAS/ANAME to the same hostname for a bare apex (an A record where your registrar offers no ALIAS).\n3. Type the domain into the Domain field and press Verify & connect. Aglyn checks DNS and connects the domain in the same click; SSL provisions automatically.\nEach site carries one custom domain, shown as a chip on the card with Re-attach and Disconnect actions beside it. Once it serves, your .aglyn.app subdomain redirects to it, path preserved, so old links keep working.\nHow-tos\n- Connect a domain — steps, apex records (ALIAS first, A as the fallback), and what happens after\n- Troubleshoot verification'
3155
+ text: '1. In Admin, choose Custom Domain in its navigation.\n2. Add one DNS record at your registrar — a CNAME to sites.aglyn.app for a subdomain, or an ALIAS/ANAME to the same hostname for a bare apex (an A record where your registrar offers no ALIAS).\n3. Type the domain into the Domain field and press Verify & connect. Aglyn checks DNS and connects the domain in the same click; SSL provisions automatically.\nEach site carries one custom domain, shown as a chip on the card with Re-attach and Disconnect actions beside it. Once it serves, your .aglyn.app subdomain redirects to it, path preserved, so old links keep working.\nHow-tos\n- Connect a domain — steps, apex records (ALIAS first, A as the fallback), and what happens after\n- Connect a domain automatically — let your DNS provider add the records in one click, where it supports Domain Connect\n- Troubleshoot verification'
3128
3156
  },
3129
3157
  {
3130
3158
  path: '/building-sites/custom-domains/overview',
@@ -8556,7 +8584,7 @@ export const DOCS_SECTION_INDEX = [
8556
8584
  title: 'Media Library & CDN',
8557
8585
  heading: 'Who an asset is shared with',
8558
8586
  anchor: '#who-an-asset-is-shared-with',
8559
- text: 'Workspace media is shared across every site by default. The Shared with control narrows that, with the same three choices as datasets:\n- All sites — every site in the workspace. A new site gets it automatically.\n- Selected sites — tick the sites that share it, up to 30. A new site doesn\'t get it until you add that site.\n- All sites except… — tick the sites to leave out. Every other site shares it, and a new site gets it automatically. A workspace with one site has nothing to leave out, so this choice stays off until you add a second, and at least one site has to stay in.\nA site left out can\'t find the file in its media picker, and its pages stop showing the file wherever they show it from the media library. A link to the file that was pasted as text into custom HTML on that site keeps loading: the workspace\'s media link serves a file shared with all sites except some to anyone who has it. Narrowing a file names the sites left out that use it, and says this, before you confirm.\nYou\'ll find the control in three places:\n- on a single asset, in its details drawer;\n- on a selection — tick several files and use Shared with… in the toolbar;\n- on a folder, from its ⋮ menu, which offers to apply the same sharing to the files inside it and its subfolders (it names the count, so you know what you\'re about to change).\nA folder applies its sharing when you save it — files keep their own setting afterwards, so moving a file into a "Client A" folder later does not re-share it. Narrowing a file that sites are already using names those sites first and asks you to confirm. Changing sharing takes the Edit the workspace media library permission, which workspace owners, admins and editors hold by default, and access to every site in the workspace: someone added to particular sites can\'t cha'
8587
+ text: 'Workspace media is shared across every site by default. The Shared with control narrows that, with the same three choices as datasets:\n- All sites — every site in the workspace. A new site gets it automatically.\n- Selected sites — tick the sites that share it, up to 30. A new site doesn\'t get it until you add that site.\n- All sites except… — tick the sites to leave out. Every other site shares it, and a new site gets it automatically. A workspace with one site has nothing to leave out, so this choice stays off until you add a second, and at least one site has to stay in.\nA site left out can\'t find the file in its media picker, and its pages stop showing the file wherever they show it from the media library. A link to the file that was pasted as text into custom HTML on that site keeps loading: the workspace\'s media link serves a file shared with all sites except some to anyone who has it. Narrowing a file names the sites left out that use it, and says this, before you confirm.\nYou\'ll find the control in three places:\n- on a single asset, in its details drawer;\n- on a selection — tick several files and use Shared with… in the toolbar;\n- on a folder, from its ⋮ menu, either on its card in the grid or on its row in the folder list beside it (both open the same dialog). It offers to apply the same sharing to the files inside it and its subfolders, and names the count, so you know what you\'re about to change.\nA folder applies its sharing when you save it — files keep their own setting afterwards, so moving a file into a "Client A" folder later does not re-share it. Narrowing a file that sites are already using names those sites first and asks you to confirm. The confirmation opens straight away and says it is checking which sites use the file; Limit access waits until the ch'
8560
8588
  },
8561
8589
  {
8562
8590
  path: '/content-and-data/media/overview',
@@ -9116,7 +9144,7 @@ export const DOCS_SECTION_INDEX = [
9116
9144
  title: 'Plugins & Marketplace',
9117
9145
  heading: 'What\'s included',
9118
9146
  anchor: '#whats-included',
9119
- text: 'A listing page carries a What\'s included box. Aglyn generates it from the listing — it is not publisher copy, so it cannot promise something the install does not do, and it says nothing about how much content is in there.\nThe first row is what the install physically produces, which depends on the type:\n| Type | The row reads |\n| Plugin | A plugin, sandboxed on its own origin with a per-plugin CSP — or, for a version staff signed to run with the site (realm trust), A plugin, reviewed and signed by Aglyn to run with your site |\n| Component | An editable component you can place on any page |\n| Template | Editable pages you can rework in Besigner |\n| Layout | An editable layout you can apply to any page |\n| Dataset schema | A new empty dataset with its fields already defined |\n| Email template | An editable email design you can send campaigns from |\n| Theme | A theme applied to the site you choose |\nA plugin whose version declares a connection to another service adds a plan row straight after it, marked as a note: Connecting Google Business Profile comes with the Starter, Pro and Custom plans. The plugin installs on any plan, but on Free its Connect button is disabled, so the shopper is told before installing rather than after.\nThen, in order, up to four more rows:\n- Where it lands. Plugins and dataset schemas install org-wide — Installs org-wide, covering sites you add later. Everything else is site-scoped and says so: Installs per site — new sites are not covered automatically. That row is marked as a note, not a tick, because it is a limit you are being told about rather than something you are getting.\n- Review — This version passed marketplace review — only when the version on offer is approved. A new release from the same publisher starts without it.\n- The license, whe'
9147
+ text: 'A listing page carries a What\'s included box. Aglyn generates it from the listing — it is not publisher copy, so it cannot promise something the install does not do, and it says nothing about how much content is in there.\nThe first row is what the install physically produces, which depends on the type:\n| Type | The row reads |\n| Plugin | A plugin that runs in its own secure space, separate from your site — or, for a version staff signed to run with the site (realm trust), A plugin, reviewed and signed by Aglyn to run with your site |\n| Component | An editable component you can place on any page |\n| Template | Editable pages you can rework in Besigner |\n| Layout | An editable layout you can apply to any page |\n| Dataset schema | A new empty dataset with its fields already defined |\n| Email template | An editable email design you can send campaigns from |\n| Theme | A theme applied to the site you choose |\nA plugin whose version declares a connection to another service adds a plan row straight after it, marked as a note: Connecting Google Business Profile comes with the Starter, Pro and Custom plans. The plugin installs on any plan, but on Free its Connect button is disabled, so the shopper is told before installing rather than after.\nThen, in order, up to four more rows:\n- Where it lands. The row follows the Install to choice on the card, so it never disagrees with it:\n| Install to | Plugin or dataset schema | Everything else |\n| All sites | Installs on every site, including sites you add later | Installs on the sites you have now. A new site doesn\'t get it automatically |\n| Selected sites | Installs only on the sites you pick. A new site doesn\'t get it until you add it | the same |\n| All sites except… | Installs on every site but the ones you leave out, including sites y'
9120
9148
  },
9121
9149
  {
9122
9150
  path: '/developers/plugins/overview',
@@ -11013,7 +11041,7 @@ export const DOCS_SECTION_INDEX = [
11013
11041
  title: 'Install your first marketplace item',
11014
11042
  heading: 'Step 4 — Choose which sites get it',
11015
11043
  anchor: '#step-4-targeting',
11016
- text: 'This is the step to read.\nOn the detail page you\'ll find Install to, with up to three choices:\n| Option | What it means |\n| All sites | Everything in the organization. For a plugin, that includes sites you add later. |\n| Selected sites | Only the sites you tick. A list of your sites appears underneath — tick at least one. |\n| All sites except… | Every site but the ones you tick to leave out. For a plugin, that includes sites you add later. Tick at least one, and keep at least one in. |\n"All sites" does not mean the same thing for every kind of listing, and that is the whole reason this step exists:\n- Plugins and dataset schemas install organization-wide. A site you create next month gets them too.\n- Components, templates, layouts, themes and email templates are site-scoped. "All sites" copies them onto every site you have right now; a site you add later will not have them. "All sites except…" works the same way: it copies them onto the sites you have now, minus the ones you leave out, and a site you add later will not have them.\nYou will have seen this fact once already, in the What\'s included box further up the page — Installs org-wide, covering sites you add later, or Installs per site — new sites are not covered automatically. The line under each Install to choice is the same fact with your own numbers in it: for the site-scoped case it reads "Installs to all 4 sites. New sites won\'t get it automatically." Two wordings, one behavior — if they ever seem to disagree, the line under the choice is the one counting your actual sites.\n"Selected sites" and "All sites except…" only appear when there\'s a choice to make. A dataset schema installs for the whole organization, so it offers All sites alone. On a one-site organization "All sites except…" is switched off, because th'
11044
+ text: 'This is the step to read.\nOn the detail page you\'ll find Install to, with up to three choices:\n| Option | What it means |\n| All sites | Everything in the organization. For a plugin, that includes sites you add later. |\n| Selected sites | Only the sites you tick. A list of your sites appears underneath — tick at least one. |\n| All sites except… | Every site but the ones you tick to leave out. For a plugin, that includes sites you add later. Tick at least one, and keep at least one in. |\n"All sites" does not mean the same thing for every kind of listing, and that is the whole reason this step exists:\n- Plugins and dataset schemas install organization-wide. A site you create next month gets them too.\n- Components, templates, layouts, themes and email templates are site-scoped. "All sites" copies them onto every site you have right now; a site you add later will not have them. "All sites except…" works the same way: it copies them onto the sites you have now, minus the ones you leave out, and a site you add later will not have them.\nThe What\'s included box further up the page says the same thing for the choice you have picked, and changes when you pick another. With All sites it reads Installs on every site, including sites you add later, or, for a site-scoped listing, Installs on the sites you have now. A new site doesn\'t get it automatically. With Selected sites it reads Installs only on the sites you pick. A new site doesn\'t get it until you add it. The line under each Install to choice is the same fact with your own numbers in it: for the site-scoped case it reads "Installs to all 4 sites. New sites won\'t get it automatically."\n"Selected sites" and "All sites except…" only appear when there\'s a choice to make. A dataset schema installs for the whole organization, so it '
11017
11045
  },
11018
11046
  {
11019
11047
  path: '/guides/install-your-first-plugin',