Terminology

Blueprint

A blueprint defines the layout of the experience and what areas (i.e. Placements) within are editable.

Business Capability

Atama introduces a couple layers of abstraction in order to avoid point-to-point integrations and make lifecycle management easier for large systems. One of those abstractions are business capabilities. They serve as a normalized schema for APIs (i.e. source capabilities) provided by 3rd party services (i.e. providers).

Business Capability Bundle

A business capability bundle logically groups one or more business capabilities. For example, you may want to group all your marketing capabilities into one bundle and your commerce ones in a separate one.

Channel

Examples: web, mobile, email, signage, IoT.

Component

A component is a block within an experience for a specific channel (web, email, etc.). The component type defines what data the code is expecting and how business capabilities map to it.

Experience

An experience is an interaction between your organization and a user (customer, partner or employee). It can target one or more channels.

Placement

A placement is an area within a blueprint that's been identified as being authorable. It also defines what components are allowed within it.

Provider

Providers connect Atama to source systems via APIs and make their source capabilities (e.g. content, data, actions) available for Composer to use.

Publisher

Publishers are associated with channels and make sure that the data gets to the channel in the right format.

Source Capabilities

A source capability can be any type of content, data, or action that's made available to Atama via a provider.

Workspace

Workspaces are used to logically separate brands, business units, or even projects. Most of the marketer's day-to-day work of creating experiences etc. happens in a workspace.