Core concepts

PageFork’s core concepts are sites (projects), pages (URLs), versions (snapshots of every edit), credits (the unit of AI work), and hosting subscriptions (per-site monthly or yearly plans). This page defines each one.

You don’t have to memorise it — but if you read it once, every other doc will make more sense.

Site

A site is one project. It has its own editor, its own chat history, its own pages, and its own publish settings. You can have many sites under a single account. New sites show up in the sidebar under Recent Sites, and the full list lives under All Sites.

Page

A page is one URL within a site, e.g. /, /pricing, /about. A site can have one page or many. PageFork decides which pages to create based on your prompts — you can always add more by asking (“add a pricing page”).

Version

Every edit produces a new version of the site. Versions are what power undo/redo — you can roll back at any point without losing your chat history. The version shown in the preview is the current one; publishing freezes one specific version and serves it from the public URL.

Block

A block is any visible element on your page — a headline, a card, a button, a pricing row, a footer link. Blocks are what you point at when you want to change “this specific thing” instead of the whole section. See Selecting blocks for how to reference them in chat.

Chat message

The editor has two kinds of messages:

• Edit — PageFork generates a new version of the site.
• Discuss — PageFork answers a question or brainstorms with you, but doesn’t change the site.

Both consume credits, but Discuss is usually cheaper. See Edit vs Discuss.

Credit

A credit is the unit of AI usage. Each generation, edit, retry, or discuss message consumes credits based on how much the AI has to think and write. You buy credits in packs. See Credits explained.

Hosting subscription

A hosting subscription is what puts a site on the internet. One subscription covers one site, billed monthly or yearly. Without an active subscription for a site, you can still edit and preview it — you just can’t publish it to a live URL. See Hosting subscriptions.

Subdomain

Every site gets a free *.pagefork.ai subdomain as soon as it’s published (e.g. acme.pagefork.ai). You can change the subdomain label at any time. See Your PageFork subdomain.

Custom domain

A custom domain is a domain you own (like acme.com) that you point at your PageFork site. It requires an active hosting subscription and a quick DNS setup. SSL is automatic. See Connecting your domain.

The lifecycle, visually

prompt/template
     │
     ▼
  version 1  ──edit──▶  version 2  ──edit──▶  version 3  …
                                                   │
                                                   ▼ publish
                                              live at
                                              acme.pagefork.ai
                                              (or acme.com)

Every edit creates a new version. Publishing snapshots one version and serves it. Editing after publishing creates new versions without affecting the live site — until you publish again.