Website source workflow

Getme separates saving website source from publishing it live. The CLI and SDKs can pull source, validate changes, save them into a development session, and create previews. Live publication remains an explicit publish-request flow.

1. Start from an existing site or custom source

Start by pulling the current site source into a local project.

getme sites pull --site site_...

The CLI stores local project metadata so later commands can compare your files against the same site and source revision.

If the workspace has no live site, or your project does not use a Getme base theme, create a standalone development session from a complete custom source tree instead:

getme sites init --name "Custom storefront"
# Replace or extend the starter files with your implementation.
getme sites create --name "Custom storefront"

sites create does not require an existing site_... id or a base-theme selection. The API applies the same path, manifest, template, registry, settings, reference, content, and asset validation rules before it creates the draft. The returned site and development-session ids are stored in .getme/.

2. Validate before saving

Run validation before pushing changes. Validation checks the project shape against the public site source contract and catches unsafe or unsupported files before a development session is updated.

getme sites check
getme sites diff

Validation errors stop the workflow. Advisory findings are returned separately in warnings[] and do not make the source invalid. For example, an enabled navigation page_key with no enabled page-registry entry is reported before the CLI continues, helping you catch a preview route mismatch without blocking an otherwise valid source save.

3. Save to a development session

Use push or deploy to save source changes. This does not publish to the live site.

getme sites push --site site_...

For guarded CI workflows, deploy performs collect, validate, diff, push, and preview in one command.

getme sites deploy --site site_...

4. Preview

Create a preview URL for the saved development session.

getme sites preview --site site_...

Use the preview to review source, page content, and visual changes before a live publish request.

5. Request publication

When the preview is ready, create a publish request. Public developer tokens do not directly publish live source.

getme sites publish-request --site site_... --message "Ready for review"