> For the complete documentation index, see [llms.txt](https://tutorials.clause9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tutorials.clause9.com/welcome.md).

# Welcome!

This page contains a number of tutorials designed to familiarise you with Clause9 in a guided, step-by-step video series.&#x20;

The basic tutorial series introduces the fundamental building blocks of working with Clause9. Here, you will learn how to create new clauses, how to introduce flexibility to them from a styling and a content perspective, and how to turn stacks of clauses into intelligent templates.&#x20;

The intermediate tutorial series is shorter in length, but introduces some more advanced ways of augmenting your clauses and introducing additional flexibility in your documents.

## Tutorial series

### Basic clause author tutorial

This tutorial teaches you how to create contracts by stacking together clauses provided to you by a template author.

### Intermediate clause author tutorial

This tutorial showcases a collection of additional functionalities allowing you to better structure and deploy your knowledge.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://tutorials.clause9.com/welcome.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 `build a script that syncs our docs to a CMS` 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.
