Phase 3H Help System additional pages

PlotLine/Help/Articles/Archive/Overview.md

@@ -0,0 +1,51 @@
+---
+title: Archived Items
+category: Archive
+tags: archive, restore, cleanup, recovery, organisation
+contextKey: archive.overview
+micro: Recover or permanently remove planning items that were archived.
+quickTitle: What is the Archive?
+quickSummary: The Archive holds hidden projects and planning items so you can restore useful material or permanently remove items you no longer need.
+screenshot:
+---
+
+# Overview
+
+The Archive gathers items that have been hidden from active project views. Archived items are not gone immediately. They are kept aside so you can recover them if you change your mind.
+
+This is useful in writing because plans evolve. A character may be cut, a scene may be removed, or a scenario may be set aside, only to become useful later. Archiving gives you a softer alternative to deletion.
+
+The Archive also helps keep active lists cleaner. If something is no longer part of the current draft, it can be archived without losing the history of the idea.
+
+# When Should I Use This?
+
+Use the Archive when you want to review hidden work, restore something that should be active again, or permanently delete material you are sure you no longer need.
+
+It is especially useful after big restructuring passes, when several scenes, assets, locations or threads may have been moved out of the active draft.
+
+# How To Use It
+
+Use the filters to narrow the list by project or item type. Restore returns an item to active lists where that makes sense. Delete Forever permanently removes it and should be used carefully.
+
+If you are unsure, restore the item or leave it archived rather than deleting it.
+
+# Example
+
+You archive a subplot thread during a tighter second draft. Later, you realise a clue from that subplot solves a continuity problem. Open the Archive, filter to plot threads, and restore it.
+
+# Writer Tip
+
+Archive is a thinking space, not a bin. Let ideas rest there until you know whether they are truly gone or just waiting for the right draft.
+
+# Common Mistakes
+
+- Using Delete Forever when Archive would be enough.
+- Forgetting to filter by project when many projects are present.
+- Restoring old material without checking whether it still fits the current draft.
+- Treating archived ideas as failures rather than useful spare parts.
+
+# Related Guides
+
+- [Projects](/Help/Article/projects.overview)
+- [Restore Points](/Help/Article/restorePoints.overview)
+- [Story Bible](/Help/Article/storyBible.overview)

PlotLine/Help/Articles/HelpCentre/Overview.md

@@ -0,0 +1,51 @@
+---
+title: Help Centre
+category: Help Centre
+tags: help, guidance, articles, search, learning
+contextKey: helpCentre.overview
+micro: Browse practical guidance for using PlotWeaver Studio.
+quickTitle: What is the Help Centre?
+quickSummary: The Help Centre collects full guides for PlotWeaver Studio so you can search, browse by category and open deeper explanations from contextual help.
+screenshot:
+---
+
+# Overview
+
+The Help Centre is the longer-form guide library for PlotWeaver Studio. Contextual help icons give quick explanations while you work; the Help Centre gives fuller guidance when you want to understand a page or workflow in more detail.
+
+The articles are written for writing practice rather than technical administration. They explain how tools fit into planning, drafting, revision, continuity and series management.
+
+You can search for a topic, browse by category, or open a full article from a help drawer.
+
+# When Should I Use This?
+
+Use the Help Centre when a quick tooltip is not enough. It is helpful when you are learning a new area, returning to a feature after a break, or trying to understand how several planning tools connect.
+
+It is also useful when you know the writing problem but not the page name. Search for terms like "restore", "warnings", "assets" or "scenes".
+
+# How To Use It
+
+Enter a term in the search box or browse the category list. Open an article to read the full guide. Related guide links at the bottom of articles can lead you through connected workflows.
+
+If you open a guide from a help icon, the Help Drawer can keep the article beside the page while you work.
+
+# Example
+
+You see a continuity warning and are not sure whether to dismiss it or mark it intentional. Search the Help Centre for "warnings" and open the guide before deciding.
+
+# Writer Tip
+
+Use help when you are choosing a workflow, not only when something feels broken. A good guide can save several minutes of wandering.
+
+# Common Mistakes
+
+- Looking only for exact page names instead of writing terms.
+- Ignoring related guides when a feature connects to another workflow.
+- Expecting tooltips to contain the full explanation.
+- Leaving the Help Drawer open to an old article after changing pages.
+
+# Related Guides
+
+- [Projects](/Help/Article/projects.overview)
+- [Story Bible](/Help/Article/storyBible.overview)
+- [Warnings](/Help/Article/warnings.overview)

PlotLine/Help/Articles/Projects/Dashboard.md

@@ -0,0 +1,52 @@
+---
+title: Project Dashboard
+category: Projects
+tags: project, dashboard, series, navigation, planning
+contextKey: projectDashboard.overview
+micro: Open the main planning areas for a project from one place.
+quickTitle: What is the Project Dashboard?
+quickSummary: The Project Dashboard gathers the main routes into a project, including books, timeline, story bible, warnings, backups and planning tools.
+screenshot:
+---
+
+# Overview
+
+The Project Dashboard is the main launch point for a single project. It shows the project name, description, books, and the tools connected to that project.
+
+This page is not meant to replace the Timeline. The Timeline is where scene-level planning happens. The Project Dashboard is more like the project table of contents: it helps you move to the right workspace quickly and keeps high-level project actions in one place.
+
+From here you can open books, create a new book, reach the Story Bible, manage scene metrics, download a backup, create restore points, review warnings, or move into the Writer Workspace.
+
+# When Should I Use This?
+
+Use the dashboard when you are orienting yourself at project level. It is useful at the start of a writing session, when you need to decide whether to work on structure, continuity, characters, assets, warnings or backups.
+
+It is also the best place to confirm whether the project has the right books in the right order before going deeper.
+
+# How To Use It
+
+Use the buttons at the top to move to the project area you need. Use the Books section to open book details or add the next book in the sequence.
+
+Download Project Backup when you want a local copy of the project. Use Restore Points when you want a database-saved safety snapshot before major changes.
+
+# Example
+
+Before revising book two, you might open the dashboard, check that both books are present, create a restore point, then move to Warnings or the Timeline depending on the work planned for the day.
+
+# Writer Tip
+
+If you feel lost, come back to the dashboard. It gives you a calmer project-level view before you dive back into scenes and details.
+
+# Common Mistakes
+
+- Treating the dashboard as the place to do detailed scene work.
+- Forgetting to create backups before major restructuring.
+- Ignoring the book list when the project has grown into a series.
+- Jumping into warnings or analytics before the basic hierarchy is in order.
+
+# Related Guides
+
+- [Projects](/Help/Article/projects.overview)
+- [Books](/Help/Article/books.overview)
+- [Story Bible](/Help/Article/storyBible.overview)
+- [Restore Points](/Help/Article/restorePoints.overview)

PlotLine/Help/Articles/Projects/Overview.md

@@ -0,0 +1,52 @@
+---
+title: Projects
+category: Projects
+tags: projects, series, novels, organisation, setup
+contextKey: projects.overview
+micro: Choose and organise the writing projects you are actively developing.
+quickTitle: What are Projects?
+quickSummary: Projects are the main containers for novels, series and story worlds. Use them to keep books, characters, locations and continuity together.
+screenshot:
+---
+
+# Overview
+
+The Projects page is the front door to your writing work. Each project is a container for a novel, a series, or a shared story world. Inside a project you can build books, chapters, scenes, characters, locations, story assets, plot threads, warnings, restore points and exports.
+
+Think of a project as the boundary around a continuity problem. If two books share characters, unresolved questions, locations or timeline consequences, they usually belong in the same project. If they have no meaningful overlap, a separate project may be cleaner.
+
+This page helps you choose what to work on next without opening the full timeline immediately. It is deliberately simple: open a project, edit its basic details, archive work you are not actively using, or create something new.
+
+# When Should I Use This?
+
+Use this page when you are starting a new novel or series, returning to an existing project, or deciding which project needs attention today.
+
+It is also useful when you want to keep dormant ideas out of the way. Archiving a project hides it from normal lists while keeping the data recoverable.
+
+# How To Use It
+
+Open a project to reach its dashboard and connected tools. Use Edit when the title or description needs updating. Use New Project when you are beginning a distinct story container.
+
+If an idea has become a series, you do not need a new project for each book. Add books inside the same project so continuity can be tracked across the whole arc.
+
+# Example
+
+You might have one project called "The Glass Meridian" containing two books, recurring characters, a shared mystery and a set of locations. A separate unrelated romance draft would normally be another project.
+
+# Writer Tip
+
+Name projects for recognition, not perfection. A clear working title is more useful than waiting for the final published title.
+
+# Common Mistakes
+
+- Splitting related books into separate projects too early.
+- Keeping old abandoned tests active instead of archiving them.
+- Using vague titles that make several projects hard to tell apart.
+- Treating the project list as a dumping ground rather than an active writing shelf.
+
+# Related Guides
+
+- [Project Settings](/Help/Article/projectSettings.overview)
+- [Books](/Help/Article/books.overview)
+- [Characters](/Help/Article/characters.overview)
+- [Imports](/Help/Article/imports.overview)

PlotLine/Help/Articles/RestorePoints/Overview.md

@@ -0,0 +1,51 @@
+---
+title: Restore Points
+category: Restore Points
+tags: restore, backup, recovery, safety, project
+contextKey: restorePoints.overview
+micro: Save recoverable snapshots before major project changes.
+quickTitle: What are Restore Points?
+quickSummary: Restore Points are database-saved project snapshots that let you return to an earlier state after risky edits, imports or restructuring.
+screenshot:
+---
+
+# Overview
+
+Restore Points are safety snapshots for a project. They save the current project state as structured backup data inside the database. Later, you can download the snapshot or restore the project from it.
+
+They are designed for moments when you are about to make changes that might be hard to undo: importing a large backup, restructuring chapters, testing a big revision plan, or cleaning up archived material.
+
+Restore Points are different from ordinary exports. A downloaded project backup is a file you keep locally. A restore point stays inside PlotWeaver Studio and is ready to use from this page.
+
+# When Should I Use This?
+
+Create a restore point before major edits, before importing, before restoring from another snapshot, or before trying a structural experiment that affects many records.
+
+You do not need a restore point before every small scene edit. Use them when the cost of manually undoing the change would be high.
+
+# How To Use It
+
+Give the restore point a short name or leave the default name. Add notes if you want to remember why it was created. Download older restore points before deleting them if you want an extra local copy.
+
+When you restore, PlotWeaver creates a safety backup first so the current state can still be recovered.
+
+# Example
+
+Before reworking the order of several chapters, create a restore point called "Before Act Two restructure". If the experiment fails, restore that snapshot and return to the earlier arrangement.
+
+# Writer Tip
+
+Name restore points after the decision you are protecting, not just the date. Future you will thank present you for "Before removing Rebecca subplot".
+
+# Common Mistakes
+
+- Waiting until after a risky change to create the snapshot.
+- Keeping too many unnamed restore points without notes.
+- Confusing downloaded backups with database-saved restore points.
+- Restoring without reading which snapshot is selected.
+
+# Related Guides
+
+- [Project Dashboard](/Help/Article/projectDashboard.overview)
+- [Imports](/Help/Article/imports.overview)
+- [Projects](/Help/Article/projects.overview)

PlotLine/Help/Articles/Scenarios/Overview.md

@@ -0,0 +1,51 @@
+---
+title: Scenarios
+category: Scenarios
+tags: scenarios, structure, revision, sandbox, scene order
+contextKey: scenarios.overview
+micro: Test alternate scene orders without changing the main timeline.
+quickTitle: What are Scenarios?
+quickSummary: Scenarios let you copy the current scene order into a sandbox so you can test structural ideas before applying them to the main story.
+screenshot:
+---
+
+# Overview
+
+Scenarios are planning sandboxes. They let you explore a different scene order without immediately changing the main timeline.
+
+This is useful when a structural idea is promising but risky. You might want to move a reveal earlier, delay a confrontation, split a chapter, or test whether a subplot works better in another position. A scenario gives you room to experiment before committing.
+
+Scenarios do not duplicate the whole story. They copy the order into a separate planning view so you can compare the alternative against the main version.
+
+# When Should I Use This?
+
+Use Scenarios when you are considering a structural change that affects several scenes or chapters. If the change is small and obvious, editing the main timeline may be simpler.
+
+Scenarios are especially useful during revision, when you are testing pacing, reveal order, suspense, emotional build or chapter endings.
+
+# How To Use It
+
+Create a scenario from the current order. Give it a name that describes the experiment. Open the scenario timeline to review the alternate order, then compare it with the main version.
+
+Only apply a scenario to the main story when you are confident the new structure is stronger.
+
+# Example
+
+You create a scenario called "Reveal Later Draft" to test whether the identity of a key witness should be delayed until chapter six. You can compare the sandbox against the main structure before changing the project.
+
+# Writer Tip
+
+Name scenarios after the story question they test. "Reveal Later" is more useful than "Scenario 3".
+
+# Common Mistakes
+
+- Creating scenarios for tiny edits that do not need a sandbox.
+- Applying a scenario before comparing its consequences.
+- Forgetting that the scenario is a test, not automatically the new truth.
+- Keeping old scenarios active after the decision has been made.
+
+# Related Guides
+
+- [Project Dashboard](/Help/Article/projectDashboard.overview)
+- [Scenes](/Help/Article/scenes.overview)
+- [Warnings](/Help/Article/warnings.overview)

PlotLine/Help/Articles/StoryBible/Overview.md

@@ -0,0 +1,52 @@
+---
+title: Story Bible
+category: Story Bible
+tags: story bible, reference, continuity, characters, threads
+contextKey: storyBible.overview
+micro: Review the project reference in one searchable place.
+quickTitle: What is the Story Bible?
+quickSummary: The Story Bible brings together characters, threads, assets, locations, relationships, timeline notes and revision attention for the project.
+screenshot:
+---
+
+# Overview
+
+The Story Bible is the project reference shelf. It gathers important planning information into one searchable view so you can check what is already true in the story.
+
+It includes characters, plot threads, story assets, relationships, locations, timeline summaries, revision status and attention items. The aim is not to replace detailed editing pages, but to help you answer the question: "What do I already know about this project?"
+
+For long novels and series, this becomes increasingly valuable. The more moving parts a story has, the more useful it is to have one place that summarises them.
+
+# When Should I Use This?
+
+Use the Story Bible when you need context before writing or revising. It is useful for checking character names, recurring objects, unresolved threads, relationship history, places and continuity notes.
+
+It is also useful before exporting reference material for review, planning meetings or revision passes.
+
+# How To Use It
+
+Use search when you are looking for a specific person, place, asset or thread. Use the sections to browse by topic. Open detail pages when you need to edit something.
+
+Use exports when you want a printable or portable reference pack.
+
+# Example
+
+Before writing a scene in the Blue Bedroom, search the Story Bible for the location, related assets and characters who have appeared there. This can prevent contradictions before they reach the draft.
+
+# Writer Tip
+
+Make the Story Bible part of revision, not only planning. It becomes strongest when you check it after the draft has changed.
+
+# Common Mistakes
+
+- Treating the Story Bible as static once the first outline exists.
+- Searching only names and forgetting assets, places and threads.
+- Editing by memory when the project already contains the answer.
+- Exporting reference material before reviewing warnings or revision notes.
+
+# Related Guides
+
+- [Characters](/Help/Article/characters.overview)
+- [Story Assets](/Help/Article/storyAssets.overview)
+- [Locations](/Help/Article/locations.overview)
+- [Warnings](/Help/Article/warnings.overview)

PlotLine/Help/Articles/Warnings/Overview.md

@@ -0,0 +1,52 @@
+---
+title: Continuity Warnings
+category: Warnings
+tags: warnings, continuity, validation, revision, review
+contextKey: warnings.overview
+micro: Review possible continuity issues before they become draft problems.
+quickTitle: What are Warnings?
+quickSummary: Warnings highlight possible continuity and planning issues so you can review them, dismiss them, or mark intentional choices.
+screenshot:
+---
+
+# Overview
+
+Continuity Warnings are review prompts. They point to places where the project may contain a contradiction, missing link, timing issue, dependency problem or other planning risk.
+
+A warning is not always an error. Fiction often uses secrets, reversals and deliberate gaps. The purpose of this page is to help you decide what needs fixing, what can be dismissed, and what is intentional.
+
+The warning list is most useful during revision, after imports, after timeline changes, or before a serious drafting session.
+
+# When Should I Use This?
+
+Use Warnings when you want to check project health. Run validation after making structural changes, adding dependencies, changing scene order, moving characters, or editing assets and locations.
+
+Use the filters when a large project has many warnings and you want to focus on one book, severity, type or entity.
+
+# How To Use It
+
+Validate the project or selected book. Review the summary counts, then work through the warning list. Open the related scene where available.
+
+Dismiss warnings that are no longer useful. Mark a warning intentional when the apparent issue is part of the story design.
+
+# Example
+
+A scene may use a story asset before the scene where the asset is introduced. The warning does not rewrite your story; it asks you to check whether the order is intentional or whether a scene needs moving.
+
+# Writer Tip
+
+Use warnings as questions, not verdicts. "Is this deliberate?" is often the most useful revision question in a complex story.
+
+# Common Mistakes
+
+- Treating every warning as automatically wrong.
+- Ignoring warnings after a major restructure.
+- Dismissing warnings without checking the related scene.
+- Forgetting to mark deliberate choices as intentional.
+
+# Related Guides
+
+- [Story Bible](/Help/Article/storyBible.overview)
+- [Scenes](/Help/Article/scenes.overview)
+- [Story Assets](/Help/Article/storyAssets.overview)
+- [Locations](/Help/Article/locations.overview)

PlotLine/Views/Archives/Index.cshtml

@@ -6,7 +6,7 @@
 <div class="page-heading">
     <div>
         <p class="eyebrow">Archive</p>
-        <h1>Archived Items</h1>
+        <h1>Archived Items <help-icon key="archive.overview" /></h1>
         <p class="lead-text">Restore projects, scenes, characters, assets, locations, threads, scenarios, and other archived planning items.</p>
     </div>
 </div>

PlotLine/Views/Help/Index.cshtml

@@ -10,7 +10,7 @@
 <div class="page-heading">
     <div>
         <p class="eyebrow">Guidance</p>
-        <h1>Help Centre</h1>
+        <h1>Help Centre <help-icon key="helpCentre.overview" /></h1>
         <p class="lead-text">Find practical guidance for planning, tracking, and shaping your story in PlotWeaver Studio.</p>
     </div>
 </div>

PlotLine/Views/ProjectRestorePoints/Index.cshtml

@@ -31,7 +31,7 @@
 <div class="page-heading compact">
     <div>
         <p class="eyebrow">Project backup</p>
-        <h1>Restore Points</h1>
+        <h1>Restore Points <help-icon key="restorePoints.overview" /></h1>
         <p class="lead-text">Create manual database-saved snapshots of the project export JSON.</p>
     </div>
     <div class="button-row">

PlotLine/Views/Projects/Details.cshtml

@@ -36,7 +36,7 @@
 <div class="page-heading">
     <div>
         <p class="eyebrow">Project / Series</p>
-        <h1>@Model.Project.ProjectName</h1>
+        <h1>@Model.Project.ProjectName <help-icon key="projectDashboard.overview" /></h1>
         @if (!string.IsNullOrWhiteSpace(Model.Project.Description))
         {
             <p class="lead-text">@Model.Project.Description</p>

PlotLine/Views/Projects/Index.cshtml

@@ -6,7 +6,7 @@
 <div class="page-heading">
     <div>
         <p class="eyebrow">Series planning</p>
-        <h1>Projects</h1>
+        <h1>Projects <help-icon key="projects.overview" /></h1>
     </div>
     <div class="button-row">
         <a class="btn btn-outline-primary" asp-controller="Imports" asp-action="Index">Import JSON</a>

PlotLine/Views/Scenarios/Create.cshtml

@@ -6,7 +6,7 @@
 <div class="page-heading">
     <div>
         <p class="eyebrow">Scenario Sandbox</p>
-        <h1>Create Scenario</h1>
+        <h1>Create Scenario <help-icon key="scenarios.overview" /></h1>
         <p class="lead-text">Copies the current scene order into a sandbox. Scenes and story data are not duplicated.</p>
     </div>
 </div>

PlotLine/Views/Scenarios/Index.cshtml

@@ -18,7 +18,7 @@
 <div class="page-heading">
     <div>
         <p class="eyebrow">Planning sandbox</p>
-        <h1>Scenarios</h1>
+        <h1>Scenarios <help-icon key="scenarios.overview" /></h1>
         <p class="lead-text">Test structural changes without changing the main story order.</p>
     </div>
     <a class="btn btn-primary" asp-action="Create" asp-route-projectId="@Model.Project.ProjectID">Create Scenario</a>

PlotLine/Views/StoryBible/Index.cshtml

@@ -33,7 +33,7 @@
 <div class="page-heading story-bible-heading">
     <div>
         <p class="eyebrow">Reference</p>
-        <h1>Story Bible</h1>
+        <h1>Story Bible <help-icon key="storyBible.overview" /></h1>
         <p class="lead-text">A project-level reference for people, threads, places, assets, continuity, and revision attention.</p>
     </div>
     <form class="story-bible-search" asp-action="Index" method="get">

PlotLine/Views/Warnings/Index.cshtml

@@ -22,7 +22,7 @@
 <div class="page-heading compact">
     <div>
         <p class="eyebrow">Continuity</p>
-        <h1>@Model.Project.ProjectName</h1>
+        <h1>@Model.Project.ProjectName <help-icon key="warnings.overview" /></h1>
     </div>
     <div class="button-row">
         <form asp-action="ValidateProject" method="post">