Projects

Archive, deletion, and republishing

A clear guide to what happens to projects after publish and how to manage them safely afterward.

4 min readUpdated April 2026

What is the archive?

The archive is where published projects live after they leave the active workspace. It acts like a management layer for finished results: you can review them, open the live link, return to editing, take them offline, or remove them permanently.

This keeps your main creation area focused on current work while still preserving access to projects that are already part of your published history.

What happens after publish

When you publish a project, Milestis creates a live web version and moves that project into the archived side of your workflow. Published projects can still be managed later, but they are treated as finished outputs rather than fresh drafts.

In the archive you may see a project as Published or Offline, depending on whether the live link is still active.

Archived does not mean lost. It means the project has already gone through publishing and is now being managed as a finished result.

Unpublish a project

Unpublishing takes the live version offline without deleting the project data itself. This is useful when you want to hide a project temporarily, revise it, or stop sharing it.

After unpublishing, the archive will still keep the project, but its live state changes from published to offline.

Republish a project

Republish brings an archived offline project back online. It is the right choice when the project already existed as a published result and you want to make it live again.

In the current product flow, republishing is supported as a lightweight return-to-live action and does not currently consume extra credits.

Delete permanently

Permanent deletion is the destructive action. It removes the archived project, clears exported files and storage data, and immediately takes any live site offline.

This is different from unpublish. Unpublish hides the project. Permanent deletion removes it.

The live site goes offline immediately.
Stored exported files are removed.
Project data is no longer kept in the archive.
Credits spent on the original publish are not refunded.

Use permanent deletion only when you are sure the project is no longer needed. If you only want to hide it for a while, unpublish is the safer choice.

Best practices

Keep active work in the editor, and treat the archive as the home for already-published results.
Unpublish when you need a pause. Delete only when you want the project gone for good.
Before deleting, make sure you no longer need the live link or associated files.
Use republish when the project already belongs to your published history and simply needs to go live again.