> 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/picturethis/configuration/configuration-screen/layout/card-layout.md).

# Card Layout

#### Columns

Enter the column width in % or px. PictureThis will automatically calculate the right amount of columns. Example: 10% or 150px.

#### Image Height

Enter the height you would like the images to be in pixels. This will make sure your images are shown in the size you prefer. Example: 100px

#### Place Image Above or Beside Text

Decide whether to place your image above or beside the text.

#### Image & Card Padding

This setting (padding) determines the space between the edge of the Image Card and the image. This will make sure that your mages are not glued together in your Image Grid but have a small whitespace between them. Choose the image padding range within your Table cell using pixels. For example: 4px to generate 4 pixels of whitespace around the image.

#### Card Margin

The Card Margin is the space between each of the cards in your layout, to add more space between each card add enter that here in pixels.

#### Border Radius

You can show your cards with a slightly rounded border. Using % or px enter your Cards border radius.

#### Card Shadow

Enable or Disable the backdrop shadow effect to match the desired look.<br>


---

# 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/picturethis/configuration/configuration-screen/layout/card-layout.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.