Projects, files, and versions
Keep the working source, rendered output, and review link aligned as a project changes.
Resume an existing project
Open a project from Home or use conversation history to return to earlier work. Continuing in the same project preserves the conversation and its files.
Open the file you intend to change
Design Files lists project files. HTML artifacts offer Preview and Code views. A motion source and an MP4 are separate artifacts: changing the source requires a new render before the MP4 changes.
A project can have several file tabs open. Check the active file before editing or leaving feedback, especially when similar drafts sit alongside each other.
Import, rename and remove files
- In the project file area, use the upload control to choose files. After the upload completes, find and open the file in Design Files; selecting a file in the system picker alone is not proof it was imported.
- Use the file menu’s Rename action when offered. Enter the intended name and retain the correct extension. Reopen it and check any pages that reference the old path.
- For Delete, check the file name in the confirmation before proceeding. Multi-selection can delete several files, so clear unrelated selections first. Keep a copy of files you still need; do not assume deleting an asset can be undone through an HTML file’s version history.
If an action is absent or disabled, check project edit permissions and wait for file synchronization to finish. Imported references may also need their fonts, images and scripts to render correctly.
Inspect version history
For a supported HTML file, open the clock control or ⋯ → Versions in the file toolbar. Select a version and preview it. To restore it, choose Switch to this version, then confirm with Switch. OpenDesign creates a new current version from that HTML; it does not remove the later history. Check the restored preview before sharing it. Versions is not available for every file type.
- Select a historical version and inspect its preview first. Use the new-tab preview when you need more space.
- If you only need to deliver that historical result, use the version panel’s available download or export action, such as HTML or ZIP. This does not require switching the project back to that version.
- Restore only when you want that content to become current. After confirmation, reopen the current artifact and check its resources and behavior. Other project files and already published links still need their own checks.
Deliver the right artifact
Export offers formats appropriate to the selected artifact. Preserve relative paths to assets when handing over editable HTML. An MP4 is a playback deliverable, not the animation source. Name checked versions clearly and reopen exported files before delivery.
Use Hand off in the project’s upper-right area to continue development in a coding agent or editor. It differs from Export, which downloads a file, and Share, which publishes a review link. Check the working directory and target tool, then run and review the result in the destination codebase.
| Delivery | Choose it for |
|---|---|
| Single-file download / Export | The selected artifact. Check the format and include dependencies when needed. An HTML file alone can omit images, fonts or scripts. |
| Project ZIP / Download project | Handing over the project files together. Unpack the archive in a separate location and verify its entry file and relative asset paths. |
| Version export | Delivering an earlier checked HTML version without restoring it as current. |
A ZIP archive is a file handover, not a hosted deployment. Open the archive and test the delivered result; a successful download only confirms that the download finished.
Understand the workspace boundary
Local project files, published artifacts, and workspace membership have separate controls. Sending a file does not give a colleague workspace edit rights, and adding a workspace member does not publish an artifact. See sharing and collaboration.