---
title: "Lookbooks"
canonical: "https://red-ant-documentation.refined.site/space/RET/33914888/Lookbooks"
format: markdown
---
> Macro (toc)
## Overview
“Looksbooks” or “Inspirations” is a dedicated area within RetailOS that enables retailers to house curated looks, using a combination of campaign imagery and products from the catalog.
They can provide a visual representation of a particular style, concept, or vision using visual elements that convey the desired aesthetic or mood.
Sales associates can share looks with customers via [Email](https://redantdigital.atlassian.net/wiki/spaces/RET/pages/228032537) or [SMS](https://redantdigital.atlassian.net/wiki/spaces/RET/pages/240222233) to create a more personalised relationship. Looks can also be showcased during a consultation, with the aim to encourage the customer to ‘shop the look’ by adding the products from the look to their basket.
## Search & Filter Inspirations
As standard, the search will run across a sub-set of the most relevant Inspiration data fields (see below), however, we can extend this to run over additional fields where required.
| **Field** | **Definition** |
| --- | --- |
| `title` | The name of the inspiration as displayed to the customer. |
| `description` | A short description of the inspiration. |
Each inspiration can be assigned one or many tags which can be used to filter the list of results. Simply select a tag from the dropdown or select the tag beneath an inspiration to apply the filter.
### View Inspiration
Selecting an inspiration will open the inspiration detail page. An inspiration can be made up of:
- One or many look images
- Inspiration title
- Inspiration tag(s)
- Inspiration summary
- Inspiration detail
- Look products
#### Customer Mode
If the sales associate wants to hand the device to the customer to view the inspirations, they can place the app in **“Customer Mode” **which allows customers to temporarily view the Inspirations securely, without access to other sections of the app.
To exit customer mode, the sales associate can select **“Colleague mode” **in the top left corner. Exiting **“Customer Mode”** requires the staff member to re-enter their password to authenticate and regain full control of the application.
### Send Inspiration
Sales associates can select to send the inspiration and its associated products to a customer via Email or SMS (subject to the customer's communication opt-ins)
### Add to consultation
During a consultation, sales associates have the option to add all products associated with an inspiration into the consultation.
### Delete inspiration
Only Admins have the option to delete Inspirations from the application.
## Managing Inspirations
RetailOS is pre-integrated with [Contentful](https://www.contentful.com/) CMS which is used to create and manage the Inspiration content.
### **Contentful**
Contentful is a headless CMS. Effectively that means it's a back-end-only content management system that acts primarily as a content repository. The content is accessible via a delivery API for display on any device, without the need for a built-in front-end or presentation layer.
It's a multichannel solution for publishing dynamic content across a variety of platforms and devices.
There are a number of benefits to using Contentful;
- Publish changes in real-time
- It’s easy to add new fields into your content models and customise components within the CMS
- You can apply custom field validation to ensure only valid content is created
- We can utilise tooltips/help text on the fields to explain their purpose
- It has built-in support for localisation should you require it
#### Environments
Space environments are entities within a space that allow you to create and maintain multiple versions of the space-specific data, and make changes to them in isolation.
By default, every space has one environment, called master. Additionally, multiple sandbox environments (QA/UAT) can be created. Sandbox environments start out as exact copies of the master environment. Environments are made up of the content model, content, and media.
#### Content Model
A content model gives structure and organisation for the content.
#### Content Type
Within the overall content model, we have individual content types. You can think of each content type as an outline for your content; it tells you what data will be contained within each individual entry and it tells the APIs what kind of content to send to our application.
Inspirations can be created using the following content types:
1. **Inspirations - **This content type is used to create an individual inspiration
2. **Inspirations - Tag - **This content type is used to create inspiration tags that can be associated with the individual inspiration
##### Content Fields
Each content type comprises of fields that denote the type of data that will be included in the entry. For example, the title of the inspiration would have its own text field and the description would have another.
Below is a list of the content fields for the two content types, including a definition for each field:
Inspirations
| **Field** | **Definition** |
| --- | --- |
| Name* | The name of the inspiration as it appears to the customer. |
| Tag(s)* | Used to associate the inspiration to one or many of the ‘Inspiration - Tags’. |
| Region* | Used to associate the inspiration to a region. This will make the inspiration available to all stores associated with the region. |
| Summary* | A short description of the inspiration. |
| Details* | A longer description of the inspiration which will display under the ‘Details’ tab. Supports basic WYSIWYG formatting. |
| Campaign Image* | The inspiration hero image. |
| Product Barcode(s) | Associate one or many products to the inspiration. You must enter the EANs as a comma-seperated list. Products will then display under the ‘Look Products’ tab. |
*Mandatory field
Inspiration - Tag
| **Field** | **Definition** |
| --- | --- |
| Label* | The name of the tag as it appears to the customer. |
*Mandatory field