webCOMAND Apps and APIs use Bases —databases geared for working with content in the cloud.

Bases make it easier to:

  • Model - Define fields and behaviors to streamline working with specific content types.
  • Organize - Manage content folders, tags, hierarchies, taxonomies, links and variants.
  • Collaborate - Facilitate teams to work on content together effectively.
  • Search - Find content by keyword and facets.
  • Query - Find content based on content state, context, metadata and field values.
  • Integrate - Build and connect apps and systems using robust, well documented APIs.


Each content item in a Base is associated with a content type that defines the fields and behaviors common to all content of the same type.  This helps streamline workflows, improve consistency and reusability, enforce constraints and script repeatable processes.

  • Fields - Structure content for consistency and reusability.
  • Behaviors - Script content creation templates, validations, custom workflows and more.
  • Inheritance - Content types can inherit the fields and behaviors of other content types to efficiently define and evolve shared content structures and behaviours.


A Base organizes content similar to a traditional database, with types (aka tables), fields (aka columns) and relationships (aka foreign keys).  However, Bases formalize a organizational constructs to make it easier to organize, access and query content more effectively.

  • Folders - A familiar way to group, organize, access and query content based on its location(s) in a hierarchy.  The database, query languages and API are all optimized to work with folders and paths.  User access control, version control, publication settings and workflows, can all be applied to a folder hierarchy making it easier to apply each to logical sets of content.
  • Hierarchies - Any content type can enable hierarchical organization with the definition of a child/parent relationship.
  • Taxonomies - Any number of tags, taxonomies and other organization structures can be applied to content internally or externally to content.
  • Variants - Maintain content variations for language translations, market segments, etc.


  • Workflow - Content can exist in multiple states, such as working version, saved drafts and approved/published.
  • Locking - Obtain content- and field-specific locks to prevent users and apps from stepping on each others toes.
  • Revisions - Record updates as content evolves over time, for reference and rollback.
  • Audit Trail - Log who creates, modifies and accesses content and when.
  • Authorizations - Control access to content and features based on user authorizations.


Find content by keyword and facets.  Facets can be based on any content information that can be queried with the query language.

  • Keyword Search - Search by keywords within a specific type or other content subset, or across the entire Base.
  • Faceted Search - Predefined facets can be searched from the UI or free-form queries can be included along with the keyword search.


Request content by type, folder, variant, workflow state, revision, point-in-time and field values, with functions, expressions and aggregation support.


Plays well with others.  Integrate with apps, internal and external data sources.

  • Locking - Obtain content- and field-specific locks to prevent users and apps from stepping on each others toes.
  • Transactions - Safely batch queries and updates in single atomic transactions.
  • Temporal - Query a Base as it existed at a specific point in time.

A Base is similar to an object-relational database because content is object-oriented and content fields form relationships. 

To learn more about Content Databases, see our blog post, What is a Content Database.