On this page 2 entries
Choose a way to deploy
There are two ways to take the site live: TinaCloud if the owner wants to edit content on the live site, a static export if the site rarely changes.
The two ways side by side
| Way 1: TinaCloud | Way 2: Static export | |
|---|---|---|
| Where content is edited | The admin on the live site, from any computer | The admin on the developer’s computer |
| Needs | A GitHub repo, a TinaCloud account, a host that builds from Git | Any static host |
| After an edit | The host rebuilds, the site changes a few minutes later | Build and upload again by hand |
| Suits | Owners who edit content often | Sites that rarely change, or have someone to edit them |
| Cost | Hosting, plus a TinaCloud plan (see tina.io’s pricing) | Hosting only |
Each way in a paragraph
Edit content on the live site, from any computer. TinaCloud handles signing in to the admin and saves content to GitHub; the host rebuilds the site after each save.
| Build command | pnpm build |
| Build output directory | dist/client |
Every step is in 3.2 TinaCloud + Cloudflare Pages.
Build on your computer and upload dist/client/ to any static host. The admin doesn’t work online; to change content, edit locally, build and upload again.
SITE_URL=https://your-domain.com pnpm build:localEvery step is in 3.3 Static export.
Tip
Not sure? Start with the static export: it needs no account besides hosting. Moving to TinaCloud later still works, because content stays files in content/.