Table of Contents

Pages

Creating a content structure in DynamicWeb 10 CMS

Pages are default building blocks primarily used for two things:

  • To define the content structure of a website
  • To act as containers for content coming from paragraphs

As an editor, you interact with pages via the content area tree. You can use the plus-button as well as the page context menu to add and interact with pages.

Pages

When you click on a page, the workspace will show the page content in either list view or visual editor mode, depending on the design. You can then create and edit content using either of these modes.

Page Settings

Pages are rich objects with lots of settings for tweaking or configuring page behaviour, accessible from the page context menu or via the Settings-button in Visual Editor mode. The page settings are organized into tabs of related settings, you can read more about each tab below.

General

The General-tab is either very important or not at all important, depending on the website design. If the design does not use items to extend page settings, the only thing on this tab is the Page title field. GeneralTab1 On the other hand, if the design does use an item type to extend page settings (via the Advanced-tab for the website), this tab also contains the fields from this item type. This is extensively used in DynamicWeb Swift. GeneralTab1

Layout

The Layout-tab contains settings related to the page layout, which is to say the template used to render page content. LayoutTab The following settings are available:

Setting Use Notes
Select template Select a page-layout for this page Only layouts from the design are available. If a default page layout is specified in the website settings for this page or item type, this is only used to override that selection.
Inherit to subpages Check to make all subpages use the layout selected above
Select content type Set a custom HTTP header content-type for this page This is typically used to when publishing data in a feed of some sort
Assign tree Section Assigns the page to a specific section in the content tree If the section hasn't been used before, it is created

Section

SEO

The SEO-tab contains search engine optimization related settings, chiefly for adding metadata and tweaking URLs: SEOTab The following settings are available:

Section Setting Use Notes
Meta Meta title Set the title tag
Description Set the meta description
Keyword(s) Set meta keywords Not in use by Google since 2009
Google preview Displays a preview of meta information
Noindex Check to set noindex on page Used to exclude a page from being indexed by search engines (if they respect the tag)
Nofollow Check to set nofollow on page Used to ask crawlers not to follow links on this page
404 for detected robots Check to present a 404-page to visitors identified as robots Based on user-agent
Canonical Set the canonical url for this page
Image Set the image for this page Useful when sharing pages on social media, as this image will be attached
URL URL Displays the auto-generated URL for this page See Customized URLs
Use in URL Specify a custom URL for this page Illegal characters are: '+', '?', '#', '%', ':', ';', '|', '<', '>', '*' ,' '(two whitespaces) ,'""' (two doublequotes). This setting depends on the url index being rebuilt, which can take a while, especially on solutions with many products or pages.
Do not include URL in subpage URLs Check to allow URLs to be trimmed by ignoring the parent page part of the URL in the subpage URL. You can use this if you don´t want the parent page name in the URL for the subpage, e.g. 'www.yourdomain.dk/Frontpage/subpage.aspx' is changed to 'www.yourdomain.dk/subpage'.aspx
Exact URL for this page Specify an exact url for this page E.g. without an extension or with a different extension, a different name, a specific path etc. The content in this field overrules the whole URL (after yourdomain.com/) for the current page. It does not have an effect on the subpage URLs.
URL Provider Select and configure an URL Provider

Publication

The Publication-tab contains settings typically used by implementers to control which pages to show in a navigation, etc. These settings don't do anything by themselves, but they are available in templates for front-enders to use. PublicationTab The following settings are available:

Setting Use Notes
Publish state Switch between publish states Published, Hide in menu, Unpublished The default publish state can be changed from the Interface settings
Publication period from/to Specify when the page will be published/unpublished
Clickable -
Show in breadcrumb trail -
Display ‘last update’ -
Show in searches -
Show in sitemap -
Hide for mobile - Legacy
Hide for tablets - Legacy
Hide for desktops - Legacy
Shortcut Create a shortcut to another page

Advanced

The Advanced-tab contains a hodgepodge of settings for advanced scenarios. AdvancedTab From the advanced tab you can:

Setting Use Notes
Navigation tag Sets the navigation tag for the page Developers have access to this tag in frontend and can use it to e.g. switch between navigation templates
Show this page in frontend Decides if access should be granted "For all users" or "Only for users with access to this page"
Login template Select a template for login
Https Overrides the HTTP configuration set up at website level
Lock language versions Locks all language versions of this page Only works if you've configured the language management settings to allow page content to differ from master content
List sub pages Shows all subpages to this page in list-like view instead of in the content tree It is not possible to use Visual Editor on the page if "List sub pages" is checked
Item type Changes the page item type
Select workflow To select a content workflow for this page

Ecommerce

The Ecommerce-tab allows you to set up Ecommerce navigation on this page. This adds channel groups to the collection of navigation nodes being generated for this page. AdvancedTab To set up Ecommerce navigation:

  • Check Ecommerce navigation
  • Select a parent group – groups or shop. If group choose between specific groups or all groups
  • Select a shop
  • Check Include products to add each product as a node in the navigation
  • Set the max levels to include – this is how deep you want the navigation to be
  • Specify a product page – this should point to a page with a product catalog used to render the product list

In many cases - e.g. on Swift-solutions - this functionality has been replaced by the Ecommerce URL Provider

To top