@realiizlabs/admin 0.15.2 → 0.15.4

package/dist/studio-ui/index.d.cts

@@ -407,7 +407,7 @@ declare function UpdateBody({ update, onLater, compact }: {
 }): react.JSX.Element;
 
 /** The Help center's data shapes. Articles are plain data so the page and the assistant read the same text. */
-type HelpSectionId = "start" | "publishing" | "blog" | "pictures" | "markdown" | "events" | "account" | "trouble";
+type HelpSectionId = "start" | "publishing" | "blog" | "pictures" | "markdown" | "events" | "account" | "updates" | "trouble";
 interface HelpSection {
     id: HelpSectionId;
     title: string;

package/dist/studio-ui/index.d.ts

@@ -407,7 +407,7 @@ declare function UpdateBody({ update, onLater, compact }: {
 }): react.JSX.Element;
 
 /** The Help center's data shapes. Articles are plain data so the page and the assistant read the same text. */
-type HelpSectionId = "start" | "publishing" | "blog" | "pictures" | "markdown" | "events" | "account" | "trouble";
+type HelpSectionId = "start" | "publishing" | "blog" | "pictures" | "markdown" | "events" | "account" | "updates" | "trouble";
 interface HelpSection {
     id: HelpSectionId;
     title: string;

package/dist/studio-ui/index.js

@@ -710,7 +710,7 @@ function Tabs({ options, value, onChange, label = "Sections" }) {
 }
 
 // src/version.ts
-var ADMIN_VERSION = "0.15.2" ;
+var ADMIN_VERSION = "0.15.4" ;
 
 // src/studio-ui/css.ts
 var STUDIO_CSS = `
@@ -1004,7 +1004,13 @@ function UpdateBody({ update, onLater, compact = false }) {
     ];
     return /* @__PURE__ */ jsxs("div", { className: `rz-update${compact ? " rz-update--strip" : ""}`, role: "status", children: [
       /* @__PURE__ */ jsx(Steps, { steps }),
-      /* @__PURE__ */ jsx("span", { className: "rz-update__done", children: live ? `Studio ${update.version} is live. Reload and the version at the foot of the sidebar will change.` : "The version shown in Studio changes once the site has rebuilt." })
+      /* @__PURE__ */ jsx("span", { className: "rz-update__done", children: live ? /* @__PURE__ */ jsxs(Fragment, { children: [
+        "Studio ",
+        update.version,
+        " is live. ",
+        /* @__PURE__ */ jsx("button", { type: "button", className: "rz-update__link", onClick: () => window.location.reload(), children: "Reload Studio" }),
+        " to start using it \u2014 the version at the foot of the sidebar will change."
+      ] }) : "Nothing to do meanwhile \u2014 keep working. The website is rebuilding with the new Studio; the version at the foot of the sidebar changes when it's done, in about two minutes." })
     ] });
   }
   const problem = outcome && outcome.state !== "pending" ? outcome.state === "stale" ? "The site changed since the checks ran. Try again in a minute." : outcome.state === "red" ? `The checks failed${outcome.failingCheck ? ` (${outcome.failingCheck})` : ""}. Your web team has been able to see this.` : outcome.state === "error" ? outcome.message : null : null;
@@ -3976,7 +3982,11 @@ function StudioTab({ update, version, role }) {
         supportName,
         " releases a new version, your site prepares the update as a checked change \u2014 the same way a blog post is checked before it goes live \u2014 and builds a private preview. Nothing changes until you press ",
         /* @__PURE__ */ jsx("b", { children: "Update" }),
-        ". If the update would break anything, the button never unlocks."
+        ". If the update would break anything, the button never unlocks. Your site looks for new versions once a week, on Monday morning."
+      ] }),
+      /* @__PURE__ */ jsxs("p", { className: "acct-blurb", style: { marginTop: ".5rem" }, children: [
+        /* @__PURE__ */ jsx("a", { href: "/admin/help#s-updates", children: "Everything about updates, in the Help center" }),
+        " \u2014 when they arrive, what they can and can\u2019t change, and what to do if one fails."
       ] })
     ] })
   ] });
@@ -4016,6 +4026,7 @@ var HELP_SECTIONS = [
   { id: "markdown", title: "Writing in Markdown", blurb: "Headings, lists, links, tables \u2014 the formatting the editor understands." },
   { id: "events", title: "Events", blurb: "Dates, times, time zones, kinds, and what to do when plans change." },
   { id: "account", title: "Account & team", blurb: "Your profile, your password, who else can sign in, your branding." },
+  { id: "updates", title: "Studio updates", blurb: "How new versions reach you, what the Update button does, and what could go wrong (not much)." },
   { id: "trouble", title: "Troubleshooting", blurb: "When something doesn't look right \u2014 what it means and what to do." }
 ];
 
@@ -4984,37 +4995,161 @@ Pictures save the moment you choose them (**Choose a picture**, **Replace**, **R
 
 In Studio's own secure storage \u2014 not in your website's files, so they don't go through Save/Publish.
 `
-  },
+  }
+];
+
+// src/studio-ui/help/updates.ts
+var UPDATES = [
   {
     id: "updating-studio",
-    section: "account",
+    section: "updates",
     title: "Updating Studio",
     summary: "When a new version is out, owners see a strip with what's new, a preview and an Update button. Nothing installs until you press it.",
-    keywords: ["update", "upgrade", "new version", "release", "what's new", "studio version"],
+    keywords: ["update", "upgrade", "new version", "release", "what's new", "studio version", "update button"],
     body: `
 ## What it is
 
-Studio is a small package inside your website, and it improves over time. When {supportName} releases a new version, your website prepares the update automatically as a **checked change** \u2014 exactly like a blog post is checked before it goes live \u2014 and builds a private preview of your site with the new Studio in it.
+Studio is a small package inside your website, and it improves over time \u2014 new features, small fixes, a nicer screen here and there. When {supportName} releases a new version, your website prepares it as a **checked change**, exactly like a blog post is checked before it goes live, and builds a private preview of your site with the new Studio in it.
 
 ## Where you see it
 
-- A quiet strip at the top of every Studio page: **Studio 0.15 is available \xB7 What's new \xB7 Preview \xB7 Update \xB7 Later**. Only owners and {supportName} see it; editors don't.
+- A quiet strip at the top of every Studio page: **Studio 0.15.2 is available \xB7 What's new \xB7 Preview \xB7 Update \xB7 Later**. Only owners and {supportName} see it; editors don't.
 - **Settings \u2192 Studio**: the version you're running, the pending update with its notes, and the same Update button.
+- The version you're running is always printed in small type at the bottom of the sidebar, under **Collapse**.
 
-The strip appears only once the update's checks have passed. If they fail, nothing is offered \u2014 {supportName} sees the failure and fixes it.
+The strip appears only once the update's checks have passed. If they fail, nothing is offered \u2014 {supportName} sees the failure and fixes it before you ever hear about it.
 
 ## How to update
 
-1. Read **What's new** (a few lines, plain English).
+1. Read **What's new** \u2014 a few lines, plain English.
 2. Optional: press **Preview** to open your website running the new Studio.
 3. Press **Update**. The tracker shows *Updated \u2192 Live*; about two minutes later the website has rebuilt.
-4. Reload Studio to use the new version.
+4. Reload Studio. The number at the bottom of the sidebar changes \u2014 that's how you know it landed.
 
 ## Good to know
 
-- **Later** hides the strip for this browser tab; it comes back next time.
-- Nothing on your public website changes because of a Studio update \u2014 only the dashboard does.
+- **Later** hides the strip for this browser tab; it comes back next time you open Studio.
+- Nothing on your public website changes because of a Studio update \u2014 only the dashboard does. Your posts, pictures and events are untouched.
 - You can't skip a version or go back from here; if something looks wrong after an update, tell {supportName}.
+`
+  },
+  {
+    id: "when-updates-arrive",
+    section: "updates",
+    title: "When updates arrive",
+    summary: "Once a week, on Monday morning. You don't have to check anything \u2014 if there's a new version, the strip is waiting.",
+    keywords: ["monday", "schedule", "when", "how often", "weekly", "check for updates", "notification"],
+    body: `
+## The rhythm
+
+Your website looks for a new Studio version **once a week, early Monday morning**. If there's one, it prepares the update, runs the checks, and the strip is waiting the next time an owner opens Studio. If there isn't one, nothing happens and you see nothing.
+
+There's no button to press and nothing to install on your computer. You don't have to remember to look \u2014 if you don't see a strip, you're up to date.
+
+## Why weekly and not instantly
+
+{supportName} may release more than one version in a week. Batching them means you get **one** update to read about and press, not three. It also means every release has been running on other sites for a few days before it's offered to you.
+
+## What if I'm away that Monday?
+
+Nothing expires. The strip stays until an owner presses **Update** or a newer version replaces it \u2014 in which case the newer one is offered instead, and its notes cover everything since the version you're on.
+
+## Will I get an email?
+
+No. Updates are quiet by design; the strip and **Settings \u2192 Studio** are the only places they appear. If an update is important enough to act on quickly, {supportName} will tell you directly.
+`
+  },
+  {
+    id: "what-an-update-changes",
+    section: "updates",
+    title: "What an update does and doesn't change",
+    summary: "The dashboard, yes. Your website's content, design and visitors' experience, no.",
+    keywords: ["safe", "risk", "what changes", "content", "design", "visitors", "break", "downtime"],
+    body: `
+## What changes
+
+The Studio dashboard \u2014 the screens you use at **/admin**. A new version might add a field to a form, improve the editor, fix something that was confusing, or add a Help article. **What's new** tells you exactly what, in a sentence or two.
+
+## What doesn't change
+
+- **Your content.** Posts, pictures, events, pages: untouched. An update never edits, moves or deletes anything you've published or saved.
+- **Your website's design.** How {siteName} looks to visitors is separate from Studio. An update can't restyle your site.
+- **Your visitors' experience.** The website keeps running the whole time. There's no maintenance page and no downtime \u2014 the new version simply replaces the old one when the rebuild finishes, the same way a published post does.
+- **Your sign-ins and team.** Everyone keeps their access and role.
+
+## Why it's safe to press
+
+Every update has already been built and checked against **your** website \u2014 not a generic one \u2014 before the strip appears. The **Preview** link is that exact build. If the checks had failed, you'd never have been offered it.
+`
+  },
+  {
+    id: "update-questions",
+    section: "updates",
+    title: "Update questions, answered",
+    summary: "Do I have to? Who can? Can I undo it? What if I press it twice? The short answers.",
+    keywords: ["faq", "questions", "must i update", "who can update", "undo update", "roll back", "editors", "pressed twice"],
+    body: `
+## Do I have to update?
+
+No \u2014 but you should. Updates are how fixes and improvements reach you, and each one has been checked against your site. If you'd rather wait, press **Later**; it'll be there when you come back.
+
+## Who can press Update?
+
+Owners and {supportName}. Editors don't see the strip or the Settings \u2192 Studio tab at all, so a well-meaning teammate can't update the site by accident.
+
+## Can I see what's coming before I press it?
+
+Yes, two ways: **What's new** shows the notes, and **Preview** opens your real website \u2014 with the new Studio installed \u2014 at a private address. Click around; nothing you do there affects the live site.
+
+## Can I undo an update?
+
+Not from Studio. It's rarely needed, because an update can't touch your content, but if something looks wrong afterwards tell {supportName} \u2014 going back is a quick job for them.
+
+## I pressed Update and nothing seems different
+
+Two things to check. First, the tracker: **Updated** means the update was accepted; **Live** means the website has finished rebuilding, which takes about two minutes. Second, reload Studio \u2014 the number at the bottom of the sidebar should now match the version the strip offered. Until the rebuild finishes you're still running the old one, which is normal.
+
+## I pressed Update twice
+
+No harm done. The second press finds nothing to update and does nothing.
+
+## The strip disappeared before I pressed anything
+
+Either another owner pressed Update, or a newer version arrived and replaced the offer. Either way, **Settings \u2192 Studio** shows what you're running now.
+
+## What does the version number mean?
+
+Just a label \u2014 0.15.2 is newer than 0.15.1. The first two numbers change when a feature is added, the last one when something is fixed or polished. You don't need to track them; the strip does.
+`
+  },
+  {
+    id: "update-problems",
+    section: "updates",
+    title: "When an update isn't offered, or fails",
+    summary: "Settings \u2192 Studio says checking or failed; the Update button gave an error. What each means and who's handling it.",
+    keywords: ["checks failed", "checking", "failed", "error", "not available", "stuck", "no update", "problem"],
+    body: `
+## Settings \u2192 Studio says "Checking\u2026"
+
+A new version exists and your website is building a test copy with it. That takes a few minutes. The strip appears once the checks pass; you don't need to wait on the page.
+
+## Settings \u2192 Studio says "The checks failed"
+
+The new version didn't build cleanly against your website. Nothing was installed and nothing on your site changed. **This is not something you need to fix** \u2014 {supportName} is told automatically and will either correct the release or adjust your site, after which the update is offered again. If it's still showing after a couple of days, mention it to them.
+
+## I pressed Update and got a message
+
+- **"The site changed since the checks ran."** Someone published a post between the checks and your press. Wait a minute and press again \u2014 the checks re-run with the newest site.
+- **"The checks failed."** Same as above: a fresh check found a problem. {supportName} can see it.
+- **"That isn't a Studio update."** The offer you were looking at is no longer current \u2014 reload Studio for the latest one.
+
+## The tracker is stuck on "Live"
+
+The rebuild usually takes about two minutes; occasionally the hosting service is slow and it takes ten. If the tracker says *taking longer than usual*, that's all it means. Leave the page and come back \u2014 the update is already accepted and will finish on its own.
+
+## I'm not seeing updates at all
+
+Only owners see them, and only when one is ready. If you're an owner, it's been a few weeks, and {supportName} says a version has shipped, tell them \u2014 it's a one-minute check on their side.
 `
   }
 ];
@@ -5135,7 +5270,7 @@ Nothing you do in Studio can damage the live website \u2014 every edit is checke
 ];
 
 // src/studio-ui/help/index.ts
-var HELP_ARTICLES = [...QUICK_START, ...PUBLISHING, ...BLOG, ...PICTURES, ...MARKDOWN, ...EVENTS, ...ACCOUNT, ...TROUBLE];
+var HELP_ARTICLES = [...QUICK_START, ...PUBLISHING, ...BLOG, ...PICTURES, ...MARKDOWN, ...EVENTS, ...ACCOUNT, ...UPDATES, ...TROUBLE];
 var GENERIC_VARS = { siteName: "your website", supportName: "your web team", types: "blog posts and events" };
 function joinTypes(labels) {
   if (labels.length === 0) return GENERIC_VARS.types;