Pages

Pages are one of the core asset types in Cascade CMS. They represent the grouping of template, content, blocks, and more that a user publishes to the web. Essentially, your ‘page’ becomes a new web page.

Introduction

Pages are one of the core asset types in Cascade CMS. They represent the grouping of template, content, blocks, and more that a user publishes to the web. Essentially, your ‘page’ becomes a new web page.

Pages can represent many different types of content on a website such as frequently asked questions (FAQs), newsletters, press releases, employee profiles, news articles, or anything else you might find online.

Cascade CMS can also index pages to dynamically generate navigation link menus, site maps, RSS feeds, and more.

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.
    • By default, the page types available in your current site are displayed, but you can use the drop-down menu to select a page type from another site.
  3. In the Page Name field, enter a name for your page.
    • Note that this name becomes the system name of the page within Cascade, and ultimately it will become part of the page's URL, so it's best to keep it short and simple. 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.
  5. Depending on the page type chosen, you may see either pre-defined content fields to fill out (a Data Definition) or simple a WYSIWYG content editor.
  6. In the Metadata tab, enter any necessary information in the Metadata Fields for your page (title, description, etc.).
  7. In the Configure tab, configure the following fields:
    • Include when indexing - Enable this if it's a page that will need to be included in an Index Block. For example, an Index Block being used to create a dynamic navigation menu could include information about this page.
    • Include when publishing - Enable this if it's a page that will need to be published to the web server.
    • Maintain absolute links when rewriting - Enable this if you need to keep absolute links in your page when rewriting.
  8. Click Preview Draft and then Submit when you're finished previewing your new page.

Previewing a Page

Pages can be previewed before publishing to allow users to see how the page will look as rendered in Cascade CMS, but without additional elements such as region indicators.

To view a full screen preview of your page in a new tab or window, select More > Full Screen Preview.

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 view is generated by combining the Site URL specified in Site Settings, the page's path, and the page's extension as specified in its output. For example: If the current Site URL is http://example.com, the page's path is /news/index and the selected output's extension is .html; then the resulting URL of the live view would be http://example.com/news/index.html.

The live view is useful as an easy way to check:

  • If the page was published successfully.
  • If it was published to the correct location. This is assuming that the Site URL is correct.
  • If the cross-site links pointing to this page will be correctly rewritten. The exact same URL will be used if a page from another site points to the current page. Therefore, if the page is published but does not render in the live page, it means that cross-site links pointing to this page will not work either.
  • How the page looks when retrieved from the web server. You can make sure that all the images, CSS, and JavaScript files were published correctly by quickly examining the live page.
  • If the links in the page were correctly rewritten during publishing. In some cases clicking on the links inside of the live page is a more reliable way of making sure they are not broken than viewing a publish report.
  • If [ system-view:internal ] and [ system-view:external ] tags work correctly. Content inside of [ system-view:internal ] tags should be rendered inside Cascade CMS while content inside of [ system-view:external ] tag should be rendered in the live page.
  • If server side scripting executes correctly. This is only in regards to pages that render server side code, like PHP, ASP, etc. While page inside Cascade CMS should display the code itself, the live page should display a result of execution of that code.

If you cannot see the live page, first confirm that the page was successfully published. If the page was published, here are possible reasons why the page is not displaying:

  • The selected output is not publishable or was not published in the past. The Publishable property can be toggled inside of the Configuration the page uses. Confirm that the selected Configuration has been published.
  • The page has been moved or renamed inside Cascade CMS. If this is the case, the page needs to be published again to the new location.
  • The Site URL is incorrect. The Site URL property can be updated in Manage Site > Site Settings.
  • The page publishes to a Database Transport only. If a page publishes to a Database Transport only, it is likely the page's content is used in a server-side application with a different URL. If this is the case, the URL generated for the live view will be invalid. 
  • The page has been published to a location you do not have access to. Verify with your network administrator or the web server administrator that you have access to the published location. The page can be blocked from the web server's side or by a firewall.