These guides describe the day-to-day product and the decisions needed to run Docleus in production.
| Guide | Use it for |
|---|---|
| Workspaces and pages | Organizations, spaces, page trees, editing, search, and collaboration |
| Reviewing and publishing | Change requests, approvals, conflicts, sites, domains, and rollback |
| People and access | Roles, invitations, account security, and OIDC |
| Plugins | The default bundle, enablement, installation, and trust |
| Administration | Configuration, databases, blobs, and reverse proxies |
| Operations | Backups, upgrades, exports, monitoring, and troubleshooting |
The content lifecycle
Docleus separates editing from publishing:
Edit a page
|
v
Commit the change on a branch
|
v
Review and merge into main
|
v
Publish an immutable site snapshotThis separation means a saved edit is not automatically visible to site
visitors. A published site continues serving its current publication until
someone explicitly publishes a newer main revision or rolls back to an
earlier one.