# Theory Section Theory sections are sections without step-by-step instructions. Instead, they explain the high-level theory that you need to understand before you dive into the code. For example, they can be used to give an overview of how an API or technique works, to explain the approach you are going to take to solve a problem. These sections often include many illustrations to help the reader understand the concepts. Theory sections are incredibly important so that you can explain the “why” behind something you are doing. * **Explain just in time:** Don't overcomplicate by spending too much time in theory. Explain the theory right before you're going to implement it. * **Explain complicated material:** The more complicated the more theory * Use images and illustrations: Get in touch with Ali to get custom illustrations. --- # 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/theory-section.md?ask= ``` 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.