Published versions

Scripvio does not ask you to manage « file v1, v2, v3 ». Behind each note or journal entry, the app links a document (life thread) and versions: a draft to work in, a published one visible in the Library. This guide explains that model and how to update published content without losing track.

→ Drafts and published · Library overview

Three ideas to remember

Concept	What it means for you	Visible where
Document	Stable « card » (same sermon, same journal thread)	Internal id — you mostly see title
Draft	Work-in-progress version	Create → Notes or Journal segment
Published version	Frozen catalog snapshot	Library → read mode

stateDiagram-v2
  [*] --> Draft: Create
  Draft --> Published: Publish
  Published --> Library: Published list
  Library --> Draft2: New version
  Draft2 --> Published: Publish again
  Published --> Library: Replaces display

First publish: creating the published version

Step	Result
Create (+ or Create list)	Draft (document + work version)
Writing, autosave	Draft grows
Publish (title required)	Draft closed → published in Library

Messages: Note published. / Entry published. — or Publish queued (offline).

The active draft leaves Create; you do not « duplicate » the note — you turn that work into the Library reference.

→ Notes — draft and publish · Journal — draft and publish

Fix after publish: New version…

You do not edit published body text in place in the Library. Official flow:

1. From read mode (Library)

Library → open note (Read) or entry (Journal).
⋮ menu → New version…
(not on View read-only preview from Create — for published Library read only.)

2. Confirmation dialog

Create a new version?

Creating a new version generates a draft from the published note / entry.

The Library will stay unchanged.
The draft will appear under Create.
You can publish later to replace the published version.

Button	Effect
Cancel	No change
Create new version	Copies published → new work draft
Open draft (if exists)	A draft already exists for this note / entry. — no second parallel draft

3. Work and republish

Edit the draft (Edit entry / Note editor).
⋮ → Publish.
Library then shows the new published content.

During steps 1–2:

Area	Content
Library	Previous published version (unchanged for readers)
Create	New version draft

Notes and journal: same engine, adapted labels

	Note	Journal
Menu	New version…	New version…
Dialog	…from the published note	…from the published entry
Existing draft hint	…for this note	…for this entry
After publish	Library Read	Library Journal
PDF export	Export as PDF… on current published	No journal PDF

Detailed guides:

→ Edit a note · Journal overview

One version draft at a time

For the same already-published document:

Scripvio allows one active « new version » draft;
running New version… again offers Open draft instead of creating another;
avoids two parallel conflicting edits.

If you abandoned a version draft without publishing, reopen it under Create (right segment) or Open draft from Library read.

What you see (and do not)

Visible	Not in the mobile app
Current published in Library	Full history of past publishes
Published chip in read	Permanent version number in UI
Active draft in Create	One-click « restore yesterday’s publish »
Updated date on list cards	Side-by-side diff of two publishes

The server keeps history on your account; the mobile UI stays simple: one published reference, one work draft when needed.

Versions and other features

Feature	Which version counts
Library (list, search, favorites)	Current published
PDF export (notes)	Current published at export time
Favorite	Tied to document / version — editable in read
Tracking links (journal)	Fixed on published; change links via new version draft
Bible references (add in draft)	Published on next Publish
Multi-device sync	Draft and published per usual rules

Common scenarios

Small fix after a service

New version… from the Library note.
Fix a section or summary in the draft.
Publish → Library updated; PDF exported before the fix stays the old file (re-export if needed).

Long journal rewrite

New version… on published entry.
Work several days in draft (Create → Journal).
Library still shows the old entry until republish — expected.

Published too early by mistake

New version… (or complete existing draft).
Enrich content.
Publish to replace the too-short version.

There is no « undo publish » action — correction goes through new version + publish.

Symptom	Explanation	Action
Library shows old text	Draft not republished	Publish draft in Create
No New version…	Not Library published read	Open from Library, not Create preview
Two drafts for same item	Only one allowed	Open draft
PDF feels « old »	Export snapshot at moment T	Re-export after republish
Publish queued	Offline	Sync then Publish

FAQ

Can I roll back to the publish before my last one?
Not via a button in the mobile app. A new Publish replaces the visible version; history is not listed.

Does publishing delete the old work draft?
Yes — that draft is closed and becomes published in the Library. To edit again, use New version….

Several notes from one service = several documents?
Yes. Each + → Note starts a new document (except untitled-draft reuse limits).

Does journal follow the same rules?
Yes: journal document, draft, publish, New version…, one version draft at a time.

Library section — recap

Guide	Topic
Overview	Tab role
Search and filter	List tools
Drafts and published	Statuses
Find your content	Practical paths
This guide	Versions and republish

Next documentation areas: Tracking, Bible search, Account, Offline, FAQ, etc.

Topic	Link
Notes — versions	Draft and publish
Edit a note	Edit a note
Journal — versions	Draft and publish
PDF (published note)	Export PDF
Sync	Sync