diff --git a/PlotLine/Help/Articles/Archive/ArchivedRecords.md b/PlotLine/Help/Articles/Archive/ArchivedRecords.md new file mode 100644 index 0000000..dfd079b --- /dev/null +++ b/PlotLine/Help/Articles/Archive/ArchivedRecords.md @@ -0,0 +1,42 @@ +--- +title: Archived Records +category: Archive +tags: archive, restore, delete, recovery +contextKey: archive.archivedRecords +micro: Review hidden items and decide whether to restore or permanently remove them. +quickTitle: Archived records +quickSummary: Archived Records keeps removed planning material available for restoration until you choose to delete it forever. +screenshot: +--- + +# Overview + +Archived Records lists items that have been hidden from active views. They are preserved so you can recover useful material later. + +# When Should I Use This? + +Use it after restructuring, cutting a subplot, retiring a location, removing a character or setting aside an experimental scenario. + +# How To Use It + +Restore items that belong back in active planning. Delete forever only when you are certain the material should be permanently removed. + +# Example + +You might restore an archived clue after discovering it solves a payoff problem in the final act. + +# Writer Tip + +Archive first, delete later. Drafts change their minds. + +# Common Mistakes + +- Using Delete Forever as cleanup before you are sure. +- Restoring material without checking whether it still fits. +- Forgetting archived items may contain useful earlier ideas. + +# Related Guides + +- [Archived Items](/Help/Article/archive.overview) +- [Projects](/Help/Article/projects.overview) +- [Story Bible](/Help/Article/storyBible.overview) diff --git a/PlotLine/Help/Articles/Archive/Overview.md b/PlotLine/Help/Articles/Archive/Overview.md index abd365c..df7c46c 100644 --- a/PlotLine/Help/Articles/Archive/Overview.md +++ b/PlotLine/Help/Articles/Archive/Overview.md @@ -47,5 +47,4 @@ Archive is a thinking space, not a bin. Let ideas rest there until you know whet # Related Guides - [Projects](/Help/Article/projects.overview) -- [Restore Points](/Help/Article/restorePoints.overview) - [Story Bible](/Help/Article/storyBible.overview) diff --git a/PlotLine/Help/Articles/RelationshipMap/Overview.md b/PlotLine/Help/Articles/RelationshipMap/Overview.md new file mode 100644 index 0000000..ff80785 --- /dev/null +++ b/PlotLine/Help/Articles/RelationshipMap/Overview.md @@ -0,0 +1,42 @@ +--- +title: Relationship Map +category: Relationship Map +tags: relationship map, characters, relationships, visualisation +contextKey: relationshipMap.overview +micro: Visualise character connections across the story. +quickTitle: What is the Relationship Map? +quickSummary: The Relationship Map shows character connections so you can spot social structure, isolation and relationship patterns. +screenshot: +--- + +# Overview + +The Relationship Map visualises connections between characters. It gives a high-level view of social structure within the story. + +# When Should I Use This? + +Use it when you want to see family, friendship, romance, conflict, professional ties or other relationship patterns without reading every character profile. + +# How To Use It + +Choose a story point or character focus, then inspect the visible network. Look for isolated characters, overloaded hubs or relationship groups that do not interact. + +# Example + +A mystery may reveal that one suspect is socially isolated from everyone except the victim, which could be a useful structural clue. + +# Writer Tip + +The map is a perspective tool. Use it to ask better questions about the cast. + +# Common Mistakes + +- Assuming a sparse map is always bad. +- Forgetting relationships can change over time. +- Treating the map as a replacement for character detail pages. + +# Related Guides + +- [Characters](/Help/Article/characters.overview) +- [Story Bible](/Help/Article/storyBible.overview) +- [Character Relationships](/Help/Article/characters.currentRelationships) diff --git a/PlotLine/Help/Articles/Scenarios/ApplyToMain.md b/PlotLine/Help/Articles/Scenarios/ApplyToMain.md new file mode 100644 index 0000000..ed55cee --- /dev/null +++ b/PlotLine/Help/Articles/Scenarios/ApplyToMain.md @@ -0,0 +1,41 @@ +--- +title: Apply Scenario To Main +category: Scenarios +tags: scenarios, apply, structure, revision +contextKey: scenarios.applyToMain +micro: Commit the sandbox order to the main story. +quickTitle: Apply to main +quickSummary: Apply Scenario To Main replaces the current scene order with the scenario order. +screenshot: +--- + +# Overview + +Apply Scenario To Main commits the sandbox order to the real story order. It should be treated as a deliberate revision decision. + +# When Should I Use This? + +Use it only after reviewing moved scenes and scenario warnings, and only when the alternate structure is the one you want to continue with. + +# How To Use It + +Read the confirmation carefully, enter the exact text and apply only when you are ready for the main order to change. + +# Example + +After testing a later reveal and clearing warnings, you apply the scenario so the main story uses the stronger order. + +# Writer Tip + +Compare first, apply second. A sandbox is valuable because it gives you time to think. + +# Common Mistakes + +- Applying before reading scenario warnings. +- Applying a scenario just to see what happens. +- Forgetting that linked story data stays attached to the same scenes. + +# Related Guides + +- [Compare Scenario](/Help/Article/scenarios.compare) +- [Warnings](/Help/Article/warnings.overview) diff --git a/PlotLine/Help/Articles/Scenarios/Compare.md b/PlotLine/Help/Articles/Scenarios/Compare.md new file mode 100644 index 0000000..0222564 --- /dev/null +++ b/PlotLine/Help/Articles/Scenarios/Compare.md @@ -0,0 +1,42 @@ +--- +title: Compare Scenario +category: Scenarios +tags: scenarios, compare, revision, scene order +contextKey: scenarios.compare +micro: Compare sandbox changes against the main story order. +quickTitle: Compare scenario +quickSummary: Compare Scenario shows what moved and what warnings appeared before you apply a sandbox to the main story. +screenshot: +--- + +# Overview + +Compare Scenario is the checkpoint before committing a what-if structure. It shows moved scenes and scenario warnings so you can judge the consequences. + +# When Should I Use This? + +Use it after making meaningful changes in a scenario and before applying the scenario to the main story. + +# How To Use It + +Review moved scenes, check warnings, then decide whether the alternate order is stronger, needs more work or should remain only an experiment. + +# Example + +If moving a clue later creates a warning that a later scene depends on it too early, the comparison page tells you where to look. + +# Writer Tip + +A scenario can succeed even if you do not apply it. Sometimes the experiment teaches you why the original order works. + +# Common Mistakes + +- Applying because the order is new, not because it is better. +- Ignoring warnings created by the alternate order. +- Forgetting which scenes moved. + +# Related Guides + +- [Scenario Timeline](/Help/Article/scenarios.timeline) +- [Warnings](/Help/Article/warnings.overview) +- [Story Health](/Help/Article/storyHealth.overview) diff --git a/PlotLine/Help/Articles/Scenarios/Create.md b/PlotLine/Help/Articles/Scenarios/Create.md new file mode 100644 index 0000000..a43a65d --- /dev/null +++ b/PlotLine/Help/Articles/Scenarios/Create.md @@ -0,0 +1,42 @@ +--- +title: Create Scenario +category: Scenarios +tags: scenarios, sandbox, structure, revision +contextKey: scenarios.create +micro: Start a safe what-if version of the current scene order. +quickTitle: Create scenario +quickSummary: Create Scenario copies the current order into a sandbox so you can test structural changes before committing them. +screenshot: +--- + +# Overview + +Creating a scenario starts a what-if version of the current scene order. It lets you test alternatives without immediately changing the main story. + +# When Should I Use This? + +Use it when a revision idea could affect several scenes, chapters or reveals, and you want to explore consequences safely. + +# How To Use It + +Give the scenario a name that describes the experiment, choose its scope and add a short note about what you are testing. + +# Example + +"Delay Witness Reveal" is clearer than "Scenario 2" because it tells you the structural question at a glance. + +# Writer Tip + +Create scenarios for decisions you genuinely need to compare, not every small adjustment. + +# Common Mistakes + +- Forgetting the scenario is a test. +- Using vague names. +- Creating a sandbox without a clear story question. + +# Related Guides + +- [Scenarios](/Help/Article/scenarios.overview) +- [Plot Lines](/Help/Article/plotLines.index) +- [Warnings](/Help/Article/warnings.overview) diff --git a/PlotLine/Help/Articles/Scenarios/Fields/ConfirmationText.md b/PlotLine/Help/Articles/Scenarios/Fields/ConfirmationText.md new file mode 100644 index 0000000..1ea9f2e --- /dev/null +++ b/PlotLine/Help/Articles/Scenarios/Fields/ConfirmationText.md @@ -0,0 +1,16 @@ +--- +title: Confirmation Text +category: Scenarios +tags: scenarios, fields, confirmation +contextKey: scenarios.fields.confirmationText +micro: Confirm that you really want to apply the sandbox order. +quickTitle: Confirmation text +quickSummary: Confirmation text protects the main story order from accidental scenario changes. +screenshot: +--- + +# Confirmation Text + +Type the exact confirmation phrase only when you are ready to replace the main scene order with the scenario order. + +This is a deliberate checkpoint because applying a scenario changes the real structure of the project. diff --git a/PlotLine/Help/Articles/Scenarios/Fields/Scope.md b/PlotLine/Help/Articles/Scenarios/Fields/Scope.md new file mode 100644 index 0000000..4eec54c --- /dev/null +++ b/PlotLine/Help/Articles/Scenarios/Fields/Scope.md @@ -0,0 +1,16 @@ +--- +title: Scenario Scope +category: Scenarios +tags: scenarios, fields, scope, books +contextKey: scenarios.fields.scope +micro: Choose whether the scenario covers one book or the whole project. +quickTitle: Scope +quickSummary: Scope limits the scenario to a book or lets it explore the whole project order. +screenshot: +--- + +# Scope + +Choose a book when the experiment only affects that volume. Choose the whole project when the idea affects series structure, cross-book continuity or the order of multiple books. + +Smaller scope is easier to compare. Wider scope is useful when the story question crosses book boundaries. diff --git a/PlotLine/Help/Articles/Scenarios/MainVsScenario.md b/PlotLine/Help/Articles/Scenarios/MainVsScenario.md new file mode 100644 index 0000000..778e768 --- /dev/null +++ b/PlotLine/Help/Articles/Scenarios/MainVsScenario.md @@ -0,0 +1,41 @@ +--- +title: Main vs Scenario +category: Scenarios +tags: scenarios, compare, structure +contextKey: scenarios.mainVsScenario +micro: See which scenes changed position in the sandbox. +quickTitle: Main vs Scenario +quickSummary: Main vs Scenario compares the real order with the sandbox order so structural changes are visible. +screenshot: +--- + +# Overview + +Main vs Scenario shows which scenes have moved between the current story order and the sandbox version. + +# When Should I Use This? + +Use it when deciding whether the scenario's structure is actually clearer, stronger or more suspenseful. + +# How To Use It + +Look at each moved scene and ask what changes in setup, payoff, character knowledge and pacing. + +# Example + +Moving a confrontation earlier may increase pace but weaken the evidence trail that made it believable. + +# Writer Tip + +Scene movement always changes context. Compare what the reader knows before and after each moved scene. + +# Common Mistakes + +- Evaluating moved scenes in isolation. +- Forgetting that character knowledge may change with order. +- Applying a scenario without checking moved scenes. + +# Related Guides + +- [Compare Scenario](/Help/Article/scenarios.compare) +- [Scenario Validation Notes](/Help/Article/scenarios.validationNotes) diff --git a/PlotLine/Help/Articles/Scenarios/Timeline.md b/PlotLine/Help/Articles/Scenarios/Timeline.md new file mode 100644 index 0000000..9005073 --- /dev/null +++ b/PlotLine/Help/Articles/Scenarios/Timeline.md @@ -0,0 +1,42 @@ +--- +title: Scenario Timeline +category: Scenarios +tags: scenarios, timeline, sandbox, scene order +contextKey: scenarios.timeline +micro: Review and adjust a sandbox scene order. +quickTitle: Scenario timeline +quickSummary: Scenario Timeline shows the alternate order you are testing without changing the main story order. +screenshot: +--- + +# Overview + +The Scenario Timeline is the sandbox view of your what-if structure. It shows the proposed order and lets you test movement before applying anything to the main story. + +# When Should I Use This? + +Use it while exploring an alternate scene order, testing chapter placement or checking whether a reveal lands better elsewhere. + +# How To Use It + +Move scenes within the scenario, validate the sandbox, then compare it against the main order before applying it. + +# Example + +You might move an accusation scene later and validate the scenario to see whether the new order creates missing setup warnings. + +# Writer Tip + +Look for consequences, not just whether the new order feels exciting. + +# Common Mistakes + +- Treating sandbox order as final too soon. +- Forgetting to compare before applying. +- Ignoring scenario warnings. + +# Related Guides + +- [Scenarios](/Help/Article/scenarios.overview) +- [Compare Scenario](/Help/Article/scenarios.compare) +- [Warnings](/Help/Article/warnings.overview) diff --git a/PlotLine/Help/Articles/Scenarios/ValidationNotes.md b/PlotLine/Help/Articles/Scenarios/ValidationNotes.md new file mode 100644 index 0000000..312fe42 --- /dev/null +++ b/PlotLine/Help/Articles/Scenarios/ValidationNotes.md @@ -0,0 +1,41 @@ +--- +title: Scenario Validation Notes +category: Scenarios +tags: scenarios, warnings, validation, sandbox +contextKey: scenarios.validationNotes +micro: Review warnings created inside a scenario sandbox. +quickTitle: Validation notes +quickSummary: Scenario Validation Notes highlight possible problems in the sandbox order before it affects the main story. +screenshot: +--- + +# Overview + +Validation notes are warnings for the scenario order. They help you see whether a what-if structure creates continuity, setup, dependency or timing problems. + +# When Should I Use This? + +Use these notes after moving scenes or before comparing and applying a scenario. + +# How To Use It + +Read each note as a review question. Decide whether it points to a real problem, an intentional change or a side effect of the experiment. + +# Example + +A moved scene might now reference an asset before the scene where the asset appears. + +# Writer Tip + +Scenario warnings are safer than main warnings: they let you learn before committing. + +# Common Mistakes + +- Treating scenario warnings as main-story errors. +- Applying a scenario without validating it. +- Ignoring dependency warnings created by scene movement. + +# Related Guides + +- [Scenarios](/Help/Article/scenarios.overview) +- [Warnings](/Help/Article/warnings.overview) diff --git a/PlotLine/Help/Articles/SceneMetrics/AddMetric.md b/PlotLine/Help/Articles/SceneMetrics/AddMetric.md new file mode 100644 index 0000000..22ee01a --- /dev/null +++ b/PlotLine/Help/Articles/SceneMetrics/AddMetric.md @@ -0,0 +1,50 @@ +--- +title: Add Scene Metric +category: Scene Metrics +tags: scene metrics, custom metrics, pacing, revision +contextKey: sceneMetrics.addMetric +micro: Create a custom slider for a repeated story quality. +quickTitle: Add scene metric +quickSummary: Add a scene metric when a story quality is important enough to track across many scenes. +screenshot: +--- + +# Overview + +Add scene metric creates a new slider for this project. Use it for qualities that shape the book and deserve consistent attention. + +# When Should I Use This? + +Use it when the existing metrics do not capture something central to the genre or draft, such as dread, trust, magic exposure, clue pressure or comic energy. + +# How To Use It + +Name the metric clearly, describe what high and low values mean, choose a range, set a neutral default and keep the active metrics list manageable. + +# Understanding the Fields + +| Field | Use it for | +| --- | --- | +| Min and Max | The scale writers will use on scenes. | +| Default | The starting value before a scene is deliberately adjusted. | +| Sort order | Where the metric appears relative to other sliders. | +| Active | Whether the metric is available for scene editing. | + +# Example + +A gothic project might add "Uncanniness" where 1 means ordinary and 10 means openly supernatural. + +# Writer Tip + +Write the description as if future-you will forget what the slider meant. + +# Common Mistakes + +- Adding several metrics that measure the same thing. +- Creating genre metrics that only apply to one scene. +- Changing a metric's meaning halfway through revision. + +# Related Guides + +- [Scene Metrics](/Help/Article/sceneMetrics.overview) +- [Story Health](/Help/Article/storyHealth.overview) diff --git a/PlotLine/Help/Articles/SceneMetrics/DefaultMetrics.md b/PlotLine/Help/Articles/SceneMetrics/DefaultMetrics.md new file mode 100644 index 0000000..851febd --- /dev/null +++ b/PlotLine/Help/Articles/SceneMetrics/DefaultMetrics.md @@ -0,0 +1,42 @@ +--- +title: Default Scene Metrics +category: Scene Metrics +tags: scene metrics, defaults, pacing, genre +contextKey: sceneMetrics.defaultMetrics +micro: Add the standard metrics that help most projects track story shape. +quickTitle: Default metrics +quickSummary: Default metrics provide a useful starting set for tracking intensity, tension, pacing and emotional movement. +screenshot: +--- + +# Overview + +Default scene metrics are the core sliders PlotWeaver Studio expects many projects to use. They may include qualities such as overall intensity, emotional weight, tension, romance, mystery, darkness, hope, comedy or action. + +# When Should I Use This? + +Use this when a project is missing the standard metric set, especially after import, setup changes or experimenting with custom metrics. + +# How To Use It + +Add the missing defaults, then deactivate anything that does not fit this project. Metrics are guidance tools, not rules. + +# Example + +A mystery might keep tension, mystery and darkness active, while a gentler romance might focus more on emotional weight, hope and romance. + +# Writer Tip + +Start with a small set. Metrics work best when you can keep them updated across scenes. + +# Common Mistakes + +- Treating default metrics as mandatory. +- Leaving metrics active just because they exist. +- Using high numbers as a quality score. + +# Related Guides + +- [Scene Metrics](/Help/Article/sceneMetrics.overview) +- [Story Health](/Help/Article/storyHealth.overview) +- [Story Dynamics](/Help/Article/storyDynamics.overview) diff --git a/PlotLine/Help/Articles/SceneMetrics/Edit.md b/PlotLine/Help/Articles/SceneMetrics/Edit.md new file mode 100644 index 0000000..5815f35 --- /dev/null +++ b/PlotLine/Help/Articles/SceneMetrics/Edit.md @@ -0,0 +1,41 @@ +--- +title: Edit Scene Metric +category: Scene Metrics +tags: scene metrics, editing, scale, revision +contextKey: sceneMetrics.edit +micro: Refine a scene metric's name, scale, default and availability. +quickTitle: Edit scene metric +quickSummary: Edit a scene metric when the slider needs clearer meaning, a better scale or a different position. +screenshot: +--- + +# Overview + +Editing a scene metric changes how a project tracks one story quality across scenes. This can affect how writers read graphs and compare pacing, tone or emotional movement. + +# When Should I Use This? + +Use it when the metric name is unclear, the scale is awkward, the default value does not represent neutral, or the metric should no longer be active. + +# How To Use It + +Keep the meaning stable once scenes have values. If you change the definition, review existing scene values so old ratings still make sense. + +# Example + +If "Darkness" was meant as moral darkness but scenes were rated as visual darkness, clarify the description before more values are added. + +# Writer Tip + +Metric descriptions are a contract with future revision. Make them concrete. + +# Common Mistakes + +- Changing min and max without considering existing values. +- Renaming a metric so old scene ratings become misleading. +- Keeping inactive metrics near the top of the list. + +# Related Guides + +- [Scene Metrics](/Help/Article/sceneMetrics.overview) +- [Project Scene Metrics](/Help/Article/sceneMetrics.projectMetrics) diff --git a/PlotLine/Help/Articles/SceneMetrics/Fields/Active.md b/PlotLine/Help/Articles/SceneMetrics/Fields/Active.md new file mode 100644 index 0000000..640dacd --- /dev/null +++ b/PlotLine/Help/Articles/SceneMetrics/Fields/Active.md @@ -0,0 +1,16 @@ +--- +title: Active Metric +category: Scene Metrics +tags: scene metrics, fields, active +contextKey: sceneMetrics.fields.active +micro: Decide whether this metric is currently available on scenes. +quickTitle: Active +quickSummary: Active metrics appear for scene editing; inactive metrics are kept out of the way without necessarily losing past data. +screenshot: +--- + +# Active + +Turn this on when the metric should be available for scene work. Turn it off when the metric no longer helps this project. + +Deactivating a metric is useful when you want less clutter but may still want to preserve earlier values. diff --git a/PlotLine/Help/Articles/SceneMetrics/Fields/DefaultValue.md b/PlotLine/Help/Articles/SceneMetrics/Fields/DefaultValue.md new file mode 100644 index 0000000..8e65a9c --- /dev/null +++ b/PlotLine/Help/Articles/SceneMetrics/Fields/DefaultValue.md @@ -0,0 +1,16 @@ +--- +title: Default Value +category: Scene Metrics +tags: scene metrics, fields, default +contextKey: sceneMetrics.fields.defaultValue +micro: Choose the starting value for scenes before deliberate adjustment. +quickTitle: Default value +quickSummary: Default Value is the neutral starting point for a metric on new or unrated scenes. +screenshot: +--- + +# Default Value + +Choose the value a scene should start with before you deliberately rate it. On a 1 to 10 scale, `5` often works as neutral. + +Use a default that will not accidentally imply every unrated scene is high or low. diff --git a/PlotLine/Help/Articles/SceneMetrics/Fields/MaxValue.md b/PlotLine/Help/Articles/SceneMetrics/Fields/MaxValue.md new file mode 100644 index 0000000..c625e4e --- /dev/null +++ b/PlotLine/Help/Articles/SceneMetrics/Fields/MaxValue.md @@ -0,0 +1,16 @@ +--- +title: Maximum Value +category: Scene Metrics +tags: scene metrics, fields, scale +contextKey: sceneMetrics.fields.maxValue +micro: Set the high end of the metric scale. +quickTitle: Maximum value +quickSummary: Maximum Value defines what the strongest rating means for this scene metric. +screenshot: +--- + +# Maximum Value + +Use this for the high end of the scale. A `10` usually means the quality dominates the scene. + +High does not mean better. It means more present, stronger or more intense. diff --git a/PlotLine/Help/Articles/SceneMetrics/Fields/MinValue.md b/PlotLine/Help/Articles/SceneMetrics/Fields/MinValue.md new file mode 100644 index 0000000..9c4c4ca --- /dev/null +++ b/PlotLine/Help/Articles/SceneMetrics/Fields/MinValue.md @@ -0,0 +1,16 @@ +--- +title: Minimum Value +category: Scene Metrics +tags: scene metrics, fields, scale +contextKey: sceneMetrics.fields.minValue +micro: Set the low end of the metric scale. +quickTitle: Minimum value +quickSummary: Minimum Value defines what the lowest rating means for this scene metric. +screenshot: +--- + +# Minimum Value + +Use this for the low end of the scale. For most projects, `1` works well because it means the quality is barely present. + +Keep the scale easy to interpret. If you change the minimum after rating scenes, review old values. diff --git a/PlotLine/Help/Articles/SceneMetrics/Fields/SortOrder.md b/PlotLine/Help/Articles/SceneMetrics/Fields/SortOrder.md new file mode 100644 index 0000000..e48e75d --- /dev/null +++ b/PlotLine/Help/Articles/SceneMetrics/Fields/SortOrder.md @@ -0,0 +1,16 @@ +--- +title: Sort Order +category: Scene Metrics +tags: scene metrics, fields, order +contextKey: sceneMetrics.fields.sortOrder +micro: Control where this metric appears among the scene sliders. +quickTitle: Sort order +quickSummary: Sort Order places important metrics where writers will see and update them easily. +screenshot: +--- + +# Sort Order + +Lower numbers appear earlier. Use sort order to keep the most important metrics near the top of the scene editor. + +This helps maintain the metrics that matter most during drafting and revision. diff --git a/PlotLine/Help/Articles/SceneMetrics/ProjectMetrics.md b/PlotLine/Help/Articles/SceneMetrics/ProjectMetrics.md new file mode 100644 index 0000000..1aa6578 --- /dev/null +++ b/PlotLine/Help/Articles/SceneMetrics/ProjectMetrics.md @@ -0,0 +1,41 @@ +--- +title: Project Scene Metrics +category: Scene Metrics +tags: scene metrics, project settings, revision +contextKey: sceneMetrics.projectMetrics +micro: Review the metric sliders currently available in this project. +quickTitle: Project scene metrics +quickSummary: Project scene metrics show which sliders are active, how they are ordered and whether scenes already use them. +screenshot: +--- + +# Overview + +Project scene metrics list the sliders available for this project. Active metrics appear in scene editing and can feed analysis views. + +# When Should I Use This? + +Use this section when cleaning up a project's metric set, changing the order of sliders or deactivating metrics that no longer help. + +# How To Use It + +Review each metric's range, default, status and value count. Deactivate a metric when it is no longer useful; remove only unused custom metrics when the app allows it. + +# Example + +If "Violence" has no values in a quiet domestic project, it may be better inactive. If "Tension" has values across every chapter, keep it visible. + +# Writer Tip + +Metrics are most useful when they reveal contrast. Keep the set small enough that each slider has a job. + +# Common Mistakes + +- Removing a metric before checking whether scenes use it. +- Keeping every metric active for every genre. +- Reordering sliders so the important ones are hard to find. + +# Related Guides + +- [Scene Metrics](/Help/Article/sceneMetrics.overview) +- [Add Scene Metric](/Help/Article/sceneMetrics.addMetric) diff --git a/PlotLine/Help/Articles/StoryBible/Attention.md b/PlotLine/Help/Articles/StoryBible/Attention.md new file mode 100644 index 0000000..95abe65 --- /dev/null +++ b/PlotLine/Help/Articles/StoryBible/Attention.md @@ -0,0 +1,42 @@ +--- +title: Story Bible Attention Items +category: Story Bible +tags: story bible, attention, continuity, revision +contextKey: storyBible.attention +micro: Review open questions and story details that may need follow-up. +quickTitle: Attention items +quickSummary: Things that may need attention gathers open questions, warnings and continuity notes from the project reference. +screenshot: +--- + +# Overview + +Attention items are prompts from the project reference. They point to facts, scenes or continuity details that may need review. + +# When Should I Use This? + +Use this section before drafting, before exporting the Story Bible, or during revision triage. + +# How To Use It + +Read each item as a question. Decide whether it needs fixing now, should be handled later, or is intentionally unresolved. + +# Example + +An attention item may remind you that a plot thread is still open or that a scene is missing a key location. + +# Writer Tip + +Attention items reduce the burden of remembering everything. Let the reference system hold the nagging details. + +# Common Mistakes + +- Treating every attention item as urgent. +- Ignoring items before a major export. +- Forgetting that some unresolved questions are deliberate. + +# Related Guides + +- [Story Bible](/Help/Article/storyBible.overview) +- [Warnings](/Help/Article/warnings.overview) +- [Writer Workspace](/Help/Article/workspace.overview) diff --git a/PlotLine/Help/Articles/StoryBible/RevisionStatus.md b/PlotLine/Help/Articles/StoryBible/RevisionStatus.md new file mode 100644 index 0000000..4ba2b18 --- /dev/null +++ b/PlotLine/Help/Articles/StoryBible/RevisionStatus.md @@ -0,0 +1,42 @@ +--- +title: Story Bible Revision Status +category: Story Bible +tags: story bible, revision, drafting, status +contextKey: storyBible.revisionStatus +micro: See revision progress grouped across the project. +quickTitle: Revision status +quickSummary: Revision Status summarises where scenes and chapters sit in the drafting and revision process. +screenshot: +--- + +# Overview + +Revision Status summarises project progress so you can see what is drafted, revised, polished or still waiting for attention. + +# When Should I Use This? + +Use it during planning reviews, before a writing session, or when deciding whether a book is ready for a deeper revision pass. + +# How To Use It + +Scan the groups for uneven progress. Open the relevant scenes or chapters when you need to update details. + +# Example + +If most scenes are drafted but one chapter still has many planning-stage scenes, that chapter may need focused attention before polishing. + +# Writer Tip + +Revision status is a navigation aid, not a measure of quality. + +# Common Mistakes + +- Polishing scenes whose structure is not settled. +- Forgetting to update status after major edits. +- Treating all chapters as equally ready because the draft is complete. + +# Related Guides + +- [Story Bible](/Help/Article/storyBible.overview) +- [Writer Workspace](/Help/Article/workspace.overview) +- [Chapter Workflow](/Help/Article/workspace.chapterWorkflow) diff --git a/PlotLine/Help/Articles/StoryBible/TimelineSummary.md b/PlotLine/Help/Articles/StoryBible/TimelineSummary.md new file mode 100644 index 0000000..9e9c19a --- /dev/null +++ b/PlotLine/Help/Articles/StoryBible/TimelineSummary.md @@ -0,0 +1,42 @@ +--- +title: Story Bible Timeline Summary +category: Story Bible +tags: story bible, timeline, continuity, scenes +contextKey: storyBible.timelineSummary +micro: Review the narrative order as a reference summary. +quickTitle: Timeline summary +quickSummary: Timeline Summary gives a compact reference view of books, chapters and scenes without leaving the Story Bible. +screenshot: +--- + +# Overview + +Timeline Summary shows the narrative order as reference material. It helps you check what happens where without opening the full timeline. + +# When Should I Use This? + +Use it when checking continuity, scene placement, POV, location or whether a fact has already appeared. + +# How To Use It + +Scan by book and chapter, then open the timeline only when you need to edit the order or inspect a scene closely. + +# Example + +Before adding a new clue, check whether a related scene already appears earlier in the same chapter. + +# Writer Tip + +Use this as a quick memory aid during revision. It prevents writing from memory when the project already has a record. + +# Common Mistakes + +- Treating the summary as the place to restructure scenes. +- Ignoring scene POV or location when checking continuity. +- Forgetting to update scene summaries after revision. + +# Related Guides + +- [Story Bible](/Help/Article/storyBible.overview) +- [Scenes](/Help/Article/scenes.overview) +- [Chapters](/Help/Article/chapters.overview) diff --git a/PlotLine/Help/Articles/StoryDynamics/Overview.md b/PlotLine/Help/Articles/StoryDynamics/Overview.md new file mode 100644 index 0000000..db1c46f --- /dev/null +++ b/PlotLine/Help/Articles/StoryDynamics/Overview.md @@ -0,0 +1,44 @@ +--- +title: Story Dynamics +category: Story Dynamics +tags: story dynamics, analytics, pacing, revision +contextKey: storyDynamics.overview +micro: Review broad balance, flow and relationship patterns in the story. +quickTitle: What is Story Dynamics? +quickSummary: Story Dynamics helps authors understand story balance and flow through analytical signals, not fixed prescriptions. +screenshot: +--- + +# Overview + +Story Dynamics helps you understand the balance and flow of a project. It surfaces patterns such as character pairings, neglected arcs, abrupt transitions and advisory continuity signals. + +These views are analytical aids. They visualise trends so you can make better revision choices; they do not prescribe one correct solution. + +# When Should I Use This? + +Use Story Dynamics during revision, after a major restructure, or when the story feels uneven but you cannot yet see why. + +# How To Use It + +Review the broad signals, then open the pages or scenes that deserve closer attention. Treat each signal as a question for the author. + +# Example + +If two central characters rarely share scenes, that may be intentional distance, a structural gap or a sign that their relationship needs more development. + +# Writer Tip + +Analytics are best when paired with taste. Let the data point; let the story decide. + +# Common Mistakes + +- Revising only to satisfy a chart. +- Treating every imbalance as a flaw. +- Ignoring repeated signals that match your own doubts. + +# Related Guides + +- [Story Health](/Help/Article/storyHealth.overview) +- [Scene Metrics](/Help/Article/sceneMetrics.overview) +- [Relationship Map](/Help/Article/relationshipMap.overview) diff --git a/PlotLine/Help/Articles/StoryHealth/Overview.md b/PlotLine/Help/Articles/StoryHealth/Overview.md new file mode 100644 index 0000000..0ee351f --- /dev/null +++ b/PlotLine/Help/Articles/StoryHealth/Overview.md @@ -0,0 +1,44 @@ +--- +title: Story Health +category: Story Health +tags: story health, analytics, revision, warnings +contextKey: storyHealth.overview +micro: Review patterns, gaps and risks across the project. +quickTitle: What is Story Health? +quickSummary: Story Health highlights possible gaps, imbalances and revision risks without replacing author judgement. +screenshot: +--- + +# Overview + +Story Health gathers analytical signals about the project: metric shape, pacing, revision status, scene purpose, warnings, plot threads, assets, POV, character appearances and location use. + +These signals are advisory. They help you find places to investigate; they do not decide what the story should become. + +# When Should I Use This? + +Use Story Health during revision, after structural changes, before drafting a new section, or when a project feels uneven and you need to know where to look. + +# How To Use It + +Start with the broad counts, then open the sections that match your concern. If pacing feels flat, check metric shape and pacing review. If continuity feels shaky, check warnings and asset health. + +# Example + +A long character absence may be fine in one genre and a problem in another. Story Health points it out so you can decide. + +# Writer Tip + +Use analytics as a flashlight, not a steering wheel. + +# Common Mistakes + +- Treating every imbalance as a flaw. +- Revising to satisfy a chart instead of the story. +- Ignoring repeated warnings after a major restructure. + +# Related Guides + +- [Warnings](/Help/Article/warnings.overview) +- [Scene Metrics](/Help/Article/sceneMetrics.overview) +- [Story Dynamics](/Help/Article/storyDynamics.overview) diff --git a/PlotLine/Help/Articles/StoryHealth/PacingReview.md b/PlotLine/Help/Articles/StoryHealth/PacingReview.md new file mode 100644 index 0000000..7da613c --- /dev/null +++ b/PlotLine/Help/Articles/StoryHealth/PacingReview.md @@ -0,0 +1,41 @@ +--- +title: Pacing Review +category: Story Health +tags: story health, pacing, revision +contextKey: storyHealth.pacingReview +micro: Find sustained metric runs that may affect pacing. +quickTitle: Pacing review +quickSummary: Pacing Review highlights repeated high or low metric patterns that may deserve revision attention. +screenshot: +--- + +# Overview + +Pacing Review looks for sustained runs in scene metrics. It helps identify sections that may feel too flat, too intense or too similar for too long. + +# When Should I Use This? + +Use it when readers may need relief, escalation, contrast or a clearer rhythm. + +# How To Use It + +Read the note, open the relevant scene range and decide whether the pattern is intentional. + +# Example + +Three high-tension scenes in a row might be thrilling, or exhausting if none of them changes the story. + +# Writer Tip + +Pacing is contrast plus consequence. + +# Common Mistakes + +- Lowering intensity just because a run is long. +- Ignoring a flat run that was not intended. +- Forgetting quiet scenes can still be powerful. + +# Related Guides + +- [Story Health](/Help/Article/storyHealth.overview) +- [Scene Metrics](/Help/Article/sceneMetrics.overview) diff --git a/PlotLine/Help/Articles/StoryHealth/PlotThreadHealth.md b/PlotLine/Help/Articles/StoryHealth/PlotThreadHealth.md new file mode 100644 index 0000000..2b51dbf --- /dev/null +++ b/PlotLine/Help/Articles/StoryHealth/PlotThreadHealth.md @@ -0,0 +1,41 @@ +--- +title: Plot Thread Health +category: Story Health +tags: story health, plot threads, payoffs +contextKey: storyHealth.plotThreadHealth +micro: Review open, dormant or underpaid plot threads. +quickTitle: Plot thread health +quickSummary: Plot Thread Health highlights threads that may need setup, development or payoff attention. +screenshot: +--- + +# Overview + +Plot Thread Health points to story promises that may be dormant, unresolved, high importance or missing payoff. + +# When Should I Use This? + +Use it during revision when you want to check whether questions, clues and promises are being carried through the story. + +# How To Use It + +Review the flagged threads and decide whether each needs a new beat, clearer payoff or intentional silence. + +# Example + +A high-importance clue without payoff may need a later scene where its meaning becomes clear. + +# Writer Tip + +Readers remember promises. Track them before they become loose ends. + +# Common Mistakes + +- Treating every dormant thread as a mistake. +- Forgetting minor threads can be intentionally quiet. +- Resolving a thread without making the payoff visible. + +# Related Guides + +- [Plot Lines](/Help/Article/plotLines.index) +- [Story Health](/Help/Article/storyHealth.overview) diff --git a/PlotLine/Help/Articles/StoryHealth/RevisionSummary.md b/PlotLine/Help/Articles/StoryHealth/RevisionSummary.md new file mode 100644 index 0000000..4fdc388 --- /dev/null +++ b/PlotLine/Help/Articles/StoryHealth/RevisionSummary.md @@ -0,0 +1,41 @@ +--- +title: Revision Summary +category: Story Health +tags: story health, revision, drafting +contextKey: storyHealth.revisionSummary +micro: See where scenes sit in the writing and revision process. +quickTitle: Revision summary +quickSummary: Revision Summary helps separate drafting, revising and polishing work. +screenshot: +--- + +# Overview + +Revision Summary shows how much of the project sits in each drafting or revision state. + +# When Should I Use This? + +Use it when planning a writing session, preparing a revision pass or checking whether a book is ready for polish. + +# How To Use It + +Look for stages that need attention and open the scenes listed under needs attention. + +# Example + +If many scenes are marked ready for revision but few are polished, plan a structural pass before line editing. + +# Writer Tip + +Do the right kind of work for the current stage. + +# Common Mistakes + +- Polishing before structure is stable. +- Forgetting to update scene status. +- Treating status as a judgement of worth. + +# Related Guides + +- [Writer Workspace](/Help/Article/workspace.overview) +- [Revision Queue](/Help/Article/workspace.revisionQueue) diff --git a/PlotLine/Help/Articles/StoryHealth/SceneMetricShape.md b/PlotLine/Help/Articles/StoryHealth/SceneMetricShape.md new file mode 100644 index 0000000..a27dcd9 --- /dev/null +++ b/PlotLine/Help/Articles/StoryHealth/SceneMetricShape.md @@ -0,0 +1,41 @@ +--- +title: Scene Metric Shape +category: Story Health +tags: story health, scene metrics, pacing, charts +contextKey: storyHealth.sceneMetricShape +micro: Compare scene metric values across narrative order. +quickTitle: Scene metric shape +quickSummary: Scene Metric Shape visualises peaks and rests in metrics such as tension, romance, darkness, hope or mystery. +screenshot: +--- + +# Overview + +Scene Metric Shape shows how selected scene metrics rise and fall across the story. It can reveal pacing patterns, tonal runs and places where the draft may need contrast. + +# When Should I Use This? + +Use it when reviewing emotional intensity, tension, mystery, romance, violence, darkness, hope, comedy or other genre-specific metrics. + +# How To Use It + +Compare the graph to your intention. A flat line may be right for a quiet sequence, or it may show that a chapter needs a turn. + +# Example + +If mystery stays low for several chapters in a mystery novel, the chart asks whether clues, questions or uncertainty need more presence. + +# Writer Tip + +Metrics describe emphasis. They do not score quality. + +# Common Mistakes + +- Assuming every chapter needs the same shape. +- Making every metric high. +- Forgetting that missing values may mean scenes have not been reviewed. + +# Related Guides + +- [Scene Metrics](/Help/Article/sceneMetrics.overview) +- [Story Health](/Help/Article/storyHealth.overview) diff --git a/PlotLine/Help/Articles/StoryHealth/ScenePurposeBalance.md b/PlotLine/Help/Articles/StoryHealth/ScenePurposeBalance.md new file mode 100644 index 0000000..48c2345 --- /dev/null +++ b/PlotLine/Help/Articles/StoryHealth/ScenePurposeBalance.md @@ -0,0 +1,41 @@ +--- +title: Scene Purpose Balance +category: Story Health +tags: story health, scene purpose, revision +contextKey: storyHealth.scenePurposeBalance +micro: Check whether scenes have clear purpose and outcome. +quickTitle: Scene purpose balance +quickSummary: Scene Purpose Balance helps find scenes whose purpose or outcome may be missing. +screenshot: +--- + +# Overview + +Scene Purpose Balance shows how scenes are distributed by purpose and highlights scenes missing purpose or outcome. + +# When Should I Use This? + +Use it when a chapter feels unfocused, repetitive or hard to justify. + +# How To Use It + +Review missing purpose and outcome links. Decide whether each scene needs clearer intent, a stronger consequence or removal. + +# Example + +A scene may have atmosphere and dialogue but no outcome. That does not make it wrong, but it asks what changes by the end. + +# Writer Tip + +Every scene should give the reader something they did not have before. + +# Common Mistakes + +- Treating purpose labels as formula. +- Keeping scenes because they are well written but consequence-free. +- Ignoring repeated missing outcomes. + +# Related Guides + +- [Scenes](/Help/Article/scenes.overview) +- [Story Health](/Help/Article/storyHealth.overview) diff --git a/PlotLine/Help/Articles/StoryHealth/StoryAssetHealth.md b/PlotLine/Help/Articles/StoryHealth/StoryAssetHealth.md new file mode 100644 index 0000000..8858986 --- /dev/null +++ b/PlotLine/Help/Articles/StoryHealth/StoryAssetHealth.md @@ -0,0 +1,41 @@ +--- +title: Story Asset Health +category: Story Health +tags: story health, assets, continuity +contextKey: storyHealth.storyAssetHealth +micro: Review important unresolved or dependency-heavy story assets. +quickTitle: Story asset health +quickSummary: Story Asset Health helps track clues, objects and secrets that may need continuity attention. +screenshot: +--- + +# Overview + +Story Asset Health highlights assets that are unresolved, high importance or connected to dependencies. + +# When Should I Use This? + +Use it when revising clues, objects, documents, secrets or other story items that move through the plot. + +# How To Use It + +Open assets that look important or unresolved and check their state, location, custody, dependencies and scene history. + +# Example + +A high-importance key with no current location may create confusion if later scenes depend on who has it. + +# Writer Tip + +Important assets need a clear chain of meaning, not only a location. + +# Common Mistakes + +- Tracking physical location but not story significance. +- Ignoring unresolved high-importance assets. +- Forgetting dependencies between objects or secrets. + +# Related Guides + +- [Story Assets](/Help/Article/storyAssets.overview) +- [Story Health](/Help/Article/storyHealth.overview) diff --git a/PlotLine/Help/Articles/StoryHealth/WarningHotspots.md b/PlotLine/Help/Articles/StoryHealth/WarningHotspots.md new file mode 100644 index 0000000..970c714 --- /dev/null +++ b/PlotLine/Help/Articles/StoryHealth/WarningHotspots.md @@ -0,0 +1,41 @@ +--- +title: Warning Hotspots +category: Story Health +tags: story health, warnings, continuity +contextKey: storyHealth.warningHotspots +micro: Find scenes with concentrated continuity warnings. +quickTitle: Warning hotspots +quickSummary: Warning Hotspots point to scenes that may deserve review because several warnings gather there. +screenshot: +--- + +# Overview + +Warning Hotspots show where multiple warnings cluster. A cluster may indicate a complex scene, a recent restructure or a continuity risk. + +# When Should I Use This? + +Use it when deciding where to start a cleanup pass. + +# How To Use It + +Open the warning board for a hotspot scene and review the warnings as questions. + +# Example + +A scene with warnings about location, asset state and character knowledge may need one careful continuity pass. + +# Writer Tip + +Hotspots are efficient revision targets because one scene may resolve several related issues. + +# Common Mistakes + +- Assuming every hotspot is broken. +- Dismissing a cluster without opening the scene. +- Fixing warnings one by one without seeing the shared cause. + +# Related Guides + +- [Warnings](/Help/Article/warnings.overview) +- [Story Health](/Help/Article/storyHealth.overview) diff --git a/PlotLine/Help/Articles/Warnings/List.md b/PlotLine/Help/Articles/Warnings/List.md new file mode 100644 index 0000000..b6f87d2 --- /dev/null +++ b/PlotLine/Help/Articles/Warnings/List.md @@ -0,0 +1,41 @@ +--- +title: Warning List +category: Warnings +tags: warnings, review, continuity +contextKey: warnings.list +micro: Review individual warning prompts and decide what to do next. +quickTitle: Warnings list +quickSummary: The Warnings list shows individual advisory prompts you can investigate, dismiss or mark intentional. +screenshot: +--- + +# Overview + +The Warnings list contains the actual review prompts. Each item points to a possible issue, the related scene or entity and available actions. + +# When Should I Use This? + +Use it when you are ready to investigate warnings rather than just view counts. + +# How To Use It + +Open the related scene when available. Dismiss warnings that no longer help, or mark intentional choices when the apparent issue is deliberate. + +# Example + +A character may appear in a scene before their introduction. That could be an error, a flashback or an intentional reveal. + +# Writer Tip + +Ask what the reader knows at this point in the story. + +# Common Mistakes + +- Dismissing warnings without checking context. +- Treating warnings as commands. +- Forgetting to mark intentional exceptions. + +# Related Guides + +- [Warnings](/Help/Article/warnings.overview) +- [Story Health](/Help/Article/storyHealth.overview) diff --git a/PlotLine/Help/Articles/Warnings/SeveritySummary.md b/PlotLine/Help/Articles/Warnings/SeveritySummary.md new file mode 100644 index 0000000..bdea3b5 --- /dev/null +++ b/PlotLine/Help/Articles/Warnings/SeveritySummary.md @@ -0,0 +1,41 @@ +--- +title: Warning Severity Summary +category: Warnings +tags: warnings, severity, continuity +contextKey: warnings.severitySummary +micro: See warning counts grouped by seriousness. +quickTitle: By severity +quickSummary: By severity helps you decide whether to start with errors, warnings or informational review notes. +screenshot: +--- + +# Overview + +By severity groups warnings by how strongly they need review. Severity is a triage signal, not an automatic judgement. + +# When Should I Use This? + +Use it when a project has many warnings and you need to decide where to start. + +# How To Use It + +Begin with the most serious items when preparing for revision, but also scan lower-severity notes for useful clues. + +# Example + +An error may point to missing required continuity. An informational note may still reveal a useful revision question. + +# Writer Tip + +Severity tells you review order, not creative truth. + +# Common Mistakes + +- Ignoring lower severity warnings entirely. +- Treating high severity as always wrong. +- Reviewing counts without opening the actual warnings. + +# Related Guides + +- [Warnings](/Help/Article/warnings.overview) +- [Story Health](/Help/Article/storyHealth.overview) diff --git a/PlotLine/Help/Articles/Warnings/TypeSummary.md b/PlotLine/Help/Articles/Warnings/TypeSummary.md new file mode 100644 index 0000000..844fdbf --- /dev/null +++ b/PlotLine/Help/Articles/Warnings/TypeSummary.md @@ -0,0 +1,41 @@ +--- +title: Warning Type Summary +category: Warnings +tags: warnings, type, continuity +contextKey: warnings.typeSummary +micro: See which kinds of possible issues are most common. +quickTitle: By type +quickSummary: By type groups warnings by continuity area, such as timing, missing information or unresolved dependencies. +screenshot: +--- + +# Overview + +By type shows what kind of warning appears most often. This helps reveal whether the project has a specific kind of revision risk. + +# When Should I Use This? + +Use it when you want to know whether issues are mostly about locations, assets, plot threads, timing or missing scene data. + +# How To Use It + +Look for clusters. A repeated warning type often points to one workflow that needs cleanup. + +# Example + +Many missing-location warnings may mean scene placement needs a focused pass. + +# Writer Tip + +Patterns are more useful than isolated warnings. + +# Common Mistakes + +- Fixing individual warnings without noticing the repeated cause. +- Assuming a common type is automatically a major problem. +- Ignoring type filters on large projects. + +# Related Guides + +- [Warnings](/Help/Article/warnings.overview) +- [Story Health](/Help/Article/storyHealth.overview) diff --git a/PlotLine/Views/Analytics/Index.cshtml b/PlotLine/Views/Analytics/Index.cshtml index afd1e21..024fe0d 100644 --- a/PlotLine/Views/Analytics/Index.cshtml +++ b/PlotLine/Views/Analytics/Index.cshtml @@ -51,7 +51,7 @@

Analytics / Story health

-

@Model.Project.ProjectName

+

@Model.Project.ProjectName

Timeline @@ -99,7 +99,7 @@
-

Scene metric shape

+

Scene metric shape

@Model.MetricGraphs.Count metric@(Model.MetricGraphs.Count == 1 ? "" : "s")
@if (!Model.MetricGraphs.Any() || !metricScenes.Any()) @@ -151,7 +151,7 @@
-

Pacing review

+

Pacing review

@if (!Model.PacingReviewNotes.Any()) {

No sustained pacing runs found in this scope.

@@ -171,7 +171,7 @@
-

Revision summary

+

Revision summary

@foreach (var status in Model.RevisionSummary.Where(x => x.SceneCount > 0 || x.ChapterCount > 0)) {
@@ -192,7 +192,7 @@
-

Scene purpose balance

+

Scene purpose balance

@foreach (var purpose in Model.PurposeSummary) {
@@ -212,7 +212,7 @@
-

Warning hotspots

+

Warning hotspots

@foreach (var count in Model.WarningSeverityCounts) {
@count.SeverityName@count.WarningCount
@@ -229,7 +229,7 @@
-

Plot thread health

+

Plot thread health

@foreach (var thread in Model.ThreadHealth.Where(x => x.IsHighImportanceOpen || x.IsDormant || x.HasClueWithoutPayoff || x.HasQuestionWithoutAnswer).Take(12)) {
@@ -246,7 +246,7 @@
-

Story asset health

+

Story asset health

@foreach (var asset in Model.AssetHealth.Where(x => !x.IsResolved || x.HasDependencies || x.Importance >= 8).Take(12)) { diff --git a/PlotLine/Views/Archives/Index.cshtml b/PlotLine/Views/Archives/Index.cshtml index 4438093..4d35186 100644 --- a/PlotLine/Views/Archives/Index.cshtml +++ b/PlotLine/Views/Archives/Index.cshtml @@ -36,7 +36,7 @@

Restore

-

Archived Records

+

Archived Records

@Model.Items.Count item@(Model.Items.Count == 1 ? "" : "s")
diff --git a/PlotLine/Views/Dynamics/Story.cshtml b/PlotLine/Views/Dynamics/Story.cshtml index 6d49923..b5fbe59 100644 --- a/PlotLine/Views/Dynamics/Story.cshtml +++ b/PlotLine/Views/Dynamics/Story.cshtml @@ -6,7 +6,7 @@

Story Dynamics

-

@Model.Project.ProjectName

+

@Model.Project.ProjectName

Character pairings, neglected arcs, abrupt transitions, knowledge jumps, and advisory continuity signals.

diff --git a/PlotLine/Views/ProjectMetrics/Edit.cshtml b/PlotLine/Views/ProjectMetrics/Edit.cshtml index 2b4f3a9..86ca3ab 100644 --- a/PlotLine/Views/ProjectMetrics/Edit.cshtml +++ b/PlotLine/Views/ProjectMetrics/Edit.cshtml @@ -6,7 +6,7 @@

Project Settings

-

Edit scene metric

+

Edit scene metric

Back to metrics
@@ -27,28 +27,28 @@
- +
- +
- +
- +
- +
diff --git a/PlotLine/Views/ProjectMetrics/Index.cshtml b/PlotLine/Views/ProjectMetrics/Index.cshtml index 5f01cb5..2c2e32c 100644 --- a/PlotLine/Views/ProjectMetrics/Index.cshtml +++ b/PlotLine/Views/ProjectMetrics/Index.cshtml @@ -29,7 +29,7 @@

Defaults

-

Add missing default metrics

+

Add missing default metrics

Adds any missing core metrics for this project without duplicating existing metrics.

@@ -43,7 +43,7 @@

New Metric

-

Add scene metric

+

Add scene metric

@@ -57,25 +57,25 @@
- +
- +
- +
- +
@@ -88,7 +88,7 @@

Available Metrics

-

Project scene metrics

+

Project scene metrics

@Model.Metrics.Count metric@(Model.Metrics.Count == 1 ? "" : "s")
diff --git a/PlotLine/Views/RelationshipMap/Index.cshtml b/PlotLine/Views/RelationshipMap/Index.cshtml index 6cb71ce..340819a 100644 --- a/PlotLine/Views/RelationshipMap/Index.cshtml +++ b/PlotLine/Views/RelationshipMap/Index.cshtml @@ -27,7 +27,7 @@

Relationships

-

Relationship Map

+

Relationship Map

A read-only network of character relationships as of @Model.StoryPointLabel.

diff --git a/PlotLine/Views/Scenarios/Compare.cshtml b/PlotLine/Views/Scenarios/Compare.cshtml index 8bb345d..a1b06c5 100644 --- a/PlotLine/Views/Scenarios/Compare.cshtml +++ b/PlotLine/Views/Scenarios/Compare.cshtml @@ -6,7 +6,7 @@

Scenario Comparison

-

@Model.Scenario.ScenarioName

+

@Model.Scenario.ScenarioName

Review moved scenes and sandbox warnings before applying anything to the main order.

@@ -24,7 +24,7 @@

Moved scenes

-

Main vs Scenario

+

Main vs Scenario

@Model.MovedScenes.Count moved
@@ -51,7 +51,7 @@

Warnings added

-

Scenario Warnings

+

Scenario Warnings

@Model.ScenarioWarnings.Count
@@ -79,11 +79,11 @@
-

Apply Scenario To Main

+

Apply Scenario To Main

This updates the real scene chapter/order using the scenario order. Linked story data stays attached to the same scenes.

- + diff --git a/PlotLine/Views/Scenarios/Create.cshtml b/PlotLine/Views/Scenarios/Create.cshtml index b9dc37e..7a6dd73 100644 --- a/PlotLine/Views/Scenarios/Create.cshtml +++ b/PlotLine/Views/Scenarios/Create.cshtml @@ -6,7 +6,7 @@

Scenario Sandbox

-

Create Scenario

+

Create Scenario

Copies the current scene order into a sandbox. Scenes and story data are not duplicated.

@@ -20,7 +20,7 @@
- + diff --git a/PlotLine/Views/Scenarios/Timeline.cshtml b/PlotLine/Views/Scenarios/Timeline.cshtml index a4ae9dc..eedd1c2 100644 --- a/PlotLine/Views/Scenarios/Timeline.cshtml +++ b/PlotLine/Views/Scenarios/Timeline.cshtml @@ -9,7 +9,7 @@

Scenario Mode

-

@Model.Scenario.ScenarioName

+

@Model.Scenario.ScenarioName

@Model.Scenario.Description

@@ -124,7 +124,7 @@

Scenario warnings

-

Validation Notes

+

Validation Notes

@Model.Warnings.Count
diff --git a/PlotLine/Views/StoryBible/Index.cshtml b/PlotLine/Views/StoryBible/Index.cshtml index 4d08968..2136499 100644 --- a/PlotLine/Views/StoryBible/Index.cshtml +++ b/PlotLine/Views/StoryBible/Index.cshtml @@ -302,7 +302,7 @@

Narrative order

-

Timeline Summary

+

Timeline Summary

Open timeline
@@ -339,7 +339,7 @@

Open Questions

-

Things that may need attention

+

Things that may need attention

@Model.OpenQuestions.Count items
@@ -366,7 +366,7 @@

Revision

-

Revision Status

+

Revision Status

diff --git a/PlotLine/Views/Warnings/Index.cshtml b/PlotLine/Views/Warnings/Index.cshtml index 5cca637..7b1eea6 100644 --- a/PlotLine/Views/Warnings/Index.cshtml +++ b/PlotLine/Views/Warnings/Index.cshtml @@ -96,7 +96,7 @@
-

By severity

+

By severity

@foreach (var count in Model.CountsBySeverity) {
@@ -106,7 +106,7 @@ }
-

By type

+

By type

@foreach (var count in Model.CountsByType.Take(8)) {
@@ -118,7 +118,7 @@
-

Warnings

+

Warnings

@if (!Model.Warnings.Any()) {

No warnings match this view.