@aglyn/aglyn 1.0.0-beta.217 → 1.0.0-beta.218
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 +14 -14
- package/src/lib/app-utils/admin-audit-index.js +2 -2
- package/src/lib/app-utils/admin-audit-index.js.map +1 -1
- package/src/lib/app-utils/analytics-events.d.ts +10 -1
- package/src/lib/app-utils/analytics-events.js +11 -2
- package/src/lib/app-utils/analytics-events.js.map +1 -1
- package/src/lib/app-utils/binding-tokens.js +1 -1
- package/src/lib/app-utils/binding-tokens.js.map +1 -1
- package/src/lib/app-utils/docs-index.generated.js +4 -4
- package/src/lib/app-utils/docs-index.generated.js.map +1 -1
- package/src/lib/app-utils/lockdown.d.ts +33 -1
- package/src/lib/app-utils/lockdown.js +45 -4
- package/src/lib/app-utils/lockdown.js.map +1 -1
- package/src/lib/app-utils/marketplace-theme.js +3 -0
- package/src/lib/app-utils/marketplace-theme.js.map +1 -1
- package/src/lib/app-utils/screen-route.d.ts +15 -0
- package/src/lib/app-utils/screen-route.js +20 -0
- package/src/lib/app-utils/screen-route.js.map +1 -1
- package/src/lib/app-utils/starter-templates.d.ts +20 -0
- package/src/lib/app-utils/starter-templates.js +49 -0
- package/src/lib/app-utils/starter-templates.js.map +1 -1
- package/src/lib/canvas-manager/canvas-manager.js +3 -3
- package/src/lib/canvas-manager/canvas-manager.js.map +1 -1
- package/src/lib/foundation/definitions/org-billing.types.d.ts +9 -0
- package/src/lib/foundation/definitions/org-billing.types.js.map +1 -1
- package/src/lib/foundation/definitions/organization.types.d.ts +5 -0
- package/src/lib/foundation/definitions/organization.types.js.map +1 -1
- package/src/lib/foundation/definitions/platform.types.d.ts +16 -0
- package/src/lib/foundation/definitions/platform.types.js.map +1 -1
- package/src/lib/plugin-manager/first-party-plugins.generated.js +1 -4
- package/src/lib/plugin-manager/first-party-plugins.generated.js.map +1 -1
|
@@ -968,7 +968,7 @@ export const ASSIST_DOCS_INDEX = [
|
|
|
968
968
|
title: 'Element catalog',
|
|
969
969
|
heading: 'Forms, Input, Commerce, Members',
|
|
970
970
|
anchor: '#forms-input-commerce-members',
|
|
971
|
-
text: 'Forms and fields, buttons and widgets, product grids and cart companions, and the member sign-in/sign-up elements. These are covered with the features they belong to — see Forms, Commerce and Member accounts.\
|
|
971
|
+
text: 'Forms and fields, buttons and widgets, product grids and cart companions, and the member sign-in/sign-up elements. These are covered with the features they belong to — see Forms, Commerce and Member accounts.\nThe calculator elements belong to none of these. They come from Calculators, a plugin you install from the marketplace, and appear under Input once it is installed:\n| Element | What it\'s for |\n| Function Widget | Runs one of your no-code functions on the live site and shows what it returns — a quote calculator, a shipping estimate, a score. Function name is the function from the site\'s Functions card; the widget draws an input per parameter — a number box, a switch or a list, under the label and starting value the function sets — a run button you can relabel, and the result under a Result label prefix. Results to show lists several named results instead of one, one per line as name | Label, and Update as the visitor types recomputes on every change, so there is no button. The function runs in the visitor\'s browser: its definition, and the site variables it names, are part of the page, so keep anything private out of both. |\n| Calculator | A container bound to one of your functions. Everything inside it reads that function: place Calculator Inputs and Calculator Results anywhere in it, between whatever stacks, grids and text the design calls for. Function name is the function from the site\'s Functions card. The results are always current; there is no run button. |\n| Calculator Input | Asks one parameter of the Calculator it sits in. Ask as picks the control: Automatic follows the parameter (a list when it has choices, a number box for a number, a switch for a true/false), and Quick picks draws buttons that set the value, so 10, 25, 50, 100 can sit beside a number bo'
|
|
972
972
|
},
|
|
973
973
|
{
|
|
974
974
|
path: '/building-sites/besigner/element-catalog',
|
|
@@ -2830,7 +2830,7 @@ export const ASSIST_DOCS_INDEX = [
|
|
|
2830
2830
|
title: 'Templates, Blocks & Content',
|
|
2831
2831
|
heading: 'Site templates & starter gallery',
|
|
2832
2832
|
anchor: '#site-templates--starter-gallery',
|
|
2833
|
-
text: '- Spin up a new site from the starter template gallery, which instantiates published screens for you. Starters are copied into your site\'s own template library, so you can edit and version them like any other template.\n- Save a site as a template from Setup → Site template, which publishes it to the marketplace — see save & share a template. Browsing and installing marketplace templates happens in the Start from a template picker, opened by the Templates button on the Screens, Layouts and Components lists.'
|
|
2833
|
+
text: '- Spin up a new site from the starter template gallery, which instantiates published screens for you. Starters are copied into your site\'s own template library, so you can edit and version them like any other template. A starter\'s first page becomes the site\'s home page: it replaces the placeholder Home screen a new site is created with (which is kept as a draft), but never a home page you published yourself.\n- Save a site as a template from Setup → Site template, which publishes it to the marketplace — see save & share a template. Browsing and installing marketplace templates happens in the Start from a template picker, opened by the Templates button on the Screens, Layouts and Components lists.'
|
|
2834
2834
|
},
|
|
2835
2835
|
{
|
|
2836
2836
|
path: '/building-sites/site-templates/overview',
|
|
@@ -2991,7 +2991,7 @@ export const ASSIST_DOCS_INDEX = [
|
|
|
2991
2991
|
title: 'Edit your theme',
|
|
2992
2992
|
heading: 'Choose a theme',
|
|
2993
2993
|
anchor: '#choose-a-theme',
|
|
2994
|
-
text: 'The Theme card at the top of the page picks the theme your site runs:\n- Built-in — Material UI (default), Bootstrap, Minimal
|
|
2994
|
+
text: 'The Theme card at the top of the page picks the theme your site runs:\n- Built-in — Material UI (default) and seven themes modeled on the design systems people know best, plus any your plugins add:\n- Bootstrap — Bootstrap 5\'s blue, system fonts, flat bordered cards and focus rings.\n- Minimal — neutral and quiet, in the style of shadcn/ui.\n- Material 3 — Material Design 3\'s tonal surfaces and pill buttons.\n- Ant Design — Ant Design 5\'s compact 14px type and 32px controls.\n- Fluent — Microsoft Fluent 2: Segoe UI, underlined inputs, soft depth.\n- Carbon — IBM Carbon: Plex Sans, light display type, square corners.\n- Cupertino — in the style of iOS: capsule buttons, segmented tabs, green switches.\nEach one restyles components (buttons, inputs, cards, tabs, switches, alerts, menus) as well as colors and every text style, in light and dark.\n- Your themes — themes you saved from this site.\n- From the marketplace — themes you installed.\nChoosing a theme shows a preview first, in light and dark; Use this theme applies it to the live site.\nYour edits never change the theme itself. Everything you set in the editor below is stored as your edits on top of the theme you picked, so:\n- Restore drops your edits and brings the theme back exactly as it was.\n- Save as custom theme saves the result — the theme plus your edits — as a new theme of your own under Your themes and switches to it. The theme you started from stays in the list, unchanged.\n- Update (on one of your own themes) folds your edits into that theme.\n- Switching themes keeps your edits. Each theme remembers the edits you made to it, and they come back when you pick it again. Themes marked Edited in the list have some.\nYour Dark scheme setting belongs to the site, not the theme, so it stays as you set it whichever theme you pi'
|
|
2995
2995
|
},
|
|
2996
2996
|
{
|
|
2997
2997
|
path: '/building-sites/theme-builder/edit-your-theme',
|
|
@@ -6512,7 +6512,7 @@ export const ASSIST_DOCS_INDEX = [
|
|
|
6512
6512
|
title: 'Create a site',
|
|
6513
6513
|
heading: 'Create your first site',
|
|
6514
6514
|
anchor: '#create-your-first-site',
|
|
6515
|
-
text: '1. Sign in to the console.\n2. Open the site switcher in the app bar (top-left) and choose Create site.\n3. Give it a name. Aglyn generates a working subdomain immediately, so the site has a real address from the first moment — you can attach a custom domain later.
|
|
6515
|
+
text: '1. Sign in to the console.\n2. Open the site switcher in the app bar (top-left) and choose Create site.\n3. Give it a name. Aglyn generates a working subdomain immediately, so the site has a real address from the first moment — you can attach a custom domain later. Every new site starts with a published Home screen at the site root — your site\'s name over a short welcome line — so the address shows a real page from the first visit. Open it from Screens to make it your own. Or replace it: the first page you publish at the site root — one you build, one the AI drafts for you, or a starter template\'s home page — takes over /, and the placeholder Home screen is kept as an unpublished draft.\n4. You land on the new site\'s Setup page (titled Host Setup), with tabs for Basic details, SEO, Tracking, Theme, and Emails; the custom domain and the activity log are under Admin. To start building rather than configuring, use the Screens tab in the site navigation — see Publish your first screen.\nName collisions Site names must be unique enough to generate a valid subdomain. If a name is taken, the console suggests an available variation.'
|
|
6516
6516
|
},
|
|
6517
6517
|
{
|
|
6518
6518
|
path: '/getting-started/create-a-site',
|