> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-pages/advanced-features/hiding-sections-and-elements.md).
# Hiding Sections and elements
How to hide a section
How to hide an element in a section
Hide specific sections on selected breakpoints using the Visibility options on the layers panel.
To do this, select the desired section or element on the layers panel, click on the eye icon, and choose where to hide it by deselecting specific breakpoints. When you’re done selecting where to hide each section and element, just click “Done.”
When hiding a section on tablet or mobile, the editor will automatically move the section before and/or after it in its place. No empty-looking white space will remain.
Note : If you create custom breakpoints after saving these changes, you will have to amend your visibility options to include any newly created breakpoints.
### How to hide an element in Sections
To hide a specific element on selected breakpoints, use the layers tab on the left. On the layers tab, select the element you wish to hide > click visibility icon > make your selection > click done.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.maker.co/maker-pages/advanced-features/hiding-sections-and-elements.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.