> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/media/media_menuboards.md).

# Menu Boards

The Menu Boards interface provides a simple way for users to create and manage 'categories' and 'product' information independently to Layouts.

Once created, Menu Board data can be added anywhere on a Layout using Elements from the Menu Board: Category and Menu Board: Products Widgets available in the Layout Editor.

{% hint style="danger" %}
Menu Board Widgets are not available to add to a Playlist!
{% endhint %}

## Overview

* Create and define Categories
* Include detailed product information
* Select Images to use from your Library
* Maintain content without accessing Layouts
* Re-use across multiple Widgets/Layouts

Menu Boards are created and managed independently to Layouts and therefore do not require user access to Layouts or the Layout Editor to add or manage categories/product data held within a Menu Board.

## Creating a Menu Board

Menu Boards are created and managed by selecting **Menu Boards** under the **Library** section of the main CMS menu:

1. Select the **Add Menu Board** button and complete the form fields to create a new record
2. Give your Menu Board a **Name** for easy identification in the CMS. Provide an optional internal **Description** and enter a **Code** if referencing this Menu Board via the API
3. Click to **Save**

## Create and Configure Categories

Categories define the structure of your data:

1. Use the row menu for a Menu Board record and select **View Categories**
2. Click on the **Add Category** button and complete the required form fields
3. Click **Next** to repeat this process to add the required **Categories** for the Menu Board

Select **Save** when entering the last Category to use.

{% hint style="info" %}
**Code** is for advanced use when referencing the API.
{% endhint %}

## Add Products

Product data is added to Categories to provide all key information which can be selected to be shown on Displays.

1. Use the row menu for a Category and select **View Products**
2. Create new Product data by clicking the **Add Product** button and complete all relevant form fields

{% hint style="info" %}
The Menu Boards: Products Widget can be configured to dim products that are marked as unavailable to show on Displays.
{% endhint %}

### Product Options

Use this tab to provide further product options.

{% hint style="success" %}
Use Options to provide special offers, limited deals etc for this particular product.
{% endhint %}

Repeat the process to add further Products/Product Options to the Category.

Menu Board data is added to Layouts using the Menu Board: Category Widget which has data elements which are primarily used to add 'header' information and the Menu Board: Products Widget which allows for precise placement of Product details on Layouts.

{% hint style="success" %}
Menu Boards are edited independently to Layouts, so there is no need to access or edit the Layout(s) the Menu Board has been added to. Changes will be available in the system straight away ready to be picked up by Players on their next collection, with no need to make any edits to Layouts! 
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xibosignage.com/media/media_menuboards.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.