CMS: content and visual editor
Create, edit, and publish your online store content pages in the Contents view and visual editor without coding.
CMS visual workflow
Content is the CMS workspace for building pages, e-commerce sections, and blogs. Content is first created as a draft, edited in a visual editor, and published using a separate function.
A single content can contain localized texts for all active data languages. Separate content rows are not automatically created for different languages. The publication checks that the values of localized fields are valid in the active languages.
CMS: content and visual editor
The Contents page can be found at /cms/content . The list shows Name , Target , Template , Updated , possible start and end times, and Status . The statuses are Unpublished , Published , and Archived . The list can be narrowed down using Template and Status filters; there is no separate language region filter in the current list.
The content types are Page , Section , and Blog . A page and blog use their own URL path. A section is assigned to a homepage, checkout, product page, category, or manufacturer page in the visual editor, with the editor taking control of the technical URL selection. Creating and editing a blog requires a CMS subscription.
Select multiple rows in the list to Duplicate , Publish , or Unpublish one by one through the same selection. The bulk operation processes the selected IDs sequentially, not as a single atomic event. The list drag handle only changes the local order of the visible rows; it does not store the new priority on the server.
Browse and filter content
Browse content using the Filters panel. Template limits the list to Page, Section, or Blog content. Status limits the list to published, unpublished, or archived content. Clear the selection to see all templates or statuses. The list returns a maximum of 200 most recently updated content, and there is no pagination on the page beyond this limit.
The target tells you the URL path of a page or blog or the technical targeting path of a section. Updated helps you find the most recently edited content. Status tells you the publishing status, but new changes made to published content may not yet be published; open the content and check the Unpublished Changes label in the editor.
Dragging the list does not replace the Priority field. If content selection in the online store depends on priority, open the content and change the integer value in the page settings. Do not infer the selection order in the online store from the visual row order in the list.
Create new content
Create a new content by selecting New Content . Select Type : Page, Section or Blog . Enter a Name that will identify the content in the content manager. For pages and blogs, a URL path is given, which must begin with / ; for sections, the URL destination is selected only in the editor. Select Create Content .
The creation creates an empty draft with a priority of 0 and an empty list of content blocks. No status and priority selections are made in the creation window. There is also no single language region selected for the content: the visual editor offers all store data languages within the same content in localizable fields.
The URL path of the page or blog must comply with the server's uniqueness limits. If the same template and path cause a conflict, creation will be blocked. A section can exist without a regular page URL, but it needs to be aligned in the editor before it can be used meaningfully. Name unpublished content clearly, because the Name is the administrator's identifier and not the localized title visible to the client.
Build content with a visual editor
Build content by opening its name from the list. On the left side of the visual editor are Add and Layers . The Add tab shows the selection of components provided by the online store, and Layers shows the hierarchy of blocks. Blocks can be added, duplicated, moved, surrounded by a partition, and deleted.
The preview in the middle uses /content/preview URL of the online store. Views include Desktop , Tablet , Mobile , Side by Side , and Full View . Width and magnification are adjustable. The preview shows a draft, but it is not a substitute for reviewing the actual published page in the online store.
On the right are Settings , Page Settings , and Style . The settings for the selected block come from the e-commerce component schema and can include texts, images, colors, lists, product and category selections, or other fields. Localizable fields are displayed by data language. Changes are automatically saved with a delay of about 600 milliseconds and mark the content as unpublished.
Edit routing and page settings
In the page settings, edit Name , Template , Status , Priority , and the template-based URL. Metadata changes are automatically saved after a delay of approximately 600 milliseconds. A confirmation of the save is displayed if successful; the error must be corrected before leaving the page.
A page uses the content category and the last part of the page URL to build the path. A section uses the Targeting option: Home, Checkout, Product Page, Category, or Manufacturer Page. A blog uses a direct URL path and separate blog information such as title, summary, preview image, publication date, and Blog Listing option.
Priority is an integer. The e-commerce content cache organizes published content within the template from highest priority to lowest priority and then by ID. Published URLs for pages and blogs are generated from the path. Avoid overlapping items and only use priority when multiple pieces of content are truly competing for the same placement.
Publish and unpublish
Publish the content only after the blocks, routing, data language texts, and different display widths have been checked. In the editor, select Publish . The service validates the content structure and localized values of the active data languages, marks the content as published, records the publishing time, and clears the e-commerce cache for that content model.
The list allows you to publish or unpublish selected rows. Unpublish changes the content to an unpublished state. The operations are performed on the selected content sequentially; if one fails, previous successful changes are not rolled back. Check the list after the bulk operation.
Archived is selected in the Status field in the editor and is automatically saved. Changing the published status to Draft or Archived triggers a template cache purge. Deleting content is a separate, permanent action; do not use deletion to simply temporarily pause publishing.
Check the content in the online store
Review content in the online store in addition to the editor preview. Published content is loaded into the online store cache with the template, URL path, priority, and localized values. Page and blog paths are formed only from published rows with a valid path.
Localized block values are resolved according to the language of the online store within the same content ID. Separate content for each language is not needed unless the business truly requires a separate structure or route. However, the publication requires the necessary values for all active data languages.
If there is multiple published content for the same item, priority and template-specific handling will affect the selection. The Published status alone does not guarantee that the content is exactly where you expect it to be. Check the public page with the correct domain, language, and device width, and make sure that the cache is not yet refreshed.
Good to know
It is good to know that creation always creates unpublished content with priority 0. The types of the creation window are Page, Section and Blog; language area, status and priority are not separate fields in it. Localized texts are maintained within the same content by data language.
Editor blocks and metadata are saved automatically, but saved unpublished content is not the same as the published version. Unpublished changes indicate that there is content in the editor that has changed since publishing. Use the Publish function only after reviewing.
The list's Duplicate, Publish, and Unpublish bulk actions are not a single event. Dragging the list does not save priority. After each major change, check the content list and the actual page in the online store.