2 min read
Core concepts
The ideas behind Adaptar: workspaces, generations, revisions, preview, credits, and publishing.
Workspace
A workspace contains one generated website, its conversation, generated files, images, preview state, saved revisions, site-feature configuration, and publication history.
Generation
A generation is an initial build or a requested update. Adaptar prepares the candidate website, restores it into the live preview, and verifies it.
Revision
A generation is saved as a revision only when the required checks succeed. If a generation fails, the last verified revision remains the safe baseline.
Preview
Preview is the working website inside Adaptar. It lets you inspect a generated change before publishing. Preview is not the public deployment.
Generation credits
Generating a website, asking for changes, and adding, updating, or removing a site feature all use generation credits.
Publishing
Publishing builds an immutable deployment from a verified revision. The public address points to the latest successfully selected deployment.
Saved, visible, and published are different
These three states are the most important distinction in Adaptar:
| State | What it means | Who can see it |
|---|---|---|
| Saved in the workspace | A verified revision exists in your workspace history. | Only you |
| Visible in preview | The change is running in the live preview inside Adaptar. | Only you |
| Published | The revision has been built and deployed to your public address. | Everyone with the link |
Your website address
Published websites use an Adaptar-managed address in this form:
Production address
your-name.adaptar.appThe name you choose stays stable across later updates: publishing a new revision updates the website at the same address. Staging environments may show an address such as staging-your-name.adaptar.app, but production websites always use the simple form above.
Keep exploring
Have a question about this guide?
Talk to support