Page assets represent the combination of Template, content, scripts, and/or Formats to produce one or more rendered outputs for publishing.


Page assets represent the combination of Template, content, scripts, and/or Formats to produce one or more rendered outputs for publishing.

Page assets can represent many different types of content on a website such as landing pages, frequently asked questions (FAQs), newsletters, press releases, employee profiles, and other content you might find online. They can also represent and render supporting files or files for machine use such as server side includes, script files, RSS feeds, and site maps.

Creating a page

To create a new page:

  1. Click Add Content > Default > Page or select a pre-configured page Asset Factory, if available.
  2. Choose a Page Type corresponding to the Content Types available, if required.
    • Asset Factories that use a base asset will inherit a Content Type.
    • By default, the Content Types available in your current site are displayed, but you can use the drop-down menu to select a Content Type from another site.
  3. In the Name field, enter a name for your page, if applicable.
    • Some Asset Factories are set up to create the asset name automatically based on the Title you provide, or other metadata.
    • This name becomes the system name of the page within Cascade, and ultimately it will become part of the page's URL, so consider a short and SEO-friendly name. You can choose a longer or more descriptive name for the Title or Display Name of the page further on.
  4. In the Placement Folder field, choose the folder where the page should be created within Cascade, if applicable.
  5. Depending on the page type chosen, you may see either pre-defined content fields to fill out (a Data Definition) or a single WYSIWYG content editor.
  6. Enter any necessary information in the Metadata Fields for your page (Title, Description, etc.), which may be located inline or on the Metadata tab.
  7. In the Configure tab, optionally configure the following fields:
    • Include when indexing - allows the page to be included in Index Blocks.
    • Include when publishing - allows the page to be included in publish jobs.
    • Override the current Site's asset link rewriting behavior for this asset - overrides the Site's default link rewriting behavior for links between assets within the current site in this page.
  8. Click Preview Draft and then Submit when you're finished previewing your new page.

Previewing a page

When creating or editing a page, you can preview your content before publishing:

  • When editing a page, you can click Show Edit Preview to see a preview of your changes alongside the content fields as you make them. The preview will refresh with each update to your Draft.
  • To view a larger preview of your Draft, drag the Edit Preview preview divider to make the preview area larger or click Preview Draft.
  • To view a full screen preview of a page in a new tab or window, select More > Full Screen Preview while viewing the page.

Live view

If your page has been published, you can go directly to the live page on the web by selecting More > Live.

The URL for the Live link is generated by combining the Site URL specified in the Site Settings, the page's path, and the page's extension as specified in its output. For example, if the current Site URL is, the page's path is /news/index, and the selected output's extension is .html; then the resulting URL of the Live link would be

If you're not able to see the live page, first confirm that the page was successfully published. If the page was published, consider the following:

  • Ensure the Site URL is correct under Manage Site > Site Settings > URL.
  • Ensure the selected Output is publishable and has been published. Outputs can be made publishable in the page's Configuration.
  • If the page was moved or renamed inside Cascade CMS, ensure you've republished the page at its new location.
  • If the page publishes to a Database Transport, it's likely the page's content is used in a server-side application with a different URL.
  • If the page was published to a location you don't have access to or is behind a firewall, verify with your network administrator or the web server administrator that you have access to the published location.