> 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/editor.md).

# Editor

### About Editor

PageFly's user interface is designed with user experience in mind. The clean and clutter-free layout makes it easy to navigate, regardless of your design experience. Drag-and-drop functionality allows you to effortlessly add and arrange elements on your pages, while clear labeling and intuitive tools ensure you can find the features you need quickly.

Beyond the core functionalities, PageFly offers a treasure trove of extra functions designed to streamline your design workflow and enhance your pages.

### Related Resources

* [Global Styles](https://help.pagefly.io/manual/global-styling-feature/)
* [Page Editor – Breadcrumb](https://help.pagefly.io/manual/page-editor-breadcrumb/)
* [Page Editor – Element Catalog](https://help.pagefly.io/manual/page-editor-element-catalog/)
* [Page Editor – Page Canvas](https://help.pagefly.io/manual/page-editor-page-canvas/)
* [Page Editor – Element Inspector](https://help.pagefly.io/manual/page-editor-element-inspector/)
* [Page Editor – Element Toolbar](https://help.pagefly.io/manual/page-editor-element-toolbar/)


---

# 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/editor.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.