Scriptwriting in Obsidian With the Fountain Plugin  🔗 **Source:** [Scriptwriting in Obsidian With the Fountain Plugin](https://www.youtube.com/watch?v=5OfvmyuJwm8) > [!note]+ Document Notes > tags: [obsidian, obsidian-plugins, screenwriting, fountain-format, writing-tools] > author: PrattDesign > source: YouTube, PrattDesign channel > reference: https://www.youtube.com/watch?v=5OfvmyuJwm8 > date created: 2026-10-02 11:00 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > # 🏷️ Title: Scriptwriting in Obsidian with the Fountain Plugin > <!-- deep-read:sections start --> ## 🧭 Table of contents - [📝 Summary](#-summary) - [📖 Main content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning styles assessment](#-learning-styles-assessment) - [📊 Accessibility assessment](#-accessibility-assessment) - [🌍 DEIB assessment](#-deib-assessment) - [✅ Logical validity](#-logical-validity) - [🛡️ DARVO analysis](#️-darvo-analysis) - [🎯 Conclusion](#-conclusion) - [🔄 Refactor appendix](#-refactor-appendix--scriptwriting-in-obsidian-with-the-fountain-plugin) How to read this note. The source is a video tutorial transcript, not a written article. The pipeline split the captions into 7 paragraphs labeled ¶1 to ¶7, and each paragraph carries inline `[m:ss]` stamps from the video. This note cites both: ¶ labels for where text sits in the capture, and stamps such as [2:56] for where it sits in the video. The video runs 6:52 and the capture holds about 1,260 words. Captions are auto-generated, so names and plugin titles may be garbled. Facts about the plugin's current state and the Fountain spec come from an earlier check dated 2026-09-14 that this rewrite carries forward. No network was used for this rewrite, so those facts are not re-verified today. ## 📝 Summary - **What happened.** On the PrattDesign YouTube channel, the narrator walks through installing the Obsidian community plugin named "Fountain" and writing a first screenplay-format script with it (¶1 to ¶7). The video runs 6:52. The earlier check logged the upload date as 2025-09-23, which this rewrite cannot confirm (the capture holds no date). The narrator signs off at [6:33] as "Mark with Pratt Design" (¶7, caption spelling, unverified). - **The claim.** Obsidian can host script writing in the Fountain plain-text format, and the plugin adds index cards, a scene outline, rehearsal mode, inline notes and synopses (¶3 to ¶6). The narrator calls it "great for people who prefer to work with scripts" (¶6) and names two limits: scripts aren't linkable and the narrator doesn't think their properties can be edited (¶6). - **Why it matters.** Fountain keeps a script as plain text. The plugin turns that text into one index card per scene, which gives a screenwriter, or anyone scripting a video or talk, a structured outline inside the same vault as research notes (¶5). - **Key stakeholders.** The narrator and the PrattDesign channel; the plugin's maintainer (the earlier check lists registry author bgrundmann, GitHub display name Benedikt Grundmann; the captions spell it "Benedict Grindman" and "Benedict Gruntman"); the author of the other registry match, "Fountain Editor" (captions: "Chang Caleb"); and viewers who own or want the narrator's "Novel Vault" (¶1). - **Risks and tradeoffs.** The video is a single-voice tutorial that promotes a vault product (see Logical validity). It leaves out 2 Fountain parsing rules the steps depend on: uppercase character cues and `INT`/`EXT` scene headings. It skips export. Its "not linkable" warning has partly aged out per the earlier check. - **Bottom line.** The typing workflow in ¶3 and ¶4 is sound once you uppercase the character cue and give each scene a proper heading. The index cards, rehearsal mode and synopsis display are shown on screen and described in plain terms (¶5, ¶6). Treat the link and properties limits (¶6) as dated: the earlier check found script-to-vault links added in plugin release 0.27.0 (2026-05-01), while backlinks and graph view still don't show them. ## 📖 Main content **What the video is.** This is a screen-recorded tutorial. The narrator works inside a "Novel Vault," which the narrator describes as similar to a vault called "Disgraceland" (caption spellings "disgraceand" and "Disgrace Land") but "a bit more streamlined" and "not as set up for world building" (¶1, [0:00] to [0:38]). The vault is "more streamlined for novel writing and script writing." The narrator says viewers asked how to set up the plugin and write "proper script pages" in Fountain format (¶1). The text doesn't say whether the Novel Vault is free or paid. Treat the vault as the narrator's own product until the channel page says otherwise (inference). **The terms.** - **Fountain.** A plain-text markup for screenplays. The format is defined at fountain.io, and the earlier check compared the video against its syntax page. - **Index cards.** The plugin's card view of a script, one card per scene, with a scene title you can edit on the card (¶3). - **Scene heading.** In the Fountain spec, a line beginning `INT`, `EXT` or a similar prefix, or forced with a leading `.`. The narrator uses "scene heading" for the first line and calls it where you put "your action or your uh scene description" (¶3). The spec treats scene heading and action as 2 elements, so the narrator's wording blends them. - **Synopsis.** A line starting with `=`. Per the narrator, it shows on the scene's index card (¶6). - **Note.** Text in double brackets, for example `[[this character should have more lines]]` (¶5). - **Rehearsal mode.** A view that blocks out the dialogue of one chosen character (¶5). **The procedure the narrator follows.** The narrator gives these steps in order, with video times: 1. Open Settings, then Community plugins, then Browse, and search for "fountain" ([0:38], ¶1). Two plugins come up (¶1, [1:00]). 2. Install the first one, "Fountain by Benedict Grindman" (caption spelling), and skip "Fountain Editor by Chang Caleb" (¶2, [1:00]). The narrator notes the plugin is already installed in the Novel Vault, so Novel Vault owners can skip this step (¶2). 3. Click "new fountain document" in the sidebar. An untitled document opens, and the narrator has to look for where it saved ([1:28], ¶2). 4. Click the eyeball (view options) icon at the top right and choose index cards ([2:01], ¶3). 5. On a card, click the three dots and choose Edit to open the script editor ([2:30], ¶3). 6. Type the description line. The narrator types "a nice hot summer day in the city" ([2:30], ¶3). 7. Press Enter twice, type the character name, press Enter once, then type the dialogue ([2:56], ¶4). The narrator says the order stays the same "the whole way down" (¶4). 8. To add another speaker, repeat the blank line and cue. To start a new scene, press Enter twice and type the next scene's text ([3:33], ¶4). 9. Open the table of contents of the script in the side panel, then go back to index cards to see one card per scene ([3:33] to [4:13], ¶4 and ¶5). 10. For rehearsal, open the eyeball menu, choose rehearsal and pick a character; that character's dialogue is blocked out ([4:13], ¶5). 11. For notes, wrap text in double brackets ([4:48], ¶5). 12. For a synopsis, start a line with `=`. Repeat the `=` on each extra line ([4:48] to [5:19], ¶5 and ¶6). Only the top synopsis shows on the card (¶6). **What the narrator says about limits.** At [5:59] the narrator says the Novel Vault contains directions, a script notes page and a sample script (¶6). Then comes the main caveat: "You can't directly link to this note." They add "I don't believe I can also edit the properties to this page" (¶6). The narrator hedges both ("as far as I can tell," "I don't believe"), so the capture presents them as unconfirmed observations, not documented facts. **What the narrator says about when to use it.** The tool suits "people who prefer to work with scripts" (¶6). For long-form chapter writing, which the narrator calls "tried and true" (caption "triedand-true," ¶7), ordinary Obsidian notes remain available (¶7). **Caption problems that affect meaning.** - **Plugin names.** "Benedict Grindman," "Benedict Gruntman" (¶2) and "Chang Caleb" (¶2) are likely garbled. The earlier check matched them to registry entries `fountain` (author bgrundmann, GitHub display name Benedikt Grundmann) and `fountain-editor` (author Chuang Caleb). Confirm the author on the install screen before you install, since two plugins share the search results. - **Vault names.** "Disgraceand" and "Disgrace Land" are the same word spelled two ways (¶1, ¶2). The capture can't settle the correct form. - **Case.** Captions drop capital letters. "character one" (¶4) says nothing about whether the narrator typed uppercase, which Fountain requires for a character cue. - **The word "synopsises"** (¶5, ¶6) appears as spoken. The plural of synopsis is "synopses." **Carried-forward checks from 2026-09-14 (not re-verified today).** - **Syntax.** Fountain requires a character line to be entirely uppercase or forced with `@`. A scene heading needs `INT`, `EXT` or `.`. A plain description line parses as action. Notes in double brackets and synopses with `=` match the spec. - **Plugin state.** At the earlier check, plugin version 0.34.3 had shipped on 2026-08-29. Release 0.27.0 (2026-05-01) added `[[>target]]` links from scripts to vault files. The plugin's README says `.fountain` links don't appear in the backlinks pane or graph view because Obsidian's plugin API doesn't expose link metadata for non-markdown file types. PDF export has been in the plugin since release 0.9.0 (2025-09-04). - **Properties.** Scripts are `.fountain` files, not markdown. The README doesn't mention properties or frontmatter, so the narrator's claim at [5:59] could be neither confirmed nor refuted. - **Upload date.** The 2025-09-23 date came from the lead agent's log and was not confirmed through a YouTube API. Treat it as unverified. **Uncertain or contested in this source.** The two limits at [5:59] are the narrator's uncertain claims. The video doesn't say which plugin version appears on screen, so the steps can't be matched to a specific release. Whether "new scene" at [3:33] carried an `INT`/`EXT` prefix isn't stated, and the capture holds no video frames. ## 🗒️ Notes #### 📄 ¶1 Purpose, vault context and where to start - The narrator sets up the plugin "within the new Novel Vault" because "some people" asked how to create script pages in Fountain format in Obsidian ([0:00]). - The Novel Vault is described as similar to Disgraceland, "more streamlined" and aimed at novel and script writing instead of world building ([0:38]). - First action: Settings, Community plugins, Browse, search "fountain." Two results appear right away ([0:38]). #### 📄 ¶2 Choosing the plugin and creating a document - The two results are "Fountain by Benedict Grindman" and "Fountain Editor by Chang Caleb" in the captions. The narrator downloads the first ([1:00]). - The plugin already ships in the Novel Vault, so owners "don't need to follow these steps." The install is for someone adding script writing to Disgraceland or a personal vault ([1:00]). - At [1:28] the narrator clicks "new fountain document" in the sidebar. An untitled document opens, then the narrator asks "where did this save?" and finds it. The capture gives no save location. #### 📄 ¶3 Index cards, editor and the first line - The eyeball icon at the top right opens view options. Choosing index cards opens the first card, where "we can set up scenes" ([2:01]). - On a card you can click the scene heading to change the title. The three-dot menu has an Edit command that opens the script layout page ([2:30]). - The first line is called a scene heading and described as "your action or your uh scene description." The narrator types a nice hot summer day in the city ([2:30]). #### 📄 ¶4 Typing order and the outline - The sequence: description, Enter twice, character name, Enter once, dialogue. The narrator says it repeats "the whole way down" ([2:56]). - A second speaker is "character 2." To end a scene, Enter twice and type "new scene," then a third character with "Hello" ([3:33]). - The side panel has a table of contents for the script that "lays out your scenes." Switching back to index cards follows ([3:33]). #### 📄 ¶5 Cards, rehearsal mode, notes and synopses - Two scenes now show as 2 index cards, "a nice breakdown of your individual scenes" ([4:13]). - Rehearsal: eyeball, rehearsal, pick a character. The chosen character's dialogue is "blocked out" ([4:13]). - Notes use double brackets, for example about a character needing more lines ([4:48]). - For synopses, press Enter twice, type `=` and the synopsis text ([4:48]). #### 📄 ¶6 Multi-line synopses, sample material and limits - A synopsis can run over several lines, each starting with `=` ([5:19]). - The synopsis text shows on the scene's index card. A scene can hold several synopses but "only the top one" shows on the card ([5:19]). - The Novel Vault includes a directions page, a script notes page and a sample script ([5:59]). - Limits at [5:59]: not linkable "as far as I can tell," and the narrator doesn't believe properties can be edited. The narrator still calls the format "fantastic" for writing. #### 📄 ¶7 Closing - Long-form chapter writing in standard Obsidian notes stays available for people who prefer it ([6:33]). - Sign-off as "Mark with Pratt Design" (caption spelling, unverified). The video ends at 6:52. ## 📚 References The captured link list is empty. No link in the captured markup points to any source for this video, and the transcript names none by URL. The entries below are primary sources for entities the narrator names, taken from the 2026-09-14 check. They are not links the author supplied. - [The video itself](https://www.youtube.com/watch?v=5OfvmyuJwm8): the source analyzed here. Title, channel and the 6:52 runtime come from the earlier check, which confirmed the title and channel through oEmbed only. - [Fountain syntax](https://fountain.io/syntax/): the format spec the earlier check used for scene headings, character cues, notes and synopses. - [Fountain plugin repository and README](https://github.com/bgrundmann/obsidian-fountain): the plugin the narrator installs (registry id `fountain`). The README documents rehearsal mode, index cards, the 0.27.0 link syntax and the backlink limit. - [Fountain Editor repository](https://github.com/chuangcaleb/obsidian-fountain-editor): the plugin the narrator skips. The earlier check found it styles ordinary markdown notes marked `.fountain.md`, a `fountain` tag or `cssclasses: fountain`. - [Obsidian community plugin registry](https://raw.githubusercontent.com/obsidianmd/obsidian-releases/master/community-plugins.json): the listing the earlier check used to match caption names to author handles. - Claims with no link in the captured markup: every statement the narrator makes, including the two limits at [5:59]. The Novel Vault and Disgraceland vaults have no link in the capture. ## 🗣️ Paraphrase The narrator explains how to add the Fountain plugin to an Obsidian vault and write a short script with it. After installing it from the community plugin browser, you create a new Fountain document, open the card view, and choose Edit on a card to get the text editor. The format works by typing in a fixed order: a description, a blank line, a character name, then the dialogue on the next line. A blank line starts the next block or scene. Each scene then appears as its own index card, and a side panel lists the scenes as an outline. Three extras get a quick demo. Rehearsal mode hides one character's lines so an actor can practice. Double brackets add private notes inside the script. A line that starts with an equals sign becomes a synopsis that shows on the scene's card, and only the first synopsis shows. The narrator says scripts can't be linked to and may not allow property edits, then points anyone who likes chapter-style writing back to normal notes. ## 📰 Newsletter **Script it in Obsidian: a 7-minute tour of the Fountain plugin.** If your next talk, video or screenplay lives in a WordPress-adjacent project folder, here's a short tutorial from the PrattDesign channel that shows how Obsidian handles screenplay format. Install the Fountain community plugin, open a new `.fountain` document, and type description, blank line, character name, dialogue. The plugin turns each scene into an index card, lists scenes in a sidebar outline, and has a rehearsal view that hides one speaker's lines. Two things to know before you start. The tutorial doesn't mention that character names need to be uppercase and scene headings need `INT`/`EXT` or a leading dot, so add those. And the "can't link to scripts" warning at the end is partly out of date: an earlier check found script-to-vault links added in release 0.27.0, though backlinks still skip them. Links: [the video](https://www.youtube.com/watch?v=5OfvmyuJwm8), [the Fountain syntax guide](https://fountain.io/syntax/) and [the plugin on GitHub](https://github.com/bgrundmann/obsidian-fountain). ## ✅ Action items Each line ties to the video or says plainly that no action follows. #### DevRel - Developer advocacy: if you script demo videos or talks, try one segment in Fountain: a `# Section` per act, a `= synopsis` per segment, an uppercase speaker cue per speaker. This is an idea built on the tutorial's steps (¶4 to ¶6), not something the narrator suggests. - Education: a short walkthrough could reuse the narrator's order of steps, listed in Main content, and add the 2 rules the video skips (uppercase cues, `INT`/`EXT` headings). - Developer experience: no direct action. The tutorial is about a note-taking plugin, not an SDK. - Developer marketing: none from this source. The video promotes the narrator's vault, and the capture gives no funnel or attribution detail. - Community management: when someone asks "how do I script in Obsidian?", link the plugin README and the Fountain spec in addition to the video. - Internal/external/cross-project: none from this source. #### OSPO - Policy and governance: none. The video makes no policy claim. - License compliance: none from this source. The earlier check listed the plugin as MIT-licensed, which an OSPO would confirm before internal use. - Security management: a community plugin runs inside the vault with the vault's file access. Review a plugin's source and maintainer history before installing it on a work vault (general practice, not stated in the video). - Software inventory: none. - Developer support: none. - Community engagement: none from this source. - Strategic alignment: none. #### Community - Maintainers: the plugin's issue tracker shows an open request for backlink support (carried from the earlier check). Anyone who wants that feature can add a use case there. - Contributors: none from this source. - Sponsors: none. The video mentions no sponsorship. - Ecosystem: none from this source. #### WordPress - Core: no direct action. The video doesn't touch WordPress. - Core Performance: none. - Core AI: none. - **Core Program Team:** none. - Mobile: none. The video shows desktop use only and doesn't mention mobile. - Playground: none. - Community: no direct action. Nearest relevance: WordCamp speakers who draft talks in Obsidian could try Fountain for talk scripts (inference). - Training: none. The numbered procedure in Main content could seed a lesson on scripting video lessons, but that is an idea. - Marketing: none. Don't cite the video as an endorsement of any vault product. - Support: none. - Design: none. - Documentation: none. A docs team that writes video narration could test Fountain for screen-recording scripts (inference). - Photos: none. - TV: nearest relevance: WordPress.tv speakers could draft talk scripts with a rehearsal view. The video doesn't mention captions or talks. - Polyglots: none. - Accessibility: none from this source. See the Accessibility assessment for the video's own gaps. - Meta: none. - CLI: none. - Hosting: none. - Tide: none. - Openverse: none. - Themes: none. - Plugins: none. The plugin discussed is an Obsidian plugin, not a WordPress plugin. #### The WPOCC - Programs: none directly. - Projects: none. - Funding experiments: none from this source. ### FAIR - Technical independence: none. The video says nothing about signing or provenance. - Policies and covenants: none from this source. - Productized governance artifacts: none from this source. ## 🧪 Hypotheses 1. A first-time user who follows the video's steps exactly (¶3, ¶4) and types the character cue in lowercase gets dialogue that doesn't parse as dialogue in at least one common Fountain tool, because the spec requires an uppercase cue. 2. A "New scene" line without an `INT`/`EXT` or `.` prefix doesn't create a heading, so the second index card in the demo (¶5) reflects either an unseen prefix or a plugin behavior different from the spec. 3. Rehearsal mode (¶5) blocks lines only for speakers whose cues are consistently spelled, so a script that varies a cue ("HOST" and "HOST (V.O.)") would need extra setup. 4. The "can't link to this note" limit (¶6) is no longer true for links out of a script in current plugin versions, and remains true for backlinks. 5. A hub markdown note beside each script gives a writer the properties and backlinks that a `.fountain` file can't hold. 6. Users who prefer chapter-style prose (¶7) gain little from index cards, while users who think in scenes gain a measurable drop in the time needed to reorder scenes. ## 📊 Methodology - **H1.** Create a script that follows ¶4 exactly with a lowercase cue, open it in the plugin and one reference Fountain editor, and record how each tool classifies the line. Repeat with an uppercase cue as a control. - **H2.** Type "new scene" with and without a `.` prefix and count the index cards produced. Compare against the plugin version on screen when the video was recorded. - **H3.** Write a 3-speaker script with 2 spellings of one cue, run rehearsal mode on each spelling, and record which lines are blocked. - **H4.** In the current plugin release, add a `[[>target]]` link in a script, then check the target note's backlinks pane and graph view. Check separately that renaming the target rewrites the link. - **H5.** Build the hub-note pattern for 3 scripts. Count which of properties, backlinks and graph edges work for the script versus the hub. - **H6.** Ask 6 to 10 writers to reorder 12 scenes using cards and using plain text. Time both. Small sample, so report it as a pilot. - **Controls throughout.** Same vault, same plugin version, and a note of the Obsidian version used. Log the version, since the video doesn't say. ## ❓ Questions - Which plugin release is on screen in the video, and does the eye-icon-to-three-dots path in ¶3 still exist in the current release? - Did the narrator type uppercase character cues, given the captions drop case (¶4)? - Did the "new scene" line at [3:33] carry an `INT`/`EXT` prefix, since the capture holds no frames? - Where do new `.fountain` files save by default? The narrator had to search for the file at [1:28]. - Is the Novel Vault a free or paid product, and does the channel link to it in the description (not in the capture)? - Can a `.fountain` file take properties through any plugin setting, as the narrator wonders at [5:59]? - How does the plugin handle PDF export for a script drafted by following this video, which never mentions export? - What does Fountain Editor offer that the first plugin doesn't, given the narrator skips it (¶2)? ## 🔮 Future research - **Version-pinned replay.** Re-run the video's steps in the current plugin release and log each place where the UI differs. This turns the tutorial into a dated test script. - **Non-screenplay scripts.** Test Fountain for talks, video narration and podcasts. The demo uses film-style scenes only, so the fit for single-speaker content is unproven. - **Plugin comparison.** The registry lists other screenplay-related plugins (Longform, Screenwriter, Final Craft, Colophon per the earlier check). A feature table would show where each fits. - **Linking and properties workarounds.** Document the hub-note pattern, and compare it against styling Fountain syntax inside markdown notes with Fountain Editor. - **Mobile and sync.** The video doesn't cover phone use, sync, or conflicts. Test across devices before moving a real script. - **Export fidelity.** The earlier check found the README warns that the PDF output may not follow industry standards. Compare against a reference tool for page count and layout. ## 💡 Implications - **Practice.** A scriptwriter who already lives in Obsidian can keep drafts, research and outline in one vault. The cost is two parsing rules to learn and a manual hub note for links and properties. - **Policy.** None stated. A team that stores scripts for client work can decide whether `.fountain` files belong in its vault conventions, since they sit outside the markdown property system. - **Security.** The plugin is third-party code. The video offers no vetting advice, so apply the usual review of maintainers, source and permissions before installing (general practice). - **Education.** The numbered procedure makes a short classroom exercise: write 2 scenes, view the cards, run rehearsal mode. Teach the uppercase cue rule at the first step. - **Funding.** The video says nothing about funding. The only commercial hint is the narrator's own vault (¶1), and the capture gives no price or sponsor. ## 🧠 Learning styles assessment - **Reading level estimate.** Flesch-Kincaid Grade Level is about 5.0 and Flesch Reading Ease is about 84, computed over the 1,260-word capture with a rough syllable counter. Spoken captions have no true sentence boundaries, so I split on captioned punctuation (about 90 pieces). Treat both numbers as indicative. #### 👀 Visual learners - Present: a screen recording shows every click and the index cards, the table of contents and the blocked-out rehearsal view (¶3 to ¶5). The capture preserves none of it, so a text-only reader sees only narration. - Improve: add captioned screenshots of the three view options, and a before/after of a typed script next to its cards. #### 🔊 Aural learners - Present: the whole video is narrated speech, 6:52 long. - Improve: the narration relies on pointing ("this icon here," ¶2), which an audio-only listener can't follow. Spoken labels would fix that. #### 🗣️ Verbal learners - Present: the narrator explains the typing order in a single reusable sentence (¶4) and defines synopses and notes by example. - Improve: add a glossary for scene heading, action, character cue and synopsis, because the narration blends scene heading and description (¶3). #### 🧩 Kinesthetic learners - Present: the video is a follow-along walkthrough with 12 discrete steps, listed in Main content. A viewer can pause and repeat each one. - Improve: supply a small starter script file with deliberate mistakes (lowercase cue, missing `INT`) to fix. #### 🧠 Logical learners - Present: the typing order has a clear rule set: description, blank line, cue, dialogue (¶4). The outline view follows the same logic. - Improve: state the grammar fully, with the 2 missing rules, so a viewer can predict how any line parses. #### 🧑‍🤝‍🧑 Social learners - Present: the narrator opens by answering viewer questions (¶1), which shows an audience loop. - Improve: a pinned comment thread or a template repository for questions. The capture mentions neither. #### 🧘‍♀️ Solitary learners - Present: self-paced and pausable. The Novel Vault ships a directions page, a script notes page and a sample script (¶6). - Improve: a self-check such as "How many cards should the sample produce?" and a worksheet for the 3 element types. #### 🌿 Naturalistic learners - Present: nothing relevant. The video is about a software workflow. - Improve: none needed for this topic. ## 📊 Accessibility assessment Judged as captured. The capture is auto-generated captions split into 7 paragraphs. I can't see the video, its player, its description or its chapters, so most items below are "unknowable from the capture." #### Screen reader semantics - Present: the transcript text is readable in order as 7 labeled paragraphs with inline `[m:ss]` stamps. - Improve: the narration says "this icon here" and "right here" (¶2, ¶3) without naming the UI element, so a listener can't recover what was clicked. WCAG 1.1.1 (Non-text Content) and 1.2.5 (Audio Description, Prerecorded) apply to the on-screen steps. Headings and landmarks of the YouTube page aren't visible in the capture. #### Keyboard navigation - Present: not assessable from the captured text. The YouTube player's keyboard support isn't in the capture. - Improve: the video demonstrates mouse clicks only. The earlier check found the README documents a keyboard toggle between cards and editor (Cmd/Ctrl+Shift+I), and the video doesn't mention it. A keyboard-only viewer gets no path (WCAG 2.1.1, Keyboard, for the tool, not the video). #### Contrast and readability - Present: unknowable from text. Colors in the Obsidian theme on screen aren't captured. - Improve: caption quality matters here. The captions drop capitalization and mangle names (¶2), which hurts readability. #### Text resizing and reflow - Present: the transcript reflows as plain text. - Improve: the video frame is fixed, so small UI text can't be enlarged without zooming the player. WCAG 1.4.4 (Resize Text) and 1.4.10 (Reflow) can't be checked from the capture. #### Media and captions - Present: the capture is auto-generated captions with inline stamps, so captions exist. Whether they are author-edited isn't stated. The capture notes no audio description or separate transcript download. - Improve: correct the plugin and vault names, restore case so uppercase cues are visible, and add audio description for the on-screen clicks. WCAG 1.2.2 (Captions, Prerecorded) needs accurate captions. 1.2.5 needs description of visuals the narration doesn't cover. #### Forms and interactions - Present: none in the capture. The tutorial describes Obsidian's settings and plugin browser, which are application UIs. - Improve: the narrator doesn't say whether the plugin's views are screen-reader or keyboard accessible, and I haven't tested them. Try them before recommending to a team. #### Standards reference - Candidate gaps against WCAG 2.2 AA, each unverified: **1.1.1** (on-screen steps rely on visuals), **1.2.2** (caption accuracy: garbled names, no case), **1.2.5** (no description of visual steps), **1.4.4** (fixed-size video frame), **2.1.1** (steps shown with the mouse). ## 🌍 DEIB assessment #### Cultural breadth - Present: Fountain is an English-language screenplay convention drawn from film. The demo uses English text only. - Improve: show a script in another language. The video doesn't say whether the plugin handles non-Latin text. That's a question, not a finding. #### Inclusive language - Present: the narrator uses neutral language and "people who prefer to work with scripts" (¶6). The capture holds no gendered terms for people. - Improve: define jargon on first use (scene heading, synopsis, index cards) and use "synopses" for the plural. #### Neurodiversity support - Present: a predictable, repeated typing pattern (¶4) and a short runtime of 6:52 chunked by task. - Improve: the narrator talks fast, backtracks ("Whoops," ¶4) and points at the screen. On-screen step titles and a written step list would reduce load. #### Representation - Present: the capture names one speaker, who signs off as "Mark" (¶7, caption spelling, unverified). It names the plugin maintainer and a second plugin author only through garbled captions. - Improve: none for a software tutorial. The demo has placeholder characters ("character one," "character two") with no identity cues. #### Psychological safety - Present: the tone is friendly and invites viewers to follow along. The narrator frames limits as "roadblocks" without blaming the tool (¶6). - Improve: invite viewers to share mistakes, and note which steps are optional so beginners don't think they've failed. ## ✅ Logical validity Source type: a promotional-adjacent software tutorial in one voice. It's instruction and advocacy, not an argument. The narrator promotes the Novel Vault (¶1) and the plugin (¶6), and the capture doesn't state whether the vault is sold. Read "great tool to use" (¶2) and "fantastic" (¶6) as the narrator's opinion. #### Strong reasoning - **Clear procedure, ¶4 ([2:56]).** The narrator gives one repeatable rule for typing and says it holds "the whole way down." This is a clean generalization that a viewer can test in under a minute. - **Demonstration over claim, ¶5 ([4:13]).** The narrator shows two scenes becoming two cards, and shows a character's dialogue blocked in rehearsal mode. The evidence is on screen, though the capture holds only the narration. - **Calibrated caveats, ¶6 ([5:59]).** "As far as I can tell" and "I don't believe" mark the limits as unconfirmed, which is more accurate than stating them as fact. #### Fallacies - **Hasty generalization / incomplete rule, ¶4 ([2:56]).** "It'll be the same the whole way down" omits that a character cue must be uppercase and that headings need a prefix. Why weak: a viewer who copies the order but not the case may see lines fail to parse. Fix: state the 2 rules at the first typing step. - **Equivocation on terms, ¶3 ([2:30]).** The narrator calls the first line a "scene heading" and the place for "your action or your uh scene description." The spec treats them as 2 elements. Fix: name each element separately. - **Appeal to convenience without evidence, ¶6 ([5:59]).** The limits are stated from a quick trial, with no check of the plugin's docs. Fix: link the README for current behavior. - No other fallacy found. Checked: all 7 paragraphs for causal, authority and false-dilemma claims, and found none beyond the points above. #### Tone of voice - Casual, friendly and conversational, with filler ("uh," "um," "Whoops," ¶4) and a warm sign-off ("we'll see you down the road," ¶7). The tone is that of a creator speaking to existing viewers ("people more familiar with Disgraceland," ¶1). ## 🛡️ DARVO analysis Not applicable to this source. DARVO describes a response to an accusation, and this tutorial responds only to viewer questions about setup (¶1). **Deny:** the narrator denies nothing and meets no accusation. **Attack:** no person, plugin author or competing tool is attacked; the narrator skips the second plugin without criticizing it (¶2). **Reverse victim/offender:** no such move appears. The "roadblocks" at [5:59] are described as tool limits, not blame. ## 🎯 Conclusion The video shows a 12-step path from installing the Fountain plugin to a script with index cards, rehearsal mode, notes and synopses, all inside Obsidian. The steps match the Fountain format, with 2 corrections the narrator never states: uppercase character cues and `INT`/`EXT` scene headings. The "not linkable" and "can't edit properties" caveats at [5:59] come with hedges, and the earlier check found script-to-vault links added in release 0.27.0 while backlinks and graph view still skip them. The source is a single-voice tutorial that also promotes the narrator's Novel Vault. Plugin and vault names in the captions are garbled, the upload date and plugin version aren't confirmed, and this rewrite didn't re-check any external fact. **Next steps for readers:** confirm the plugin author on the install screen before installing, uppercase every character cue, give each scene an `INT`/`EXT` or `.` heading, test export on a short script before moving real work over, and keep a markdown hub note beside the script for properties and backlinks. ## 🔄 Refactor Appendix — Scriptwriting in Obsidian with the Fountain Plugin > Density: 2–5 Literature atoms (H1 pad), 0–3 Permanent candidates (H4 pad). > Emitted: 4 Literature, 2 Permanent. Resonance filter applied: the sign-off, the vault pitch > and the install-screen detail were dropped as procedural or promotional. > > Konik claim-header rules: present tense, declarative, ≤10 words, searchable, unique. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Split Pad #### [H1] Fountain scripts follow one fixed typing order > [!quote] [¶4] > The description, hitting enter twice, the character name, hitting enter once will create the dialogue and it'll be the same the whole way down. **Context & use**: - ¶4, [2:56]. The core rule of the tutorial. - The captions drop case, so the rule as spoken omits the uppercase requirement for the cue. Add it when you reuse this. **Tags**: #xref #share <!-- atomicity: 1 idea ✓ --> #### [H2] Rehearsal mode blocks one character's dialogue > [!quote] [¶5] > You'll notice that the dialogue for character one has been blocked out here. **Context & use**: - ¶5, [4:13]. The narrator picks a character in the rehearsal view and the lines vanish. - Useful for a speaker practicing a part. The earlier check found the README confirms the feature. **Tags**: #xref #articleseed <!-- atomicity: 1 idea ✓ --> #### [H3] A synopsis shows directly on the index card > [!quote] [¶6] > the thing about the synopsises is they will show directly on the index cards. **Context & use**: - ¶6, [5:19]. Only the first synopsis of a scene shows on its card, per the narrator. - Use a synopsis line as a one-sentence scene summary when outlining a talk. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> #### [H4] The narrator hedges that scripts aren't linkable > [!quote] [¶6] > You can't directly link to this note. It's not um it's not linkable as far as I can tell. **Context & use**: - ¶6, [5:59]. A hedged observation, not a documented limit. - The earlier check found it half out of date: links out of a script exist, backlinks and graph view still skip them. **Tags**: #xref #share <!-- atomicity: 1 idea ✓ --> ### 🧠 Atomic Split Pad #### [P1] A plain-text script format turns an outline into cards **Claim** (one sentence, Courtney's voice): When a script is plain text with a strict element grammar, a tool can turn that text into an outline of scene cards without any extra data entry. **Evidence pointer**: [[#H1]] · [[#H3]] **Scope & conditions**: Holds where the writer follows the grammar, including the uppercase cue and heading prefix the video leaves out. Breaks when the file mixes in free-form prose or the parser's rules change between plugin versions. **Links**: - [[Plain text as a durable format]] — because extends - [[Scripting talks and videos]] — because applies-in presentation drafts - [[Obsidian properties and frontmatter]] — because contrasts on where metadata lives <!-- atomicity: 1 idea ✓ --> #### [P2] Tutorials that hedge limits should be re-checked later **Claim** (one sentence, Courtney's voice): A tutorial that says "as far as I can tell" about a limit gives me a testable claim to re-check against the current release. **Evidence pointer**: [[#H4]] **Scope & conditions**: Applies to fast-moving plugins where releases ship every few weeks. Breaks when the author doesn't hedge, because then I'd treat the claim as settled and skip the test. **Links**: - [[Verifying software claims]] — because applies-in - [[Reading video tutorials as sources]] — because extends <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Test one talk segment as a `.fountain` file with a section, a synopsis, an uppercase cue and a `[[>link]]` #fleeting #inbox #articleseed - [F2] Open question: did "new scene" at [3:33] carry an `INT`/`EXT` prefix? Check the video frame #fleeting #inbox - [F3] Compare Fountain Editor against the first plugin for properties support #fleeting #inbox #xref ### → Things 3 (max 2 actions) - [ ] Draft a test .fountain script for one talk segment and export a PDF to check layout, Obsidian scripting trial #things - [ ] Watch the video frames at 2:30 to 3:40 and note the exact scene heading text, to settle the INT/EXT question #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Scriptwriting in Obsidian With the Fountain Plugin.md|Scriptwriting in Obsidian With the Fountain Plugin by PrattDesign]] ## Highlights - [2:56] And then, uh, to work within fountain, what we're going to do is I'm going to hit enter twice. And then I can start typing a character name. So I'm going to type character one. And I'm going to hit enter once. And then this will be the dialogue. Okay. So, typing it in that specific order. The description, hitting enter twice, the character name, hitting enter once will create the dialogue and it'll be the same the whole way down. If we need to add another character, we go character 2. This will be other talking. [3:33] And then if we need to go back uh to like a description if this little scene wants to end, we're going to hit enter twice and we're going to uh new Whoops. Uh new scene. Okay. And then we can keep typing character three. Hello. Okay. So that's sort of the layout as to how you type within uh the fountain format. And we can go over to our side panel here and we can click on option up here, the table of contents of fountain script. And it'll just give you a layout of your scenes. And we can also uh go back up to our index cards. And ([View Highlight](https://read.readwise.io/read/01m2g494qtj1w4q75v91ngy8wn)) - Note: Core Fountain typing rule: blank line, character cue, dialogue on the next line. fountain.io also requires the cue in UPPERCASE (or forced with @). - Tags: action/h1, atom/literature/h1 - [4:13] you'll notice that we now have uh the two scenes that we have created broken down on each individual index cards within our index card screen, which provides a nice breakdown of your individual scenes. The Fountain plugin also has another neat option. If we go um if we go up to our eyeball again and we look at our options and we hit rehearsal and let's pick let's pick character one. You'll notice that the dialogue for character one has been blocked out here. If you need to rehearse lines or things like that, it's just another neat feature uh that's available within the Fountain plugin. [4:48] Uh, another thing of note, if you wanted to take quick little notes, you could double bracket and this character should have more lines. And you can just add some notes directly to your script if needed. The other thing that I'm going to quickly go over are synopsises. Um, if we Well, let's do the new scene. So, I'm going to hit enter twice and I'm going to do an equal sign. This is a synopsis of the scene. ([View Highlight](https://read.readwise.io/read/01m2g49ayvckxfmhzeeamx3nf5)) - Note: Rehearsal mode blanks one character's dialogue; `[[double brackets]]` add notes; `=` starts a synopsis. All three match the plugin README and fountain.io syntax as of 2026-09-14. - Tags: atom/literature/h3 - [5:19] Uh this can show uh it well it can show on multiple lines. So I will do this on multiple lines. Same equal sign as uh the previous one. But the thing about the synopsises is they will show directly on the index cards. So what I wrote in that synopsis is now showing on the index card for that scene. And of course, your scene can have multiple synopsises as they go down, but um only the first one, only the top one will actually show on uh the index card screen. And within the novel vault, there is um directions and a script notes page walking through this and uh [5:59] directions within the sample script as well in the novel vault. So uh that should help guide you along a little bit more. And this is great for people who prefer to work with scripts, who would enjoy writing more in a script format uh that is in the fountain layout directly within Obsidian. Uh there are of course some uh roadblocks. You can't directly link to this note. It's not um it's not linkable as far as I can tell. Um I don't believe I can also edit the properties to this page or anything. But to write in fountain format, it is fantastic. But if you prefer the old ([View Highlight](https://read.readwise.io/read/01m2g49jss004keyyans2jbadv)) - Note: Synopses show on index cards; the "not linkable" limitation is partly outdated: plugin 0.27.0 (2026-05-01) added `[[>target]]` links, but .fountain links still don't appear in backlinks or graph view. - Tags: atom/literature/h2, atom/zettel/z1