Phase 3N Help System - locations, workspace.

PlotLine/Help/Articles/Locations/Edit.md

@@ -0,0 +1,42 @@
+---
+title: Create or Edit Location
+category: Locations
+tags: locations, setting, hierarchy, continuity
+contextKey: locations.edit
+micro: Define a story place and how it fits into the project map.
+quickTitle: What belongs in a Location?
+quickSummary: Use a Location to track places that affect scenes, movement, atmosphere or continuity.
+screenshot:
+---
+
+# Overview
+
+Locations are the story places your scenes depend on. They can be broad areas, buildings, rooms, streets, vehicles or any setting that needs a stable record.
+
+# When Should I Use This?
+
+Use this page when a place appears more than once, affects movement, holds an important asset, or changes the meaning of a scene.
+
+# How To Use It
+
+Name the location clearly, choose its type, place it under a parent location if it belongs inside a larger place, and describe the details that matter for writing continuity.
+
+# Example
+
+A "Blue Bedroom" might sit under "North Wing" and carry notes about a locked connecting door, a cold window seat and the place where a clue is hidden.
+
+# Writer Tip
+
+Track the details that can cause mistakes later: entrances, sightlines, sound, ownership, emotional meaning and where objects can plausibly be found.
+
+# Common Mistakes
+
+- Creating every decorative place as a location.
+- Leaving rooms at top level when they belong inside a building.
+- Changing a layout in revision without updating related scenes.
+
+# Related Guides
+
+- [Locations](/Help/Article/locations.overview)
+- [Location Details](/Help/Article/locations.details)
+- [Scenes](/Help/Article/scenes.overview)

PlotLine/Help/Articles/Locations/Fields/LocationType.md

@@ -0,0 +1,16 @@
+---
+title: Location Type
+category: Locations
+tags: locations, fields, type
+contextKey: locations.fields.locationType
+micro: Classify what kind of place this location is.
+quickTitle: Location type
+quickSummary: Location Type helps you scan and organise places by their role in the story world.
+screenshot:
+---
+
+# Location Type
+
+Choose the kind of place this is, such as a building, room, outdoor area or transport location. The type helps you scan the location list and keep similar places organised.
+
+Use the type as a practical planning label, not a perfect taxonomy. Pick the option that would help you find the location again during revision.

PlotLine/Help/Articles/Locations/Fields/ParentLocation.md

@@ -0,0 +1,16 @@
+---
+title: Parent Location
+category: Locations
+tags: locations, fields, hierarchy, continuity
+contextKey: locations.fields.parentLocation
+micro: Place this location inside a larger story place.
+quickTitle: Parent location
+quickSummary: Parent Location builds a hierarchy, such as house, floor, room, so movement and setting stay clear.
+screenshot:
+---
+
+# Parent Location
+
+Choose a parent location when this place belongs inside a larger one. For example, a bedroom may belong inside a house, and a platform may belong inside a station.
+
+This keeps the location path clear and helps you reason about movement, sightlines and whether characters can plausibly reach or overhear something.

PlotLine/Help/Articles/Locations/Fields/QuickAdd.md

@@ -0,0 +1,16 @@
+---
+title: Location Quick Add
+category: Locations
+tags: locations, fields, quick add, scenes
+contextKey: locations.fields.quickAdd
+micro: Make an important location easy to add while planning scenes.
+quickTitle: Show in Quick Add Bar
+quickSummary: Show in Quick Add Bar promotes a recurring location so it is easier to use during scene planning.
+screenshot:
+---
+
+# Show in Quick Add Bar
+
+Turn this on for locations you use often or need to place quickly while planning scenes. It is best for major rooms, recurring places and settings that carry important continuity.
+
+Leave it off for rare or background locations so the shortcut area stays useful.

PlotLine/Help/Articles/Workspace/ChapterGoals.md

@@ -0,0 +1,52 @@
+---
+title: Chapter Goals
+category: Workspace
+tags: workspace, chapters, goals, revision
+contextKey: workspace.chapterGoals
+micro: Capture what this chapter needs to achieve for the reader and story.
+quickTitle: Chapter Goals
+quickSummary: Chapter Goals record the purpose, emotional movement, reader takeaway and risks for a chapter.
+screenshot:
+---
+
+# Overview
+
+Chapter Goals describe what the chapter is meant to achieve. They help keep drafting and revision focused on purpose, not just sequence.
+
+# When Should I Use This?
+
+Use this section before drafting a chapter, when revising a chapter that feels loose, or after moving scenes around.
+
+# How To Use It
+
+Write short, practical notes. The goal is not polished prose; it is a working brief that helps you decide whether the chapter is doing its job.
+
+# Understanding the Fields
+
+| Field | Use it for |
+| --- | --- |
+| Goal summary | The chapter's main story job. |
+| Emotional goal | The feeling or relationship shift the chapter should create. |
+| Reader takeaway | What the reader should understand, suspect or feel by the end. |
+| Must include | Clues, promises, turns or continuity details that cannot be dropped. |
+| Risks or concerns | Weak spots, open questions or choices to watch during revision. |
+
+# Example
+
+A chapter goal might be: "Beth commits to reopening Annie's case, but the reader should suspect the family version is incomplete."
+
+# Writer Tip
+
+If the chapter feels crowded, compare each scene against the goal and ask whether it contributes to the same movement.
+
+# Common Mistakes
+
+- Writing a full synopsis instead of a useful working brief.
+- Forgetting the reader takeaway.
+- Keeping old goals after the chapter's scene order changes.
+
+# Related Guides
+
+- [Chapter Workflow](/Help/Article/workspace.chapterWorkflow)
+- [Chapters](/Help/Article/chapters.overview)
+- [Revision Queue](/Help/Article/workspace.revisionQueue)

PlotLine/Help/Articles/Workspace/ChapterWorkflow.md

@@ -0,0 +1,42 @@
+---
+title: Chapter Workflow
+category: Workspace
+tags: workspace, chapters, revision, readiness
+contextKey: workspace.chapterWorkflow
+micro: Review one chapter's goals, scene readiness and blockers.
+quickTitle: Chapter Workflow
+quickSummary: Chapter Workflow helps you decide what a chapter needs before drafting, revision or polish.
+screenshot:
+---
+
+# Overview
+
+Chapter Workflow brings one chapter's intent, scene readiness, blockers and checklist signals into a single working view. It is a bridge between chapter planning and scene-level work.
+
+# When Should I Use This?
+
+Use it when a chapter feels vague, uneven, blocked or ready for review. It is especially useful before starting a writing session for a specific chapter.
+
+# How To Use It
+
+Review the readiness counts, update chapter goals, then scan the scene workflow summary for blocked, draft-ready, revision-ready and polish-ready scenes.
+
+# Example
+
+If a chapter has three scenes but only one is ready to draft, the workflow view helps you see whether the others need decisions, notes or structural changes first.
+
+# Writer Tip
+
+Think of this page as a chapter briefing. It should help you know what the chapter is trying to do before you open individual scenes.
+
+# Common Mistakes
+
+- Drafting scenes before the chapter's purpose is clear.
+- Treating readiness counts as quality scores.
+- Forgetting to update goals after restructuring the chapter.
+
+# Related Guides
+
+- [Writer Workspace](/Help/Article/workspace.overview)
+- [Chapters](/Help/Article/chapters.overview)
+- [Scenes](/Help/Article/scenes.overview)

PlotLine/Help/Articles/Workspace/PolishingQueue.md

@@ -0,0 +1,42 @@
+---
+title: Polishing Queue
+category: Workspace
+tags: workspace, polish, prose, pacing
+contextKey: workspace.polishingQueue
+micro: Find scenes ready for a final clarity and wording pass.
+quickTitle: Polishing Queue
+quickSummary: Polishing Queue is for scenes whose structure is settled enough for wording, clarity and rhythm work.
+screenshot:
+---
+
+# Overview
+
+Polishing Queue is for scenes that are close enough to finished that language-level work makes sense. This includes clarity, rhythm, pacing, transitions and final presentation.
+
+# When Should I Use This?
+
+Use it when you want a focused editing session and the scene no longer needs major structural changes.
+
+# How To Use It
+
+Open a queued scene and work on readability, emphasis, paragraph flow, sensory detail and whether the ending lands cleanly.
+
+# Example
+
+A scene may be structurally sound but still need sharper dialogue, smoother transitions or a clearer emotional turn.
+
+# Writer Tip
+
+Polishing is best when the scene has already earned its place.
+
+# Common Mistakes
+
+- Polishing before scene purpose is clear.
+- Mistaking pretty wording for stronger pacing.
+- Ignoring continuity warnings because the prose reads well.
+
+# Related Guides
+
+- [Writer Workspace](/Help/Article/workspace.overview)
+- [Revision Queue](/Help/Article/workspace.revisionQueue)
+- [Scenes](/Help/Article/scenes.overview)

PlotLine/Help/Articles/Workspace/PracticalBlockers.md

@@ -0,0 +1,42 @@
+---
+title: Practical Blockers
+category: Workspace
+tags: workspace, blockers, revision, planning
+contextKey: workspace.practicalBlockers
+micro: Find scenes blocked by missing decisions, research or planning details.
+quickTitle: Practical blockers
+quickSummary: Practical Blockers shows scenes that need attention before drafting or revision can proceed cleanly.
+screenshot:
+---
+
+# Overview
+
+Practical Blockers collects scenes where something is preventing smooth progress. The blocker might be missing research, an unresolved timeline choice, unclear motivation or a continuity question.
+
+# When Should I Use This?
+
+Use this queue when you have planning energy, or when drafting keeps stalling because too many decisions are still open.
+
+# How To Use It
+
+Open a blocked scene, read the blocker note, and resolve the smallest decision that would make the scene workable again.
+
+# Example
+
+A scene may be blocked because you have not decided how a character enters the locked room. Clearing that question may unlock several later scenes.
+
+# Writer Tip
+
+Blockers are not failures. They are signposts showing where the story needs a decision.
+
+# Common Mistakes
+
+- Trying to draft around a blocker that affects continuity.
+- Leaving research tasks vague.
+- Treating every warning as equally urgent.
+
+# Related Guides
+
+- [Writer Workspace](/Help/Article/workspace.overview)
+- [Scenes](/Help/Article/scenes.overview)
+- [Locations](/Help/Article/locations.overview)

PlotLine/Help/Articles/Workspace/Reminders.md

@@ -0,0 +1,42 @@
+---
+title: Workspace Reminders
+category: Workspace
+tags: workspace, reminders, story health, follow up
+contextKey: workspace.reminders
+micro: Keep future story-health tasks from being forgotten.
+quickTitle: Reminders
+quickSummary: Reminders collect follow-up items, warnings and story-health notes that may need attention later.
+screenshot:
+---
+
+# Overview
+
+Reminders collect story-health notes and follow-up items so useful thoughts do not disappear between writing sessions.
+
+# When Should I Use This?
+
+Use reminders when you want to scan what the project is asking you to revisit: continuity gaps, unresolved notes, warnings, missing scene details or later checks.
+
+# How To Use It
+
+Read the category and detail, then open the linked scene if the reminder points to one. Resolve the underlying issue when it is actually useful to your current drafting or revision stage.
+
+# Example
+
+A reminder might point out that a scene has warnings or that an important setup has not yet been followed through.
+
+# Writer Tip
+
+Reminders are a memory aid, not an accusation. Use them to protect future-you from losing important context.
+
+# Common Mistakes
+
+- Treating every reminder as urgent.
+- Ignoring reminders until a continuity problem becomes harder to fix.
+- Clearing reminders without fixing the underlying story issue.
+
+# Related Guides
+
+- [Writer Workspace](/Help/Article/workspace.overview)
+- [Scenes](/Help/Article/scenes.overview)
+- [Chapters](/Help/Article/chapters.overview)

PlotLine/Help/Articles/Workspace/RevisionQueue.md

@@ -0,0 +1,42 @@
+---
+title: Revision Queue
+category: Workspace
+tags: workspace, revision, scenes, structure
+contextKey: workspace.revisionQueue
+micro: Review scenes that need structural or content revision.
+quickTitle: Revision Queue
+quickSummary: Revision Queue gathers scenes that need more than final wording polish.
+screenshot:
+---
+
+# Overview
+
+Revision Queue is for scenes that need structural, content or continuity work. These are scenes where the idea, order, purpose or consequence may still need attention.
+
+# When Should I Use This?
+
+Use it during revision sessions, after drafting a chapter, or when you want to strengthen story logic before polishing prose.
+
+# How To Use It
+
+Open a scene and look for what must change: purpose, conflict, viewpoint, continuity, reveal order, pacing or consequences.
+
+# Example
+
+A scene may need revision because the clue appears before the reader understands why it matters, or because the viewpoint character has no reason to be present.
+
+# Writer Tip
+
+Revise before polishing. A beautiful paragraph is still expensive if the scene later moves or disappears.
+
+# Common Mistakes
+
+- Polishing a scene whose structure is still unstable.
+- Fixing sentence-level issues while ignoring a missing consequence.
+- Treating revision as punishment instead of design work.
+
+# Related Guides
+
+- [Writer Workspace](/Help/Article/workspace.overview)
+- [Chapter Workflow](/Help/Article/workspace.chapterWorkflow)
+- [Scenes](/Help/Article/scenes.overview)

PlotLine/Help/Articles/Workspace/WorkflowSummary.md

@@ -0,0 +1,42 @@
+---
+title: Workflow Summary
+category: Workspace
+tags: workspace, scenes, readiness, blockers
+contextKey: workspace.workflowSummary
+micro: Scan every scene in the chapter for readiness, warnings and blockers.
+quickTitle: Workflow Summary
+quickSummary: Workflow Summary shows which scenes are ready, blocked or still carrying practical work.
+screenshot:
+---
+
+# Overview
+
+Workflow Summary lists the scenes in a chapter with practical signals such as draft status, priority, warnings, checklist items, open notes and blockers.
+
+# When Should I Use This?
+
+Use it when deciding what to work on next inside a chapter, or when checking whether the chapter is ready for drafting, revision or polish.
+
+# How To Use It
+
+Scan the scene cards and choose the next useful action. A blocked scene may need a decision. A warning-heavy scene may need continuity attention. A ready scene may be safe to draft or polish.
+
+# Example
+
+If one scene is blocked by a missing location and another is ready for revision, you can choose the task that fits the session instead of opening scenes at random.
+
+# Writer Tip
+
+Use the summary to separate creative drafting from practical cleanup. Both matter, but they use different kinds of attention.
+
+# Common Mistakes
+
+- Treating a blocked scene as ready because its summary sounds exciting.
+- Ignoring warnings before polishing.
+- Trying to fix every scene in one pass.
+
+# Related Guides
+
+- [Chapter Workflow](/Help/Article/workspace.chapterWorkflow)
+- [Writer Workspace](/Help/Article/workspace.overview)
+- [Scenes](/Help/Article/scenes.overview)

PlotLine/Help/Articles/Workspace/WriteNext.md

@@ -0,0 +1,42 @@
+---
+title: Continue Writing
+category: Workspace
+tags: workspace, drafting, scenes, write next
+contextKey: workspace.writeNext
+micro: Find scenes that are ready to move forward in drafting.
+quickTitle: Continue Writing
+quickSummary: Continue Writing gathers scenes that look ready for your next drafting session.
+screenshot:
+---
+
+# Overview
+
+Continue Writing is the workspace queue for scenes that can move forward now. It helps turn a large project into a smaller set of practical next choices.
+
+# When Should I Use This?
+
+Use it at the start of a drafting session, especially when you do not want to reread the whole outline just to decide where to begin.
+
+# How To Use It
+
+Scan the scene title, status, summary, priority, warnings and notes. Open the scene that best matches the energy and time you have today.
+
+# Example
+
+If a scene has a clear summary, few blockers and a useful priority, it may be a better session target than a dramatic scene that still needs decisions.
+
+# Writer Tip
+
+Momentum often comes from choosing the next workable scene, not the most important scene.
+
+# Common Mistakes
+
+- Treating the queue as a command list.
+- Starting a scene that still has unresolved blockers.
+- Ignoring priority and notes when choosing what to draft.
+
+# Related Guides
+
+- [Writer Workspace](/Help/Article/workspace.overview)
+- [Scenes](/Help/Article/scenes.overview)
+- [Chapters](/Help/Article/chapters.overview)

PlotLine/Views/Locations/Edit.cshtml

@@ -6,7 +6,7 @@
 <div class="page-heading compact">
     <div>
         <p class="eyebrow">Location</p>
-        <h1>@ViewData["Title"]</h1>
+        <h1>@ViewData["Title"] <help-icon key="locations.edit" /></h1>
     </div>
 </div>
 
@@ -21,13 +21,13 @@
             <span asp-validation-for="LocationName" class="text-danger"></span>
         </div>
         <div class="col-md-4">
-            <label asp-for="LocationTypeID" class="form-label"></label>
+            <label asp-for="LocationTypeID" class="form-label">Location type <help-icon key="locations.fields.locationType" mode="inline" /></label>
             <select asp-for="LocationTypeID" asp-items="Model.LocationTypeOptions" class="form-select">
                 <option value="">Not set</option>
             </select>
         </div>
         <div class="col-12">
-            <label asp-for="ParentLocationID" class="form-label"></label>
+            <label asp-for="ParentLocationID" class="form-label">Parent location <help-icon key="locations.fields.parentLocation" mode="inline" /></label>
             <select asp-for="ParentLocationID" asp-items="Model.ParentLocationOptions" class="form-select">
                 <option value="">Top level</option>
             </select>
@@ -35,7 +35,7 @@
         <div class="col-12">
             <div class="form-check">
                 <input asp-for="ShowInQuickAddBar" class="form-check-input" />
-                <label asp-for="ShowInQuickAddBar" class="form-check-label"></label>
+                <label asp-for="ShowInQuickAddBar" class="form-check-label">Show in Quick Add Bar <help-icon key="locations.fields.quickAdd" mode="inline" /></label>
                 <div class="form-text">Makes this item available as a draggable shortcut on the Timeline page.</div>
             </div>
         </div>

PlotLine/Views/Writer/Chapter.cshtml

@@ -18,7 +18,7 @@
 <div class="page-heading">
     <div>
         <p class="eyebrow">Chapter workflow</p>
-        <h1>Chapter @Model.Chapter.ChapterNumber: @Model.Chapter.ChapterTitle</h1>
+        <h1>Chapter @Model.Chapter.ChapterNumber: @Model.Chapter.ChapterTitle <help-icon key="workspace.chapterWorkflow" /></h1>
         <p class="lead-text">Chapter intent, readiness, blockers, notes, and checklist progress.</p>
     </div>
     <div class="button-row">
@@ -42,7 +42,7 @@
     <div class="story-bible-section-heading">
         <div>
             <p class="eyebrow">Intent</p>
-            <h2>Chapter Goals</h2>
+            <h2>Chapter Goals <help-icon key="workspace.chapterGoals" /></h2>
         </div>
     </div>
     <form asp-action="SaveChapterGoal" method="post" class="story-bible-card chapter-goal-form">
@@ -66,7 +66,7 @@
     <div class="story-bible-section-heading">
         <div>
             <p class="eyebrow">Scenes</p>
-            <h2>Workflow Summary</h2>
+            <h2>Workflow Summary <help-icon key="workspace.workflowSummary" /></h2>
         </div>
     </div>
     <div class="writer-queue-list">

PlotLine/Views/Writer/Index.cshtml

@@ -22,7 +22,7 @@
         <div class="story-bible-section-heading">
             <div>
                 <p class="eyebrow">Write Next</p>
-                <h2>Continue Writing</h2>
+                <h2>Continue Writing <help-icon key="workspace.writeNext" /></h2>
             </div>
             <span class="soft-count">@Model.ContinueWriting.Count scenes</span>
         </div>
@@ -33,7 +33,7 @@
         <div class="story-bible-section-heading">
             <div>
                 <p class="eyebrow">Practical blockers</p>
-                <h2>Needs Attention</h2>
+                <h2>Needs Attention <help-icon key="workspace.practicalBlockers" /></h2>
             </div>
             <span class="soft-count">@Model.NeedsAttention.Count scenes</span>
         </div>
@@ -44,7 +44,7 @@
         <div class="story-bible-section-heading">
             <div>
                 <p class="eyebrow">Revision</p>
-                <h2>Revision Queue</h2>
+                <h2>Revision Queue <help-icon key="workspace.revisionQueue" /></h2>
             </div>
             <span class="soft-count">@Model.RevisionQueue.Count scenes</span>
         </div>
@@ -55,7 +55,7 @@
         <div class="story-bible-section-heading">
             <div>
                 <p class="eyebrow">Final pass</p>
-                <h2>Polishing Queue</h2>
+                <h2>Polishing Queue <help-icon key="workspace.polishingQueue" /></h2>
             </div>
             <span class="soft-count">@Model.PolishingQueue.Count scenes</span>
         </div>
@@ -67,7 +67,7 @@
     <div class="story-bible-section-heading">
         <div>
             <p class="eyebrow">Story health</p>
-            <h2>Reminders</h2>
+            <h2>Reminders <help-icon key="workspace.reminders" /></h2>
         </div>
         <span class="soft-count">@Model.StoryHealthReminders.Count items</span>
     </div>