create-jant 0.3.46 → 0.3.48

package/dist/index.js

@@ -9,7 +9,7 @@ import path from "path";
 import { fileURLToPath } from "url";
 var __filename = fileURLToPath(import.meta.url);
 var __dirname = path.dirname(__filename);
-var CORE_VERSION = "0.3.46";
+var CORE_VERSION = "0.3.48";
 var WRANGLER_VERSION = "^4.76.0";
 var TEMPLATE_DIR = fs.existsSync(path.resolve(__dirname, "../template")) ? path.resolve(__dirname, "../template") : path.resolve(__dirname, "../../../sites/demo");
 function isValidProjectName(name) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-jant",
-  "version": "0.3.46",
+  "version": "0.3.48",
   "description": "Create a new Jant project",
   "type": "module",
   "bin": {

package/template/.agents/skills/building-jant-site/SKILL.md

@@ -23,7 +23,7 @@ Do not patch `node_modules/@jant/core`.
 
 If the change is product behavior that should apply to all Jant sites, make it in the Jant monorepo. If the change is site-specific, keep it in:
 
-- dashboard settings
+- the Settings page
 - custom CSS
 - site docs or helper scripts
 - `wrangler.toml`
@@ -50,7 +50,7 @@ This already runs local migrations before starting Wrangler dev.
 
 ### 2. Pick the right customization layer
 
-- Content or editorial defaults: use the dashboard or the HTTP API
+- Content or editorial defaults: use the Settings page or the HTTP API
 - Theme and layout changes: use Settings plus custom CSS
 - Deployment and runtime config: edit `wrangler.toml`
 - One-off site behavior at the server edge: wrap `createApp()` in `index.js`

package/template/.agents/skills/jant-http-api/SKILL.md

@@ -15,22 +15,6 @@ Use one of these:
 - `Authorization: Bearer jnt_...` API token
 - local `DEV_API_TOKEN` on localhost-style hosts
 
-## Prefer Local CLI First
-
-When you already have shell access to the site directory, prefer the built-in `jant` CLI for common automation:
-
-```bash
-npx jant posts list --limit 20
-npx jant posts create --input ./post.json
-npx jant media upload ./photo.webp --alt "Cover image"
-npx jant media list --mimePrefix image/
-npx jant collections add-post col_... pst_...
-npx jant settings get
-npx jant search "quiet design"
-```
-
-The CLI uses the same site URL and token model as the HTTP API.
-
 ## Built-in MCP
 
 Jant also exposes a built-in MCP endpoint at `/api/mcp`.
@@ -39,7 +23,7 @@ Jant also exposes a built-in MCP endpoint at `/api/mcp`.
 - tools: posts, media, collections, settings, and search
 - protocol: streamable HTTP request/response shape with `initialize`, `tools/list`, and `tools/call`
 
-Use MCP when the caller already speaks MCP. Use the CLI or plain HTTP when you just need a direct script.
+Use MCP when the caller already speaks MCP. Use plain HTTP when you just need a direct script.
 
 Generated sites also include worked examples in `examples/agent-content-automation/`.
 
@@ -104,24 +88,19 @@ curl -X PUT "$JANT_URL/api/posts/pst_..." \
 
 ## Uploads
 
-For scripted clients, prefer the local CLI:
-
-```bash
-npx jant media upload ./photo.webp --alt "Cover image"
-```
-
 For raw HTTP clients, use the recommended upload session flow:
 
 1. `POST /api/uploads/init`
 2. upload bytes to the returned transport
 3. `POST /api/uploads/:id/complete`
 
-For simple agent scripts, the legacy one-shot endpoint can be easier:
+For simple agent scripts, the legacy one-shot endpoint is easier:
 
 ```bash
 curl -X POST "$JANT_URL/api/upload" \
   -H "Authorization: Bearer $JANT_API_TOKEN" \
-  -F "file=@./photo.jpg"
+  -F "file=@./photo.jpg" \
+  -F "alt=Cover image"
 ```
 
 Use the returned `med_*` ID inside a post attachment:

package/template/.agents/skills/jant-site-ops/SKILL.md

@@ -32,8 +32,8 @@ What they do:
 ```bash
 npx jant migrate --local
 npx jant migrate --remote --config ./wrangler.toml
-npx jant site export --output ./jant-site-export.zip
-npx jant site import --path ./jant-site-export.zip --dry-run
+npx jant site export https://your-site.example --output ./jant-site-export.zip
+npx jant site import https://your-site.example --path ./jant-site-export.zip --dry-run
 npx jant site snapshot export --output ./jant-site-snapshot.zip
 npx jant site snapshot import --path ./jant-site-snapshot.zip --replace
 npx jant db export --output ./jant-export.sql
@@ -69,16 +69,16 @@ npx jant uploads cleanup --help
 
 Use `assets prepare` when you need the publishable asset directory assembled locally.
 
-## Remote Operations
+## Authentication
 
-Remote site export/import can use an API token:
+`site export` and `site import` always target a deployed site URL and require an API token:
 
 ```bash
 export JANT_API_TOKEN=jnt_your_token
-npx jant site export --url https://your-site.example --output ./jant-site-export.zip
+npx jant site export https://your-site.example --output ./jant-site-export.zip
 ```
 
-For remote D1-oriented commands, pass `--remote` and your Wrangler config when needed.
+For D1-oriented commands like snapshot export and `db export`, pass `--remote` and your Wrangler config when needed.
 
 ## Gotchas
 

package/template/AGENTS.md

@@ -11,11 +11,11 @@ This is a standalone Jant site created with `create-jant`.
 
 Most customization happens through:
 
-- site settings in the dashboard
+- site settings from the Settings page
 - custom CSS and theme variables
-- HTTP API calls
-- `jant` CLI commands for posts, collections, settings, search, export, import, migrate, and deploy
+- HTTP API calls for content (posts, media, collections, settings, search)
 - the built-in MCP endpoint at `/api/mcp` for remote agent tooling
+- `jant` CLI commands for local-only ops: export, import, migrate, deploy, snapshot, reset-password
 - examples in `examples/agent-content-automation/`
 
 Do not edit `node_modules/@jant/core`. If you need reusable product changes, make them in the Jant monorepo instead.
@@ -29,16 +29,13 @@ npm run export
 npm run reset-password
 
 npx jant migrate --local
-npx jant posts list --limit 20
-npx jant media list --mimePrefix image/
-npx jant collections list
-npx jant settings get
-npx jant search "quiet design"
-npx jant site export --output ./jant-site-export.zip
-npx jant site import --path ./jant-site-export.zip --dry-run
+npx jant site export https://your-site.example --output ./jant-site-export.zip
+npx jant site import https://your-site.example --path ./jant-site-export.zip --dry-run
 npx jant db export --output ./jant-export.sql
 ```
 
+Content automation (posts, media, collections, settings, search) goes through the HTTP API or `/api/mcp`. See `.agents/skills/jant-http-api/SKILL.md` and `examples/agent-content-automation/`.
+
 Use `npm run deploy` for normal Cloudflare deploys. It applies remote migrations and prepares assets before calling Wrangler.
 
 ## Skills
@@ -53,8 +50,7 @@ Load the matching skill before making substantive changes:
 
 - Keep `index.js` minimal unless the site truly needs custom server behavior.
 - Prefer settings, custom CSS, and documented extension points before changing runtime code.
-- Prefer local `npx jant posts`, `collections`, `settings`, and `search` commands for scripted automation when you are already on the site machine.
-- Use `npx jant media` for file uploads, media listing, text attachment reads, alt updates, and deletes.
+- Use the HTTP API (`/api/posts`, `/api/upload`, `/api/collections`, `/api/settings`, `/api/search`) for scripted content automation. The CLI no longer covers content — those commands were removed because they were thin HTTP wrappers.
 - Use `/api/mcp` when an MCP client is available and you need the site to expose posts, collections, settings, or search as tools.
 - Start from `examples/agent-content-automation/README.md` if the task is content automation rather than app development.
 - Use `bodyMarkdown` in API scripts instead of raw TipTap JSON unless you already have trusted editor output.

package/template/README.md

@@ -105,12 +105,12 @@ Open `http://localhost:3000`.
 
 ## Common Commands
 
-| Command                                                | Description                           |
-| ------------------------------------------------------ | ------------------------------------- |
-| `npm run dev`                                          | Start local development               |
-| `npm run deploy`                                       | Apply remote migrations and deploy    |
-| `npm run reset-password`                               | Generate a password reset token       |
-| `npx jant site export --output ./jant-site-export.zip` | Export the site as a portable archive |
+| Command                                                                          | Description                           |
+| -------------------------------------------------------------------------------- | ------------------------------------- |
+| `npm run dev`                                                                    | Start local development               |
+| `npm run deploy`                                                                 | Apply remote migrations and deploy    |
+| `npm run reset-password`                                                         | Generate a password reset token       |
+| `npx jant site export https://your-site.example --output ./jant-site-export.zip` | Export the site as a portable archive |
 
 ## Configuration
 

package/template/examples/agent-content-automation/README.md

@@ -2,24 +2,42 @@
 
 This folder shows the shortest path for content automation in a generated Jant site.
 
-Prefer the local CLI when the agent is already on the site machine. Use MCP only when the caller already speaks MCP.
+All content operations go through the HTTP API. Use MCP (`/api/mcp`) only when the caller already speaks MCP.
+
+Set these once:
+
+```bash
+export JANT_URL="https://your-site.example"
+export JANT_API_TOKEN="jnt_..."
+```
+
+For local development, `JANT_URL=http://localhost:8787` and `JANT_API_TOKEN=$DEV_API_TOKEN`.
 
 ## Publish a note from JSON
 
 ```bash
-npx jant posts create --input ./examples/agent-content-automation/note.json
+curl -X POST "$JANT_URL/api/posts" \
+  -H "Authorization: Bearer $JANT_API_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d @./examples/agent-content-automation/note.json
 ```
 
 ## Publish a quote from JSON
 
 ```bash
-npx jant posts create --input ./examples/agent-content-automation/quote.json
+curl -X POST "$JANT_URL/api/posts" \
+  -H "Authorization: Bearer $JANT_API_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d @./examples/agent-content-automation/quote.json
 ```
 
 ## Update site settings from JSON
 
 ```bash
-npx jant settings update --input ./examples/agent-content-automation/site-settings.json
+curl -X PUT "$JANT_URL/api/settings" \
+  -H "Authorization: Bearer $JANT_API_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d @./examples/agent-content-automation/site-settings.json
 ```
 
 ## Upload an image, then attach it to a post
@@ -27,7 +45,10 @@ npx jant settings update --input ./examples/agent-content-automation/site-settin
 Upload the file:
 
 ```bash
-npx jant media upload ./path/to/photo.webp --alt "Cover image"
+curl -X POST "$JANT_URL/api/upload" \
+  -H "Authorization: Bearer $JANT_API_TOKEN" \
+  -F "file=@./path/to/photo.webp" \
+  -F "alt=Cover image"
 ```
 
 That returns a `med_*` ID. Use it in a post payload:
@@ -36,7 +57,7 @@ That returns a `med_*` ID. Use it in a post payload:
 {
   "format": "note",
   "title": "A post with media",
-  "bodyMarkdown": "Uploaded through the local CLI.",
+  "bodyMarkdown": "Uploaded through the HTTP API.",
   "status": "published",
   "visibility": "public",
   "attachments": [{ "type": "media", "mediaId": "med_..." }]
@@ -46,7 +67,10 @@ That returns a `med_*` ID. Use it in a post payload:
 Then publish it:
 
 ```bash
-npx jant posts create --json '{"format":"note","title":"A post with media","bodyMarkdown":"Uploaded through the local CLI.","status":"published","visibility":"public","attachments":[{"type":"media","mediaId":"med_..."}]}'
+curl -X POST "$JANT_URL/api/posts" \
+  -H "Authorization: Bearer $JANT_API_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"format":"note","title":"A post with media","bodyMarkdown":"Uploaded through the HTTP API.","status":"published","visibility":"public","attachments":[{"type":"media","mediaId":"med_..."}]}'
 ```
 
 ## Inline text attachments stay in the post payload

package/template/examples/agent-content-automation/note.json

@@ -1,7 +1,7 @@
 {
   "format": "note",
   "title": "A short note",
-  "bodyMarkdown": "Published through the local CLI example.",
+  "bodyMarkdown": "Published through the HTTP API example.",
   "status": "published",
   "visibility": "public"
 }

package/template/examples/agent-content-automation/site-settings.json

@@ -1,5 +1,5 @@
 {
   "SITE_NAME": "Example Jant Site",
-  "SITE_DESCRIPTION": "Automated through the local CLI example.",
+  "SITE_DESCRIPTION": "Automated through the HTTP API example.",
   "TIME_ZONE": "Asia/Shanghai"
 }

package/template/wrangler.toml

@@ -29,8 +29,8 @@ SITE_ORIGIN = "https://demo.jant.me" # @create-jant: @remove
 # SITE_PATH_PREFIX = "/blog"
 
 # Optional: Site configuration
-# You can also set these in the dashboard UI at /dash/settings
-# https://github.com/jant-me/jant/blob/main/docs/configuration.md#dashboard-settings
+# You can also set these from the Settings page at /settings
+# https://github.com/jant-me/jant/blob/main/docs/configuration.md#settings-page
 # SITE_NAME = "My Blog"
 # SITE_DESCRIPTION = "A personal blog powered by Jant"
 # SITE_LANGUAGE = "en"