Sites and Settings
Every site has a Settings section with five pages: General, Generation, Databases, Email, and API Keys. This page tells you what each field actually does at build time and at run time.
General
The basics of the site record itself.
- Site Name is editable at any time.
- Slug is shown read only. It is fixed at creation.
- Database shows where content lives right now, with a Migrate… button that opens the migration wizard.
- Domain is the custom hostname. If you have Cloudflare Pages connected, the domain you set here is added to the Pages project on your next deploy.
A Fediverse / ActivityPub card sits below it.
The Danger Zone deletes the site. That removes its content permanently, posts, pages, and media included.
Generation
This is the static site generator’s configuration, and the page you build and deploy from.
| Field | What it drives |
|---|---|
| Site Title | page titles and feed metadata |
| Site Description | SEO meta tags and feed metadata |
| Site URL | canonical links, sitemap entries, and the Sitemap: line in robots.txt |
| Language | the site language code, default en |
| Author | author metadata |
| Theme | which bundled theme the build renders with |
| Homepage | a page to serve as /, or the default post listing |
| Favicon | uploaded through the media library and copied to the output root |
| Nav Button Text / URL | the call to action button in the theme’s navigation |
| Output Directory | where the build is written, default ./dist/{slug} |
| Include draft posts | when on, drafts are rendered into the build |
Build Site runs a full production build (clean output, minified HTML). Afterwards the page shows the last build time and a Download button that hands you the output as a zip.
The Deploy to Cloudflare Pages card is greyed out with a link to Platforms until you connect Cloudflare. Once connected it gives you a custom domain field and a Build & Deploy button. See Publishing and Custom Domains.
Databases
Two things live here.
Saved connections are stored on the account, so a connection you add once can be picked when creating any site. A connection is one of:
- a Supabase project
- a plain PostgreSQL or MySQL connection string
- a connection string reached over an SSH tunnel
You can test a connection before saving it, and test a saved one at any time. Credentials are encrypted at rest and only ever read back as a masked preview.
Content Database tells you where this site’s content is right now: the WordPuppi hosted database, your own external PostgreSQL or MySQL, or (in the desktop app) a local file after a detach.
SMTP settings for the mail this site sends: form notifications, confirmations, and newsletter sends.
Pick a provider (Postmark, SendGrid, Mailchimp/Mandrill, Brevo) to prefill host and port, or choose Custom and type your own. Then fill in username, password, from address, from name, and reply-to.
API Keys
Keys for MCP servers, CI pipelines, automation tools, and anything else that talks to the REST API.
- Keys are per user and grant full access to your account, not to one site.
- A new key is displayed once, in full. After that only a masked preview (
lo-abcd...wxyz) is shown, along with the created and last used dates. - Revoke deactivates a key and keeps the row. Delete removes it entirely.
The page also prints two ready to copy snippets: an MCP server config block, and the two step curl flow that exchanges an API key for a JWT. Both are covered in API and MCP.
Search Console
Not under Settings, but worth knowing about: the site’s Search page connects Google Search Console with OAuth and then shows clicks, impressions, CTR, and average position for your pages. It is env-gated. If the server has no Google OAuth client configured, the page reports “not configured” rather than failing.