> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/basics/content-and-preview.md). # Content & Preview ### Overview Content & Preview is the step in the send wizard where you add and configure the content of your communication - and check how it will look before it goes out. It appears as a named step across mailouts, TXT outs, and push notifications. What you can configure within it varies by channel, but the purpose is the same: get your content right and verify it before sending. *** ### Where Content & Preview applies Content & Preview is available in the following areas of UbiQuity: * **Mailouts** - Set sender details, add HTML and text content, and preview your email * **Automated Mailouts** - Configure and preview content for recurring scheduled sends * **TXT Outs** - Write and preview your TXT message content * **Push Notifications** - Build and preview push notification content *** ### How it works Within Content & Preview, you add the content for your send and then use the preview tools to check it before committing. **Adding content** varies by channel. For email, this means selecting your template and editing article blocks. For TXT and push, it typically means composing your message directly. **Previewing** lets you check your content in two ways. You can view a generic preview of the content as-is, or preview it as a specific contact from your database - which resolves any merge fields and shows how the message will appear for that person. You can also send preview emails to yourself or your team for testing before the actual send goes out. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ubiquity.co.nz/documentation/basics/content-and-preview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.