diff --git a/PlotLine/Controllers/PublicController.cs b/PlotLine/Controllers/PublicController.cs index 12fd283..7ce13bb 100644 --- a/PlotLine/Controllers/PublicController.cs +++ b/PlotLine/Controllers/PublicController.cs @@ -8,7 +8,7 @@ namespace PlotLine.Controllers; [Route("")] public sealed class PublicController : Controller { - private const string SupportEmail = "hello@plotweaver.studio"; + private const string SupportEmail = "hello@plotdirector.com"; private const string PolicyDate = "June 7, 2026"; [HttpGet("About")] diff --git a/PlotLine/Docs/Architecture/Phase5-MultiUser-Subscription-Architecture.md b/PlotLine/Docs/Architecture/Phase5-MultiUser-Subscription-Architecture.md index 26ff295..6def853 100644 --- a/PlotLine/Docs/Architecture/Phase5-MultiUser-Subscription-Architecture.md +++ b/PlotLine/Docs/Architecture/Phase5-MultiUser-Subscription-Architecture.md @@ -1,4 +1,4 @@ -# PlotWeaver Studio +# PlotDirector # Phase 5 -- Multi-User, Collaboration & Subscription Architecture @@ -10,15 +10,15 @@ Date: June 2026 Phase 5 introduces multi-user support, subscriptions, collaboration capabilities, storage management, auditing, and monetisation foundations -to PlotWeaver Studio. +to PlotDirector. -The goal is to transform PlotWeaver Studio from a single-user authoring +The goal is to transform PlotDirector from a single-user authoring platform into a secure SaaS application while preserving its core philosophy as a planning and writing workspace for authors. ## Core Principles -- PlotWeaver Studio is an active workspace, not a permanent archive. +- PlotDirector is an active workspace, not a permanent archive. - Security takes precedence over convenience. - Collaboration supports planning, not real-time writing. - Subscription limits should be generous but prevent abuse. @@ -27,7 +27,7 @@ philosophy as a planning and writing workspace for authors. ### User -Authenticated account holder within PlotWeaver Studio. +Authenticated account holder within PlotDirector. ### Project diff --git a/PlotLine/Help/Articles/Books/Overview.md b/PlotLine/Help/Articles/Books/Overview.md index d9899c4..4becb5b 100644 --- a/PlotLine/Help/Articles/Books/Overview.md +++ b/PlotLine/Help/Articles/Books/Overview.md @@ -11,7 +11,7 @@ screenshot: # Overview -Books are the major containers inside a PlotWeaver Studio project. A project may be a single novel, but it can also be a series, trilogy, collection of novellas, or long-running world with several planned instalments. Books give that larger structure somewhere practical to live. +Books are the major containers inside a PlotDirector project. A project may be a single novel, but it can also be a series, trilogy, collection of novellas, or long-running world with several planned instalments. Books give that larger structure somewhere practical to live. Each book contains chapters, and each chapter contains scenes. This hierarchy keeps the writing plan readable while still allowing story details to connect across the whole project. A clue introduced in book one, a relationship shift in book two, or an asset that returns in book three can remain part of the same continuity system. diff --git a/PlotLine/Help/Articles/Chapters/Overview.md b/PlotLine/Help/Articles/Chapters/Overview.md index 8cb0361..ec2aa9c 100644 --- a/PlotLine/Help/Articles/Chapters/Overview.md +++ b/PlotLine/Help/Articles/Chapters/Overview.md @@ -11,9 +11,9 @@ screenshot: # Overview -Chapters are the reader-facing containers that turn a sequence of scenes into a shaped reading experience. In PlotWeaver Studio, a chapter belongs to a book and contains one or more scenes. The chapter does not need to carry every detail of the action. Its job is to help you organise the narrative, decide where a reader enters and leaves a movement, and keep the rhythm of the book visible. +Chapters are the reader-facing containers that turn a sequence of scenes into a shaped reading experience. In PlotDirector, a chapter belongs to a book and contains one or more scenes. The chapter does not need to carry every detail of the action. Its job is to help you organise the narrative, decide where a reader enters and leaves a movement, and keep the rhythm of the book visible. -Think of a chapter as a purposeful stretch of story. It may cover one continuous sequence, a set of related beats, a shift in point of view, or a deliberate contrast between scenes. Some writers plan chapters before drafting. Others draft scenes first and only later decide where chapter breaks should fall. PlotWeaver Studio supports both approaches because the scenes remain the core building blocks. +Think of a chapter as a purposeful stretch of story. It may cover one continuous sequence, a set of related beats, a shift in point of view, or a deliberate contrast between scenes. Some writers plan chapters before drafting. Others draft scenes first and only later decide where chapter breaks should fall. PlotDirector supports both approaches because the scenes remain the core building blocks. # When Should I Use This? diff --git a/PlotLine/Help/Articles/Characters/Fields/Reciprocal.md b/PlotLine/Help/Articles/Characters/Fields/Reciprocal.md index 971d4c4..444fd23 100644 --- a/PlotLine/Help/Articles/Characters/Fields/Reciprocal.md +++ b/PlotLine/Help/Articles/Characters/Fields/Reciprocal.md @@ -3,7 +3,7 @@ title: Reciprocal Relationship category: Characters tags: characters, relationships, fields contextKey: characters.relationships.reciprocal -micro: Decide whether PlotWeaver should create the reverse relationship too. +micro: Decide whether PlotDirector should create the reverse relationship too. quickTitle: Reciprocal quickSummary: Turn this on when the reverse connection should also exist, such as parent and child, siblings or friends. screenshot: @@ -11,6 +11,6 @@ screenshot: # Reciprocal -Reciprocal tells PlotWeaver to create the reverse relationship too. If Annie is Beth's parent, Beth is Annie's child. +Reciprocal tells PlotDirector to create the reverse relationship too. If Annie is Beth's parent, Beth is Annie's child. Use this for relationships where both directions should be tracked. Turn it off when the connection is one-sided, secret, unequal or should be handled separately. diff --git a/PlotLine/Help/Articles/Characters/InitialRelationships.md b/PlotLine/Help/Articles/Characters/InitialRelationships.md index 387db8e..436d623 100644 --- a/PlotLine/Help/Articles/Characters/InitialRelationships.md +++ b/PlotLine/Help/Articles/Characters/InitialRelationships.md @@ -30,7 +30,7 @@ Initial Relationships can also separate story truth from reader knowledge. The w | Awareness | Who knows about the relationship or understands its true nature. | The writer knows Beth and Maggie are sisters before the reader does. | | Initial book | Where this relationship baseline begins. | Book 1 if the bond exists from the start; Book 2 if the character enters the series later. | | Confidence / intensity | How strong, certain or emotionally charged the relationship is. | 10 for devoted family or intense hatred; 2 for a weak acquaintance. | -| Reciprocal | Whether PlotWeaver should also create the reverse connection. | If Annie is Beth's parent, Beth is Annie's child. | +| Reciprocal | Whether PlotDirector should also create the reverse connection. | If Annie is Beth's parent, Beth is Annie's child. | | Reader initially knows | Whether the reader knows this relationship at the starting point. | Untick for hidden family ties, secret affairs or delayed reveals. | | Notes | Extra context, hidden history or author-only explanation. | "The reader thinks they are strangers, but Annie is Beth's mother." | diff --git a/PlotLine/Help/Articles/Characters/Overview.md b/PlotLine/Help/Articles/Characters/Overview.md index b1b2f16..81f8602 100644 --- a/PlotLine/Help/Articles/Characters/Overview.md +++ b/PlotLine/Help/Articles/Characters/Overview.md @@ -11,7 +11,7 @@ screenshot: # Overview -Characters are the people, beings or important figures who move through your story. PlotWeaver Studio treats characters as more than a name in a list. A character can appear in scenes, carry knowledge, form relationships, connect to story assets, move between locations and develop an arc across the book or series. +Characters are the people, beings or important figures who move through your story. PlotDirector treats characters as more than a name in a list. A character can appear in scenes, carry knowledge, form relationships, connect to story assets, move between locations and develop an arc across the book or series. You can use character records lightly at first. A name and a short description are enough to begin. As the story becomes more complex, the same record can grow into a continuity anchor: where the character appears, what they know, how they feel, what relationships have changed, and which scenes matter most to their journey. @@ -27,7 +27,7 @@ You do not need to create a full record for every unnamed passer-by. If someone Start with the character's display name and a short description. Add details that help you identify them quickly while planning. Then assign the character to scenes where they appear. Scene appearances are important because they allow the rest of the system to answer questions such as: when did this character last appear, where were they, and what did they know at that point? -Use relationship tools to record initial relationships and later changes. A character may begin as a stranger, become a friend, and later be revealed as family. PlotWeaver Studio keeps that evolution visible without erasing the past. +Use relationship tools to record initial relationships and later changes. A character may begin as a stranger, become a friend, and later be revealed as family. PlotDirector keeps that evolution visible without erasing the past. For revision, use character pages to look for long absences, uneven appearances and key scenes that define an arc. diff --git a/PlotLine/Help/Articles/HelpCentre/Overview.md b/PlotLine/Help/Articles/HelpCentre/Overview.md index 4567613..831e032 100644 --- a/PlotLine/Help/Articles/HelpCentre/Overview.md +++ b/PlotLine/Help/Articles/HelpCentre/Overview.md @@ -3,15 +3,15 @@ title: Help Centre category: Help Centre tags: help, guidance, articles, search, learning contextKey: helpCentre.overview -micro: Browse practical guidance for using PlotWeaver Studio. +micro: Browse practical guidance for using PlotDirector. 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. +quickSummary: The Help Centre collects full guides for PlotDirector 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 Help Centre is the longer-form guide library for PlotDirector. 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. diff --git a/PlotLine/Help/Articles/Imports/Overview.md b/PlotLine/Help/Articles/Imports/Overview.md index efa67ad..94d5a87 100644 --- a/PlotLine/Help/Articles/Imports/Overview.md +++ b/PlotLine/Help/Articles/Imports/Overview.md @@ -3,15 +3,15 @@ title: Imports category: Imports tags: imports, json, structure, setup, migration contextKey: imports.overview -micro: Bring prepared project structure into PlotWeaver Studio. +micro: Bring prepared project structure into PlotDirector. quickTitle: What are Imports? -quickSummary: Imports let you bring prepared story structure into PlotWeaver Studio so books, chapters, scenes and related items can be created together. +quickSummary: Imports let you bring prepared story structure into PlotDirector so books, chapters, scenes and related items can be created together. screenshot: --- # Overview -Imports allow you to bring prepared story structure into PlotWeaver Studio instead of entering every project, book, chapter and scene by hand. This is useful when you have planned elsewhere, generated a structured outline, or need to move a project from another format into the app. +Imports allow you to bring prepared story structure into PlotDirector instead of entering every project, book, chapter and scene by hand. This is useful when you have planned elsewhere, generated a structured outline, or need to move a project from another format into the app. The import page is intentionally practical. You can upload or paste a JSON package, preview the result, run checks, and then create a new project when the package looks safe. The goal is to reduce setup friction while still protecting your data from accidental messy imports. @@ -35,7 +35,7 @@ After a successful import, open the created project and review the books, chapte # Example -You may have an outline with three books, thirty chapters and two hundred scenes. Entering that manually would be slow. An import package can create the structure, then you can use PlotWeaver Studio to refine scene summaries, metrics, relationships, locations and continuity. +You may have an outline with three books, thirty chapters and two hundred scenes. Entering that manually would be slow. An import package can create the structure, then you can use PlotDirector to refine scene summaries, metrics, relationships, locations and continuity. # Writer Tip diff --git a/PlotLine/Help/Articles/Locations/Overview.md b/PlotLine/Help/Articles/Locations/Overview.md index b3daf31..097248f 100644 --- a/PlotLine/Help/Articles/Locations/Overview.md +++ b/PlotLine/Help/Articles/Locations/Overview.md @@ -11,7 +11,7 @@ screenshot: # Overview -Locations are the places where your story happens. They can be broad settings, such as a city or estate, or specific places, such as a bedroom, kitchen, railway platform, office, cellar or garden path. PlotWeaver Studio uses locations to support both atmosphere and continuity. +Locations are the places where your story happens. They can be broad settings, such as a city or estate, or specific places, such as a bedroom, kitchen, railway platform, office, cellar or garden path. PlotDirector uses locations to support both atmosphere and continuity. A location is not only scenery. It affects what characters can see, hear, hide, discover and misunderstand. In a tightly plotted story, the distance between rooms may matter. In a mystery, who could hear a conversation may matter. In a romance, returning to the same place after an emotional change may matter. Locations give those details a stable home. diff --git a/PlotLine/Help/Articles/Projects/Settings.md b/PlotLine/Help/Articles/Projects/Settings.md index a26ca52..9f31211 100644 --- a/PlotLine/Help/Articles/Projects/Settings.md +++ b/PlotLine/Help/Articles/Projects/Settings.md @@ -11,7 +11,7 @@ screenshot: # Overview -Project Settings define the working container for your story. In PlotWeaver Studio, a project can be a single novel, a planned series, a shared story world, or a large writing idea that will eventually split into several books. +Project Settings define the working container for your story. In PlotDirector, a project can be a single novel, a planned series, a shared story world, or a large writing idea that will eventually split into several books. The project is where the major pieces connect: books, chapters, scenes, characters, locations, assets, plot threads, relationship history and workspace queues. The settings page keeps the practical identity of that container simple and editable. diff --git a/PlotLine/Help/Articles/RestorePoints/Overview.md b/PlotLine/Help/Articles/RestorePoints/Overview.md index c844b37..dd282b3 100644 --- a/PlotLine/Help/Articles/RestorePoints/Overview.md +++ b/PlotLine/Help/Articles/RestorePoints/Overview.md @@ -15,7 +15,7 @@ Restore Points are safety snapshots for a project. They save the current project 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. +Restore Points are different from ordinary exports. A downloaded project backup is a file you keep locally. A restore point stays inside PlotDirector and is ready to use from this page. # When Should I Use This? @@ -27,7 +27,7 @@ You do not need a restore point before every small scene edit. Use them when the 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. +When you restore, PlotDirector creates a safety backup first so the current state can still be recovered. # Example diff --git a/PlotLine/Help/Articles/SceneMetrics/DefaultMetrics.md b/PlotLine/Help/Articles/SceneMetrics/DefaultMetrics.md index 851febd..62be71e 100644 --- a/PlotLine/Help/Articles/SceneMetrics/DefaultMetrics.md +++ b/PlotLine/Help/Articles/SceneMetrics/DefaultMetrics.md @@ -11,7 +11,7 @@ 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. +Default scene metrics are the core sliders PlotDirector 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? diff --git a/PlotLine/Help/Articles/Scenes/Overview.md b/PlotLine/Help/Articles/Scenes/Overview.md index 149e0cd..63f7ddd 100644 --- a/PlotLine/Help/Articles/Scenes/Overview.md +++ b/PlotLine/Help/Articles/Scenes/Overview.md @@ -5,15 +5,15 @@ tags: scenes, structure, pacing, metrics, purpose contextKey: scenes.overview micro: Plan each story beat with purpose, time, consequences and emotional shape. quickTitle: What are Scenes? -quickSummary: Scenes are the core building blocks of PlotWeaver Studio, where story action, character change and continuity details come together. +quickSummary: Scenes are the core building blocks of PlotDirector, where story action, character change and continuity details come together. screenshot: --- # Overview -Scenes are the heart of PlotWeaver Studio. A scene is a single unit of story action: something happens, someone wants something, pressure changes, and the reader leaves with a different understanding than they had before. Books and chapters provide structure, but scenes are where the story actually moves. +Scenes are the heart of PlotDirector. A scene is a single unit of story action: something happens, someone wants something, pressure changes, and the reader leaves with a different understanding than they had before. Books and chapters provide structure, but scenes are where the story actually moves. -In PlotWeaver Studio, a scene can hold its title, summary, time information, revision status, purpose, outcome, character appearances, assets, locations, attachments and metrics. You do not need to fill every field immediately. The point is to give you a practical place to capture the details that matter when you are planning, drafting or revising. +In PlotDirector, a scene can hold its title, summary, time information, revision status, purpose, outcome, character appearances, assets, locations, attachments and metrics. You do not need to fill every field immediately. The point is to give you a practical place to capture the details that matter when you are planning, drafting or revising. The scene editor is also designed to support continuity. If a character enters from one location and exits to another, if an object changes hands, or if the emotional weight spikes sharply, the scene is the place where that evidence belongs. diff --git a/PlotLine/Help/Articles/StoryAssets/Overview.md b/PlotLine/Help/Articles/StoryAssets/Overview.md index db49391..645a79d 100644 --- a/PlotLine/Help/Articles/StoryAssets/Overview.md +++ b/PlotLine/Help/Articles/StoryAssets/Overview.md @@ -11,7 +11,7 @@ screenshot: # Overview -Story Assets are important things that move through the story or matter to the plot. They might be physical objects, clues, documents, weapons, letters, heirlooms, passwords, secrets, debts, promises or pieces of evidence. If something has continuity weight, PlotWeaver Studio can treat it as an asset. +Story Assets are important things that move through the story or matter to the plot. They might be physical objects, clues, documents, weapons, letters, heirlooms, passwords, secrets, debts, promises or pieces of evidence. If something has continuity weight, PlotDirector can treat it as an asset. An asset does not have to be glamorous. A hotel key, a torn photograph, a train ticket or a missing notebook can be more important than a dramatic artefact if it affects what characters know or what they can do. The purpose of asset tracking is to stop important items becoming vague once the plot becomes busy. diff --git a/PlotLine/Help/Articles/Workspace/Overview.md b/PlotLine/Help/Articles/Workspace/Overview.md index 2eb36b2..1b68443 100644 --- a/PlotLine/Help/Articles/Workspace/Overview.md +++ b/PlotLine/Help/Articles/Workspace/Overview.md @@ -13,7 +13,7 @@ screenshot: The Writer Workspace is a practical working view. It helps you decide what to do next without reopening every book, chapter and scene. Instead of showing the whole structure, it gathers scenes and reminders into useful queues: continue writing, needs attention, revision, polishing and story health reminders. -This is where PlotWeaver Studio becomes less like a filing cabinet and more like a desk. The timeline is for seeing story shape. The workspace is for choosing the next piece of work. +This is where PlotDirector becomes less like a filing cabinet and more like a desk. The timeline is for seeing story shape. The workspace is for choosing the next piece of work. The queues are based on the information already recorded in your scenes and project. A scene that is planned may belong in a drafting queue. A scene with structural uncertainty may need attention. A nearly finished scene may belong in polishing. Reminders point you back to continuity, research or story health issues that should not be forgotten. diff --git a/PlotLine/Help/HelpAuthoringGuidelines.md b/PlotLine/Help/HelpAuthoringGuidelines.md index 96f5ce9..b40dc92 100644 --- a/PlotLine/Help/HelpAuthoringGuidelines.md +++ b/PlotLine/Help/HelpAuthoringGuidelines.md @@ -3,15 +3,15 @@ title: Help Authoring Guidelines category: Internal tags: help, authoring, guidelines contextKey: internal.helpAuthoringGuidelines -micro: Internal guidance for writing PlotWeaver contextual help. +micro: Internal guidance for writing PlotDirector contextual help. quickTitle: Help authoring guidelines -quickSummary: Internal guidance for applying the three-level help pattern across PlotWeaver Studio. +quickSummary: Internal guidance for applying the three-level help pattern across PlotDirector. screenshot: --- # Three-Level Help Pattern -Use this guideline when adding contextual help to a new PlotWeaver Studio area. The goal is to help authors understand the writing purpose of a page, section or field without exposing implementation details. +Use this guideline when adding contextual help to a new PlotDirector area. The goal is to help authors understand the writing purpose of a page, section or field without exposing implementation details. # Level 1: Page Help diff --git a/PlotLine/Models/EmailSettings.cs b/PlotLine/Models/EmailSettings.cs index 1e72162..43e40df 100644 --- a/PlotLine/Models/EmailSettings.cs +++ b/PlotLine/Models/EmailSettings.cs @@ -8,5 +8,5 @@ public sealed class EmailSettings public string Password { get; set; } = string.Empty; public bool EnableSsl { get; set; } = true; public string FromAddress { get; set; } = string.Empty; - public string FromName { get; set; } = "PlotWeaver Studio"; + public string FromName { get; set; } = "PlotDirector"; } diff --git a/PlotLine/Models/ProjectBackupModels.cs b/PlotLine/Models/ProjectBackupModels.cs index 965d795..27c0594 100644 --- a/PlotLine/Models/ProjectBackupModels.cs +++ b/PlotLine/Models/ProjectBackupModels.cs @@ -5,7 +5,7 @@ public sealed class ProjectBackupExport public string Format { get; init; } = "PlotWeaver.ProjectBackup"; public string FormatVersion { get; init; } = "1.0"; public DateTime ExportedAtUtc { get; init; } - public string SourceApplication { get; init; } = "PlotWeaver Studio"; + public string SourceApplication { get; init; } = "PlotDirector"; public Project? Project { get; init; } public ProjectBackupData Data { get; init; } = new(); public ProjectBackupDiagnostics Diagnostics { get; init; } = new(); diff --git a/PlotLine/Services/AuthServices.cs b/PlotLine/Services/AuthServices.cs index 0b47b21..96ef325 100644 --- a/PlotLine/Services/AuthServices.cs +++ b/PlotLine/Services/AuthServices.cs @@ -61,28 +61,28 @@ public sealed class EmailService( { var link = BuildAccountUrl("VerifyEmail", token); var (plainText, html) = BuildTemplate( - "Verify your PlotWeaver Studio account", + "Verify your PlotDirector account", displayName, - "Please verify your email address to finish setting up your PlotWeaver Studio account.", + "Please verify your email address to finish setting up your PlotDirector account.", "Verify account", link, "This link expires in 24 hours."); - return QueueAsync(email, displayName, "Verify your PlotWeaver Studio account", plainText, html); + return QueueAsync(email, displayName, "Verify your PlotDirector account", plainText, html); } public Task SendPasswordResetEmailAsync(string email, string displayName, Guid token) { var link = BuildAccountUrl("ResetPassword", token); var (plainText, html) = BuildTemplate( - "Reset your PlotWeaver Studio password", + "Reset your PlotDirector password", displayName, - "Use the link below to choose a new password for your PlotWeaver Studio account.", + "Use the link below to choose a new password for your PlotDirector account.", "Reset password", link, "This link expires in 24 hours. If you did not request a reset, you can ignore this email."); - return QueueAsync(email, displayName, "Reset your PlotWeaver Studio password", plainText, html); + return QueueAsync(email, displayName, "Reset your PlotDirector password", plainText, html); } private async Task QueueAsync(string toEmail, string displayName, string subject, string plainText, string html) @@ -140,7 +140,7 @@ public sealed class EmailService(
PlotWeaver Studio
+PlotDirector
Hello {safeName},
{safeIntro}
@@ -160,13 +160,13 @@ public sealed class EmailService( private static string CleanDisplayName(string value) { - return string.IsNullOrWhiteSpace(value) ? "PlotWeaver Studio" : value.Trim(); + return string.IsNullOrWhiteSpace(value) ? "PlotDirector" : value.Trim(); } private string GetFromAddress() { return string.IsNullOrWhiteSpace(_settings.FromAddress) - ? "hello@plotweaver.studio" + ? "hello@plotdirector.com" : _settings.FromAddress.Trim(); } } @@ -220,7 +220,7 @@ public sealed class QueuedEmailSender( private static string CleanDisplayName(string? value) { - return string.IsNullOrWhiteSpace(value) ? "PlotWeaver Studio" : value.Trim(); + return string.IsNullOrWhiteSpace(value) ? "PlotDirector" : value.Trim(); } } diff --git a/PlotLine/Services/CoreServices.cs b/PlotLine/Services/CoreServices.cs index 6d6f583..d4f5f74 100644 --- a/PlotLine/Services/CoreServices.cs +++ b/PlotLine/Services/CoreServices.cs @@ -546,24 +546,24 @@ public sealed class ProjectCollaborationService( var project = currentUser.UserId.HasValue ? await projects.GetForUserAsync(projectId, currentUser.UserId.Value) : null; var projectName = project?.ProjectName ?? "a project"; var inviterName = CleanDisplayName(currentUser.DisplayName); - var subject = $"You have been added to {projectName} in PlotWeaver Studio"; + var subject = $"You have been added to {projectName} in PlotDirector"; var plainText = $""" You have been added as a collaborator. Hello {CleanDisplayName(user.DisplayName)}, - {inviterName} added you as a collaborator on "{projectName}" in PlotWeaver Studio. Sign in to PlotWeaver Studio to open the shared project. + {inviterName} added you as a collaborator on "{projectName}" in PlotDirector. Sign in to PlotDirector to open the shared project. """; var html = $"""PlotWeaver Studio
+PlotDirector
Hello {WebUtility.HtmlEncode(CleanDisplayName(user.DisplayName))},
{WebUtility.HtmlEncode(inviterName)} added you as a collaborator on {WebUtility.HtmlEncode(projectName)}.
-Sign in to PlotWeaver Studio to open the shared project.
+Sign in to PlotDirector to open the shared project.
Account
Sign in to PlotWeaver Studio.
+Sign in to PlotDirector.
Account
Create a PlotWeaver Studio account so your workspace can use the new authentication foundation.
+Create a PlotDirector account so your workspace can use the new authentication foundation.
Account
Choose a new password for your PlotWeaver Studio account.
+Choose a new password for your PlotDirector account.
Guidance
Find practical guidance for planning, tracking, and shaping your story in PlotWeaver Studio.
+Find practical guidance for planning, tracking, and shaping your story in PlotDirector.
PlotWeaver Studio for novelists
+PlotDirector for novelists
- Forgotten clues. Contradictory timelines. Notes scattered across half a dozen documents. PlotWeaver Studio helps you bring every part of your story together so you can write with confidence. + Forgotten clues. Contradictory timelines. Notes scattered across half a dozen documents. PlotDirector helps you bring every part of your story together so you can write with confidence.
-Managing complex plots
When plots, subplots, mysteries, romances, and character arcs start pulling in different directions, it's easy to lose sight of the bigger picture. PlotWeaver helps you see how everything fits together.
+When plots, subplots, mysteries, romances, and character arcs start pulling in different directions, it's easy to lose sight of the bigger picture. PlotDirector helps you see how everything fits together.
Continuity mistakes
Readers notice when characters know things they shouldn't, important objects disappear, or timelines stop making sense. PlotWeaver helps you spot those problems before publication.
+Readers notice when characters know things they shouldn't, important objects disappear, or timelines stop making sense. PlotDirector helps you spot those problems before publication.
Knowing what to work on next
Many novels stall because writers simply don't know what to tackle next. PlotWeaver helps you identify the scenes, revisions, and unresolved issues that deserve your attention today.
+Many novels stall because writers simply don't know what to tackle next. PlotDirector helps you identify the scenes, revisions, and unresolved issues that deserve your attention today.
Drowning in notes and documents
If your story lives across Word documents, notebooks, spreadsheets, and scraps of paper, you're not alone. PlotWeaver brings everything together in one organised place.
+If your story lives across Word documents, notebooks, spreadsheets, and scraps of paper, you're not alone. PlotDirector brings everything together in one organised place.
Tracking character relationships
Friendships evolve. Rivalries deepen. Secrets change everything. PlotWeaver helps you track how your characters connect and how those relationships change over time.
+Friendships evolve. Rivalries deepen. Secrets change everything. PlotDirector helps you track how your characters connect and how those relationships change over time.
Managing series and multiple books
Long-running mysteries, character journeys, and future revelations become difficult to manage across multiple books. PlotWeaver helps you keep the bigger picture in view.
+Long-running mysteries, character journeys, and future revelations become difficult to manage across multiple books. PlotDirector helps you keep the bigger picture in view.
Understanding pacing and emotional flow
Action without breathing room can exhaust readers. Quiet moments without momentum can slow the story. PlotWeaver helps you visualise pacing and emotional balance across your manuscript.
+Action without breathing room can exhaust readers. Quiet moments without momentum can slow the story. PlotDirector helps you visualise pacing and emotional balance across your manuscript.
Loved by story-obsessed writers
-"PlotWeaver turned my revision from panic into decisions. I knew what to fix next."+
"PlotDirector turned my revision from panic into decisions. I knew what to fix next."
Built by an author
- PlotWeaver Studio was created by a novelist who was tired of juggling Word documents, spreadsheets, notebooks, and sticky notes while writing complex stories. + PlotDirector was created by a novelist who was tired of juggling Word documents, spreadsheets, notebooks, and sticky notes while writing complex stories.
The goal was simple: make a beautiful, dependable place where story structure, emotional logic, continuity, and the next writing step can live together. @@ -307,7 +307,7 @@
Start with the story you already have
Whether you're writing your first novel or untangling an epic series, PlotWeaver Studio helps you stay organised, maintain confidence, and finally finish your story.
+Whether you're writing your first novel or untangling an epic series, PlotDirector helps you stay organised, maintain confidence, and finally finish your story.
Start Your Free TrialTools
Paste or upload a legacy JSON package or a PlotWeaver backup file, preview it, dry-run if needed, then import a new project.
+Paste or upload a legacy JSON package or a PlotDirector backup file, preview it, dry-run if needed, then import a new project.