> ## Documentation Index
> Fetch the complete documentation index at: https://docs.webdock.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Websites and content

> Edit through Console while keeping drafts, previews and published pages separate.

Each connected website keeps its own Payload CMS, content schema and runtime credentials. Console provides a common entry point without combining customer content into a shared website database.

<Steps>
  <Step title="Select the website">Open an assigned website in Console. Access is checked against your current account, workspace and website grants.</Step>
  <Step title="Edit supported content">Choose a collection or page available for that website. Fields depend on its schema; connecting a website does not create a generic schema designer.</Step>
  <Step title="Preview your changes">Inspect the draft. On websites with the canvas integration, preview can show unsaved edits on responsive artboards.</Step>
  <Step title="Publish deliberately">Save and publish through the supported controls. A preview does not publish changes. Check the public page after publication.</Step>
</Steps>

## Canvas-enabled websites

The canvas supports text, images, shapes and buttons, layers, undo, and desktop, tablet and mobile artboards. Draft and published pages are separate. Homepage activation is also separate from editing.

If another editor changed a page, resolve the version conflict before saving. Do not overwrite a newer version just to dismiss the conflict.

## Connecting a website

A CMS inventory record describes an existing connection. It does not install Payload, provision a database or establish all SSO permissions. Operators configure the website binding and integration before customers can enter it.

See [website integration](/developers/website-integration) for the developer boundary.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.