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

# Project and Publishing

Configure, preview, publish and safely move an Elements project

This section covers the settings and checks that turn an Elements project into a published website.

### Project Settings

[Project Settings](/elements-docs/using-elements/project-and-publishing/site-settings.md) contains site-wide details and configuration:

* **General** — Website title, primary address, language, logo, and appearance.
* **Web Icons** — Favicons and related website icons.
* **Advanced Settings** — Preview and project-level technical options.
* **Site Template** — HTML applied during preview and export.

### Browser Preview

Use [Browser Preview](/elements-docs/using-elements/project-and-publishing/previewing-your-website.md) to test the generated site in a real browser before publishing. Check every page, breakpoint, form, link, and interactive component.

### Publishing

[Publishing](/elements-docs/using-elements/project-and-publishing/publishing.md) explains how to export locally or publish with FTP, FTPS, or SFTP.

### Syncing Projects

[Syncing Projects](/elements-docs/using-elements/project-and-publishing/syncing-projects.md) covers safely working on the same project across multiple Macs.

{% hint style="info" %}
Preview the complete site before every important publish, especially after changing Project Settings, the Site Template, page extensions, or shared Globals.
{% endhint %}


---

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