Overview
CMS has a lot of potential for crafting various content pages and micro sites. Some ideas may be: current promotions highlights, company information pages, information on delivery process, ordering and processing returns, and even image galleries and slide shows. Content body can include any text, images, links and forms that are rendered as part of the page. Therefore is is possible to display data and capture it using external services such as Google forms to get feedback, conduct polls etc.
Default theme implementation provides the following template variations in order to render category view:
Template variation | Condition | Notes |
---|---|---|
include | Content which cannot be accessed via public URL. Used to defined content elements to be included in other content pages or page templates | |
content | Basic content template provides a "category page" style template where middle section is filled by content from content object as is. | |
dynocontent | Advanced content template uses similar layout as "content" however the body is treated as dynamic template written in Groovy. Default variables passed to context are "shoppingCart" (see ShoppingCart), "shop" (see Shop) and "datetime" (current timestamp) |
Content page
Annotations
Element | Template | Configurations1 | Content include2 | Description |
---|---|---|---|---|
C.1 Content page body | Category page body | |||
F.1 Footer | Standard footer | This component is described in Home page documentation | ||
H.1 Header | Standard header | This component is described in Home page documentation | ||
M.1 Breadcrumbs | Breadcrumbs | Automatically resolves current breadcrumbs path depending on the URI | ||
M.2 Content navigation | Top categories | Displays current menu depending on current content selected. For leaf content menu highlights its position, for content with sub categories its menu is displayed. | ||
P.1 Featured products | This component is described in Home page documentation | |||
P.2 Product tabs | This component is described in Home page documentation |
1Configurations refer to shop and category custom attributes that define behaviour of components
2Content include refers to shop URI suffix for content. For example if shop has code "SHOP10" and content include is specified as "custom_content" then URI of the content include that will be rendered is "SHOP10_custom_content"