Pages
Table of Contents
Simple web pages can be created by the Site admin.
Page has
- name, i.e. slug
- localized title
- localized content.
The Page slug is unique within a Site and may only contain lowercase letters a-z, numbers and dashes, since it is used in URL. The title is plain text and editable. The content of the Page is HTML and can be edited with a WYSIWYG editor.
When a page has been created in Manager, it is accessible in Shop via URL /pages/:name e.g. /pages/about-this. Note that a non-active page won't be visible in the Shop.
For every Shop, a predefined set of default pages are created
- privacy-policy
- terms-of-use
- contact
These can always be reset back to the default title and content with "Reset page". Reset will affect all locales of the Page.
Variables
Variables can be used in the Page title and content.
A variable is added in double-braces, e.g. {{company.name}}. See list of available variables below:
| Variable Name | Where the Value comes from |
|---|---|
| company.name | Preference: COMPANY_NAME |
| company.email | Preference: COMPANY_EMAIL |
| company.address | Preference: COMPANY_ADDRESS |
| company.zipcode | Preference: COMPANY_ZIP_CODE |
| company.city | Preference: COMPANY_CITY |
| company.country | Preference: COMPANY_COUNTRY |
| company.phone | Preference: COMPANY_PHONE |
| company.site.url | Preference: COMPANY_SITE_URL |
| company.logo.url | Preference: COMPANY_LOGO_URL |
| company.vat.id | Preference: COMPANY_VAT_ID |
| site.name | Site name. My Shop |
| site.domain | Site domain. ex. my-shop.saas.pilvi.com |
| user.email | User email when the user is logged in |
Side menu links
Side menu links may be added for privacy-policy, terms-of-use and contact Pages.
See Preferences starting with FRONTEND_SIDEMENU_LINK_.
System Pages
Many System Pages can be customized by the Site admin. For example Product Detail, Product Configure, Login, Register, and Cart pages are supported. Each System Page can have several System Page Blocks, typically a Top and a Bottom block. The Top block is located just below the header and the Bottom block below the other content.
The contents of the System Page Blocks can be edited in Manager as localized WYSIWYG fields.
Default contents
Some of the System Page Blocks have default contents. These contents can be edited similarly to any block.
System Page Variables
Variables can be used in System Page Blocks in the same way as in Pages. In addition to the Pages variables, System Pages may have page specific variables available. On Product Configure and Product Detail pages the following variables are available:
| Variable Name | Where the Value comes from |
|---|---|
| product.id | The current product ID |
| product.no | The current product number |
| product.name | The current product localized name |
| product.plan | The current product localized plan |
Sections
A System Page Block may contain sections, which visibility depends on the section variable values. The system defines these section variables on some of the System Pages. A section consists of section start, content, and section end. For example:
{{#section.order_fail}}
Oops, something went wrong
{{/section.order_fail}}
The text is included only if variable section.order_fail value is true. Sections may be nested.
Cart Ready page
On this page, when section.order_success is true, the order was received successfully. Only one of the sections inside order_success is true at a time.
| Section (1st level) | Section (2nd level, only one present at a time) |
|---|---|
| section.order_success | section.order_payment_received section.order_payment_invoice section.order_payment_not_needed section.order_payment_fail |
| section.order_failed |
Examples
See the default System Page Block contents, for example Product Configure Top block. For more advanced example, see Cart Ready Top block.
SEO
Pages (excluding System pages) have localized SEO fields such as Title tag, Meta description and Meta Keywords that can be manually set. If not set, Pilvi Platform tries to automatically provide best possible values based on the existing data.