Apollo CMS: content publishing and product scope
Assess the Apollo CMS content product separately from conversation or commerce tools. Check editing, publication and the retailer’s delivery setup.
- Published
- Last updated
Apollo CMS is 5Lab’s content management product within ApolloSuite. Assess it as the place your team structures and publishes content, with a separate scope for customer conversations and commerce. A retail proposal needs to name the CMS installation, the website that displays its records and the work needed to connect them.
Identify the Apollo content product
5Lab identifies Apollo CMS, Apollo CIP and Apollo Commerce as separate products in ApolloSuite. Its terms describe the same product family. Apollo CMS is the content product covered here. The conversation inbox belongs to Apollo CIP, while Apollo Commerce covers the commerce layer.
Put the provider’s full name, 5Lab Group Co., Ltd., beside Apollo CMS in your purchase record. Add the supplied release or build identifier and the contracted modules. The label Apollo alone is too broad to define what your retailer receives. An unrelated product with the same name establishes nothing about this CMS.
Use that record to separate a CMS purchase from a wider implementation. A shared product family can share infrastructure while the contracted website work, conversation service and payment setup have different owners. Price and acceptance criteria need to follow those owners.
Assess the editor’s actual records
Apollo CMS is described by 5Lab through post types, content fields and revisions. The developer overview describes locale-aware fields and shared field definitions across the editor and its interfaces. These are useful foundations for structured content, but your store’s records determine whether the editor fits daily work.
For a hypothetical furniture retailer, use a sofa-care guide and a delivery policy as the assessment records. The guide needs explanatory text and images with useful descriptions. The policy needs a clear delivery area and an approved fee rule. Keep the policy rule separate from decorative page content so a redesign does not change its meaning.
Run an ordinary update through the proposed installation. An author edits the guide, another authorised person approves it and the public page displays the approved version. Compare what each account can change. Include an attempted edit by an account that must only read content. This tests the retailer’s required workflow without assuming that a general permission model supplies a particular approval process.
For media, replace an image and inspect its description and public address. A changed image must reach the guide without breaking other pages that reuse it. Retain the earlier content and image together when testing recovery.
Trace the CMS publication route
An Apollo CMS record needs a defined delivery route to become your public guide. 5Lab describes REST interfaces with permissions and cache rules, plus signed webhooks. Those interfaces give a developer integration options. The storefront implementation determines which option publishes your page.
Trace one policy change from the saved record to the public URL. Record whether publication triggers a site rebuild, refreshes a cache or changes content that the site reads directly. Reload the public page in a fresh session and confirm that its rule matches the approved record. Editing success inside the CMS alone does not complete this check.
If a separate answer service uses the policy, trace its source independently. Identify whether it reads the public page, retrieves CMS records or receives an exported document. Repeat the policy question after the update and compare its answer with the public wording. A connection to the same product family does not establish the refresh interval for that route.
Keep draft material outside the public delivery path. Test this with harmless sample text that appears in an unpublished record and must remain absent from the public page and any connected answer source.
Define the implementation and service boundary
5Lab describes customer-hosted and provider-hosted installations, with CMS pricing quoted per project. Its terms place fees and usage limits in the agreement. They also provide for customer-data export on termination within an agreed period.
Assign hosting maintenance and application updates explicitly. The website developer must also own the page templates, integration failures and the route for recovering a failed publication. Where your existing store retains catalogue prices and checkout, keep those responsibilities in the store contract.
Make portability concrete before signing. Request a sample export of the guide and policy with their media files, field names and relationships. Have the receiving developer map those records to a replacement system. An export right is useful only when the material can be turned back into working pages.
Choose Apollo CMS when the proposed installation completes your content workflow and its service agreement assigns the ongoing work. Approve the implementation against a published guide, a corrected policy and a recovered earlier version, with each result visible on the actual website.
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.