> 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/welcome.md).

# Welcome

<button type="button" class="button primary" data-action="ask" data-icon="gitbook-assistant">Ask a question…</button>

## Welcome to the Culinary Trail Documentation

{% hint style="success" %}
**Estimated time: 10 minutes.**
{% endhint %}

Welcome to the official documentation for the **Culinary Trail platform**. This documentation explains how registered users, contributors, and visitors can use the platform to create, manage, browse, and explore culinary heritage content from the Danube Region.

The guides are organized by the main sections of the platform and provide step-by-step instructions for working with Units of Culinary Heritage, restaurants, trails, the Digital Catalogue, and the Transnational Trails maps.

***

### What You Can Find in This Documentation

#### Managing Units of Culinary Heritage

Learn how registered users can create and manage Units of Culinary Heritage through their account dashboard. This guide explains how to add a new unit, complete the submission form, use the Overview, Food, Beverage, Technique, Tradition, and Media tabs, and understand the approval process before publication.

***

#### Managing Restaurants

Learn how users can add, view, edit, and delete restaurants connected to the Culinary Trail platform. This section explains the restaurant submission form, the approval process, and how published restaurants appear on the Transnational Trails map.

***

#### Managing Trails

Learn how users can create and manage trails by selecting restaurants as trail stops. This guide explains how to add a new trail, complete the trail creation form, select trail types, add restaurant stops, and view published trails on the platform.

***

#### Using the Digital Catalogue

Learn how visitors can browse published Units of Culinary Heritage in the Digital Catalogue. This section explains how to search, filter, and open individual unit detail pages, as well as how logged-in users can leave ratings and comments.

***

#### Using the Transnational Trails Pages

Learn how users can explore culinary heritage entries, partner restaurants, published trails, and EuroVelo cycling routes on interactive maps. This guide explains the difference between the Transnational Trails map and the Trails Map page, including how to filter map content and open detail pages.

***

### Review and Publication Process

Content submitted by users is not published immediately. New Units of Culinary Heritage, restaurants, and trails are first saved with the status **Pending**.

A Content Manager reviews the submitted content. Once approved, the status changes to **Published**, and the content becomes visible on the public areas of the platform, such as the Digital Catalogue, restaurant pages, trail pages, or interactive maps.

***

### Who This Documentation Is For

This documentation is intended for:

* Registered users contributing culinary heritage content
* Project partners managing local or regional entries
* Content Managers reviewing submitted content
* Visitors who want to understand how to browse the Digital Catalogue and Transnational Trails maps

***

### Getting Started

To begin contributing content, create an account or sign in to the Culinary Trail platform. After logging in, open **My Account** to access your dashboard. From there, you can manage your Culinary Units, Restaurants, Trails, and account details.

For browsing published content, visitors can use the **Digital Catalogue** and **Transnational Trails** sections without creating new entries.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-hat-chef" style="color:$primary;">:hat-chef:</i></h4></td><td><h4>Units of Culinary Heritage</h4></td><td>Learn how to create and manage new Units of Culinary Heritage.</td><td><a href="/pages/0VSaT3FcvVnNIGiJkWVo">/pages/0VSaT3FcvVnNIGiJkWVo</a></td></tr><tr><td><h4><i class="fa-fork-knife" style="color:$primary;">:fork-knife:</i></h4></td><td><h4>Restaurants</h4></td><td>Learn how to create and manage new Restaurants.</td><td><a href="/pages/uCfuMhmSKMlAuLMCcvnu">/pages/uCfuMhmSKMlAuLMCcvnu</a></td></tr><tr><td><h4><i class="fa-route" style="color:$primary;">:route:</i></h4></td><td><h4>Trails</h4></td><td>Learn how to create and manager new Culinary Trails.</td><td><a href="/pages/58CUu2v9PJva7OrETodY">/pages/58CUu2v9PJva7OrETodY</a></td></tr></tbody></table>


---

# 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/welcome.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.