> For the complete documentation index, see [llms.txt](https://docs.culinarytrail.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.culinarytrail.eu/guides/units-of-culinary-heritage.md).

# Units of Culinary Heritage

{% hint style="success" %}
**Estimated time: 15 minutes.** All you need is a created account.
{% endhint %}

## Manage Units of Culinary Heritage

Users can contribute to the Culinary Trail Digital Catalogue by creating and managing **Units of Culinary Heritage**. These units may include traditional dishes, recipes, beverages, culinary techniques, traditions, stories, or other forms of culinary heritage connected to a community or region. The catalogue supports the project’s goal of safeguarding and recording traditional recipes, practices, and food-related rituals in the Danube Region.

### Accessing Your Account

After creating an account and signing in, users can access their personal account area through the **My Account** page.

The account dashboard allows users to manage their submitted content, including:

* Culinary Units
* Restaurants
* Trails
* Account details

To manage Units of Culinary Heritage, select **My Culinary Units** from the account menu.

<figure><img src="/files/FWD3qw9O8Ivm7oWqxzvc" alt=""><figcaption></figcaption></figure>

### Viewing Existing Culinary Units

In the **My Culinary Units** section, users can see a list of all Units of Culinary Heritage they have already created.

Each unit is displayed with the following information:

* **Title**
* **Status**
* **Date**
* **Available actions**, such as editing or deleting the unit

Newly submitted units are marked with the status **Pending** until they are reviewed by a Content Manager.

<figure><img src="/files/YpnWECJJh24cV8cvKigb" alt=""><figcaption></figcaption></figure>

### Adding a New Unit

To create a new Unit of Culinary Heritage, click the **Add new Unit** button.

This opens the unit submission form, where users can enter information about the culinary heritage item they want to contribute.

<div align="center"><figure><img src="/files/1c8KvCmw9Y4n3iiGyT9e" alt=""><figcaption></figcaption></figure></div>

### Completing the Unit Submission Form

The submission form is divided into several sections.

<figure><img src="/files/fpsD3m1sW7XMqghElVGO" alt=""><figcaption></figcaption></figure>

The Unit Submission Form is organized into several tabs to make the submission process easier to follow.&#x20;

Each tab contains a specific group of fields related to the selected type of culinary heritage. Users should first complete the Overview tab, then select the appropriate Unit Type.&#x20;

Depending on the selected type, the corresponding tab — Food, Beverage, Technique, or Tradition — becomes available for entering detailed information.&#x20;

The Media tab can be used to add images and video content for the submitted unit.

{% tabs %}
{% tab title="Overview Tab" %}

#### Overview Tab

In the **Overview** tab, users enter the basic information about the unit.

This includes general details such as the unit title, country, project partner, ethnic group information, and other required classification fields.

Fields marked with an asterisk `*` are mandatory and must be completed before the unit can be submitted.

<figure><img src="/files/e3qYMBoDuPfPFVT9joiX" alt=""><figcaption></figcaption></figure>

The user must select a **Unit Type**.

After a unit type is selected, an additional tab becomes available. For example, if the user selects **Food**, the **Food** tab is enabled.

The user should then open this tab and complete the required details related to the selected unit type.

<figure><img src="/files/eo2XptRKFlVPjGxPgjId" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Food Tab" %}

#### Food Tab

If the selected unit type is **Food**, the user should fill in all relevant information about the dish or food item.

This may include descriptive details, ingredients, preparation information, cultural background, and any other required fields provided in the form.

<figure><img src="/files/oK3wxnsulPqFjg7E32lK" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Beverage Tab" %}

#### Beverage Tab

If the selected unit type is **Beverage**, the **Beverage** tab becomes available. In this section, users should provide detailed information about the beverage they are submitting.

Users can enter the type of beverage, its classification, a short description, and information about the preparation process or techniques used. This section should clearly describe the beverage’s cultural, traditional, or local significance, especially if it is connected to a specific community, region, or preparation method.

<figure><img src="/files/W0PtfrrNKgk8yc5rKpBF" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Technique Tab" %}

#### Technique Tab

If the selected unit type is **Technique**, the **Technique** tab becomes available. This section is used to document culinary methods, preparation processes, or traditional kitchen practices.

Users should provide the name of the culinary technique, describe how it is performed, and list any appliances, tools, or equipment used. If the technique includes an innovative, sustainable, or resource-efficient approach, this can be described in the **Identified Frugal Innovation** field.
{% endtab %}

{% tab title="Tradition Tab" %}

#### Tradition Tab

If the selected unit type is **Tradition**, the **Tradition** tab becomes available. This section is intended for documenting culinary customs, rituals, stories, celebrations, or other food-related traditions.

Users should select the type of tradition, enter the name of the culinary tradition, and provide a clear description of its meaning, background, and relevance. The description should explain how the tradition is practiced and why it is important for the local community or cultural heritage.

<figure><img src="/files/CVFEFVAE27Vf23OEi8Ac" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Media Tab" %}

#### Media Tab

In the **Media** tab, users can add visual and multimedia content for the unit.

Users can:

* Add a video URL, such as a YouTube link
* Upload additional gallery images

Gallery images are displayed under the unit description and help present the culinary item more clearly in the Digital Catalogue.

<figure><img src="/files/uRk1zQi1gIniSl779mRZ" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

{% hint style="warning" %}

#### Common Fields in All Unit Forms

Several fields appear across all unit types, including **Location**, **Geolocation**, and **References**.

The **Location** field should be used to enter the city or place connected to the submitted unit. This may be the location of a restaurant, producer, local community, event, or other place where the dish, beverage, technique, or tradition can be experienced.

The **Geolocation** field can be used to enter latitude and longitude coordinates, helping to place the unit accurately on a map.

The **References** field should include any relevant sources, such as a restaurant website, official webpage, publication, article, or other link that provides additional information about the submitted unit.

***Based on the References data, the Content Manager creates a new Restaurant and saves it to the Database. It is very important that Content manager also goes to the Unit's details and connects it to the newly created restaurant (this is done in the wordpress dashboard).***
{% endhint %}

### Submitting the Unit

After completing all required fields, the user can submit the unit.

Once submitted, the unit will appear in the **My Culinary Units** list with the status **Pending**.

This means the unit has been saved successfully and is waiting for review.

### Approval and Publication

All submitted units must be reviewed by a Content Manager before they are published.

When the Content Manager approves the unit, its status changes from **Pending** to **Published**.

After publication, the unit becomes visible in the **Digital Catalogue** and can be viewed by other users as part of the Culinary Trail collection.

<figure><img src="/files/ZTQu82JRUwgcFxHtqWi4" alt=""><figcaption></figcaption></figure>

### Editing or Deleting a Unit

Users can manage their submitted units from the **My Culinary Units** list.

Available actions may include:

* **Edit** – update or correct the information in an existing unit
* **Delete** – remove a unit from the user’s list

If a published unit is edited, it may require another review before the changes are visible publicly, depending on the approval process.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.culinarytrail.eu/guides/units-of-culinary-heritage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.