@gentbajko/slopify 3.0.0 → 3.0.1

package/dist/tutorials/Shorts.md

@@ -0,0 +1,116 @@
+# Shorts
+
+Shorts turns the best moments of your long video into vertical clips for YouTube Shorts, TikTok and Reels, with no editing on your part. After the narration is timed, the text model picks self-contained moments; each becomes a 1080×1920 (9:16) clip with new images, big word-by-word captions and its own title, description and hashtags.
+
+**Where to find it:** Play → **Outputs** row → **Shorts**. On a finished project: the **Shorts** section, and Edit project → **Shorts**.
+
+## What you get
+
+For each short:
+
+- A vertical 1080×1920 MP4, cut from the long video's narration at sentence edges.
+- New 9:16 images drawn for that clip (the long video's images are not reused).
+- Big captions a little below the middle of the frame, two to four words at a time, with the word being spoken in a strong colour.
+- The short's title at the top for the whole clip, if **Title on screen** is on.
+- A title (up to 60 characters), a one-line description ending with a link to the full video, and 3 to 5 hashtags.
+
+Shorts are made in the Video stage, beside the long video's render. They need narration.
+
+## Turn on Shorts
+
+1. On Play, open the **Outputs** row.
+2. Tick **Shorts**. It is greyed out, with "Needs narration", when the Narration row is off.
+3. Set **How many** and **Length**.
+4. Optionally pick a **Shorts prompt** and an **Image style** from your Library.
+5. Open **More shorts options** to set the title, speed, music and full video link. The disclosure's summary names what differs from the defaults, such as "Title on screen · 1.10× · Full video linked". The [Shorts preview](#shorts-preview) shows the result as you change them.
+6. Check the estimate in the right rail and start the run.
+
+## Options
+
+| Option | What it does | Default / range |
+|---|---|---|
+| **Shorts** | Turns the step on. Turning it off keeps your numbers and prompts for next time. | Off |
+| **How many** | How many shorts to cut from this video. Each needs its own new images, so more shorts cost more image calls and render time. | 3; 1 to 10 |
+| **Length** | The shortest and longest a short may run, in seconds. The text model picks moments within these bounds. | 60 to 120; each between 15 and 180 |
+| **Shorts prompt** | The Library prompt the text model follows to pick the moments and write each short's title, description and hashtags. | **Built-in**: picks moments that make sense alone, open on a hook and end on a complete thought |
+| **Image style** | The Library Image prompt the shorts' new vertical images are drawn from. | **Built-in**: cinematic, high-contrast, uncluttered images with the subject large and centred, the lower half calm for captions, no text |
+| **Title on screen** | Keeps the short's title at the top for the whole clip, large and bold in the caption font, below where the apps draw their own buttons. | On |
+| **Speed** | Plays each short faster than the narration, with the pitch kept. | 1.00× (normal); 1.00× to 1.25× in steps of 0.05 |
+| **Music volume** | How loud the background music plays under every short. It dips while the narrator speaks. Only used when you add a music file. | 15; 0 to 100 percent |
+| **Full video link** | Each short's description ends with "Watch the full video:" and this link. Without it the line says `[PASTE THE FULL VIDEO LINK HERE]` for you to fill in. | Empty; up to 2,000 characters |
+| Background music | An audio file mixed under every short, looped if shorter than a short. | None |
+
+Write your own Shorts prompts and Image prompts in **Library → Prompts** ([Prompts](Prompts)). To match the long video's look, pick one of your own Image prompts as the Image style.
+
+## Shorts preview
+
+While **More shorts options** is open (on Play, or in Edit project → **Shorts**), **Shorts preview** ("A few seconds of the sample as a short, rendered with your settings") renders a few seconds of the bundled sample project as a 9:16 short, through the same renderer real shorts use: the big word-by-word captions in your caption font, the title on screen when **Title on screen** is on (the sample's title, "The Library of Alexandria"), and your **Speed**. The line under it reads, for example, "Title on screen · 1.10×". It renders on your computer at no cost; **Render again** forces a fresh one.
+
+## What it costs
+
+- **Picking:** one text-model call picks the moments, then one call per short writes its image prompts.
+- **Images:** each short gets one image per **Seconds per image** of its length (at least one), and each image is one image-model call on your image provider. Before the clips are picked, the estimate charges the most the step could ask for: every short at the longest length you allowed.
+- **Rendering:** done on your computer at no provider cost.
+- **Reviews:** with Automatic reviews on, each short can be reviewed like other outputs. Picture reviews need Claude Code or Codex as the reviewer.
+
+With the establishing image on, the shorts' images are drawn with it as a reference too, so characters and style stay the same. See [Play-Images](Play-Images).
+
+## See, copy and download your shorts
+
+When the run finishes, the project page's **Shorts** section shows a grid headed with the count, for example **3 shorts · 9:16**. Above the grid, one lime **Download** holds every short's MP4 in a menu (**Download the short** when there is one), with **Open folder** and **Pick different moments** beside it. Each short has:
+
+- A vertical player (Slopify's own, showing the short's first picture until it plays), its title and length.
+- Its description, the full video line and its hashtags.
+- One row of icon buttons whose names show when you point at them: **Download** (the short's MP4; left out when there is only one short, since the section's Download already fetches it), **Copy title, description and hashtags**, which puts all three on the clipboard in one go, and **More**, which holds **Make short N again**.
+
+While the stage runs, a short not rendered yet says how far it got, such as "Making images · 2 of 5" or "Rendering". A short that failed says so and points you to Error details in the Video section.
+
+To upload them, open **Prepare upload**: each short is listed on its own, with its title, description and tags. See [Publishing-to-YouTube](Publishing-to-YouTube).
+
+## Change the picked moments
+
+1. Open the project and press **Edit settings**, then open **Shorts**. (**Make short N again** on the project page opens the same place with the change made.)
+2. Under **Picked clips**, each clip is shown by its first and last sentence.
+3. Move a clip with **Earlier start**, **Later start**, **Earlier end** and **Later end**, one sentence at a time.
+4. Or press **Use my own range** and pick the **Start sentence** and **End sentence** from the lists. **Back to the AI's choice** restores the model's pick.
+5. Save, then continue the run.
+
+A clip must stay between the shortest and longest length you set and must not overlap another clip; the line under the clip says what to change. Moving a clip costs no text calls and keeps its images where the sentences stay the same.
+
+## Pick new moments or remake one short
+
+| Action | What happens when you save and continue the run | Cost |
+|---|---|---|
+| **Pick different moments** | The text model picks new moments. Ranges you set by hand are dropped. A new clip on the same sentences as an old one keeps its images; any other clip gets new images and is rendered again. **Keep the current moments** cancels it. | One text call, plus one image call per new image |
+| **Make short N again** | This one short's image prompts are written again, its images drawn again and the short rendered again. Its moment, title and the other shorts stay as they are. | One image call per image |
+| Change **How many**, **Length** or **Shorts prompt** | The moments are picked again, as with Pick different moments. | As above |
+
+## Add background music
+
+1. Open Edit project → **Shorts** (or use the music control under **More shorts options** on Play).
+2. Choose an audio file under **Background music (optional)**. It is looped if shorter than a short.
+3. Set **Music volume**. The music dips while the narrator speaks.
+4. Save and continue the run. **Remove the music** takes it off again.
+
+## Shorts with other features
+
+- **Multiple voices:** shorts start and end on a speaker's turn. See [Multiple-Voices](Multiple-Voices).
+- **Other languages:** titles and hashtags are written in the project's language. In languages without word timing, shorts show whole caption groups instead of word by word. See [Other-Languages](Other-Languages).
+- **Tables and figures:** a short that includes a described table or figure shows it upright.
+- **AI use answer:** a short's answer follows its Image style: Yes only if that Image prompt is marked **Draws photorealistic pictures** (the Built-in style is not), or a narrating voice is marked Real person. See [Publishing-to-YouTube](Publishing-to-YouTube#ai-use-disclosure).
+
+## Tips
+
+- Keep **Length** close to the default 60 to 120 seconds; very short clips often lose the setup that makes a moment work.
+- After you upload the long video, paste its link in **Full video link** (Edit project → **Shorts**) and save. Copy and Prepare upload read the link when you use them, so the description line picks it up.
+- A frame format of 9:16 on the Video and style row makes the long video itself vertical; Shorts are separate clips and are always 9:16.
+
+## Related pages
+
+- [Play-Outputs](Play-Outputs)
+- [Prompts](Prompts)
+- [Video-Editing](Video-Editing)
+- [Editing-a-Project](Editing-a-Project)
+- [Publishing-to-YouTube](Publishing-to-YouTube)
+- [Reviews-and-Checkpoints](Reviews-and-Checkpoints)
+- [Costs-and-Run-Cost](Costs-and-Run-Cost)

package/dist/tutorials/Start-at-Login.md

@@ -0,0 +1,126 @@
+# Start at Login
+
+One switch makes Slopify start quietly in the background when you log in to your computer, so it is ready whenever you open your bookmark. It needs no administrator password, and turning it off removes exactly what it added.
+
+**Where to find it:** Settings → **General** → **Start Slopify when I log in**. It is also offered once on the first-run screen and in the terminal.
+
+## Turn it on
+
+1. Open Settings → **General**.
+2. Turn on **Start Slopify when I log in**.
+3. The line under the switch confirms it and names the login entry it added.
+
+From the next login, Slopify starts without opening a browser tab. Open it from your bookmark (`http://127.0.0.1:6969`) as usual.
+
+Default: off.
+
+## Turn it off
+
+1. Open Settings → **General**.
+2. Turn off **Start Slopify when I log in**.
+
+The login entry is removed. The Slopify you are using keeps running until you stop it.
+
+## Where you are asked
+
+You are asked once, in whichever place comes first:
+
+| Place | Question | Answers |
+| --- | --- | --- |
+| The terminal, the first time `npx @gentbajko/slopify` starts on an interactive terminal | `Start Slopify when you log in? (Y/n)` | Enter or `y` means yes; `n` means no. It is asked after Slopify is already running, so it never holds it up. |
+| The first-run screen (step 3) | **Start Slopify when I log in** | **Start when I log in** or **No thanks** |
+| After an update, when neither of those asked (an update started from the app has no terminal, and the first-run screen is only for new installs) | A one-time dialog, **Start Slopify when you log in?** | **Start when I log in** or **No thanks**. Closing it counts as No thanks. |
+
+Answering in any of these places, or using the switch in Settings, ends the question for good.
+
+### In scripts
+
+Without an interactive terminal nothing is asked. Use a flag instead:
+
+| Flag | What it does |
+| --- | --- |
+| `--autostart` | Turns the switch on. |
+| `--no-autostart` | Turns the switch off. |
+
+Unlike the question, the flags set the switch every time you give them.
+
+## What it adds on each system
+
+Two things: a small launcher in Slopify's data folder, and one login entry in your own account's start-up list that runs it.
+
+| System | Login entry | Launcher |
+| --- | --- | --- |
+| Linux | `~/.config/autostart/slopify.desktop` (or `$XDG_CONFIG_HOME/autostart`) | `<data folder>/autostart/start-slopify.sh` |
+| macOS | `~/Library/LaunchAgents/stream.slopify.app.plist` | `<data folder>/autostart/start-slopify.sh` |
+| Windows | Registry `HKCU\Software\Microsoft\Windows\CurrentVersion\Run`, value `Slopify` | `<data folder>\autostart\start-slopify.cmd` |
+
+### Linux
+
+A standard desktop autostart entry, which GNOME, KDE, Xfce, Cinnamon and most other desktops run at login. No systemd unit is used.
+
+### macOS
+
+A per-user LaunchAgent that runs at load. It takes effect at your next login; turning the switch on doesn't start a second Slopify beside the one you are using. Turning it off deletes the file. There is no keep-alive: if you quit Slopify, it stays quit until the next login.
+
+### Windows
+
+A value in your user's Run list. At login it opens Slopify in a minimised window in the taskbar; closing that window stops Slopify. A data folder whose path contains `%` can't be used, because Windows would read it as a variable. Start Slopify with another folder (for example `--data-dir C:\Slopify`) and turn the switch on there.
+
+### WSL
+
+Not available. Windows doesn't start Linux programs when you log in. Start Slopify from a Windows terminal instead and turn the switch on there.
+
+### An entry you made yourself
+
+If an entry with the same name exists and Slopify didn't write it, Slopify leaves it alone. Turning the switch on says so and names the file (on Windows, see Task Manager → Startup apps).
+
+## How the launcher starts Slopify
+
+`npx` keeps packages in a cache it may clean or move, so the login entry never points into it. It runs the launcher in the data folder, which starts, in this order:
+
+1. your installed Slopify (`npm install -g`), when you don't run it through `npx`;
+2. `npx` beside the Node you were using, asking for the exact version you were running. A pinned version starts offline once it is cached, and never jumps to a new release by itself;
+3. `npx` from your `PATH`, the same way.
+
+It starts Slopify with `--no-open`, and with the data folder, port and (when it isn't `127.0.0.1`) host that were in use when you turned the switch on, since no terminal passes them at login.
+
+- If the Node it recorded is gone (after an nvm or Homebrew upgrade), it uses the `node` on your `PATH`.
+- In-app updates still apply: the started version hands over to the newest one installed in the data folder. See [Updating and Patch Notes](Updating-and-Patch-Notes).
+- Every start with the switch on rewrites the launcher, so it follows the Node, the install and the version you actually use.
+- A Slopify started with a different `--data-dir` leaves the entry pointing where it was.
+
+Output from login starts is added to `<data folder>/logs/autostart.log`. Look there if Slopify didn't come up after a login.
+
+## Docker
+
+In Docker the switch isn't used. The container restarts with Docker (`restart: unless-stopped`), so Slopify starts at login exactly when Docker does. Slopify never changes Docker's own settings.
+
+1. The `--docker` installer asks `Start Slopify when you log in? (Y/n)` once (or takes `--autostart` / `--no-autostart`).
+2. It reads, without changing, whether Docker starts by itself. With Docker Desktop (always on macOS and Windows, and on Linux when its settings file is there), that is Docker Desktop's own setting **Start Docker Desktop when you sign in**, read from its settings file. Otherwise it asks `systemctl is-enabled docker.service` for the system Docker, or `systemctl --user is-enabled docker.service` for rootless Docker.
+3. If Docker doesn't start by itself, it prints how to turn that on: with Docker Desktop, "Turn on Docker Desktop → Settings → General → Start Docker Desktop when you sign in to your computer."; with Docker Engine, `sudo systemctl enable docker`, or `systemctl --user enable docker` for rootless Docker.
+
+Settings → **General** and the first-run screen then show (the first-run screen only informs; there is nothing to switch):
+
+| Line | Meaning |
+| --- | --- |
+| **Starts with Docker: yes** | Docker starts at boot or login, so Slopify does too. |
+| **Starts with Docker: no** | Docker doesn't start by itself. The screen says where to change that. |
+| **Starts with Docker: unknown** | The installer couldn't check, or you run the compose file yourself. |
+| **Checked by the installer on …** | When it last looked. |
+
+After changing Docker's setting, run `npx @gentbajko/slopify@latest --docker` again so it checks again. A compose file you run by hand has no record, so the screen says it can't know and points to Docker Desktop → Settings → General → Start Docker Desktop when you sign in, or `sudo systemctl enable docker` for Docker Engine.
+
+## Tips
+
+- Bookmark `http://127.0.0.1:6969` so you can open Slopify after login without a terminal.
+- If you uninstall Slopify, turn the switch off first so no login entry is left behind. See [Uninstalling and Moving](Uninstalling-and-Moving).
+- If you usually start Slopify with `--port` or `--data-dir`, turn the switch on from a Slopify started with those options; the launcher remembers them.
+
+## Related pages
+
+- [Install](Install)
+- [Docker](Docker)
+- [First Launch and Welcome](First-Launch-and-Welcome)
+- [Updating and Patch Notes](Updating-and-Patch-Notes)
+- [Settings Reference](Settings-Reference)
+- [Troubleshooting](Troubleshooting)

package/dist/tutorials/Studio-Extension.md

@@ -0,0 +1,146 @@
+# Studio Extension
+
+Slopify Studio is an optional browser extension that fills YouTube Studio's upload dialog from a project's Prepare upload list: title, description, thumbnails, playlist, audience, the AI use answer and tags. You drop the video file in yourself, check what it filled, and press Publish yourself. The extension never presses Next, Save, Schedule or Publish.
+
+**Where to find it:** it ships with Slopify. Download it from Settings → **YouTube Studio** → **Install the Studio extension** (or from **Prepare upload** while no extension is paired). Pairing is in the same Settings section. You use it from a finished project → **Prepare upload** → **Fill in YouTube Studio**.
+
+## What you need
+
+- Slopify running on this computer (it opens at `http://127.0.0.1:6969` by default).
+- Chrome, Chromium, Edge or Brave, or Firefox 128 or newer.
+
+The extension is built into Slopify, so there is nothing else to get. It is not published in a browser store. It has no remote code: everything it runs is in the zip you download.
+
+## Get the extension
+
+1. Open Settings → **YouTube Studio**. Under **Install the Studio extension**, pick your browser: **Chrome, Edge, Brave** or **Firefox**.
+2. Press **Download for Chrome** or **Download for Firefox**. It saves `slopify-studio-chrome.zip` or `slopify-studio-firefox.zip`.
+3. Follow the three steps shown under the button, also written out below.
+
+Prepare upload shows the same download and steps while no extension is paired.
+
+## Install on Chrome, Chromium, Edge or Brave
+
+1. Unzip `slopify-studio-chrome.zip` into a folder you keep: the browser loads the extension from there.
+2. Open `chrome://extensions` (in Edge, `edge://extensions`; in Brave, `brave://extensions`) and turn on **Developer mode**.
+3. Press **Load unpacked** and pick that folder.
+4. Pin **Slopify Studio** to the toolbar if you like.
+
+## Install on Firefox
+
+1. Keep the zip as it is.
+2. Open `about:debugging#/runtime/this-firefox` and press **Load Temporary Add-on**.
+3. Pick `slopify-studio-firefox.zip`.
+
+A temporary add-on is removed when Firefox restarts. Load it again after each restart.
+
+## Update the extension
+
+After updating Slopify, download the zip again from Settings → **YouTube Studio** and replace the old one: unzip over the same folder and press the reload arrow on `chrome://extensions`, or load the new Firefox zip.
+
+## Pair it with Slopify
+
+Pairing gives the extension a secret so that only it, and no web page, can read your upload packs.
+
+1. In Slopify, open **Settings → YouTube Studio**.
+2. Under **Extension pairing token**, press **Copy**.
+3. Click the extension's toolbar button (or open its options). The **Slopify Studio · Pairing** page opens.
+4. Check **Slopify address**. It must be the address in your Slopify tab, `http://127.0.0.1:6969` by default.
+5. Paste the token into **Pairing token** and press **Pair**.
+
+The options page says "Paired with Slopify at …". Back in Settings, the line under the token says "Paired with the extension at …" with the extension's address.
+
+To unpair, press **New pairing token** in Settings. It makes a fresh token and unpairs the extension until you paste the new one and press Pair again.
+
+## Settings → YouTube Studio
+
+The section is headed **Upload pack and extension**.
+
+| Option | What it does | Default / range |
+|---|---|---|
+| **Playlist** | The YouTube playlist upload packs name, so the extension ticks it in Studio's dialog. Pick **Every channel (default)** or one channel in the channel list, type the playlist exactly as it is called in Studio, and press **Save**. The default is used by every channel without its own; a channel's own playlist wins for its videos. Leave it empty for no playlist. | Empty; up to 150 characters |
+| **Extension pairing token** | The secret the extension needs before it may read your upload packs. **Copy** copies it; **New pairing token** makes a new one and unpairs the extension. | Made for you |
+| **Install the Studio extension** | The download and install steps (see [Get the extension](#get-the-extension)). | |
+
+## Fill in an upload
+
+1. Open a finished project and press **Prepare upload**.
+2. Under **What to upload**, pick **Video** or a short.
+3. Press **Fill in YouTube Studio**. Studio's upload page opens in a new tab, and the item joins **Waiting for Studio**.
+4. Drop the video file into Studio's upload dialog. (Use **Download** or **Open folder** on the Video file row to find it.)
+5. When the **Details** step appears, the extension first checks that the dialog has every field the item needs, then fills them and shows a message for each, bottom right.
+6. Check everything. If you want to start over, press **Fill again from Slopify** (bottom right).
+7. Go through Studio's remaining steps and publish yourself.
+8. Back in Slopify, press **Mark uploaded**. See [Publishing-to-YouTube](Publishing-to-YouTube#mark-a-video-uploaded).
+
+**Fill in YouTube Studio** is only offered once an extension is paired. Unpaired, Prepare upload says "The Slopify Studio extension isn't paired.", shows the install and pair steps, keeps the Copy steps as your upload pack, and offers **Open YouTube Studio**.
+
+### Upload several one after another
+
+Each press of **Fill in YouTube Studio** adds the item to **Waiting for Studio** instead of replacing the last one. Every new upload dialog you open in Studio is filled with the next waiting item, in order. So you can queue the video and all its shorts, then upload them one by one.
+
+- Prepare upload lists what waits: the first row says "Next: filled in the next upload dialog you open in Studio.", the others "Filled after N more uploads." **Remove** takes one off.
+- The list survives a restart of Slopify. An item waits up to 24 hours. A new pairing token clears the list, and it never travels in a backup.
+
+## What it fills
+
+| Field in Studio | What the extension does |
+|---|---|
+| **Title** | Types the title (up to 100 characters for the video, the short's own title for a short). |
+| **Description** | Types the description line by line, so line breaks are kept. |
+| **Thumbnail** | Sets the first thumbnail. With three thumbnails, it looks for Studio's **A/B Testing** button beside the title and puts all three in. If the button isn't there or its dialog can't be filled, it sets the first and asks you to add the others in A/B Testing by hand. Shorts get no thumbnail. |
+| **Playlists** | Opens the dropdown, ticks the playlist named in Settings → YouTube Studio, and closes it. |
+| **Audience** | Picks "No, it's not made for kids". |
+| **Show more** | Presses it once, to reach the advanced settings. |
+| **AI use** | Picks Yes or No, as Prepare upload worked it out. See [AI use disclosure](Publishing-to-YouTube#ai-use-disclosure). |
+| **Tags** | Types each tag and turns it into a chip. Tags already there are skipped. |
+
+It then says what it did. It does not choose visibility, schedule, or press any button that saves or publishes.
+
+## When a field can't be filled
+
+Studio changes its page from time to time.
+
+- **A field is missing before anything is written.** The extension checks every field the item needs first. If Studio's dialog lacks one, it fills nothing at all, so you never get a half-filled upload: "Nothing was filled: Studio's upload dialog has changed, and Slopify couldn't find …". It copies the whole upload pack (or offers **Copy** for it) and names the missing fields. Paste each part by hand, or use the Copy buttons in Prepare upload. Downloading the extension again from Settings → YouTube Studio may fix it.
+- **A field doesn't take the text.** It shows a message for that field, for example "Couldn't find the Tags field — the text is copied, paste it by hand", and fills the rest ("Filled what it could; 1 field needs you. Nothing was published.").
+
+Every message with text to paste has a **Copy** button. If the browser refuses the clipboard, the text is shown selected so you can copy it yourself.
+
+Before relying on the extension, try it on one real upload and read its messages.
+
+## Privacy and security
+
+- Only the extension's background worker talks to Slopify, and only at `127.0.0.1` or `localhost`.
+- Slopify answers the extension's requests only with the pairing token, and only from the extension that paired. It never answers web pages.
+- The extension reads only the upload pack you chose and its thumbnails.
+- It runs on `studio.youtube.com` only, and needs no YouTube sign-in of its own: it works in the Studio tab you are already signed in to.
+
+## Limits
+
+- It never uploads the video file: you drop it into Studio.
+- It never presses Next, Save, Schedule or Publish.
+- It fills the Details step only. Monetisation, end screens, cards, visibility and scheduling are left to you.
+- Some parts of Studio have not been checked against the live page and may not fill: the playlist list the dropdown opens, the A/B Testing dialog (the button may only appear once the upload is saved), whether the upload dialog behaves exactly like the Details editor, and whether Studio makes a tag chip on Enter or on comma. The extension tries both keys and reports what it can't confirm.
+- It looks at Studio at most every quarter of a second and stops looking while it fills a dialog, so it doesn't slow Studio down.
+- In Firefox, a temporary add-on disappears when Firefox restarts.
+- If you change Slopify's port or address, pair again with the new **Slopify address**.
+
+## Troubleshooting
+
+| Problem | What to do |
+|---|---|
+| Studio opens but nothing is filled | Make sure you dropped the video file in and reached the Details step. Check the extension is paired (Settings → YouTube Studio says "Paired with the extension at …") and that the item is under **Waiting for Studio** in Prepare upload. Press **Fill again from Slopify** in Studio. If it says "Nothing was filled", see [When a field can't be filled](#when-a-field-cant-be-filled). |
+| The wrong item was filled | Items fill in the order they wait. **Remove** the ones you don't want under **Waiting for Studio** in Prepare upload. |
+| Pairing fails | Check the **Slopify address** matches your Slopify tab, and copy the token again from Settings → YouTube Studio. If you pressed New pairing token, the old one no longer works. |
+| Studio says "The extension isn't paired with Slopify yet." | Open the extension's options, paste the pairing token from Settings → YouTube Studio and press **Pair**. |
+| Settings says "No extension is paired" | Paste the token into the extension's options and press **Pair**. |
+| A field says it couldn't be filled | Paste the copied text by hand. Studio may have changed that field. |
+| The extension is gone in Firefox | Load it again from `about:debugging`; temporary add-ons are removed on restart. |
+
+## Related pages
+
+- [Publishing-to-YouTube](Publishing-to-YouTube)
+- [YouTube-Description](YouTube-Description)
+- [Shorts](Shorts)
+- [Settings-Reference](Settings-Reference)
+- [Troubleshooting](Troubleshooting)

package/dist/tutorials/Templates.md

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

package/dist/tutorials/Trash.md

@@ -0,0 +1,87 @@
+# Trash
+
+Deleting something in Slopify does not remove it at once. Deleted projects, prompts, intros and outros, templates and schedules go to the trash for 30 days, where you can put them back or remove them for good.
+
+**Where to find it:** Settings → **Trash**.
+
+## What goes to the trash
+
+| Kind | Shown as | Deleted from |
+| --- | --- | --- |
+| Project | Project | Projects (the delete button on a project's row, then **Delete project**) |
+| Library prompt | Prompt · *type* (for example Prompt · article) | Library → Prompts |
+| Intro or outro | Intro or Outro | Library → Intros & Outros |
+| Template | Template | Templates |
+| Schedule | Schedule | Schedules |
+
+As soon as an item is in the trash it disappears from every list, picker, lookup, the calendar and the batch queue, and its name is free for a new item right away.
+
+Each row in the trash shows the item's name, its kind, when it was deleted and how many days are left, for example "Project · deleted *date* · 30 days left". On its last day it says "removed for good today".
+
+## Restore an item
+
+1. Open Settings → **Trash**.
+2. Find the item under **Deleted items**.
+3. Press **Restore**.
+
+It comes back as it was. A few kinds have their own rules:
+
+| Item | What happens on restore |
+| --- | --- |
+| Prompt, intro/outro or template whose name was taken meanwhile | It comes back as "Name (restored)", then "Name (restored 2)" and so on. The message says which name it got. A renamed template gets a new version. |
+| Project that was waiting its turn (a queued batch item, or held at a checkpoint) | It was held while in the trash and picks up where it was. |
+| Schedule | It comes back **paused**, with no next run. Press **Resume** on Schedules to run it again. |
+| Schedule whose template is also in the trash | Restore the template first (it is listed in the trash too), then the schedule. |
+| Schedule whose template was removed for good | It cannot be restored: it has nothing to run. **Delete now** removes it from the trash. |
+
+## Delete an item for good
+
+1. Open Settings → **Trash**.
+2. Press **Delete now** on the item.
+3. Confirm with **Delete for good**, or press **Keep it**.
+
+What the confirmation says:
+
+- **Project**: "The project and every file it produced are removed from disk. This cannot be undone." The project's folder is removed first, then its records.
+- **Schedule**: "The schedule leaves the trash and cannot be restored. Its run history stays on Schedules."
+- **Anything else**: "It is removed for good. This cannot be undone." A prompt or intro/outro goes with its History.
+
+There is no button to empty the whole trash at once; each item is deleted on its own, or left for the daily clean-up.
+
+## Retention: the 30-day clean-up
+
+Anything in the trash for more than 30 days is removed for good by a daily clean-up, the same way as **Delete now**. Slopify checks hourly whether a day has passed since the last clean-up, so a computer that was asleep catches up. If one item cannot be removed (for example a project folder another program has open), it stays in the trash for the next pass and the rest still go.
+
+A project's disk space is freed only when it leaves the trash. Settings → **Storage** counts deleted projects still in the trash. See [Where Your Files Live](Where-Your-Files-Live).
+
+## What cannot be deleted
+
+| Situation | What to do |
+| --- | --- |
+| A project that is still running | Open the project and use **More project actions → Cancel the run…** first. On Projects the delete button says "Cancel the run first, then delete it." |
+| A template that a schedule (not in the trash) uses | Delete that schedule first. |
+
+## Messages you may see
+
+| Message | Fix |
+| --- | --- |
+| "This project is still running. Use Cancel run on the project page first, then try again." | Cancel the run, then delete. |
+| "Some of this project's files could not be removed. Close any program using files in the project folder, then press Delete now again." | Close the file manager, player or editor that has the folder open, then press **Delete now** again. |
+| "This schedule's template is in the trash too. Restore the template first (it is listed here), then restore the schedule." | Restore the template, then the schedule. |
+| "This schedule's template was removed for good, so the schedule has nothing to run. It cannot be restored; Delete now removes it from the trash." | Use **Delete now**. |
+| "This item is no longer in the trash: it was restored or removed for good. Reload Settings → Trash to see what is left." | Reload the page. |
+
+## Tips
+
+- Delete what you do not need with **Delete now** when you want the disk space back at once.
+- A deleted schedule's past runs stay listed on Schedules even after it is removed for good.
+
+## Related pages
+
+- [Home and Projects](Home-and-Projects)
+- [Where Your Files Live](Where-Your-Files-Live)
+- [Prompts](Prompts)
+- [Intros and Outros](Intros-and-Outros)
+- [Templates](Templates)
+- [Schedules](Schedules)
+- [Settings Reference](Settings-Reference)