@gentbajko/slopify 3.0.0 → 3.0.1

package/dist/tutorials/Troubleshooting.md

@@ -0,0 +1,149 @@
+# Troubleshooting
+
+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.
+
+## 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.
+
+### 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.
+
+## Provider 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. |
+| "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. |
+
+Keys and how to get them: [Providers and Keys](Providers-and-Keys).
+
+## AI CLIs (Claude Code, Codex, Gemini)
+
+| Message (or part of it) | Fix |
+| --- | --- |
+| "The *CLI* is not signed in, or its sign-in has expired." | Press **Copy sign-in command** on the project (or on Home's Needs you), run it in a terminal on the computer running Slopify (`claude auth login`, `codex login`, or `gemini`), sign in, then press **Check again**: once the CLI answers that it is signed in, the step runs again by itself. See [Recovery and Retries](Recovery-and-Retries#sign-a-cli-in-again). |
+| "Your Codex plan's usage limit is used up ... Slopify waits for it to reset and then carries on by itself." (also Claude and Gemini) | 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**. |
+| Gemini CLI shows "Slopify could not tell from the Gemini CLI's files (~/.gemini/settings.json) whether it is signed in." | Run `gemini` in a terminal once and sign in (Login with Google), or set `GEMINI_API_KEY`, then press **Check again**. |
+
+See [AI CLIs](AI-CLIs).
+
+## Provider 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**. |
+| Rate limit messages (429) | Nothing to do: Slopify waits and tries again by itself. |
+
+## ffmpeg, captions and rendering
+
+Slopify ships its own ffmpeg; you do not need to install one. In Docker it is inside the image.
+
+| Message (or part of it) | Fix |
+| --- | --- |
+| "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 95 MB caption model downloads on first use. Check your connection and try again. `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. |
+
+With **Language** set to one without word timing, captions and cuts work differently; see [Other Languages](Other-Languages).
+
+## Starting Slopify
+
+| Message | Fix |
+| --- | --- |
+| "Port 6969 is already in use by another program (maybe another Slopify)." | Stop that program, or start on another port: `npx @gentbajko/slopify --port 7070`. |
+| "Slopify is not allowed to use port ... (ports below 1024 need administrator rights)" | Use a port above 1024 with `--port`. |
+| "Slopify can't listen on ... because that address doesn't belong to this machine." | Leave out `--host` (and `SLOPIFY_HOST`) to use `127.0.0.1`. |
+| "Slopify can't write to its data folder ..." | Make sure your user owns the folder, or choose another with `--data-dir`. |
+| "The disk is full ... Free up some space and start Slopify again." | Free disk space. |
+| npm refuses to install because of the Node version | Slopify needs Node 26 or newer. |
+
+See [Install](Install) for the command-line options.
+
+## In the browser
+
+| Message | Fix |
+| --- | --- |
+| "Slopify isn't responding. …" | Slopify stopped, is restarting or is being updated. The message names the fix for your install: for a normal install, wait a moment or start it again with `npx @gentbajko/slopify`; in Docker, check that its container is running (Docker Desktop, or `docker ps`) and start it. Then reload. |
+| "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." | The project was saved elsewhere (another tab, a remake). Press **Reload current revision and discard my draft**, or keep your draft and save it. |
+
+## 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. |
+
+See [Where Your Files Live](Where-Your-Files-Live).
+
+## Docker and native differences
+
+| Topic | Native install | Docker |
+| --- | --- | --- |
+| Where it runs | Any system with Node 26 or newer | The installer is Linux only; Docker Desktop and remote Docker daemons are refused, and the installer must not be run with sudo |
+| Project files | `Documents/Slopify` for new installs (Settings → **Your files**); the database, settings and keys stay in the hidden data folder (`~/.slopify` by default, `--data-dir`) | `<Documents>/Slopify/Projects` on the host for new installs (`~/Slopify/Projects` on one from before 3.0); the database and keys stay in the `slopify-data` volume |
+| 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. |
+
+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).
+
+## A run seems stuck
+
+| What you see | What it means |
+| --- | --- |
+| **Queued** | Other videos in the batch queue go first. The Calendar's **Batch queue** shows 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 you** | A checkpoint is holding the run. Press **Approve ...**. |
+| 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. |
+| **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.
+- 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)
+- [AI CLIs](AI-CLIs)
+- [Docker](Docker)
+- [Install](Install)
+- [Where Your Files Live](Where-Your-Files-Live)

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

@@ -0,0 +1,113 @@
+# Uninstalling and Moving
+
+How to take Slopify off a computer, and how to move your projects between a normal install and Docker, or to another computer. Slopify has no uninstall command: removing it means removing the few things listed here. Moving always goes through a backup archive, which carries everything except your provider keys.
+
+**Where to find it:** Settings → **Backup & storage** (**Export everything**, **Import a backup**) and a terminal.
+
+## 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.
+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.
+
+## Remove a normal install
+
+1. Stop Slopify: press `Ctrl+C` in the terminal it runs in (or close its minimised window on Windows).
+2. If you installed it with npm, run `npm uninstall -g @gentbajko/slopify`. If you only used `npx`, there is nothing installed globally; npm's cache holds a copy it manages itself.
+3. Delete Slopify's data folder: `~/.slopify` (on Windows `%USERPROFILE%\.slopify`), or the folder you gave with `--data-dir` / `SLOPIFY_DATA_DIR`. This removes the database, your saved keys, logs, caption models and any versions installed by in-app updates.
+4. Delete your files folder if you don't want your projects any more: `Documents/Slopify` on a new install. Settings → **Backup & storage** → **Your files** shows exactly where it is (check before you uninstall). On an install from before 3.0, the projects are inside the data folder and went with step 3.
+5. If you left the start-at-login switch on, remove the entry by hand: `~/.config/autostart/slopify.desktop` on Linux, `~/Library/LaunchAgents/stream.slopify.app.plist` on macOS, or the `Slopify` value under `HKCU\Software\Microsoft\Windows\CurrentVersion\Run` on Windows (Task Manager → Startup apps shows it).
+
+## Remove a Docker install
+
+Run these as your normal user on the computer running Docker.
+
+1. If you use the host CLI bridge, stop and disable it:
+
+   ```sh
+   systemctl --user disable --now slopify-cli-bridge.service
+   ```
+
+2. Stop and remove the container from the folder the installer set up:
+
+   ```sh
+   cd ~/.local/share/slopify/docker/slopify
+   docker compose down
+   ```
+
+3. Delete the data volume (database, keys, settings, logs). The installer declares it external, so `docker compose down` never deletes it; you have to do it yourself:
+
+   ```sh
+   docker volume rm slopify-data
+   ```
+
+4. Delete any recovery volume left by the last update. `docker volume ls` lists it as `slopify-data-recovery-<id>`; remove it with `docker volume rm`.
+5. Remove the image: `docker image ls ghcr.io/gentbajko/slopify` lists it; remove it with `docker image rm`.
+6. Delete the installer's folders: `~/.local/share/slopify/` (the compose file, `install.json` and the host CLI helper) and, if you used the bridge, its unit file `~/.config/systemd/user/slopify-cli-bridge.service`.
+7. Delete your Projects and Backups folders if you don't want them any more: `Documents/Slopify` on a new install, `~/Slopify/Projects` on an install from before 3.0.
+
+If you used a different `SLOPIFY_DOCKER_NAME` or `SLOPIFY_DOCKER_VOLUME`, use those names instead of `slopify` and `slopify-data`.
+
+The installer turned on user lingering for the bridge (so your user services run at boot). It leaves that setting as it is when you remove Slopify; change it with `loginctl` only if you know nothing else of yours needs it.
+
+## Move from Docker to a normal install
+
+1. In the Docker Slopify, let running work finish, then open Settings → **Backup & storage** → **Export everything** and save the `.tar` file.
+2. Stop the Docker install so the port is free: `docker stop slopify` (or start the new one on another port with `--port 7070`).
+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**.
+7. Resume your schedules on the Schedules screen. See [Schedules](Schedules).
+8. Once everything opens fine, remove the Docker install as above.
+
+## Move from a normal install to Docker
+
+1. In the normal Slopify, let running work finish and use **Export everything**.
+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.
+6. Remove the old install when you are sure.
+
+## Move to another computer
+
+The same way: **Export everything** on the old computer, install Slopify on the new one, **Import a backup** there, then enter your keys and resume your schedules. If both computers keep running, leave the schedules paused on one of them so they don't both make the same videos.
+
+## How an import treats what's already there
+
+An import adds and never replaces:
+
+| Item | What happens |
+| --- | --- |
+| Projects already on this install | Skipped. |
+| Prompts, templates and others whose name is taken | Added as "(imported)". |
+| 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. |
+
+Running projects must finish or pause before an import. See [Backups](Backups) for what an archive carries in full.
+
+## Move your files without moving the install
+
+To put your project files on another disk or in Documents while keeping the same install, you don't need to export: use **Move to Documents/Slopify** or **Choose another folder** in Settings → **Backup & storage**, or `--projects-dir` for Docker. See [Where Your Files Live](Where-Your-Files-Live).
+
+## Tips
+
+- An export can be many gigabytes, because it holds every video. Check you have the space, and keep Slopify running until the browser's download finishes.
+- **Keep outputs only** (Settings → Backup & storage → Disk space) makes finished projects smaller before you export, at the cost of remaking working files if you edit them later.
+- Export and import is the documented way to move between installs. Copying a data folder or a Docker volume by hand is not covered here.
+
+## Related pages
+
+- [Backups](Backups)
+- [Where Your Files Live](Where-Your-Files-Live)
+- [Install](Install)
+- [Docker](Docker)
+- [Start at Login](Start-at-Login)
+- [Providers and Keys](Providers-and-Keys)
+- [Schedules](Schedules)
+- [Trash](Trash)

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

@@ -0,0 +1,120 @@
+# Updating and Patch Notes
+
+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**.
+
+## The updates button
+
+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.
+
+| What you see | Meaning | Click 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. |
+
+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.
+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**.
+
+## Update from the terminal
+
+Run:
+
+```sh
+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:
+
+- `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.
+- `Updating Slopify X to Y...` then `Slopify Y is running at http://127.0.0.1:6969`.
+
+Slopify has to be running for this. If it isn't, the command says so: start it and run `update` again, adding `--port <number>` if it runs on another port. To just start the newest version, run `npx @gentbajko/slopify@latest`.
+
+If you have a Docker install on your account, the same command updates that instead. See [Docker](Docker#update-the-docker-install).
+
+## What an update does
+
+For a normal (non-Docker) install:
+
+1. **Waits** until no stage or edit is running.
+2. **Installs** the new version with npm into `<data folder>/updates/<version>`. If this fails, the running Slopify is left alone.
+3. **Backs up the database** to `<data folder>/updates/before-<version>-….db`.
+4. **Starts the new version** and waits up to 60 seconds for it to answer.
+5. **On success**, removes old update files. It keeps the new version, the previous version and the latest database backup.
+6. **If the new version doesn't start**, it stops it, copies the database back from the backup and restarts the previous version. The reason is written to `logs/updates.log` in the data folder.
+
+Later starts of Slopify, including an older `npx` or a global `slopify` command, hand over to the newest version installed in the data folder. That is how an in-app update sticks for both npx and npm installs.
+
+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
+
+The button's label says why:
+
+| Message | What to do |
+| --- | --- |
+| Slopify in Docker is updated from the terminal: `npx @gentbajko/slopify@latest update`. | Run that on the computer running Docker. |
+| 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. |
+
+If an update didn't finish, Slopify keeps or puts back the previous version. `logs/updates.log` in the data folder says why.
+
+## After an update
+
+### Patch notes open once
+
+After an update, the new version's notes open by themselves once, in a drawer titled **What's new in X**:
+
+- **See all patch notes** opens Settings → **Patch notes**.
+- **Close notes** (or the close button) records them as seen. They don't open again for that version.
+
+They open only for a version that has notes of its own, and never on a fresh install. They wait for other windows first: the usage stats notice, the tutorial and the What's new tour.
+
+### What's new tour on a major update
+
+After an update to a new major version (for example 2.x to 3.0), the first launch opens a short **What's new in 3.0** tour instead: a drawer on the right with one step per feature and an **Open …** button to its screen. The drawer doesn't block the page, so you can follow a link while it stays open.
+
+- **Back** and **Next** move between steps; **Finish tour** on the last one.
+- **Close tour**, the close button or `Esc` record it as seen. It doesn't come back until the next major version.
+- 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.
+
+## Read the patch notes
+
+1. Open Settings → **Patch notes**, or press `Ctrl+K` and choose **Show patch notes**.
+2. The newest notes are open, with contents, search and copy.
+3. Older versions are folded under **Earlier versions**. Press **Read** on one to open it. Your browser's Back button returns to the one before.
+
+The notes ship with the app, so they work offline.
+
+To open the notes for the version you are running, go to Settings → **About** and press **What's new in this version**. When this version has no notes of its own, it opens the newest ones.
+
+## 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.
+- Updating doesn't touch your projects folder. For extra safety before a big update, use **Export everything** or turn on [Backups](Backups).
+
+## Related pages
+
+- [Install](Install)
+- [Docker](Docker)
+- [Start at Login](Start-at-Login)
+- [Backups](Backups)
+- [Troubleshooting](Troubleshooting)
+- [Settings Reference](Settings-Reference)

package/dist/tutorials/Video-Editing.md

@@ -0,0 +1,135 @@
+# Video Editing
+
+These settings decide how the finished video looks and sounds: how long each image stays, where the cuts fall, how images move and hand over, the Look, chapter cards, animated images, ambient sound and captions. All of it except animated images is done on your computer with ffmpeg, so it costs render time, not API calls.
+
+**Where to find it:** a project → **Edit settings** → **Inputs** (**Timing**, **Cuts and look**, **Ambient sound**) and **Subtitles**. On a new run the same controls are on Play → **Video and style** (see [Play Video and Style](Play-Video-and-Style)).
+
+## How the video is put together
+
+Slopify plans the whole video as an edit list: which image or clip plays, for how long, how it moves, how it hands over to the next, and the effects on top. The renderer reads only that list, so the same project renders the same video every time. The video is always exactly as long as its narration plus the silence you set.
+
+## Timing
+
+| Option | What it does | Default / range |
+| --- | --- | --- |
+| **Silence gap (seconds)** | Quiet between the intro and the narration, and between the narration and the outro. Only matters when an intro or outro is set. | Settings value (3 s unless changed); 0 to 30 |
+| **Silence at start and end (seconds)** | Quiet before the narration starts and after it ends. | 2; 0 to 30 |
+| **Seconds per image** | How long each image stays on screen. With cuts that follow the narration, it is the target and a cut waits for a sentence end. When images run out they start again. | 15; 1 to 600 whole seconds |
+| **Zoom (%)** | How far each image zooms in or out over its time on screen. 0 keeps zoom motions still. | 22.5; 0 to 50 in 0.5 steps |
+| **Motion** | How each image moves: **Zoom in and out**, **Pan across**, **Mix of both** (by turns) or **Still**. | Zoom in and out |
+
+Motion takes turns so a long video stays watchable. Zoom goes in, out, in. Pan goes across one way, back, down, back up. Mix of both alternates zoom and pan, each keeping its own order. A pan always travels at least 10% of the frame, so pans still move with Zoom at 0.
+
+## Cuts
+
+**Cuts** decides where one image ends and the next begins.
+
+| Option | What it does |
+| --- | --- |
+| **Every N seconds** | Holds each image for **Seconds per image**. |
+| **Follow the narration** | Cuts in the pause after a sentence, as close to Seconds per image as the sentences allow (never under 40% of it), and starts a new image at every chapter. |
+
+New projects default to **Follow the narration**. It needs word timing, so it works in English and the languages that have it; in other languages the picker is fixed to Every N seconds and a note says why. See [Other Languages](Other-Languages).
+
+## The Look
+
+**Look** is a folding row under Cuts. Its summary line lists what is on, or "Plain cuts, no effects".
+
+| Option | What it does | Default / choices |
+| --- | --- | --- |
+| **Transition** | How one image hands over to the next: **Cut**, **Crossfade**, **Fade through black**, **Slide** or **Wipe**. The change is centred on the cut, so the video stays exactly as long as its narration. | Cut |
+| **Transition length** | How long the transition takes (ignored for Cut). | 0.6 s; 0.2, 0.4, 0.6, 0.8, 1, 1.2, 1.5 or 2 s |
+| **Colour grade** | A colour treatment over the whole video: **Warm fantasy**, **Cold**, **Desaturated** or **Sepia**. | None |
+| **Vignette** | Darkens the corners to draw the eye to the middle: **Subtle** or **Strong**. | Off |
+| **Film grain** | Moving film grain over the whole picture: **Subtle** or **Strong**. | Off |
+| **Atmosphere** | An overlay Slopify draws itself: **Embers** (rising), **Dust** (drifting) or **Fog** (low, along the bottom). No footage is downloaded. | None |
+| **Chapter cards** | Shows each chapter's title in the middle of the picture for 2.5 seconds as the chapter starts, in the caption font. Chapters come from the YouTube description when that step runs, otherwise from the article's headings. Needs narration. | Off |
+| **Animate images** | Turns some images into 5-second moving clips with an image-to-video model on your image provider (fal.ai or Replicate). **Chapter openers** animates the first image of each chapter (needs narration); **Every Nth image** animates every 2nd to 10th image (**Animate every how many images**). Pick the model in **Image-to-video model**. | Off |
+
+Every Look option except **Animate images** is applied while the video renders, with no API cost. Each animated clip is one paid call, shown in the estimate. An image that cannot be animated stays still, and the Video section lists it under **Render notes**.
+
+### Set up the Look
+
+1. Open the project → **Edit settings** → **Inputs**.
+2. Under **Cuts and look**, click **Look** to open it.
+3. Pick a transition, grade, vignette, grain, atmosphere, chapter cards or animation.
+4. Press **Save changes**.
+5. Press the next action, **Remake the outdated video**, or review it in **Choose what to remake**.
+
+Changing the Look outdates the video; narration and images are kept.
+
+## Video clips in place of images
+
+In **Edit project → Images**, **Add a video clip** puts your own clip into the image order. It plays muted for as long as an image would be shown: trimmed, slowed (to half speed at most) or looped to fit. See [Editing a Project](Editing-a-Project#edit-images).
+
+If the clips you uploaded are real filmed footage, turn on **Real footage** in Prepare upload so YouTube's AI-use answer is right. See [Publishing to YouTube](Publishing-to-YouTube).
+
+## Ambient sound
+
+A quiet bed under the whole narration of the long video. It dips while the narrator speaks. Costs no API calls. Shorts never get it. Changing it remakes only the video.
+
+**Where to find it:** a project → **Edit settings** → **Inputs** → **Ambient sound** (shown when the project has narration and video).
+
+| Option | What it does | Default / range |
+| --- | --- | --- |
+| **Ambient sound** | **Rain**, **Fireplace** or **Wind**, made on your computer, or **None**. **My own file** stays offered while the project has an uploaded bed; a new file is chosen on Play. | None, or the channel's bed |
+| **Level (dB)** | How loud it plays under the voice, from -40 (barely there) to -6 (close to the voice). Whole numbers only. | -18 |
+| **Fade in (seconds)** | How long it takes to rise from silence at the start. | 3; 0 to 30 in 0.5 steps |
+| **Tail after the narration (seconds)** | How long it keeps playing, fading out, after the narration ends. A tail longer than the silence at the end makes the video that much longer. | 6; 0 to 30 in 0.5 steps |
+
+With **Level the volume** on, the bed is mixed and ducked first, then the whole mix is mastered. See [Editing a Project](Editing-a-Project#pauses-and-volume).
+
+## Subtitles
+
+**Where to find it:** a project → **Edit settings** → **Subtitles**.
+
+| Option | What it does | Default / range |
+| --- | --- | --- |
+| **Subtitles** | **Off** makes none. **Subtitle files (.srt + .vtt)** gives you files to upload beside the video. **Burn into video + files** draws the captions into the picture and also makes the files; it needs Video on. | Off |
+| **Subtitle font** | The typeface of burned-in captions and chapter cards. Pick a bundled font (**Default font · bundled**) or upload one with **Upload font (.ttf or .otf)**; uploaded fonts stay available to every project. | The bundled font |
+| **Subtitle font size** | How big burned-in captions are. Larger is easier to read on phones but covers more of the picture. | 48; 16 to 120 |
+| **Subtitle position** | Where burned-in captions sit: **Top**, **Upper-middle**, **Center**, **Lower-middle** or **Bottom**. Move them up when pictures have detail near the bottom. | Bottom |
+
+Captions are timed from your narration on your computer, with no paid API. The first use downloads a speech model of about 95 MB. Subtitle files carry no font, size or position, because players style them. Changing the font, size or position remakes only the video.
+
+Subtitles need narration: with Audio off the section says "Turn Audio on to add subtitles." With Video off (an audio export), only subtitle files are offered.
+
+To fix a misheard word or move a caption, edit the captions themselves: see [Editing a Project](Editing-a-Project#edit-captions).
+
+## Style preview
+
+**Style preview** (under Subtitles in Edit project, and in Play's right rail) renders six seconds of video with the real renderer, at a small size: your format, captions, Look, transition, motion and a chapter card when chapter cards are on.
+
+- It is drawn on the project's establishing image or a cast picture when there is one (the line under it says "Drawn on ..."), otherwise on three plain stills.
+- It renders again by itself a moment after you change a setting. **Render again** forces a fresh one.
+- Captions show in the preview only when they are burned in.
+- The sound is silence. It costs no API calls, only a few seconds of your computer's time.
+
+If it says "Fix the caption settings to render the preview", correct the subtitle fields first.
+
+## What a change remakes
+
+| You change | What is made again |
+| --- | --- |
+| Seconds per image, zoom, motion, cuts, the Look (except Animate images), subtitles style, ambient sound | The video only |
+| Animate images | The animated clips (paid) and the video |
+| Subtitle mode | Subtitle files and the video |
+| Caption text or timing | Subtitle files and the video |
+| Pauses between sentences or paragraphs | The narration join and timing, captions, the video, and (when on) the YouTube description and the shorts' pick |
+
+The rebuild review lists exactly what will be made before anything runs. See [Editing a Project](Editing-a-Project#choose-what-to-remake).
+
+## Tips
+
+- Try a Look on the style preview first; it costs nothing.
+- A crossfade longer than about a second eats into short shots. Keep transitions short when Seconds per image is low.
+- Captions burned into the picture cannot be turned off by viewers. Subtitle files let YouTube viewers switch them.
+
+## Related pages
+
+- [Play Video and Style](Play-Video-and-Style)
+- [Editing a Project](Editing-a-Project)
+- [Project Page](Project-Page)
+- [Shorts](Shorts)
+- [Channels](Channels)
+- [Other Languages](Other-Languages)