$wsCmsPage - Output a CMS page - WEBSALE Dokumentation

With the $wsCmsPage module, you access the page document of the currently requested CMS page in the template. The module delivers the JSON document from the object storage unchanged, without renaming or reordering. A typical use case is the CMS page template, which outputs the content of a content page maintained in Strapi.

The module is only populated on CMS pages, i.e. on pages rendered via the CmsPage view controller. On all other pages, $wsCmsPage is empty (null).

Further pages on this topic:

Delivery of CMS pages to the shop explains how the pages get into the object storage, how the SEO URL is created, and which fields the shop itself evaluates.
Template theme explains the CMS page template and its integration into the base template.

Module overview

Example / excerpt of $wsCmsPage

{{= $wsCmsPage | json }}

JSON output

{
  "contentType": "api::contentpage.contentpage",
  "meta": {
    "id": 92,
    "documentId": "jyllb6ubw0dj62vndr0lh7z1",
    "locale": "de",
    "createdAt": "2026-06-26T08:00:00.000Z",
    "updatedAt": "2026-07-16T09:00:00.000Z",
    "publishedAt": "2026-07-16T09:03:00.000Z",
    "url": "Zahlungsarten",
    "metaTitle": "Zahlungsarten",
    "metaDescription": "Beschreibung zu Zahlungsarten",
    "robots": ["noindex", "nofollow"],
    "hreflang": [
      {
        "language": "fr-fr",
        "url": "myshop.fr/paiement",
        "subshopId": "francais",
        "default": false
      }
    ]
  },
  "fields": [
    { "name": "Markup", "type": "richtext", "value": "AGB Content" },
    {
      "name": "content",
      "type": "dynamiczone",
      "value": [
        {
          "component": "elemente.ws-markup",
          "id": 96,
          "fields": [
            { "name": "FullWidth", "type": "boolean", "value": false }
          ]
        }
      ]
    }
  ]
}

Variables overview

Name	Return type	Description
`contentType`	string	Strapi identifier of the content type the page originates from. Not evaluated by the shop.
`meta`	map	Administrative data of the page plus the SEO block.
`meta.url`	string	URL of the page, without a leading slash.
`meta.metaTitle`	string	Meta title. Additionally set by the shop as the page title and available via `$wsViews.metaTitle()`.
`meta.metaDescription`	string	Meta description. Additionally set by the shop and available via `$wsViews.metaDescription()`.
`meta.robots`	array	Robots directives of the page. Additionally merged by the shop into `$wsViews.current.robotOptions`.
`meta.publishedAt`	string or null	Timestamp of publication. `null` for drafts.
`meta.hreflang`	array	Alternate language objects (`language`, `url`, `subshopId`, `default`). Are not output automatically.
`meta.id`	number	Internal numeric Strapi ID (per language version).
`meta.documentId`	string	Stable, language-independent document ID.
`meta.locale`	string	Language of the document, for example `de`.
`meta.createdAt` / `meta.updatedAt`	string (ISO-8601)	Timestamps from Strapi.
`fields`	array	The content fields of the page, each `{ name, type, value }`. Unchanged from Strapi.

Methods

No methods are available for $wsCmsPage.

Variables

$wsCmsPage.contentType

Returns the Strapi content type the requested page originates from. The content type corresponds to the input mask behind the page and defines which fields an editor can fill in.

{{= $wsCmsPage.contentType }}

$wsCmsPage.meta

Contains the administrative data and the SEO block of the page.

{{= $wsCmsPage.meta | json }}

The shop already sets the meta title and meta description itself. In the base template, they are usually output via the functions $wsViews.metaTitle() and $wsViews.metaDescription(), so that all page types are handled consistently. Direct access via $wsCmsPage.meta is only needed if you require the raw values elsewhere.

Which of these fields the shop evaluates and which fields are purely administrative data is described under The SEO block in meta.

$wsCmsPage.fields

Contains the content fields of the page. Each entry has the keys name, type, and value. The shop passes this list on unchanged and does not interpret it. Which field names and components exist depends on the Strapi modeling of the respective shop. For access, the list is converted once into a name/value object:

{{ if $wsCmsPage }}
    {{ var $cFields = {} }}
    {{ foreach $cField in $wsCmsPage.fields }}
        {{ $cFields[$cField.name] = $cField.value }}
    {{ /foreach }}

    <h1>{{= $wsCmsPage.meta.metaTitle }}</h1>
    <div>{{! $cFields.Markup }}</div>
{{ /if }}

The pattern applies at every level, including within components (value.fields) and for the blocks of content blocks. The field types and the form of the respective value are described under The field types, migrating existing field accesses under Step 4 and Step 5.

The order of the fields list follows the schema definition and is meaningless for rendering. Therefore, always access fields via name and never via position. The order within an array value (content blocks, repeatable components), by contrast, corresponds exactly to the editor’s arrangement and must be preserved when rendering.

Actions

No actions are available for $wsCmsPage.

Examples

Check a shared base template for CMS content

Since $wsCmsPage is null on all other pages, a shared base template can safely check for it:

{{ if $wsCmsPage }}
    {{# only on CMS pages #}}
{{ /if }}

Output alternate languages

meta.hreflang is not automatically included in the shop’s hreflang directives, $wsViews.current.getHreflangAutomatic() returns nothing for CMS pages. For output in the HTML head:

{{ foreach $cAlt in $wsCmsPage.meta.hreflang }}
    <link rel="alternate" hreflang="{{= $cAlt.language }}" href="{{= $cAlt.url }}">
{{ /foreach }}

Make unknown components visible in test mode

Without an {{ else }} branch, a newly created component that is not implemented in the template silently disappears from the page:

{{ foreach $cItem in $cFields.content }}
    {{ if $cItem.component == "elemente.ws-markup" }}
        {{# … output … #}}
    {{ else }}
        {{ if $wsTestMode.active }}
            <!-- Component "{{= $cItem.component }}" is not implemented in the template -->
        {{ /if }}
    {{ /if }}
{{ /foreach }}

Mark a draft in test mode

A draft (meta.publishedAt is null) is only delivered when test mode is active. This can be made visible in the template:

{{ if $wsCmsPage && !$wsCmsPage.meta.publishedAt }}
    <p class="notice">This page is a draft and not publicly accessible.</p>
{{ /if }}

Frontend

The basics

Getting started

Feature overview

Examples

Reference – Actions

Reference – Language

Reference – Modules

$wsCmsPage - Output a CMS page

Module overview

Methods

Variables

$wsCmsPage.contentType

$wsCmsPage.meta

$wsCmsPage.fields

Actions

Examples

Check a shared base template for CMS content

Output alternate languages

Make unknown components visible in test mode

Mark a draft in test mode

​Module overview

​Methods

​Variables

​$wsCmsPage.contentType

​$wsCmsPage.meta

​$wsCmsPage.fields

​Actions

​Examples

​Check a shared base template for CMS content

​Output alternate languages

​Make unknown components visible in test mode

​Mark a draft in test mode

​Related links

Module overview

Methods

Variables

$wsCmsPage.contentType

$wsCmsPage.meta

$wsCmsPage.fields

Actions

Examples

Check a shared base template for CMS content

Output alternate languages

Make unknown components visible in test mode

Mark a draft in test mode

Related links