Phase 3M Help System - projects, books, chapters, basic scene

PlotLine/Help/Articles/Books/Chapters.md

@@ -0,0 +1,42 @@
+---
+title: Book Chapters
+category: Books
+tags: books, chapters, pacing, structure
+contextKey: books.chapters
+micro: Review the chapters that shape this book's reader-facing structure.
+quickTitle: Chapters in a book
+quickSummary: The Chapters section shows how this book is divided into reader-facing movements.
+screenshot:
+---
+
+# Overview
+
+The Chapters section shows the reader-facing structure inside a book. Chapters group scenes into movements, helping you check pacing, rhythm, point of view shifts and the order of reveals.
+
+# When Should I Use This?
+
+Use it when you want to review the book's shape without opening every scene. It is useful during outlining, restructuring and revision.
+
+# How To Use It
+
+Open a chapter to review its scenes, edit a chapter when its number or summary changes, or add a new chapter when the book needs another movement.
+
+# Example
+
+A chapter may gather the arrival at a hotel, the first warning and the discovery of a photograph into one escalating mystery movement.
+
+# Writer Tip
+
+Chapter breaks can stay flexible. Scenes are the working units; chapters are how you shape the reader's experience.
+
+# Common Mistakes
+
+- Locking chapter breaks before the scene order has settled.
+- Letting chapters grow too large to have a clear movement.
+- Treating chapter summaries as full synopses.
+
+# Related Guides
+
+- [Chapters](/Help/Article/chapters.overview)
+- [Edit Chapter](/Help/Article/chapters.edit)
+- [Scenes](/Help/Article/scenes.overview)

PlotLine/Help/Articles/Books/Edit.md

@@ -0,0 +1,42 @@
+---
+title: Create or Edit a Book
+category: Books
+tags: books, series, chapters, planning
+contextKey: books.edit
+micro: Define a book or instalment inside a project.
+quickTitle: What belongs in a Book?
+quickSummary: Use a Book to organise a standalone novel, novella or series instalment inside a project.
+screenshot:
+---
+
+# Overview
+
+Books are the major containers inside a project. A book may be a standalone novel, a novella, a later series instalment or a planned volume that shares continuity with the rest of the project.
+
+# When Should I Use This?
+
+Use this page when creating a new volume or updating the order, title or planning description for an existing book.
+
+# How To Use It
+
+Set the book number so the reading order is clear. Use the title and description to capture the book's working promise: its central question, major conflict, emotional movement or role in the series.
+
+# Example
+
+Book 2 might carry the description: "Beth follows the memory tin trail while Maggie's version of Annie's death begins to collapse."
+
+# Writer Tip
+
+Keep book descriptions practical. They should help you remember what this instalment does, not pretend to be polished back-cover copy.
+
+# Common Mistakes
+
+- Treating book order as fixed too early.
+- Creating separate projects for books that share heavy continuity.
+- Leaving the description unchanged after the book's purpose changes.
+
+# Related Guides
+
+- [Books](/Help/Article/books.overview)
+- [Chapters](/Help/Article/chapters.overview)
+- [Scenes](/Help/Article/scenes.overview)

PlotLine/Help/Articles/Books/Fields/BookNumber.md

@@ -0,0 +1,16 @@
+---
+title: Book Number
+category: Books
+tags: books, fields, order, series
+contextKey: books.fields.bookNumber
+micro: Set this book's reading or planning order inside the project.
+quickTitle: Book number
+quickSummary: Book Number controls the order of books or instalments inside a project.
+screenshot:
+---
+
+# Book Number
+
+Use Book Number to set the order of this book inside the project. In a series, this usually matches reading order. In a standalone project, it may simply be `1`.
+
+This helps keep chapters, scenes and continuity grouped under the correct volume.

PlotLine/Help/Articles/Chapters/Edit.md

@@ -0,0 +1,42 @@
+---
+title: Create or Edit a Chapter
+category: Chapters
+tags: chapters, scenes, pacing, revision
+contextKey: chapters.edit
+micro: Shape a chapter as a reader-facing movement inside a book.
+quickTitle: What belongs in a Chapter?
+quickSummary: Use a Chapter to group scenes into a readable movement with clear pacing, rhythm and purpose.
+screenshot:
+---
+
+# Overview
+
+Chapters organise scenes into reader-facing structure. A chapter can group related scenes, hold a viewpoint movement, create a pacing beat or mark a turn in the book's rhythm.
+
+# When Should I Use This?
+
+Use this page when creating a new chapter, adjusting chapter order, or updating the summary and revision status for an existing chapter.
+
+# How To Use It
+
+Set the chapter number, add a working title, choose revision status and write a summary that explains what the chapter does for the book.
+
+# Example
+
+A chapter summary might be: "Maggie enters the hotel mystery and receives the first impossible clue."
+
+# Writer Tip
+
+Do not treat chapters as fixed too early. During revision, chapter boundaries often move as scene rhythm becomes clearer.
+
+# Common Mistakes
+
+- Using chapter summaries as full scene-by-scene recaps.
+- Keeping a chapter intact after it has split into two different movements.
+- Ignoring revision status when deciding what still needs work.
+
+# Related Guides
+
+- [Chapters](/Help/Article/chapters.overview)
+- [Scenes](/Help/Article/scenes.overview)
+- [Books](/Help/Article/books.overview)

PlotLine/Help/Articles/Chapters/Fields/ChapterNumber.md

@@ -0,0 +1,16 @@
+---
+title: Chapter Number
+category: Chapters
+tags: chapters, fields, order, pacing
+contextKey: chapters.fields.chapterNumber
+micro: Set the chapter's order inside the book.
+quickTitle: Chapter number
+quickSummary: Chapter Number controls where this chapter sits in the book's reader-facing order.
+screenshot:
+---
+
+# Chapter Number
+
+Use Chapter Number to set where the chapter sits in the book. Decimal numbers can be useful while restructuring because they let you insert chapters between existing ones before renumbering cleanly.
+
+The number should reflect reading order, not necessarily the order in which you drafted the material.

PlotLine/Help/Articles/Chapters/Fields/RevisionStatus.md

@@ -0,0 +1,16 @@
+---
+title: Chapter Revision Status
+category: Chapters
+tags: chapters, fields, revision
+contextKey: chapters.fields.revisionStatus
+micro: Mark how ready this chapter is for drafting or revision.
+quickTitle: Revision status
+quickSummary: Revision Status helps you see which chapters are planned, drafted, revised or still need attention.
+screenshot:
+---
+
+# Revision Status
+
+Choose the status that best describes where the chapter is in your writing process. This helps you scan the book for unfinished, rough or ready sections.
+
+Use status honestly. It is more useful as a planning signal than as a judgement of quality.

PlotLine/Help/Articles/Chapters/Scenes.md

@@ -0,0 +1,42 @@
+---
+title: Chapter Scenes
+category: Chapters
+tags: chapters, scenes, pacing, continuity
+contextKey: chapters.scenes
+micro: Review the scenes that make up this chapter's story movement.
+quickTitle: Scenes in a chapter
+quickSummary: The Scenes section shows the working story beats inside a chapter.
+screenshot:
+---
+
+# Overview
+
+The Scenes section shows the working story beats inside the chapter. Scenes are where action, viewpoint, location, time, consequence and continuity details are tracked.
+
+# When Should I Use This?
+
+Use it to check whether the chapter has a clear beginning, development and turn. It is also useful when you need to reorder, add or archive scenes.
+
+# How To Use It
+
+Open a scene to edit its planning details, use the order controls to adjust the chapter flow, and scan summaries to see whether the chapter movement still makes sense.
+
+# Example
+
+One chapter might contain a warning scene, a discovery scene and a reaction scene. Together they create a single reader-facing movement.
+
+# Writer Tip
+
+If a chapter feels flat, look at its scenes and ask what changes by the end of each one.
+
+# Common Mistakes
+
+- Treating a chapter as one large scene.
+- Moving scenes without checking surrounding continuity.
+- Keeping scenes in a chapter after their purpose has shifted elsewhere.
+
+# Related Guides
+
+- [Scenes](/Help/Article/scenes.overview)
+- [Edit Scene](/Help/Article/scenes.edit)
+- [Chapters](/Help/Article/chapters.overview)

PlotLine/Help/Articles/Projects/Books.md

@@ -0,0 +1,42 @@
+---
+title: Project Books
+category: Projects
+tags: projects, books, series, structure
+contextKey: projects.books
+micro: Review the books that belong inside this project.
+quickTitle: Books in a project
+quickSummary: The Books section shows the novels, instalments or volumes that make up the project.
+screenshot:
+---
+
+# Overview
+
+The Books section shows the major story containers inside the project. A project might hold one standalone novel, several books in a series, or planned instalments that share characters, locations, assets and continuity.
+
+# When Should I Use This?
+
+Use this section when you need to check whether the project has the right book structure before planning chapters and scenes in detail.
+
+# How To Use It
+
+Open a book to review its chapters, edit a book when its number or purpose changes, or add a new book when the project grows into another instalment.
+
+# Example
+
+A mystery series may keep Books 1, 2 and 3 in one project so a clue or family secret can stay connected across all volumes.
+
+# Writer Tip
+
+Do not split related books into separate projects unless they truly have no shared continuity.
+
+# Common Mistakes
+
+- Creating a new project for every book in a connected series.
+- Leaving books out of order after restructuring.
+- Using book descriptions as marketing copy rather than planning notes.
+
+# Related Guides
+
+- [Books](/Help/Article/books.overview)
+- [Edit Book](/Help/Article/books.edit)
+- [Chapters](/Help/Article/chapters.overview)

PlotLine/Help/Articles/Projects/Fields/GenreMetricPreset.md

@@ -0,0 +1,16 @@
+---
+title: Genre / Metric Preset
+category: Projects
+tags: projects, fields, metrics, setup
+contextKey: projects.fields.genreMetricPreset
+micro: Choose a starting set of scene metrics for a new project.
+quickTitle: Genre / Metric Preset
+quickSummary: Genre / Metric Preset gives a new project a useful starting set of scene metrics that can be adjusted later.
+screenshot:
+---
+
+# Genre / Metric Preset
+
+Choose a starting set of scene metrics that fits the kind of story you are planning. This can help the first scenes track useful qualities such as tension, intensity, mystery or emotional weight.
+
+The choice is only a starting point. You can adjust project metrics later as the book or series becomes clearer.

PlotLine/Help/Articles/Scenes/Edit.md

@@ -0,0 +1,45 @@
+---
+title: Create or Edit a Scene
+category: Scenes
+tags: scenes, editing, structure, continuity
+contextKey: scenes.edit
+micro: Work on a scene as a focused unit of story action and continuity.
+quickTitle: What belongs in a Scene?
+quickSummary: Use the Scene editor to plan what happens, where and when it happens, who is involved, and why the moment matters.
+screenshot:
+---
+
+# Overview
+
+Scenes are the working units of story. A scene captures what happens, who is present, where and when it happens, why it matters, and what changes because of it.
+
+This page is the simple entry point for editing a scene. The detailed scene tools help track timing, summary, point of view, location, characters, assets, consequences and revision state without losing continuity.
+
+# When Should I Use This?
+
+Use this page when creating a new story beat, adjusting an existing scene, or checking whether a scene has enough purpose and consequence.
+
+# How To Use It
+
+Start with the scene title, summary and revision status. Add time, location and point-of-view details when they matter. Record enough continuity information that later scenes can rely on it.
+
+# Example
+
+A scene might be: "Beth opens the memory tin and finds a photograph that contradicts what she was told about Annie." The important details are not only the object, but who knows, where it happens and what changes afterward.
+
+# Writer Tip
+
+Every scene should leave the story different. The change may be external, emotional, informational or relational.
+
+# Common Mistakes
+
+- Writing atmosphere without recording what changes.
+- Leaving location, time or point of view vague when continuity depends on them.
+- Treating scene summaries as polished prose instead of practical planning notes.
+
+# Related Guides
+
+- [Scenes](/Help/Article/scenes.overview)
+- [Chapters](/Help/Article/chapters.overview)
+- [Characters](/Help/Article/characters.overview)
+- [Story Assets](/Help/Article/storyAssets.overview)

PlotLine/Views/Books/Details.cshtml

@@ -48,7 +48,7 @@
 </div>
 
 <section class="list-section">
-    <h2>Chapters</h2>
+    <h2>Chapters <help-icon key="books.chapters" /></h2>
     @if (!Model.Chapters.Any())
     {
         <p class="muted">No chapters yet.</p>

PlotLine/Views/Books/Edit.cshtml

@@ -6,7 +6,7 @@
 <div class="page-heading compact">
     <div>
         <p class="eyebrow">@Model.Project?.ProjectName</p>
-        <h1>@ViewData["Title"]</h1>
+        <h1>@ViewData["Title"] <help-icon key="books.edit" /></h1>
     </div>
     <a class="btn btn-outline-secondary" asp-controller="Projects" asp-action="Details" asp-route-id="@Model.ProjectID">Back to project</a>
 </div>
@@ -17,7 +17,7 @@
     <div asp-validation-summary="ModelOnly" class="text-danger"></div>
     <div class="row g-3">
         <div class="col-md-3">
-            <label asp-for="BookNumber" class="form-label"></label>
+            <label asp-for="BookNumber" class="form-label">Book number <help-icon key="books.fields.bookNumber" mode="inline" /></label>
             <input asp-for="BookNumber" class="form-control" />
         </div>
         <div class="col-md-9">

PlotLine/Views/Chapters/Details.cshtml

@@ -53,7 +53,7 @@
 </div>
 
 <section class="list-section">
-    <h2>Scenes</h2>
+    <h2>Scenes <help-icon key="chapters.scenes" /></h2>
     @if (!Model.Scenes.Any())
     {
         <p class="muted">No scenes yet.</p>

PlotLine/Views/Chapters/Edit.cshtml

@@ -6,7 +6,7 @@
 <div class="page-heading compact">
     <div>
         <p class="eyebrow">@Model.Book?.BookTitle</p>
-        <h1>@ViewData["Title"]</h1>
+        <h1>@ViewData["Title"] <help-icon key="chapters.edit" /></h1>
     </div>
     <a class="btn btn-outline-secondary" asp-controller="Books" asp-action="Details" asp-route-id="@Model.BookID">Back to book</a>
 </div>
@@ -17,7 +17,7 @@
     <div asp-validation-summary="ModelOnly" class="text-danger"></div>
     <div class="row g-3">
         <div class="col-md-3">
-            <label asp-for="ChapterNumber" class="form-label"></label>
+            <label asp-for="ChapterNumber" class="form-label">Chapter number <help-icon key="chapters.fields.chapterNumber" mode="inline" /></label>
             <input asp-for="ChapterNumber" class="form-control" />
         </div>
         <div class="col-md-6">
@@ -26,7 +26,7 @@
             <span asp-validation-for="ChapterTitle" class="text-danger"></span>
         </div>
         <div class="col-md-3">
-            <label asp-for="RevisionStatusID" class="form-label"></label>
+            <label asp-for="RevisionStatusID" class="form-label">Revision status <help-icon key="chapters.fields.revisionStatus" mode="inline" /></label>
             <select asp-for="RevisionStatusID" asp-items="Model.RevisionStatuses" class="form-select"></select>
         </div>
         <div class="col-12">

PlotLine/Views/Projects/Details.cshtml

@@ -77,7 +77,7 @@
 }
 
 <section class="list-section">
-    <h2>Books</h2>
+    <h2>Books <help-icon key="projects.books" /></h2>
     @if (!Model.Books.Any())
     {
         <p class="muted">No books yet. Add the first book to begin the hierarchy.</p>

PlotLine/Views/Projects/Edit.cshtml

@@ -26,7 +26,7 @@
     @if (Model.ProjectID == 0)
     {
         <div class="mb-3">
-            <label asp-for="GenreMetricPresetKey" class="form-label"></label>
+            <label asp-for="GenreMetricPresetKey" class="form-label">Genre / Metric Preset <help-icon key="projects.fields.genreMetricPreset" mode="inline" /></label>
             <select asp-for="GenreMetricPresetKey" asp-items="Model.GenreMetricPresetOptions" class="form-select"></select>
             <div class="form-text">Choose a starting set of scene metrics for this project. You can adjust timeline metrics later in Timeline Settings.</div>
         </div>

PlotLine/Views/Scenes/Edit.cshtml

@@ -39,7 +39,7 @@
 <div class="page-heading compact">
     <div>
         <p class="eyebrow">@Model.Book?.BookTitle / Chapter @Model.Chapter?.ChapterNumber</p>
-        <h1>@ViewData["Title"] <help-icon key="scenes.overview" /></h1>
+        <h1>@ViewData["Title"] <help-icon key="scenes.edit" /></h1>
     </div>
     <div class="button-row">
         @if (Model.SceneID > 0)