Glossary

Need a definition? This glossary explains every PageFork concept in one sentence, with a link to the full article when one exists.

Core concepts

Site

A site is one PageFork project — one set of pages, one style, one domain. Every site has its own version history, submissions inbox, and hosting subscription.

Page

A page is a single URL inside a site (for example, the home page, an about page, or a pricing page). PageFork sites can be single-page or multi-page; you control this with prompts.

Generation

A generation is the first-time creation of a site from your prompt. Generation uses generation credits and typically finishes in under a minute.

Edit

An edit is any change you make to an existing site by typing an instruction in plain English. Edits use edit credits.

Prompt

A prompt is the natural-language instruction you type to generate or edit a site (for example, “Create a landing page for a dog-training business in Austin”).

Version

A version is a saved snapshot of your site at a point in time. Every generation and every edit creates a new version. You can preview any version, revert to it, or fork from it.

Fork

A fork is a branch of your version history. Forking lets you explore an alternative direction without losing the current one — useful when you want to try a redesign or test a different hero.

Fork tree

The fork tree is the full graph of versions and forks for a site. It’s how you navigate and compare directions.

AI & editing

Edit vs Discuss

Edit mode applies your instruction to the site. Discuss mode answers questions about the site or brainstorms changes without modifying anything. See Edit vs Discuss.

Block selection

Block selection lets you click a specific section of the preview (hero, pricing card, FAQ) and scope an edit to just that block — the fastest way to iterate on one piece without disturbing the rest. See Selecting blocks.

Reference image

A reference image is an image you attach to a prompt so PageFork can match its style, layout, or mood. See Reference images.

Credits & billing

Credit

A credit is PageFork’s unit of AI work. Credits are consumed by generations and edits. Credits never expire.

Generation credit

A generation credit is spent the first time you turn a prompt into a site.

Edit credit

An edit credit is spent each time you change an existing site with a prompt.

Hosting subscription

A hosting subscription is the per-site monthly or yearly plan that keeps a site live on PageFork’s CDN with SSL. One subscription per published site.

Apex domain

An apex (or root) domain is the bare domain without a subdomain — for example, pagefork.ai. The opposite is www.pagefork.ai. See Apex vs WWW.

Publishing & domains

Publish

To publish a site is to make its current version live at its connected URL (either *.pagefork.ai or a custom domain).

Unpublish

To unpublish a site is to take it offline while keeping all its versions and submissions intact.

PageFork subdomain

Every site gets a free *.pagefork.ai subdomain automatically. See Your PageFork subdomain.

Custom domain

A custom domain is any domain you own, connected to a PageFork site via two DNS records. See Connecting your domain.

SSL certificate

PageFork automatically issues and renews a free SSL certificate (via Let’s Encrypt) for every custom domain once DNS verification succeeds.

Forms & submissions

Form

A form is a lead-capture block on a page (contact, waitlist, booking). PageFork generates forms from your prompt and stores submissions in the inbox.

Submission

A submission is one entry someone made by filling out a form on your site. Submissions live in the site’s inbox and can be exported to CSV.

Field schema

A field schema is the set of fields and validation rules for a form (name, email, message, custom fields). See Form field schemas.

---

Missing a term? Email support@pagefork.ai and we’ll add it.