create-smoodly-app 0.0.50 → 0.0.52

package/templates/astro-lorem-intl/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-intl/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-intl/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/blank/AGENTS.md

@@ -1,9 +1,9 @@
 # Working in this Smoodly site
 
-This is a Next.js app with Smoodly installed: content lives in Supabase,
-the admin is mounted at /admin from the `smoodly` package, and the site
-reads content through `smoodly/server.ts`. Read README.md first: it says
-where things are.
+This is a Next.js app with Smoodly installed: content lives in Smoodly's service,
+reached through the API, the admin is mounted at /admin from the `smoodly`
+package, and the site reads content through `smoodly/server.ts`. Read
+README.md first: it says where things are.
 
 ## Rules
 
@@ -20,12 +20,6 @@ where things are.
   `smoodly/server.ts` or `smoodly/richtext.tsx`. Zones, toolsets, global
   items and `node()` take schemas (`z.locked(heroSchema)`), never
   components.
-- **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 `content()`.** `scripts/seed.ts` is
   starter content written with `content()` from `smoodly/server.ts`:
   the admin's own operations, so validation and publish checks apply and
@@ -35,8 +29,8 @@ where things are.
   serves the admin's page, its files and its operations from the
   `smoodly` package; the folder name must match `admin.path` in the
   config. The admin is prebuilt: nothing of it is compiled into the
-  site, and it takes no layout. Server-side pieces such as
-  `supabaseAdminAuth` and the content API come from `smoodly/admin`.
+  site, and it takes no layout. The content API (`createSmoodlyContent`,
+  `apiTransport`) comes from `smoodly/admin`.
 - **One root layout.** The site's layout lives in its route group or
   locale segment. Do not add an `app/layout.tsx`: it would wrap that
   layout in a second `<html>`.
@@ -59,6 +53,6 @@ where things are.
 ## Commands
 
     npm run dev          # http://localhost:3000, /admin is the editor
-    npm run build        # checks the schema files (smoodly migrate --check), then next build
+    npm run build        # next build
     npm run seed         # starter content, idempotent
     npm run typecheck    # tsc --noEmit

package/templates/blank/README.md

@@ -1,8 +1,8 @@
 # Smoodly site
 
-Created by `create-smoodly-app`. Content lives in Supabase; the admin is
-mounted at `/admin` from the `smoodly` package. 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` from the `smoodly` package. AGENTS.md holds
+the rules for an agent (or a person) building the site.
 
     npm run dev          # http://localhost:3000 — /admin is the editor
 
@@ -17,7 +17,7 @@ for an agent (or a person) building the site.
 - `smoodly/` — the wiring: `config.ts` (the registry of schemas and the settings; it imports no component), `collections.ts` (posts), `globals.ts` (the site item), `sections.ts` and `elements.ts` (the schemas the config registers), `views.ts` (the components that render them), `toolsets.ts`, `server.ts` (site layer, renderer, the read API `q`, the content API `content()`), `richtext.tsx` (the bound renderer).
 - `scripts/seed.ts` — the home page and the site item, written through the content API (`content()`). `npm run seed` is idempotent.
 - `app/globals.css` — a reset, a container, the two tones. Replace it.
-- `.env.local` — `SMOODLY_URL`, `SMOODLY_SECRET_KEY`, `SMOODLY_PUBLISHABLE_KEY`.
+- `.env.local` — `SMOODLY_SPACE_ID`, `SMOODLY_SECRET_KEY`, `SMOODLY_PUBLISHABLE_KEY` (the space's values from smoodly.io) and `SITE_URL`.
 
 ## Add a section
 
@@ -44,12 +44,6 @@ it; add the component to `elements` in `smoodly/views.ts` and in
 Copy the `posts` block in `smoodly/collections.ts`, add the new
 collection to `collections`, and write its entry page by copying
 `components/pages/Post.tsx` (list it in `smoodly/views.ts` under `pages`).
-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.
 
 ## Add a global item
 
@@ -59,7 +53,7 @@ visual item (`section: someSectionSchema`) renders through its section and can
 be placed on pages from the picker's Global group. Edit both 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
 
@@ -72,16 +66,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.local`.
+`.env.local` 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/blank/app/(smoodly)/admin/[[...segments]]/route.ts

@@ -1,8 +1,9 @@
-// The admin: its page, the package's files and the operations endpoint, all from this one route. The
-// admin is prebuilt in the `smoodly` package; nothing of it is compiled into the site. The folder name
-// must match `admin.path` in smoodly/config.ts.
+// The admin: its page, the package's files, the revalidate route Smoodly's API calls after a publish and
+// the preview route, all from this one route; the operations run in Smoodly's API. The admin is prebuilt
+// in the `smoodly` package; nothing of it is compiled into the site. The folder name must match
+// `admin.path` in smoodly/config.ts.
 import { createAdminRoute } from "smoodly/next";
 import { config } from "@/smoodly/config";
-import { adminDeps, presence, publicAuth } from "@/smoodly/server";
+import { adminDeps, presence } from "@/smoodly/server";
 
-export const { GET, POST } = createAdminRoute(() => ({ config, ...adminDeps(), signIn: publicAuth(), presence }));
+export const { GET, POST } = createAdminRoute(() => ({ config, ...adminDeps(), presence }));

package/templates/blank/next.config.ts

@@ -1,8 +1,5 @@
 import type { NextConfig } from "next";
-import { smoodlyImages } from "smoodly/image/config";
 
-// next/image may only optimize from the Supabase host named in SMOODLY_URL
-// (a local stack also needs Next's local-IP allowance; the helper sets it).
-const config: NextConfig = { images: smoodlyImages() };
+const config: NextConfig = {};
 
 export default config;

package/templates/blank/package.json

@@ -4,17 +4,17 @@
   "type": "module",
   "scripts": {
     "dev": "next dev",
-    "build": "smoodly migrate --check && next build",
+    "build": "next build",
     "start": "next start",
     "seed": "tsx scripts/seed.ts",
-    "typecheck": "tsc --noEmit"
+    "typecheck": "tsc --noEmit",
+    "prebuild": "smoodly push"
   },
   "dependencies": {
-    "@supabase/supabase-js": "^2.113.0",
     "next": "^16.3.4",
     "react": "^19",
     "react-dom": "^19",
-    "smoodly": "0.0.50"
+    "smoodly": "0.0.52"
   },
   "devDependencies": {
     "@next/env": "^16.3.4",

package/templates/blank/scripts/seed.ts

@@ -2,16 +2,22 @@
 // from smoodly/server.ts): 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.local and a Supabase stack).
+// Run: npm run seed  (needs .env.local).
 import next from "@next/env";
 import type { PageTree, TreeNode } from "smoodly";
 const { loadEnvConfig } = next;
 
 loadEnvConfig(process.cwd());
 
+// 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("../smoodly/config");
 const { content, node } = await import("../smoodly/server");
 const { textSchema } = await import("../components/sections/Text.schema");
@@ -21,7 +27,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/blank/smoodly/collections.ts

@@ -5,8 +5,8 @@ import { text } from "./toolsets";
 // `path` by its entry page (components/pages/Post.tsx). 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/blank/smoodly/server.ts

@@ -1,59 +1,46 @@
-// Server-only glue: the client, the stores, the site layer and the
-// renderer, constructed lazily so `next build` doesn't need env vars at
-// import time. The env shape is the package's (SMOODLY_*): the live site
-// needs SMOODLY_URL and SMOODLY_SECRET_KEY, the admin also
-// SMOODLY_PUBLISHABLE_KEY (the `smoodlyEnv("admin")` calls below); whether the
-// secret is a service-role key or a cloud write key is invisible here.
+// Server-only glue: the reads over Smoodly's API and the renderer,
+// constructed lazily so `next build` doesn't need env vars at import time.
+// The env shape is the package's (SMOODLY_*): the live site and the admin need
+// SMOODLY_API_URL, SMOODLY_SPACE_ID and SMOODLY_SECRET_KEY; the admin learns
+// where editors sign in from Smoodly's API. The site opens no database.
 //
 // Lazy on purpose: a page component imports this file to read through
 // `q` (components/pages/Articles.tsx), and this file imports the
 // components through ./views. That is a cycle, so nothing here reads
 // views() or the env at module scope.
-import {
-  createSmoodlyClient, createSmoodlySite, createSupabaseStores, presenceConfig, siteOptions, smoodlyEnv,
-  type PresenceConfig, type SmoodlySite, type SupabaseAssetStore, type SupabaseEntryStore, type SupabaseMemberStore, type SupabasePageStore,
-} from "smoodly";
-// The admin's server pieces: the sign-in check and the content API. No browser code lives in the package's
-// entries; the admin itself is prebuilt and served by app/(smoodly)/admin/[[...segments]]/route.ts.
-import { createSmoodlyContent, supabaseAdminAuth, type AdminAuth, type AuthConfig, type SmoodlyContent } from "smoodly/admin";
+import { apiEnv, createSmoodlyApi, presenceConfig, smoodlyEnv, type ContentReads, type PresenceConfig } from "smoodly";
+// The admin's server pieces: the content API for scripts. No browser code lives in the package's entries;
+// the admin itself is prebuilt and served by app/(smoodly)/admin/[[...segments]]/route.ts.
+import { apiTransport, createSmoodlyContent, type SmoodlyContent } from "smoodly/admin";
 import { buildGate, createPageRenderer, createSmoodlyQueries } from "smoodly/next";
-import type { SupabaseClient } from "@supabase/supabase-js";
 import { collections, config, globals } from "./config";
 import { views } from "./views";
 
 type Renderer = ReturnType<typeof createPageRenderer>;
 type Queries = ReturnType<typeof createSmoodlyQueries<typeof collections, typeof globals>>;
-type Bound = {
-  db: SupabaseClient; pages: SupabasePageStore; entries: SupabaseEntryStore; assets: SupabaseAssetStore; members: SupabaseMemberStore; auth: AdminAuth; site: SmoodlySite; renderer: Renderer; q: Queries;
-};
+type Bound = { site: ContentReads; renderer: Renderer; q: Queries };
 
 let cached: Bound | null = null;
 
 function bound(): Bound {
   if (cached) return cached;
-  const env = smoodlyEnv();
-  const db = createSmoodlyClient(env);
-  // The stores, read off the config: pages, entries, the media library and the admission table.
-  const { pages, entries, assets, members, published } = createSupabaseStores(db, config);
-  const auth = supabaseAdminAuth({ authUrl: env.authUrl, authKey: env.authKey, db });
-  // The site layer: (locale, path) → page or entry, and the content API
-  // `q` wraps below. Not exported — the app reads through `q`, which adds
-  // draft awareness and the cache.
-  const site = createSmoodlySite(siteOptions(config, () => ({ pages, entries, assets, published })));
+  // The site's reads go over Smoodly's API (SMOODLY_API_URL, SMOODLY_SPACE_ID, SMOODLY_SECRET_KEY):
+  // (locale, path) → page or entry, and the reads `q` wraps below. Not exported — the app reads
+  // through `q`, which adds draft awareness and the cache.
+  const site = createSmoodlyApi({ ...apiEnv(), config });
   // The components, checked against the config's schemas here, on first use.
   const renderer = createPageRenderer({ site, ...views(), href });
   // The read API (spec 2026-09-11): typed by the registry, draft-aware, cached under tags the admin expires.
   const q = createSmoodlyQueries({ site, collections, globals });
-  cached = { db, pages, entries, assets, members, auth, site, renderer, q };
+  cached = { site, renderer, q };
   return cached;
 }
 
-/** The admin's wiring, for the admin route only. Scripts write through `content()`. */
+/** The admin's wiring, for the admin route only: the page and its files, the revalidate route the
+ *  service calls and the preview route the browser posts the grant to. Operations run in the service. */
 export function adminDeps() {
-  smoodlyEnv("admin"); // the admin signs in with the publishable key: a missing one is named here, not on a live page
-  const { pages, entries, assets, members, auth, site } = bound();
-  // The projector: a publish writes the finished documents a live page reads.
-  return { pages, entries, assets, members, auth, href, projector: site.projector };
+  const env = smoodlyEnv("admin"); // the admin talks to SMOODLY_API_URL, which also tells it where editors sign in
+  return { apiUrl: env.apiUrl, spaceId: env.spaceId, delivery: "live" as const };
 }
 
 /** Write content from code — seeds, migrations, route handlers (spec 2026-09-30 tester findings §1).
@@ -61,24 +48,15 @@ export function adminDeps() {
  *  throws `SmoodlyContentError`. `content().pages.create(…)`, `.entries.create(…)`, `.globals.set(…)`,
  *  `.media.upload(…)`; build tree nodes with `node(Section, fields)`. */
 export function content(): SmoodlyContent {
-  const { pages, entries, assets, members, site } = bound();
-  return createSmoodlyContent({ config, pages, entries, assets, members, href, projector: site.projector });
+  // Over Smoodly's API with the secret key: the service runs the operations.
+  return createSmoodlyContent({ config, href, transport: apiTransport(apiEnv()) });
 }
 
 export { node } from "smoodly";
 
-/** The server-side client (seed script, one-off admin tasks). */
-export const client = () => bound().db;
-
-/** What the browser needs to sign in — public values only. */
-export function publicAuth(): AuthConfig {
-  const env = smoodlyEnv("admin");
-  return { url: env.authUrl, key: env.authKey };
-}
-
-/** What the browser needs to join the editing-presence channel — public values only (spec 2026-09-26 concurrency §5).
- * The space is asked of the database once per process. */
-export function presence(): Promise<PresenceConfig> {
+/** What the browser needs to open the editing-presence socket — Smoodly's API and the space, public values only
+ * (spec 2026-10-15 the space object §6). */
+export function presence(): PresenceConfig {
   return presenceConfig(smoodlyEnv("admin"));
 }
 
@@ -105,7 +83,7 @@ export const q = (): Queries =>
 // route file without a dynamic segment reads nothing at build and the build needs no keys — a layout
 // reading a global through q() included (2026-10-02, tester round 6). At run time it does nothing: a
 // CMS route renders on its first visit and is cached until a publish expires it (plan 2026-10-09).
-/** The two route files call these. */
+/** The route file calls these. */
 export const renderSmoodlyPath: Renderer["renderSmoodlyPath"] = async (...args) => { await buildGate(); return bound().renderer.renderSmoodlyPath(...args); };
 export const smoodlyMetadata: Renderer["smoodlyMetadata"] = async (...args) => { await buildGate(); return bound().renderer.smoodlyMetadata(...args); };
 export const renderSmoodlyPage: Renderer["renderSmoodlyPage"] = async (...args) => { await buildGate(); return bound().renderer.renderSmoodlyPage(...args); };

package/templates/blank-intl/AGENTS.md

@@ -1,9 +1,9 @@
 # Working in this Smoodly site
 
-This is a Next.js app with Smoodly installed: content lives in Supabase,
-the admin is mounted at /admin from the `smoodly` package, and the site
-reads content through `smoodly/server.ts`. Read README.md first: it says
-where things are.
+This is a Next.js app with Smoodly installed: content lives in Smoodly's service,
+reached through the API, the admin is mounted at /admin from the `smoodly`
+package, and the site reads content through `smoodly/server.ts`. Read
+README.md first: it says where things are.
 
 ## Rules
 
@@ -20,12 +20,6 @@ where things are.
   `smoodly/server.ts` or `smoodly/richtext.tsx`. Zones, toolsets, global
   items and `node()` take schemas (`z.locked(heroSchema)`), never
   components.
-- **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 `content()`.** `scripts/seed.ts` is
   starter content written with `content()` from `smoodly/server.ts`:
   the admin's own operations, so validation and publish checks apply and
@@ -35,8 +29,8 @@ where things are.
   serves the admin's page, its files and its operations from the
   `smoodly` package; the folder name must match `admin.path` in the
   config. The admin is prebuilt: nothing of it is compiled into the
-  site, and it takes no layout. Server-side pieces such as
-  `supabaseAdminAuth` and the content API come from `smoodly/admin`.
+  site, and it takes no layout. The content API (`createSmoodlyContent`,
+  `apiTransport`) comes from `smoodly/admin`.
 - **One root layout.** The site's layout lives in its route group or
   locale segment. Do not add an `app/layout.tsx`: it would wrap that
   layout in a second `<html>`.
@@ -59,6 +53,6 @@ where things are.
 ## Commands
 
     npm run dev          # http://localhost:3000, /admin is the editor
-    npm run build        # checks the schema files (smoodly migrate --check), then next build
+    npm run build        # next build
     npm run seed         # starter content, idempotent
     npm run typecheck    # tsc --noEmit

package/templates/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` from the `smoodly` package. 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` from the `smoodly` package. AGENTS.md holds
+the rules for an agent (or a person) building the site.
 
     npm run dev          # http://localhost:3000 — /admin is the editor
 
@@ -18,7 +18,7 @@ for an agent (or a person) building the site.
 - `smoodly/` — the wiring: `config.ts` (the registry of schemas and the settings; it imports no component), `collections.ts` (posts), `globals.ts` (the site item), `sections.ts` and `elements.ts` (the schemas the config registers), `views.ts` (the components that render them), `toolsets.ts`, `server.ts` (site layer, renderer, the read API `q`, the content API `content()`), `richtext.tsx` (the bound renderer).
 - `scripts/seed.ts` — the home page and the site item, written through the content API (`content()`). `npm run seed` is idempotent.
 - `app/globals.css` — a reset, a container, the two tones. Replace it.
-- `.env.local` — `SMOODLY_URL`, `SMOODLY_SECRET_KEY`, `SMOODLY_PUBLISHABLE_KEY`.
+- `.env.local` — `SMOODLY_SPACE_ID`, `SMOODLY_SECRET_KEY`, `SMOODLY_PUBLISHABLE_KEY` (the space's values from smoodly.io) and `SITE_URL`.
 
 ## Add a section
 
@@ -45,12 +45,6 @@ it; add the component to `elements` in `smoodly/views.ts` and in
 Copy the `posts` block in `smoodly/collections.ts`, add the new
 collection to `collections`, and write its entry page by copying
 `components/pages/Post.tsx` (list it in `smoodly/views.ts` under `pages`).
-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.
 
 ## Add a global item
 
@@ -60,7 +54,7 @@ visual item (`section: someSectionSchema`) renders through its section and can
 be placed on pages from the picker's Global group. Edit both 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
 
@@ -75,16 +69,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.local`.
+`.env.local` 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/blank-intl/app/(smoodly)/admin/[[...segments]]/route.ts

@@ -1,8 +1,9 @@
-// The admin: its page, the package's files and the operations endpoint, all from this one route. The
-// admin is prebuilt in the `smoodly` package; nothing of it is compiled into the site. The folder name
-// must match `admin.path` in smoodly/config.ts.
+// The admin: its page, the package's files, the revalidate route Smoodly's API calls after a publish and
+// the preview route, all from this one route; the operations run in Smoodly's API. The admin is prebuilt
+// in the `smoodly` package; nothing of it is compiled into the site. The folder name must match
+// `admin.path` in smoodly/config.ts.
 import { createAdminRoute } from "smoodly/next";
 import { config } from "@/smoodly/config";
-import { adminDeps, presence, publicAuth } from "@/smoodly/server";
+import { adminDeps, presence } from "@/smoodly/server";
 
-export const { GET, POST } = createAdminRoute(() => ({ config, ...adminDeps(), signIn: publicAuth(), presence }));
+export const { GET, POST } = createAdminRoute(() => ({ config, ...adminDeps(), presence }));

package/templates/blank-intl/next.config.ts

@@ -1,11 +1,8 @@
 import type { NextConfig } from "next";
 import createNextIntlPlugin from "next-intl/plugin";
-import { smoodlyImages } from "smoodly/image/config";
 
 const withNextIntl = createNextIntlPlugin();
 
-// next/image may only optimize from the Supabase host named in SMOODLY_URL
-// (a local stack also needs Next's local-IP allowance; the helper sets it).
-const config: NextConfig = { images: smoodlyImages() };
+const config: NextConfig = {};
 
 export default withNextIntl(config);

package/templates/blank-intl/package.json

@@ -4,17 +4,17 @@
   "type": "module",
   "scripts": {
     "dev": "next dev",
-    "build": "smoodly migrate --check && next build",
+    "build": "next build",
     "start": "next start",
     "seed": "tsx scripts/seed.ts",
-    "typecheck": "tsc --noEmit"
+    "typecheck": "tsc --noEmit",
+    "prebuild": "smoodly push"
   },
   "dependencies": {
-    "@supabase/supabase-js": "^2.113.0",
     "next": "^16.3.4",
     "react": "^19",
     "react-dom": "^19",
-    "smoodly": "0.0.50",
+    "smoodly": "0.0.52",
     "next-intl": "^4.14.2"
   },
   "devDependencies": {

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

@@ -2,16 +2,22 @@
 // from smoodly/server.ts): 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.local and a Supabase stack).
+// Run: npm run seed  (needs .env.local).
 import next from "@next/env";
 import type { PageTree, TreeNode } from "smoodly";
 const { loadEnvConfig } = next;
 
 loadEnvConfig(process.cwd());
 
+// 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("../smoodly/config");
 const { content, node } = await import("../smoodly/server");
 const { textSchema } = await import("../components/sections/Text.schema");
@@ -21,7 +27,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/blank-intl/smoodly/collections.ts

@@ -5,8 +5,8 @@ import { text } from "./toolsets";
 // `path` by its entry page (components/pages/Post.tsx). 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",