create-smoodly-app 0.0.50 → 0.0.52

package/package.json

@@ -1,11 +1,11 @@
 {
   "name": "create-smoodly-app",
-  "version": "0.0.50",
-  "description": "Create a Smoodly site: a fresh Next.js app with the admin mounted, a Supabase schema, an env file and a first editor.",
+  "version": "0.0.52",
+  "description": "Create a Smoodly site: a fresh Astro or Next.js app with the admin mounted, its env file on a space's three values, its schema pushed and its starter content seeded.",
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/laniakea-studio/smoodly-cms.git",
+    "url": "git+https://github.com/smoodly-io/smoodly.git",
     "directory": "packages/create-smoodly-app"
   },
   "type": "module",
@@ -29,8 +29,7 @@
     "typecheck:templates": "npm run build:template && tsc -p templates/lorem.tsconfig.json && tsc -p templates/lorem-intl.tsconfig.json && tsc -p templates/blank.tsconfig.json && tsc -p templates/blank-intl.tsconfig.json && tsc -p templates/astro-lorem.tsconfig.json && tsc -p templates/astro-lorem-intl.tsconfig.json && tsc -p templates/astro-blank.tsconfig.json && tsc -p templates/astro-blank-intl.tsconfig.json"
   },
   "dependencies": {
-    "@clack/prompts": "^1.7.0",
-    "@supabase/supabase-js": "^2.113.0"
+    "@clack/prompts": "^1.7.0"
   },
   "devDependencies": {
     "@types/node": "^26.4.1",

package/templates/astro-blank/AGENTS.md

@@ -1,6 +1,6 @@
 # Working in this Smoodly site
 
-This is an Astro site with Smoodly installed: content lives in Supabase, the admin is mounted at /admin by the `smoodly/astro` integration in `astro.config.ts`, and the site reads content through live collections (`src/live.config.ts`). Read README.md first: it says where things are.
+This is an Astro site with Smoodly installed: content lives in Smoodly's service, reached through the API, the admin is mounted at /admin by the `smoodly/astro` integration in `astro.config.ts`, and the site reads content through live collections (`src/live.config.ts`). Read README.md first: it says where things are.
 
 ## Rules
 
@@ -14,12 +14,6 @@ This is an Astro site with Smoodly installed: content lives in Supabase, the adm
   names a schema with no file, and a file with no schema, at the first request.
 - **A `.schema.ts` file imports no component.** Zones, toolsets, global items and
   `node()` take schemas (`z.locked(heroSchema)`), never views.
-- **After a new collection or a `smoodly` upgrade, run `npx smoodly migrate`**
-  and apply what it writes (`supabase db push` hosted, `supabase migration up`
-  local). It copies the core schema files the package ships and writes a
-  read view and order index per collection. Never edit a file it wrote.
-  The admin reads the base tables, so it lists a collection either way;
-  the view is for SQL and PostgREST readers, the index for `order`.
 - **Content from code goes through `createContent(config)`** from `smoodly/astro`:
   `scripts/seed.ts` is starter content written with it — the admin's own
   operations, so validation and publish checks apply and a failure throws. Never
@@ -49,7 +43,7 @@ This is an Astro site with Smoodly installed: content lives in Supabase, the adm
 ## Commands
 
     npm run dev          # http://localhost:4321, /admin is the editor
-    npm run build        # checks the schema files (smoodly migrate --check), then astro build
+    npm run build        # astro build
     npm run start        # the built server (dist/server/entry.mjs)
     npm run seed         # starter content, idempotent
     npm run typecheck    # astro check

package/templates/astro-blank/README.md

@@ -1,8 +1,8 @@
 # Smoodly site
 
-Created by `create-smoodly-app`. Content lives in Supabase; the admin is
-mounted at `/admin` by the `smoodly/astro` integration. AGENTS.md holds the
-rules for an agent (or a person) building the site.
+Created by `create-smoodly-app`. Content lives in Smoodly's service; the
+admin is mounted at `/admin` by the `smoodly/astro` integration. AGENTS.md
+holds the rules for an agent (or a person) building the site.
 
     npm run dev          # http://localhost:4321 — /admin is the editor
 
@@ -19,7 +19,7 @@ rules for an agent (or a person) building the site.
 - `src/live.config.ts` — the live collections the views read with `getLiveCollection` and `getLiveEntry`.
 - `scripts/seed.ts` — the home page and the site item, written through `createContent(config)`. `npm run seed` is idempotent.
 - `src/styles/global.css` — a reset, a container, the two tones. Replace it.
-- `.env` — `SMOODLY_URL`, `SMOODLY_SECRET_KEY`, `SMOODLY_PUBLISHABLE_KEY`.
+- `.env` — `SMOODLY_SPACE_ID`, `SMOODLY_SECRET_KEY`, `SMOODLY_PUBLISHABLE_KEY` (the space's values from smoodly.io) and `SITE_URL`.
 
 ## Add a section
 
@@ -46,13 +46,7 @@ editor's "/" menu.
 Copy the `posts` block in `src/smoodly/collections.ts`, add the new
 collection to `collections` and a loader for it in `src/live.config.ts`,
 and write its entry page, `src/entry-pages/<collection>.astro`, by
-copying `posts.astro`. Then write its read view and order index and
-apply them:
-
-    npx smoodly migrate
-    supabase db push        # hosted; `supabase migration up` for the local stack (keeps the content)
-
-The same command brings the core schema forward after a `smoodly` upgrade.
+copying `posts.astro`.
 
 ## Add a global item
 
@@ -60,7 +54,7 @@ Copy the `site` block in `src/smoodly/globals.ts`, add it to `globals`
 and give it a loader in `src/live.config.ts`. A view reads it with
 `getLiveEntry("name", { locale })`. Edit it under Globals in the admin.
 
-Reseed an empty database any time with `npm run seed`.
+Reseed an empty space any time with `npm run seed`.
 
 ## Moving the admin
 
@@ -73,16 +67,12 @@ The two must agree; the admin says so when they do not.
 
 ## Editors
 
-Anyone who may open `/admin` is a Supabase Auth user with a row in the
-`editors` table. To add one: create the user in Supabase Studio
-(Authentication → Users), then in the SQL editor:
-
-    insert into editors (user_id, role) values ('<the user id>', 'editor');
-
-## Hosted Supabase
+Editors sign in at `/admin` with their smoodly.io account. Colleagues are
+invited from the project at smoodly.io; the admin's Members page lists them.
 
-    supabase init        # if the CLI has not been set up here yet
-    supabase link        # pick the project
-    supabase db push     # applies supabase/migrations/
+## Deploying
 
-Then put the project's URL and keys in `.env`.
+`.env` holds the preview space's values, for development. Where you
+deploy, set the production space's three values and `SITE_URL` in the
+host's environment variables; each build pushes the
+schema to its space. https://smoodly.io/docs/getting-started/deploying

package/templates/astro-blank/package.json

@@ -4,16 +4,15 @@
   "type": "module",
   "scripts": {
     "dev": "astro dev",
-    "build": "smoodly migrate --check && astro build",
+    "build": "astro build",
     "start": "node --env-file-if-exists=.env dist/server/entry.mjs",
     "seed": "tsx scripts/seed.ts",
     "typecheck": "astro check"
   },
   "dependencies": {
     "@astrojs/node": "^11.1.6",
-    "@supabase/supabase-js": "^2.113.0",
     "astro": "^7.3.5",
-    "smoodly": "0.0.50"
+    "smoodly": "0.0.52"
   },
   "devDependencies": {
     "@astrojs/check": "^0.9.10",

package/templates/astro-blank/scripts/seed.ts

@@ -2,12 +2,18 @@
 // from smoodly/astro): the admin's own operations, so validation and
 // the publish checks apply and a failure throws. It is also the example
 // of writing content from code. Ships in the scaffold; create-smoodly-app
-// runs `npm run seed` after the first editor. Idempotent: exits once the
+// runs `npm run seed` after it pushes the schema. Idempotent: exits once the
 // home page has content in the default locale. Writes the same copy into every configured locale, whatever
 // their codes, so every locale's "/" resolves.
-// Run: npm run seed  (needs .env and a Supabase stack).
+// Run: npm run seed  (needs .env).
 import type { PageTree, TreeNode } from "smoodly";
 
+// A refusal from Smoodly's API (a space with no schema yet, a wrong key) prints its message and code, not a stack trace.
+process.on("uncaughtException", (e) => {
+  console.error(e.name === "SmoodlyContentError" ? `${e.message} (${(e as Error & { code?: string }).code})` : e);
+  process.exit(1);
+});
+
 const { config } = await import("../src/smoodly/config");
 const { node } = await import("smoodly");
 const { createContent } = await import("smoodly/astro");
@@ -19,7 +25,7 @@ const DEFAULT = config.locales.default;
 const OTHERS = config.locales.supported.filter((l) => l !== DEFAULT);
 
 // The home page is code-owned: `find` returns its record, creating it when
-// the database is new. It is seeded once somebody has given it sections.
+// the space is new. It is seeded once somebody has given it sections.
 const home = (await c.pages.find(DEFAULT, "/"))!;
 if (Object.values((await c.pages.getTree(home.id, DEFAULT))?.zones ?? {}).some((nodes) => nodes.length > 0)) {
   console.log(`Already seeded — the home page has content in "${DEFAULT}".`);

package/templates/astro-blank/src/smoodly/collections.ts

@@ -5,8 +5,8 @@ import { text } from "./toolsets";
 // `path` by its entry page (src/entry-pages/posts.astro). Fields marked
 // .localized() are stored per locale; the rest are shared across
 // locales. To add a collection: copy this block, add it to
-// `collections`, run `npx smoodly migrate` and apply the file it writes
-// (supabase db push, or supabase migration up locally).
+// `collections`; the dev server and every build push the change to your
+// space.
 export const posts = smoodly.collection({
   name: "posts",
   title: "Posts",

package/templates/astro-blank-intl/AGENTS.md

@@ -1,6 +1,6 @@
 # Working in this Smoodly site
 
-This is an Astro site with Smoodly installed: content lives in Supabase, the admin is mounted at /admin by the `smoodly/astro` integration in `astro.config.ts`, and the site reads content through live collections (`src/live.config.ts`). Read README.md first: it says where things are.
+This is an Astro site with Smoodly installed: content lives in Smoodly's service, reached through the API, the admin is mounted at /admin by the `smoodly/astro` integration in `astro.config.ts`, and the site reads content through live collections (`src/live.config.ts`). Read README.md first: it says where things are.
 
 ## Rules
 
@@ -14,12 +14,6 @@ This is an Astro site with Smoodly installed: content lives in Supabase, the adm
   names a schema with no file, and a file with no schema, at the first request.
 - **A `.schema.ts` file imports no component.** Zones, toolsets, global items and
   `node()` take schemas (`z.locked(heroSchema)`), never views.
-- **After a new collection or a `smoodly` upgrade, run `npx smoodly migrate`**
-  and apply what it writes (`supabase db push` hosted, `supabase migration up`
-  local). It copies the core schema files the package ships and writes a
-  read view and order index per collection. Never edit a file it wrote.
-  The admin reads the base tables, so it lists a collection either way;
-  the view is for SQL and PostgREST readers, the index for `order`.
 - **Content from code goes through `createContent(config)`** from `smoodly/astro`:
   `scripts/seed.ts` is starter content written with it — the admin's own
   operations, so validation and publish checks apply and a failure throws. Never
@@ -49,7 +43,7 @@ This is an Astro site with Smoodly installed: content lives in Supabase, the adm
 ## Commands
 
     npm run dev          # http://localhost:4321, /admin is the editor
-    npm run build        # checks the schema files (smoodly migrate --check), then astro build
+    npm run build        # astro build
     npm run start        # the built server (dist/server/entry.mjs)
     npm run seed         # starter content, idempotent
     npm run typecheck    # astro check

package/templates/astro-blank-intl/README.md

@@ -1,8 +1,8 @@
 # Smoodly site
 
-Created by `create-smoodly-app`. Content lives in Supabase; the admin is
-mounted at `/admin` by the `smoodly/astro` integration. AGENTS.md holds the
-rules for an agent (or a person) building the site.
+Created by `create-smoodly-app`. Content lives in Smoodly's service; the
+admin is mounted at `/admin` by the `smoodly/astro` integration. AGENTS.md
+holds the rules for an agent (or a person) building the site.
 
     npm run dev          # http://localhost:4321 — /admin is the editor
 
@@ -20,7 +20,7 @@ rules for an agent (or a person) building the site.
 - `src/live.config.ts` — the live collections the views read with `getLiveCollection` and `getLiveEntry`.
 - `scripts/seed.ts` — the home page and the site item, written through `createContent(config)`. `npm run seed` is idempotent.
 - `src/styles/global.css` — a reset, a container, the two tones. Replace it.
-- `.env` — `SMOODLY_URL`, `SMOODLY_SECRET_KEY`, `SMOODLY_PUBLISHABLE_KEY`.
+- `.env` — `SMOODLY_SPACE_ID`, `SMOODLY_SECRET_KEY`, `SMOODLY_PUBLISHABLE_KEY` (the space's values from smoodly.io) and `SITE_URL`.
 
 ## Add a section
 
@@ -47,13 +47,7 @@ editor's "/" menu.
 Copy the `posts` block in `src/smoodly/collections.ts`, add the new
 collection to `collections` and a loader for it in `src/live.config.ts`,
 and write its entry page, `src/entry-pages/<collection>.astro`, by
-copying `posts.astro`. Then write its read view and order index and
-apply them:
-
-    npx smoodly migrate
-    supabase db push        # hosted; `supabase migration up` for the local stack (keeps the content)
-
-The same command brings the core schema forward after a `smoodly` upgrade.
+copying `posts.astro`.
 
 ## Add a global item
 
@@ -61,7 +55,7 @@ Copy the `site` block in `src/smoodly/globals.ts`, add it to `globals`
 and give it a loader in `src/live.config.ts`. A view reads it with
 `getLiveEntry("name", { locale })`. Edit it under Globals in the admin.
 
-Reseed an empty database any time with `npm run seed`.
+Reseed an empty space any time with `npm run seed`.
 
 ## Moving the admin
 
@@ -74,16 +68,12 @@ The two must agree; the admin says so when they do not.
 
 ## Editors
 
-Anyone who may open `/admin` is a Supabase Auth user with a row in the
-`editors` table. To add one: create the user in Supabase Studio
-(Authentication → Users), then in the SQL editor:
-
-    insert into editors (user_id, role) values ('<the user id>', 'editor');
-
-## Hosted Supabase
+Editors sign in at `/admin` with their smoodly.io account. Colleagues are
+invited from the project at smoodly.io; the admin's Members page lists them.
 
-    supabase init        # if the CLI has not been set up here yet
-    supabase link        # pick the project
-    supabase db push     # applies supabase/migrations/
+## Deploying
 
-Then put the project's URL and keys in `.env`.
+`.env` holds the preview space's values, for development. Where you
+deploy, set the production space's three values and `SITE_URL` in the
+host's environment variables; each build pushes the
+schema to its space. https://smoodly.io/docs/getting-started/deploying

package/templates/astro-blank-intl/package.json

@@ -4,16 +4,15 @@
   "type": "module",
   "scripts": {
     "dev": "astro dev",
-    "build": "smoodly migrate --check && astro build",
+    "build": "astro build",
     "start": "node --env-file-if-exists=.env dist/server/entry.mjs",
     "seed": "tsx scripts/seed.ts",
     "typecheck": "astro check"
   },
   "dependencies": {
     "@astrojs/node": "^11.1.6",
-    "@supabase/supabase-js": "^2.113.0",
     "astro": "^7.3.5",
-    "smoodly": "0.0.50"
+    "smoodly": "0.0.52"
   },
   "devDependencies": {
     "@astrojs/check": "^0.9.10",

package/templates/astro-blank-intl/scripts/seed.ts

@@ -2,12 +2,18 @@
 // from smoodly/astro): the admin's own operations, so validation and
 // the publish checks apply and a failure throws. It is also the example
 // of writing content from code. Ships in the scaffold; create-smoodly-app
-// runs `npm run seed` after the first editor. Idempotent: exits once the
+// runs `npm run seed` after it pushes the schema. Idempotent: exits once the
 // home page has content in the default locale. Writes the same copy into every configured locale, whatever
 // their codes, so every locale's "/" resolves.
-// Run: npm run seed  (needs .env and a Supabase stack).
+// Run: npm run seed  (needs .env).
 import type { PageTree, TreeNode } from "smoodly";
 
+// A refusal from Smoodly's API (a space with no schema yet, a wrong key) prints its message and code, not a stack trace.
+process.on("uncaughtException", (e) => {
+  console.error(e.name === "SmoodlyContentError" ? `${e.message} (${(e as Error & { code?: string }).code})` : e);
+  process.exit(1);
+});
+
 const { config } = await import("../src/smoodly/config");
 const { node } = await import("smoodly");
 const { createContent } = await import("smoodly/astro");
@@ -19,7 +25,7 @@ const DEFAULT = config.locales.default;
 const OTHERS = config.locales.supported.filter((l) => l !== DEFAULT);
 
 // The home page is code-owned: `find` returns its record, creating it when
-// the database is new. It is seeded once somebody has given it sections.
+// the space is new. It is seeded once somebody has given it sections.
 const home = (await c.pages.find(DEFAULT, "/"))!;
 if (Object.values((await c.pages.getTree(home.id, DEFAULT))?.zones ?? {}).some((nodes) => nodes.length > 0)) {
   console.log(`Already seeded — the home page has content in "${DEFAULT}".`);

package/templates/astro-blank-intl/src/smoodly/collections.ts

@@ -5,8 +5,8 @@ import { text } from "./toolsets";
 // `path` by its entry page (src/entry-pages/posts.astro). Fields marked
 // .localized() are stored per locale; the rest are shared across
 // locales. To add a collection: copy this block, add it to
-// `collections`, run `npx smoodly migrate` and apply the file it writes
-// (supabase db push, or supabase migration up locally).
+// `collections`; the dev server and every build push the change to your
+// space.
 export const posts = smoodly.collection({
   name: "posts",
   title: "Posts",

package/templates/astro-lorem/AGENTS.md

@@ -1,6 +1,6 @@
 # Working in this Smoodly site
 
-This is an Astro site with Smoodly installed: content lives in Supabase, the admin is mounted at /admin by the `smoodly/astro` integration in `astro.config.ts`, and the site reads content through live collections (`src/live.config.ts`). Read README.md first: it says where things are.
+This is an Astro site with Smoodly installed: content lives in Smoodly's service, reached through the API, the admin is mounted at /admin by the `smoodly/astro` integration in `astro.config.ts`, and the site reads content through live collections (`src/live.config.ts`). Read README.md first: it says where things are.
 
 ## Rules
 
@@ -14,12 +14,6 @@ This is an Astro site with Smoodly installed: content lives in Supabase, the adm
   names a schema with no file, and a file with no schema, at the first request.
 - **A `.schema.ts` file imports no component.** Zones, toolsets, global items and
   `node()` take schemas (`z.locked(heroSchema)`), never views.
-- **After a new collection or a `smoodly` upgrade, run `npx smoodly migrate`**
-  and apply what it writes (`supabase db push` hosted, `supabase migration up`
-  local). It copies the core schema files the package ships and writes a
-  read view and order index per collection. Never edit a file it wrote.
-  The admin reads the base tables, so it lists a collection either way;
-  the view is for SQL and PostgREST readers, the index for `order`.
 - **Content from code goes through `createContent(config)`** from `smoodly/astro`:
   `scripts/seed.ts` is starter content written with it — the admin's own
   operations, so validation and publish checks apply and a failure throws. Never
@@ -49,7 +43,7 @@ This is an Astro site with Smoodly installed: content lives in Supabase, the adm
 ## Commands
 
     npm run dev          # http://localhost:4321, /admin is the editor
-    npm run build        # checks the schema files (smoodly migrate --check), then astro build
+    npm run build        # astro build
     npm run start        # the built server (dist/server/entry.mjs)
     npm run seed         # starter content, idempotent
     npm run typecheck    # astro check

package/templates/astro-lorem/README.md

@@ -1,8 +1,8 @@
 # Smoodly site
 
-Created by `create-smoodly-app`. Content lives in Supabase; the admin is
-mounted at `/admin` by the `smoodly/astro` integration. AGENTS.md holds the
-rules for an agent (or a person) building the site.
+Created by `create-smoodly-app`. Content lives in Smoodly's service; the
+admin is mounted at `/admin` by the `smoodly/astro` integration. AGENTS.md
+holds the rules for an agent (or a person) building the site.
 
     npm run dev          # http://localhost:4321 — /admin is the editor
 
@@ -19,7 +19,7 @@ rules for an agent (or a person) building the site.
 - `src/strings.ts`, `src/messages/` — the site's own UI strings in the page's language.
 - `public/images/` — the starter's photos; image fields hold URLs like `/images/hero_image.jpg`.
 - `scripts/seed.ts` — the starter content, written through `createContent(config)`. `npm run seed` is idempotent.
-- `.env` — `SMOODLY_URL`, `SMOODLY_SECRET_KEY`, `SMOODLY_PUBLISHABLE_KEY`.
+- `.env` — `SMOODLY_SPACE_ID`, `SMOODLY_SECRET_KEY`, `SMOODLY_PUBLISHABLE_KEY` (the space's values from smoodly.io) and `SITE_URL`.
 
 ## What is in the starter
 
@@ -32,7 +32,7 @@ The Lorem Co. site the installer seeded is a tour of the features:
 - **An article** — a collection entry with a richtext body, tags (a localized list), a date and an author ref; versioned, so every save is a snapshot.
 - **Global content** — the header and footer every page renders through \`src/layouts/Layout.astro\`, the contact details the footer reads, the quote pages place.
 
-Reseed an empty database any time with `npm run seed`.
+Reseed an empty space any time with `npm run seed`.
 
 ## Moving the admin
 
@@ -45,16 +45,12 @@ The two must agree; the admin says so when they do not.
 
 ## Editors
 
-Anyone who may open `/admin` is a Supabase Auth user with a row in the
-`editors` table. To add one: create the user in Supabase Studio
-(Authentication → Users), then in the SQL editor:
+Editors sign in at `/admin` with their smoodly.io account. Colleagues are
+invited from the project at smoodly.io; the admin's Members page lists them.
 
-    insert into editors (user_id, role) values ('<the user id>', 'editor');
+## Deploying
 
-## Hosted Supabase
-
-    supabase init        # if the CLI has not been set up here yet
-    supabase link        # pick the project
-    supabase db push     # applies supabase/migrations/
-
-Then put the project's URL and keys in `.env`.
+`.env` holds the preview space's values, for development. Where you
+deploy, set the production space's three values and `SITE_URL` in the
+host's environment variables; each build pushes the
+schema to its space. https://smoodly.io/docs/getting-started/deploying

package/templates/astro-lorem/package.json

@@ -4,16 +4,15 @@
   "type": "module",
   "scripts": {
     "dev": "astro dev",
-    "build": "smoodly migrate --check && astro build",
+    "build": "astro build",
     "start": "node --env-file-if-exists=.env dist/server/entry.mjs",
     "seed": "tsx scripts/seed.ts",
     "typecheck": "astro check"
   },
   "dependencies": {
     "@astrojs/node": "^11.1.6",
-    "@supabase/supabase-js": "^2.113.0",
     "astro": "^7.3.5",
-    "smoodly": "0.0.50"
+    "smoodly": "0.0.52"
   },
   "devDependencies": {
     "@astrojs/check": "^0.9.10",

package/templates/astro-lorem/scripts/seed.ts

@@ -2,9 +2,9 @@
 // from smoodly/astro): the admin's own operations, so validation and
 // the publish checks apply and a failure throws. This file is also the
 // example of writing content from code. Content only; it ships in the template and create-smoodly-app runs
-// `npm run seed` after the first editor. (The example repo's demo
+// `npm run seed` after it pushes the schema. (The example repo's demo
 // editor account is a separate, example-only script.)
-// Run: npm run seed  (needs .env and a Supabase stack).
+// Run: npm run seed  (needs .env).
 //
 // Locales: the English content goes into the configured default locale,
 // whatever its code, and the Finnish rows are written only when `fi` is
@@ -17,6 +17,12 @@
 // page has content.
 import type { PageTree, TreeNode } from "smoodly";
 
+// A refusal from Smoodly's API (a space with no schema yet, a wrong key) prints its message and code, not a stack trace.
+process.on("uncaughtException", (e) => {
+  console.error(e.name === "SmoodlyContentError" ? `${e.message} (${(e as Error & { code?: string }).code})` : e);
+  process.exit(1);
+});
+
 const { config } = await import("../src/smoodly/config");
 const { articles, news } = await import("../src/smoodly/collections");
 const { node } = await import("smoodly");
@@ -34,7 +40,7 @@ const EN = config.locales.default;
 const FI = config.locales.supported.includes("fi") && EN !== "fi" ? "fi" : null;
 
 // The home page is code-owned: `find` returns its record, creating it when
-// the database is new. It is seeded once somebody has given it sections.
+// the space is new. It is seeded once somebody has given it sections.
 const home = (await c.pages.find(EN, "/"))!;
 if (Object.values((await c.pages.getTree(home.id, EN))?.zones ?? {}).some((nodes) => nodes.length > 0)) {
   console.log(`Already seeded — the home page has content in "${EN}".`);

package/templates/astro-lorem/src/components/sections/PageHero.schema.ts

@@ -4,6 +4,8 @@ import { f, smoodly } from "smoodly";
 // text and an optional wide photo. Page and Articles lock it — each page
 // shape locks its own hero, which is the point: a locked zone is per
 // shape. Without an image the copy stands alone (the Articles index).
+// The photo has two named crops: wide on a desktop, tall on a phone; the
+// view says which applies where.
 export const pageHeroSchema = smoodly.schema.section({
   name: "pageHero",
   title: "Page hero",
@@ -12,7 +14,7 @@ export const pageHeroSchema = smoodly.schema.section({
     kicker: f.text().optional(),
     heading: f.text(),
     text: f.text(),
-    image: f.image({ aspect: "21:9" }).optional(),
+    image: f.image({ crops: { wide: "21:9", tall: "4:5" } }).optional(),
   },
   sample: {
     heading: "About us",

package/templates/astro-lorem/src/sections/pageHero.astro

@@ -15,6 +15,6 @@ const m = smoodly.marks(pageHeroSchema);
       <h1 class="page-hero__heading" {...m.field("heading")}>{heading}</h1>
       <p class="page-hero__text" {...m.field("text")}>{text}</p>
     </div>
-    {image && <Image image={image} class="page-hero__image" sizes="100vw" priority {...m.field("image")} />}
+    {image && <Image image={image} media={{ tall: "(max-width: 767px)" }} class="page-hero__image" sizes="100vw" priority {...m.field("image")} />}
   </div>
 </Section>

package/templates/astro-lorem-intl/AGENTS.md

@@ -1,6 +1,6 @@
 # Working in this Smoodly site
 
-This is an Astro site with Smoodly installed: content lives in Supabase, the admin is mounted at /admin by the `smoodly/astro` integration in `astro.config.ts`, and the site reads content through live collections (`src/live.config.ts`). Read README.md first: it says where things are.
+This is an Astro site with Smoodly installed: content lives in Smoodly's service, reached through the API, the admin is mounted at /admin by the `smoodly/astro` integration in `astro.config.ts`, and the site reads content through live collections (`src/live.config.ts`). Read README.md first: it says where things are.
 
 ## Rules
 
@@ -14,12 +14,6 @@ This is an Astro site with Smoodly installed: content lives in Supabase, the adm
   names a schema with no file, and a file with no schema, at the first request.
 - **A `.schema.ts` file imports no component.** Zones, toolsets, global items and
   `node()` take schemas (`z.locked(heroSchema)`), never views.
-- **After a new collection or a `smoodly` upgrade, run `npx smoodly migrate`**
-  and apply what it writes (`supabase db push` hosted, `supabase migration up`
-  local). It copies the core schema files the package ships and writes a
-  read view and order index per collection. Never edit a file it wrote.
-  The admin reads the base tables, so it lists a collection either way;
-  the view is for SQL and PostgREST readers, the index for `order`.
 - **Content from code goes through `createContent(config)`** from `smoodly/astro`:
   `scripts/seed.ts` is starter content written with it — the admin's own
   operations, so validation and publish checks apply and a failure throws. Never
@@ -49,7 +43,7 @@ This is an Astro site with Smoodly installed: content lives in Supabase, the adm
 ## Commands
 
     npm run dev          # http://localhost:4321, /admin is the editor
-    npm run build        # checks the schema files (smoodly migrate --check), then astro build
+    npm run build        # astro build
     npm run start        # the built server (dist/server/entry.mjs)
     npm run seed         # starter content, idempotent
     npm run typecheck    # astro check

package/templates/astro-lorem-intl/README.md

@@ -1,8 +1,8 @@
 # Smoodly site
 
-Created by `create-smoodly-app`. Content lives in Supabase; the admin is
-mounted at `/admin` by the `smoodly/astro` integration. AGENTS.md holds the
-rules for an agent (or a person) building the site.
+Created by `create-smoodly-app`. Content lives in Smoodly's service; the
+admin is mounted at `/admin` by the `smoodly/astro` integration. AGENTS.md
+holds the rules for an agent (or a person) building the site.
 
     npm run dev          # http://localhost:4321 — /admin is the editor
 
@@ -20,7 +20,7 @@ rules for an agent (or a person) building the site.
 - `src/strings.ts`, `src/messages/` — the site's own UI strings in the page's language.
 - `public/images/` — the starter's photos; image fields hold URLs like `/images/hero_image.jpg`.
 - `scripts/seed.ts` — the starter content, written through `createContent(config)`. `npm run seed` is idempotent.
-- `.env` — `SMOODLY_URL`, `SMOODLY_SECRET_KEY`, `SMOODLY_PUBLISHABLE_KEY`.
+- `.env` — `SMOODLY_SPACE_ID`, `SMOODLY_SECRET_KEY`, `SMOODLY_PUBLISHABLE_KEY` (the space's values from smoodly.io) and `SITE_URL`.
 
 ## What is in the starter
 
@@ -34,7 +34,7 @@ The Lorem Co. site the installer seeded is a tour of the features:
 - **Global content** — the header and footer every page renders through \`src/layouts/Layout.astro\`, the contact details the footer reads, the quote pages place.
 
 Every page and entry exists in each locale with its own slug. Reseed an
-empty database any time with `npm run seed`.
+empty space any time with `npm run seed`.
 
 ## Moving the admin
 
@@ -47,16 +47,12 @@ The two must agree; the admin says so when they do not.
 
 ## Editors
 
-Anyone who may open `/admin` is a Supabase Auth user with a row in the
-`editors` table. To add one: create the user in Supabase Studio
-(Authentication → Users), then in the SQL editor:
+Editors sign in at `/admin` with their smoodly.io account. Colleagues are
+invited from the project at smoodly.io; the admin's Members page lists them.
 
-    insert into editors (user_id, role) values ('<the user id>', 'editor');
+## Deploying
 
-## Hosted Supabase
-
-    supabase init        # if the CLI has not been set up here yet
-    supabase link        # pick the project
-    supabase db push     # applies supabase/migrations/
-
-Then put the project's URL and keys in `.env`.
+`.env` holds the preview space's values, for development. Where you
+deploy, set the production space's three values and `SITE_URL` in the
+host's environment variables; each build pushes the
+schema to its space. https://smoodly.io/docs/getting-started/deploying

package/templates/astro-lorem-intl/package.json

@@ -4,16 +4,15 @@
   "type": "module",
   "scripts": {
     "dev": "astro dev",
-    "build": "smoodly migrate --check && astro build",
+    "build": "astro build",
     "start": "node --env-file-if-exists=.env dist/server/entry.mjs",
     "seed": "tsx scripts/seed.ts",
     "typecheck": "astro check"
   },
   "dependencies": {
     "@astrojs/node": "^11.1.6",
-    "@supabase/supabase-js": "^2.113.0",
     "astro": "^7.3.5",
-    "smoodly": "0.0.50"
+    "smoodly": "0.0.52"
   },
   "devDependencies": {
     "@astrojs/check": "^0.9.10",