@gentbajko/slopify 3.25.9 → 4.1.0

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
@@ -99,16 +103,22 @@ To turn it off, clear the field and press **Save**.
 - [Agents](Agents-MCP) never see the address, only whether one is configured. They may set a new one.
 - In [Docker](Docker) the request goes out from the container, so the address must be reachable from there. `localhost` means the container itself.
 
+## Weekly report
+
+Settings → Notifications → **Weekly report** sends last week in one message to the Notification URL: how many videos were made, each failed step with its project and reason (the first ten, then a count), what it cost, and how much of each CLI plan's week is used. It goes out once a week, on Monday from 09:00 in this computer's time zone; if Slopify was off on Monday, it goes out the next time it runs that week. It needs a Notification URL. A send that fails is tried again 15 minutes later. Default: off.
+
+Home shows the same last 7 days under **Coming up** (see [Home and Projects](Home-and-Projects#autopilot)).
+
 ## 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

@@ -0,0 +1,121 @@
+# Posting to Social Sites
+
+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 → **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 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 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: Copy for YouTube Studio shows YouTube alone.
+
+### What each site gets by default
+
+| Site | Words | Media |
+|---|---|---|
+| X | The summary, two hashtags | The video |
+| LinkedIn | The summary, three hashtags | The video |
+| Instagram | The summary as the caption, five hashtags | Up to 10 pictures as a carousel, cut to 4:5 |
+| TikTok | The summary, five hashtags | Short 1 |
+| Bluesky | The summary, two hashtags | Up to 4 pictures |
+| Reddit | A link post with the project's title | The YouTube link |
+
+## The post in Copy for YouTube Studio
+
+Choose a site under **Where**. Its panel shows, top to bottom:
+
+- **Where it stands**: not filled yet, waiting for the extension, filled (press Post on the site), scheduled, posted, or why the fill stopped.
+- **Things to check**: what doesn't fit the site, each with its fix (text too long, too many pictures, a video too long for X Free, no subreddit, a release time the site can't schedule). A warning never stops you from filling the post.
+- **The post** as the site will show it: its words in an editable box, counted live the way the site counts them, and its media in the shape it is sent in. Your changes save when you leave the box and stay this project's own; **Reset to the written text** drops them.
+- **When it goes out** (see below).
+- **Settings**: the text source, video, pictures, designs, hashtags, thumbnail and YouTube link for this project. A change here is this project's own; **Use the template's settings** goes back.
+
+## Where the words come from
+
+| Text | What it posts | Cost |
+|---|---|---|
+| 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 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 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 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
+
+Slopify counts the way each site does: X counts a link as 23 characters and CJK characters and emoji twice, Bluesky counts characters as you see them, the others count plainly.
+
+| Site | Text | Pictures | Video | Video and pictures together | Seen on the site |
+|---|---|---|---|---|---|
+| X Free | 280 | 4 | 2 min 20 s | Yes | Not yet |
+| X Premium, Premium+ | 25,000 | 4 | 3 h | Yes | Not yet |
+| LinkedIn | 3,000 | 20 | 15 min | No | Not yet |
+| Instagram | 2,200 | 20 | 15 min | Yes | 2026-10-18 |
+| TikTok | 4,000 | 35 | 60 min | No | 2026-10-18 |
+| Bluesky | 300 | 4 | 3 min | No | 2026-10-18 |
+| Reddit | 40,000 (title 300) | 20 | 15 min | No | Not yet |
+
+## When it goes out
+
+The post follows the YouTube item it carries: a short's own release time when it carries a short, else the long video's.
+
+- **X, LinkedIn and TikTok** have their own scheduler. The extension sets it to the release time; you press **Schedule**. Outside the site's window (TikTok takes about 15 minutes to 10 days ahead, LinkedIn about 3 months), or after the release time, it leaves the post to go out now, and the post says why.
+- **Instagram, Bluesky and Reddit** have none. Pressing **Fill** before the release time makes the post wait: about 2 minutes before the release time, the extension opens the site in a background tab, fills the post and shows a notification (and calls your [Notification URL](Notifications), when one is set); you press **Post**. If the browser was closed, it fills when it opens again, up to 12 hours late.
+- With no release time, or one already past, the post goes out when you press **Post**.
+
+## Fill in a site
+
+**Fill in X** (and each other site) is the drawer's main button while that site is chosen. It opens the site's post form and hands the post to the extension. It stays disabled, with the reason beside it, until:
+
+- the Slopify Studio extension is installed and paired (**Settings → YouTube Studio and posting**);
+- the extension is new enough to post; and
+- the site is allowed in the extension's options (**Allow posting on X**, and so on).
+
+The extension only fills a tab that Slopify opened: the one **Fill in X** opens, or the background tab it opens at release time. A site's page you open yourself is never filled or touched. The extension never presses Post, Share, Publish or the final Schedule.
+
+## AI labels
+
+Instagram's **Add AI label**, TikTok's **AI-generated content** and X's content disclosure are always turned on for a post that carries Slopify's pictures or video. LinkedIn, Bluesky and Reddit have none.
+
+## After it is posted
+
+When the site shows the published post, the extension reads its link and the panel shows **Posted** with **Open the post**. When it can't, it looks the post up on your profile (the account names below). When you posted it yourself, or the link was missed, paste it under **Posted it yourself? Paste its link**; only the site's own post links are taken. **Remove link** lets the post be filled again.
+
+## Reddit
+
+A Reddit post has its own **Subreddit** (without `r/`), **Title**, **Flair** and **Post type** (Link, Text or Media). Reddit refuses a post without a subreddit, so the post warns until one is set. Reddit's post form hasn't been checked in a real browser yet (**Needs a live check**): the title, subreddit and text go in through Reddit's own submit address, but check the media and flair before you press Post.
+
+## Your accounts and X subscription
+
+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 **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
+
+Agents read and prepare posts (`get_post_packs`, `set_post_choice`, `edit_post_text`, `reset_post_text`, `set_reddit_post`, `set_post_link`) and report a post waiting for your Post. They can't press Fill and can't post. See [Agents (MCP)](Agents-MCP).
+
+## Related pages
+
+- [Publishing to YouTube](Publishing-to-YouTube)
+- [Studio extension](Studio-Extension)
+- [Edit template](Template-Studio)
+- [Channels](Channels)
+- [Prompts](Prompts)