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

# Device specific visibility

After editing your theme and previewing it across devices, you may find some sections work better on specific devices. For example:

* Sliders often work better on mobile
* Grid sections often work better on desktop

Keystone lets you create device-specific sections to optimize user experience.

#### How to Set Up Device-Specific Sections

1. Open the Theme Editor
   * Click **Customize** next to your theme
2. Create two sections
   * One section for desktop
   * One section for mobile
3. Set mobile display preferences
   * Click into your mobile section
   * Scroll to **Display**
   * Click **Show on mobile only**
4. Set desktop display preferences
   * Click into your desktop section
   * Scroll to **Display**
   * Click **Show on desktop only**
5. Save your changes
   * You now have sections that display exclusively on their intended devices


---

# 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/keystone/guides/sitewide/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.