Glossary & Reference Links

By Customer Success Managers
April 18, 2015
Terminology (Jump to Links)
  • ACL
    • Access control for viewing, editing, publishing, and configuration options.
  • API
    • Application Programming Interface
  • Asset
    • Any file or folder in the CMS
    • There are two main kinds of assets:
      • Templated Asset
        • Assets that have a template applied to them to manage I/O.
        • Includes assets that will be published as site pages and configuration assets used to store settings.
      • Digital Asset
        • Also called a Binary asset, is composed of uploaded data like an image or pdf.
  • Branching
    • Branching creates a related copy or "branch" of an asset, allowing you to manage separate versions of it in different workflow states and better manage revisions of live pages. The CMS intelligently tracks and updates links to branches as they are promoted through workflow.
  • Content
    • Data stored in an asset.
  • CMS
    • Content Management System, a system for managing your web site's content.
  • Dependency
    • Content interconnections between published templated assets in your CMS, for instance, between a press release index and individual press release pages, or between images assets displayed on a page and the page that contains them.
  • Dev Server / Stage Server / Live Server
    • An external web server where the CMS is configured to publish files.
  • Edit
    • Edit a configuration, content, or page in the CMS.
  • Model
    • A group of assets with assigned templates, workflow and access that gives a structure or blueprint for new content creation.  Folders are assigned models to define their options for new content creation available in the "new" menu.
  • Navigation Wrapper
    • A template similar to master page in .NET.  Shared content, like site header and footer, is embedded in the template and referenced in all other site templates to wrap around template output.
  • Package (Publishing Package)
    • One of the steps required to configure publishing. Defines a connection between FTP server settings and a workflow state. 
    • To set up publishing, you must define an FTP location and then define a package that points to the FTP location.  With those set, workflows and publishing properties must be configured to publish using that package.
  • Preview
    • Viewing assets inside of the CMS's built in browse. Preview shows the entered asset's current content as rendered by the asset's assigned template.
  • Publish
    • Rendering an asset into a file or files following it's assigned template and publishing package(s) then transferring the file(s) via SFTP to an external web server for review (on servers with restricted access) or public view (on public-facing web servers). 
  • Publishing Package
    • Defines a connection between FTP server settings and a workflow state.
  • Publishing Properties 
    • Configuration settings available on all folders and the assets in the CMS for linking publishing packages, template layouts (defaulting to "output") and setting publishing locations and names.  
    • Generally set on a high level in the folder structure, publishing properties are then inherited from parent folders.
  • State
    • (Workflow State)A milestone within a workflow, also called a "Status".
  • Workflow
    • Defines the states and commands available to users to move content through the content creation process and to a published environment.
  • Workflow Command
    • A defined transition between workflow states or to redeploy/refresh content in its current state. 

CP Terminology (Developers)

  • Context (for developers)
    • Methods, data, and properties particular to the environment.
  • Library Files (for developers)
    • Reusable code functions not tied to specific template functions.
  • Template (for developers)
    • A collection of template files in a folder that provide code to manage the input form and output behavior (including preview rendering and publishing) and business logic of a templated asset.  Template code is a mix of Crownpeak's C#-based API and web languages such as HTML and CSS.


  • Getting Started in Crownpeak CMS
    • Links to downloads required for CMS to function properly
  • C# API
    • C# API documentation
    • WCO API documentation
Tags:  wiki
comments powered by Disqus