@aglyn/aglyn 1.0.0-beta.192 → 1.0.0-beta.193

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aglyn/aglyn",
-  "version": "1.0.0-beta.192",
+  "version": "1.0.0-beta.193",
   "license": "Apache-2.0",
   "homepage": "https://aglyn.com",
   "repository": {
@@ -33,16 +33,16 @@
     "./package.json": "./package.json"
   },
   "dependencies": {
-    "@aglyn/shared-data-enums": "1.0.0-beta.192",
-    "@aglyn/shared-data-mdi": "1.0.0-beta.192",
-    "@aglyn/shared-data-types": "1.0.0-beta.192",
-    "@aglyn/shared-util-email": "1.0.0-beta.192",
-    "@aglyn/shared-util-first-touch": "1.0.0-beta.192",
-    "@aglyn/shared-util-http": "1.0.0-beta.192",
-    "@aglyn/shared-util-logger": "1.0.0-beta.192",
-    "@aglyn/shared-util-timestamp": "1.0.0-beta.192",
-    "@aglyn/shared-util-tools": "1.0.0-beta.192",
-    "@aglyn/shared-util-vendor": "1.0.0-beta.192",
+    "@aglyn/shared-data-enums": "1.0.0-beta.193",
+    "@aglyn/shared-data-mdi": "1.0.0-beta.193",
+    "@aglyn/shared-data-types": "1.0.0-beta.193",
+    "@aglyn/shared-util-email": "1.0.0-beta.193",
+    "@aglyn/shared-util-first-touch": "1.0.0-beta.193",
+    "@aglyn/shared-util-http": "1.0.0-beta.193",
+    "@aglyn/shared-util-logger": "1.0.0-beta.193",
+    "@aglyn/shared-util-timestamp": "1.0.0-beta.193",
+    "@aglyn/shared-util-tools": "1.0.0-beta.193",
+    "@aglyn/shared-util-vendor": "1.0.0-beta.193",
     "@data-driven-forms/react-form-renderer": "^4.2.0",
     "@msgpack/msgpack": "^3.1.3",
     "@types/unist": "^3.0.3",

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

@@ -1500,7 +1500,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Reusable components',
         heading: 'Manage',
         anchor: '#manage',
-        text: 'From the site\'s Components page you can rename, edit the description, open the besigner, or delete a reusable component. The component\'s ID is persisted inside every screen that places it and never changes.\nYou can also give a component its own icon, from the same picker the besigner uses for icon elements — either in the Edit component dialog on the Components page, or on the component\'s detail page. Every instance is then marked with it: in the hierarchy, on the canvas badge, and in the element drawer under Your components. A page assembled from promoted sections becomes readable at a glance. Components without an icon keep the generic package glyph.'
+        text: 'From the site\'s Components page you can rename, edit the description, open the besigner, or delete a reusable component. The component\'s ID is persisted inside every screen that places it and never changes.\nYou can also give a component its own icon, from the same picker the besigner uses for icon elements — either in the Edit component dialog on the Components page, or on the component\'s detail page. Every instance is then marked with it: in the hierarchy, on the canvas badge, and in the element drawer under Your components. A page assembled from promoted sections becomes readable at a glance. Components without an icon keep the generic package glyph.\nFilters in the Components table\'s toolbar narrows the list by name, Used in (page or email), ID, description, or date, and Search matches any word of the name, ID, or description. Each filter in force shows as a chip above the table. The list pages as you go, so a filter looks through the components read so far and reads further as you page on.'
     },
     {
         path: '/building-sites/besigner/reusable-components',
@@ -2258,6 +2258,13 @@ export const ASSIST_DOCS_INDEX = [
         anchor: '#what-a-layout-is',
         text: 'A layout holds the furniture many screens have in common — header, navigation, footer, a cookie banner, a site-wide search box. Bind a screen to a layout in the Besigner and the layout chrome wraps the screen both in the editor and on the published site.\nBecause the chrome lives in one document, changing it changes every screen bound to it at once. That is the point, and it is also the thing to keep in mind before you publish: see Versions & scheduled publishing.'
     },
+    {
+        path: '/building-sites/screens-and-layouts/layouts',
+        title: 'Layouts',
+        heading: 'Find a layout',
+        anchor: '#find-a-layout',
+        text: 'The site\'s Layouts page lists every layout. Filters in the table\'s toolbar narrows it by display name, ID, description, or the date it was created or last updated, and Search matches any word of the name, ID, or description. Each filter in force shows as a chip above the table; remove a chip to drop it. The list pages as you go, so a filter looks through the layouts read so far and reads further as you page on; the table says so while more remain.'
+    },
     {
         path: '/building-sites/screens-and-layouts/layouts',
         title: 'Layouts',
@@ -2767,7 +2774,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Build a blog',
         heading: '2. Write entries',
         anchor: '#2-write-entries',
-        text: 'Add rich blog entries with images, a live preview, and scheduling so posts publish at the right time.\nNew entry, or clicking any row in the entries table, opens that entry on its own page. The page has its own address, so you can bookmark an entry you\'re mid-way through or paste the link to a colleague and they land on the same one. Back to entries — or your browser\'s Back button — returns to the list; if the entry has edits you haven\'t saved, you\'re asked before they\'re dropped.\nThe table opens with the most recently Published entries first. Click the Title, Status, Updated or Published header to sort by that column, and again to reverse it. Entries with nothing in the sorted column, such as a draft with no published date, follow the rest in either direction rather than dropping out. Filters in the table\'s toolbar narrows the list to one Status or one Category across the whole collection, not only the page you\'re on.\nEach entry carries, besides the title, excerpt, cover image, and markdown body:\n- Category — a single bucket (e.g. Guides) used for filtering and related posts, picked from the collection\'s category list (see below), never typed free-form.\n- Tags — comma-separated labels (e.g. nextjs, seo).\n- Author — the entry\'s byline: an author record from the Authors tab or a one-off custom byline. An entry needs one to be published or scheduled; a draft can be saved without it. See Authors.\n- SEO title / SEO description — search & social overrides; they fall back to the title and excerpt when blank.\n- Featured video — a film for the entry\'s page: one from your media library, a video link, or a Wistia link. It plays where the cover image would sit. See Build a video collection.\nScheduling\nThe same three publication controls live in two places, so you can decide when a '
+        text: 'Add rich blog entries with images, a live preview, and scheduling so posts publish at the right time.\nNew entry, or clicking any row in the entries table, opens that entry on its own page. The page has its own address, so you can bookmark an entry you\'re mid-way through or paste the link to a colleague and they land on the same one. Back to entries — or your browser\'s Back button — returns to the list; if the entry has edits you haven\'t saved, you\'re asked before they\'re dropped.\nThe table opens with the most recently Published entries first. Click the Title, Status, Updated or Published header to sort by that column, and again to reverse it. Entries with nothing in the sorted column, such as a draft with no published date, follow the rest in either direction rather than dropping out. Filters in the table\'s toolbar narrows the list to one Status or one Category across the whole collection, not only the page you\'re on, and the filter in force shows as a chip above the table.\nEach entry carries, besides the title, excerpt, cover image, and markdown body:\n- Category — a single bucket (e.g. Guides) used for filtering and related posts, picked from the collection\'s category list (see below), never typed free-form.\n- Tags — comma-separated labels (e.g. nextjs, seo).\n- Author — the entry\'s byline: an author record from the Authors tab or a one-off custom byline. An entry needs one to be published or scheduled; a draft can be saved without it. See Authors.\n- SEO title / SEO description — search & social overrides; they fall back to the title and excerpt when blank.\n- Featured video — a film for the entry\'s page: one from your media library, a video link, or a Wistia link. It plays where the cover image would sit. See Build a video collection.\nScheduling\nThe same three publicati'
     },
     {
         path: '/building-sites/site-templates/build-a-blog',
@@ -2879,7 +2886,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Your templates library',
         heading: '',
         anchor: '',
-        text: 'Your templates library\nTemplates are saved starting points. A template is inert: nothing in your library is on your live site until you deliberately use it. That is the whole point of the library — it means installing something from the marketplace can never publish pages to a site you are running.\nFind it at Templates in a site\'s navigation, alongside Screens, Layouts and Components — the three things a template can produce.\nA template is a copy, not a live link: once you use one, the result is yours outright and editing the template never changes what you already made. If you want one edit to update every place a thing appears, you want a reusable component. If you want one frame around many pages, you want a layout.'
+        text: 'Your templates library\nTemplates are saved starting points. A template is inert: nothing in your library is on your live site until you deliberately use it. That is the whole point of the library — it means installing something from the marketplace can never publish pages to a site you are running.\nFind it at Templates in a site\'s navigation, alongside Screens, Layouts and Components — the three things a template can produce.\nA template is a copy, not a live link: once you use one, the result is yours outright and editing the template never changes what you already made. If you want one edit to update every place a thing appears, you want a reusable component. If you want one frame around many pages, you want a layout.\nFilters in the library\'s toolbar narrows it by Kind (page, component, or layout), Source (marketplace, starter, or saved here), name, description, or date, and Search matches any word of the name or description. Filters look at every template the library read, and each one in force shows as a chip above the table.'
     },
     {
         path: '/building-sites/site-templates/templates-library',
@@ -6918,7 +6925,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Member accounts',
         heading: '5. Manage members from the console',
         anchor: '#5-manage-members-from-the-console',
-        text: 'The site\'s Users page has two cards: Site users (your members — this guide) and Users (console collaborators). The Site users card is searchable and paged, newest first, with Email, Name, Joined, and Status columns. For members who may open the CRM, each row\'s ⋮ menu holds Open in CRM — the member\'s contact, found by the address they signed up with.\nClick a member to open the member drawer:\n- Profile — email, display name, and join date, with a Suspended chip when applicable.\n- Lifetime purchases — charged order totals minus refunds (pending and canceled orders excluded).\n- Orders — the member\'s payment history, newest first: order number, status, total, date, any refunded amount, and the Stripe payment reference. Needs the editor or admin role on the site.\n- Subscriptions — each with its renewal date and status chip.\n- Addresses — the member\'s saved addresses.\nSuspend & reactivate\nThe drawer\'s action button flips between Suspend member and Reactivate member, each behind a confirmation:\n- Suspend — the member can no longer sign in on the published site (they see an "account suspended" message), and their account page signs out on its next load. Orders, subscriptions, and history are all kept.\n- Reactivate — restores access with the member\'s existing password.\nBoth actions are recorded in the site\'s activity log.\nPassword help\nThe drawer\'s Password section gets a member back into their account. This is their sign-in for this site only — it has nothing to do with any Aglyn console account the same person might also have.\n- Send password reset email — emails the member a link to the site\'s /recover page. The link works once and expires after an hour, and their current password keeps working until they use it. This is the option to reach for. Capped at a few sends per hour '
+        text: 'The site\'s Users page has two cards: Site users (your members — this guide) and Users (console collaborators). The Site users card is searchable and paged, newest first, with Email, Name, Joined, and Status columns. Filters in the table\'s toolbar narrows it by email, name, or join date, one filter at a time, across every member rather than the page on screen; the filter in force shows as a chip above the table. Status is not a filter, because an active member carries no status to match. For members who may open the CRM, each row\'s ⋮ menu holds Open in CRM — the member\'s contact, found by the address they signed up with.\nClick a member to open the member drawer:\n- Profile — email, display name, and join date, with a Suspended chip when applicable.\n- Lifetime purchases — charged order totals minus refunds (pending and canceled orders excluded).\n- Orders — the member\'s payment history, newest first: order number, status, total, date, any refunded amount, and the Stripe payment reference. Needs the editor or admin role on the site.\n- Subscriptions — each with its renewal date and status chip.\n- Addresses — the member\'s saved addresses.\nSuspend & reactivate\nThe drawer\'s action button flips between Suspend member and Reactivate member, each behind a confirmation:\n- Suspend — the member can no longer sign in on the published site (they see an "account suspended" message), and their account page signs out on its next load. Orders, subscriptions, and history are all kept.\n- Reactivate — restores access with the member\'s existing password.\nBoth actions are recorded in the site\'s activity log.\nPassword help\nThe drawer\'s Password section gets a member back into their account. This is their sign-in for this site only — it has nothing to do with any Aglyn console account the same per'
     },
     {
         path: '/guides/member-accounts',
@@ -8346,7 +8353,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Invite teammates',
         heading: 'Activity log',
         anchor: '#activity-log',
-        text: 'The organization\'s Team page shows a Recent Activity feed — renames, workspace URL changes, ownership transfers, members added/removed or re-roled, and invites sent, revoked, or accepted — each with who did it and when.\nVisible to members whose role carries the Activity & audit log permission. Owners and admins have it by default; viewers do not, and neither does a custom role until you grant it. Revoking it does not merely hide the card — the feed is served by an API that checks the permission, so a member without it cannot read the log by any route.\nEntries name the thing that changed and link straight to it, so "Saved the screen — Home" takes you to that screen. Entries recorded before this shipped show a plain description instead of a link.\nAI actions in the log {#ai-actions}\nEverything the AI does in your workspace is recorded in the same feed, attributed to the member who asked for it — or to nobody, when nothing a person did caused it (a generation that paused because the included band ran out, or the add-on leaving at the end of a billing period). The feed shows an AI chip whenever the page holds one of these rows; press it to see only them.\n| Entry | What it records |\n| Started an AI generation | A generation was briefed: what it builds, how long the brief was, and the site. |\n| AI generated | One thing a generation produced — a screen, a layout, a component — linked like any other change. A site\'s own activity carries a copy. |\n| Canceled an AI generation | A generation was stopped before it finished. |\n| AI generation paused for input | A generation stopped and asked for a person, and why: the included band, the overage ceiling, the monthly message cap, or the job\'s own budget. |\n| Applied AI edits | Edits from a proposal landed on a screen version, with a co'
+        text: 'The organization\'s Team page shows a Recent Activity feed — renames, workspace URL changes, ownership transfers, members added/removed or re-roled, and invites sent, revoked, or accepted — each with who did it and when.\nVisible to members whose role carries the Activity & audit log permission. Owners and admins have it by default; viewers do not, and neither does a custom role until you grant it. Revoking it does not merely hide the card — the feed is served by an API that checks the permission, so a member without it cannot read the log by any route.\nEntries name the thing that changed and link straight to it, so "Saved the screen — Home" takes you to that screen. Entries recorded before this shipped show a plain description instead of a link.\nA site\'s own activity log, on its Setup page, filters through its table\'s toolbar: Filters narrows it to one Action (or several, with is any of) or to entries before or after a date, across the whole log rather than the page on screen. It has no search box, because nothing can search the whole log by word.\nAI actions in the log {#ai-actions}\nEverything the AI does in your workspace is recorded in the same feed, attributed to the member who asked for it — or to nobody, when nothing a person did caused it (a generation that paused because the included band ran out, or the add-on leaving at the end of a billing period). The feed shows an AI chip whenever the page holds one of these rows; press it to see only them.\n| Entry | What it records |\n| Started an AI generation | A generation was briefed: what it builds, how long the brief was, and the site. |\n| AI generated | One thing a generation produced — a screen, a layout, a component — linked like any other change. A site\'s own activity carries a copy. |\n| Canceled an AI generation | '
     },
     {
         path: '/workspace-and-billing/teams-and-roles/invite-teammates',
@@ -8423,7 +8430,7 @@ export const ASSIST_DOCS_INDEX = [
         title: 'Teams, Roles & Membership',
         heading: '',
         anchor: '',
-        text: 'Teams, Roles & Membership\nAglyn has two kinds of people: your team (who build and manage the site) and site members (visitors who sign up to your site). Both are permission-aware.\nPlan availability Paid. Seats are metered per tier; see Billing & plans.'
+        text: 'Teams, Roles & Membership\nAglyn has two kinds of people: your team (who build and manage the site) and site members (visitors who sign up to your site). Both are permission-aware.\nPlan availability Paid. Seats are metered per tier; see Billing & plans.\nThe Team page\'s roster filters through its table\'s toolbar: Filters narrows it by Role or by Access (team manager or site collaborator), and Search matches any word of a member\'s name, email, or title. Each filter in force shows as a chip above the table. The role pickers and Permissions in each row work as before.'
     },
     {
         path: '/workspace-and-billing/teams-and-roles/overview',