@gentbajko/slopify 3.25.9 → 4.1.0

package/dist/tutorials/Templates.md

@@ -1,99 +1,75 @@
 # Templates
 
-A template is a saved Play setup: prompts, voice, images, style, outputs, reviews and checkpoints, under a name. Pick it on Play, type a topic, and the video is set up the way you like it. Schedules run templates too, so a template is also the recipe every scheduled video follows.
+A template is a saved setup: prompts, voice, images, style, extras, pauses and checks, under a name. Start from it on Create, type a topic, and the video is set up the way you like it. Schedules run templates too, so a template is also the recipe every scheduled video follows.
 
-**Where to find it:** **Library → Templates**. You also pick templates at the top of **Play**, save them from Play's right rail or a project's **More** menu, and move them between channels on a channel's **Templates** tab.
+Set a template up section by section, with a live sample beside every setting, in **Edit template** (see [Edit template](Template-Studio)).
+
+**Where to find it:** **Templates** in the rail. You also pick templates under **Start from** on Create, save them with Create's **Save as template** or a project's **More** menu, and move them between channels on a channel's **Templates** tab.
+
+## The Templates page
+
+Two tabs: **Video templates** (with how many you have) and **Poster templates** (posters, flyers and social sizes). The header holds **Add starter templates**, while a starter is left to add, and **Import a template file (.zip)**. With seven or more templates, **Search templates** and a sort menu sit above the cards; with two or more channels, **Show templates of** narrows them to one channel.
+
+Each video template is a card: a still from its sample once it has one, its name in full, one line of what it makes (for example "Landscape 16:9 · Voice: History narrator (storyteller), OpenAI · about 2,200 words · captions on the video · 2 shorts"), what it **Asks for**, its channel and, once schedules run it, how they run it (for example **Used by 1 schedule**). Pressing its name or its still opens Edit template. Its actions:
+
+| Action | What it does |
+|---|---|
+| **Make a video** | Opens Create with a fresh draft made from the template. Nothing starts until you press **Make the video**. |
+| **Edit template** | Opens the template's editor, section by section, with a sample beside the settings. See [Edit template](Template-Studio). |
+| **More** → **Duplicate** | Makes a copy in the same channel, named "<name> copy", then "<name> copy 2" and so on. |
+| **More** → **Versions** | Every saved version (see [Versions](#versions)). |
+| **More** → **Export as a file (.zip)** | Saves the template as a `<name>.slopify-template.zip` file you can import on another computer with **Import a template file (.zip)**. |
+| **More** → **Delete…** | Asks first, then moves the template to the trash (see [Delete a template](#delete-a-template)). |
+
+With no templates yet, the page says what a template is for and offers **Add starter templates**.
 
 ## What a template keeps
 
 | Kept | Left out |
 |---|---|
-| Every Play setting and every checkpoint choice | The topic you typed: keywords the project title names, such as `{{Topic}}`, are saved empty |
-| A copy of each prompt the setup uses (article, image, thumbnail, description, shorts and so on) | Extra videos you queued with **Add topic** |
+| Every setting of Create and every pause and check | The topic you typed: keywords the project title names, such as `{{Topic}}`, are saved empty |
+| A copy of each prompt the setup uses (article, image, thumbnail, description, shorts and so on) | Extra videos you added with **Another topic** |
 | A copy of each picked intro and outro | Uploaded fonts |
 | Values of the other keywords, such as a word count | Uploaded files keep their names but must be attached again when you use the template |
 | The channel it belongs to | |
 
-Because the template keeps copies of its prompts, editing a prompt in the Library later does not change a template you already saved. Save the template again to pick up the new prompt.
+Because the template keeps copies of its prompts, editing a prompt on Prompts later does not change a template you already saved. Save the template again to pick up the new prompt.
 
-## Save a template from Play
+## Save a template from Create
 
-1. Set up a video on [Play](Play-Overview) the way you want every video of this kind to look.
-2. In the right rail, press **Save as template**.
+1. Set up a video on [Create](Create-Overview) the way you want every video of this kind to look.
+2. Press **Save as template** in the page header.
 3. Type a **Template name** (up to 120 characters). The placeholder suggests the title without its keywords.
-4. Read the list under the name. It says what is left out, such as the topic you typed and any extra videos. If the title names no keyword, it says every keyword keeps its value.
-5. Press **Save template**. The template appears on Play's **Template** picker and in **Library → Templates**.
+4. Read the line under the name. It says what is left out, such as the topic you typed.
+5. Press **Save template**. The template appears under Create's **Start from** and on **Templates**.
 
 ## Save a template from a finished project
 
-You can turn any project's current setup into a template, which is handy after you have tuned a project with **Edit project**.
+You can turn any project's current setup into a template, which is handy after you have tuned a project with **Edit settings**.
 
 1. Open the project.
-2. Open the **More** menu (or press `Ctrl+K` and search for **Save as template**).
+2. Press **Save as template…** under the project's status (or press `Ctrl+K` and search for **Save as template**).
 3. Type a **Template name** (up to 120 characters) and press **Save template**.
 
-The template takes the setup of the revision you are looking at.
-
-## Save a template from Library → Templates
-
-1. Open **Library → Templates** and press **Save a setup**.
-2. Under **Saved Play draft**, choose a draft. Only drafts saved in Play are listed; open Play and set one up first if the list is empty. The draft itself is not changed.
-3. Type a **Template name** (up to 120 characters).
-4. Pick the **Channel**. The default, **The draft's channel**, is the draft's own channel, or its template's channel when it has none.
-5. Press **Save template**.
+The template takes the settings of the version you are looking at.
 
 ## Use a template
 
-**From Play:**
+**From Create:**
 
-1. Open **Play**.
-2. Pick the template in the **Template** field at the top. Play opens a fresh draft made from it and carries over the topic you already typed.
-3. Type the topic, check the rows, and press **Start run**.
+1. Open **Create**.
+2. Pick the template under **Start from**. Create opens a fresh draft made from it and carries over the topic you already typed.
+3. Type the topic, check the rows, and press **Make the video**.
 
-**From Library → Templates:**
-
-1. Find the template in the list.
-2. Press **Use in Play**. Slopify makes a new Play draft from the template and opens it. Nothing starts until you press **Start run**.
+**From Templates or Home:** press **Make a video** on the template. Create opens with a fresh draft made from it.
 
 Keywords the project title names start empty so you can type this video's topic. Uploaded files keep their names but must be attached again.
 
-## The row actions
-
-Every template row has the same actions as the other Library lists, always in this order:
-
-| Action | What it does |
-|---|---|
-| **Edit** | Picks the template and shows its keywords beside the list (below). To change its settings, press **Use in Play**, change the draft, then **Save a setup**. |
-| **Duplicate** | Makes `<name> copy` in the same channel ("Duplicated as …"). |
-| **Use in Play** | Makes a fresh Play draft from the template and opens it. |
-| **History** (clock icon) | Every saved version, compared with the current one, with **Restore** (see [History](#history)). |
-| **Delete** (bin icon) | Asks first, then moves the template to the trash (see [Delete a template](#delete-a-template)). |
-
-A press anywhere on a row picks it. The pencil beside a template's name renames it in the row (see [Rename a template](#rename-a-template)).
-
-## See a template's keywords
-
-Pick a template (or press **Edit**) and its keywords show beside the list: each keyword, whether it is a topic keyword (saved empty) or a setting-like keyword that keeps its value, and which prompts or fields it feeds. This is the same list Play and Edit project show. With nothing picked it says "Pick a template to see the keywords it fills."; a template with none says "No keywords: the prompts and the title name none."
-
-## Rename a template
-
-1. Press the pencil (**Rename <name>**) beside the template's name.
-2. Type the new name (up to 120 characters) and press **Save name** or Enter. `Esc` or **Cancel** keeps the old name.
-
-The notice says "Renamed “A” to “B”." with **Undo**. A rename saves a new version of the template; its settings stay as they are.
-
-## History
-
-Press the clock icon (**History of <name>**) on a template's row. The drawer has:
-
-- **Versions**: every version, newest first, as **Version N** with its name and date. The newest is marked **Current**; the others have **Restore**.
-- **Compare with the current version**: the version you picked, side by side with the current one. A rename between them is said above ("Renamed from … to …").
-
-**Restore** saves the old version again as a new version ("Restored version 2 of … as version 5."), so nothing after it is lost. Schedules keep the version they were set up with; see [Versions](#versions).
+## Versions
 
-## Filter by channel
+Every save of a template is a new version. **More** → **Versions** lists them, newest first, as **Version N** with its name and date, the newest marked current, the others with **Restore**, and **Compare with the current version** beside the list. **Restore** saves the old version again as a new version ("Restored version 2 of … as version 5."), so nothing after it is lost.
 
-Use **Show templates of** above the list to see only one channel's templates, or **All channels**. This only changes what you see. A template's channel is the one a draft made from it runs in; see [Channels](Channels).
+Schedules run the template's newest version until you approve one for schedules in Edit template (**More** → **Approve for schedules**); from then on they run the approved one. See [Edit template](Template-Studio#approve-for-schedules) and [Schedules](Schedules).
 
 ## Move a template to another channel
 
@@ -103,43 +79,41 @@ Use **Show templates of** above the list to see only one channel's templates, or
 
 The template and every schedule that runs it move together. Their next runs use the new channel's brand kit, cast and series brief. Projects already made keep what they were made with. Moving a template does not make a new version of it.
 
-## Versions
-
-Each template shows **Version N · updated** with the date. Schedules remember the version they were set up with; to make a schedule use a newer version, pick the template again in the schedule's **Template** field. See [Schedules](Schedules).
-
 ## Delete a template
 
-1. Press the bin icon (**Delete <name>**) on the template's row.
+1. Open the template's **More** and choose **Delete…**.
 2. Confirm with **Delete template**.
 
-The template goes to **Settings → Backup & storage → Trash** for 30 days, where you can restore it. A template that a schedule still runs can't be deleted: delete or change that schedule first. See [Trash](Trash).
+The template goes to **Settings → Trash** for 30 days, where you can restore it. Projects already made from it keep their setup. A template that a schedule still runs can't be deleted: delete or change that schedule first. See [Trash](Trash).
 
 ## Retired models
 
-When a template picks a model that has been retired, its row says so, for example "Images … is retired.", with **Switch to <model>**. One press switches the template to the replacement, as in Settings → **Models**, and the schedules that run it follow. When there is no replacement, the row says to choose another model in Settings → **Models** or edit the template. See [Models](Models#switch-away-from-a-retired-model).
+When a template picks a model that has been retired, it says so, for example "Images … is retired.", with **Switch to <model>**. One press switches the template to the replacement, as in Settings → **Models**, and the schedules that run it follow. When there is no replacement, it says to choose another model in Settings → **Models** or edit the template. See [Models](Models#switch-away-from-a-retired-model).
 
-## Starter packs
+## Starter templates
 
-**Library → Templates → Add pack** opens **Add a starter pack**. Press **Add pack** on a pack's row; it then reads **Added**. Each pack adds prompts, a suggested voice and a ready-made Play template for one kind of channel:
+**Templates → Add starter templates** offers a ready-made set for one kind of channel. Each adds prompts, a suggested voice and a ready-made template, named `<kind> starter`:
 
-| Pack | What it is for |
+| Starter | What it is for |
 |---|---|
 | **Sleep lore** | Slow, gentle myths and legends told to fall asleep to |
 | **True crime** | Measured, factual retellings of real cases and their investigations |
 | **History** | Narrative history of people, places and events, told like a documentary |
 | **Science explainers** | Clear, friendly explanations of how the world works, one idea at a time |
 
-Adding a pack twice changes nothing, and a pack never replaces a prompt or template of yours with the same name. The first-run screen offers the same packs (**Add to library**); see [First launch and welcome](First-Launch-and-Welcome#starter-packs).
+Adding one twice changes nothing, and it never replaces a prompt or template of yours with the same name. The first-run screen offers the same starters; see [First launch and welcome](First-Launch-and-Welcome#starter-templates).
 
 ## Tips
 
 - Make one template per kind of video (a long documentary, a 60-second short, a podcast) rather than one template you change each time.
-- Put the topic keyword in the title, like `History: {{Topic}}`. Then the template saves it empty, Play asks for it, and a schedule can fill it from its topic list.
+- Put the topic keyword in the title, like `History: {{Topic}}`. Then the template saves it empty, Create asks for it, and a schedule can fill it from its topic list.
 - Keep settings you vary per video, such as a word count, as their own keywords. A schedule can set them per topic in its table.
 
 ## Related pages
 
-- [Play overview](Play-Overview)
+- [Edit template](Template-Studio)
+- [Create Overview](Create-Overview)
+- [Prompts and Templates](Prompts-and-Templates)
 - [Schedules](Schedules)
 - [Channels](Channels)
 - [Prompts](Prompts)

package/dist/tutorials/Trash.md

@@ -9,8 +9,8 @@ Deleting something in Slopify does not remove it at once. Deleted projects, prom
 | Kind | Shown as | Deleted from |
 | --- | --- | --- |
 | Project | Project | Projects (the delete button on a project's row, then **Delete project**) |
-| Library prompt | Prompt · *type* (for example Prompt · article) | Library → Prompts |
-| Intro or outro | Intro or Outro | Library → Intros & outros |
+| Prompt | Prompt · *type* (for example Prompt · article) | Prompts |
+| Intro or outro | Intro or Outro | Prompts → Intros and Outros |
 | Template | Template | Templates |
 | Schedule | Schedule | Schedules |
 
@@ -29,7 +29,7 @@ It comes back as it was. A few kinds have their own rules:
 | Item | What happens on restore |
 | --- | --- |
 | Prompt, intro/outro or template whose name was taken meanwhile | It comes back as "Name (restored)", then "Name (restored 2)" and so on. The message says which name it got. A renamed template gets a new version. |
-| Project that was waiting its turn (a queued batch item, or held at a checkpoint) | It was held while in the trash and picks up where it was. |
+| Project that was waiting its turn (queued behind other videos, or held at a pause) | It was held while in the trash and picks up where it was. |
 | Schedule | It comes back **paused**, with no next run. Press **Resume** on Schedules to run it again. |
 | Schedule whose template is also in the trash | Restore the template first (it is listed in the trash too), then the schedule. |
 | Schedule whose template was removed for good | It cannot be restored: it has nothing to run. **Delete now** removes it from the trash. |
@@ -58,7 +58,7 @@ A project's disk space is freed only when it leaves the trash. Settings → **Ba
 
 | Situation | What to do |
 | --- | --- |
-| A project that is still running | Open the project and use **More project actions → Cancel the run…** first. On Projects the delete button says "Cancel the run first, then delete it." |
+| A project that is still running | Open the project and press **Cancel the run…** under its status first. On Projects the delete button says "Cancel the run first, then delete it." |
 | A template that a schedule (not in the trash) uses | Delete that schedule first. |
 
 ## Messages you may see

package/dist/tutorials/Troubleshooting.md

@@ -2,31 +2,31 @@
 
 Most problems in Slopify show up as a failed step on the project page with a message that says what failed and where to fix it. This page collects the common ones, grouped by where you meet them, with the fix for each.
 
-**Where to find it:** failed steps show on the project page (the right rail and the step's section, under **Error details**). Startup problems show in the terminal that started Slopify. **Download diagnostics** is on every Settings section.
+**Where to find it:** failed steps show on the project page (the title row's next action and the step's part, under **Error details**). Startup problems show in the terminal that started Slopify. **Download diagnostics** is at the foot of Settings → **About** and in the **Help** menu.
 
 ## First steps for any problem
 
 1. Read the message. Slopify's messages name the screen or the command that fixes them.
 2. On a project, press the next action button. For a failed step it is the fix, or **Try ... again**, which keeps everything already made. See [Recovery and Retries](Recovery-and-Retries).
 3. Reload the page. A lot of "couldn't load" messages clear with a reload.
-4. If it keeps happening, open Settings and press **Download diagnostics**, then attach the file to a bug report.
+4. If it keeps happening, press **Download diagnostics** (Settings → **About**, or the **Help** menu), then attach the file to a bug report.
 
 ### Download diagnostics
 
-**Download diagnostics** saves `slopify-diagnostics.json`: the Slopify version, your system and Node version, which providers are set up or found, the project count and the state of the model catalogue. It never holds your keys, prompts or project content.
+**Download diagnostics** saves `slopify-diagnostics.json`: the Slopify version, your system and Node version, which services are set up or found, the project count and the state of the model list. It never holds your keys, prompts or project content.
 
-## Provider keys and accounts
+## Service keys and accounts
 
 | Message (or part of it) | Cause | Fix |
 | --- | --- | --- |
-| "*Provider* did not accept the API key ... The key may be wrong, expired or revoked" | The key is wrong or was revoked. | Paste a current key in Settings → **Providers**, save, then press **Try ... again** on the project. The fix-it button **Open Settings → Providers → *provider*** takes you there. |
-| "No *provider* API key is saved. Add one in Settings → Providers, then use Try again." | The project uses a provider with no key. | Add the key, or switch the project to another provider in **Edit project → Providers**. |
-| "*Provider* says the account is out of credits" | Your provider account has no balance. | Add credits on the provider's website, then try again. |
+| "*Service* did not accept the API key ... The key may be wrong, expired or revoked" | The key is wrong or was revoked. | Paste a current key in Settings → **Keys & services**, save, then press **Try ... again** on the project. The fix-it button **Open Settings → Keys & services → *service*** takes you there. |
+| "No *service* API key is saved. Add one in Settings → Keys & services, then use Try again." | The project uses a service with no key. | Add the key, or switch the project to another service in **Edit settings** (under **Written by** in Article, in Narration or in Images). |
+| "*Service* says the account is out of credits" | Your account with that service has no balance. | Add credits on the service's website, then try again. |
 | "Google gives this API key no image quota for this model" | The Google project behind the key has no quota for that image model. | Enable billing or quota in Google's console, or pick another image model. |
-| "Slopify could not load this provider's model list. Check the API key in Settings → Providers and your internet connection, then refresh the list." | The model list could not be fetched. | Check the key and your connection, then refresh. |
-| "Save this provider's API key in Settings → Providers to load its models." | No key yet. | Save the key first. |
+| "Slopify could not load this provider's model list. Check the API key in Settings → Keys & services and your internet connection, then refresh the list." | The model list could not be fetched. | Check the key and your connection, then refresh. |
+| "Save this provider's API key in Settings → Keys & services to load its models." | No key yet. | Save the key first. |
 
-Keys and how to get them: [Providers and Keys](Providers-and-Keys).
+Keys and how to get them: [Keys and Services](Providers-and-Keys).
 
 ## AI CLIs (Claude Code, Codex, Antigravity)
 
@@ -36,31 +36,31 @@ Keys and how to get them: [Providers and Keys](Providers-and-Keys).
 | "Your Codex plan's usage limit is used up ... Slopify waits for it to reset and then carries on by itself." (also Claude and Antigravity) | Nothing to do: the run waits instead of failing. The project, Home, Projects and the Calendar say "Waiting for Codex limits (resets at 14:00)". See [Recovery and Retries](Recovery-and-Retries#waiting-for-cli-plan-limits). |
 | "The *CLI* stopped without answering" | Run the CLI in a terminal to check it works and is signed in, then try again. |
 | "Slopify could not hand the whole prompt to the CLI, so it cannot tell what the CLI worked on (it may already have used your quota)." | Use **Try again**. This is not retried automatically, so you choose whether to spend the quota again. |
-| "No Codex model is chosen for images." | Choose a model (or Codex default) for images in **Edit project → Providers**, then try again. |
-| "Slopify could not get the model list from the *CLI* CLI." | Check the CLI is installed and signed in (Settings → Providers), refresh the list, or type an exact model ID. |
-| A CLI shows as not installed in Settings | Install the CLI so it is on your `PATH`, or, in Docker, rerun the Docker install after installing or moving a CLI so the host helper finds it. Then press **Check again** on its row under **Health check**. |
-| "The Antigravity CLI tried to use a tool Slopify does not allow (it said: …), so it gave no answer." | Headless `agy` refuses page reading, the browser and commands, and then ends its turn with no text. Press **Try again**. If it keeps happening, choose another model or text provider in the **Providers** section of **Edit project**. |
-| "The Antigravity CLI answered with no text." | Press **Try again**. If it keeps happening, run `agy` in a terminal to check it works, or choose another model in the **Providers** section of **Edit project**. |
-| "The Antigravity CLI is busy: Google's capacity for this model is used for the moment…" | Nothing to do: Slopify tries again by itself shortly. If it keeps happening, run fewer projects at once or choose another model in the **Providers** section of **Edit project**. |
+| "No Codex model is chosen for images." | Choose a model (or Codex default) under **Images by** in **Edit settings** → **Images**, then try again. |
+| "Slopify could not get the model list from the *CLI* CLI." | Check the CLI is installed and signed in (Settings → Keys & services), refresh the list, or type an exact model ID. |
+| A CLI shows as not installed in Settings | Install the CLI so it is on your `PATH`, or, in Docker, rerun the Docker install after installing or moving a CLI so the host helper finds it. Then press **Check every service** on Settings → **Keys & services**, or **Check again** on its row. |
+| "The Antigravity CLI tried to use a tool Slopify does not allow (it said: …), so it gave no answer." | Headless `agy` refuses page reading, the browser and commands, and then ends its turn with no text. Press **Try again**. If it keeps happening, choose another model or writing service under **Written by** in **Edit settings** → **Article**. |
+| "The Antigravity CLI answered with no text." | Press **Try again**. If it keeps happening, run `agy` in a terminal to check it works, or choose another model under **Written by** in **Edit settings** → **Article**. |
+| "The Antigravity CLI is busy: Google's capacity for this model is used for the moment…" | Nothing to do: Slopify tries again by itself shortly. If it keeps happening, run fewer projects at once or choose another model under **Written by** in **Edit settings** → **Article**. |
 | "The Antigravity CLI is not signed in…" | Run `agy` in a terminal, sign in with your Google account, then press **Try again**. |
-| A run stops with "The chosen model is not available…" after the move from Gemini CLI | The old Gemini CLI model ids (for example `gemini-2.5-pro`) are not in the Antigravity CLI list. Run `agy models` and pick a model in **Edit project → Providers**. |
+| A run stops with "The chosen model is not available…" after the move from Gemini CLI | The old Gemini CLI model ids (for example `gemini-2.5-pro`) are not in the Antigravity CLI list. Run `agy models` and pick a model under **Written by** in **Edit settings** → **Article**. |
 
 See [AI CLIs](AI-CLIs).
 
-## Provider refusals, models and timeouts
+## Refusals, models and timeouts
 
 | Message (or part of it) | Fix |
 | --- | --- |
-| "*Provider* refused to make this image under its content rules" | Press **Soften and retry**, or reword the image prompt in **Edit project → Images**, or choose another image provider. |
-| A content filter refused a text prompt | Press **Edit the prompt** and reword it in **Edit project → Prompts**. |
-| "The chosen model may not exist or not be available to your account" / "The model for ... is no longer offered." | Press **Switch model**, pick another model in **Edit project → Providers**, save, try again. See [Models](Models). |
-| "The AI model did not answer within 120 seconds. It may be overloaded" (also the narration provider, image provider or image-to-video model) | Wait a few minutes, then **Try again**, or choose another model. Slopify already retried several times before showing this. |
-| "*Provider* sent back something that is not a PNG or JPEG image" | Use **Try again**; if it keeps happening, choose another image model. |
-| "Check that voice ... still exists in Settings → Voices and that each narration part fits the model's length limit" | The voice was removed, or a chunk is too long for the model. Pick a saved voice, or lower **Chunking** in **Edit project → Providers**. |
-| An animated image failed ("choose another image-to-video model under Animate images in Edit project → Inputs → Look") | Try again, or pick another model under **Animate images**. The image stays still meanwhile and is listed under **Render notes**. |
+| "*Service* refused to make this image under its content rules" | Press **Soften and retry**, or reword the image prompt in **Edit settings** → **Images**, or choose another image service. |
+| A content filter refused a text prompt | Press **Edit the prompt** and reword the prompt in **Edit settings**, in the section of the step that failed. |
+| "The chosen model may not exist or not be available to your account" / "The model for ... is no longer offered." | Press **Switch model**, pick another model in **Edit settings** (under **Written by**, **Read by** or **Images by**), save, try again. See [Models](Models). |
+| "The … did not answer within … seconds. It may be overloaded" (the AI model, the voice service, the image service or the image-to-video model) | Wait a few minutes, then **Try again**, or choose another model. Slopify already retried several times before showing this. |
+| "*Service* sent back something that is not a PNG or JPEG image" | Use **Try again**; if it keeps happening, choose another image model. |
+| "Check that voice ... still exists in Settings → Voices and that each narration part fits the model's length limit" | The voice was removed, or a chunk is too long for the model. Pick a saved voice, or split the narration into smaller parts (**Split the narration by** in **Edit settings** → **Narration**). |
+| An animated image failed ("choose another image-to-video model under Animate images …") | Try again, or pick another model under **Animate images** (**Edit settings** → **Video and style** → **Look**). The image stays still meanwhile, and the Video part says so in its notes. |
 | Rate limit messages (429) | Nothing to do: Slopify waits and tries again by itself. |
 
-## ffmpeg, captions and rendering
+## ffmpeg, captions and making the video
 
 Slopify ships its own ffmpeg; you do not need to install one. In Docker it is inside the image.
 
@@ -68,13 +68,13 @@ Slopify ships its own ffmpeg; you do not need to install one. In Docker it is in
 | --- | --- |
 | "Slopify can't find ffmpeg ... its bundled copy is missing for this computer." | Reinstall Slopify, or set `SLOPIFY_FFMPEG` to the path of an ffmpeg program. On first start Slopify also tries to download the same build into `<data-dir>/bin/`; if that fails, check your connection and your antivirus quarantine. |
 | "Slopify could not start ffmpeg ..." | Reinstall Slopify. If you set `SLOPIFY_FFMPEG`, check it points to a working ffmpeg. |
-| "The audio/video export failed (ffmpeg exited with code ...)" | Open **Error details**: it quotes what ffmpeg could not do, for example an input file it could not open. Replace that file (an uploaded image or clip in **Edit project → Images**), or try again. |
-| "Slopify couldn't measure the loudness of the narration" | Try again. If it happens again, turn off **Level the volume** in **Edit project → Inputs → Pauses and volume**, then download diagnostics and report it. |
-| "The style preview couldn't render ... Press Render again." | Press **Render again**. If it fails again, download diagnostics and report it. |
-| "The free subtitle model could not be downloaded" / "download was interrupted" / "failed download verification" | The caption model (378 MB by default, the size chosen in Settings → Production defaults → **Subtitle timing model**) downloads on first use. Check your connection, then **Continue** the run, or pick a smaller model there. `SLOPIFY_NO_MODEL_PREFETCH` only skips the download at start; captions still need it. |
-| "Captions can't be edited until the current narration has finished and its subtitle timing is ready." | Let the narration and subtitle timing finish, then edit captions. |
-| "The saved subtitle timing doesn't match the current narration." | Do what the message says: make the subtitle timing again (More → make it again), then edit the captions. |
-| "Subtitles recovered after missing narration (N)" under the video | Some transcript passages could not be matched to the audio and were left out of the captions. The audio is fine. Review those passages before sharing. |
+| "The audio/video export failed (ffmpeg exited with code ...)" | Open **Error details**: it quotes what ffmpeg could not do, for example an input file it could not open. Replace that file (an uploaded image or clip in **Edit settings** → **Images**), or try again. |
+| "Slopify couldn't measure the loudness of the narration" | Try again. If it happens again, turn off **Level the volume** in **Edit settings** → **Video and style** → **Sound polish**, then download diagnostics and report it. |
+| "The style preview couldn't be made. Press Make the preview again." | Press **Make the preview again**. If it fails again, download diagnostics and report it. |
+| "The free subtitle model could not be downloaded" / "download … was interrupted" / "failed download verification" | The caption timing model (378 MB by default, the size chosen in Settings → Production defaults → **Caption timing model**) downloads on first use. Check your connection, then **Continue** the run, or pick a smaller model there. `SLOPIFY_NO_MODEL_PREFETCH` only skips the download at start; captions still need it. |
+| "Captions can't be edited until the current narration has finished and its caption timing is ready." | Let the narration and its caption timing finish, then edit the captions. |
+| "The saved caption timing doesn't match the current narration." | Do what the message says: press **Make the video again** in the project's Video part, which times the captions again, then edit the captions. |
+| **Passages left out of the captions** under the video | Some passages could not be matched to the audio, so the captions skip them. The audio is fine. Press a passage's time to hear it, and look them over before sharing. |
 
 With **Language** set to one without word timing, captions and cuts work differently; see [Other Languages](Other-Languages).
 
@@ -99,15 +99,15 @@ See [Install](Install) for the command-line options.
 | "Slopify hit an unexpected error (*code*). Reload the page and try again." | Reload. If it keeps happening, download diagnostics and report it. |
 | "The project could not be loaded." | Reload, or go back to Projects. |
 | "The upload stopped before the file finished copying. Choose the file again." | Pick the file again and wait for "Waiting for uploads to finish…" to clear before saving. |
-| "A newer revision is available. Your unsaved changes are kept below and in this browser." | The project was saved elsewhere (another tab, a remake). Press **Reload latest and re-apply my edit** to lay your changes over the newer revision, check them and press **Save changes**; **Copy my edit** puts your changes on the clipboard first. |
+| "A newer version is available. Your unsaved changes are kept below and in this browser." | The project was saved elsewhere (another tab, or something made again). Press **Reload latest and re-apply my edit** to lay your changes over the newer version, check them and press **Save changes**; **Copy my edit** puts your changes on the clipboard first. |
 
 ## Disk space
 
 | Symptom | Fix |
 | --- | --- |
 | A step fails with "The disk is full, so ... stopped." | Press **Free space**; Settings → **Backup & storage** shows each project's size. Delete projects you do not need (they go to the [Trash](Trash); **Delete now** frees the space at once), or use **Keep outputs only** on finished projects. Then try again. |
-| You want space back from a finished project | On its page, **Free space** → **Free …: keep the outputs, drop the working files**. See [Project Page](Project-Page#free-space). |
-| History shows "Retained file missing" or "File missing" | That output's file was removed from disk (for example by **Keep outputs only**, or by hand). Remake the output to get it back. |
+| You want space back from a finished project | On its page, **Edit settings** → **Versions** → **Free space** → **Free …**. See [Project Page](Project-Page#free-space). |
+| **Versions** or **All files** shows "File missing" | That file was removed from disk (for example by **Keep outputs only**, or by hand). Make it again to get it back. |
 
 See [Where Your Files Live](Where-Your-Files-Live).
 
@@ -120,7 +120,7 @@ See [Where Your Files Live](Where-Your-Files-Live).
 | AI CLIs | Run directly with your logins | Run on the host through a small helper, `slopify-cli-bridge.service`, with your existing logins. Check it with `systemctl --user status slopify-cli-bridge.service`. Without it, Settings shows the CLIs as unavailable. |
 | **Open folder** | Opens your file manager | Opens it through the host helper; without the helper you get the path to copy, and "run the Docker launcher again ... so it sets up the host helper" |
 | Start at login | Settings → General → **Start Slopify when I log in** | Slopify starts whenever Docker does; Settings only shows Docker's own setting (with Docker Desktop, its **Start Docker Desktop when you sign in**) |
-| Updating | The updates button at the foot of the sidebar, or `npx @gentbajko/slopify@latest update` while Slopify is running | `npx @gentbajko/slopify@latest update` from the terminal. It keeps a recovery copy of your data in a Docker volume and puts the previous version back if the new one does not start. |
+| Updating | **Help → Check for updates** at the foot of the rail, or `npx @gentbajko/slopify@latest update` while Slopify is running | `npx @gentbajko/slopify@latest update` from the terminal. It keeps a recovery copy of your data in a Docker volume and puts the previous version back if the new one does not start. |
 
 If an install or update fails, the message names what failed and, in Docker, the volume that holds the recovery copy of your data. Do not delete that volume; fix the problem and run the same command again. See [Docker](Docker) and [Updating and Patch Notes](Updating-and-Patch-Notes).
 
@@ -128,27 +128,27 @@ If an install or update fails, the message names what failed and, in Docker, the
 
 | What you see | What it means |
 | --- | --- |
-| **Queued** | Other videos in the batch queue go first. The Calendar's **Batch queue** shows the order. |
+| **Queued** | Other videos in the queue go first. Home's and the Calendar's **Waiting to start** show the order. |
 | **Waiting for limits** / "Waiting for Codex limits (resets at 14:00)" | A CLI plan is used up; the run waits and carries on after the reset time shown. |
 | **Waiting to try again** | A rate limit or timeout; it retries at the time shown. |
-| **Waiting for your review** | A checkpoint is holding the run. Press **Approve ...**. |
-| **Waiting for the agent** | A review set to **External agent (MCP)** waits for your agent. Check the agent's routine is running; with no answer, the review passes by itself after 2 hours. See [Agents (MCP)](Agents-MCP). |
-| **Prepared** | Its schedule made it ahead; the video is made on its day. |
-| A step says **taking longer than usual** | It has run longer than the same step usually takes in your finished runs. It is still going; open **Live** to see whether text or images are still arriving. |
+| **Waiting for your review** | A pause is holding the run. Press **Approve and make the …**. See [Pauses and Checks](Reviews-and-Checkpoints). |
+| **Waiting for the agent** | An AI check set to **Your own AI agent** waits for your agent. Check the agent's routine is running; with no answer, the review passes by itself after 2 hours. See [Agents (MCP)](Agents-MCP). |
+| **Waiting for its day** | Its schedule made it ahead; the video is made on its day. |
+| A step says **taking longer than usual** | It has run longer than the same step usually takes in your finished runs. It is still going; open **Progress** to see whether text or images are still arriving. |
 | **Paused** | Press **Continue the run**. |
 | **Stopped** | The run was interrupted (for example by a restart). Press **Continue the run**. |
 | A step is failed with "interrupted" | Slopify stopped while it ran. Press **Try ... again**. |
 
 ## Tips
 
-- Open the **Live** view on a project to watch text, narration and images arrive; it shows whether anything is still happening.
+- Open **Progress** on a running project to watch text, narration and images arrive; it shows whether anything is still happening.
 - Keep Slopify on `127.0.0.1`. There is no login, so anyone who reaches the port controls the app and its keys.
 
 ## Related pages
 
 - [Recovery and Retries](Recovery-and-Retries)
 - [FAQ](FAQ)
-- [Providers and Keys](Providers-and-Keys)
+- [Keys and Services](Providers-and-Keys)
 - [AI CLIs](AI-CLIs)
 - [Docker](Docker)
 - [Install](Install)

package/dist/tutorials/Uninstalling-and-Moving.md

@@ -7,7 +7,7 @@ How to take Slopify off a computer, and how to move your projects between a norm
 ## Before you remove anything
 
 1. Let running projects finish, or pause them.
-2. Open Settings → **Backup & storage** and press **Export everything**. Keep the downloaded `.tar` file somewhere safe. It holds every project with its files and history, your library, templates, schedules, Play drafts, fonts, settings and usage. It does not hold your provider keys; keep those in your password manager.
+2. Open Settings → **Backup & storage** and press **Export everything**. Keep the downloaded `.tar` file somewhere safe. It holds every project with its files and versions, your prompts, templates, schedules, Create drafts, fonts, settings and usage. It does not hold your service keys; keep those in your password manager.
 3. If you turned on Settings → **General** → **Start Slopify when I log in**, turn it off. That removes the login entry, so nothing tries to start Slopify at your next login.
 
 Deleting the folders below can't be undone. Scheduled backups in your `Backups` folder are deleted with it unless you move them first.
@@ -59,7 +59,7 @@ The installer turned on user lingering for the bridge (so your user services run
 3. Start Slopify normally: `npx @gentbajko/slopify@latest`. See [Install](Install).
 4. In the new Slopify, open Settings → **Backup & storage** → **Import a backup** and pick the `.tar` file. Large backups take a while to upload and check.
 5. Read the summary. Projects, library, templates and settings come in; schedules arrive paused.
-6. Enter your provider keys in Settings → **Providers** and check your voices in Settings → **Voices**.
+6. Enter your service keys in Settings → **Keys & services** and check your voices in Settings → **Voices**.
 7. Resume your schedules on the Schedules screen. See [Schedules](Schedules).
 8. Once everything opens fine, remove the Docker install as above.
 
@@ -69,7 +69,7 @@ The installer turned on user lingering for the bridge (so your user services run
 2. Stop it (`Ctrl+C`). If start-at-login is on, turn it off first so it doesn't come back at the next login and take port 6969.
 3. Install Docker: `npx @gentbajko/slopify@latest --docker`. See [Docker](Docker).
 4. Open `http://127.0.0.1:6969`, go to Settings → **Backup & storage** → **Import a backup** and pick the file.
-5. Enter your provider keys, resume schedules, and check that your projects open.
+5. Enter your service keys, resume schedules, and check that your projects open.
 6. Remove the old install when you are sure.
 
 ## Move to another computer
@@ -87,7 +87,7 @@ An import adds and never replaces:
 | Schedules | Arrive paused, so two installs never run them both. |
 | Settings | Filled in where this install has none; this install's own are kept. |
 | Usage history | Added once; importing the same backup again doesn't count it twice. |
-| Provider keys | Never in a backup. Enter them again. |
+| Service keys | Never in a backup. Enter them again. |
 
 Running projects must finish or pause before an import. See [Backups](Backups) for what an archive carries in full.
 
@@ -108,6 +108,6 @@ To put your project files on another disk or in Documents while keeping the same
 - [Install](Install)
 - [Docker](Docker)
 - [Start at Login](Start-at-Login)
-- [Providers and Keys](Providers-and-Keys)
+- [Keys and Services](Providers-and-Keys)
 - [Schedules](Schedules)
 - [Trash](Trash)

package/dist/tutorials/Updating-and-Patch-Notes.md

@@ -2,26 +2,26 @@
 
 Slopify checks for new versions by itself and updates with one click or one command. An update waits for running work, keeps a copy to go back to, and puts the previous version back if the new one doesn't start. After an update, the new version's patch notes open once.
 
-**Where to find it:** the circular-arrows button at the foot of the sidebar. Patch notes are in Settings → **Patch notes**; Settings → **About** has **What's new in this version**.
+**Where to find it:** **Help → Check for updates** at the foot of the rail, and **Update ready** in the rail when a new version is ready. Patch notes are in **Help → What's new** (Settings → **Patch notes**); Settings → **About** has **What's new in this version**.
 
-## The updates button
+## Where updates show
 
-The circular-arrows button at the foot of the sidebar (in the top bar on a phone) shows the update state. Hover it (or read it with a screen reader) to see `Your version: … · Newest: …` and what a click does. The version you are running is also shown beside the Slopify logo at the top of the sidebar.
+**Help** at the foot of the rail ends with the update row: a line with the version you are running (`You have Slopify …`, or `Your version: … · Newest: …`) and the one thing to do. While there is something new, the rail also shows an item for it, in words, above **Search**. On a phone the update stays inside **Help**, which turns lime-ink while an update is ready.
 
-| What you see | Meaning | Click does |
+| What you see | Meaning | The row does |
 | --- | --- | --- |
-| No dot | You have the newest version, as of the last check. | Checks again now. |
-| A dot on the button | An update is ready. | Downloads and installs it. |
-| Spinning | Checking, or updating. | Nothing; wait. |
-| Label says **Update to X will install when 'Title' finishes.** | The update is waiting for running work. | Cancels the waiting update. |
-| Amber | The last check or update had a problem. The label says what. | Checks again. |
+| No item in the rail; Help says **Check for updates** | You have the newest version, as of the last check. | Checks again now. |
+| **Update ready** in the rail; its menu says what installing does | An update is ready. | **Install update X** downloads and installs it. |
+| **Checking for updates…** or **Updating…** | Checking, or updating. | Nothing; wait. |
+| **Update waiting**, and the line **Update to X will install when 'Title' finishes.** | The update is waiting for running work. | **Cancel the update** drops the waiting update. |
+| **Update failed**, and the line says what | The last update had a problem. | **Install update X** tries again. |
 
 Slopify checks every 15 minutes and whenever you come back to the tab.
 
 ## Update from the app
 
-1. Click the circular-arrows button when it shows a dot.
-2. If a video is being made, the update waits. A message says **Update to X will install when 'Title' finishes.** Click the button again to cancel the waiting update; nothing has changed yet.
+1. Press **Update ready** in the rail (or **Help**), then **Install update X**. The menu says first that installing restarts Slopify and that anything running finishes first.
+2. If a video is being made, the update waits. A message says **Update to X will install when 'Title' finishes.** **Cancel the update** in the same menu drops it; nothing has changed yet.
 3. When nothing is running, Slopify installs the new version, stops, and starts the new one.
 4. The page reconnects by itself. If another open tab was loaded before the update, it shows **Slopify was updated** with **Reload**.
 
@@ -33,7 +33,7 @@ Run:
 npx @gentbajko/slopify@latest update
 ```
 
-It asks the running Slopify to update itself, exactly as the button does, and follows it until it is done:
+It asks the running Slopify to update itself, exactly as **Install update** does, and follows it until it is done:
 
 - `Slopify X is already the newest version.` when there is nothing to do.
 - `Slopify is generating right now. Waiting for running work to finish before updating (press Ctrl+C to cancel; nothing has been changed yet)...` while work runs.
@@ -58,9 +58,9 @@ Later starts of Slopify, including an older `npx` or a global `slopify` command,
 
 For Docker, the installer does the update from the host with a recovery copy of the whole data volume. See [Docker](Docker#update-the-docker-install).
 
-## When the button can't update
+## When the app can't update
 
-The button's label says why:
+The line above the update row says why:
 
 | Message | What to do |
 | --- | --- |
@@ -68,7 +68,7 @@ The button's label says why:
 | Run Slopify from its installed package to use in-app updates. | You are running from source or a copy without its package files. Start it with `npx @gentbajko/slopify@latest`. |
 | npm was not found, so in-app updates are off. | Install Node.js with npm from nodejs.org, or update from the terminal with `npx @gentbajko/slopify@latest`. |
 | An update is already in progress. | Wait for it to finish. |
-| An update is already waiting for running work to finish. | Wait, or click the button to cancel it. |
+| An update is already waiting for running work to finish. | Wait, or press **Cancel the update**. |
 
 If an update didn't finish, Slopify keeps or puts back the previous version. `logs/updates.log` in the data folder says why.
 
@@ -92,7 +92,7 @@ After an update to a new major version (for example 2.x to 3.0), the first launc
 - The last step has **Read the full patch notes**.
 - Closing the tour also counts as having seen that version's patch notes.
 
-The 3.0 tour covers Home, Play's one path, Automatic reviews, Channels and cast, Episodes that remember (episode memory and your existing videos), The calendar, What a run cost, YouTube Studio prep, Multiple voices, Long videos stay watchable (more images per hour and ambient sound), Other languages and A trash bin. A fresh install never sees it.
+The 3.0 tour covers Home, Create's one path, An AI checks the results, Channels and cast, A channel that remembers (its Memory and Titles to avoid tabs), The calendar, What a run cost, Copy for YouTube Studio, Multiple voices, Long videos stay watchable (more images per hour and ambient sound), Other languages and A trash bin. A fresh install never sees it.
 
 ## Read the patch notes
 
@@ -106,8 +106,8 @@ To open the notes for the version you are running, go to Settings → **About**
 
 ## Tips
 
-- Keep Slopify running overnight? Updates wait for running work, so you can press the button at any time and it installs when the current video is done.
-- Settings → **About** has the same explanation of the updates button, and links to GitHub, Patreon and Buy Me a Coffee.
+- Keep Slopify running overnight? Updates wait for running work, so you can press **Install update** at any time and it installs when the current video is done.
+- Settings → **About** has the same explanation of updates. GitHub, Patreon and Buy Me a Coffee are under **Support Slopify** at the foot of the rail.
 - Updating doesn't touch your projects folder. For extra safety before a big update, use **Export everything** or turn on [Backups](Backups).
 
 ## Related pages