> 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/the-admin-panel/content/virtual-platform/faqs.md).
# Pages (Virtual event)
Three pages can be added to the virtual event platform to provide additional information. The frequently asked questions tab shows questions and answers which could be of use during the virtual event.
## Manual adjustments in the admin panel
To find the navigation menu settings/home page within the admin panel, hover over the content tab and select 'Page' from the drop down menu.
## The overview
The page overview shows three pages by default. These pages can be customised and displayed on the virtual event platform. The purpose of these pages will be explained in more detail below.
### The pages
{% tabs %}
{% tab title="Everything about our platform" %}
{% hint style="info" %}
Our default text will be displayed on the landing page when not adjusted.
{% endhint %}
Name the page. In the main text box add information about the platform.
Click on 'Save changes'.
The page is now visible on the landing page:
{% endtab %}
{% tab title="FAQ" %}
{% hint style="info" %}
Our default FAQ is displayed for events with a core [package](https://knowledge-base.letsgetdigital.com/pricing-and-packaging/service-packages).
{% endhint %}
In the main text box, add the FAQ answers and questions. It is advised to write down the questions in **bold** to make a distinction between questions and answers.
Consult our [Frequently Asked Questions](https://eventinsight-consultants.gitbook.io/let-s-get-digital/faqs-for-the-lgd-website) article to see some frequently asked questions which could be of use for the FAQ page.
Click on 'Save changes'.
The page is now visible on the event page:
The FAQ page can also be set up by using the questions and answers function:
The page is now visible on the event page:
#### Changing the order of the FAQ questions:
In the admin panel, hover over 'Content' and choose 'Page', and then click on the edit button next to 'FAQ'. Here, you will find a drag-and-drop menu to change the order of the questions:
{% endtab %}
{% tab title="Prepare yourself" %}
{% hint style="info" %}
Our default text will be displayed on the landing page when not adjusted.
{% endhint %}
Name the page. In the main text box add information about the platform.
Click on 'Save changes'.
To edit the text displayed after the arrows, click on the question mark under actions for the 'Prepare yourself' page.
A page will be displayed where you can edit the header and the text under the header by clicking the edit button under 'Actions':
The page is now visible on the landing page:
{% endtab %}
{% endtabs %}
## Registration & Pre-event page
The registration & pre-event page can be edited in the general settings. More information on how to set up the pre-event page can be found in [this article](https://knowledge-base.letsgetdigital.com/the-admin-panel/settings/general-settings-app-+-vp-1/registration-and-pre-event-page).
---
# 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/the-admin-panel/content/virtual-platform/faqs.md?ask=&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.
%20(1)%20(1)%20(1)%20(2)%20(1).gif?alt=media&token=d2926e62-4645-499c-9891-d5cfec95334a)