> For the complete documentation index, see [llms.txt](https://docs.pulseinsights.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulseinsights.com/configuring-pulse-insights-console/editor/formatting.md).

# Formatting

Formatting is how you configure the look and feel of your survey. The survey's design can impact user behavior, so it is important to format your surveys with results and response rates in mind.&#x20;

A survey's formatting of the following components, which together determines how the survey will look to the end-user:

* Widget type
* Themes
* Question Display&#x20;
* Custom survey-level CSS (optional)

### **Pulse Insights can match your theme to your website for you!** <a href="#match-your-theme-to-your-website.-pulse-can-do-this-for-you" id="match-your-theme-to-your-website.-pulse-can-do-this-for-you"></a>

Pulse Insights surveys are designed to be a native user-experience and to fit in with your site branding. Pulse Insights can customize colors, fonts, buttons and backgrounds via JSON “themes” so the formatting matches your brand.&#x20;

Pulse thinks ahead to include those things you may not consider, like accessibility and dynamic screen sizes.


---

# 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.pulseinsights.com/configuring-pulse-insights-console/editor/formatting.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.
