diff --git a/content/documentation-assets/docs/zoo-design-studio/features/data-management/cloud-sync/cloud-sync-conflict-dialog.webp b/content/documentation-assets/docs/zoo-design-studio/features/data-management/cloud-sync/cloud-sync-conflict-dialog.webp new file mode 100644 index 00000000..61b03626 Binary files /dev/null and b/content/documentation-assets/docs/zoo-design-studio/features/data-management/cloud-sync/cloud-sync-conflict-dialog.webp differ diff --git a/content/documentation-assets/docs/zoo-design-studio/features/data-management/cloud-sync/cloud-sync-conflict-home.webp b/content/documentation-assets/docs/zoo-design-studio/features/data-management/cloud-sync/cloud-sync-conflict-home.webp new file mode 100644 index 00000000..5dd16e56 Binary files /dev/null and b/content/documentation-assets/docs/zoo-design-studio/features/data-management/cloud-sync/cloud-sync-conflict-home.webp differ diff --git a/content/documentation-assets/docs/zoo-design-studio/features/data-management/cloud-sync/cloud-sync-duplicate-copies-menu.webp b/content/documentation-assets/docs/zoo-design-studio/features/data-management/cloud-sync/cloud-sync-duplicate-copies-menu.webp new file mode 100644 index 00000000..5dcb7de6 Binary files /dev/null and b/content/documentation-assets/docs/zoo-design-studio/features/data-management/cloud-sync/cloud-sync-duplicate-copies-menu.webp differ diff --git a/content/documentation-assets/docs/zoo-design-studio/features/data-management/cloud-sync/cloud-sync-status.webp b/content/documentation-assets/docs/zoo-design-studio/features/data-management/cloud-sync/cloud-sync-status.webp new file mode 100644 index 00000000..f141853b Binary files /dev/null and b/content/documentation-assets/docs/zoo-design-studio/features/data-management/cloud-sync/cloud-sync-status.webp differ diff --git a/content/documentation-assets/docs/zoo-design-studio/features/data-management/project-libraries/create-project-library-chooser.webp b/content/documentation-assets/docs/zoo-design-studio/features/data-management/project-libraries/create-project-library-chooser.webp new file mode 100644 index 00000000..f5c2231f Binary files /dev/null and b/content/documentation-assets/docs/zoo-design-studio/features/data-management/project-libraries/create-project-library-chooser.webp differ diff --git a/content/documentation-assets/docs/zoo-design-studio/features/data-management/project-libraries/move-directory-to-personal-cloud.webp b/content/documentation-assets/docs/zoo-design-studio/features/data-management/project-libraries/move-directory-to-personal-cloud.webp new file mode 100644 index 00000000..30011afd Binary files /dev/null and b/content/documentation-assets/docs/zoo-design-studio/features/data-management/project-libraries/move-directory-to-personal-cloud.webp differ diff --git a/content/documentation-assets/docs/zoo-design-studio/features/data-management/project-libraries/move-personal-cloud-to-directory.webp b/content/documentation-assets/docs/zoo-design-studio/features/data-management/project-libraries/move-personal-cloud-to-directory.webp new file mode 100644 index 00000000..1fbcc081 Binary files /dev/null and b/content/documentation-assets/docs/zoo-design-studio/features/data-management/project-libraries/move-personal-cloud-to-directory.webp differ diff --git a/content/documentation-assets/docs/zoo-design-studio/features/data-management/project-libraries/project-libraries-home.webp b/content/documentation-assets/docs/zoo-design-studio/features/data-management/project-libraries/project-libraries-home.webp new file mode 100644 index 00000000..efa77b5b Binary files /dev/null and b/content/documentation-assets/docs/zoo-design-studio/features/data-management/project-libraries/project-libraries-home.webp differ diff --git a/content/documentation-assets/docs/zoo-design-studio/features/data-management/project-libraries/project-libraries-settings.webp b/content/documentation-assets/docs/zoo-design-studio/features/data-management/project-libraries/project-libraries-settings.webp new file mode 100644 index 00000000..8956336c Binary files /dev/null and b/content/documentation-assets/docs/zoo-design-studio/features/data-management/project-libraries/project-libraries-settings.webp differ diff --git a/content/pages/docs/zoo-design-studio/features/data-management/aquarium.mdx b/content/pages/docs/zoo-design-studio/features/data-management/aquarium.mdx index 9ef36263..3018454f 100644 --- a/content/pages/docs/zoo-design-studio/features/data-management/aquarium.mdx +++ b/content/pages/docs/zoo-design-studio/features/data-management/aquarium.mdx @@ -1,7 +1,7 @@ --- title: Aquarium excerpt: Share and discover public Zoo models through the Aquarium CAD Gallery. -sidebarPosition: 4 +sidebarPosition: 6 --- Aquarium is Zoo's public CAD gallery for discovering, viewing, and sharing models. Use it when you diff --git a/content/pages/docs/zoo-design-studio/features/data-management/cloud-sync.mdx b/content/pages/docs/zoo-design-studio/features/data-management/cloud-sync.mdx new file mode 100644 index 00000000..75aed86f --- /dev/null +++ b/content/pages/docs/zoo-design-studio/features/data-management/cloud-sync.mdx @@ -0,0 +1,276 @@ +--- +title: Cloud Sync +excerpt: Keep Zoo Design Studio projects available across devices while preserving local files. +sidebarPosition: 4 +--- + +Cloud sync keeps Zoo Design Studio projects available through your Zoo account while preserving the +project files you work with locally. + +It is built around the same file-based project model as +[Project Libraries](/docs/zoo-design-studio/features/data-management/project-libraries): + +- A project is still a directory with `project.toml` and at least one `.kcl` file. +- KCL and project metadata are still readable outside Zoo Design Studio. +- Local file changes happen first. +- Cloud sync runs in the background and uploads or downloads project snapshots. + +Cloud sync is not version control. It keeps project copies available across Zoo surfaces, while Git +or another version-control tool records intentional history and code review. + + + +## How Cloud Sync Works + +When cloud sync is enabled, Zoo Design Studio watches project file changes and queues sync work in +the background. Creating, editing, renaming, and deleting project files still happens locally first. +Zoo Design Studio then reconciles those local files with the matching project in Zoo cloud. + +On desktop, synced projects live in a managed Personal Cloud folder on your computer. You can see +that path in User Settings under `App` > `Libraries`, then reveal it in your file explorer. + +Cloud projects can appear in several states: + +| State | Meaning | +| --- | --- | +| Cloud-only | The project exists in Zoo cloud and has not been downloaded on this device yet. Opening it creates a local working copy. | +| Cloud synced | Local files and the cloud project are up to date. | +| Cloud sync pending | Local changes are queued for upload. | +| Cloud syncing | Zoo Design Studio is uploading or downloading project data. | +| Cloud sync failed | Sync could not complete and will be retried. Your local files remain available. | +| Cloud sync blocked | Zoo Design Studio can read the cloud project but cannot upload local changes, usually because the current account does not have write access. | +| Cloud conflict | Local and cloud data both changed since the last synced version and need manual resolution. | + +Failed work stays queued and is retried automatically. A downloaded project remains locally +available after a network request fails, but a cloud-only project needs a connection before it can +be opened. + +Browser working copies live in site storage. Clearing the browser's site data can remove those local +copies and any work that has not reached `Cloud synced`. + +Before changing the same project on another device or browser, wait for the first device to show +`Cloud synced`. Cloud sync is not a real-time collaboration session; if both copies change, Zoo +Design Studio may merge independent file changes or ask you to resolve a conflict. + +## What Is Included in Cloud Sync + +Cloud sync uploads KCL, project metadata, and other project files that are not excluded. + +Cloud sync does not upload: + +- Files and folders matched by the project's `.gitignore` rules. The `.gitignore` files themselves + are uploaded. +- Version-control metadata directories named `.git`, `.hg`, `.svn`, or `.jj`. +- Zoo's internal `._meta` data or the generated project thumbnail. + +Binary files are included unless `.gitignore` excludes them. Cloud sync does not infer which files +contain secrets, so exclude sensitive paths before syncing. + +**Important:** Excluded files are not part of the cloud project. Current versions can replace or +remove the entire managed project folder during a remote update, automatic merge, remote deletion, +automatic duplicate cleanup, or `Use cloud data`. This can remove local Git history, ignored files, +and other excluded content. + +## Duplicate Local Copies + +A cloud project can have more than one local copy. This can happen if you copy a synced project +folder in Finder or File Explorer, restore one from a backup, or keep overlapping project library +folders that both include the same project. + +Zoo Design Studio tracks this as one cloud project with one or more local copies. Home picks one +canonical copy to open and sync from, then marks extra copies with a `Duplicate copies` badge. + +Duplicate copies are handled conservatively: + +- The canonical copy is kept. +- Extra local copies are not hidden just because they share the same cloud project ID. +- Directory library copies are not silently deleted. +- Zoo Design Studio may clean up an exact duplicate in the cloud library only when it can prove that + copy matches the clean synced version. +- Pending, conflicted, unreadable, tombstoned, sync-excluded, or changed copies stay available for + review. + +Ignored files and version-control metadata do not make an otherwise exact extra copy divergent, so +automatic cleanup can remove that excluded content with the duplicate folder. + +Use `Review duplicate copies` from the project card context menu to inspect duplicate local folders. +You can select duplicate folders to permanently delete, and Zoo Design Studio will still keep the +canonical folder. This review action removes selected local folders; it does not delete the cloud +project. + + + +## Automatic Merging + +Cloud sync can automatically merge simple project changes when local files and cloud files changed +in different places after the last synced version. + +For example, if you edit `main.kcl` locally while another Zoo surface adds `mount.kcl` in the cloud, +Zoo Design Studio can keep your local `main.kcl`, download the cloud-only `mount.kcl`, upload the +combined project snapshot, and continue syncing without asking you to resolve a conflict. + +Automatic merging is intentionally conservative: + +- If only the local copy changed a file, Zoo Design Studio keeps the local file. +- If only the cloud copy changed a file, Zoo Design Studio uses the cloud file. +- If both copies changed the same file to the same contents, Zoo Design Studio accepts that file. +- If both copies changed the same file differently, Zoo Design Studio shows a cloud sync conflict. + +Cloud sync does not perform line-by-line or semantic code merges inside a `.kcl` file. Use Git or +another version-control tool when you need intentional history, branches, code review, or manual +same-file merging. + +## Start Syncing + +To start syncing a local Directory project, move it to `Personal Cloud`: + +1. Select `Move to library` from the Command Bar, the project menu in the top bar, or the project + card context menu on Home. +2. Choose the local project. +3. Choose `Personal Cloud` as the destination library. +4. Confirm the move. + +Zoo Design Studio moves the project into the cloud library and keeps a local working copy for normal +editing. If cloud sync is enabled, it uploads the project to your Zoo account; if cloud sync is paused +on desktop, the project remains local in that folder until you enable it again. + +Creating a project directly in `Personal Cloud` also starts it as a synced project. In the browser, +Personal Cloud is the only project library, so projects are cloud-backed by default. + +{/* VIDEO PLACEHOLDER: Moving a Directory project to Personal Cloud and watching the sync status reach Cloud synced. */} + + + +## Stop Syncing + +To make a synced project local-only, move it from `Personal Cloud` to a Directory library: + +1. Select `Move to library` from the Command Bar, the project menu in the top bar, or the project + card context menu on Home. +2. Choose the synced project. +3. Choose a Directory library as the destination. +4. Confirm the move. + +Zoo Design Studio disconnects the project from cloud sync and moves the files into the selected +local library. The moved local copy is the project that remains, and future edits happen only in +that Directory library unless you move the project back to `Personal Cloud`. + +**Important:** Moving a project from Personal Cloud to a Directory library deletes the remote cloud +project before moving the remaining local folder. The cloud project is no longer available in the +browser or on other devices. If remote deletion fails, Zoo Design Studio restores the cloud link and +the move fails. + +Remote deletion happens before the filesystem move. If that later move fails, the remote project is +not restored automatically. Back up important work before moving it out of Personal Cloud. + +Turning the cloud sync plugin off only pauses synchronization; it does not make a project local-only. +A cloud-only project must first be opened and downloaded before it can be moved. + +{/* VIDEO PLACEHOLDER: Moving a Personal Cloud project into a Directory library to make it local-only. */} + + + +## Delete Synced Projects + +Deleting a cloud-backed project follows the library that owns the project card. + +If you delete a project from `Personal Cloud`, Zoo Design Studio deletes the cloud project. If the +project has a local working copy on that device, the local working copy is removed too. + +If you delete a cloud-backed project from a Directory library, Zoo Design Studio deletes only that +local folder. The cloud project remains in your Zoo account, and the delete dialog says that the +cloud version will not be deleted. + +Keep cloud sync enabled and make sure Zoo Design Studio can reach the cloud before deleting a +cloud-linked project. Deleting a downloaded Personal Cloud project removes its local folder before +the remote request finishes. If that request fails, Zoo Design Studio reports the failure, but the +local folder may already be gone and the remote project can reappear on Home. + +Deletion from Personal Cloud propagates to other devices. Copies with unsynced changes, or copies Zoo +Design Studio cannot verify, are preserved and disconnected instead. Excluded files do not count as +changes, so keep the separate backup described above. + +This is different from `Move to library`. Use `Move to library` when you want to change where a +project belongs. Use delete when you want to remove the project card from its current library. +Moving from Personal Cloud to a Directory library also deletes the remote project, but preserves and +relocates the selected local folder. + +## Resolve Conflicts + +A cloud sync conflict happens when the local project and the cloud project both changed after the +last synced version, and Zoo Design Studio cannot safely combine the changes automatically. + +When a conflict is detected: + +- The project card on Home shows a `Cloud conflict` badge. +- The project breadcrumb can show a `Cloud conflict` badge while the project is open. +- The Home status bar (bottom-left corner) shows `Cloud conflict`; select it to list conflicted projects. +- The open project's menu (top-left corner) shows `Cloud conflict`; select it to open the dialog. + +Zoo Design Studio keeps your current local project as the primary project while you review the +conflict. + + + +Open the conflict dialog from the project menu or from the cloud sync status UI. The dialog compares +the local version and the cloud version file by file. + +Files are labeled as: + +- `Changed`, when local and cloud both have the file but with different contents. +- `Only local`, when the file exists only in the local project. +- `Only cloud`, when the file exists only in the cloud project. + +Text files, including `.kcl` and Markdown files, show a side-by-side diff when possible. Large, +binary, or non-UTF-8 files may show file metadata without an inline diff. + +The resolution applies to the whole project, not individual files. Choose one resolution: + +- `Use local data` uploads the current local project to the cloud, clears the conflict, and resumes + sync from the local version. +- `Use cloud data` replaces the entire local project with the cloud version shown in the dialog, + clears the conflict, and resumes sync from the cloud version. + +If you need to combine both versions, manually copy or edit the files you want into the local +project first, then choose `Use local data`. + +You may want to back up the local folder before choosing `Use cloud data`, especially if it contains ignored or +version-control files. + + + +## Related + +- [Project Libraries](/docs/zoo-design-studio/features/data-management/project-libraries) +- [Project Browser](/docs/zoo-design-studio/features/workspace/project-browser) +- [File Explorer](/docs/zoo-design-studio/features/workspace/file-explorer) diff --git a/content/pages/docs/zoo-design-studio/features/data-management/default-project-folder.mdx b/content/pages/docs/zoo-design-studio/features/data-management/default-project-folder.mdx index 4fe8f2df..d4228536 100644 --- a/content/pages/docs/zoo-design-studio/features/data-management/default-project-folder.mdx +++ b/content/pages/docs/zoo-design-studio/features/data-management/default-project-folder.mdx @@ -1,20 +1,12 @@ --- title: Default Project Folder -excerpt: Configure the default project root in Zoo Design Studio. -sidebarPosition: 3 +excerpt: Understand how the legacy default project folder maps to Project Libraries. +sidebarPosition: 5 --- -The Default Project Folder sets the default location for Zoo Design Studio projects. +Project Libraries replaced the single Default Project Folder control in current Zoo Design Studio +releases. The legacy `Project Directory` setting is no longer shown in Settings. -When a folder is assigned as the `Loaded From` location, new projects are created in that directory -by default. This helps keep ZDS projects organized in one place while still allowing you to open -existing projects from other locations when needed. - -You can reassign the default folder at any time. - -## Behavior - -- Choose a default project folder. -- New projects are created in that folder automatically. -- The assigned folder can be changed at any time. -- Existing projects can still be opened from other locations. +Manage project locations under `Settings` > `User` > `App` > `Libraries`. See +[Project Libraries](/docs/zoo-design-studio/features/data-management/project-libraries) for the current +workflow. diff --git a/content/pages/docs/zoo-design-studio/features/data-management/index.mdx b/content/pages/docs/zoo-design-studio/features/data-management/index.mdx index 87c09ed0..65977f19 100644 --- a/content/pages/docs/zoo-design-studio/features/data-management/index.mdx +++ b/content/pages/docs/zoo-design-studio/features/data-management/index.mdx @@ -7,9 +7,23 @@ sidebarPosition: 7 Data Management covers how geometry and project files are imported, exported, versioned, and stored in Zoo Design Studio. -This section includes -[Import](/docs/zoo-design-studio/features/data-management/import), -[Export](/docs/zoo-design-studio/features/data-management/export), -[Version Control](/docs/zoo-design-studio/features/data-management/version-control), -[Default Project Folder](/docs/zoo-design-studio/features/data-management/default-project-folder), and -[Aquarium](/docs/zoo-design-studio/features/data-management/aquarium). +Zoo Design Studio projects are folders of files. The main project source is human-readable text: +KCL files for model logic and, when present, `project.toml` for project metadata. That makes projects +portable, inspectable, syncable, and practical to version with normal developer tools. + +## Topics + +- [Import](/docs/zoo-design-studio/features/data-management/import) covers bringing CAD files, + models, and KCL into a project. +- [Export](/docs/zoo-design-studio/features/data-management/export) covers writing geometry and + project output to other formats. +- [Version Control](/docs/zoo-design-studio/features/data-management/version-control) covers using + Git and other text-based revision workflows with Zoo Design Studio projects. +- [Aquarium](/docs/zoo-design-studio/features/data-management/aquarium) covers browser-based project + and data-management workflows. +- [Project Libraries](/docs/zoo-design-studio/features/data-management/project-libraries) covers + organizing projects across local folders and cloud-backed libraries. +- [Cloud Sync](/docs/zoo-design-studio/features/data-management/cloud-sync) covers syncing projects + through your Zoo account and resolving sync conflicts. +- [Default Project Folder](/docs/zoo-design-studio/features/data-management/default-project-folder) + explains how the legacy single-folder setting maps to Project Libraries. diff --git a/content/pages/docs/zoo-design-studio/features/data-management/project-libraries.mdx b/content/pages/docs/zoo-design-studio/features/data-management/project-libraries.mdx new file mode 100644 index 00000000..3d4c3903 --- /dev/null +++ b/content/pages/docs/zoo-design-studio/features/data-management/project-libraries.mdx @@ -0,0 +1,169 @@ +--- +title: Project Libraries +excerpt: Organize Zoo Design Studio projects across local folders and cloud-backed libraries. +sidebarPosition: 3 +--- + +Project libraries are the groups of projects you see on Home. Use them to organize work around a +theme, client, product line, experiment, local Git folder, or anything else that makes your project +list easier to scan. + +Zoo Design Studio keeps this model intentionally file based. A project is a directory with at least +one `.kcl` file somewhere inside the project folder. Projects created by Zoo Design Studio normally +also include `project.toml`, which stores project metadata, but an existing KCL project does not need +that file before it can be discovered. + +That means your work is not locked inside Zoo Design Studio. You can open a project folder in a text +editor, search it, copy it, diff it, version it with Git, or ask an AI agent to read the source. +KCL files and `project.toml` are designed to be readable outside the app. + + + +## Library Types + +Zoo Design Studio currently supports two library types. + +| Type | Where it stores projects | Best for | +| --- | --- | --- | +| Directory | A folder on your computer, with projects as immediate subfolders. | Local-only work, client folders, Git worktrees, shared drives, and explicit filesystem organization. | +| Cloud | Your Zoo Personal Cloud, with a local working copy on your device. | Projects you want available through your Zoo account, across devices, or in the browser. | + +### Directory Libraries + +A Directory library points to a normal folder on your computer. Each project appears as an immediate +subfolder inside that library folder. + +Directory libraries are available in the desktop app. Under `Settings` > `User` > `App` > +`Libraries`, you can add more than one, rename them, choose different folders, reorder them, or remove +them from Home. Changing a library path changes which folder Home scans; it does not move projects. +Removing a Directory library does not delete its folder or projects on disk. + +Use Directory libraries when you want full control over where projects live, how they are backed up, +or how they fit into other tools. + +A Directory library can also show a project folder that is linked to a Zoo cloud project. In that +case, the folder is still owned by the Directory library for local actions such as delete. Deleting +that Directory library copy removes the local folder, not the cloud project. + +### Cloud Libraries + +A Cloud library points to projects served from Zoo's API. The cloud library you see today is +`Personal Cloud`. + +Cloud projects still have source files on your device. When you create or open a cloud project, Zoo +Design Studio places a local working copy in its managed cloud sync folder and syncs changes in the +background. On desktop, the Personal Cloud settings row shows that local path and can reveal it in +your file explorer. + +Some Personal Cloud projects may appear before they have been opened on the current device. These are +cloud-only entries. Opening one downloads the project first, then opens the local working copy. + + + +## Desktop and Browser Behavior + +On desktop, Zoo Design Studio can show Directory and Cloud libraries side by side. This lets you keep +local-only work, Git-based work, and cloud-backed work in one Home view. + +In the browser, Zoo Design Studio uses `Personal Cloud`. Browser storage. Browser storage +is not a normal folder that you manage in Finder, File Explorer, or a terminal, so browser projects +are treated as cloud-backed projects instead of local-only Directory projects. In the browser, you +can edit a library's display title, but you cannot add or reorder libraries or change their type or +storage location. + +## Browse Libraries on Home + +With multiple libraries, Home shows a `Project Libraries` overview in configured order. Select a +library to see all of its projects, then use `All libraries` to return to the overview. With only one +configured library, Home goes directly to that library's projects. + +## Create a Project in a Library + +From Home, choose `Create project`. If more than one writable library is available, the Create +project command includes a `Library` field. + +Creating a project in a Directory library creates a new folder inside that Directory library's path. +Creating a project in Personal Cloud creates a local cloud working copy and starts cloud sync when +sync is enabled. + +{/* VIDEO PLACEHOLDER: Short walkthrough creating one project in a Directory library and one in Personal Cloud. */} + + + +## Move Projects Between Libraries + +Use `Move to library` to change where a project lives. You can start this from the Command Bar, the +project menu in the top bar, or a project card's context menu on Home. + +1. Select `Move to library`. +2. Choose the project. +3. Choose the destination library. +4. Confirm the move. + +The result depends on the source and destination: + +- Directory to Directory moves the project folder between local library paths. +- Directory to Personal Cloud moves it into managed cloud storage and enrolls it for cloud sync +- Personal Cloud to Directory deletes the remote cloud project, disconnects the local copy, and + moves that remaining folder to the Directory library. + +A cloud-only project must be opened before it can be moved. Moving out of Personal Cloud also +requires Cloud Sync to be enabled. + +**Important:** Moving out of Personal Cloud is a permanent remote deletion, not a way to retain both +copies. If Zoo Design Studio cannot delete the remote project, the move fails and restores the cloud +link. + +This is the preferred way to move projects between libraries. It lets Zoo Design Studio update the +project files, library membership, and cloud sync metadata together. + +{/* VIDEO PLACEHOLDER: Moving a local project into Personal Cloud, then moving it back to a Directory library. */} + + +
+ + +## Delete Projects from Libraries + +Deleting a project follows the library it belongs to: + +- Deleting from a Directory library removes the local project folder. +- Deleting a cloud-backed copy from a Directory library removes the selected folder but keeps the + cloud project. Other local folders with the same cloud identity may be removed if they are exact + duplicates or disconnected if they differ. +- Deleting from `Personal Cloud` deletes the cloud project and removes the local working copy on the + current device when one exists. + +Zoo Design Studio shows different delete confirmation copy when a Directory library delete will keep +the cloud version. Project deletion is permanent and has no undo. + +## Related + +- [Cloud Sync](/docs/zoo-design-studio/features/data-management/cloud-sync) +- [Project Browser](/docs/zoo-design-studio/features/workspace/project-browser) +- [Version Control](/docs/zoo-design-studio/features/data-management/version-control) diff --git a/content/pages/docs/zoo-design-studio/features/data-management/version-control/index.mdx b/content/pages/docs/zoo-design-studio/features/data-management/version-control/index.mdx index 816057b3..d04e84eb 100644 --- a/content/pages/docs/zoo-design-studio/features/data-management/version-control/index.mdx +++ b/content/pages/docs/zoo-design-studio/features/data-management/version-control/index.mdx @@ -9,3 +9,7 @@ code-based, and KCL is human-readable text. That makes it practical to track rev design states, review changes, and collaborate on models using standard Git workflows today. Native version control in Zoo Design Studio is planned to ship later in 2026. + +[Cloud Sync](/docs/zoo-design-studio/features/data-management/cloud-sync) is separate from Git-style +version control. Cloud sync keeps project copies available through your Zoo account, while Git +records intentional revision history and reviewable changes. diff --git a/content/pages/docs/zoo-design-studio/features/index.mdx b/content/pages/docs/zoo-design-studio/features/index.mdx index 64e7f0e2..cc8cc319 100644 --- a/content/pages/docs/zoo-design-studio/features/index.mdx +++ b/content/pages/docs/zoo-design-studio/features/index.mdx @@ -49,8 +49,9 @@ Studio models into downstream analysis tools while preserving parametric source ### Data Management -[Data Management](/docs/zoo-design-studio/features/data-management) covers project storage, import -and export workflows, default project folders, and code-based version-control workflows. +[Data Management](/docs/zoo-design-studio/features/data-management) covers project storage, project +libraries, cloud sync, import and export workflows, default project folders, and code-based +version-control workflows. ### Technical Support diff --git a/content/pages/docs/zoo-design-studio/features/workspace/project-browser.mdx b/content/pages/docs/zoo-design-studio/features/workspace/project-browser.mdx index 2c2e8aa0..21e379ca 100644 --- a/content/pages/docs/zoo-design-studio/features/workspace/project-browser.mdx +++ b/content/pages/docs/zoo-design-studio/features/workspace/project-browser.mdx @@ -15,7 +15,7 @@ The Project Browser is your home screen for project-level work. ## What You Can Do -- See all projects in your current project directory. +- See projects grouped by [Project Libraries](/docs/zoo-design-studio/features/data-management/project-libraries). - Search projects by name. - Sort projects by `Name` or `Last Modified`. - Create a project. @@ -23,7 +23,11 @@ The Project Browser is your home screen for project-level work. - Open a project. - Duplicate a project. - Rename or delete a project (if you have write access). -- Jump to project directory settings. +- Move projects between libraries. +- Review duplicate local copies of the same cloud project. +- Open Project Libraries settings. +- Inspect cloud sync status badges, including cloud-only, synced, blocked, conflicted, and duplicate + projects. ## Duplicate a Project @@ -36,7 +40,7 @@ From the Project Browser: 1. Right-click the project card. 2. Select **Duplicate project**. -From an open project, open the project menu next to the project name in the left sidebar and select +From an open project, open the project menu next to the project name in the top bar and select **Duplicate project**. In the desktop app, you can also select **File → Duplicate Project**. The copy is named after the original project with `-copy` appended. If that name is already in use, @@ -45,9 +49,16 @@ Zoo Design Studio adds a number, such as `-copy-1` or `-copy-2`. ## What You Cannot Do - Open a project card that does not have write access. -- Rename a project to a name that starts with `.`. ## Key Differences in This Area - Work starts from a project dashboard, not from a single-file open flow. - Project metadata (preview, file count, edit time) is part of the default start experience. +- Cloud projects can appear before they are downloaded locally; opening one creates a local working + copy first. +- A cloud project can have duplicate local copies. The Project Browser keeps the canonical copy + clear, shows duplicate copies for review, and does not silently delete Directory library copies. + +For project storage and sync details, see +[Project Libraries](/docs/zoo-design-studio/features/data-management/project-libraries) and +[Cloud Sync](/docs/zoo-design-studio/features/data-management/cloud-sync). diff --git a/content/pages/docs/zoo-design-studio/features/workspace/settings/user-settings/app/index.mdx b/content/pages/docs/zoo-design-studio/features/workspace/settings/user-settings/app/index.mdx index b73cb9cc..904bee5b 100644 --- a/content/pages/docs/zoo-design-studio/features/workspace/settings/user-settings/app/index.mdx +++ b/content/pages/docs/zoo-design-studio/features/workspace/settings/user-settings/app/index.mdx @@ -16,8 +16,21 @@ The overall appearance of the app. Whether to show the debug panel, a development tool. -### Project Directory +### Libraries -The directory to save and load projects from. +Project libraries control which project sources appear on Home. -This setting is desktop-only. +On desktop, you can add, rename, reorder, and remove Directory libraries. A Directory library points +to a folder on your computer. Removing the library from settings does not delete the projects in that +folder. + +With Cloud Sync, the `Personal Cloud` library appears as a Cloud library. Its settings +row shows the resolved local storage path for the cloud working copy. + +On web, Project Libraries are limited to Personal Cloud. Browser storage is not a +normal local folder, so Zoo Design Studio treats browser projects as cloud-backed projects rather than +showing local-only browser libraries. + +For the full storage model, see +[Project Libraries](/docs/zoo-design-studio/features/data-management/project-libraries) and +[Cloud Sync](/docs/zoo-design-studio/features/data-management/cloud-sync). diff --git a/content/pages/docs/zoo-design-studio/features/workspace/settings/user-settings/projects/index.mdx b/content/pages/docs/zoo-design-studio/features/workspace/settings/user-settings/projects/index.mdx index 3ccde9c0..f21bcb3f 100644 --- a/content/pages/docs/zoo-design-studio/features/workspace/settings/user-settings/projects/index.mdx +++ b/content/pages/docs/zoo-design-studio/features/workspace/settings/user-settings/projects/index.mdx @@ -11,3 +11,6 @@ The `Projects` section contains user-level defaults used when creating new proje ### Default Project Name The default project name to use when creating a new project. + +This setting is desktop-only. Project locations are configured under +[User Settings > App](/docs/zoo-design-studio/features/workspace/settings/user-settings/app).