> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/in-person-event/pre-event-page-app.md).

# Pre-event page (App)

It is possible to set up a pre event page for in-person events. This pages describes how to do that that.

{% hint style="info" %}
Available for: in-person events; packages: extensive
{% endhint %}

A pre-event page can be used to display information about your event and to make the registration for your event available. The integrated [registration form function](https://knowledge-base.letsgetdigital.com/lgd-features/registration-form?q=regis) of Let's Get Digital can be used to make registering for your event easy and convenient.

## How to set it up

1. In the admin panel, hover over 'Settings' and choose 'General settings'.
2. Click on 'Registration & pre-event page' on the left-hand side menu.
3. Select the registration form that you would like to use (you will first need to create one before you can link one to the pre-event page).

For information about the settings of the pre-event page, please navigate to the [pre-event settings article](https://knowledge-base.letsgetdigital.com/the-admin-panel/settings/virtual-event-settings-vp/pre-event-settings-vp) in our knowledge base. 

{% hint style="info" %}
**Note:** Once the timer finishes the countdown, the register button will disappear, so it won't be possible to register anymore once your event has started.
{% endhint %}

## Branding of the pre-event page

### Images

To set up the images of your pre-event page:

1. Hover over settings and select 'General Settings'.
2. Click on 'Branding' on the left-hand side menu. 
3. Select your 'Background image' for the pre-event page.
4. Scroll further down to 'Virtual event images' and select your 'Event Logo'. This logo will be visible in the left corners of your pre-event page. 

### Colours

To set up the colours of your pre-event page:

1. Hover over settings and select 'General Settings'.
2. Click on 'Branding' on the left-hand side menu. 
3. Scroll down to 'Virtual event & Pre-event page colours'.
4. Fill in the colours that you want to use for the pre-event page. (to see which colours will become visible where use the LGD ColourGuide).  

{% file src="/files/c1tluIaN1p2SUCXzCxli" %}

## The final result

To check out your pre-event page and retrieve the URL that can be shared, please follow these steps:

1. In the admin panel, hover over 'Settings' and choose 'General settings'
2. Click on 'Registration & pre-event page' on the left-hand side menu.
3. Click on 'Click here' next to 'Go to pre-event page'

![](https://772941315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M5LNCGpK5lyymcFZU4V%2Fuploads%2F4YyiCBGk6ztHZr3laEoc%2Ffinalresultpreeventpageapp.gif?alt=media\&token=a8784f79-0ac0-4a9b-b8d5-ce39ee4eacdd)


---

# 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://knowledge-base.letsgetdigital.com/in-person-event/pre-event-page-app.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.