Vivant CMS: assess the proposed content workflow
Assess a Vivant CMS proposal against the retail content workflow, public publication, access and maintenance responsibilities required for the website.
- Published
- Last updated
Assess a Vivant CMS proposal by identifying the exact product, then following a buying guide from its first draft to the page customers read. The proposal must name who approves changes, who publishes them and who restores the site after a failed update. Use those responsibilities to compare the complete service cost.
Identify the product in the proposal
Require the proposal to identify the vendor’s legal name, the exact product spelling and the supported release or hosted service edition. CMS means content management system: the software your team uses to create and maintain website content.
Record the product’s official documentation address and the party responsible for maintaining it. Match that information to the order form and support agreement. If an agency supplies the website, distinguish the agency’s trading name from the software it installs or operates.
Use these questions to make the product description specific enough to assess:
- What software will editors sign in to, and who supplies it?
- Which release or service edition does the quoted implementation use?
- Where are the installation, editorial and recovery instructions maintained?
- Who owns the content, hosting account and domain when the service ends?
- Which parts of the proposal are standard product functions, and which require custom work?
A similarly named company’s website cannot establish what the proposed system does. Match every capability to the identified product and the quoted implementation. For an agency-built system, require written operating instructions and a support owner alongside the demonstration.
Evaluate the retail publication task
Ask the supplier to demonstrate a buying guide and a policy correction using the workflow included in the proposal. Follow each change through editing and approval to its public destination. This gives your retail team a concrete acceptance task before it agrees to the service.
For example, consider a hypothetical retailer preparing a guide to choosing outdoor furniture. An editor writes care advice, adds images and references products by their catalogue identifiers. A reviewer checks the advice before a publisher makes the guide available to customers.
During the demonstration, make the editor change a product reference and replace an image. Check where the public page gets its product name and link. Identify whether those details come from the catalogue or from text someone copies into the guide.
Keep transactional facts with the system that owns them. Stock availability, checkout prices and customer orders need an explicit source and update path. A buying guide can explain materials and sizing without becoming a second manually maintained stock list.
Follow a policy correction to every destination
Use a hypothetical change to a bulky-item delivery rule. Have the editor correct the approved policy record, submit it for review and publish the accepted wording. Check the policy page and any buying guide that uses that rule.
If customer answers use the same content, include their source in the demonstration. Establish whether they read the published page, receive an export or use a separate document. Name the event that updates that source and the person who handles a failed update.
Record the expected result at each stage. Saving a draft must leave the previous approved wording available to customers. Publication must put the corrected version at the agreed destination. A linked guide must either receive the correction automatically or have a named editor responsible for updating it.
Check access and operating ownership
Give each publishing responsibility an owner and test it with the access that person will actually receive. An administrator’s demonstration alone does not show what an editor can do.
Test the permissions and recovery process
Use separate editor and publisher accounts to run the acceptance task. Confirm that an editor can prepare a correction without publishing it, if separate approval is part of the proposed workflow. Open the preview as an authorised reviewer, then open the ordinary customer page without editor access. The customer must receive only approved content.
Ask the supplier to remove the test guide and demonstrate the agreed recovery method. Check what happens to its public address, images and any links from other pages. Restoring a record also needs to restore the content the website requires.
The operating agreement must name who handles account removal, backups and failed releases. Specify who receives an incident, who can restore service and which support hours apply. Include access to content exports and the steps for moving to another provider.
Compare the same workload and dependencies
Give each supplier the same workload, such as two editors maintaining buying guides, category advice and store policies. State the expected number of pages and images, update frequency and approval steps. Add catalogue references and any customer-answer destination to the scope.
Compare the implementation charge separately from ongoing service costs. Include hosting, editor access, storage and support, plus any required integration or custom development. Ask who pays for upgrades and changes to the catalogue connection. Record exclusions and the work your team must perform itself.
Use the CMS platform comparison to compare other systems against that same workload. Keep the Vivant CMS proposal’s acceptance tasks in its written scope, with a responsible person and an expected public result for each. Agree the service once its identity, demonstration and operating responsibilities match what your team needs to publish.
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.