# Getting Started Section

The first instruction section in an article is a special case.

It should always be named **Getting Started** and should cover the initial steps to get started with the rest of the article.

If you have a starter project, typically this section should contain the following:

1. **Instructions to download the starter project**: Typically you can use a set sentence for this: “Download the starter project by clicking on the **Download Materials** button at the top or bottom of the tutorial.”
2. **An overview of the starter project**: This should include an overview of what the project does, a build and run with screenshots, and optionally an overview of the code.
3. **An overview of the problem**: Finally, give a description of what feature(s) you are trying to add to the starter project in this tutorial.


---

# Agent Instructions: 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:

```
GET https://playbook.wednesday.is/communications/content/processes/articles/article-structure/getting-started-section.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.