> For the complete documentation index, see [llms.txt](https://whoof-docs.rdnz.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whoof-docs.rdnz.dev/about.md).

# About

{% hint style="success" %}
Web app running at <https://whoof.rdnz.dev/> - that is a simple front end built with Refine to demonstrate the available features.
{% endhint %}

The Whoof project is a simple pet vaccination application with a variety of learning purposes created by [Guilherme Raduenz](https://gui.rdnz.dev/_/).

This documentation has the main purpose of helping with the development of front-end applications for the back-end service. It is divided across the pages of this site, and the actual API specification is under [OpenAPI Specification](/openapi-specification.md).

## External links

Some external resources can help you learn about the project.

### GitHub repository

{% embed url="<https://github.com/graduenz/whoof-aspnetcore/>" %}

### Author website

{% embed url="<https://gui.rdnz.dev/labs/whoof>" %}


---

# 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://whoof-docs.rdnz.dev/about.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.