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

# Trails

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

## Managing Trails

Registered users can create and manage trails through the **My Trails** section of their account dashboard. Trails allow users to connect selected restaurants into a themed route, such as a culinary trail, wine trail, hiking trail, or bike trail.

Once a trail is approved and published, it becomes visible on the platform and can be explored on the Transnational Trails map.

### Accessing My Trails

After signing in, users can open the **My Account** page and select **My Trails** from the account menu.

This section displays all trails created by the user. Each trail is shown in a table with the following information:

* **Title**
* **Status**
* **Date**
* **Actions**

The available actions allow users to **view**, **edit**, or **delete** a trail.

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

### Adding a New Trail

To create a new trail, click the **Add new Trail** button.

This opens the trail creation form, where users can enter the main information about the trail and select the restaurants that should be included as stops.

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

### Completing the Trail Creation Form

The trail creation form contains the required information needed to create and display the trail.

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

Users should complete the following fields:

<details open>

<summary><strong>Trail Name</strong></summary>

Enter the name of the trail. This is a required field and will be displayed as the trail title.

</details>

<details open>

<summary><strong>Trail Description</strong></summary>

Use this field to describe the trail. The description can include information about the theme of the route, the culinary experience, the region, and what visitors can discover by following the trail.

</details>

<details open>

<summary><strong>Featured Image</strong></summary>

Upload a featured image that represents the trail. This image will be displayed on the trail details page.

</details>

<details open>

<summary><strong>Trail Type</strong></summary>

Select the appropriate trail type. Available options may include:

* Bike Trail
* Culinary Trail
* Hiking Trail
* Wine Trail

</details>

<details open>

<summary><strong>Restaurant Stops</strong></summary>

In the **Restaurant Stops** section, users can select restaurants that are already saved in the system. Selected restaurants will become stops on the trail and will be displayed on the trail map and in the list of restaurant stop cards.

</details>

### Submitting a Trail

After completing the required fields and selecting the restaurant stops, users can submit the trail.

Once submitted, the trail status is set to **Pending**. This means the trail has been saved successfully and is waiting for review by a Content Manager.

After the Content Manager approves the trail, its status changes to **Published**. Published trails become visible on the platform and can be viewed by users.

### Viewing a Trail

Users can click **View** to open the trail details page.

The trail details page displays the main information about the trail, including its title, type, featured image, and description. It also includes a trail map showing the selected restaurant stops.

Under the map, the restaurant stops are displayed as individual cards. Each card provides useful information about the stop and includes action buttons that allow users to:

* Open the restaurant details page
* Get directions in Google Maps
* Visit the restaurant website

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

### Editing or Deleting a Trail

From the **My Trails** list, users can manage their created trails using the available action buttons.

The **Edit** button allows users to update trail information, such as the description, image, trail type, or selected restaurant stops.

The **Delete** button removes the trail from the user’s list.

If changes are made to a published trail, they may need to be reviewed again before appearing publicly.

### Viewing Trails on the Transnational Trails Map

Published trails can also be viewed from the main website navigation.

To access the public trails map, open the **Transnational Trails** page and click **View the trails**. This opens the **Transnational Trails Map**, where users can explore the available trails displayed on an interactive map.

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

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

The map shows different Culinary Trail routes together with EuroVelo cycling routes, allowing users to view culinary experiences in connection with broader sustainable travel routes.


---

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