Projects and saving

Keep your editable project separate from exported packages and generated code. This makes it easier to move the project, recover from mistakes, and regenerate output later.

Project files

A project manifest describes the project's documents and related content. Pages and other editable documents normally use .yt; standalone themes use .thme. Imported older documents may keep their existing names.

Use the editor's project and document actions to create, open, rename, or move supported content. Editing a manifest or moving an open document outside the editor can break references or trigger a source conflict.

Removing a project from the workspace list is different from deleting its files. Read the action and its confirmation before proceeding.

Automatic saving

The normal workflow saves committed edits in the background. Give the editor time to complete the write and check its save or error feedback before closing the app or moving the project.

A property field can contain unfinished input. If a panel offers Apply, finish or apply the edit before expecting it to appear in the saved document. Recovery data, an unfinished draft, and a saved source file are different states.

1. Finish the current gesture or field edit.
2. Resolve any invalid input or pending Apply action.
3. Check that the intended page is active and the save operation has completed.
4. If saving fails, keep the editor open and read the error before retrying.

Conflicts and recovery

If another program changes a source file, Yuntu may block a write rather than overwrite the external change. Preserve both versions, identify which program changed the file, and use the editor's available reload or recovery action deliberately.

Do not clear profile, recovery, or history files as a first troubleshooting step. They may contain work that has not reached the source file. Recovery support depends on the document type and the state of the last successful write.

Back up or move a project

Close or finish work on the project before copying it. Keep the manifest, document files, assets, and required local dependencies together. Use the editor's project copy or import workflow where available, then reopen the copy and check its pages and assets.

Generation programs registered globally may need to be installed separately on the destination computer. Fonts available only on your current machine may also need separate setup and appropriate licensing.

History is useful for revisions, but it has retention limits. Maintain your own backups or version control for durable project snapshots. Read Review and history for the distinction between undo, history, and feedback.