@gentbajko/slopify 3.0.0 → 3.0.1

package/dist/tutorials/Home-and-Projects.md

@@ -0,0 +1,174 @@
+# Home and Projects
+
+Home is Slopify's front page: what needs you, what is running, what is coming up, what is ready to upload and what this week cost, on one screen. Projects is the full list of every run you ever started, with search and filters.
+
+**Where to find it:** the sidebar → **Home** (the Slopify logo also goes there) and **Projects**. On a phone, the bottom bar.
+
+## Finding your way around
+
+Every page shares the same frame: the sidebar on the left and the page beside it. On a computer there is no top bar; everything lives in the sidebar.
+
+### The sidebar
+
+From top to bottom:
+
+| Part | What it has |
+| --- | --- |
+| Logo | The Slopify play logo and name, with the version you are running beside it (for example `v3.0.0`). Click it to go Home. |
+| **Search or run a command** | Opens the command palette (`Ctrl+K`). |
+| Destinations | **Home**, **Projects**, **Calendar** (also lit on Schedules), **Channels**, **Library** (Prompts, Intros & Outros, Templates, Document themes, Narration aliases), **Settings** (also lit on Usage). |
+| **N running** | Shown while runs are going. It links to Running now on Home. |
+| **Channel** | The channel picker (see below). |
+| **New video** | Opens Play (`C` from anywhere). |
+| Links | **GitHub**, **Patreon** and **Buy Me a Coffee**, each opening in a new tab. |
+| Foot | "Free. Your keys, your machine.", the updates button (circular arrows, see [Updating and Patch Notes](Updating-and-Patch-Notes)) and the tutorial button (question mark, **Start interactive tutorial**). |
+
+### On a phone
+
+Below 768 pixels wide the sidebar is hidden. A slim bar at the top holds the logo, the search button, the running count, the GitHub, Patreon and Buy Me a Coffee icons, the updates button and the tutorial button. A bottom bar has five destinations: Home, Projects, Calendar, Library and Settings. Channels is reachable from the command palette, and the Channel picker sits at the top of Home.
+
+### Rows open with one press
+
+In every list, a press anywhere on a row or tile opens or picks it, not only on its name: projects, Home items, calendar entries, channels, schedules, Library lists, samples, saved drafts and media tiles. The buttons on a row still do their own thing.
+
+### The command palette
+
+Press `Ctrl+K`, or click **Search or run a command**, to jump anywhere or run an action by typing. The **Go to** group has **Open home**, **Open projects**, **Open calendar**, **Open schedules**, **Open channels**, **Open library**, **Open settings**, **Open usage and costs** and **Show patch notes**. **New video** opens Play. The **Channel** group has **Show all channels** and **Switch to <channel>**. See [Keyboard Shortcuts and Command Palette](Keyboard-Shortcuts-and-Command-Palette).
+
+### The Channel picker
+
+The **Channel** picker near the foot of the sidebar (at the top of Home on a phone) shows Home and the other screens for one channel, or for **All channels**. It only filters what you see: projects, schedules and costs of other channels keep running. Slopify remembers your choice in this browser. See [Channels](Channels).
+
+## Home
+
+**Where to find it:** the sidebar → **Home**.
+
+The page title is the channel you picked (or **Home**), under today's date. At the top right are **Open calendar** and **New video**.
+
+On a fresh install, Home sends you to the first-run screen once. See [First Launch and Welcome](First-Launch-and-Welcome).
+
+### Needs you
+
+Things that don't move on until you act:
+
+| Item | Status | Button |
+| --- | --- | --- |
+| A run held at a review before a step | **Waiting for you · review before the narration** (or the images, or the video) | **Approve the article and record**, **Approve and draw the images** or **Approve and render**. Approving here lets the run continue. Open the project to look first. |
+| A run whose next step is held another way | **Waiting for you** | **Open to continue** |
+| A run you paused | **Paused** | **Open to continue** |
+| Topics a schedule suggested | **N new topics** | **Review topics**, on the calendar: queue the ones you want and reject the rest. |
+| A failed run | **Failed · <step>**, with a short reason | The fix to try: a button to Settings → Providers or Storage when that is the fix, otherwise **Open to retry**. |
+| A run that failed because a CLI is signed out | **Failed · <step>** | **Copy sign-in command** copies the command (`claude auth login`, `codex login` or `gemini`). Run it in a terminal on the computer running Slopify, then **Open to retry** and press **Check again** on the project. |
+
+Up to 4 failed runs show here. Only the first item's button is lime; the rest are plain buttons. The heading says how many things are waiting, or **Nothing is waiting for a decision**. See [Reviews and Checkpoints](Reviews-and-Checkpoints), [Schedules](Schedules) and [Recovery and Retries](Recovery-and-Retries).
+
+### Running now
+
+Videos being made or paused, up to 3. Each shows the step it is on, how long each step has taken, the running step's time left (for example `2 of 8 · about 4 min left`), the last few images as they land (with a tile for the one being drawn) and **Images N of M** while drawing. A run waiting for a CLI plan says so instead of the step, for example **Waiting for Codex limits (resets at 14:00)**. Open one to follow it live, pause it or cancel it. With nothing running it says **Start the next video**.
+
+- With more than three running, **See all N running** opens Projects filtered to running.
+- Queued runs show as one line under them, for example "Queued, waiting to start (2): Hypatia, Cleopatra", with **See queued** (Projects filtered to queued).
+
+Time left comes from the step's own pace once it has counted something, otherwise from how long the same kind of step took in your finished runs. Past that it says **taking longer than usual**, and with nothing to go by **time left unknown**.
+
+### Coming up
+
+The schedule runs due in the next 7 days, with the template and topic each will use, up to 6. Paused schedules show too. **Calendar** opens the calendar to plan or move runs. With none it says **No scheduled runs this week. Plan some on the calendar.** See [Calendar](Calendar).
+
+### Ready to upload
+
+Finished videos you have not marked uploaded, up to 4. The bundled samples never show here.
+
+- **Prepare upload** lists everything YouTube Studio asks for, with Copy buttons. Slopify never uploads for you. See [Publishing to YouTube](Publishing-to-YouTube).
+- **Mark uploaded** takes the video off this list. Projects still has it.
+
+### This week
+
+Since Monday, for the picked channel:
+
+| Figure | Meaning |
+| --- | --- |
+| **videos made** | Videos finished since Monday. |
+| **spent** | What their provider calls cost. Calls billed to a command-line plan cost nothing per call; **~$X via API** says what they would have cost with API keys. Calls with no known price are counted separately (**N calls without a price**). |
+| **weekly <plan> limit** | How much of each command-line plan's weekly limit is used, from the tool's last reading. The bar turns amber at 80%. |
+
+See [Costs and Run Cost](Costs-and-Run-Cost).
+
+## Projects
+
+**Where to find it:** the sidebar → **Projects**.
+
+Every run ever started, newest first, for the channel picked in the sidebar. The heading says how many projects there are and for which channel. **New video** opens Play.
+
+### Search and filter
+
+1. Type in **Search projects** to match titles.
+2. Pick a filter under **Show**:
+
+| Filter | Shows |
+| --- | --- |
+| **All** | Everything. |
+| **Running** | Running and paused projects. |
+| **Queued** | Projects waiting for their turn in the video queue. |
+| **Needs you** | Projects waiting at a review or held step. |
+| **Ready to upload** | Finished videos not marked uploaded. |
+| **Failed** | Failed projects and those **Done with problems**. |
+
+The filter is part of the address, so a link can open Projects on it: `/projects?show=running`, `queued`, `waiting` (Needs you), `ready` or `failed`. Press `/` to jump to the search box. The command palette has shortcuts: **Show projects that need you**, **Show videos ready to upload** and **Show failed projects**.
+
+On a wide screen, **At a glance** beside the list counts the projects under each filter.
+
+If nothing matches, the list says **No project matches. Clear the search or pick All.** If the picked channel has no projects, pick **All channels** in the sidebar.
+
+### What each row shows
+
+- The title, with a **Sample** badge on the bundled samples. A press anywhere on the row opens the project.
+- For an audiobook that is a chapter of a book, **Book · Chapter N**.
+- What it was made of and when: the article prompt and format, for example `Documentary dossier · 16:9 · started …`.
+- A progress bar with **N% done** while it runs.
+- Its state:
+
+| State | Meaning |
+| --- | --- |
+| **Running** | A step is being made. A run waiting for a CLI plan says **Waiting for Codex limits (resets at 14:00)** instead. |
+| **Paused** | Paused by you; nothing runs until you resume. |
+| **Queued** | Waiting for its turn in the video queue. |
+| **Waiting for you** | Held at a review or checkpoint. |
+| **Done** | Finished. |
+| **Done with problems** | Finished, but part of it failed. |
+| **Failed** | Stopped with an error. |
+| **Canceled** | You cancelled it. |
+
+- **Mark uploaded** on a finished video; once marked, an **Uploaded** badge with **Undo**.
+- The delete button (bin icon).
+
+### Delete a project
+
+1. Press the bin icon on its row. While the project is running it is disabled: cancel the run first.
+2. Confirm with **Delete project** (or **Keep it** to back out).
+3. The project goes to the trash for 30 days. Restore it or delete it for good in Settings → **Trash**. See [Trash](Trash).
+
+### The video queue
+
+Videos started together (a batch from Play, for example) run one at a time. The queue itself is on the Calendar, under **Batch queue**, numbered in the order they run (see [Calendar](Calendar#the-batch-queue)); Projects only links to it (**Video queue** → **Open calendar**) and has the **Queued** filter. Pausing a project holds the queue; when one fails or is cancelled, the next one starts. The project page has the same list behind a **Queue · N** button in its right rail. See [Templates](Templates) and [Schedules](Schedules) for batches.
+
+### When there are no projects
+
+Projects shows **No projects yet** with **Make your first video** (opens Play), and an invitation to the interactive tutorial with **Start tutorial**.
+
+## Tips
+
+- The sidebar's **N running** link jumps straight to Running now on Home.
+- Home and Projects follow the Channel picker. If a project seems missing, switch to **All channels**.
+- Updates wait for running work. See [Updating and Patch Notes](Updating-and-Patch-Notes).
+
+## Related pages
+
+- [Project Page](Project-Page)
+- [Play Overview](Play-Overview)
+- [Channels](Channels)
+- [Calendar](Calendar)
+- [Schedules](Schedules)
+- [Reviews and Checkpoints](Reviews-and-Checkpoints)
+- [Publishing to YouTube](Publishing-to-YouTube)
+- [Keyboard Shortcuts and Command Palette](Keyboard-Shortcuts-and-Command-Palette)

package/dist/tutorials/Home.md

@@ -0,0 +1,119 @@
+# Slopify Wiki
+
+Slopify turns a prompt and a few keywords into a narrated, captioned video. It writes the article, narrates it, makes the images and cuts the video, and can also give you shorts, a PDF of the article and a ready-to-paste YouTube description. It runs as a local web app on your own machine, with your own provider keys or the Claude Code, Codex or Gemini CLI you already use. It is free.
+
+These pages cover Slopify 3.0: every screen, every setting and every workflow, step by step.
+
+**Read them inside Slopify too:** the same pages are under **Help → Tutorials** in the app (the address is `/help/tutorials/<Page>`, for example `/help/tutorials/Install`), with a search box over all of them. From the command palette (`Ctrl+K`), **Open tutorial: <page>** jumps straight to one. See [Keyboard and Ctrl+K](Keyboard-Shortcuts-and-Command-Palette#open-a-tutorial-page).
+
+## Start here
+
+1. [Install](Install) Slopify (Node 26 or newer) or run it in [Docker](Docker).
+2. Open it at `http://127.0.0.1:6969` and follow [First launch and welcome](First-Launch-and-Welcome).
+3. Make [your first 60-second short](Your-First-Short). With a signed-in CLI and your computer's own voice it needs no keys at all.
+4. Add the keys you want in [Providers and keys](Providers-and-Keys) (press **Test** to check a key before you save it), or sign in to an [AI CLI](AI-CLIs).
+5. Make a full video from [Play](Play-Overview).
+
+## How a video gets made
+
+1. **Settings:** add provider keys and voices, or use a signed-in CLI.
+2. **Library → Prompts:** write article, image and thumbnail prompts once, with `{{keywords}}` where the subject goes.
+3. **Play:** pick a template or prompts, type the topic, choose your outputs, check the cost estimate, press **Start run** (or **Queue 3 videos** for several topics).
+4. **The project page** shows each stage as it runs. Download the video, captions, PDF and description when it is done.
+5. **Edit settings** on the project (the Edit project form) to change anything. Slopify remakes only what the change affects.
+
+## Contents
+
+### Getting started
+| Page | What it covers |
+|---|---|
+| [Install](Install) | Installing with npx or npm, command-line options, ffmpeg, telemetry |
+| [Docker](Docker) | Running Slopify in Docker with the compose file and the CLI helper |
+| [First launch and welcome](First-Launch-and-Welcome) | The three-step first run, the three samples, Make my own copy, starter packs |
+| [Your first short](Your-First-Short) | A 60-second short from topic to finished video |
+| [Home and Projects](Home-and-Projects) | The sidebar, the Home dashboard and the Projects list |
+| [Where your files live](Where-Your-Files-Live) | Documents/Slopify, the data folder and moving your files |
+| [Start at login](Start-at-Login) | Starting Slopify when you log in |
+| [Updating and patch notes](Updating-and-Patch-Notes) | Updating, going back, and reading patch notes |
+| [Uninstalling and moving](Uninstalling-and-Moving) | Removing Slopify and moving between Docker and a native install |
+
+### Providers
+| Page | What it covers |
+|---|---|
+| [Providers and keys](Providers-and-Keys) | Every API provider, testing and saving keys, the system voice, Settings → Voices |
+| [AI CLIs](AI-CLIs) | Claude Code, Codex and Gemini CLI: sign-in, use and plan limits |
+| [Models](Models) | The model catalogue, retired models and switching |
+| [Costs and run cost](Costs-and-Run-Cost) | Cost estimates, the run cost line, the Run cost tab and usage |
+
+### Making a video
+| Page | What it covers |
+|---|---|
+| [Play overview](Play-Overview) | Templates, topics, batches, drafts, the estimate, Start and Queue |
+| [Title and article](Play-Title-and-Article) | Title patterns, article prompts, research and your own text |
+| [Narration](Play-Narration) | Voices, pauses, volume, glossary, aliases, described tables |
+| [Images](Play-Images) | Image prompts, the establishing image, cast, image pacing, Codex |
+| [Video and style](Play-Video-and-Style) | Cuts, the Look, transitions, chapter cards, motion, captions, ambient sound |
+| [Outputs](Play-Outputs) | Video, shorts, description, PDF, thumbnails and audio exports |
+| [Reviews and checkpoints](Reviews-and-Checkpoints) | Automatic reviews and pausing a run for you to check |
+
+### Formats and outputs
+| Page | What it covers |
+|---|---|
+| [Multiple voices](Multiple-Voices) | Audiobook, podcast, radio drama and interview formats |
+| [Other languages](Other-Languages) | Making videos in languages other than English |
+| [Shorts](Shorts) | Vertical shorts cut from the long video |
+| [YouTube description](YouTube-Description) | Description, chapters, hashtags and tags |
+| [PDF documents](PDF-Documents) | The article as a PDF with contents, sources and a cover |
+
+### The project page
+| Page | What it covers |
+|---|---|
+| [Project page](Project-Page) | The next action, the run cost line, time left, downloads, the players, freeing space |
+| [Editing a project](Editing-a-Project) | Edit project, remaking outdated work, the rebuild review, history |
+| [Video editing](Video-Editing) | Video, caption, subtitle and ambient sound controls on a project |
+| [Recovery and retries](Recovery-and-Retries) | Fix-it buttons, retries and waiting for plan limits |
+| [Trash](Trash) | Deleted projects and how to get them back |
+
+### Publishing
+| Page | What it covers |
+|---|---|
+| [Publishing to YouTube](Publishing-to-YouTube) | Prepare upload, AI use disclosure, chapters and links |
+| [Studio extension](Studio-Extension) | The browser extension that fills YouTube Studio's upload dialog |
+
+### Automation
+| Page | What it covers |
+|---|---|
+| [Templates](Templates) | Saving and reusing a setup |
+| [Schedules](Schedules) | Videos on a cadence, topic lists and self-filling topics |
+| [Calendar](Calendar) | What needs you, what is coming up, the video queue |
+| [Notifications](Notifications) | Browser and phone (ntfy) notifications |
+| [Backups](Backups) | Automatic backups, export and import |
+
+### Channels
+| Page | What it covers |
+|---|---|
+| [Channels](Channels) | Brand kit, episode memory, existing videos and channel links |
+| [Cast library](Cast-Library) | Recurring characters with pictures and voices |
+
+### Library
+| Page | What it covers |
+|---|---|
+| [Library overview](Library-Overview) | What the Library holds |
+| [Prompts](Prompts) | Writing prompts, keyword slots, history and restore |
+| [Intros and outros](Intros-and-Outros) | Reusable openings and closings |
+| [Aliases and glossary](Narration-Aliases-and-Glossary) | How the narrator says words |
+| [Document themes](Document-Themes) | The look of the PDF |
+
+### Reference
+| Page | What it covers |
+|---|---|
+| [Settings reference](Settings-Reference) | Every Settings section and control |
+| [Keyboard and Ctrl+K](Keyboard-Shortcuts-and-Command-Palette) | Shortcuts and the command palette |
+| [Troubleshooting](Troubleshooting) | Common errors and how to fix them |
+| [FAQ](FAQ) | Short answers to common questions |
+
+## Getting help inside the app
+
+Every setting in Slopify has an info button beside it that explains what it does. If something goes wrong, the project page shows a button that names the fix. The question-mark button at the foot of the sidebar starts the interactive tutorial.
+
+These pages ship inside Slopify too, so they work offline and match the version you run: the book button beside the question mark opens **Help → Tutorials**, with the same groups as this wiki's sidebar and a search across every page. Many info buttons end in **Learn more**, which opens the matching section there, and `Ctrl+K` → **Open tutorial: <page>** opens any page. See [Troubleshooting](Troubleshooting) for the rest.

package/dist/tutorials/Install.md

@@ -0,0 +1,154 @@
+# Install
+
+Slopify is a local web app you start from a terminal. It runs on your own computer, opens in your browser at `http://127.0.0.1:6969`, and uses your own provider keys or the AI command-line tools you are already signed in to.
+
+**Where to find it:** a terminal on your computer (PowerShell or Windows Terminal on Windows, Terminal on macOS, any shell on Linux).
+
+## What you need
+
+| Requirement | Details |
+| --- | --- |
+| Node.js | Version 26 or newer, with npm (it comes with Node). Get it from nodejs.org. |
+| Operating system | Windows, macOS or Linux for the normal install. The managed Docker install is Linux only (see [Docker](Docker)). |
+| ffmpeg | Nothing to install: Slopify brings its own copy. See [ffmpeg](#ffmpeg) below. |
+| Disk space | Enough for your videos. Every project keeps its video, images, narration and working files. The caption model is a 95 MB download. |
+| Keys or CLIs | Text and images can come from Claude Code, Codex or Gemini CLI, or from API keys. Narration can use a voice provider key, or your computer's own speech for free (the System voice; on Linux, install `espeak-ng`). See [Providers and Keys](Providers-and-Keys) and [AI CLIs](AI-CLIs). |
+
+## Choose how to run it
+
+There are three ways. All three give you the same app.
+
+| Way | Command | Good for |
+| --- | --- | --- |
+| Run with npx | `npx @gentbajko/slopify@latest` | Trying it, or always starting the newest version. Nothing is installed globally. |
+| Install with npm | `npm install -g @gentbajko/slopify`, then `slopify` | A permanent `slopify` command. |
+| Docker (Linux) | `npx @gentbajko/slopify@latest --docker` | Keeping Slopify running in the background, restarting with Docker. See [Docker](Docker). |
+
+## Start Slopify with npx
+
+1. Open a terminal.
+2. Run `npx @gentbajko/slopify@latest`.
+3. Wait while npm downloads the package the first time. Slopify then checks ffmpeg, starts, and prints where everything is:
+   - `Slopify is running at http://127.0.0.1:6969`
+   - `Slopify data directory:` the hidden data folder (normally `~/.slopify`)
+   - `Projects:` where your project folders are (on a new install, `Documents/Slopify/Projects`)
+   - `Database:` and `Logs:` inside the data folder
+4. Your browser opens at `http://127.0.0.1:6969`. If it doesn't, open that address yourself.
+5. On an interactive terminal Slopify asks once: `Start Slopify when you log in? (Y/n)`. Press Enter for yes, or type `n`. See [Start at Login](Start-at-Login).
+6. Keep the terminal open while you use Slopify. Press `Ctrl+C` in it to stop Slopify.
+
+Continue with [First Launch and Welcome](First-Launch-and-Welcome).
+
+## Install it with npm
+
+1. Run `npm install -g @gentbajko/slopify`.
+2. Start it any time with `slopify`. The same flags work: `slopify --port 7070`.
+
+In-app updates work for both npx and a global install: the new version is installed inside the data folder and later starts take it from there. See [Updating and Patch Notes](Updating-and-Patch-Notes).
+
+## Commands
+
+| Command | What it does |
+| --- | --- |
+| `npx @gentbajko/slopify@latest` | Starts Slopify. |
+| `npx @gentbajko/slopify@latest update` | Updates a running Slopify to the newest version, the same way the in-app update button does. It only works while Slopify is running. If you have a Docker install, it updates that one instead. |
+| `npx @gentbajko/slopify@latest --docker` | Installs Slopify in Docker, or re-applies changed Docker settings. Same as `install --docker`. |
+| `npx @gentbajko/slopify@latest update --docker` | Updates the Docker install. |
+
+Any other word after the package name is refused with a message listing these commands. Without `--docker` there is nothing to install: `install` on its own is refused.
+
+`update` for a normal install needs Slopify to be running. If it isn't, the command says so: start Slopify first, and add `--port <number>` if it runs on another port.
+
+## Options
+
+A flag beats the environment variable, and the variable beats the default.
+
+| Flag | Variable | Default | What it does |
+| --- | --- | --- | --- |
+| `--port` | `SLOPIFY_PORT` | `6969` | The port Slopify listens on. A whole number from 1 to 65535. |
+| `--host` | `SLOPIFY_HOST` | `127.0.0.1` | The address it binds to. |
+| `--data-dir` | `SLOPIFY_DATA_DIR` | `~/.slopify` | Where the database, settings, keys, logs and caption models live. A relative path is taken from the folder you run the command in. |
+| `--no-open` | `SLOPIFY_NO_OPEN` | opens a browser | Doesn't open a browser tab. For the variable, any value except empty, `0` or `false` counts as on. |
+| `--autostart` / `--no-autostart` | | asks once | Turns [Start at Login](Start-at-Login) on or off without asking. Useful in scripts. |
+| | `SLOPIFY_FFMPEG` | the bundled ffmpeg | The full path of another ffmpeg to use. |
+| | `SLOPIFY_NO_MODEL_PREFETCH` | downloads at start | Set to `1` to skip fetching the 95 MB caption model when Slopify starts. It is then fetched the first time a video needs captions. |
+
+Options that only work with `--docker`: `--projects-dir <folder>`, `--host-cli=off` and `--accept-host-cli`. See [Docker](Docker). With `--docker`, `--host` and `--data-dir` are refused, because the Docker version always listens on localhost and keeps its data in a Docker volume.
+
+### A second install or a test install
+
+Start Slopify with its own data folder, for example `npx @gentbajko/slopify@latest --data-dir ~/slopify-test --port 7070`. A new install with its own data folder keeps its project files inside that folder instead of in `Documents/Slopify`, so it never shares files with your main install. See [Where Your Files Live](Where-Your-Files-Live).
+
+Only one Slopify can use a data folder at a time. A second one on the same folder stops with `Slopify is already running on this data directory`.
+
+## Keep it on 127.0.0.1
+
+Slopify has no login. Whoever can reach its port controls the app and every provider key saved in it. The default `127.0.0.1` means only your own computer can reach it.
+
+If you start it with another `--host`, the terminal prints a warning: `WARNING: bound to <host> - anyone who reaches this port controls the app and its keys (no login).` Only do that on a network you trust completely.
+
+## ffmpeg
+
+Slopify makes its videos with ffmpeg, and you don't need to install it.
+
+- A normal install gets a tested ffmpeg for your system through npm when the package is installed. Slopify never uses an ffmpeg from your `PATH` on its own.
+- Before starting, Slopify checks that ffmpeg runs. If the install-time download is missing, it downloads the same build into `<data folder>/bin/`, with its licence and source notice, and reuses it on later starts.
+- The Docker image already contains ffmpeg.
+
+To use your own ffmpeg, set `SLOPIFY_FFMPEG` to its full path:
+
+```sh
+SLOPIFY_FFMPEG=/usr/bin/ffmpeg npx @gentbajko/slopify@latest
+```
+
+In Windows PowerShell:
+
+```powershell
+$env:SLOPIFY_FFMPEG = 'C:\tools\ffmpeg\bin\ffmpeg.exe'
+npx @gentbajko/slopify@latest
+```
+
+The bundled ffmpeg is a separate program under the GPL-3.0-or-later licence. Slopify runs it as a separate process and does not link to it.
+
+## The caption model
+
+Captions are timed against the narration by a speech model that runs on your computer, at no cost. The English model (95 MB) is downloaded when Slopify starts, in the background, so a run never waits for it later. It is kept in `<data folder>/models/`. Set `SLOPIFY_NO_MODEL_PREFETCH=1` to skip the download at start. Other languages use a separate model that is downloaded the first time a project in that language needs it.
+
+## Anonymous usage stats
+
+The first time you open Slopify it shows **Anonymous usage stats**, a notice listing exactly what is counted, with one button, **Got it**. These counts feed the live totals on slopify.stream.
+
+| Tracked | Never tracked |
+| --- | --- |
+| Tokens in and out per stage, with provider and model | API keys |
+| Audio seconds, images, thumbnails, videos rendered | Prompt bodies and keyword values |
+| PDF documents, YouTube descriptions and shorts made | Titles, article or research text |
+| Projects created, and that this machine installed Slopify | Files and file names |
+| The time each of those happened | OS, locale, hardware |
+
+Each report carries a random id of its own, a random id for this machine and the Slopify version. There is no setting to turn it off. Settings → **Usage** shows the same counters for your machine only.
+
+## If it doesn't start
+
+| Message | What to do |
+| --- | --- |
+| `Port 6969 is already in use by another program (maybe another Slopify)` | Stop the other program, or start on another port: `npx @gentbajko/slopify --port 7070`. |
+| `Slopify is not allowed to use port …` | Pick 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`. |
+| `Slopify can't write to its data folder …` | Make sure your user owns that folder, or choose another with `--data-dir <folder>`. |
+| `The disk is full` | Free some space and start again. |
+| `Slopify could not download and start ffmpeg` | Check your connection and whether antivirus quarantined it, or set `SLOPIFY_FFMPEG`. |
+| `Slopify is already running on this data directory` | Use the Slopify that is already running, or close it first. If none is running, delete the lock file the message names. |
+
+More in [Troubleshooting](Troubleshooting).
+
+## Related pages
+
+- [Docker](Docker)
+- [First Launch and Welcome](First-Launch-and-Welcome)
+- [Where Your Files Live](Where-Your-Files-Live)
+- [Start at Login](Start-at-Login)
+- [Updating and Patch Notes](Updating-and-Patch-Notes)
+- [Providers and Keys](Providers-and-Keys)
+- [AI CLIs](AI-CLIs)
+- [Troubleshooting](Troubleshooting)

package/dist/tutorials/Intros-and-Outros.md

@@ -0,0 +1,86 @@
+# Intros and Outros
+
+Intros and outros are short narrated passages read before and after the body of a video, in the same voice: a greeting, a series tagline, a sign-off, a call to subscribe. Write one as fixed text, or as an instruction the text model answers fresh for each video.
+
+**Where to find it:** **Library → Intros & Outros**. Pick them on Play in the **Intro** and **Outro** pickers (Narration row → **Audio Advanced**), in **Edit project**, or as a channel default in the channel's brand kit.
+
+## Text or LLM
+
+Each entry has a **Mode**:
+
+| Mode | What happens | Extra cost |
+|---|---|---|
+| **Text** (default) | "Text is narrated as written." Keywords are filled in, with no extra call. | Only the voice request |
+| **LLM** | "LLM is an instruction whose answer is narrated." The body goes to the project's text model with the title, the keyword values and the article, and the answer is narrated. The run then needs an LLM. | One text call per entry, plus the voice request |
+
+Either way the intro or outro is narrated as its own audio file with the run's voice: one voice request each.
+
+## Write an intro or outro
+
+1. Open **Library → Intros & Outros**.
+2. Choose **Intros** or **Outros** with **Entry category**.
+3. Press **New intro or outro**.
+4. Fill in the editor:
+   - **Name**: what Play and Edit project list it by. Up to 200 characters, unique within its category.
+   - **Category**: **Intro** (read before the body) or **Outro** (read after it). You can change it later.
+   - **Mode**: **Text** or **LLM**.
+   - **Body**: in Text mode, the words the narrator says; in LLM mode, the instruction whose answer is said. Each `{{keyword}}` becomes a field on Play, just like in prompts.
+5. Press **Save** (or `Ctrl+S`).
+
+### Examples
+
+A text intro:
+
+```
+Welcome back to the channel. Tonight: {{Topic}}. Get comfortable.
+```
+
+An LLM outro:
+
+```
+Write two sentences that close this video warmly. Mention one idea from the article
+the listener can think about tonight. Do not ask them to subscribe.
+```
+
+## Use one in a video
+
+**On Play:**
+
+1. Open the **Narration** row with **Change**, then open **Audio Advanced**.
+2. Pick an entry in **Intro** and, if you like, in **Outro**. **Off** reads none.
+3. Fill in any new keyword fields the entry added.
+
+**From the Library:** press **Use in Play** on the entry's row. It is picked in your open Play draft and Play opens on its field.
+
+**For a whole channel:** open **Channels** → the channel → **Brand** and set **Intro** and **Outro** under the brand kit. Every video of that channel whose template has no intro or outro of its own gets them. See [Channels](Channels).
+
+**In a finished project:** open **Edit project**, pick a different intro or outro, and save. Only the parts that change are remade. See [Editing a project](Editing-a-Project).
+
+## Edit, duplicate, delete and history
+
+Entries have the same row actions as prompts:
+
+| Action | What it does |
+|---|---|
+| **Edit** | Opens the editor. Change it and press **Save**. |
+| **Duplicate** | Opens the editor with a copy to rename and save. |
+| **Use in Play** | Picks the entry in the open Play draft. |
+| **History** | Versions, compare and **Used by**, exactly as for prompts. See [Prompts](Prompts#history-and-versions). |
+| **Delete** | Asks first, then moves it to **Settings → Trash** for 30 days. |
+
+Use **Search intros and outros** (`/`) to find one by name. The pencil beside a name renames the entry in its row, with **Undo** on the notice; see [Rename in the row](Library-Overview#rename-in-the-row).
+
+A project keeps its own copy of the intro and outro it started with, so editing an entry here changes only runs started later. Templates keep their own copies too.
+
+## Tips
+
+- Keep intros short. Viewers leave during long openings; two sentences is plenty.
+- An LLM outro that summarises the video costs one small text call and never repeats itself across videos.
+- Put the channel's standard intro and outro in the brand kit instead of every template.
+
+## Related pages
+
+- [Narration](Play-Narration)
+- [Prompts](Prompts)
+- [Channels](Channels)
+- [Library overview](Library-Overview)