Publish, preview, or export the site
Choose hosted preview, live publishing, or source export based on handoff needs.
Publish, preview, or export the site
Choose hosted preview, live publishing, or source export based on handoff needs.
Steps
- Open the preview link and check key pages, mobile views, and form paths.
- Publish when ready, then record the publish time and version status.
- When handing off to developers, export the site with assets, locale content, and deployment notes.
Export a standalone CMS
site-only downloads only pre-rendered HTML pages and static assets, with no installer or runtime API. Extract the ZIP and open index.html; other pages live in locale folders. Forms need a separate service. cms-managed is a deployable website and CMS package; cms-only contains the CMS and content APIs for a separately deployed frontend.
- Use a role with publishing permission and a plan that enables standalone export. In Projects, open the project’s More menu and choose Export standalone CMS package. The same action is in Creator’s Tools → Export menu.
- Download and extract the ZIP. Use Node.js 20.12 or newer. Copy the environment example, then edit
.envto replace the administrator credentials and session secret:
cp .env.example .envSet the CMS public origin and the external website origin. Allowed origins must be exact HTTP(S) origins separated by commas; wildcard origins are not supported.
CMS_ADMIN_EMAIL=owner@example.com
CMS_ADMIN_PASSWORD=replace-with-at-least-12-characters
CMS_SESSION_SECRET=replace-with-at-least-32-random-characters
CMS_PUBLIC_URL=https://cms.example.com
SITE_PUBLIC_URL=https://www.example.com
CMS_ALLOWED_ORIGINS=https://www.example.com,http://localhost:4321- Start the service after configuring it. The runtime loads
.envautomatically:
npm run check
npm start- Open
/adminand sign in with the deployment credentials. The root redirects to the CMS; this package does not serve website pages. Verify/healthand read published content through/api/content/collections/news/entries?locale=en. External forms can submit to/api/forms/contact/submissions. Drafts remain private, and administrator login stays on the CMS origin.
Persist and back up data and public/uploads. Protect data/update-config.json. Updates preserve this deployment type and local data. If export is unavailable, check role and plan permissions; if a frontend request returns 403, check the configured origin and restart the service.
Connect a standalone CMS to Qokit
The CMS owner can start the connection. To confirm it, sign in to Qokit with an account that can publish the target project in a workspace with standalone export enabled.
- In the CMS settings, open Deployment license and select Connect to Qokit. Generate a pairing code, copy it, and select Open Qokit.
- Select the target project and enter the code. If the project is missing, switch to its workspace and check that the project is active and you have publishing permission. If the site exists only in the standalone CMS, create a project in the intended Qokit workspace first, then select it here.
- Select Review connection. Check the project, CMS name and address, then select Confirm connection. Return to the CMS and wait for the connection confirmation.
If you already have the target site open in Qokit, go to System settings → Hosting and delivery → Standalone deployments and choose Connect standalone CMS. Enter the code there to use the current project. Pairing registers the installation and issues its deployment license. If the code expires, return to the CMS and choose Generate a new code.
Last updated on