@aglyn/aglyn 1.20.3 → 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 +11 -11
- package/src/lib/app-utils/docs-index.generated.js +5 -5
- package/src/lib/app-utils/docs-index.generated.js.map +1 -1
- package/src/lib/app-utils/native-besigner-back.d.ts +60 -0
- package/src/lib/app-utils/native-besigner-back.js +97 -0
- package/src/lib/app-utils/native-besigner-back.js.map +1 -0
- package/src/lib/app-utils/variables.js +13 -6
- package/src/lib/app-utils/variables.js.map +1 -1
- package/src/lib/foundation/definitions/components.types.d.ts +11 -0
- package/src/lib/foundation/definitions/components.types.js.map +1 -1
- package/src/lib/types/nodes.d.ts +18 -2
- package/src/lib/types/nodes.js.map +1 -1
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@aglyn/aglyn",
|
|
3
|
-
"version": "1.
|
|
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.
|
|
41
|
-
"@aglyn/shared-data-mdi": "1.
|
|
42
|
-
"@aglyn/shared-data-types": "1.
|
|
43
|
-
"@aglyn/shared-util-email": "1.
|
|
44
|
-
"@aglyn/shared-util-first-touch": "1.
|
|
45
|
-
"@aglyn/shared-util-http": "1.
|
|
46
|
-
"@aglyn/shared-util-logger": "1.
|
|
47
|
-
"@aglyn/shared-util-timestamp": "1.
|
|
48
|
-
"@aglyn/shared-util-tools": "1.
|
|
49
|
-
"@aglyn/shared-util-vendor": "1.
|
|
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",
|
|
@@ -3061,7 +3061,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
3061
3061
|
title: 'Connect a domain automatically',
|
|
3062
3062
|
heading: '',
|
|
3063
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 and
|
|
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
3065
|
},
|
|
3066
3066
|
{
|
|
3067
3067
|
path: '/building-sites/custom-domains/connect-automatically',
|
|
@@ -3131,7 +3131,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
3131
3131
|
title: 'Manage your domains',
|
|
3132
3132
|
heading: 'DNS records',
|
|
3133
3133
|
anchor: '#dns',
|
|
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.
|
|
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.'
|
|
3135
3135
|
},
|
|
3136
3136
|
{
|
|
3137
3137
|
path: '/building-sites/custom-domains/manage-domains',
|
|
@@ -8584,7 +8584,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
8584
8584
|
title: 'Media Library & CDN',
|
|
8585
8585
|
heading: 'Who an asset is shared with',
|
|
8586
8586
|
anchor: '#who-an-asset-is-shared-with',
|
|
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,
|
|
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'
|
|
8588
8588
|
},
|
|
8589
8589
|
{
|
|
8590
8590
|
path: '/content-and-data/media/overview',
|
|
@@ -9144,7 +9144,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
9144
9144
|
title: 'Plugins & Marketplace',
|
|
9145
9145
|
heading: 'What\'s included',
|
|
9146
9146
|
anchor: '#whats-included',
|
|
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
|
|
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'
|
|
9148
9148
|
},
|
|
9149
9149
|
{
|
|
9150
9150
|
path: '/developers/plugins/overview',
|
|
@@ -11041,7 +11041,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
11041
11041
|
title: 'Install your first marketplace item',
|
|
11042
11042
|
heading: 'Step 4 — Choose which sites get it',
|
|
11043
11043
|
anchor: '#step-4-targeting',
|
|
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.\
|
|
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 '
|
|
11045
11045
|
},
|
|
11046
11046
|
{
|
|
11047
11047
|
path: '/guides/install-your-first-plugin',
|