@aglyn/aglyn 1.0.0-beta.209 → 1.0.0-beta.211

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.
Files changed (6) hide show
  1. package/package.json +11 -11
  2. package/src/lib/app-utils/docs-index.generated.js +1 -1
  3. package/src/lib/app-utils/docs-index.generated.js.map +1 -1
  4. package/src/lib/app-utils/announce-site-wide-change.d.ts +0 -45
  5. package/src/lib/app-utils/announce-site-wide-change.js +0 -58
  6. package/src/lib/app-utils/announce-site-wide-change.js.map +0 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@aglyn/aglyn",
3
- "version": "1.0.0-beta.209",
3
+ "version": "1.0.0-beta.211",
4
4
  "license": "Apache-2.0",
5
5
  "homepage": "https://aglyn.com",
6
6
  "repository": {
@@ -33,16 +33,16 @@
33
33
  "./package.json": "./package.json"
34
34
  },
35
35
  "dependencies": {
36
- "@aglyn/shared-data-enums": "1.0.0-beta.209",
37
- "@aglyn/shared-data-mdi": "1.0.0-beta.209",
38
- "@aglyn/shared-data-types": "1.0.0-beta.209",
39
- "@aglyn/shared-util-email": "1.0.0-beta.209",
40
- "@aglyn/shared-util-first-touch": "1.0.0-beta.209",
41
- "@aglyn/shared-util-http": "1.0.0-beta.209",
42
- "@aglyn/shared-util-logger": "1.0.0-beta.209",
43
- "@aglyn/shared-util-timestamp": "1.0.0-beta.209",
44
- "@aglyn/shared-util-tools": "1.0.0-beta.209",
45
- "@aglyn/shared-util-vendor": "1.0.0-beta.209",
36
+ "@aglyn/shared-data-enums": "1.0.0-beta.211",
37
+ "@aglyn/shared-data-mdi": "1.0.0-beta.211",
38
+ "@aglyn/shared-data-types": "1.0.0-beta.211",
39
+ "@aglyn/shared-util-email": "1.0.0-beta.211",
40
+ "@aglyn/shared-util-first-touch": "1.0.0-beta.211",
41
+ "@aglyn/shared-util-http": "1.0.0-beta.211",
42
+ "@aglyn/shared-util-logger": "1.0.0-beta.211",
43
+ "@aglyn/shared-util-timestamp": "1.0.0-beta.211",
44
+ "@aglyn/shared-util-tools": "1.0.0-beta.211",
45
+ "@aglyn/shared-util-vendor": "1.0.0-beta.211",
46
46
  "@data-driven-forms/react-form-renderer": "^4.2.0",
47
47
  "@msgpack/msgpack": "^3.1.3",
48
48
  "@types/unist": "^3.0.3",
package/src/lib/app-utils/docs-index.generated.js CHANGED
@@ -6540,7 +6540,7 @@ export const ASSIST_DOCS_INDEX = [
6540
6540
  title: 'Publish your first screen',
6541
6541
  heading: 'How fast changes go live',
6542
6542
  anchor: '#how-fast-changes-go-live',
6543
- text: '- Publishing a screen refreshes its live page immediately — the very next visitor gets the new version, usually within seconds.\n- Publishing a layout or a reusable component refreshes every page that uses it the same way. When that fan-out is very large, the publish confirms that the remaining pages "update on their own within an hour" — and they do.\n- Site settings go live when you save them. Your theme, logo, favicon, app icon, social image, SEO and structured data, business details, languages, consent banner, announcement bar, popup and store settings have no publish step — saving one refreshes every page of the live site immediately, the same way a publish does. Installing, updating or resetting a marketplace theme does too.\n- Saving is not publishing. A save writes your working version; the live site serves the published one. The one subtle case: if you edit the version that is currently live and press Save, the live site catches up on its own within about a minute — and because pages regenerate behind the scenes, you may need to refresh twice to see it.\n- Your site\'s sitemap.xml, robots.txt, and RSS feeds refresh within about five minutes (a publish refreshes the sitemap immediately).'
6543
+ text: '- Publishing a screen refreshes its live page immediately — the very next visitor gets the new version, usually within seconds.\n- Publishing a layout or a reusable component refreshes every page that uses it the same way. When that fan-out is very large, the publish confirms that the remaining pages "update on their own within an hour" — and they do.\n- Site settings go live when you save them. Your theme, logo, favicon, app icon, social image, SEO and structured data, business details, languages, consent banner, announcement bar, popup and store settings have no publish step — saving one refreshes every page of the live site immediately, the same way a publish does. Installing, updating or resetting a marketplace theme does too, and so does saving a product, a review\'s moderation, a site variable or function, an overlay or an A/B test. If you close the tab straight after saving, the refresh still happens within a few minutes.\n- Collections refresh their own pages. Changing a collection\'s template screens, its address or its categories refreshes its listing and every published entry page — including the old addresses after a rename.\n- A deleted site stops serving at once. Its cached pages are dropped when you delete it, rather than lingering for up to an hour.\n- Saving is not publishing. A save writes your working version; the live site serves the published one. The one subtle case: if you edit the version that is currently live and press Save, the live site catches up on its own within about a minute — and because pages regenerate behind the scenes, you may need to refresh twice to see it.\n- Your site\'s sitemap.xml, robots.txt, and RSS feeds refresh within about five minutes (a publish refreshes the sitemap immediately).'
6544
6544
  },
6545
6545
  {
6546
6546
  path: '/getting-started/publish-your-first-screen',