CMS product guides
Find the guide for your store’s CMS. Check its editing, publishing and maintenance responsibilities, or compare platforms before choosing one.
- Published
- Last updated
Use these CMS product guides to assess the system named in your store’s proposal or existing website. A content management system (CMS) can control page editing, supply structured content to another site or organise documents that a publishing connection reads. Start with the product’s actual role in your store. If you haven’t shortlisted a product, use the CMS platform comparison to choose an approach.
Find the system you need to assess
Choose the named guide that matches the product and edition you use. The assessments distinguish the following content roles so you can judge the work behind the product name.
- Site-editing applications let staff edit pages and publish through the application’s templates or connected site. The Craft CMS guide examines a tailored editorial model, templates and commerce options. Assess preview, approval and the person responsible for maintaining extensions.
- Structured content services store fields and content models for a separate website or app to retrieve. The Sanity CMS guide covers content models and the boundary with the transactional catalogue. Assess which team builds the storefront connection and handles changes to those models.
- Controlled document or knowledge sources organise material that another service can read or publish. The Alfresco CMS guide traces approved policy documents into public store knowledge. Assess access permissions and the process that turns approved source material into public content.
A product can cover more than one role. Its guide checks what it publishes, which records it owns and who operates its connection to the store. A document repository’s editing features alone don’t establish that it manages a storefront or takes customer payments.
Keep product prices, stock and order records with their designated system. When a CMS repeats those facts, identify how its copy stays consistent with the store and who fixes a failed update.
Compare platforms before choosing one
The ranked CMS shortlist compares platforms against common retail publishing requirements before you open a product assessment.
Start with the editing your staff need and the content your store must publish. Compare preview and approval controls, then account for developer work and ongoing maintenance. Once you have a named option, use its product guide to examine those responsibilities in detail.
Explore this topic
68 guides
Start here
- Sanity CMS: product and policy contentEvaluate Sanity CMS for a retail content stack. Examine content models, editorial previews, delivery APIs and the boundary with your commerce catalogue.
- Payload CMS: retail content and appsReview Payload CMS collections, blocks and access rules for a retail site. Separate content from commerce records and assess deployment work.
- Contentful CMS: a retail content stackAssess Contentful CMS for reusable retail content. Map product references, locales, publishing controls and delivery to the rest of your stack.
More guides
- Craft CMS: content and commerce decisionsExplore Craft CMS for a bespoke retail site. Examine editorial structure, templates, plugins and commerce options, plus the work your team must maintain.
- Ghost CMS: a retail brand’s publicationConsider Ghost CMS for your brand’s editorial site. Separate publication and membership needs from the catalogue and checkout your store requires.
- HubSpot CMS: content and CRM for retailersUnderstand HubSpot CMS beside its CRM and marketing tools. Review content editing, customer-data boundaries and the implementation your retail team needs.
- Strapi CMS: retail content and APIsAssess Strapi CMS as a retail content source. Review content types, API permissions, customisation and deployment beside your catalogue and storefront.
- Kentico CMS in Australia: publishing in 2026Considering Kentico for retail content? Compare current and legacy editions, then check publishing, headless delivery, hosting and security updates.
- Sitecore CMS: retail publishing in 2026Choose a Sitecore CMS for retail publishing. Check content models, headless delivery and the boundary between approved facts and personalisation.
- Kontent CMS: retail content in 2026Assess Kontent’s CMS for structured retail guidance. Check content relationships, editorial workflow and delivery while keeping it distinct from Kentico.
- Storyblok CMS: retail content in 2026Evaluate Storyblok for retail content and visual editing. Trace blocks and published delivery while keeping the CMS separate from stock and checkout.
- WordPress CMS: retail content in 2026Use WordPress as a retail content source with clear publication rules. Compare conventional and headless delivery, plugins and multilingual guidance.
- Optimizely CMS: retail publishing in 2026Compare Optimizely CMS editions for retail content. Keep approved product guidance separate from experiments, commerce and partner services.
- Framer CMS: retail content in 2026Assess Framer’s CMS for product guidance. Understand collections, publishing and the separate systems needed for catalogue facts and checkout.
- Squarespace CMS: retail content in 2026See how Squarespace’s CMS supports retail guidance. Check editorial control, product records and export limits before choosing a publishing workflow.
- Wix CMS: retail content in 2026Evaluate Wix CMS for retail guidance. Separate public content from customer records and check dynamic pages, permissions and product-data ownership.
- Agility CMS: content editing and deliveryAssess Agility CMS for store guides and policies. Check how editors model, preview and publish content, and what the separate storefront must deliver.
- Alfresco CMS: documents and public store knowledgeUnderstand Alfresco’s document and content role before using it for store policies. Check approved versions, access and the route to public answers.
- Backdrop CMS: editing, modules and maintenanceEvaluate Backdrop CMS for a retail content site. Check editing, layouts, modules and maintenance, with product and checkout records kept separate.
- Brightspot CMS: editorial workflow and deliveryAssess Brightspot CMS for a retail publishing team. Compare content models, review, delivery and implementation responsibilities before choosing it.
- ButterCMS: editing beside your storefrontEvaluate ButterCMS as the editing layer beside a store. Check content types, previews, API delivery and the work needed to keep published guidance current.
- Camaleon CMS: site editing and operating workCheck Camaleon CMS for a retail content site. Assess its editing, theme and extension model, then identify the hosting and maintenance work it needs.
- Cloud CMS: content models and delivery controlsAssess the Cloud CMS product for retail content. Check models, access and delivery, while separating it from generic cloud-hosted CMS options.
- Concrete CMS: page editing and store contentEvaluate Concrete CMS for store guides and policy pages. Check page editing, permissions, extensions and the maintenance behind the finished site.
- Contentstack CMS: content workflows and frontendsAssess Contentstack for retail content reuse. Check modelling, editorial review, preview and delivery, with the storefront’s responsibilities made clear.
- DatoCMS: content modelling, media and previewsEvaluate DatoCMS for retail guides and policies. Check content relationships, media, editor previews and the frontend work required to publish updates.
- Decap CMS: Git editing and site publicationAssess Decap CMS and the former Netlify CMS name. Check repository editing, authentication, preview and the build that publishes store content.
- Directus CMS: content records, access and deliveryEvaluate Directus for retail content records. Check schema, editor access, API delivery and hosting, while keeping private and transactional data separate.
- django CMS: editing a retail websiteAssess django CMS as a publishing application. Check page editing, plugins, permissions and the Django development needed around a retail content site.
- Duda CMS: content editing and store boundariesEvaluate Duda for retail content. Check page editing, connected collections and publishing, then separate those functions from selling and orders.
- Elcom CMS: public content and access controlsAssess Elcom CMS for retail publishing. Check public pages, editor workflow and permissions, while distinguishing internal portals and private records.
- EmDash CMS: publishing with AstroEvaluate EmDash CMS for an Astro content site. Check editing, plugins, publication and hosting responsibilities before connecting store guidance.
- FarCry CMS: content publishing and supportUnderstand the FarCry CMS behind an existing content site. Check publishing, extensions and runtime support before maintaining or replacing it.
- Figma Sites CMS: content and publishingCheck how Figma Sites manages CMS collections and published pages. Separate that workflow from design prototypes, Figma Make and commerce records.
- Grav CMS: file-based content and editingAssess Grav CMS for a retail content site. Check file-based content, editor access, themes and plugins, with a clear plan for publishing and recovery.
- Hygraph CMS: schemas, review and content APIsEvaluate Hygraph for reusable retail content. Check schemas, editorial stages, preview and API delivery before connecting guides to the storefront.
- Apollo CMS: content publishing and product scopeAssess the Apollo CMS content product separately from conversation or commerce tools. Check editing, publication and the retailer’s delivery setup.
- FusionCMS: editions, editing and maintenanceIdentify the original FusionCMS and its edition before assessing a retail site. Check editing and maintenance without mixing unrelated products.
- Genesis CMS: identify the platform and workflowWhich Genesis CMS does the proposal mean? The guide separates providers, content models and retail integration work before you choose.
- Spark CMS: site editing and provider supportSpark CMS puts editing, publishing and retail integration responsibilities into a provider-led website setup that this guide helps you assess.
- CMS Builder: content models and site publishingAssess interactivetools.com’s CMS Builder for a retail content site. Check content models, editor access, template integration and maintenance.
- Salesforce CMS: content, channels and store recordsAssess Salesforce CMS for the retail team’s content workflow and check who controls the published guidance and its links to store records.
- Sitefinity CMS: editing, delivery and retail useEvaluate Sitefinity CMS through the way editors maintain product guidance, approve a correction and deliver the intended content to customers.
- Squiz CMS: content operations and store connectionsCheck the Squiz CMS proposal against the retailer’s editing and publication work, with clear responsibility for content and commerce connections.
- Total CMS: content editing and deployment choicesAssess the proposed Total CMS version through its content model, editing and deployment responsibilities before assigning the store’s ongoing work.
- Tina CMS: editing, Git and the published store siteFollow a Tina CMS content correction from the editor through storage, preview and the site build to verify what customers actually receive.
- Confluence CMS: internal knowledge and public contentAssess Confluence as a CMS for retail knowledge, separating internal guidance from public publication, access and keeping product facts current.
- Keystatic CMS: editing and publishing store contentAssess Keystatic CMS through an editor’s change, its stored content and the published retail page, including access, previews and failed deployments.
- Kirby CMS: files, editing and retail content deliveryAssess Kirby CMS for retail content by following a page from its files and editor to publication, with clear commerce boundaries and maintenance duties.
- Magnolia CMS: authoring, delivery and retail recordsAssess Magnolia CMS for retail authoring, public delivery and commerce records, with the proposed deployment and operating costs made clear.
- October CMS: content, extensions and store recordsAssess October CMS by its content workflow, required extensions and published retail pages, including the runtime and maintenance responsibilities.
- Silverstripe CMS: editing, extensions and retail contentAssess Silverstripe CMS through a retail content change, its permissions and public delivery, with separate responsibilities for commerce and maintenance.
- Statamic CMS: modelling and publishing retail contentAssess Statamic CMS for structured retail guidance, editorial access and publication, with catalogue records and ongoing work clearly assigned.
- Prismic CMS: page models, previews and publicationAssess Prismic CMS by following retail content through page models, previews and publication, with clear owners for the storefront and product facts.
- Instatic CMS: editing, static publication and upkeepAssess Instatic CMS through its visual editing, content records and static publication, with the server, recovery and commerce responsibilities made clear.
- Sveltia CMS: Git editing and the published retail siteAssess Sveltia CMS for repository-backed retail content, editor access, previews and publication, keeping the site aligned with approved records.
- Vivant CMS: assess the proposed content workflowAssess a Vivant CMS proposal against the retail content workflow, public publication, access and maintenance responsibilities required for the website.
- Joomla CMS: editing and maintaining retail contentAssess Joomla CMS through its configured editor, extensions and public retail content, with the commerce connection and maintenance work clearly assigned.
- CMS Made Simple for retail contentAssess CMS Made Simple for store guides and policies, checking editorial work, maintained extensions and how an approved change reaches the customer.
- Microsoft CMS options for retail publishingCompare Microsoft publishing products and SharePoint content roles, keeping public retail pages, internal documents and commerce records separate.
- Keystone CMS for structured retail contentAssess Keystone CMS for the content model, editor and delivery path behind retail guides, with application and checkout responsibilities kept explicit.
- Liferay CMS for a retail content workflowAssess Liferay’s content and experience tools for retail publishing, comparing editorial controls, integration work and the customer-facing result.
- Notion CMS: publishing retail content from NotionAssess Notion as an editing and publishing source for retail guides, checking permissions, supported delivery and how corrections reach the public page.
- Pages CMS for repository-backed retail contentAssess Pages CMS for editing repository content, checking its file model, editor access and the build that publishes a retail page.
- Supabase CMS: define the editor and publishing layerAssess a CMS built around Supabase by separating database and backend services from editing, approval and the public retail content path.
- TYPO3 CMS for retail content and publishingAssess TYPO3 CMS for retail guides and policies, checking editorial permissions, content delivery and the work needed to maintain the actual installation.
- Wagtail CMS for structured retail publishingAssess Wagtail CMS for retail editing, structured pages and supported delivery, keeping the Python application and commerce responsibilities explicit.
- Zoho CMS options for retail contentIdentify the actual Zoho publishing product and assess its editor, public pages and commerce handover against the retailer’s content requirements.