@sandboxsonny/ace-kit 0.4.0 → 0.6.0

package/dist/react-router-server.js

@@ -1,5 +1,6 @@
 import { createAceClient, loadMenuLinks, loadPage } from './chunk-XYOW63V6.js';
 import './chunk-M5WR5TCR.js';
+import { hostedAdminOrigin, hostedApiUrl } from './chunk-N5DIMG3X.js';
 import { previewTokenFrom, addFramingPolicy } from './chunk-YLO6IAXF.js';
 import { createReadableStreamFromReadable } from '@react-router/node';
 import { PassThrough } from 'stream';
@@ -10,9 +11,9 @@ import { jsx } from 'react/jsx-runtime';
 // src/react-router/settings.ts
 function getAceSettings() {
   return {
-    apiUrl: process.env.ACE_API_URL ?? "http://localhost:8080",
+    apiUrl: process.env.ACE_API_URL ?? hostedApiUrl,
     siteDomain: process.env.ACE_SITE_DOMAIN ?? "localhost",
-    previewAdminOrigin: process.env.ACE_PREVIEW_ADMIN_ORIGIN ?? "http://localhost:5173"
+    previewAdminOrigin: process.env.ACE_PREVIEW_ADMIN_ORIGIN ?? hostedAdminOrigin
   };
 }
 if (typeof window !== "undefined" && typeof process === "undefined") {

package/dist/vite.js

@@ -1,4 +1,5 @@
-import { startDevSite, startSectionSync } from './chunk-O3NAJNUN.js';
+import { startDevSite, startSectionSync } from './chunk-G5FGBOFT.js';
+import './chunk-N5DIMG3X.js';
 import { resolve } from 'path';
 import { loadEnv } from 'vite';
 

package/docs/astro.md

@@ -17,13 +17,19 @@ export default defineConfig({
 
 The integration declares three settings, adds the middleware that lets the CMS's admin app (and only it) frame the site for [live preview](./live-preview.md), and makes Vite process the kit. The settings are read when the server starts, not baked into the build, so one build runs anywhere:
 
-| Setting                    | Default                 | Meaning                                                   |
-| -------------------------- | ----------------------- | --------------------------------------------------------- |
-| `ACE_API_URL`              | `http://localhost:8080` | where the CMS Ace API lives                               |
-| `ACE_SITE_DOMAIN`          | `localhost`             | the domain this site has in the CMS (the port is ignored) |
-| `ACE_PREVIEW_ADMIN_ORIGIN` | `http://localhost:5173` | where the CMS admin app runs                              |
+| Setting                    | Default                                              | Meaning                                                   |
+| -------------------------- | ---------------------------------------------------- | --------------------------------------------------------- |
+| `ACE_API_URL`              | `https://api.ace-cms.co.uk`                          | where the CMS Ace API lives                               |
+| `ACE_SITE_DOMAIN`          | the host of Astro's `site` setting, else `localhost` | the domain this site has in the CMS (the port is ignored) |
+| `ACE_PREVIEW_ADMIN_ORIGIN` | `https://app.ace-cms.co.uk`                          | where the CMS admin app runs                              |
 
-Put them in `.env` for development and in the environment for production.
+CMS Ace is a hosted platform, so a site normally sets none of these except its domain, and it does that with Astro's own `site` setting, which Astro needs for canonical addresses anyway:
+
+```js
+export default defineConfig({ site: "https://www.example.com", integrations: [ace()] });
+```
+
+To try a site without editing the config, `npm run dev -- --site https://www.example.com` does the same. `ACE_SITE_DOMAIN`, when set, wins. Set `ACE_API_URL` and `ACE_PREVIEW_ADMIN_ORIGIN` (in `.env`) only to use a CMS running on your own machine, for example `http://localhost:8080` and `http://localhost:5173`.
 
 ## Pages
 

package/docs/command-line.md

@@ -1,8 +1,9 @@
 # The command line
 
-`ace-kit` is also a command. It signs you in to CMS Ace from your terminal, and writes types for your content.
+`ace-kit` is also a command. It makes new sites, signs you in to CMS Ace from your terminal, and writes types for your content.
 
 ```sh
+npx @sandboxsonny/ace-kit create my-site --site my-site.com   # make a new site (see Making a site)
 npx ace-kit login      # sign in
 npx ace-kit whoami     # who am I signed in as?
 npx ace-kit logout     # sign out
@@ -10,18 +11,46 @@ npx ace-kit generate   # write TypeScript types (see Typed content)
 npx ace-kit sync       # send your section types to the CMS (see Sections)
 ```
 
-Every command takes `--api-url`, or reads `ACE_API_URL` from the environment or a `.env` file in the folder you run it in. Failing both, it uses the address you last signed in to (kept in a small file beside your logins), so after `ace-kit login --api-url …` you can simply run `ace-kit whoami` from anywhere.
+Commands talk to the hosted CMS Ace unless told otherwise. Only for a CMS on your own machine, give `--api-url`, or set `ACE_API_URL` in the environment or a `.env` file in the folder you run it in. Failing both, a command uses the address you last signed in to (kept in a small file beside your logins), and failing that the hosted one, so `ace-kit login` and `ace-kit whoami` need no flags at all. Commands about a site (`sync`, `generate`) take `--site example.com`, or read `ACE_SITE_DOMAIN`.
+
+## Making a site
+
+```sh
+npx @sandboxsonny/ace-kit create my-site my-site.com
+```
+
+One command makes everything a new site needs:
+
+1. **Checks** the folder, the domain and the name, before anything is made.
+2. **Signs you in** if you aren't already (your browser opens; type the code from the terminal, as in [Signing in](#signing-in)).
+3. **Makes the site in CMS Ace** and gives it a starter: a `pages` content type, Home, About and Contact entries, a main menu and, for the Astro starter, the three example section types (hero, FAQ, gallery).
+4. **Copies a starter site** into `my-site/` with its name, domain and package name filled in.
+
+If a site with that domain already exists in CMS Ace, it is **left alone** (nothing is added to it, in case it has real content), a warning says so, and only the folder is made. If the CMS refuses to make the site (for instance, you have made as many as your account allows) nothing is made at all.
+
+Your account must be a **partner or super admin** (only they can make sites). The login `create` uses can set up the site it just made, for an hour, and no other site: it can't write content anywhere else.
+
+| Option                            | Meaning                                                                                |
+| --------------------------------- | -------------------------------------------------------------------------------------- |
+| `<domain>` (or `--site <domain>`) | The domain the site has in CMS Ace. Required.                                          |
+| `--framework astro\|react-router` | `astro` (the default) or `react-router`. The React Router starter has no sections yet. |
+| `--name <name>`                   | The name shown to visitors. Default: made from the folder, so `my-site` is "My Site".  |
+| `--api-url <address>`             | Only for a CMS on your own machine (or set `ACE_API_URL`).                             |
+
+Against a CMS on your own machine (`--api-url` or `ACE_API_URL` set to `http://localhost:8080`), it also writes a `.env` in the new folder with `ACE_API_URL` and `ACE_PREVIEW_ADMIN_ORIGIN=http://localhost:5173`, and sets the site's Preview address to the local dev server (`http://localhost:4321`, or 4322 for React Router), so the site and live preview work with no more setup. Against the hosted CMS Ace none of that is needed.
+
+The folder must not exist yet (or must be empty). The starter is a small server-rendered site with a header, footer, rich text, live preview and Prettier, ESLint, tests and a CI workflow. When it finishes: `cd my-site`, `npm install`, `npm run dev`.
 
 ## Signing in
 
 ```sh
-npx ace-kit login --api-url http://localhost:8080
+npx ace-kit login
 ```
 
 ```
-Signing in to http://localhost:8080
+Signing in to https://api.ace-cms.co.uk
 
-  1. Go to   http://localhost:5173/device
+  1. Go to   https://app.ace-cms.co.uk/device
   2. Type    BCDF-GHJK
 
 Check the code on that page matches. Waiting for you to approve it (Ctrl-C to cancel)...

package/docs/dev-sites.md

@@ -6,7 +6,7 @@ When your site's dev server works against a hosted CMS, it doesn't touch the liv
 
 On start, the dev server (the Astro integration, or the `ace()` Vite plugin on React Router):
 
-1. checks you are signed in (`npx ace-kit login`), and finds the site `ACE_SITE_DOMAIN` names;
+1. checks you are signed in (`npx ace-kit login`), and finds the site you are working on (Astro's `site` setting, or `ACE_SITE_DOMAIN`);
 2. asks the CMS for your dev site of it, which the CMS makes the first time as a copy of the live site: its content types, section types, menus and the **text** of its entries, with every link between entries pointing at the copy. Images are not copied yet, so image fields start empty;
 3. points the site at it: `ACE_SITE_DOMAIN` becomes the dev site's domain for as long as the dev server runs (your `.env` is not changed), so the site reads its content from the dev site, and section sync goes there;
 4. tells the CMS where the dev server is running, so the live preview in the admin app shows your dev server.
@@ -23,7 +23,7 @@ Partner accounts and super admins, for sites they own. Ask for a partner account
 
 ## Going to the live site
 
-A dev site is never merged into the live site. When your change is ready, deploy your site, then run `npx ace-kit sync` against the live site (`ACE_SITE_DOMAIN` set to the live domain, as in your `.env`). Deploy first: the live CMS then has the section types the deployed code expects.
+A dev site is never merged into the live site. When your change is ready, deploy your site, then run `npx ace-kit sync` against the live site (`--site www.example.com`, or `ACE_SITE_DOMAIN`). Deploy first: the live CMS then has the section types the deployed code expects.
 
 ## Settings
 

package/docs/getting-started.md

@@ -2,6 +2,14 @@
 
 Ace Kit is everything a website needs to use CMS Ace (see the [README](../README.md)): a typed client for the public API, addressing (`/{content type}/{entry}`), responsive images, menus, rich text, live preview support, and thin Astro and React adapters. It has no runtime dependencies.
 
+## Starting from nothing
+
+```sh
+npx @sandboxsonny/ace-kit create my-site my-site.com
+```
+
+makes an Astro (or, with `--framework react-router`, a React Router) site with everything below already wired up. See [the command line](./command-line.md#making-a-site). To add the kit to a site you already have, read on.
+
 ## Install
 
 ```sh

package/docs/react-router.md

@@ -26,11 +26,13 @@ export default defineConfig({ plugins: [ace(), reactRouter()] });
 
 The settings are environment variables, read when the server starts, so one build runs anywhere. Put them in `.env` for development and in the host's environment for production:
 
-| Variable                   | Default                 | Meaning                                                   |
-| -------------------------- | ----------------------- | --------------------------------------------------------- |
-| `ACE_API_URL`              | `http://localhost:8080` | where the CMS Ace API lives                               |
-| `ACE_SITE_DOMAIN`          | `localhost`             | the domain this site has in the CMS (the port is ignored) |
-| `ACE_PREVIEW_ADMIN_ORIGIN` | `http://localhost:5173` | where the CMS admin app runs                              |
+| Variable                   | Default                     | Meaning                                                   |
+| -------------------------- | --------------------------- | --------------------------------------------------------- |
+| `ACE_API_URL`              | `https://api.ace-cms.co.uk` | where the CMS Ace API lives                               |
+| `ACE_SITE_DOMAIN`          | `localhost`                 | the domain this site has in the CMS (the port is ignored) |
+| `ACE_PREVIEW_ADMIN_ORIGIN` | `https://app.ace-cms.co.uk` | where the CMS admin app runs                              |
+
+CMS Ace is a hosted platform, so a site normally sets only `ACE_SITE_DOMAIN`. Set the other two only to use a CMS on your own machine (`http://localhost:8080` and `http://localhost:5173`).
 
 **2. The server entry**, which renders pages and lets the CMS's admin app (and only it) frame the site for [live preview](./live-preview.md):
 

package/docs/sections.md

@@ -87,7 +87,7 @@ While the dev server runs, Ace Kit watches for `*.schema.ts` files (in `src`) an
 10:41:07 [ace-kit] Synced 3 section types (faq, gallery, hero) to localhost (http://localhost:8080).
 ```
 
-You don't run anything. You do need to be signed in once: `npx ace-kit login` (see [the command line](./command-line.md)). The sync goes to the site named by `ACE_SITE_DOMAIN` at `ACE_API_URL`, the same settings the site reads its content with, and only an owner of that site (or a super admin) can sync to it.
+You don't run anything. You do need to be signed in once: `npx ace-kit login` (see [the command line](./command-line.md)). The sync goes to the site the dev server is working on, the same one it reads its content from, and only an owner of that site (or a super admin) can sync to it.
 
 **Your dev site, not the live one.** Against a _hosted_ CMS the dev server works on a [dev site](./dev-sites.md): your own private copy of the site, made for you the first time, so a half-written field never reaches editors or visitors of the live site. The sync goes there. Against a CMS on your own machine there is no need for one, and the sync goes to the site itself.
 

package/docs/typed-content.md

@@ -3,16 +3,16 @@
 The kit can write TypeScript types for your site's content types, so `getEntry` and `getEntries` return the right shape and a change in the CMS shows up as a type error in your site.
 
 ```sh
-npx ace-kit generate --api-url http://localhost:8080 --domain localhost
+npx ace-kit generate --site www.example.com
 ```
 
 or with the settings in the environment:
 
 ```sh
-ACE_API_URL=http://localhost:8080 ACE_SITE_DOMAIN=localhost npx ace-kit generate
+ACE_SITE_DOMAIN=www.example.com npx ace-kit generate
 ```
 
-It reads `GET /public/content-types` (no login: it describes field names and kinds, never entries) and writes `src/ace-kit.generated.d.ts` (change it with `--out`). Make sure the file is inside your `tsconfig` `include`. Commit it, and run the command again whenever content types change (a good moment is a CI step, or a `generate` script next to `dev`).
+Add `--api-url http://localhost:8080` (or `ACE_API_URL`) only for a CMS on your own machine. It reads `GET /public/content-types` (no login: it describes field names and kinds, never entries) and writes `src/ace-kit.generated.d.ts` (change it with `--out`). Make sure the file is inside your `tsconfig` `include`. Commit it, and run the command again whenever content types change (a good moment is a CI step, or a `generate` script next to `dev`).
 
 ```ts
 // ace-kit.generated.d.ts (generated)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sandboxsonny/ace-kit",
-  "version": "0.4.0",
+  "version": "0.6.0",
   "description": "Everything a website needs to use CMS Ace: a typed client, addressing, images, menus, rich text, live preview, and Astro and React adapters.",
   "keywords": [
     "cms",
@@ -29,6 +29,7 @@
   "files": [
     "dist",
     "astro",
+    "templates",
     "docs",
     "CHANGELOG.md",
     "LICENSE"
@@ -87,8 +88,10 @@
     "format": "prettier --write .",
     "format:check": "prettier --check .",
     "typecheck": "tsc --noEmit",
-    "check": "npm run format:check && npm run lint && npm run typecheck && npm test && npm run build && npm run check:package",
+    "check": "npm run format:check && npm run lint && npm run typecheck && npm test && npm run build && npm run check:package && npm run check:templates",
     "check:package": "node scripts/check-package.mjs",
+    "check:templates": "node scripts/sync-templates.mjs --check",
+    "sync:templates": "node scripts/sync-templates.mjs",
     "pack:local": "npm run build && npm pack",
     "storybook": "storybook dev -p 6006",
     "build:storybook": "storybook build",

package/templates/astro/.dockerignore

@@ -0,0 +1,7 @@
+node_modules
+dist
+.astro
+.env
+.env.*
+!.env.example
+.vscode

package/templates/astro/.github/dependabot.yml

@@ -0,0 +1,19 @@
+version: 2
+updates:
+  - package-ecosystem: npm
+    directory: /
+    schedule:
+      interval: weekly
+    groups:
+      # Small upgrades arrive together as one pull request. A major version of anything is its own pull request, so
+      # one that needs a deliberate look (a new Astro or Ace Kit major) doesn't hold back the rest.
+      minor-and-patch:
+        update-types: [minor, patch]
+  - package-ecosystem: docker
+    directory: /
+    schedule:
+      interval: monthly
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: monthly

package/templates/astro/.github/workflows/ci.yml

@@ -0,0 +1,23 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  check:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: actions/setup-node@v7
+        with:
+          # Matches the Dockerfile's node:24-alpine, so CI tests what production runs.
+          node-version: 24
+          cache: npm
+      - run: npm ci
+      # Format, lint, types, tests and a build.
+      - run: npm run check

package/templates/astro/.prettierignore

@@ -0,0 +1,6 @@
+node_modules
+dist
+.astro
+public
+package-lock.json
+src/ace-kit.generated.d.ts

package/templates/astro/.prettierrc.json

@@ -0,0 +1,20 @@
+{
+  "printWidth": 120,
+  "tabWidth": 2,
+  "useTabs": false,
+  "semi": true,
+  "singleQuote": false,
+  "trailingComma": "all",
+  "bracketSpacing": true,
+  "arrowParens": "always",
+  "endOfLine": "lf",
+  "plugins": ["prettier-plugin-astro"],
+  "overrides": [
+    {
+      "files": "*.astro",
+      "options": {
+        "parser": "astro"
+      }
+    }
+  ]
+}

package/templates/astro/.vscode/extensions.json

@@ -0,0 +1,4 @@
+{
+  "recommendations": ["astro-build.astro-vscode"],
+  "unwantedRecommendations": []
+}

package/templates/astro/.vscode/launch.json

@@ -0,0 +1,11 @@
+{
+  "version": "0.2.0",
+  "configurations": [
+    {
+      "command": "./node_modules/.bin/astro dev",
+      "name": "Development server",
+      "request": "launch",
+      "type": "node-terminal"
+    }
+  ]
+}

package/templates/astro/AGENTS.md

@@ -0,0 +1,22 @@
+## Development
+
+When starting the dev server, use background mode:
+
+```
+astro dev --background
+```
+
+Manage the background server with `astro dev stop`, `astro dev status`, and `astro dev logs`.
+
+## Documentation
+
+Full documentation: https://docs.astro.build
+
+Consult these guides before working on related tasks:
+
+- [Adding pages, dynamic routes, or middleware](https://docs.astro.build/en/guides/routing/)
+- [Working with Astro components](https://docs.astro.build/en/basics/astro-components/)
+- [Using React, Vue, Svelte, or other framework components](https://docs.astro.build/en/guides/framework-components/)
+- [Adding or managing content](https://docs.astro.build/en/guides/content-collections/)
+- [Adding styles or using Tailwind](https://docs.astro.build/en/guides/styling/)
+- [Supporting multiple languages](https://docs.astro.build/en/guides/internationalization/)

package/templates/astro/Dockerfile

@@ -0,0 +1,17 @@
+FROM node:24-alpine AS production-dependencies-env
+COPY ./package.json package-lock.json /app/
+WORKDIR /app
+RUN npm ci --omit=dev
+
+FROM node:24-alpine AS build-env
+COPY . /app/
+WORKDIR /app
+RUN npm ci && npm run build
+
+FROM node:24-alpine
+ENV HOST=0.0.0.0
+COPY ./package.json package-lock.json /app/
+COPY --from=production-dependencies-env /app/node_modules /app/node_modules
+COPY --from=build-env /app/dist /app/dist
+WORKDIR /app
+CMD ["node", "dist/server/entry.mjs"]

package/templates/astro/_gitignore

@@ -0,0 +1,26 @@
+# build output
+dist/
+# generated types
+.astro/
+
+# dependencies
+node_modules/
+
+# logs
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+
+
+# environment variables
+.env
+.env.production
+
+# macOS-specific files
+.DS_Store
+
+# jetbrains setting folder
+.idea/
+.env.*
+!.env.example

package/templates/astro/astro.config.mjs

@@ -0,0 +1,18 @@
+// @ts-check
+import { defineConfig } from "astro/config";
+
+import node from "@astrojs/node";
+import ace from "@sandboxsonny/ace-kit/astro/integration";
+
+// https://astro.build/config
+export default defineConfig({
+  // The site's domain in CMS Ace. Ace Kit reads it from here (ACE_SITE_DOMAIN, if set, wins), so the dev server can find
+  // or make your own private copy of this site to work on.
+  site: "https://example.adamsdevelopment.co.uk",
+  // Pages are rendered on each request so they always show the CMS's live content.
+  output: "server",
+  adapter: node({ mode: "standalone" }),
+  // Ace Kit connects the site to CMS Ace: it declares ACE_API_URL, ACE_SITE_DOMAIN and ACE_PREVIEW_ADMIN_ORIGIN, and
+  // lets the CMS's admin app frame the site for live preview.
+  integrations: [ace()],
+});

package/templates/astro/eslint.config.js

@@ -0,0 +1,56 @@
+import eslint from "@eslint/js";
+import astro from "eslint-plugin-astro";
+import prettierConfig from "eslint-config-prettier";
+import globals from "globals";
+import typescriptEslint from "typescript-eslint";
+
+export default typescriptEslint.config(
+  { ignores: ["node_modules", "dist", ".astro", "public"] },
+
+  eslint.configs.recommended,
+  ...typescriptEslint.configs.recommended,
+  ...astro.configs.recommended,
+
+  {
+    files: ["**/*.{ts,astro,mjs}"],
+    languageOptions: { globals: { ...globals.browser, ...globals.node } },
+    rules: {
+      // Types are imported with `import type` from src/types.
+      "@typescript-eslint/consistent-type-imports": ["error", { fixStyle: "separate-type-imports" }],
+      "@typescript-eslint/no-unused-vars": ["error", { argsIgnorePattern: "^_", varsIgnorePattern: "^_" }],
+
+      // No abbreviated names in code. Spell it out: `request`, `response`, `message`...
+      "id-denylist": [
+        "error",
+        "req",
+        "res",
+        "resp",
+        "cfg",
+        "msg",
+        "btn",
+        "tmp",
+        "idx",
+        "evt",
+        "cb",
+        "fn",
+        "opts",
+        "args",
+        "val",
+        "num",
+        "str",
+        "obj",
+        "arr",
+      ],
+
+      eqeqeq: ["error", "always"],
+      "no-console": ["warn", { allow: ["error", "warn"] }],
+      "prefer-const": "error",
+    },
+  },
+
+  // Command-line scripts report what they did on the console.
+  { files: ["scripts/**"], rules: { "no-console": "off" } },
+
+  // Must stay last: turns off any rule that would fight with Prettier.
+  prettierConfig,
+);

package/templates/astro/package.json

@@ -0,0 +1,41 @@
+{
+  "name": "example-astro-site",
+  "type": "module",
+  "version": "0.0.1",
+  "engines": {
+    "node": ">=22.12.0"
+  },
+  "scripts": {
+    "dev": "astro dev",
+    "build": "astro build",
+    "preview": "astro preview",
+    "astro": "astro",
+    "lint": "eslint .",
+    "lint:fix": "eslint . --fix",
+    "format": "prettier --write .",
+    "format:check": "prettier --check .",
+    "typecheck": "astro check",
+    "check": "npm run format:check && npm run lint && npm run typecheck && npm test && npm run build",
+    "test": "vitest run --passWithNoTests",
+    "generate": "ace-kit generate"
+  },
+  "dependencies": {
+    "@astrojs/node": "^11.1.7",
+    "@sandboxsonny/ace-kit": "^0.5.0",
+    "astro": "^7.3.8"
+  },
+  "devDependencies": {
+    "@astrojs/check": "^0.9.10",
+    "@eslint/js": "^10.0.1",
+    "eslint": "^10.12.0",
+    "eslint-config-prettier": "^10.1.8",
+    "eslint-plugin-astro": "^1.7.0",
+    "globals": "^17.13.0",
+    "jsdom": "^29.1.1",
+    "prettier": "^3.9.10",
+    "prettier-plugin-astro": "^1.1.1",
+    "typescript": "^6.0.3",
+    "typescript-eslint": "^8.71.1",
+    "vitest": "^5.0.4"
+  }
+}

package/templates/astro/public/favicon.svg

@@ -0,0 +1,9 @@
+<svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 128 128">
+    <path d="M50.4 78.5a75.1 75.1 0 0 0-28.5 6.9l24.2-65.7c.7-2 1.9-3.2 3.4-3.2h29c1.5 0 2.7 1.2 3.4 3.2l24.2 65.7s-11.6-7-28.5-7L67 45.5c-.4-1.7-1.6-2.8-2.9-2.8-1.3 0-2.5 1.1-2.9 2.7L50.4 78.5Zm-1.1 28.2Zm-4.2-20.2c-2 6.6-.6 15.8 4.2 20.2a17.5 17.5 0 0 1 .2-.7 5.5 5.5 0 0 1 5.7-4.5c2.8.1 4.3 1.5 4.7 4.7.2 1.1.2 2.3.2 3.5v.4c0 2.7.7 5.2 2.2 7.4a13 13 0 0 0 5.7 4.9v-.3l-.2-.3c-1.8-5.6-.5-9.5 4.4-12.8l1.5-1a73 73 0 0 0 3.2-2.2 16 16 0 0 0 6.8-11.4c.3-2 .1-4-.6-6l-.8.6-1.6 1a37 37 0 0 1-22.4 2.7c-5-.7-9.7-2-13.2-6.2Z" />
+    <style>
+        path { fill: #000; }
+        @media (prefers-color-scheme: dark) {
+            path { fill: #FFF; }
+        }
+    </style>
+</svg>

package/templates/astro/src/ace-kit.generated.d.ts

@@ -0,0 +1,24 @@
+// Generated by ace-kit from localhost. Do not edit: run `ace-kit generate` to update it.
+import type { AceImageData, AceLinkData, AceRichTextDocument, AceSection } from "@sandboxsonny/ace-kit";
+
+declare module "@sandboxsonny/ace-kit" {
+  interface AceContentTypes {
+    /** Pages */
+    "pages": {
+      /** Headline */
+      "headline": string;
+      /** Body */
+      "body"?: AceRichTextDocument;
+      /** Hero image */
+      "hero"?: AceImageData;
+      /** Published */
+      "published"?: string;
+      /** Button */
+      "button"?: AceLinkData;
+      /** Content */
+      "content"?: AceSection[];
+    };
+  }
+}
+
+export {};