> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/writebackextreme/features/tableau-extension/configuration/schemas/general-features/padding.md). # Padding Add spacing between fields to improve layout and readability **Padding** allows you to add visual spacing **above or below** form elements. This helps organize content more clearly and creates breathing room between sections, improving the overall form layout and user experience. ## Use Cases * Separate key sections visually * Create space around surrounding text * Improve readability of long forms * Enhance the appearance of dynamic field groups ### Example Use Case: * Add spacing between “Personal Details” and “Contact Info” sections to make forms easier to scan and fill.

## Best practices * Use consistent padding to align form elements * Avoid excessive spacing that pushes content out of view * Combine padding with **surrounding text** for more structured designs --- # 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.infotopics.com/writebackextreme/features/tableau-extension/configuration/schemas/general-features/padding.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.