Clearer onboarding, project menus, and Continuity articles

This update focuses on making Scriptri easier to understand when you first open a project. The core workflow is the same — tag what matters, add what changed, check At This Point — but several parts of the app should now do a better job explaining that workflow without getting in your way.

Clearer empty states

Empty projects, blank scenes, notes, entities, timeline events, and continuity flags now use shorter, more direct guidance.

For example, an empty project now points you toward either starting from scratch or importing a manuscript. Empty note and context panels now focus on the next useful action instead of long explanations.

---

In-app help

Scriptri now includes small help hints for a few concepts that can be confusing at first, including:

• At This Point
• state notes
• Update
• Resolve
• continuity concerns

There is also a new Help dialog inside the project editor, so you can read a quick overview of how Scriptri works without leaving your project.

---

Cleaner project menus

The project header has been reorganized so related actions are grouped together.

The Editor menu now holds project workspaces like Entities, Flags, and Timeline.

The Data menu now holds manuscript import, Scrivener import, and project backups.

The Help menu now holds help, Continuity articles, updates, roadmap, feedback, and email.

This should make the app feel less like a row of unrelated buttons and more like a project workspace that can grow over time.

---

Guides are now Continuity articles

The old Guides section has been renamed to Continuity articles.

These articles are still about writing, revision, and story continuity, but the new name better reflects what Scriptri is focused on: helping writers track what is true, known, changed, unresolved, or contradicted at specific points in a story.

Old /guides links now redirect to /continuity.

---

New article: two kinds of continuity work

There is also a new article:

Two Kinds of Continuity Work: Tracking as You Go vs. Investigating Later

The article explains an important design direction for Scriptri: continuity work is not only something writers do while drafting. Sometimes a detail becomes important later, and the writer needs to investigate backward through the manuscript to recover what has already been established.

That distinction matters for where Scriptri is headed.

---

Small privacy-conscious analytics update

I also made a small analytics change so Scriptri can better understand whether people return to the app over time.

This uses a random local identifier stored in the browser. It is not based on personal information, accounts, device fingerprinting, or manuscript content. Clearing site data resets it.

Scriptri still does not send manuscript text, scene titles, note content, entity names, search text, or imported file names to analytics.