> For the complete documentation index, see [llms.txt](https://upskilling.stacs.scot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upskilling.stacs.scot/conference26/conference-programme/venue-and-travel.md).

# Venue and Travel

Venue and Travel information

#### Dietary Requirements

{% hint style="info" %}
If you have any specific allergies such as nuts, can you please confirm the severity (e.g. is it airborne or if ingested and if they carry epi pens)?   *Whilst we take steps to minimise the risk of cross contamination, our food is prepared in a kitchen where nuts, gluten and other allergens are present.   As our menu descriptions do not include all ingredients we use, please let us know if you have a food allergy or intolerance before placing an order.    Full allergen information is available on request.*

* Please enter relevant details when registering for a conference ticket.
  {% endhint %}

#### Car Travel

{% hint style="info" %}
Stirling Court Hotel has 150 complimentary car parking spaces. &#x20;

These are operated on a first come first serve basis.   Parking in the Hotel car park is free to our guests. A barrier system is in operation however guests must also input their car registration number immediately upon entering the hotel. If you don’t submit your car registration on arrival this will result in a private parking notice.   Please see the link below for more details:
{% endhint %}

{% embed url="<https://www.stirlingvenues.com/visiting-us/find-us-parking>" %}

#### Campus Map

{% embed url="<https://www.stirlingcourthotel.co.uk/application/files/2115/7053/7801/University_of_Stirling_Venues_Map.pdf>" %}


---

# 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://upskilling.stacs.scot/conference26/conference-programme/venue-and-travel.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.
