> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/into-the-weeds/configuring-pdf-form-fills-in-scribeware/adding-pages-to-your-pdf-with-additional-information.md).
# Adding pages to your PDF with additional information
Often, PDF forms require additional pages containing photos of property being inspected, narrative findings, etc.
ScribeWare allows you to specify a specific *section* in the report be used for this additional information. You can add any images, captions, narratives and fields to this section, and they’ll be appended to the end of the published PDF form.
{% hint style="info" %}
ScribeWare forms that have a photos section, like the 4-Point's **4-Point Photos** or the Wind Mitigation's **Wind Mitigation Photos**, set this up for you when you click **Add missing fields**. If the PDF is later set to append nothing, its dialog offers **Set append section**. See [Using PDF forms](/into-the-weeds/using-pdf-forms.md).
{% endhint %}
To configure additional pages:
1. Navigate to the chapter/section you wish to store the additional information in
2. select the 3 dots at the top right, then “add blank section”
3. Give the section a name. This will appear as the title of each page added to the PDF, and a section needs a name to be appended.
4. Double click the PDF in the media bar, or in a report
5. Under “Append section to end of document?”, select the section added in step 1
6. Check “Include section in report” if you want the the section to *also* appear in the published HTML report; otherwise leave it unchecked
7. Be sure to click “Save template” to save your changes to the new section
### Post navigation
---
# 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://docs.scribeware.com/into-the-weeds/configuring-pdf-form-fills-in-scribeware/adding-pages-to-your-pdf-with-additional-information.md?ask=&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.
