Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 5 Next »

Marketing Content → Static Pages

What are Static Pages?

Static Pages allow publishing arbitrary web content to customers under a publicly accessible address. These will be available both on the web and native apps.

Basics

All Static Pages contain an identifiable title and path.

Localized Title

The Localized Title field defines the page’s title as seen by users in their web browsers.

Localized Title and Title serve the same purpose; the latter is only used as a fallback, doesn’t support multilingual features, and it will be deprecated in the future.

Localized Path

The Localized Path field defines the URL path where the page will become publicly accessible.

Localized Path and Path serve the same purpose; the latter is only used as a fallback, doesn’t support multilingual features, and it will be deprecated in the future.

irudia-20240917-121528.png

Content

Static Pages' content can be defined using either widgets or by manually authoring HTML and CSS.

We strongly recommend relying on Widgets as much as possible because they integrate best with other multilingual features as well as the overall look & feel of the site.

Widgets

Widgets give you the ability to add functionality for your static pages, without having to code a single line.

TBD: list of widgets

Accordion

Locale Block Text

Header

Image

Call To Action

Double Image

Preview

Quote

Info Cells

Multi

Nutrition Explorer

Nutrition Info

Anchor

Anchor Links

Download File

Video

YouTube

WebView

Loyalty Banner

Loyalty Tab Selector

Rewards Carousel

Manual Authoring

Alternatively, static pages' content can be populated manually.

Under the Body HTML field it is possible to insert HTML markup that will be rendered almost as-is in the context of a static page. Additionally, Custom CSS allows to set style definitions that can be applied to the custom HTML.

Using HTML and CSS is considered an advanced feature that can have unintended consequences on the rest of the site.

It’s strongly discouraged to:

  • Use html, body, head, script, iframe with onload="javascript:", or any other tags that might alter the behavior of the rest of the site.

  • Using CSS properties that alter the layout of the main site, e.g. fixed/absolute positioned elements.

Please handle this with care!

Special Variables

When manually authoring pages, it’s possible to inject some dynamic content via placeholders. The placeholders take the {{ placeholder-name }} form.

  • Current application language can be referenced as {{{LANG}}}

  • Variables from URL query strings can be referenced as {{{parameterName}}}
    e.g. https://market.tld/en/test-static-page?someKey=someValue → {{{someKey}}}

Additional Configuration

SEO

Static pages allow for custom metadata and configuration to be set for SEO purposes.

To learn more about all the SEO capabilities, please head to SEO (Search Engine Optimization).

User Acceptance

When the Requires User Acceptance toggle is enable, the static page will be treated as a document signed in users will need to review and accept before using the site. This is useful when willing to have users agree legally-binding documents such as Terms of Service or Privacy Policy pages.

To learn more about this feature, please head to Feature Agreements.

TBD: Redirect URL

redirectUrl

list-of-links: when present, it takes precedence over path.

  • No labels