Previewing and publishing
Share a draft, publish it, update it, take it offline, and who in your organization can do each.
Every site has two versions: the preview, which is what your latest build
produced, and the live site at its memcode.app address. Builds only ever
change the preview. Nothing reaches the live site until you publish.
Share a preview
To show someone a draft before it's live, open the preview link:
memcode websites open crumb --previewAnyone with a preview link can view the draft for 6 hours. After that the link stops working; open a fresh one.
Publish
Click Publish, or:
memcode websites publish(run inside a pulled site, or pass its directory). The site is live within a minute.
When you build more changes later, the button becomes Publish changes. The live site keeps showing the old version until you click it.
You can't publish while a build is still running, or when the most recent build failed. Build again, and publish once it succeeds. This keeps a half-finished build from ever going live.
Take a site offline
Unpublish takes the live site down but keeps everything else: the preview, the code, assets, and any custom domain setup. Publish again to bring it back.
memcode websites unpublishDelete a site
Under Site settings, Delete website removes the site and takes it offline. Its address and custom domain are released, so you can use them for a new site.
Who can do what
In an organization, anyone can view a site, chat about it, and build changes, because builds only touch the preview. Changing what the public sees or who controls the site takes more:
| Action | Who |
|---|---|
| View, plan, build, edit text in the preview | Any member |
| Publish, publish changes, unpublish | The site's creator, or an org owner or admin |
| Add, verify, or remove a custom domain | The site's creator, or an org owner or admin |
| Upload or delete assets | The site's creator, or an org owner or admin |
| Rename, change the site's default model, delete | The site's creator, or an org owner or admin |
Any member can still pick a model for the builds they run; only saving it as the site's default is limited.