Cloud CMS: content models and delivery controls
Assess the Cloud CMS product for retail content. Check models, access and delivery, while separating it from generic cloud-hosted CMS options.
- Published
- Last updated
Cloud CMS is Gitana’s editorial content service for modelling, reviewing and delivering content to your applications. It suits retail guidance that needs controlled versions and approval. Your storefront still needs its own presentation and connection to live commerce data.
Identify Cloud CMS and Gitana
Cloud CMS is a named product within Gitana’s content platform. A CMS installed on cloud hosting describes a deployment choice and says nothing about these editorial controls.
Gitana’s current site presents the product as Editorial & Collaboration, while its technical documentation retains the Cloud CMS name. The provider is Gitana Software, Inc. Hosted procurement uses Gitana Cloud plans, and self-managed licensing is a separate operating choice.
Specify the plan and deployed version in your implementation proposal. This assessment uses Gitana’s 4.0 documentation for the content engine. Don’t apply a feature from another Gitana service to your proposed edition without matching its entitlement.
Cloud CMS makes content available through an application programming interface (API). Gitana’s frontend guidance explains that you build the consuming application. The editorial interface doesn’t create a finished retail storefront for you.
Model reusable store guidance
Use typed content records for advice you want to reuse across the store. Gitana’s content model definitions describe types, associations and aspects through JSON Schema. These describe the fields a record accepts and its relationships to other content.
For example, a hypothetical walking-shoe guide could have a title, advice sections, an image reference and a list of product identifiers. Put shared care instructions in a separate record that several guides reference. Give images meaningful alternative text and retain their usage rights alongside the asset.
Keep the product identifiers stable when an editor changes the guide. The storefront can use those identifiers to retrieve current prices and availability from the commerce system. Copying those values into editorial paragraphs creates a second version for staff to maintain.
Model a delivery policy separately from a buying guide. A policy record needs its approved wording and applicable region. An order’s current dispatch status belongs to the order system. Reusing the same policy record across pages reduces the number of places an editor must change it.
Release the intended content version
Branches separate work in progress from the content a consuming application reads. Gitana documents forking and merging branches, including previews through frontends that switch branch identifiers. A branch is a content workspace, not proof of a separate production environment.
Consider a hypothetical delivery-policy change for oversized items. An editor revises the policy on a working branch and previews the affected pages. A reviewer approves the wording before the configured publishing process sends it to the production destination. Grant editorial access separately from the production application’s read access, using the plan’s roles and access controls.
Gitana’s deployment documentation describes publication from a project branch to configured endpoints, including another branch or file storage. Workflow can trigger deployment. The chosen publishing configuration determines the content that reaches each destination.
Approval and storefront refresh are separate events. An API-driven page must read the production content. A static storefront needs a rebuild, and cached pages need the configured cache refresh. Any downstream answer source also needs its refresh before it uses the revised policy.
Make that complete path the acceptance check. Publish the approved example, reload the customer-facing policy page and confirm that its wording matches the production version. Also check that an unfinished edit remains private.
Check deployment and exit requirements
Gitana Cloud assigns infrastructure operation to the provider, while self-managed Gitana assigns it to your team. The hosted service runs in US or EU regions. Include that location in your data-handling assessment for an Australian store.
The hosted plan comparison separates project and user limits from asset storage, API throughput and monthly transfer allowances. Environment provision and support also differ by plan. Size the proposal against both normal traffic and a campaign peak, including images delivered from the service.
Self-managed Gitana uses commercial licensing with container images and Kubernetes deployment resources. Your operating budget must cover infrastructure and recovery work as well as the licence. Name who applies upgrades and who investigates failed content delivery.
Gitana’s transfer service exports content through archives with a manifest and dependency information. An export is an input to migration, not a replacement frontend. Include the models and media required to reconstruct one representative guide in another system.
Before committing to the implementation, assign owners for the publishing process, frontend refresh and recovery. Include an export rehearsal in the handover so the retailer can recover its content without relying on the original developer.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.