Core Concepts

Before you start using LexasCMS, it is useful to understand some of the core concepts and terminology that you will come across.


A user is anyone that has an account and they can be a part of multiple organisations. After creating an account, a user can either create their own organisation or be invited into an existing one.


An organisation is the billable entity to which users and spaces can be added. When a space is created, it is both linked and billed to the organisation that it was created within.

When a user is added to an organisation, they are given a role that dictates which actions they can perform and the information they can see within that organisation.

The available user roles are described below:

  • Admin - Capable of performing any action within an organisation including creating and deleting spaces, managing billing information and managing content.
  • Editor - Limited to managing the content for all spaces within an organisation. Editors cannot manage a spaces content model.


A space acts as a container for your content and is created within an organisation. Creating multiple spaces allows you to separate your content depending on your project’s needs.

You can create as many spaces as you need within an organisation.

Content Model

A content model defines the structure of the content that is contained within a space and consists of locales and content types.

Locales allow you to define the languages that your content can be translated into. A space can either have one locale or multiple depending on your requirements.

Content types are the main building blocks for your content. They define the specific types of content (e.g. Articles, Promotions etc.) that can be created within your space and the fields that those pieces of content are comprised of.

Components are a special variety of content type which, amongst other benefits, provide a vastly improved interface for working with dynamic content structures. For more details, please see the components documentation.

For more information about modelling content, click here.

Content Item

A content item is an entry of content that has been created within a space. They are created using one of the content types defined in the space’s content model and contain one or more variations.

See below for more information about variations.


A variation can be seen as an instance of a particular content item. Content items are composed of one or more variations and it is in the variations where your content is stored.

Each variation can be targetted at a specific audience and can also be independently scheduled to become active and expire. Variations are also sorted by priority to control what should happen in the event that multiple variations are active simultaneously.

Very simple use cases may only require content items to contain one variation, whereas more advanced use cases–such as those where content is personalised or multiple content changes are planned in advance–will require multiple variations to be created.

These features work in tandem to make variations an incredibly powerful concept which enables you to control exactly what content each of your visitors should see at any point in time.


Audiences provide a method of grouping visitors based on their individual characteristics. These audiences can then be used to control and tailor the content that each of your visitors see.

An individual audience is essentially a set of conditions which determine whether or not the current visitor is apart of that audience. Each condition within an audience is based on either a single or a combination of audience attributes.

When requesting content from LexasCMS, you simply provide some contextual information about the visitor making the request, and let LexasCMS calculate which audiences they belong to.

Audience Attribute

Audience attributes enable you to define the specific characteristics which can be used when configuring an audiences conditions.

For example, if you wanted to create an audience which was based on a visitors age and location, you would need two audience attributes. The first being a number attribute for the visitors age, and the second being a text attribute for the visitors location.

Integrates with your favourite tools and frameworks

© 2022 Status200 Ltd.