> For the complete documentation index, see [llms.txt](https://help.brickspacelab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brickspacelab.com/paper/getting-started/theme-settings/borders.md).

# Borders

Border styling helps define your brand’s visual tone. Choose between rounded edges for a friendly, approachable look or sharp corners for a modern, bold aesthetic.

### Design tips

{% stepper %}
{% step %}
Use consistent radius values (e.g., all 5px) for a harmonious look
{% endstep %}

{% step %}
Combine sharp elements (0px) with some rounded components for visual interest
{% endstep %}

{% step %}
Thicker borders (2px+) work well for high-contrast designs
{% endstep %}

{% step %}
Borderless (0px width) creates a minimalist aesthetic
{% endstep %}
{% endstepper %}

### Border settings

{% stepper %}
{% step %}
**Border Radius:** Controls the corner rounding for different elements:

* **Button Radius**: Adjusts corner curvature for all buttons (0px = sharp, higher values = more rounded)
* **Input Radius**: Sets rounding for form fields (5px recommended for friendly but clean look)
* **Element Radius**: Controls corner rounding for content sections (0px = sharp edges for modern layouts)
  {% endstep %}

{% step %}
**Border Width:** Determines the thickness of border lines:

* **Button Width**: 1px standard (thicker for emphasis, 0px for borderless)
* **Input Width**: 1px recommended for clean form fields
* **Element Width**: 1px standard for subtle framing of sections
  {% endstep %}
  {% endstepper %}


---

# 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://help.brickspacelab.com/paper/getting-started/theme-settings/borders.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.