MOMENTVM works as a headless CMS, this means that MOMENTVM itself is not required for the published content to be viewed. It merely facilitates content processes and then handed over the content artifacts to Commerce Cloud - which will serve the content to your users.
For this to work we need to establish an API connection to Commerce Cloud. This is a standard way of sending over content in a format which Commerce Cloud understands.
Every row on a page is made of a different „blueprint“ which we call Template.
A Template for example determines that there is an image on the left and a headline and text on the right.
Another template would then be a paragraph which spans the whole page.
Templates are only html, so they can be developed by any web developer. You don’t need Salesforce expertise to do this.
Templates also support a bit of magic like conditionals and other control syntax. This can be used to create small variants of these templates and not to create a new template for each little variation.
Also it takes in variables. Those can be image paths or translations or other fields that users should be able to set in the live editor.
As soon as you send your page it will be stored as either only content assets or a content slot and content assets.
Both terms are Salesforce specific and needed so Commerce Cloud understands what MOMENTVM sends it.
Content Assets are plain html content which can be localized in different languages.
Content Slots determine which asset should be shown at any given point in time. Meaning they handle scheduling and more advanced functionality like showing content for a specific customer group and more.
If you choose to use MOMENTVMs image/media features, images will be resized on the fly to whatever your templates specify and will be stored on Commerce Clouds WebDAV storage automatically. To learn more read about MOMENTVM images.
Last updated January 21, 2020
This is the official documentation for MOMENTVM Content Cloud for Salesforce Commerce Cloud.