> For the complete documentation index, see [llms.txt](https://docs.swingsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swingsoftware.com/pdf-converter-for-notes/getting-started/pdf-converter-terminology/alternate-notes-forms.md).

# Alternate Notes forms

By default, Notes documents will be converted to PDF based on the layout of the default Notes document form.

If you wish to generate PDF files with a different layout, you may design a new document form in Domino Designer (which will look better when rendered to PDF and which may hide or display additional information) and then set SWING PDF Converter to use this form instead of the original form during conversions.

In SWING PDF Converter, this type of document form is referred to as the **Alternate Form**.

### For administrators

{% content-ref url="/pages/-MlCEf5-St8fbGC522sQ" %}
[How to use alternate forms](/pdf-converter-for-notes/getting-started/using-pdf-converter-client-side/how-to-use-alternate-forms.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MlF6m12cpRuO4mEV88o" %}
[Using alternate forms](/pdf-converter-for-notes/how-to/how-to-use-alternate-forms.md)
{% endcontent-ref %}

### For developers

{% content-ref url="/pages/-MlFqVGCpaK9DXigoxlh" %}
[PDF conversion on the Web](/pdf-converter-for-notes/for-developers/lotusscript-code-samples/pdf-conversion-on-the-web.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MlETsVeweezORmvMxuF" %}
[How to convert a document collection using multiple alternate forms](/pdf-converter-for-notes/how-to/how-to-convert-a-document-collection-using-multiple-alternate-forms.md)
{% endcontent-ref %}


---

# 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.swingsoftware.com/pdf-converter-for-notes/getting-started/pdf-converter-terminology/alternate-notes-forms.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 `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.