Testing, saving, and deploying a template

At a glance

• Test previews the result without saving anything.
• Save keeps your progress on MorphMapper's servers so you can come back to it.
• Local Save downloads a copy of the template to your own device.
• Deploy is the one that makes it live — do this last.

All four of these live in the actions menu in the workspace's top bar. They look similar but do different things — know which is which before you click.

Test

Renders your current template against your file and sends the result off for preview, without saving or publishing anything. Use this as often as you like while you're building — it's the safe, no-consequence option.

Clicking Test gives no visible confirmation inside the workspace itself — no toast, no result panel opening here. The rendered output is posted out for whatever's showing the preview to pick up; if you don't have that preview open somewhere, clicking Test will look like nothing happened. Test (like the other three actions) is disabled whenever there's nothing saveable yet — for instance, on a brand-new template you haven't touched.

Save

Saves your current progress — every entry, every graph, your schema configuration, and your plugin settings — so it's there when you come back to this template later. This is what you want after any meaningful chunk of work; it doesn't publish anything or make the template live anywhere.

Only one Save request is ever in flight at a time: if Save gets triggered more than once in quick succession (say, from the header menu and from the leave-without-saving prompt below, back to back), MorphMapper reuses the same in-progress save for both rather than firing a second request.

Local Save

Downloads a copy of the rendered template to your own device as a file, separate from MorphMapper's own save. Use this if you want a local backup, or need to hand the template to someone or something outside MorphMapper.

Deploy

The one action here with real consequences: it renders your template and pushes it live. Do this once you've tested it and you're confident it's ready — it's the last step, not something to click along the way like Test or Save.

The raw editor works differently

Everything above describes the normal workspace. In the raw editor, Save and Deploy aren't separate — saving there deploys immediately. Don't assume the same safety net applies if you ever end up in that screen.

If you try to leave with unsaved changes

Switching templates or domains while you have unsaved changes stops you with a choice: save first and continue, or continue without saving and lose them. There's no silent option here — MorphMapper always asks rather than guessing what you meant.

The confirmation is a modal titled "Navigate to Template Selection" or "Navigate to Domain Selection" (matching whichever you clicked), asking "Do you want to save your changes before navigating?" with two buttons: Continue without saving, which discards your changes and navigates immediately, and Save and continue, which runs the same Save this page describes and only navigates once it succeeds.