Glossary of Terms
Following is a selection of terms from Hannon Hill’s Knowledge Database. A full set of terms can be viewed at http://www.hannonhill.com/new-kb/glossary.html
AssetsAn Asset is any entity within the system that can be used to generate content. Many different types of entities can be assets: images, CSS stylesheets, XML blocks, pages, and more. For ease of classification, assets are divided into several different groups:
- Page - This is a mutable asset built by the CMS from other assets to create the finished product of published documents such as web pages or XML documents.
- File - may be a jpeg image, CSS file, or any other indivisible and immutable asset.
- Block - a "pluggable " piece of content that can be easily substituted, with or without styling, into any page region. As the name suggests, these are the building blocks from which other blocks and pages are built.
- Format- used to transform and style data, such as an XML block
- External Link - a symbolic link to a specific URL
- Folder - a container within Cascade that acts a parent asset to other assets.
- Template - the basic building block for a page's layout.
- Reference - a special asset that is created to represent an existing asset in another location, allowing it to be indexed in multiple folders.
BlockA Block is a 'pluggable' piece of content that can be easily substituted (with or without styling) into any page region. Therefore, whenever there is content that is common to many pages or regions, i.e. an “About the Company” section that appears after every press release and newsletter, that content should be put into a block. Doing so allows the appropriate content to appear in many pages while always being updated from one place, making it easy to maintain consistency in that text/markup across many pages. Cascade users can reuse a single block on an unlimited amount of page regions.
The text or markup contained by a block can be plugged into a page region at three different levels: the template level, the page configuration level, or the page level. When a block is plugged into a page region at the template level, the block content will appear in any pages using that template. Any blocks assigned at the page configuration level will appear in any pages using that configuration.
There are five types of Blocks in Cascade Server:
- Index Block - used to dynamically generate system assets as XML
- Text Block - static text content
- XML Block- static XML content
- XHTML Block - static XHTML content
- XML Feed Block - dynamic XML from a third-party server (e.g. RSS feed)
BreadcrumbsBreadcrumbs are a type of Dynamic Navigation typically used for every page except the home page. By showing a backwards pathway from the current page back to the home page, breadcrumbs ensure that users know where they are and how they got there.
KeywordsKeywords are part of the metadata content for pages, files, folders, blocks and external links, and are used by search engines to determine the relevancy of individual pages or sites. Typically, keywords are a comma-delimited list of words used on pages and generated in such a way that the page can receive higher points in a search engine query.
MetadataMetadata is data within the CMS that describes an asset. Common fields such as title, summary, or keywords provide quick information about the content contained inside of a particular asset. Because the system manages all assets as XML, the metadata that a user enters for assets can be used for display purposes on site pages. When used in conjunction with index blocks, an XSLT format can be applied to the metadata to create common HTML content listings such as a listing of recent press releases including the title and a quick summary of the press release content. Cascade Server uses two types of metadata – wired and dynamic.
TemplateA Template is a fundamental system entity that defines the HTML/XML structure of page asset in the CMS. Templates are essentially XHTML documents that contain standard HTML tags and CSS that create what is commonly referred to as the "look and feel" of a web page.
WorkflowWhen creating web content (a page, file, image, etc.), a workflow is a series of ordered steps that the content must go through to be quality-checked, and either approved, modified, or disapproved by the appropriate user (an approver) before being publish-ready. Workflows can be customized or created from scratch. Workflows provide Cascade Server users with a customizable, assignable method of assuring that content (any asset) is checked multiple times by multiple users before being published. The resulting diversity of input ensures that content is accurate and presented in a professional manner.
All users may initiate a workflow when creating or editing content. Users assume different roles in the workflow process according to their system role. A higher-level user, such as an Approver, reviews the content, and either approves it to be sent to the next step in the workflow, or returns it to the user associated with the previous step for changes. After the content has been approved by all users in the process, a Publisher may then publish the content to a live site. Managers and Administrators have the capability to bypass any of these steps anywhere in the workflow process.
WYSIWYGWYSIWYG is an acronym for “What You See Is What You Get.” Cascade’s word processing functionality is referred to as the WYSIWYG editor because as its name implies, it allows you to see formatting while editing in your content in the word processor (much like Microsoft Word®).
The word processor, which is integrated in the CMS system, has the same functionality and features you are most likely accustomed to using in a standard editor (such as Microsoft Word).