Skip to main content
Managed CMS is optional and requires explicit operator activation, approved resources and deployment acceptance. A plugin installation or successful image build does not establish that it is ready for customer content. Each new instance has its own database and persistent media storage.

​
Create an instance

1

Open CMS

Open CMS in the intended project. The operator must have approved its template and resources.
2

Request the instance

Enter the website name and select Create CMS. This requests a new project instance; it does not create one for every project.
3

Wait for readiness

Follow setup progress. Open the editor once setup and its HTTPS address are ready. You can leave and return to the existing instance.
4

Resolve a blocked setup

Ask your operator to resolve the reported Hosting requirement, then use Resume setup. Do not delete retained resources to force an uncertain setup to run again.

​
Edit and publish

Choose the content language, open a page and save your draft before publishing. The initial template includes pages, text and image sections, SEO fields, media and site settings in English and German. Content language is separate from the Console interface language. Publishing updates the public version. Use Unpublish to take the selected language offline while retaining its content and history. If a newer version was saved by someone else, reload and reconcile your changes before saving. Website grants and local account restrictions apply to each request. CMS access to one project does not grant access to another website.

​
Upload and replace images

Use single-frame PNG, JPEG, WebP or AVIF images up to 10 MiB and 40 megapixels. Add useful alternative text. SVG, HTML and animated images are rejected. To replace an image, upload a new media item and select it in the page. Managed files are immutable; alternative text remains editable. Administrators can move media to trash. Trashed bytes remain retained and count toward storage until a separate explicit purge. If saving or uploading has an uncertain outcome, check the saved content before retrying. Reconcile the state before making another change.

​
Existing websites and retention

An existing website can use the CMS bridge while retaining its own schema and content. Only explicitly allowed collections and globals are exposed. See websites and content and website integration. Disabling the plugin blocks editing and further provisioning, while published content continues serving. Suspend its application in Hosting to take it offline. Database and media remain retained; permanent deletion is separate. Agree on matched database and media backups before using the instance for important content. Retained storage is not a backup or a verified restore service.