@aglyn/aglyn 1.0.0-beta.296 → 1.0.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.0.0-beta.296",
3
+ "version": "1.0.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.0.0-beta.296",
41
- "@aglyn/shared-data-mdi": "1.0.0-beta.296",
42
- "@aglyn/shared-data-types": "1.0.0-beta.296",
43
- "@aglyn/shared-util-email": "1.0.0-beta.296",
44
- "@aglyn/shared-util-first-touch": "1.0.0-beta.296",
45
- "@aglyn/shared-util-http": "1.0.0-beta.296",
46
- "@aglyn/shared-util-logger": "1.0.0-beta.296",
47
- "@aglyn/shared-util-timestamp": "1.0.0-beta.296",
48
- "@aglyn/shared-util-tools": "1.0.0-beta.296",
49
- "@aglyn/shared-util-vendor": "1.0.0-beta.296",
40
+ "@aglyn/shared-data-enums": "1.0.0",
41
+ "@aglyn/shared-data-mdi": "1.0.0",
42
+ "@aglyn/shared-data-types": "1.0.0",
43
+ "@aglyn/shared-util-email": "1.0.0",
44
+ "@aglyn/shared-util-first-touch": "1.0.0",
45
+ "@aglyn/shared-util-http": "1.0.0",
46
+ "@aglyn/shared-util-logger": "1.0.0",
47
+ "@aglyn/shared-util-timestamp": "1.0.0",
48
+ "@aglyn/shared-util-tools": "1.0.0",
49
+ "@aglyn/shared-util-vendor": "1.0.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",
@@ -387,7 +387,7 @@ export const DOCS_SECTION_INDEX = [
387
387
  title: 'Build from Assist chat',
388
388
  heading: 'Change a page',
389
389
  anchor: '#change-a-page',
390
- text: 'Ask for a change to a page the site already has, such as make the image at the top of the home page fill the background, and Assist makes it on that page:\n1. The card says Making the change as a draft of Home… while it works.\n2. The change is saved into the page\'s draft, the same draft the Besigner keeps for you when you work on a page. Your published page stays as it is: visitors see no change until you publish.\n3. The card then says where the change is, with Open in the Besigner. Choose Open draft there to see the change, then publish it when you are happy with it. To leave it, choose Discard instead.\nThere is no plan to confirm, and nothing is added to the page that you did not ask for. If you already had a draft of the page, the change is made on it, so your own work is kept. Ask for another change to the same page and it is made on the same draft, so the draft holds every change you asked for. If a change could not be made, the card says why, with Try again.\nThis works on every plan. To keep the change apart as a new version instead, say so, such as make the hero image fill the background, as a new version. A new version needs version history, which comes with a Pro plan; without it, the change goes into the draft and the card says so.\nOne message changes one page. For changes to several pages, ask for the next one when the first is ready.'
390
+ text: 'Ask for a change to a page the site already has, such as make the image at the top of the home page fill the background, and Assist makes it on that page:\n1. The card says Making the change as a draft of Home… while it works.\n2. The change is saved into the page\'s draft, the same draft the Besigner keeps for you when you work on a page. Your published page stays as it is: visitors see no change until you publish.\n3. The card then says where the change is, with Open in the Besigner, which opens the page with the draft already on the canvas. Check the change, then publish it when you are happy with it. To leave it, choose File > Discard changes instead. If someone else is working on the page, the Besigner says so and opens the draft once they\'re done.\nThere is no plan to confirm, and nothing is added to the page that you did not ask for. If you already had a draft of the page, the change is made on it, so your own work is kept. Ask for another change to the same page and it is made on the same draft, so the draft holds every change you asked for. If a change could not be made, the card says why, with Try again.\nThis works on every plan. To keep the change apart as a new version instead, say so, such as make the hero image fill the background, as a new version. A new version needs version history, which comes with a Pro plan; without it, the change goes into the draft and the card says so.\nOne message changes one page. For changes to several pages, ask for the next one when the first is ready.'
391
391
  },
392
392
  {
393
393
  path: '/ai/assist-builds',
@@ -10355,7 +10355,7 @@ export const DOCS_SECTION_INDEX = [
10355
10355
  title: 'Aglyn Assist',
10356
10356
  heading: 'Edits in the Besigner',
10357
10357
  anchor: '#edits-in-the-besigner',
10358
- text: 'With a page, a reusable component or a layout open in the Besigner, you can ask the assistant for a change: "make this hero darker", "add a testimonial band below", "point this button at the pricing page". On every plan, from its included AI credits (and any Aglyn AI tier on top), it answers with a Proposed change card listing what would change: elements added, removed, moved or restyled, settings changed, interactions added, and a page\'s search title or description filled in. Anything it could not match to your canvas is listed under Left out.\n- Interactions on the selected element. Ask "when this is clicked, show the panel below" and the assistant proposes an interaction on the element: something a visitor does to it — a click, a hover, scrolling it into view — and the steps that follow, chosen from the presentational ones every plan runs (show, hide or toggle an element, add or remove a class, scroll to or play an element, open or close a drawer or menu, go to a page, show a message). It is added beside anything the element already does, never in place of it; edit or remove it under Interactions like any other. Ask "what does this do?" and it explains the interactions the element carries.\n- Nothing changes until you apply. Apply as draft puts the changes on the open canvas as unsaved edits, all in one step, so a single Undo takes the whole change back. Nothing is saved or published until you do that yourself. A proposed search title or description is filled into Page Properties, where Save SEO stores it.\n- The live version is never edited in place. When the version open is the one your live site shows, the card offers Make a new version instead — the same New version you would use yourself. Once the new version opens, the card offers Apply as draft there.\n- Select th'
10358
+ text: 'With a page, a reusable component or a layout open in the Besigner, you can ask the assistant for a change: "make this hero darker", "add a testimonial band below", "point this button at the pricing page". On every plan, from its included AI credits (and any Aglyn AI tier on top), it answers with a Proposed change card listing what would change: elements added, removed, moved or restyled, settings changed, interactions added, and a page\'s search title or description filled in. Anything it could not match to your canvas is listed under Left out.\n- Interactions on the selected element. Ask "when this is clicked, show the panel below" and the assistant proposes an interaction on the element: something a visitor does to it — a click, a hover, scrolling it into view — and the steps that follow, chosen from the presentational ones every plan runs (show, hide or toggle an element, add or remove a class, scroll to or play an element, open or close a drawer or menu, go to a page, show a message). It is added beside anything the element already does, never in place of it; edit or remove it under Interactions like any other. Ask "what does this do?" and it explains the interactions the element carries.\n- Nothing changes until you apply. Apply as draft puts the changes on the open canvas as unsaved edits, all in one step, so a single Undo takes the whole change back. Nothing is saved or published until you do that yourself. A proposed search title or description is filled into Page Properties, where Save SEO stores it.\n- The version your live site shows takes the change too. Apply as draft works there the same way, as unsaved edits on the canvas. Save draft keeps them in the page\'s draft, and visitors see nothing until you publish. To make the change on a copy instead, choose Make '
10359
10359
  },
10360
10360
  {
10361
10361
  path: '/getting-started/aglyn-assist',