> For the complete documentation index, see [llms.txt](https://docs.beefree.io/end-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beefree.io/end-user-guide/design-tools/content-area-padding.md).
# Content Area Padding
The Content Area Padding feature empowers you to adjust the padding for any row’s content, providing you with greater design flexibility and precision. By managing padding on all sides—top, bottom, left, and right—you can fine-tune the spacing within your layouts to achieve clean, professional, and visually appealing designs easily.
Take the following steps to adjust a row's content area padding:
1. Enter your email, page, or popup design.
2. Click on the row you'd like to edit the content area padding for.
3. Navigate to the sidebar on the left-hand side.
4. Ensure you are under the **ROWS** tab.
5. Scroll down to the **Layout** section of the **Row properties**.
6. Navigate to the **Content Area Padding** option
7. **(Option 1)** Under **All sides** click the plus (+) sign to uniformly apply padding around all the content within the row.
8. **(Option 2)** If you'd like to adjust the padding for each side of the content within the row, toggle on **More options** and adjust the padding for each side accordingly.
{% hint style="info" %}
**Note:** The **Content Area Padding** option applies to one row at a time. To adjust the content area padding for multiple rows within your design, ensure that you select each row and make your desired adjustments accordingly.
{% endhint %}
---
# 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.beefree.io/end-user-guide/design-tools/content-area-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.
