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

# About Corgi

Corgi is an HTML template language, inspired by pug (hence the name), for Go. Just like pug, corgi also uses code generation to generate its templates.

{% hint style="info" %}
Just a quick note before you get started reading: When you see examples of corgi code you'll often also see the resulting HTML. This HTML is pretty printed and further formatted to increase glanceability. In reality, whitespace is formatted as described in [Writing Text](/corgi/learning-corgi/arrow-blocks.md).
{% endhint %}

The syntax is very similar to pug and those familiar with it will quickly feel at home. Do note though, that despite many similarities, corgi does not aim to be a 1:1 pug clone. Instead corgi attempts to be a template engine that feels Go-like and is easily readable for any Go developer, while, at its foundation, still using the syntax of pug.


---

# 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://mavolin.gitbook.io/corgi/about-corgi.md?ask=<question>&goal=<user_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.