> For the complete documentation index, see [llms.txt](https://mariohernandez.gitbook.io/components/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariohernandez.gitbook.io/components/a-components-lifecycle/add-hero-to-homepage.md).

# Add Hero to homepage

Now that we have a view mode display ready to go, let create a new node of type Homepage so we can add the hero of our choice.

### Exercise: Create the homepage node with a hero

1. From Drupal's admin toolbar, click **Content | Add content**
2. Select \*\*Homepage \*\*as the type of content to create
3. Under title type **Homepage**
4. In the Hero field, begin typing to search for the article you wish to turn into the Hero
5. When the targeted article is found, select it and click the \*\*Save \*\*button
6. The homepage node will now rendered and we should see a large image and a title

The Hero is now displaying in Drupal using the designated view mode display. We will handle the styles of the hero in a later exercise.


---

# 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://mariohernandez.gitbook.io/components/a-components-lifecycle/add-hero-to-homepage.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.