> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/systeme-und-projekte/startseite.md). # Home page The home page of a project in Eliona provides a quick overview of important information and widgets relevant to the project. It is shown first when opening a project or after logging in. There you can see the **project overview** with the created elements, direct access to the **project settings**, a **Map** with the project location and a **weather widget**, which shows the current weather and the forecast for the location.


[1]	project overview	Shows the created and configured elements, such as asset data, status overviews or alarms that were manually added. -> Configure element
[2]	project settings	Allows direct access to the project settings, where configurations and adjustments can be made. -> Configure home page
[3]	Map	Shows a map with the locations of the assets selected in the elements.
[4]	weather widget	Shows the current weather as well as a weather forecast for the coming days based on the user's location. The weather widget uses the following priority for determining the location: Location in the user profile Location in the project role If no location is specified, the location of your office is used. -> Weather widget

## Configure home page

Follow these steps to set up a home page for your project: 1. **Open Engineering**\ Click in the sidebar on **Engineering \[A]**\ ▷ The menu **Engineering** opens. 2. **Open projects**\ Select the item **Projects \[B]**\ ▷ The project overview is displayed. 3. **Open project**\ Open the desired project **\[C]**\ ▷ The project settings are loaded. 4. **Activate home page**\ Activate the option **home page** in the project settings **\[D]**\ ▷ The home page is set for this project. 5. **Add element to the home page**\ Add an element to the home page by clicking on **“Add element”** click **\[E]**
## Configure element To add a new element to the home page, click on **+Add element** \[E]. If you want to edit an existing element, click the **pencil button**, to open the configuration.


[F]	Set name	Enter a name for the element. The name is displayed as the heading for the element on the home page.
[G]	Add description	Write a short description; the description is displayed below the name in the element.
[H]	Select asset	Select the asset that should be linked to the element by clicking on Search asset clicking. This connects the element with a specific asset and its data will be displayed in the element.
[I]	Add image	Optionally, you can upload an image to visually support the element. A square image with a 1:1 ratio is recommended to ensure optimal display.
[J]	Select element attribute	Select the attributes that should be listed below in the element on the home page, e.g. a measured value or a status value of the linked asset.
[K]	Save	Click on Save, to add the element to the home page or apply the changes.

--- # 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://docs.buildings.ability.abb/collection/english-v14/documentation/systeme-und-projekte/startseite.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.