wptom new

npx wptom new my-site -t aurora

Downloads the latest version of a template and creates a site from it in a new folder. wptom create does the same. Prefer answering questions? npm create wptom@latest.

Usage

wptom new [dir] [-t <template>] [--cms <name>]

Part	Meaning	If you leave it out
dir	The folder to create, e.g. my-site or ../clients/acme	Asked, suggesting ./my-<template>-site
-t, --template	The template’s short name (its slug), e.g. aurora. wptom list shows them	Asked: a list of templates, with ones you can’t use marked 🔒
--cms	Where the content lives (below)	Asked, if the template has variants

The folder must not exist yet, or be empty. Otherwise: my-site isn't empty. Pick a new folder.

PRO templates need wptom login first; without it you get aurora is a PRO template. Run wptom login first.

Where the content lives

Some templates come in variants. --cms picks one; without it, wptom new asks:

◆  Where should the content live?
│  ● Files or Sanity (static site, any host)
│  ○ EmDash (EmDash inside the site: admin at /_emdash/admin, rendered on request on Cloudflare Workers (D1 + R2).)

--cms	You get
files (also keystatic, sanity or default)	The default: content as Markdown and JSON files in your project, edited in Keystatic; switch to Sanity with one setting. A static site for any host. See Content and CMS.
emdash	EmDash runs inside your site on Cloudflare, with a WordPress-like admin. See EmDash.

An option the template doesn’t have: aurora has no "wordpress" option. Pick one of: files, sanity, emdash. Nothing is created in that case.

The choice is remembered, so wptom update keeps updating the same variant.

What happens

1. The CLI asks app.wptom.com for the template (with your device token for PRO), downloads the release and checks its checksum (Checksum mismatch: the download is corrupted. Try again. if it doesn’t match).
2. It applies the variant you picked.
3. It writes the files, names the project in package.json after your folder, and saves .wptom/meta.json and .wptom/base/ (see files).
4. It prints the next steps:

◇  Created my-site from aurora@1.0.0
│
◇  Next steps ───╮
│                │
│  cd my-site    │
│  npm install   │
│  npm run dev   │
│                │
├────────────────╯
│
└  Updates later: wptom update keeps your edits.

Nothing is installed or run for you: npm install and npm run dev are yours to run (step by step).

Examples

npx wptom new                                 # asks for everything
npx wptom new client-site -t aurora           # into ./client-site
npx wptom new shop -t aurora --cms sanity     # content in Sanity (same files, CMS set later)
npx wptom new blog -t aurora --cms emdash     # the EmDash variant