System Pseudo-Tags


System pseudo-tags are special system tags that instruct Cascade CMS to act on the content contained within them. System pseudo-tags are not XML elements but instead use a square bracket notation.

System View Internal

This tag surrounds content to be displayed inside the system only. It can be used for paths or blocks of code that need to be present upon rendering within the system, but not necessarily when published out of Cascade CMS.

[system-view:internal]This appears inside Cascade.[/system-view:internal]


  • Generating a message for users in Cascade CMS displaying when the last published date occurred.
  • Simulating an area of a page where some server-side scripting code will exist when the page is published.

System View External

This tag surrounds content to be displayed outside the system only. It can be used for paths or blocks of code that need to be present upon publishing, but not necessarily when viewed within Cascade CMS.

[system-view:external]This appears outside Cascade.[/system-view:external]


  • Wrap around web analytics JavaScript so it only tracks traffic on the published page.
  • Wrap around server-side includes, since they'll only work outside of Cascade CMS.

System CDATA

XML's CDATA section instructs the XML parser to ignore whatever content is inside of it. This results in the content being treated strictly as character data instead of markup.


In the following example:

function matchwo(a,b) 
if (a < b && a < 0) then 
  return 1; 
  return 0; 
the < and & characters, if not wrapped in a CDATA section, would generate a parser error because they indicate the start of an element and the start of a character entity respectively. When applying formats to page content, CDATA sections in the content are often interpreted and then removed from the resulting XML. The Cascade CMS CDATA tags are used to ensure that the CDATA section makes it into the page content that is output when rendered inside the system and when published.

This is useful when generating RSS feeds, for example, as the feed itself should contain CDATA sections to instruct the feed readers to interpret the content within the sections as character data.