> For the complete documentation index, see [llms.txt](https://help.pagefly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pagefly.io/page-structure-and-elements/pagefly-elements/containers.md).

# Containers

### About Containers

PageFly Editor empowers you to bring your design vision to life with its intuitive layout system and diverse collection of elements. This section equips you with the knowledge to craft unique and engaging page layouts that will capture your audience's attention.

Here, you'll find a treasure trove of articles offering comprehensive guides on utilizing various layout options and elements within PageFly Editor. These guides will take you through the process of:

* Building flexible layouts: move beyond static page structures and explore PageFly's layout system. Learn how to create custom layouts with rows and columns, providing you with the freedom to arrange your content in any way you desire.
* Enhancing engagement with multimedia: incorporate captivating slideshows, informative tabs, and interactive accordions into your pages.

The provided articles will show you how to effectively configure these elements to showcase your products, highlight key information, and keep visitors engaged

### Related Resources

* [How to create a Homepage with PageFly?](/pages-and-sections-creation/pages/how-to-create-a-homepage-with-pagefly.md)
* [How to create a Product page with PageFly](/pages-and-sections-creation/pages/add-more-content-to-my-shopify-product-page.md)


---

# 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.pagefly.io/page-structure-and-elements/pagefly-elements/containers.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.
