@gentbajko/slopify 4.0.0 → 4.2.0

package/dist/tutorials/Narration-Aliases-and-Glossary.md

@@ -1,14 +1,61 @@
 # Narration Aliases and Glossary
 
-Two tools control how the narrator says words without changing what is written. **Narration aliases** swap a written form for a spoken one, such as `Dr.` said as "Doctor", with any generated voice. The **Pronunciation Glossary** gives exact IPA pronunciations for names, such as `Arda: /ˈɑɹdə/`, with Inworld's TTS-2 voices. In both cases the article, the transcript and the captions keep the written words; only the audio changes.
+Three tools control how the narrator says words without changing what is written. **Name pronunciations** is your own list of names with their IPA, used before anything an article says, so a name sounds the same in every video. **Narration aliases** swap a written form for a spoken one, such as `Dr.` said as "Doctor", with any generated voice. The **Pronunciation Glossary** is the list each article writes for itself, such as `Arda: /ˈɑɹdə/`. IPA is read by Inworld's TTS-2 voices; aliases work with every voice. In all three the article, the transcript and the captions keep the written words; only the audio changes.
 
-**Where to find it:** aliases in **Library → Narration aliases**. Both switches are on Play under **Narration → Change → More audio settings**, and in **Edit project**. A project's glossary is shown on its **Article** section, in the **Pronunciation** tab.
+**Where to find it:** your list in **Settings → Voices → Name pronunciations**, aliases in **Settings → Voices → Pronunciation**. The switches are on Create under **Narration → Change → More narration settings**, and in a project's **Edit settings** → **Narration**. A project's own glossary is shown on its **Article** section, in the **Pronunciation** tab.
+
+## Name pronunciations
+
+Your list settles a name once. Every project copies it when it starts, and its entries come **before** the glossary that project's article wrote, so the name is said your way whatever the article spelled out.
+
+1. Open **Settings → Voices → Name pronunciations**.
+2. Write one `Term: /IPA/` per line, in standard-English IPA between slashes:
+
+```
+Gygax: /ˈɡaɪɡæks/
+Faerûn: /feɪˈruːn/
+Mordenkainen: /ˌmɔːrdənˈkeɪnən/
+```
+
+3. Press **Save pronunciations**. The line under the box says how many names the list pronounces, and a note names any line narration has to skip, by its number and reason, the way the article's glossary does.
+
+- One IPA word per written word. A hyphenated name's parts each get one.
+- A possessive follows its name: `Gygax's` is said from the `Gygax` entry.
+- A dash, `n/a` or nothing leaves the name read as written: useful for a name you want plain.
+- Up to 100,000 characters, which is thousands of names.
+- Only Inworld **TTS-2** and **TTS-2 Flash** read IPA. For any other voice, use an alias instead.
+- **Use pronunciations** must be on for the project (the default) — the same switch that reads the article's glossary.
+
+A project keeps the copy it started with. Editing the list later changes new projects only, until you open a project's **Edit settings** → **Narration** and press **Copy the list again** under **Use pronunciations**; only the narration where a changed name appears is made again.
+
+### Two people, or an agent, at the same list
+
+The whole list is saved at once, so Slopify makes sure one save never quietly replaces another. Every save carries the version of the list it was made from. If something else saved meanwhile — a second window, or an agent — the save is refused and the page says so:
+
+> **The list changed somewhere else.** An agent saved it: it has 3 names you don't have, 1 said differently.
+
+Nothing is lost. What you typed stays in the box, and you choose:
+
+- **Save mine anyway** keeps what is on screen, over theirs.
+- **Load theirs instead** puts their list in the box, so you can add your change to it and save.
+
+An agent gets the same refusal as a sentence, with the list as it stands: it reads the version, folds its change into that text, and saves again (`get_library_pronunciations`, then `set_library_pronunciations` with `{text, version}`).
+
+### Which list wins
+
+| Where a pronunciation comes from | Order |
+|---|---|
+| **Name pronunciations** (your list) | First: it wins everywhere |
+| The article's own **Pronunciation Glossary** | Next, for names your list does not have |
+| **Other projects' pronunciations**, while shared | Last, for names neither of the above has |
+
+An alias beats all three, because it changes the words before the sounds are decided.
 
 ## Narration aliases
 
 ### Add aliases
 
-1. Open **Library → Narration aliases**.
+1. Open **Settings → Voices → Pronunciation**.
 2. Press **Add alias**. A new row appears in the list, titled **Alias N**, with its fields under it.
 3. Fill in the row:
 
@@ -39,17 +86,17 @@ Each row's title line sums it up, for example "Says Dr. as Doctor · whole word"
 - Two aliases can't share a written form.
 - Where two overlap in the text, the one starting first wins, then the longer.
 - A multi-word alias is read with single spaces around it: "Grey et al. wrote" goes to the voice as "Grey and others wrote".
-- An alias wins over a Pronunciation Glossary entry for the same words.
+- An alias wins over a Name pronunciations entry and a Pronunciation Glossary entry for the same words.
 - Aliases work with every generated voice, and in multi-voice runs they apply to each speaker's turn.
-- Aliases also change the sentences **Narration Preparation** reads, so its cues match what is said.
+- Aliases also change the sentences **Narration preparation** reads, so its cues match what is said.
 
 ### Use aliases in a video
 
-1. On Play, open the **Narration** row with **Change**, then **More audio settings**.
-2. Keep **Use narration aliases** on (the default for new drafts).
+1. On Create, open the **Narration** row with **Change**, then **More narration settings**.
+2. Keep **Use your pronunciation list** on (the default for new drafts).
 3. Start the run.
 
-A project copies the Library's aliases when it starts. Editing the Library later never changes a started project until you open **Edit project** and press **Update from Library** beside the aliases switch. Only the parts of the narration where a changed alias appears are made again.
+A project copies your Pronunciation list when it starts. Editing the list later never changes a started project until you open its **Edit settings** → **Narration** and press **Copy the list again** beside the aliases switch. Only the parts of the narration where a changed alias appears are made again.
 
 Projects from before aliases existed have the switch off and nothing copied.
 
@@ -59,11 +106,11 @@ Captions show the written words, while the audio says the alias. A caption reads
 
 ## The Pronunciation Glossary
 
-The Pronunciation Glossary is a section at the end of the article that lists names with their pronunciation in IPA. With a voice that supports it, the narrator reads each listed name the way the glossary says, with no extra text-model call. The glossary itself is never narrated.
+The Pronunciation Glossary is a section at the end of the article that lists names with their pronunciation in IPA. With a voice that supports it, the narrator reads each listed name the way the glossary says, with no extra AI call. The glossary itself is never narrated.
 
 ### Which voices support it
 
-Inworld **TTS-2** and **TTS-2 Flash**. With other providers or models the switch is greyed out and says "Unavailable for this provider or model. Your saved preference is retained."
+Inworld **TTS-2** and **TTS-2 Flash**. With other services or models the tick is not shown; your choice is kept for when you pick one of those voices.
 
 ### Get a glossary into the article
 
@@ -86,8 +133,8 @@ A table with `Term | IPA` columns works too. If you paste your own article, add
 
 ### Turn it on
 
-1. On Play, open **Narration → Change → More audio settings**.
-2. Keep **Use Pronunciation Glossary** on (the default).
+1. On Create, open **Narration → Change → More narration settings**.
+2. Keep **Use pronunciations** on (the default). It shows only while the voice is one that reads IPA, and it covers both your Name pronunciations and this article's glossary.
 3. Optional: keep **Also use pronunciations from my other projects** on (the default). It adds every term from your other projects' glossaries, copied when this project starts. This project's own glossary wins where they differ. Turn it off to use only this article's glossary.
 
 ### Entries that are skipped
@@ -102,28 +149,63 @@ An entry narration can't use is skipped and read as ordinary text. It never bloc
 | supply one IPA word for each written word | "New York" needs two IPA words. |
 | an earlier entry already gives this term a different pronunciation | The term is listed twice with different sounds. |
 
-To fix skipped entries, edit the Pronunciation Glossary at the end of the article in **Edit project → Article**, then save. See [Editing a project](Editing-a-Project).
+To fix skipped entries, edit the Pronunciation Glossary at the end of the article in **Edit settings** → **Article**, then save. See [Editing a project](Editing-a-Project).
+
+## Does this video say the names right?
+
+Two checks on the project page answer that from files the project already has. Neither one blocks the run or the upload, neither costs anything, and neither changes a thing.
+
+### Before the narration is paid for
+
+The **Narration** section says, in one line, which names this article uses that nothing pronounces: not its own Pronunciation Glossary, not your **Name pronunciations** list, not the pooled copy of the other projects' glossaries. **Every mention** opens the table — each name, how often it is said as written and how often as a possessive, proper names first.
+
+This is the cheapest moment to settle a name, because adding it to **Name pronunciations** costs nothing and the voice has not been paid yet.
+
+It also catches the names a glossary looks like it covers and doesn't:
+
+| What the glossary has | What the article says | Why the voice guesses |
+|---|---|---|
+| `Belwar Dissengulp` | "Belwar" on its own | A two-word term never matches one of its words said alone. |
+| `Drizzt` | "Drizzt's" | A project narrated under the old pronunciation rules wrapped no possessive. |
+| `Catti-brie` | "Catti-brie" | The old rules skipped a hyphenated term, so it was read as ordinary text. |
+
+A project is judged by the rules it was voiced under, so a video made before those rules changed is told what actually happened to it, not what would happen today.
+
+### After the render, before the upload
+
+The **YouTube** section carries the same line, saying two things.
+
+**What the voice was sent.** Counted from the voice script itself, which is exactly the text the voice received: a name with no IPA in front of it there was guessed, whatever the glossary says.
+
+**How each name was heard.** Read from the per-word confidence the subtitle timing already wrote when the captions were made: each name's mean, and the spread across its mentions. Nothing is listened to again and nothing is re-aligned.
+
+The spread is the signal, not a low score. A rare name is heard poorly even when it is said perfectly, so only a name whose own mentions disagree with each other is flagged: eight mentions or more, and a spread of 0.30 or more between its 10th and 90th percentile.
+
+A name read as an ordinary English word is left out of both checks: a one-word name that the same text also writes in lower case is a word here and not a name, which is why "Hall" stays quiet in a video that also says "hall".
 
-## Aliases or glossary?
+## Which one do I use?
 
 | You want | Use |
 |---|---|
 | An abbreviation read in full (Dr., St., vs.) | Alias |
 | A word read as a different word or spelling | Alias |
-| Any voice provider | Alias |
-| A made-up or foreign name said exactly right, on Inworld TTS-2 | Glossary |
-| Pronunciations that come with each article automatically | Glossary |
+| Any voice service | Alias |
+| A name said the same way in every video | Name pronunciations |
+| To correct a name once, for everything you have made since | Name pronunciations |
+| A made-up or foreign name said exactly right, on Inworld TTS-2 | Name pronunciations, or the article's glossary |
+| Pronunciations that come with each article automatically | The article's glossary |
 
 ## Tips
 
 - Spell **Say it as** the way it sounds, not the way it is written: "Shiv-awn" rather than "Siobhan".
 - Keep **Whole word** on unless you really want to match inside other words. Otherwise `St.` could fire inside unrelated text.
 - Listen to the first minute of a new run before a long batch, and add aliases for anything the voice stumbles on.
+- A name that comes back video after video belongs in **Name pronunciations**, not in each article's prompt: one line there holds for every project that follows.
 
 ## Related pages
 
-- [Narration](Play-Narration)
+- [Create: Narration](Create-Narration)
 - [Prompts](Prompts)
 - [Editing a project](Editing-a-Project)
 - [Multiple voices](Multiple-Voices)
-- [Providers and keys](Providers-and-Keys)
+- [Keys and Services](Providers-and-Keys)

package/dist/tutorials/Notifications.md

@@ -11,35 +11,39 @@ Runs can take a while, so Slopify can tell you when one needs you: in the browse
 | A run **finishes** | "Video ready: *title*", or "Run finished: *title*" for a run that makes audio only |
 | A run **finishes with problems** | "Video ready with problems: *title* — *reason*": the video was made but another step failed |
 | A run **fails** | "Run failed: *title* — *reason*", with the first line of the reason |
-| A step **fails while the run waits on something else** | "Step failed: *title* — *reason*". Only when another step is waiting: an agent's review, your checkpoint, or a prepared run's day. See [Step failed](#step-failed). |
-| A run **stops to wait for you** | "Waiting for you: *title*": a review checkpoint is holding the next step, or the work left is waiting for **Continue the run** |
-| An agent's review **passed without an answer** | "Passed without review: no agent answered in 2 h", naming the project and the item. See [Agents (MCP)](Agents-MCP#if-no-agent-answers). |
-| An automatic review **needs a decision** | "Review needs a decision: <title>", when an automatic review flags an item and keeps it (its redos ran out, or the stage only flags). It says what was flagged and to press **Overrule** or **Redo** on the project. Sent once per verdict. |
+| A step **fails while the run waits on something else** | "Step failed: *title* — *reason*". Only when another step is waiting: an agent's check, your approval at a pause, or the day of a video made ahead. See [Step failed](#step-failed). |
+| A run **stops to wait for you** | "Waiting for you: *title*": a pause is holding the next step, or the work left is waiting for **Continue the run** |
+| An agent's check **passed without an answer** | "Passed without review: no agent answered in 2 h", naming the project and the item. See [Agents (MCP)](Agents-MCP#if-no-agent-answers). |
+| An AI check **needs a decision** | "Review needs a decision: <title>", when an AI check flags an item and keeps it (its redos ran out, or the stage only flags). It says what was flagged and to press **Overrule** or **Redo** on the project. Sent once per verdict. |
 | A schedule has **new topics waiting** for approval | For example "5 new topics are waiting for you" |
 
-Pausing or cancelling a run yourself sends nothing, and neither does a project that was already finished when the page loaded. A run waiting for an [agent's review](Agents-MCP#the-external-agent-reviewer), or a prepared run waiting for its day, sends no "Waiting for you": nobody needs to act. A message holds the project title and what happened, never your keys, prompts or files.
+Pausing or cancelling a run yourself sends nothing, and neither does a project that was already finished when the page loaded. A run waiting for an [agent's check](Agents-MCP#your-own-ai-agent-as-the-checker), or a video made ahead waiting for its day, sends no "Waiting for you": nobody needs to act. A message holds the project title and what happened, never your keys, prompts or files.
 
-A run an [agent](Agents-MCP) started ends its messages with **· started by agent**, and a flag from an agent's review ends with **· by agent**.
+A run an [agent](Agents-MCP) started ends its messages with **· started by agent**, and a flag from an agent's check ends with **· by agent**.
 
 ### Step failed
 
 An ordinary run tells you once, at its end: "Run failed" or "Video ready with problems", with the end chime. A step that fails on the way is named there, not in a message of its own.
 
-"Step failed" is for the other case: a step fails while another step of the run is waiting (for an agent's review, your checkpoint, or a prepared run's day). The run is not over and may wait for hours, so Slopify tells you right away instead of at the end. The project still reads by what it waits for, and the failed step shows on its page with its fix.
+"Step failed" is for the other case: a step fails while another step of the run is waiting (for an agent's check, your approval at a pause, or the day of a video made ahead). The run is not over and may wait for hours, so Slopify tells you right away instead of at the end. The project still reads by what it waits for, and the failed step shows on its page with its fix.
 
 Each failure is told once. A restart neither repeats a message already sent nor loses one: what was told is saved. A step that fails again after **Try again** is a new failure and is told again. If the run later ends **Failed** on failures already told, no second "Run failed" goes out.
 
+### On the page, always
+
+The end of a run is also said on the page itself, whatever the switches below say: while a Slopify tab is open, a notice in the corner reads "Video ready: *title*" with **Watch** (the project's Video part), "Run finished: *title*" with **Open** for a run without a video, or "Run failed: *title* — *reason*" with **Open**, which stays until you close it. With several tabs open, one of them shows it.
+
 ### While you were away
 
 When you come back to a Slopify tab after more than two minutes away (or open one after closing it), one notice sums up what happened meanwhile, for example "While you were away: 2 runs finished, 1 step failed beside a wait, 1 run waits for you.", with **Open Home**. It counts runs that finished, runs that failed, steps that failed beside a wait, and runs that started waiting for you. Runs waiting for an agent or for their day are not counted as waiting for you. It works from this browser's own memory of what it last saw, with no setting.
 
 ## Turn on browser notifications
 
-Browser notifications work while any Slopify tab is open, in any section, even in the background.
+Browser notifications work while any Slopify tab is open, on any page, even in the background.
 
 1. Open **Settings → Notifications**.
-2. Turn **Browser notifications** on. The browser asks for permission now (never when the page loads). Allow it.
-3. Press **Send test notification** to check. You should see "Test notification sent to this browser."
+2. Turn **Notify me in this browser** on. The browser asks for permission now (never when the page loads). Allow it.
+3. Press **Send test notification**, which appears beside the switch once it is on, to check. You should see "Test notification sent to this browser."
 
 What to expect:
 
@@ -55,22 +59,22 @@ If you blocked notifications for Slopify earlier, Slopify says "Notifications ar
 1. Click the icon left of the address bar and open the site settings.
 2. Allow notifications.
 3. Reload the page.
-4. Turn **Browser notifications** on again.
+4. Turn **Notify me in this browser** on again.
 
 Some browsers only allow notifications from installed apps. If the test says so, use a Notification URL instead.
 
-## Run sounds
+## Sounds when a run starts and ends
 
-**Settings → Notifications → Run sounds** (on by default) plays a chime when a run starts and a different, longer one when it finishes, fails or stops to wait for you, like a message arriving on a phone. A "Step failed" plays the end chime too. **Play start** and **Play end** let you hear them.
+**Settings → Notifications → Play a sound when a run starts and ends** (on by default) plays a chime when a run starts and a different, longer one when it finishes, fails or stops to wait for you, like a message arriving on a phone. A "Step failed" plays the end chime too. **Hear the start sound** and **Hear the end sound** play them.
 
 - Works while any Slopify tab is open; only one tab plays each chime.
 - Needs no permission, but browsers keep a page silent until it has been clicked once, so click anywhere in Slopify after opening it.
-- With **Browser notifications** on too, a run's start also shows "Started: *title*".
+- With **Notify me in this browser** on too, a run's start also shows "Started: *title*".
 - It is this browser's own setting. Your computer's volume sets how loud.
 
 ## Get notifications on your phone (Notification URL)
 
-A Notification URL works with no Slopify tab open. When a run finishes, fails or waits, a step fails beside a wait, a review needs a decision or passes without an agent's answer, Slopify sends that address one `POST` with a short plain-text body. Its last line is the project's link, so you can open it straight from the message, for example:
+A Notification URL works with no Slopify tab open. When a run finishes, fails or waits, a step fails beside a wait, an AI check needs a decision or passes without an agent's answer, Slopify sends that address one `POST` with a short plain-text body. Its last line is the project's link, so you can open it straight from the message, for example:
 
 ```
 Video ready: Black holes explained
@@ -108,13 +112,13 @@ Home shows the same last 7 days under **Coming up** (see [Home and Projects](Hom
 ## Tips
 
 - Turn on both: browser notifications while you are at the computer, ntfy for when you walk away.
-- Pair notifications with [Reviews and checkpoints](Reviews-and-Checkpoints) so a run that waits for your review tells you right away.
+- Pair notifications with [pauses](Reviews-and-Checkpoints) so a run that waits for your review tells you right away.
 
 ## Related pages
 
 - [Settings reference](Settings-Reference)
 - [Schedules](Schedules)
 - [Calendar](Calendar)
-- [Reviews and checkpoints](Reviews-and-Checkpoints)
+- [Pauses and checks](Reviews-and-Checkpoints)
 - [Agents (MCP)](Agents-MCP)
 - [Troubleshooting](Troubleshooting)

package/dist/tutorials/Other-Languages.md

@@ -1,12 +1,12 @@
 # Other Languages
 
-A project can be written and narrated in one of 30 languages, not only English. Slopify asks the text model to write the article, description and shorts titles in that language, lists the voices that speak it, and times the captions for it. English and nine other languages get word-by-word captions; the rest are timed sentence by sentence.
+A project can be written and narrated in one of 30 languages, not only English. Slopify asks the AI to write the article, description and shorts titles in that language, lists the voices that speak it, and times the captions for it. English and nine other languages get word-by-word captions; the rest are timed sentence by sentence.
 
-**Where to find it:** Play → **Channel** row → **Language**. On a finished project: Edit project → **Providers** → **Language**. For a channel's default: Channels → the channel → **Brand** → **Language of new projects**.
+**Where to find it:** Create → **Article** row → **Language**. On a finished project: **Edit settings** → **Channel** → **Language**. For a channel's default: Channels → the channel → **Name and look** → **Language of new projects**.
 
 ## Pick a language for one video
 
-1. On Play, open the **Channel** row.
+1. On Create, open the **Article** row.
 2. Under **Language**, pick the language. The first option, **Channel's language (…)**, uses the channel's language and names it.
 3. Open the **Narration** row and pick a **Voice** that speaks the language. The list only shows voices listed for that language, plus voices whose languages are unknown.
 4. Read the line under the Language picker: it says what is written in the language and how the captions will be timed.
@@ -16,16 +16,16 @@ A template saves the language its draft had. A draft that never picked one uses
 
 ## Set a channel's language
 
-1. Open **Channels**, pick the channel and open its **Brand** tab.
+1. Open **Channels**, pick the channel and open its **Name and look** tab.
 2. Under **Language of new projects**, pick the language. **Not set** means English.
 
 This applies with the brand kit off too, because language is not styling. Projects already made keep their language.
 
 ## Change the language of a finished project
 
-1. Open the project and press **Edit project**.
-2. Open **Providers** and pick the new **Language**.
-3. Save. Changing the language re-writes the project's text and re-times its captions; the rebuild review shows what will be remade and what it costs.
+1. Open the project and press **Edit settings**.
+2. Open **Channel** and pick the new **Language**.
+3. Press **Save changes**. Changing the language writes the project's text again and times its captions again; **Choose what to make again** shows what will be made and what it costs.
 
 ## What changes with the language
 
@@ -61,12 +61,12 @@ English projects get no extra line, so they are exactly what they were before la
 Saved voices carry the languages they speak.
 
 1. Open **Settings → Voices** and add a voice.
-2. Leave **Languages** blank and Slopify asks ElevenLabs, Cartesia or Inworld which languages the voice speaks, or type codes yourself, such as `es, de`.
-3. Press **Edit** in the Languages column to change them later.
+2. Leave **Languages it speaks** on **Any language** and Slopify asks ElevenLabs, Cartesia or Inworld which languages the voice speaks, or pick them yourself by name.
+3. Change them later in the voice's row, under **Speaks**: pick a language to add it, or remove one.
 
 OpenAI has no voice API for this, and its voices read every language its model does. A voice whose languages are unknown is offered for every language.
 
-On Play, the voice list shows the voices that speak the project language. Tick **Show all voices** to pick one listed for other languages, for example a multilingual voice whose languages are listed wrong. If you pick such a voice, Play warns you but does not stop the run. Speaker voice pickers under Speakers, and a cast member's voice picker, filter the same way. See [Multiple-Voices](Multiple-Voices).
+On Create, the voice list shows the voices that speak the project language. Tick **Show all voices** to pick one listed for other languages, for example a multilingual voice whose languages are listed wrong. If you pick such a voice, Create warns you but does not stop the run. Speaker voice pickers under Speakers, and a cast member's voice picker, filter the same way. See [Multiple-Voices](Multiple-Voices).
 
 ## Caption timing in detail
 
@@ -87,21 +87,21 @@ For any language other than English, Slopify checks that your caption font has t
 
 1. It uses a bundled Noto font for Latin, Greek, Cyrillic, Arabic, Hebrew, Devanagari and Thai.
 2. For Chinese, Japanese and Korean, which are not bundled (their fonts run to 10-20 MB), it looks for a font on your computer that has the letters.
-3. If none is found, the Video stage stops and says so. Upload a font that has the letters with **Upload font (.ttf or .otf)** in the caption font picker (Play → **Video and style**, or Edit project → **Subtitles**), choose it, then press **Try again**. Noto Sans JP, KR or SC from fonts.google.com work.
+3. If none is found, the Video stage stops and says so. Upload a font that has the letters with **Upload font (.ttf or .otf)** in the caption font picker (Create → **Video and style**, or **Edit settings** → **Captions**), choose it, then press **Try again**. Noto Sans JP, KR or SC from fonts.google.com work.
 
-English projects always render with exactly the font you chose.
+English projects always use exactly the font you chose.
 
 ## Limits
 
 - Only the 30 languages above can be picked.
 - Word-by-word captions and cuts that follow the narration are only available in English and the nine multilingual languages.
 - The first captions in a multilingual language need a one-time download of about 248 MB.
-- Some voice providers list languages incorrectly; use Show all voices if the voice you want is missing.
+- Some voice services list languages incorrectly; use Show all voices if the voice you want is missing.
 
 ## Related pages
 
-- [Play-Narration](Play-Narration)
-- [Play-Video-and-Style](Play-Video-and-Style)
+- [Create: Narration](Create-Narration)
+- [Create: Video and Style](Create-Video-and-Style)
 - [Channels](Channels)
 - [Multiple-Voices](Multiple-Voices)
 - [Shorts](Shorts)

package/dist/tutorials/PDF-Documents.md

@@ -1,26 +1,26 @@
 # PDF Documents
 
-Slopify can lay out your article as a styled PDF: a title page with the thumbnail as its cover, a table of contents, the article with drop caps, a sources page and an optional closing page. It is drawn on your computer in the theme you pick, needs no provider and costs nothing.
+Slopify can lay out your article as a styled PDF: a title page with the thumbnail as its cover, a table of contents, the article with drop caps, a sources page and an optional closing page. It is drawn on your computer in the look you pick, needs no service and costs nothing.
 
-**Where to find it:** Play → **Outputs** row → **Document**. On a finished project: the **Document** section of the project page, and Edit project → **Inputs** → **Stages** → **Document theme**.
+**Where to find it:** Create → **Extras** → **PDF of the article**. On a finished project: the **PDF** section of the project page, and **Edit settings** → **Extras** → **PDF**.
 
 ## Make a PDF
 
-1. On Play, open the **Outputs** row.
-2. In the **Document** rail, switch the source from **Off** to **Generate**.
-3. Pick a **Theme**: the built-in **Plain**, or one of your own themes from Library → PDF themes.
-4. Start the run.
+1. On Create, open the **Extras** row.
+2. Tick **PDF of the article**.
+3. Pick a **PDF look**: one of the three ready looks, **Plain**, **Book** or **Modern** (**Preview** shows it), or one of your own PDF looks.
+4. Make the video.
 
-The Document stage runs after the article (and the thumbnail, if there is one) is ready. A thumbnail that failed or was canceled doesn't hold it back: the PDF is then laid out without a cover. It needs an article with some text; an empty article stops the stage with a message pointing you to Edit project → Article.
+The Document stage runs after the article (and the thumbnail, if there is one) is ready. A thumbnail that failed or was canceled doesn't hold it back: the PDF is then laid out without a cover. It needs an article with some text; an empty article stops the stage with a message pointing you to **Edit settings** → **Article**.
 
 ## Options
 
 | Option | What it does | Default |
 |---|---|---|
-| **Document** source | **Generate** lays out a PDF of the article and title on this computer, in the theme you pick. It needs no provider and costs nothing. | Off |
-| **Theme** | How the PDF looks: the built-in **Plain** theme, or one of yours from **Library → PDF themes**. **Edit themes** opens the list. | Plain, or the channel's document theme |
+| **PDF of the article** | Lays out a PDF of the article and title on this computer, in the look you pick. It needs no service and costs nothing. | Off |
+| **PDF look** | How the PDF looks: a ready look (**Plain**, **Book** or **Modern**), or one of your own PDF looks. **Edit PDF looks** opens the list. | Plain, or the channel's PDF look |
 
-A theme of yours is copied into the project when you pick it. Editing the theme later leaves this project alone until you pick it again, so a PDF already made or queued never changes by surprise. A channel's brand kit can set a **Document theme** for its videos whose template picks none; see [Channels](Channels).
+A look of yours is copied into the project when you pick it. Editing the look later leaves this project alone until you pick it again, so a PDF already made or queued never changes by surprise. A channel's brand kit can set a **PDF look** for its videos whose template picks none; see [Channels](Channels).
 
 ## What's in the PDF
 
@@ -28,11 +28,11 @@ In order:
 
 | Part | What it holds |
 |---|---|
-| **Title page** | The theme's brand name and tagline (if the theme sets them), the video's title, the project's thumbnail as a cover, then the date and word count. |
-| **Table of Contents** | Headings from the article, down to the level the theme sets (two levels in Plain), with page numbers. |
+| **Title page** | The look's brand name and tagline (if the look sets them), the video's title, the project's thumbnail as a cover, then the date and word count. |
+| **Table of Contents** | Headings from the article, down to the level the look sets (two levels in Plain), with page numbers. |
 | **Body** | The article: headings, paragraphs with a drop cap after headings, bold and italic, links, lists, quotes and rules. |
 | **Sources Consulted** | The article's "Sources Consulted" section, then any other web link cited in the research notes. Links stay clickable. |
-| **Closing page** | Optional: the theme's own lines, the document's details (written on, total words, total pages), a link and a closing line. Off in Plain. |
+| **Closing page** | Optional: the look's own lines, the document's details (written on, total words, total pages), a link and a closing line. Off in Plain. |
 
 Every page after the title page has a running header ("Brand | Title", or the title alone) and a page number in the footer.
 
@@ -49,9 +49,9 @@ The title page uses the project's thumbnail as its cover when:
 
 - the project makes or uploads a thumbnail (its Thumbnail source is not Off),
 - the thumbnail is a PNG, JPEG or WebP image, and
-- the theme's cover setting is on (it is in Plain).
+- the look's cover setting is on (it is in Plain).
 
-Otherwise the title page has no cover and the details sit in the theme's usual place. That includes a thumbnail step that failed or was canceled: the PDF is made anyway, without a cover. If you make the thumbnail later, the PDF is marked outdated, so you can remake it with the cover. If the thumbnail file can't be read, the Document stage stops and asks you to regenerate or upload the thumbnail again, then use **Try again** on Document.
+Otherwise the title page has no cover and the details sit in the look's usual place. That includes a thumbnail step that failed or was canceled: the PDF is made anyway, without a cover. If you make the thumbnail later, the PDF is marked outdated, so you can make it again with the cover. If the thumbnail file can't be read, the PDF stage stops and asks you to make or upload the thumbnail again, then use **Try again** on the PDF.
 
 ### Sources
 
@@ -62,39 +62,48 @@ Sources come from two places:
 
 When there are no sources, the Sources page is left out.
 
-## The Plain theme
+## The ready looks
 
-Plain is the one built-in theme: an unbranded A4 page on a warm off-white background, headings in dark blue, the Cinzel typeface for body and headings, a three-line drop cap after headings, a table of contents and a sources page, no closing page.
+Three looks come with Slopify, all unbranded A4 pages with a table of contents and a sources page and no closing page:
 
-To change fonts, colours, paper size (A4 or Letter), page parts and the closing page, make your own theme. See [Document-Themes](Document-Themes).
+| Look | What it looks like |
+|---|---|
+| **Plain** | A warm off-white page, headings in dark blue, the Cinzel typeface for body and headings, a three-line drop cap after headings. What a new project gets. |
+| **Book** | The article set like a novel in Literata on a parchment texture, Cinzel headings and drop caps in warm brown. |
+| **Modern** | A sans-serif on a white page, blue headings and no drop caps, like a report. |
+
+To change fonts, colors, paper size (A4 or Letter), page parts and the closing page, make your own PDF look. See [PDF looks](Document-Themes).
 
 ## Open and download the PDF
 
-On the project page, the **Document** section shows the theme's name (for example **Plain theme**) and, once the PDF is made:
+On the project page, the **PDF** part shows the PDF itself (where the browser can show PDFs) and, beside it:
 
-- **Open PDF** opens it in a new browser tab.
 - **Download PDF** saves the file to your computer.
+- **Open in a new tab** opens it in a new browser tab.
+- **Open folder** opens the project's folder.
+
+A line under them gives the file's size and the look's name (for example **Plain theme**).
 
-While the stage runs it says "The PDF will be saved when rendering finishes." The file lives in the project's folder; see [Where-Your-Files-Live](Where-Your-Files-Live).
+While the stage runs it says "The PDF will be saved when it is made." The file lives in the project's folder; see [Where-Your-Files-Live](Where-Your-Files-Live).
 
-## Change the theme of a finished project
+## Change the look of a finished project
 
-1. Open the project and press **Edit project**.
-2. Open **Inputs**. Under **Stages**, set the Document source to Generate if it was Off.
-3. Pick a **Document theme**.
-4. Save. The rebuild review lists the PDF to be made again; it costs nothing.
+1. Open the project and press **Edit settings**.
+2. Open **Extras**. Turn on **PDF of the article** if it was off.
+3. Pick a **PDF look**.
+4. Press **Save changes**, then **Make the PDF again (free)** (or the title row's next action).
 
 ## Tips
 
-- Use Library → PDF themes' live preview to try a theme on a sample article before you pick it for a project.
+- Use the live preview on the PDF looks page (Settings → Production defaults → PDF look → Edit PDF looks) to try a look on a sample article before you pick it for a project.
 - If a PDF has no cover, check that the project has a thumbnail and that it is a PNG, JPEG or WebP image.
 - Want the sources page filled? Make sure your Article prompt asks for a "Sources Consulted" section, and consider turning on research.
 
 ## Related pages
 
 - [Document-Themes](Document-Themes)
-- [Play-Outputs](Play-Outputs)
+- [Create: Extras](Create-Extras)
 - [Channels](Channels)
 - [Project-Page](Project-Page)
 - [Editing-a-Project](Editing-a-Project)
-- [Play-Title-and-Article](Play-Title-and-Article)
+- [Create: Article](Create-Article)

package/dist/tutorials/Posting-to-Social-Sites.md

@@ -2,16 +2,16 @@
 
 Slopify can get a project's post ready for **X, LinkedIn, Instagram, TikTok, Reddit and Bluesky**, beside its YouTube upload. Slopify prepares each site's post (its words, hashtags, link, pictures or video in the site's shape, and when it goes out). It never posts for you: there is no sign-in and no site API. The optional [Studio extension](Studio-Extension) fills each site's own post form in your browser, sets the site's scheduler where it has one, and turns the site's AI label on. You check the post and press **Post** yourself.
 
-**Where to find it:** a finished project → **Prepare upload** → **Where** (shown once the project posts to at least one site). A template's sites are set in **Library → Templates → Open studio → Upload pack**, or on Play under **Outputs**. Each channel's **Brand** tab holds its account names and X subscription.
+**Where to find it:** a finished project → **Copy for YouTube Studio** → **Where** (shown once the project posts to at least one site). A template's sites are set in **Templates → Edit template → YouTube description and posts**, or on Create in the **Extras** row under **Post to other sites**. Each channel's **Name and look** tab holds its account names and X subscription.
 
 ## Turn posting on
 
-1. Open the template in **Template Studio** and go to **Upload pack**.
+1. Open the template with **Edit template** and go to **YouTube description and posts**.
 2. Under **Post to**, turn on each site. Each one starts with the defaults below.
-3. Change the **text** and the **video** or **pictures** of each site there; hashtags, the thumbnail and the YouTube link are under **Fine-tune**.
-4. Press **Save**. A site whose words come from a post prompt is a paid step, so Save shows its price like any other (the **Posts** line).
+3. Change the **text** and the **video** or **pictures** of each site there; hashtags, the thumbnail and the YouTube link are in the section's fold (**More … settings**).
+4. Press **Save**. A site whose words come from a post prompt is a paid step, so the sample's **Make sample** shows its price like any other (the **Posts** line).
 
-A project or template with no site turned on works exactly as before: Prepare upload shows YouTube alone.
+A project or template with no site turned on works exactly as before: Copy for YouTube Studio shows YouTube alone.
 
 ### What each site gets by default
 
@@ -24,7 +24,7 @@ A project or template with no site turned on works exactly as before: Prepare up
 | Bluesky | The summary, two hashtags | Up to 4 pictures |
 | Reddit | A link post with the project's title | The YouTube link |
 
-## The post in Prepare upload
+## The post in Copy for YouTube Studio
 
 Choose a site under **Where**. Its panel shows, top to bottom:
 
@@ -41,17 +41,17 @@ Choose a site under **Where**. Its panel shows, top to bottom:
 | Summary | The keyword digest's summary when the run wrote one, otherwise the YouTube description's first paragraph (the default) | Free |
 | YouTube description | The description without its chapters and hashtags | Free |
 | Title | The video's title | Free |
-| Written by a post prompt | A post written from the article by a Library prompt of kind Post (or the built-in one) | One text-model call per site; it shows in the estimate as **Posts** |
+| Written by a post prompt | A post written from the article by one of your prompts of kind Post (or the built-in one) | One AI call per site; it shows in the estimate as **Posts** |
 | My own text | Your text, with `{{Slopify_Title}}`, `{{Slopify_Summary}}` and the other [keywords Slopify fills](Keywords-Slopify-Fills) | Free |
 | No text | Nothing | Free |
 
-A post prompt is a paid step, so it is picked in the template's Upload pack (or Play), where Save shows its cost. Prepare upload can switch a site between the free sources.
+A post prompt is a paid step, so it is picked in Edit template's **YouTube description and posts** (or on Create), where the estimate shows its cost. Copy for YouTube Studio can switch a site between the free sources.
 
 Hashtags come from the video's YouTube tags, then the shorts' hashtags, up to each site's most. The YouTube link is added, when asked, once the video is on YouTube. Text longer than the site takes is cut at the last whole sentence that fits, and the post says so.
 
 ## Pictures and video
 
-A post can carry the long video, one of the shorts, the thumbnail, any number of the project's pictures, and designs from **Library → Designs** kept in the project (its **Keep in project**), in any mix. Instagram's pictures are cut to 4:5 the first time they are needed; a design goes in its own format closest to the site's shape (portrait on Instagram, a story on TikTok, square elsewhere), drawn when the post needs it; shorts are already vertical; the long video is never re-encoded. Sites that don't mix a video with pictures (LinkedIn, TikTok, Reddit, Bluesky) get a warning rather than a refusal.
+A post can carry the long video, one of the shorts, the thumbnail, any number of the project's pictures, and the project's posters and edited images kept in it (**Posters and edited images…** under the project's status, then **Keep in project**), in any mix. Instagram's pictures are cut to 4:5 the first time they are needed; a design goes in its own format closest to the site's shape (portrait on Instagram, a story on TikTok, square elsewhere), drawn when the post needs it; shorts are already vertical; the long video is never re-encoded. Sites that don't mix a video with pictures (LinkedIn, TikTok, Reddit, Bluesky) get a warning rather than a refusal.
 
 ## Each site's limits
 
@@ -99,14 +99,14 @@ A Reddit post has its own **Subreddit** (without `r/`), **Title**, **Flair** and
 
 ## Your accounts and X subscription
 
-In **Channels** → your channel → **Brand** → **Posting**:
+In **Channels** → your channel → **Name and look** → **Posting**:
 
 - **X subscription** (Free, Premium or Premium+) only changes which warnings a post gets, such as the 280-character and 2 min 20 s limits of X Free.
 - **Account names** let the extension find a published post's link on your profile page. They are never used to sign in.
 
 ## Post prompts
 
-Write your own in **Library → Prompts**, kind **Post** (**Use Built-in Starter** fills in Slopify's own wording). Slopify gives it the site's length limit and asks again when the answer is over it, then adds the hashtags and link itself. Pick it for a site in Template Studio's Upload pack by choosing **Written by a post prompt** as its text.
+Write your own in **Prompts**, kind **Post** (**Start from an example** → **Slopify's own wording** fills in the wording Slopify uses). Slopify gives it the site's length limit and asks again when the answer is over it, then adds the hashtags and link itself. Pick it for a site in Edit template's **YouTube description and posts** by choosing **Written by a post prompt** as its text.
 
 ## Agents
 
@@ -116,6 +116,6 @@ Agents read and prepare posts (`get_post_packs`, `set_post_choice`, `edit_post_t
 
 - [Publishing to YouTube](Publishing-to-YouTube)
 - [Studio extension](Studio-Extension)
-- [Template studio](Template-Studio)
+- [Edit template](Template-Studio)
 - [Channels](Channels)
 - [Prompts](Prompts)