> 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/borders.md).
# Borders
#### Overview
Borders are not just decorative; they can also help delineate content and draw attention to specific elements in your design. In the builder, you can set borders both for rows and for individual elements like buttons. You have the choice to apply borders to all sides or specify different borders for each side.
#### Row-Level Border Customization
When your row comprises multiple columns, you'll need to set borders for each one individually.
* Selecting a Row: Click outside the content area to select the entire row.
* Column Selection: Your sidebar will display a menu showing the columns in the row. Choose the one you wish to modify.
#### Granular Control
* Toggling More Options: Use the 'More options' toggle to specify which sides of the element will have borders.
* Border Style: Choose from various styles including solid, dotted, or dashed lines.
* Size and Color: Adjust the thickness and choose the color to make the border align with your design aesthetic.
#### Tip
Consistency is key; if you're setting up borders for multiple columns, ensure that the style complements the overall design.
---
# 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/borders.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.
