> For the complete documentation index, see [llms.txt](https://docs.shipped.club/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shipped.club/components/hero.md). # Hero The hero section of your landing page

Designed for the landing pages, the hero goes at the top of your page. It includes: * a headline to show the problem solved, or the transformation you'll allow your customers to achieve. * a strong Call to Action (Try FREE now). * optionally, a "Talk to us" button (or Book a demo), you can define the Calendly link in the `config.ts` file. * a testimonials section, if you already have customers, show their avatars. * a placeholder for your product image (I use [Figma](https://figma.com/) to design, but I know that [Canva](https://www.canva.com/) is a great product too). Component: ``\ File: `src/components/Hero/Hero.tsx` {% code title="page.tsx" %} ```typescript import { Hero } from "@/components/Hero/Hero"; ``` {% endcode %} ### Props The Hero component has a few props | Prop | Type | Description | | ------------ | ------- | -------------------------------------------- | | showBookDemo | boolean | Shows or hides the "Talk to us" button | | showCta | boolean | Shows or hides the Call to Action button | | showUsers | boolean | Shows or hides the testimonial users section | ### Examples Some examples of hero sections from my products:

*** {% hint style="info" %} If you need basic components like buttons, inputs, etc, they are all available with [ChakraUI](https://chakra-ui.com/). {% endhint %} --- # 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.shipped.club/components/hero.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.