> For the complete documentation index, see [llms.txt](https://help.webhash.com/webhash-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.webhash.com/webhash-docs/how-to-edit-every-component-on-your-website/advanced-blocks-power-up-your-websites-functionality/timeline.md).

# Timeline

{% embed url="<https://youtu.be/OVciqWwlk8g>" %}

#### Adding the Timeline Block

* **Add Block:**
  * Once selected, a pop-up might appear to confirm the addition of a Timeline block.
  * Click the 'Submit' button to add the block to your page.
* **Input Timeline Content:**
  * With the Timeline block now part of your page, click on it to start adding content.
  * Look for a 'Create' button within the block to begin inputting individual timeline entries.
  * Enter details for each entry, such as the title, date, and description of the event or milestone. These details will help visitors understand the chronological order and significance of each point on the timeline.
* **Add Multiple Entries:**
  * To build a comprehensive timeline, continue adding entries by clicking the 'Create' button for each new event or milestone.
  * Fill in the relevant information for each entry to develop a full narrative or historical record.
* **Customize the Appearance:**
  * Depending on the block’s features, you may have options to customize the appearance of your timeline. This could include changing text colors, adjusting line styles, or modifying date formats.
  * Tailor these settings to match your website’s design and the timeline’s purpose.
* &#x20;**Update and Publish:**
  * After adding and customizing your timeline entries, ensure you save or update the block to reflect the changes on your website.
  * Review the timeline on your page to confirm that all entries are displayed correctly and in the right order.


---

# 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://help.webhash.com/webhash-docs/how-to-edit-every-component-on-your-website/advanced-blocks-power-up-your-websites-functionality/timeline.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.