> 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/pages-and-sections-creation/pages.md). # Pages ### About Pages Every thriving online store needs a well-structured website that guides customers seamlessly through their shopping journey. This section empowers you to create every page crucial for your store's success. The provided articles act as your comprehensive roadmap, offering a detailed breakdown of crafting each essential page. Whether you're a complete beginner or possess some experience, these guides cater to all skill levels. You'll find clear instructions that take you from the fundamental steps of building a page all the way to advanced optimization techniques. ### Related Resources * [Pricing and billing](https://help.pagefly.io/manual/pricing-and-billing/) * [How to create pages in PageFly](http://pages) * [How to create section and use it in your theme](https://help.pagefly.io/manual/create-a-section-with-image-and-text/) --- # 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/pages-and-sections-creation/pages.md?ask=&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.