Skip to main content
Version: 1.0.0

Saving and Publishing

This document explains how to save and publish project data.

Save​

  1. on Menu > Save, or press Ctrl or ⌘+S.
  2. The project is saved.
  3. A toast message with save completion and save information appears in the top right.

Publish​

  1. on Menu > Publish.
  2. The project is published.
  3. A toast message with publish completion and publish information appears in the top right.

Difference Between Save and Publish​

Save​

  • Saves project data to the browser's local storage.
  • The project version remains the same.
  • Other users cannot access the data.
  • Saved data is automatically loaded on refresh.

Publish​

  • Uploads project data to the remote server.
  • The project version increments.
  • Other users can access the data.
  • Published stages can be imported from a parent integrated project.
  • Published data is automatically loaded on refresh.

If both are automatically loaded, which one loads first?​

  • If the saved data and published data have the same version, the saved data takes priority.
  • If the saved data and published data have different versions, the published data takes priority.

Concurrent Editing Precautions​

When multiple users work on the same project simultaneously, data consistency issues may arise. Please exercise caution.

Sequential Collaboration (No Conflicts)
  1. User 1: Loads v0.0.0 → Works and publishes → v1.0.0 created
  2. User 2: Loads v1.0.0 → Works and publishes → v2.0.0 created
  3. User 3: Loads v2.0.0 → Works and publishes → v3.0.0 created
Uncoordinated Concurrent Editing (Conflict and Data Loss)
  1. User 1 and User 2 both load v1.0.0 at the same time.
  2. User 1 finishes and publishes to the server. The remote version becomes v2.0.0.
  3. User 2 also finishes and saves locally. (Still v1.0.0)
  4. When User 2 reloads or re-accesses the project, the system detects remote v2.0.0 > local v1.0.0 and automatically loads the remote v2.0.0.
  5. User 2's locally saved data is completely overwritten and lost.
Preventing Data Loss

When multiple people work on the same project, always publish sequentially. One user should complete their publish before the next user loads the latest version to begin their work.