> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/platform-overview/page-editor/open-the-page-editor.md).
# Open the Page Editor
The Page Editor used to develop and customize mods.
### Open from the Floating Action Button
To access the Page Editor, you can click the Bricks icon that appear when you hover over the Floating Action Button that appears on any page:
{% hint style="info" %}
Don't see the PixieBrix Floating Action Button? You may have disabled it on a current page. You can head to your [Extension Settings](/platform-overview/extension-console.md) to re-enable it.
{% endhint %}
### Open from the Quick Bar
Alternatively, you can open the Page Editor from the PixieBrix Quick Bar by pressing CMD/Ctrl + M and choose the **Open Page Editor** action.
### Open from the Sidebar
Click the PixieBrix icon from the Chrome Extension menu to open the Sidebar. At the bottom of the main tab, choose the **Open Page Editor** link.
Excellent work! Now youโre ready to dive into the [Page Editor Components](/platform-overview/page-editor/page-editor-components.md).
### Troubleshooting
If you can't find the Page Editor, try these troubleshooting tips.
#### Check for hidden tabs
If you've opened the Chrome Dev Tools ([*how?*](https://developer.chrome.com/docs/devtools/open)) and don't see the PixieBrix tab, you might need to click the **>>** icon at the end of the tabs.
Still don't see it? Keep reading!
#### Make sure you've got the Extension installed.
Head to [app.pixiebrix.com](https://app.pixiebrix.com/) and confirm that you see a button that says **Open Extension Console**.
โ Extension has been installed if you see this:
If it says **Install from Chrome Web Store,** you need to install the Chrome Extension. Click the button from the Admin Console to install.
#### Go to an extension-accessible page
You cannot access the Page Editor from a blank new tab page or certain pages, like the [Extension Console](/platform-overview/extension-console.md).
To see if you're on a page that PixieBrix can't access, click the PixieBrix icon in the Chrome Extension section of your URL bar.
โ If the sidebar opens, you're on a page that PixieBrix can access!
๐ If you see a modal that says PixieBrix mods cannot run on this page, then you'll need to go to another page to access the Page Editor.
Try visiting another page, like [Linkedin](https://www.linkedin.com/), [GitHub](https://github.com/), [Wikipedia](https://www.wikipedia.org/), or even [the PixieBrix website](https://www.pixiebrix.com/).
#### Still having issues?
Pick one of the following ways to get support:
* Join the [PixieBrix Slack Community](https://slack.pixiebrix.com/) and post in the #learning channel
* Send an email to
---
# 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://docs.pixiebrix.com/platform-overview/page-editor/open-the-page-editor.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.
