Publishing

Frontage builds your site as static files and puts it on Cloudflare Pages. Each site has a Pages project of its own, named frontage- followed by the site's name.

Share a preview

Press Share a preview on the site's page in the app, or Deploy… then Share a preview in the editor. Frontage builds the site as it is saved now and gives it an address of its own on pages.dev, which you can send to anyone. Previews never change the live site.

Designers, developers and owners can share previews.

Go live

Press Go live… and confirm. Frontage builds the saved site, publishes it to its public address, https://frontage-<site>.pages.dev, and saves the change as one commit on the main branch of the site's repository. Developers and owners can go live.

A publish goes through four steps, shown as it runs: getting the latest version, building the site, sending it to Cloudflare, and checking it is up. The first publish of a new site can take a few minutes to answer; later ones are quicker. If the build fails, nothing is published and the live site stays as it was.

The site's page lists recent publishes, with who started each one and its address.

Your own domain

Once a site has had a preview or gone live, open its page in the app and find Your own domain. Enter the domain, for example www.example.com, and press Connect domain. Then, where your domain's DNS is managed, add the one record the page shows:

Type   Name              Value CNAME  www.example.com   frontage-<site>.pages.dev

It can take a few minutes to an hour for the domain to go live; press Check again to see its state. A bare domain such as example.com works when its DNS is on Cloudflare; elsewhere, use www. A site can have up to 10 domains, on every plan.

Sites imported from GitHub

An imported site publishes as a pull request on its own repository. If it builds as a static site, it can also have previews and go live on Frontage. If it does not, your own hosting deploys it when the pull request merges. See Developers.