# First draft

- [Think of the reader as a beginnner](https://playbook.wednesday.is/communications/content/processes/articles/first-draft/think-of-the-reader-as-a-beginnner.md): A quick guide on how to think about your reader when writing the first draft of your article pieces.
- [Stay in limit](https://playbook.wednesday.is/communications/content/processes/articles/first-draft/stay-in-limit.md): The word limit to stick to, when writing the first draft of your article pieces.
- [Make it scannable](https://playbook.wednesday.is/communications/content/processes/articles/first-draft/make-it-scannable.md): A quick guide on how to make your first draft scannable, while writing for the Wednesday website.
- [Explain Code](https://playbook.wednesday.is/communications/content/processes/articles/first-draft/explain-code.md): A quick guide on how to explain and talk about code, when writing the first draft of your article pieces.


---

# 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/first-draft.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.
