> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/using-elements/project-and-publishing/publishing.md).
# Publishing
Export your project locally or online
When you are ready to publish, open Project Settings and select **Publishing** in the sidebar to create a publishing destination.
Elements can publish to the following locations and services:
* Local (to your Mac)
* FTP
* SFTP / FTPS
* Amazon S3
Publishing your site is an exciting moment: you’ll be able to enter a website address into Safari and see the fruits of your work.
You may need to adjust a few options before publishing because hosting providers use different server configurations.
Your hosting provider supplies the connection details entered into Elements; Realmac Software does not have access to them. These details may differ from the credentials used to access your hosting control panel. If you are unsure what to enter, contact your hosting provider.
We also run a dedicated hosting service built specifically for Elements websites. No unnecessary complexity. Just fast, reliable hosting that works flawlessly and gets out of your way. [Learn more about Element Hosting](https://docs.realmacsoftware.com/elements-docs/hosting).
## How to Fix Publishing Issues
If you have trouble publishing your website, follow our detailed [publishing troubleshooting guide](/elements-docs/getting-started/troubleshooting/fixing-issues.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://docs.realmacsoftware.com/elements-docs/using-elements/project-and-publishing/publishing.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.
