Agility CMS: content editing and delivery

Assess Agility CMS for store guides and policies. Check how editors model, preview and publish content, and what the separate storefront must deliver.

Agility CMS manages structured editorial content and delivers it to a separately built storefront. It suits retail teams that want reusable buying guides and policy content, provided a developer owns the preview and publication connection.

What Agility manages

Agility holds content items, pages and media. Editors work in its content manager, while the storefront reads published content through an application programming interface (API). Agility’s architecture guide separates content delivery from the website that renders it.

For a retailer, that makes Agility a home for buying advice, category introductions and delivery explanations. Keep current prices, stock quantities and orders in the commerce systems that own them. A guide can reference a product identifier so the storefront retrieves the matching product’s current details.

Copying a price into a guide creates a second value to maintain. Linking the guide to a product identifier lets editorial advice and transactional information change independently. The connection still needs handling for a discontinued product or an identifier that no longer resolves.

Model and preview a store guide

Model a buying guide as reusable fields, then preview it through the storefront that will display it. Agility’s content model documentation describes required fields and validation, plus relationships between content items.

Consider an illustrative mattress guide. Give the guide a title and advice body, with a related policy item for delivery conditions. Store product identifiers in a separate field. These are proposed model choices, not a built-in retail template.

Shared policy content avoids copying the same delivery paragraph into every guide. Decide whether a policy change must affect all linked guides together. A product identifier field also needs a defined matching rule, such as one identifier per sellable variant.

Agility’s preview setup requires a deployed website and a registered preview address. The preview comes from your frontend. The CMS button opens it, but your developer implements the rendering and draft-content access.

Preview the mattress guide with one available product and one unavailable product. Inspect the advice beside the product details, then follow its delivery link. An editor needs to see the consequences of a broken relationship before publication.

Follow an approved content change

An approved change reaches shoppers only after publication and the storefront’s own refresh process. Agility distinguishes saved changes from published content, so a draft can coexist with the version customers already read.

For an illustrative policy update, change the mattress delivery explanation while leaving the existing public version in place. Use the configured approval permissions to separate editing from publication. Agility documents approval and publishing states, including requested approval and declined changes.

After approval, publish the policy and any dependent content that must change with it. The Content Fetch API distinguishes published-content access from preview access. A public content consumer must use the published version.

Agility’s webhooks notify your application about changes. Your application must process the event and refresh its own cached page or trigger its build. Treat a successful CMS publication and a refreshed storefront as separate outcomes.

If customer answers use a separate content index, refresh that index from the approved published content too. Record the source content identifier and version in your connection. Compare the public delivery page with an answer to the same delivery question before closing the change.

Include withdrawal in the workflow. Unpublishing a policy must remove or replace its cached public copy and any answer source that still contains it.

Decide who operates the connection

Agility runs the content service, while your team or agency operates the storefront and its connection. Budget for both responsibilities. A content licence alone does not deliver your page templates or maintain the refresh process.

Agility’s pricing page lists Starter, Pro and Enterprise packages. Its cost factors include users, entries, storage and bandwidth. The comparison lists unlimited API and asset requests, but asset bandwidth has package allowances. Entries include pages and assets as well as content items.

Size a proposal using your actual guide count, media library and publishing team. Include preview hosting and production hosting in the operating budget. Specify the required hosting region in the proposal because the listed location options differ by package.

Agility states that content can be exported through its interface or APIs. An exit rehearsal must also preserve relationships and download the assets the next site needs. Exporting content does not recreate your storefront templates.

Assign a named owner for failed publication events and a second owner for editorial approval. Before choosing Agility, have the delivery owner demonstrate one policy update from draft preview to the public page and connected answer source. That proves who maintains each step after the initial build.

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.

See it in actionFree trial · Simple setup