> For the complete documentation index, see [llms.txt](https://au-dohp.gitbook.io/au-dohp-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://au-dohp.gitbook.io/au-dohp-docs/getting-started/quickstart-guides.md).

# Quickstart guides

A simplified path to setting up and managing your AU-DOHP project efficiently. Follow these key steps to structure and optimize data workflows:

<figure><img src="/files/OFPfaSEMfi1NEs2isC8F" alt=""><figcaption></figcaption></figure>

#### **Key Steps:**

1. **Creating your data pipeline** – Automate the process of extracting, transforming, and loading (ETL) data from source to destination, ensuring seamless data flow and integration.
2. **Defining your data contract** – Establish the structure, format, semantics, quality, and usage terms for exchanging data between your data provider and consumers, ensuring consistency and reliability.
3. **Developing your data product** – Package consumable units of data that users can interact with, leveraging your already established data pipeline for structured and accessible insights.
4. **Designing your graphs and dashboards** – Visualize your generated data products through interactive dashboards, enabling better analysis, decision-making, and user engagement.


---

# 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://au-dohp.gitbook.io/au-dohp-docs/getting-started/quickstart-guides.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.