> 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/space/guides/sitewide/using-device-specific-visibility.md).

# Use device-specific visibility

## Space: Using device specific visibility

## Summary <a href="#h_ebe495baf7" id="h_ebe495baf7"></a>

***

After editing your theme and previewing it across different devices you may find that some sections just look better on some devices. For example on mobile devices you may want to use a slider instead of a grid section.

## How to <a href="#h_347c6cec81" id="h_347c6cec81"></a>

***

1. Open the theme editor by clicking Customize next to the relevant theme.
2. Create two sections, one will be on desktop and one will be for mobile.
3. Click into one of the sections and scroll down to Display then click Show on mobile only.
4. Click into one of the sections and scroll down to Display then click Show on desktop only.
5. Thats it! Now you have two sections that each only display on mobile and desktop separately.

<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://help.brickspacelab.com/space/guides/sitewide/using-device-specific-visibility.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.