Getting Started
By the end of this page you will have an account, a site with a published post, a build, and (if you connect Cloudflare Pages) a live URL. It takes about ten minutes.
Create your account
Sign up
Open the sign-up page and enter your name, your email, and a password of at least 8 characters. If your server has social login configured, “Continue with Google / Apple / Microsoft / Facebook” buttons appear above the form. If it does not, they are simply not rendered.
Check your email
Sign-up always lands on the same “check your email” screen, even when the address already has an account. That is deliberate: the response never reveals which addresses are registered. Open the verification link in the message to activate the account.
Sign in
Return to the sign-in page with your email and password. Forgot it? Use the “forgot password” link, which mails a reset token.
Create your first site
A brand new account has no sites, so the sites list sends you straight to the new-site form.
You need one field: Site Name. The slug is generated from the name as you type (you can override it, but it cannot be changed after the site is created). Everything else lives under Advanced options:
- Database: leave it on Internal Built-in to use the managed SQLite database. You can attach your own PostgreSQL or MySQL connection later and migrate to it.
- Domain: optional. You can set it later, and you will want the site deployed first anyway.
Creating the site drops you on its Posts page with a four step “Get your site live” checklist: create your first post, publish it, build the site, deploy it. The checklist is dismissible and only shows for a freshly created site.
Write and publish a post
Choose New Post. Title, slug (auto-generated from the title), and body are the only things you need. The editor page also carries a feature image card, a tag selector, an SEO panel, and a status control.
Set Status to published and save. Draft posts are excluded from builds unless you turn on “Include draft posts in build” in generation settings.
Build the site
Go to Settings, Generation. Fill in at least:
- Site Title and Site Description, used in page titles, meta tags, and feed metadata.
- Site URL, the base URL used for canonical links and the sitemap.
Press Save SSG Settings, then Build Site. A build renders every published post and page, plus archives, tag pages, a 404 page, rss.xml, atom.xml, sitemap.xml, robots.txt, llms.txt, and llms-full.txt, and copies your theme assets and media into the output directory. After a successful build the page shows a “Last built” timestamp and a Download button that hands you the whole output as a zip.
Deploy it
Deployment goes to Cloudflare Pages.
Connect Cloudflare Pages
On the site’s Platforms page choose Connect platform and pick Cloudflare Pages. The dialog walks you through creating a custom API token with Account, Cloudflare Pages: Edit and Account, Account Settings: Read. Add Zone, DNS: Edit and Zone, Zone: Read if you want WordPuppi to point your custom domain’s DNS record for you. Paste the token and press Verify Token; the account id is filled in for you.
Build and deploy
Back on Settings, Generation, the “Deploy to Cloudflare Pages” card is now live. Press Build & Deploy. WordPuppi rebuilds the site and uploads the output with Cloudflare’s direct upload API, creating the Pages project if it does not exist yet (the project is named after your site slug by default). The toast shows the deployment URL, and the card keeps a link to the latest deployment.
Attach a domain (optional)
Type a hostname into Custom Domain and press Save. WordPuppi registers it on the Pages project and, when your token has zone permissions, rewrites the DNS record to a proxied CNAME at <project>.pages.dev. The card then polls Cloudflare until the domain reads “Active on Cloudflare Pages”.
Where to next
Accounts, seats, sites, content types, and how they nest.
Posts and pagesStatuses, SEO fields, tags, and modelling your own content types.
Themes and blueprintsFork a theme, edit its colors and fonts, and reuse it across sites.
Media and formsUploads, static files, form building, and spam protection.
Bark and distributionPush published posts to the platforms you have connected.
API and MCPAPI keys, the REST surface, and driving WordPuppi from an AI client.