@gentbajko/slopify 3.0.0 → 3.0.2

package/dist/tutorials/Reviews-and-Checkpoints.md

@@ -0,0 +1,143 @@
+# Reviews and Checkpoints
+
+Two ways to keep an eye on a run before it spends more. A **review checkpoint** holds the run before a step until you approve it, so you can check and edit what came before. An **automatic review** has a reviewer model check each finished item (the article, every image, the narration, the thumbnail, every short) and flag it, or make it again, when it fails.
+
+**Where to find it:** Play → **Reviews** row → **Change**, which opens the **Review** side panel. **Review the whole setup** in the right rail and `Ctrl+Enter` open the same panel. After the run starts: the project page → **Checkpoints**, and Edit project → **Reviews**.
+
+## The Review side panel
+
+The panel holds, from top to bottom:
+
+1. Any setup errors. Press one to jump to the field.
+2. **Review checkpoints**.
+3. **Automatic reviews**.
+4. The whole setup in words, with **Read the resolved prompt** (or **Read the supplied article and resolved prompts**), which shows each prompt exactly as it will be sent.
+
+The estimate and the Play key stay in the right rail. Opening the panel also asks the server to check the setup, since it knows rules the browser cannot see. **Refresh review** in the right rail does the same and recalculates the estimate now, instead of waiting for you to pause typing. Use it after changing a prompt in the Library.
+
+The Reviews row summary says what is set, for example `1 checkpoint · 2 automatic reviews`, or `No checkpoints · no automatic reviews`.
+
+## Review checkpoints
+
+A checkpoint holds the run before a step so you can check and edit what came before it. Steps that do not depend on it carry on. You approve each checkpoint on the project page to continue.
+
+| Checkpoint | Holds | Available when |
+| --- | --- | --- |
+| **Before Audio** | The narration and what depends on it | Narration Source is **Generate** |
+| **Before Images** | The images and what depends on them | Images Source is **Generate** |
+| **Before Video / export** | The render and the exports | The video is on, or narration is on |
+
+A step must be generated to have a checkpoint. A greyed checkbox says why: "Choose Generate for Images to add this checkpoint", or "Enable Video or Audio to review before export." A ticked checkpoint whose step you later turn off says "This step is unavailable. Remove its checkpoint or enable the step."
+
+Default: no checkpoints.
+
+### Add a checkpoint on Play
+
+1. Open the **Reviews** row (or press **Review the whole setup**).
+2. Under **Review checkpoints**, tick **Before Audio**, **Before Images** or **Before Video / export**.
+3. Press **Refresh review** to see, per video, which steps each checkpoint also holds ("Run 1 · Before Images", "Also holds: Video / export.").
+4. Start the run.
+
+Starting the run does not approve the checkpoints. The run stops at each one until you approve it on the project page.
+
+### Continue a run held at a checkpoint
+
+When the run reaches a checkpoint, the held step waits and the project's next action says so.
+
+1. Open the project. The right rail's next action names what runs after approval, for example **Approve and make the images**, **Approve and record the narration** or **Approve and render the video**.
+2. Check and edit what came before: read the article, listen to the narration, look at the images. See [Editing a Project](Editing-a-Project).
+3. Press the next action, or open **Checkpoints** in the project's side list (it shows how many are held) and press **Approve Images checkpoint** (or the stage you are at).
+
+The checkpoint then says "Checkpoint approved. Work will run when its dependencies are ready." Each checkpoint card shows its state:
+
+| Message | Meaning |
+| --- | --- |
+| "Images is held for your review. Its dependent work waits for this approval; independent work can continue." | Waiting for you. |
+| "Inputs changed. Review the current revision before approving." | You edited something the held step uses. Check the new version before approving. |
+| "Authorized for this revision. Work can run when dependencies are ready and the project is resumed." | Approved; it runs when it can. |
+| "Checkpoint satisfied. Its reviewed work is complete." | Done. |
+
+If the project is paused, the panel says "The project is paused. Continue the run before approving held work." Pausing always applies on top of checkpoints.
+
+### Change checkpoints after the run started
+
+On the project page → **Checkpoints** → **Checkpoint choices**:
+
+1. Tick a step that has not started to add a checkpoint, or untick one to remove it. Work already admitted for an unticked step carries on when ready.
+2. Press **Save checkpoints**.
+
+Only generated steps can have one. If the project was edited elsewhere in the meantime, press **Reload checkpoint choices** and make your change again.
+
+## Automatic reviews
+
+A reviewer model checks each finished item and saves its verdict and reasons on the project page. Each review is a text-model call, counted in usage and in the estimate.
+
+| Option | What it does | Default / range |
+| --- | --- | --- |
+| **Reviewer** | Who runs the review model. Picture reviews (images, the thumbnail and shorts) need Claude Code or Codex, which can look at images; other providers review text only. | None |
+| **Reviewer model** | The model that judges each item. A stronger model catches more but costs more per review. It can differ from the model that wrote the text. | None |
+| **Redos per item** | How many times **Flag and redo** makes a failed item again before it keeps the last one and flags it. Each redo costs the item again plus one more review. | 2; 0 to 5 |
+
+Then, for each stage (**Article**, **Images**, **Narration**, **Thumbnail**, **Shorts**), pick a mode and a prompt:
+
+| Mode | What happens to a failed item |
+| --- | --- |
+| **Off** (default) | No review. |
+| **Flag only** | The item is marked failed, with the reasons, and the run carries on. |
+| **Flag and redo** | The item is made again and reviewed again, up to **Redos per item**. After that it is kept and flagged. It never loops. |
+
+The prompt next to each mode is **Built-in** or a **Review** prompt from the Library (see [Prompts](Prompts)). It is greyed while the mode is Off. A stage the run makes nothing for is greyed too; a stage set to review but with nothing to review says "This stage makes nothing to review in this run."
+
+### What each review checks
+
+| Stage | The built-in reviewer checks |
+| --- | --- |
+| **Article** | The article prompt's rules (length, structure, tone), no invented lore, no repeated sections. The research notes are included. |
+| **Images** | Malformed hands or bodies, stray text or letters, that it matches its brief, and that it matches the establishing image when one is on. |
+| **Narration** | Nothing missing or garbled compared with the text: the reviewer reads what the word timing heard and the stretches it could not hear. |
+| **Thumbnail** | Readable at phone size, clear subject. |
+| **Shorts** | The short's images at phone size: clear subject, no stray text, fits the title. |
+
+### Set up automatic reviews
+
+1. Open the **Reviews** row.
+2. Pick the **Reviewer** and **Reviewer model**. For image, thumbnail or shorts reviews, pick Claude Code or Codex. With another reviewer, the panel says "Picture reviews need Claude Code or Codex as the reviewer: Slopify can't show pictures to this one." and the run cannot start.
+3. Optional: set **Redos per item** (empty means 2).
+4. For each stage you want checked, pick **Flag only** or **Flag and redo**, and optionally a Review prompt.
+5. Check the estimate: each review adds one text-model call. Redos are not in the estimate; each costs what the item cost, at most the redos allowed.
+
+### Reviews on the project page
+
+Beside the article, the narration, the thumbnail and each short, and on each image tile, the verdict shows as **Review passed**, **Flagged by review**, **Waiting to be made again**, **Being made again**, **Redone after review** or **Accepted by you**, with the reasons. For a failed item nobody has acted on:
+
+- **Overrule** accepts it as it is.
+- **Redo** makes it again (a new version of the project, then the item and what depends on it are rebuilt), and it is reviewed again.
+
+Both buttons wait while other work on the project is running, with one exception: while a **Flag and redo** review's automatic redo is still waiting to start (**Waiting to be made again**), **Overrule** stays available and calls the redo off. The item is accepted as it is, the badge turns to **Accepted by you**, and the work waiting on it goes ahead. Once the redo has started, Overrule is greyed: "Slopify is already making this item again; wait for the new version".
+
+When an automatic review flags an item and keeps it (its redos ran out, or the stage is on **Flag only**), Slopify sends a **Review needs a decision** notification (see [Notifications](Notifications)), and the project shows in the Calendar's **Needs you** with **Open to review** (see [Calendar](Calendar#needs-you)). Everything that uses a reviewed item waits for its review, in the same way a checkpoint holds work. Reviewing the same output with the same reviewer and prompt again reuses the earlier verdict.
+
+## Checkpoints or reviews?
+
+| You want to | Use |
+| --- | --- |
+| Read the article yourself before paying for the narration | **Before Audio** checkpoint |
+| Look at the images before the render | **Before Images** is too early; use **Before Video / export** |
+| Catch broken hands or stray text without watching every run | **Images** review, **Flag and redo** |
+| Run unattended on a schedule and fix things later | Reviews on **Flag only**, no checkpoints |
+
+## Tips
+
+- Checkpoints and reviews are saved with a template, so every video started from it gets them. See [Templates](Templates).
+- Keep **Redos per item** low for images: five redos is already six paid images for one slot.
+- You can change reviews later in Edit project → **Reviews**. See [Editing a Project](Editing-a-Project).
+
+## Related pages
+
+- [Play Overview](Play-Overview)
+- [Project Page](Project-Page)
+- [Editing a Project](Editing-a-Project)
+- [Recovery and Retries](Recovery-and-Retries)
+- [Prompts](Prompts)
+- [AI CLIs](AI-CLIs)
+- [Costs and Run Cost](Costs-and-Run-Cost)

package/dist/tutorials/Schedules.md

@@ -0,0 +1,154 @@
+# Schedules
+
+A schedule starts a new project from a saved template at a set local time: every day, on chosen weekdays, or once. Give it a list of topics and each run takes the next one. Turn on topic generation and it asks your text model for new topics before the list runs dry.
+
+**Where to find it:** **Calendar → Schedules**, the second tab on the calendar. Old `/schedules` links and **G then S** open it too. A channel's **Schedules** tab lists the schedules that run its templates.
+
+## Before you start
+
+- A schedule runs a **template**, so save one first: see [Templates](Templates).
+- Runs only start while Slopify is open on this machine. If you want it running all the time, see [Start at login](Start-at-Login) or [Docker](Docker).
+- Each run costs what that template's project costs. Set a **Spend ceiling** to stop an unexpectedly expensive run.
+
+## Create a schedule
+
+1. Open **Calendar**, then the **Schedules** tab, and press **New schedule**.
+2. Fill in **Name** (up to 200 characters). It never appears in the videos.
+3. Pick the **Template** each run starts from. The schedule keeps the template's current version.
+4. Choose the **Cadence** and times (see below).
+5. Add **Topics** (see below), or leave the list empty to run the template exactly as saved.
+6. Optional: set up **Topic generation**, a **Spend ceiling** and what happens to a **Missed run**.
+7. Press **Save schedule**.
+
+The schedule appears under **Saved schedules** with its status, next run and the title that run will get. A press anywhere on a schedule's row opens it.
+
+## When it runs
+
+| Setting | What it does | Default |
+|---|---|---|
+| **Cadence** | **Every day** runs once a day at the local time. **Selected weekdays** runs on the days you tick. **One time** runs once at a date and time, then shows as completed. Each run starts one project. | Every day |
+| **Local time** | The clock time each run starts, read in the timezone below. | 09:00 |
+| **Weekdays** | The days a Selected weekdays schedule runs. Tick at least one; each ticked day is one project a week. | Mon, Wed and Fri |
+| **Run at** | The date and time of a One time schedule's single run. | |
+| **Timezone** | An IANA zone name such as `Europe/Tirane` or `America/New_York`. When clocks go back, a repeated time uses the earlier one. When clocks go forward, a skipped time moves forward by the gap (a One time schedule refuses a time that doesn't exist; pick another). | This computer's zone |
+| **Missed run** | What happens to a run that came due while Slopify was closed or asleep. **Skip if Slopify was closed** drops a run that is more than 1 minute late and waits for the next time. **Run once when Slopify reopens** starts one catch-up run, however many were missed. | Skip |
+| **Spend ceiling** | The most one run may cost, in US cents: `500` is $5.00. Before each run Slopify estimates the project's cost. When the high estimate is over the ceiling, or the cost can't be estimated, the run fails instead of starting. Leave it empty for no ceiling. | Empty |
+
+A schedule never runs two projects at once. If the previous run is still going when the next one comes due, the new run is skipped with the reason "the previous run of this schedule was still going". The detail panel shows this as **Overlap: Skip**.
+
+## Topics
+
+Each run takes the first topic, starts one project with it and removes it from the list. When the list is empty the schedule completes, unless topic generation is on. With no topics and generation off, every run uses the template as saved. A schedule holds up to 500 topics.
+
+### Which keyword a topic fills
+
+**Each topic fills** is the template keyword a topic replaces, such as `{{Topic}}`. By default it is the keyword the template's project title uses, or else the first one. If the title doesn't use this keyword, every project gets the same title.
+
+Every other keyword of the template has an every-run value: the value it gets on every run, such as a word count. The fields are labelled `<keyword> (every run)` and use the same keyword list as Play, Edit project and templates: the line under each says which prompts it feeds ("Feeds …"), or "Not used by any picked prompt". The default is the template's own value. A topic can set its own value for any keyword, which wins for that one run; the field then notes "Unless a topic sets its own."
+
+### Three ways to write the list
+
+**How to write the topics** switches between three views of the same list. Switching keeps everything.
+
+**One per line.** Type or paste one topic per line. Blank lines are skipped. The first line is the next run. Each topic fills only the topic keyword; every other keyword uses its every-run value. A line that matches a topic already in the queue keeps that topic's own values.
+
+**Table.** One row per run, in order. The first column fills the topic keyword. **Set a keyword per topic…** adds a column for another keyword; each cell sets that keyword for that row's run only, and a blank cell uses the every-run value. The **×** in a column's header drops the column. **Project title** shows the title each row will make.
+
+**YAML / JSON.** The same list as text, for pasting or keeping in a file. Write a plain list, or one map per topic with the topic under the topic keyword and a line for each other keyword it sets:
+
+```yaml
+- Topic: The Library of Alexandria
+  Min. Word Count: 12000
+- The Antikythera mechanism
+```
+
+A JSON array of the same shape works too. Values are read as the text written, so `12000`, `yes` and `0012` stay text. The schedule refuses, naming the topic number and key:
+
+- a value that is a list or a map,
+- a key that is not a keyword of the template,
+- a map without the topic keyword,
+- a topic missing a keyword that has no every-run value,
+- a value over 2,000 characters.
+
+The schedule saves only once the list reads. **Copy as YAML** and **Export as YAML** give you the queue in this shape.
+
+### Edit the queued topics in place
+
+Pick a schedule in the list to see its **Queued topics · N**. You can change the queue there without opening the form:
+
+- **Add topic**: type in **New topic** and press **Add topic** (or Enter). It goes to the end of the queue.
+- **Rename**: each topic is a field (**Topic 1**, **Topic 2**, …). Change the words and press Enter or click away to save; `Esc` puts the old words back.
+- **Move up** / **Move down**: the arrow buttons beside a topic.
+- **Remove**: the remove button beside a topic.
+
+Each change saves at once and says so, for example "Renamed to “Hypatia of Alexandria”.", with **Undo** on the notice. Only the queue changes; the next run and the other settings stay as they are. If the schedule changed in another tab meanwhile, the change is refused with the reason; reload and try again.
+
+## Topics that find themselves
+
+Under **Topic generation**, a schedule can ask an LLM for its next topics so it never runs dry.
+
+| Setting | What it does | Default |
+|---|---|---|
+| **New topics** | **Off: add topics yourself.** **Generate and queue directly:** new topics join the end of the list. **Generate and hold for approval:** they wait under **Topics waiting**, and beside the calendar, until you approve them. | Off |
+| **Series brief** | What the series covers, its style and what makes a topic worth a video. Only topic generation reads it. Leave it empty to use the channel's series brief from the channel's **Brand** tab. Up to 4,000 characters. | Empty |
+| **Keep at least this many queued** | Slopify asks for more topics whenever the queue, plus topics waiting for approval, drops below this number. From 1 to 100. | 10 |
+| **Topic generation LLM** | Ticked, it uses the provider and model the template writes with. Untick to pick another **Provider** and **Model**, such as a cheaper one. | The template's LLM |
+
+### How generation works
+
+1. When the queue (plus held topics) drops below your number, Slopify starts one generation in the background. It checks about every 15 seconds.
+2. It makes one LLM call for what is missing plus 5 spare, at most 50 topics.
+3. The call carries the series brief and every title already known: this schedule's queued, held, rejected and used topics, the titles of the projects in the schedule's own channel, and that channel's **Existing videos** (see [Channels](Channels)). Another channel's videos don't count: two channels may cover the same subject.
+4. Suggestions come back ranked most view-worthy first. Slopify drops near-duplicates of titles it already knows, for example "Hypatia" and "Hypatia's Library" count as one video, while "Ptolemaic Egypt" and "Roman Egypt" are two. A topic of one or two words only counts as made when a part of a title (split at `:`, `|`, brackets, `?` and similar) holds exactly those words, leaving aside words like "who", "what" or "explained": "Cleopatra" matches "Who was Cleopatra? The Last Pharaoh", but "Egypt" does not match "The Gods of Ancient Egypt".
+5. The rest join the queue, or wait for you under **Topics waiting**.
+
+Only one generation per schedule runs at a time. A failed try shows its reason on the schedule and is tried again 5 minutes later, not in a loop. A schedule with generation on keeps going when its queue empties; a run that finds no topic is skipped with the reason, instead of running the template without one.
+
+### Generate topics now
+
+Press **Generate topics now** to ask for new topics at once: at least 5, even when the queue is full and even during the 5-minute wait after a failed try. It is one LLM call. Saving the schedule also clears the wait.
+
+### Approve held topics
+
+When **New topics** is **Generate and hold for approval**, suggestions wait under **Topics waiting** on the schedule (and under **Suggested topics** on the [Calendar](Calendar)):
+
+- **Approve** adds one to the end of the queue.
+- **Edit** changes its words first, and can set the template's other keywords for that topic's run: one field per keyword, showing the every-run value (or the template's) as its placeholder. Press **Save**. The values are checked like the queue's and go with the topic into the queue when you approve it. A held row shows the values it sets, for example `Min. Word Count: 12000`.
+- **Reject** drops it for good; it is never suggested again.
+- **Approve all** queues every one in order.
+
+Waiting topics count toward **Keep at least**, so nothing more is asked for while they wait. If you set a Notification URL, you get a message such as "5 new topics are waiting for you"; see [Notifications](Notifications).
+
+## Manage a schedule
+
+Pick a schedule in the list to see its detail: **When**, **Timezone**, **Next run**, **Topics** left, **Missed runs**, **Overlap**, **Spend ceiling** and its **Run history**.
+
+| Action | What it does |
+|---|---|
+| **Edit** | Opens the **Edit schedule** form on the right. Only an active or paused schedule can change. Press **Save changes**. |
+| **Pause** / **Resume** | Stops runs until you resume. Only an active schedule can pause. |
+| **Cancel schedule** | Stops future runs for good. Existing projects and run history are kept. |
+| **Delete schedule** | Moves the schedule to **Settings → Trash** for 30 days. Its run history is kept. Restore brings it back paused. |
+| **Filter schedules by channel** | Shows only one channel's schedules. |
+| **Switch to <model>** | Shown under a schedule whose template picks a retired model, with "<model> is retired." Switches that model to its replacement in one press, as in Settings → **Models**. See [Models](Models). |
+
+**Run history** lists each run with its status (running, done, failed, skipped and so on), the time it was due, and either the project it made or the reason it didn't run. Deleted schedules are listed under **Deleted schedules** at the bottom; pick one to see its history.
+
+## Use a newer template version
+
+A schedule keeps the template version it was set up with, so saving a newer template doesn't change what the schedule makes. To switch, edit the schedule, pick the template again in **Template**, and save.
+
+## Tips
+
+- Try the template once from Play before scheduling it, so you know what one run costs. Then set the **Spend ceiling** a little above that.
+- Hold generated topics for approval at first. Once you trust the suggestions, switch to queue directly.
+- Write a clear series brief: what the series covers, the tone, and what makes a topic worth a video. Add your older videos under the channel's **Existing videos** so they aren't suggested again.
+
+## Related pages
+
+- [Calendar](Calendar)
+- [Templates](Templates)
+- [Channels](Channels)
+- [Notifications](Notifications)
+- [Costs and run cost](Costs-and-Run-Cost)
+- [Start at login](Start-at-Login)

package/dist/tutorials/Settings-Reference.md

@@ -0,0 +1,258 @@
+# Settings Reference
+
+Every section of Settings, what each control does and its default. Sections with a page of their own are summarised here and linked for the details.
+
+**Where to find it:** **Settings** in the sidebar, or press `Ctrl+K` and run **Open settings**. Settings opens on **Providers**. Pick a section in the rail on the left; on a phone the rail is a row of tabs you can scroll sideways.
+
+## Sections at a glance
+
+| Section | What it holds | Details |
+|---|---|---|
+| [General](#general) | Starting Slopify when you log in | [Start-at-Login](Start-at-Login) |
+| [Providers](#providers) | API keys, command-line tools, the system voice, health check | [Providers-and-Keys](Providers-and-Keys), [AI-CLIs](AI-CLIs) |
+| [Voices](#voices) | Voice IDs for narration | [Providers-and-Keys](Providers-and-Keys#add-a-voice) |
+| [Models](#models) | Model catalogue, retired models | [Models](Models) |
+| [Playback & appearance](#playback--appearance) | Silence gap, light or dark, volume levelling | This page |
+| [Notifications](#notifications) | Browser and phone notifications | [Notifications](Notifications) |
+| [Channel links](#channel-links) | A pointer to each channel's own links | [Channels](Channels#channel-links) |
+| [YouTube Studio](#youtube-studio) | Playlist per channel, the Studio extension's download and pairing | [Studio-Extension](Studio-Extension) |
+| [Backup & storage](#backup--storage) | Your files folder, export and import, disk space, samples | [Where-Your-Files-Live](Where-Your-Files-Live) |
+| [Backups](#backups) | The daily automatic backup | [Backups](Backups) |
+| [Trash](#trash) | Deleted items, kept 30 days | [Trash](Trash) |
+| [Usage](#usage) | This install's counters | [Costs-and-Run-Cost](Costs-and-Run-Cost#your-usage-totals-settings--usage) |
+| [Patch notes](#patch-notes) | What changed in each version | [Updating-and-Patch-Notes](Updating-and-Patch-Notes) |
+| [About](#about) | Updates, what's new, links | [Updating-and-Patch-Notes](Updating-and-Patch-Notes) |
+
+## Download diagnostics
+
+At the top right of every Settings section.
+
+| Control | What it does |
+|---|---|
+| **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 model catalogue's state. It never holds your keys, prompts or project content. Attach it to a bug report. |
+
+You can also press `Ctrl+K` and run **Download diagnostics** from anywhere in Settings.
+
+## General
+
+"How Slopify starts on this computer."
+
+| Control | What it does | Default |
+|---|---|---|
+| **Start Slopify when I log in** | Slopify starts in the background when you log in, without opening a browser tab; open it from your bookmark. It uses your account's own start-up list, so no administrator password is needed, and turning it off removes exactly what it added. | Off |
+
+In Docker, this section only shows whether Docker starts at login ("Starts with Docker: yes / no / unknown"), when the installer checked, and where to change that. With Docker Desktop it names Docker Desktop's own setting: Docker Desktop → Settings → General → **Start Docker Desktop when you sign in to your computer**. Slopify starts whenever Docker does and never changes Docker's own settings. See [Start-at-Login](Start-at-Login).
+
+## Providers
+
+"Keys stay on this machine and go only to their provider. Readiness is checked again before each run."
+
+| Control | What it does |
+|---|---|
+| Provider lists (**Text**, **Speech**, **Images**) | Every supported provider with its state and kind (**Command line**, **Built in, no key** or **API key**). Pick one to open its setup. |
+| **<Provider> API key** and **Save** | Stores a key on this computer only. Never in backups or exports. |
+| **Test** | Checks a pasted key before you save it (without storing it), or the saved key when the field is empty, with the cheapest harmless call. Nothing is billed. |
+| **System voice** | Shows the speech program found on this computer and its voices, or what to install, with **Add a system voice**. See [the system voice](Providers-and-Keys#the-system-voice). |
+| **Remove** | Deletes the saved key after you confirm with **Remove key**. |
+| **Where to get a key** | The provider's own sign-up, key and billing pages, with the permissions a key needs. |
+| **Change path** / **Executable path** / **Save path** | Where a command-line tool is. Blank finds it on PATH. Shows **Managed on host** in Docker. |
+| **Check all** | Checks every tool's sign-in, the system voice, every saved key, whether each chosen model is still offered and reachable with your key (**Model reachable**). Results show under **Health check**. |
+| **Check again** | On one provider's health row: checks that provider alone. |
+
+On a first launch you may also see the welcome message about command-line tools that were found, with **Got it** to hide it. Full details: [Providers-and-Keys](Providers-and-Keys) and [AI-CLIs](AI-CLIs).
+
+## Voices
+
+"A wrong voice ID shows up when the audio stage uses it."
+
+| Control | What it does | Rules |
+|---|---|---|
+| **Voice name** | The name you pick the voice by on Play and in Edit project. | Required, up to 200 characters. |
+| **Provider** | The speech provider the ID belongs to. | Speech providers only. |
+| **Voice ID** | The provider's own ID for the voice. For **System voice** and **Google Gemini** it is a list to pick from. | Required, up to 200 characters, unique per provider. |
+| **Languages** | Codes such as `es, de`. Play lists the voice only for projects in these languages. | Blank: asked from the provider when it can say; otherwise offered for every language. |
+| **Add voice** | Adds the voice to the table. | |
+| **Edit** (Languages cell) | Changes a voice's languages; **Save** or **Cancel**. | |
+| **Real person** | On for a voice cloned from, or made to sound like, a real person. Prepare upload then answers Yes to YouTube's AI use question for videos it narrates. | Default: off. |
+| **Remove** | Removes the voice after **Remove voice**. Projects keep the audio they made with it. | |
+
+See [Providers-and-Keys](Providers-and-Keys#add-a-voice).
+
+## Models
+
+"New models, prices and retirements, checked once a day."
+
+| Control | What it does |
+|---|---|
+| **Check now** | Checks the published catalogue and OpenRouter's live list at once. Slopify also does this at start and once a day. |
+| **Replace with published file** | Overwrites your local catalogue with the published one, dropping your edits. The previous file is kept as `models.yaml.previous`. |
+| **Catalogue file**, **Verified**, **Last checked** | Where the file is, when its prices were verified, and what the last check changed. |
+| **Switch to <model>** | Replaces one retired model choice with the suggestion shown. |
+| **Switch all** | Replaces every retired choice that has a suggestion. |
+
+Templates and schedules that pick a retired model are also flagged on their own rows, with the same **Switch to <model>**. See [Models](Models).
+
+## Playback & appearance
+
+"How narration is paced and how Slopify looks."
+
+### Silence between segments
+
+| Control | What it does | Default / range |
+|---|---|---|
+| **Silence between segments** | Seconds of quiet between the intro and the narration, and between the narration and the outro, in every new video, unless Play sets a different gap for one video. It only matters when an intro or outro is set; 0 runs them together. Type a whole number and choose **Save**. | 3 seconds, 0 to 30 |
+
+Videos already started keep their own gap. A value that is not a whole number from 0 to 30 is refused with "The silence gap is a whole number of seconds between 0 and 30." See [Intros-and-Outros](Intros-and-Outros).
+
+### Appearance
+
+| Control | What it does | Default |
+|---|---|---|
+| **Appearance** | **System**, **Dark** or **Light** colours for Slopify on this computer. System follows your operating system and changes with it. It changes at once and does not affect your videos. | System |
+
+### Level the volume for new runs
+
+| Control | What it does | Default / range |
+|---|---|---|
+| **Level the volume for new runs** | Whether a new run on Play (and a template or quick short) starts with **Level the volume** on. On evens out every narration piece and sets the finished files to a standard loudness. | On |
+| **Video volume** | How loud the long video and shorts are, in dB from the recommended -14 LUFS (the level YouTube and Spotify play at). Type dB or a percentage. Peaks stay under -1.5 dBTP. | 0 dB (-14 LUFS); -10 dB to +4 dB (32% to 158%) |
+| **Audio files volume** | How loud the audio-only WAV and an audiobook's MP3 and M4B are, in dB from the recommended -18 LUFS. Peaks stay under -3 dBTP. | 0 dB (-18 LUFS); -10 dB to +4 dB |
+
+The volume fields show only while the switch is on. A project keeps what it started with; change it there in **Edit project**. Levelling runs on this computer and makes no API calls. Changes save as you make them.
+
+## Notifications
+
+"When a run finishes, fails, or waits for you."
+
+| Control | What it does | Default |
+|---|---|---|
+| **Browser notifications** | Shows a notification from this browser while any Slopify tab is open, even in the background. Turning it on asks the browser's permission. Applies to this browser only. | Off |
+| **Send test notification** (beside the switch) | Shows a sample notification in this browser. | |
+| **Notification URL** | An address Slopify POSTs a short plain-text message to, with no tab open, for example `https://ntfy.sh/your-topic`. Each message is sent once, with a 5 second timeout. Empty turns it off. **Save** stores it; **Send test notification** sends a sample. | Empty |
+
+Messages hold the project title and what happened, never your keys. See [Notifications](Notifications).
+
+## Channel links
+
+"The links a YouTube description's {{Name}} placeholders fill from."
+
+Each channel now keeps its own links, on its **Brand** tab under **Channel links**. This section only says so, with **Open the default channel's links**. Links saved here in an earlier version still fill the default channel's descriptions until you save its Brand tab. See [Channels](Channels#channel-links) and [YouTube-Description](YouTube-Description).
+
+## YouTube Studio
+
+"The playlist upload packs name, and the Studio extension's pairing."
+
+| Control | What it does | Default / limit |
+|---|---|---|
+| **Upload pack and extension** | Explains that Slopify never uploads or publishes: **Prepare upload** on a finished project lists everything Studio asks for, and the optional extension fills Studio's upload dialog from it. | |
+| **Playlist** | The YouTube playlist upload packs name, typed exactly as it is called in Studio. Pick **Every channel (default)** or one channel first: the default is used by every channel without its own. **Save** stores it. Empty means no playlist (or, for a channel, the default). | Empty; up to 150 characters |
+| **Extension pairing token** | A secret the Slopify Studio extension needs before it may read your upload packs. **Copy** it into the extension's options and press Pair there. | |
+| **New pairing token** | Makes a fresh token, unpairs the extension until you paste the new one, and clears the uploads waiting for Studio. | |
+| **Install the Studio extension** | **Chrome, Edge, Brave** or **Firefox**, then **Download for Chrome** or **Download for Firefox**, with the three install steps. | |
+
+See [Studio-Extension](Studio-Extension) and [Publishing-to-YouTube](Publishing-to-YouTube).
+
+## Backup & storage
+
+"Export everything, import a backup, and see what uses disk space."
+
+### Your files
+
+| Control | What it does |
+|---|---|
+| **Your files** | Where your projects, automatic backups and exports live; new installs use `Documents/Slopify`. The database, settings, keys and logs stay in Slopify's hidden data folder. |
+| **Open folder** | Opens the folder on this computer. |
+| **Choose another folder** / **New folder** / **Move here** | Moves your files to another folder. Slopify copies every file, checks each copy, then switches, and keeps the old folder until you delete it. The new folder must be empty or not exist yet. It cannot start while a project is being made. |
+
+In Docker, this shows the command to run on the computer running Docker, with **Copy command**. See [Where-Your-Files-Live](Where-Your-Files-Live).
+
+### Export and import
+
+| Control | What it does |
+|---|---|
+| **Export everything** | Downloads one `.tar` file with every project (files and history), your library, templates, schedules, Play drafts, fonts, settings and usage. Never provider keys. Your browser's downloads show its progress; keep Slopify running until it finishes. |
+| **Import a backup** | Adds a `.tar` from Export everything (or a `.zip` from an older version's Export backup, up to 100 MB) to this install. It replaces nothing: projects already here are skipped, taken names arrive as "(imported)" and schedules arrive paused. Running projects must finish or pause first. A summary lists what was added and skipped. |
+| **Clean orphan files** | Deletes files in the projects folder that no project records any more, and uploaded files nothing uses. Your projects, outputs and library are never touched. Slopify also does this at each start. |
+
+After importing, enter your keys again in Settings → Providers. You can also run **Export everything** from `Ctrl+K`. See [Backups](Backups).
+
+### Disk space
+
+| Control | What it does |
+|---|---|
+| **Disk space** | What Slopify stores: the total, project files, staged uploads, and deleted projects still in the trash (freed when the trash removes them after 30 days, or with **Delete now**). |
+| Storage by project | Each project's size, split into outputs and working files, largest first. A finished project's page offers the same on its own (**Free space**, see [Project Page](Project-Page#free-space)). |
+| **Keep outputs only** | On a finished project, deletes the working files (images, narration parts, subtitle timing, render settings) and keeps the video, shorts, thumbnail, article, description, document and your uploads. You confirm first. Changing the project later makes those files again, which takes time and provider credits. |
+
+### Sample projects
+
+| Control | What it does |
+|---|---|
+| **Sample projects** | Lists the three samples that come with Slopify (a narrated video, an audiobook and a podcast), with **Open** for each one in your projects. |
+| **Restore samples** | Adds back any that were deleted and puts the others back as they shipped. Your own copies of them are not touched. |
+
+## Backups
+
+"A daily copy of everything, in a folder you choose."
+
+| Control | What it does | Default / range |
+|---|---|---|
+| **Back up now** | Writes a backup at once, whether or not the daily backup is on. Also in `Ctrl+K`. | |
+| **Back up automatically** | Turns the daily backup on or off. | Off |
+| **Time of day** | When the daily backup runs, in this browser's time zone. | 03:00 |
+| **Keep last** | How many of Slopify's own backups stay; older ones are deleted. | 5, from 1 to 30 |
+| **Folder** | Where backups go. Empty uses the Backups folder beside your projects. | Empty |
+| **Save** | Saves the four settings above. | |
+
+Each backup is the same file Export everything makes and can be many gigabytes. See [Backups](Backups).
+
+## Trash
+
+"Deleted projects, prompts, templates and schedules, kept for 30 days."
+
+| Control | What it does |
+|---|---|
+| **Restore** | Puts an item back. If its name was taken meanwhile it comes back renamed, and a schedule comes back paused. |
+| **Delete now** | Removes an item for good at once, freeing its space. You confirm first. |
+
+Deleted projects, prompts, intros and outros, templates and schedules stay 30 days, then are removed for good. See [Trash](Trash).
+
+## Usage
+
+"This machine only. The same counters, anonymised, feed slopify.stream."
+
+Shows **Videos made**, **Hours of audio**, **Images made**, **Tokens used** and **Projects**, then **Tokens by stage** by provider and model, and the machine ID and version. There are no controls. Money figures are on each project's **Run cost** tab and Home's **This week**. See [Costs-and-Run-Cost](Costs-and-Run-Cost).
+
+## Patch notes
+
+"What changed in each version of Slopify."
+
+| Control | What it does |
+|---|---|
+| **Latest version** | The newest notes, open. |
+| **Earlier versions** | Older versions, each opened with **Read**. |
+
+The notes ship with the app, so they work offline. After an update, the new version's notes open by themselves once; a fresh install skips that. On a major update the What's new tour shows instead and links here. `Ctrl+K` → **Show patch notes** opens this section. See [Updating-and-Patch-Notes](Updating-and-Patch-Notes).
+
+## About
+
+"Free and open source, running on your machine with your own keys."
+
+| Control | What it does |
+|---|---|
+| **Updates** | Points to the circular-arrows button (at the foot of the sidebar), which checks for a newer Slopify and installs it. A dot on it means an update is ready. If a video is being made, the update waits until it finishes, and you can cancel it meanwhile. Slopify restarts itself and the page reconnects. |
+| **What's new in this version** | Opens the patch notes for the version you are running. When this version has no notes of its own, it opens the newest ones. |
+| Links | GitHub (code, issues, releases), Patreon, Buy Me a Coffee, and "How I run a channel with it". |
+
+Slopify is made by Gent Bajko under the Apache License 2.0. See [Updating-and-Patch-Notes](Updating-and-Patch-Notes).
+
+## Related pages
+
+- [Providers-and-Keys](Providers-and-Keys)
+- [AI-CLIs](AI-CLIs)
+- [Models](Models)
+- [Costs-and-Run-Cost](Costs-and-Run-Cost)
+- [Keyboard-Shortcuts-and-Command-Palette](Keyboard-Shortcuts-and-Command-Palette)
+- [Where-Your-Files-Live](Where-Your-Files-Live)
+- [Backups](Backups)
+- [Troubleshooting](Troubleshooting)