@omniharmonic/openspace-cli 0.0.0-stage → 0.1.1

package/dist/index.d.ts

@@ -0,0 +1,83 @@
+import { Command } from 'commander';
+import { ChildProcess } from 'node:child_process';
+
+type Severity = "error" | "warning";
+type CheckRule = "schema" | "block" | "link" | "redirect" | "image" | "media" | "size" | "secret" | "gating";
+interface Finding {
+    severity: Severity;
+    rule: CheckRule;
+    /** Repo-relative file the finding is in. */
+    file: string;
+    /** Location inside the file's JSON value (dot path), when known. */
+    path?: string;
+    /** 1-based line, when known (secrets). */
+    line?: number;
+    message: string;
+}
+interface Budgets {
+    /** `media/` total at which a warning is shown (arch §5.6: 600 MB). */
+    mediaWarnBytes: number;
+    /** `media/` total above which the check fails (900 MB). */
+    mediaFailBytes: number;
+    /** Longest image edge in px (the upload pipeline's cap). */
+    maxImageEdge: number;
+    /** GitHub rejects single files over 100 MB. */
+    maxFileBytes: number;
+}
+declare const DEFAULT_BUDGETS: Budgets;
+interface CheckOptions {
+    budgets?: Partial<Budgets>;
+}
+interface CheckReport {
+    ok: boolean;
+    errors: number;
+    warnings: number;
+    findings: Finding[];
+    stats: {
+        pages: number;
+        items: number;
+        mediaFiles: number;
+        mediaBytes: number;
+        filesScanned: number;
+    };
+}
+declare function runCheck(root: string, options?: CheckOptions): Promise<CheckReport>;
+/** Plain-text report grouped by file. */
+declare function formatReport(report: CheckReport, paint: (code: number, s: string) => string): string;
+
+/** Process I/O, injectable so commands are testable in-process. */
+interface Io {
+    cwd: string;
+    env: Record<string, string | undefined>;
+    out(text: string): void;
+    err(text: string): void;
+    /** Node version used for engine checks. */
+    nodeVersion: string;
+}
+
+type Spawner = (cmd: string, args: string[], opts: {
+    cwd: string;
+}) => ChildProcess;
+
+type FetchLike = (input: string, init?: RequestInit) => Promise<Response>;
+/** Run wrangler with `args`; resolves with its exit code. */
+type WranglerRunner = (args: string[], cwd: string) => Promise<number>;
+interface GatedSyncDeps {
+    fetch?: FetchLike;
+    wrangler?: WranglerRunner;
+}
+
+declare const VERSION = "0.1.0";
+/** Build the `openspace` command tree. Commands report problems by throwing `CliError`. */
+interface ProgramDeps {
+    spawner?: Spawner;
+    findBin?: (cwd: string) => string | undefined;
+    gatedSync?: GatedSyncDeps;
+}
+declare function createProgram(io: Io, setExit: (code: number) => void, deps?: ProgramDeps): Command;
+/** Run the CLI with `argv` (without node and script) and return the exit code. */
+declare function run(argv: string[], io: Io, deps?: ProgramDeps): Promise<number>;
+
+declare const name = "@omniharmonic/openspace-cli";
+
+export { type Budgets, type CheckOptions, type CheckReport, DEFAULT_BUDGETS, type Finding, VERSION, createProgram, formatReport, name, run, runCheck };

package/dist/index.js

@@ -0,0 +1,23 @@
+import { createRequire as __osCreateRequire } from "node:module"; const require = __osCreateRequire(import.meta.url);
+import {
+  DEFAULT_BUDGETS,
+  VERSION,
+  createProgram,
+  formatReport,
+  run,
+  runCheck
+} from "./chunk-LTJEM3DN.js";
+import "./chunk-3F6TAUAT.js";
+
+// src/index.ts
+var name = "@omniharmonic/openspace-cli";
+export {
+  DEFAULT_BUDGETS,
+  VERSION,
+  createProgram,
+  formatReport,
+  name,
+  run,
+  runCheck
+};
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/index.ts"],"sourcesContent":["export const name = \"@omniharmonic/openspace-cli\";\n\nexport {\n  type Budgets,\n  type CheckOptions,\n  type CheckReport,\n  DEFAULT_BUDGETS,\n  type Finding,\n  formatReport,\n  runCheck,\n} from \"./check\";\nexport { createProgram, run, VERSION } from \"./program\";\n"],"mappings":";;;;;;;;;;;;AAAO,IAAM,OAAO;","names":[]}

package/dist/starter/site/.github/workflows/publish.yml

@@ -0,0 +1,38 @@
+# .github/workflows/publish.yml (generated; managed by site-kit updates)
+name: Publish
+on:
+  push: { branches: [main] }
+  workflow_dispatch:
+permissions: { contents: read, pages: write, id-token: write }
+concurrency: { group: publish, cancel-in-progress: true }
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: actions/setup-node@v7
+        # package.json keys the npm cache: Hub-created sites have no lockfile at first.
+        with: { node-version: 24, cache: npm, cache-dependency-path: package.json }
+      - uses: actions/cache@v6
+        with:
+          path: node_modules/.astro
+          key: os-assets-${{ hashFiles('media/**') }}
+          restore-keys: os-assets-
+      # Sites created by the Hub start without a lockfile.
+      - run: if [ -f package-lock.json ]; then npm ci; else npm install; fi
+      - run: npx openspace check --ci # schema, links, budgets, secret scan
+      - run: npm run build # astro build (+ pagefind, og images)
+        env:
+          OPENSPACE_TURNSTILE_SITE_KEY: ${{ vars.OPENSPACE_TURNSTILE_SITE_KEY }}
+          # Self-host the font pairing (downloaded once from Google Fonts during the build).
+          OPENSPACE_GOOGLE_FONTS: download
+          OPENSPACE_REMOTE_IMAGES: download
+      - uses: actions/upload-pages-artifact@v5
+        with: { path: dist }
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: { name: github-pages, url: "${{ steps.d.outputs.page_url }}" }
+    steps:
+      - id: d
+        uses: actions/deploy-pages@v5

package/dist/starter/site/AGENTS.md

@@ -0,0 +1,392 @@
+<!-- Generated by @omniharmonic/openspace-site-kit from the schema and block registry. Do not edit by hand; run `npx openspace agents-md` to refresh. -->
+# AGENTS.md — this OpenSpace site
+
+This repository is an OpenSpace website. The content and design choices live here; the code
+lives in versioned npm packages (`@omniharmonic/openspace-site-kit`). Publishing happens automatically when
+changes land on `main` (`.github/workflows/publish.yml`).
+
+## Rules
+
+1. **Content lives in `content/`.** Never hand-edit `src/`, `astro.config.mjs` or the
+   workflow unless you were asked for a custom block (`src/overrides/`).
+2. **Preserve ids.** Every page (`pg_`), section (`sec_`), block (`blk_`), media item (`med_`)
+   and form (`frm_`) has a stable id. Keep ids when editing; new ids are the prefix plus 10
+   lowercase Crockford base32 characters (no i, l, o, u).
+3. **Only valid block types and fields** (listed below; full JSON Schema at
+   https://schema.openspace.dev/v1/). Unknown fields fail the build.
+4. **Styles change through tokens** in `content/styles.json` (palette, type pairing, density,
+   shape…), never inline CSS. Sections pick one of five color themes.
+5. **Never put secrets in content** (API keys, tokens, passwords). `openspace check` fails on them.
+   Members-only and password pages are only stubs here (a page file with `contentRef` and no
+   sections): their content is kept by the OpenSpace Hub and never committed. Edit them in
+   Studio or with the Hub's MCP tools; never add sections to a stub (they would be public).
+6. **Run `npx openspace check` before committing.** It validates schemas, links, image references,
+   size budgets and scans for secrets.
+7. Write real copy in the owner's voice. No placeholder text, no invented testimonials, prices
+   or facts — ask the owner.
+
+## Layout
+
+```
+openspace.json               site id, Hub URL, deploy target, features (https://schema.openspace.dev/v1/site-config.json)
+content/site.json            title, navigation, header, footer, SEO defaults, redirects
+content/styles.json          design tokens and Site Styles choices
+content/media.json           metadata for files in media/ (alt text, size, focal point, credit)
+content/pages/home.json      the home page (slug ""); other pages mirror their URL:
+content/pages/about.json     → /about/      content/pages/services/pricing.json → /services/pricing/
+content/collections/<name>/_collection.json   collection kind, list + item page layout, feeds
+content/collections/<name>/<slug>.mdoc        one item: YAML frontmatter + Markdoc body
+media/                       images ≤ 2400px on the long edge, audio, files
+```
+
+A page is `{ id, title, slug, seo?, sections: [...] }`; a section has a `layout` (`stack` with
+column spans that add up to 12, or `grid`) and `blocks`; a block is
+`{ id, type, v, fields, variant?, style? }`.
+
+## Collection items (Markdoc)
+
+Frontmatter follows the collection kind (blog, events, portfolio, podcast, products): `title`,
+`status` (draft | scheduled | published), `publishAt` for scheduled items, `excerpt`, `image`,
+`categories`, `tags`, plus kind-specific fields (`date`, `start`/`end`, `price` in minor units…).
+
+The body is Markdown prose plus Markdoc tags. **Tags map 1:1 to blocks**: the tag name is the
+block type, attributes are its fields, and content between the tags fills its text:
+
+```markdoc
+{% gallery layout="grid" images=["media/2026/10/a.jpg", "media/2026/10/b.jpg"] /%}
+
+{% button href="/schedule" variant="primary" %}See the schedule{% /button %}
+```
+
+No scripts or raw HTML: anything interactive is a block.
+
+## Running locally
+
+- `npm install`, then `npm run dev` for a live preview.
+- `npx openspace mcp` starts the local MCP server so an AI assistant can edit through the same
+  structured operations as the Studio.
+- `npm run build` builds the site into `dist/` exactly as the publish workflow does.
+
+## Blocks
+
+### `accordion` — Accordion / FAQ
+
+Expandable questions and answers, with schema.org FAQPage markup. Use: FAQs, policies, class or service details — anything visitors scan for one answer. 4–10 items works best. Avoid: Hiding essential information (prices, hours) only inside an accordion; answers longer than a short paragraph or list.
+
+- Variants: `lines`, `cards`, `minimal`
+- Fields: `items: list of { question: text ≤ 160, answer: richText }`, `exclusive: boolean`, `openFirst: boolean`, `faqSchema: boolean`
+
+### `audio` — Audio / podcast episode
+
+Plays one audio file — a podcast episode, track, talk or guided practice — with its notes. Use: Episode pages, music and talks. Add listen links for the podcast apps the show is on. `minimal` is just the player and title. Avoid: Autoplay (never supported); audio without a written summary or transcript link for deaf visitors.
+
+- Variants: `episode`, `card`, `minimal`
+- Fields: `audio?: media`, `title: text ≤ 120`, `show?: text ≤ 80`, `episode?: number`, `date?: text ≤ 10`, `description?: text ≤ 600`, `cover?: image { src, alt }`, `links: list of { platform: "apple" | "spotify" | "youtube" | "rss" | "other", label?: text ≤ 40, link: link }`, `credit?: text ≤ 200`
+
+### `before-after` — Before / after
+
+Compares two matching images with a draggable divider: renovations, retouching, seasons. Use: When the difference between two shots of the same view is the point. Use images with identical framing and size. Avoid: Unrelated images; misleading edits; more than one or two per page.
+
+- Variants: `labels`, `minimal`
+- Fields: `before: image { src, alt }`, `after: image { src, alt }`, `beforeLabel: text ≤ 30`, `afterLabel: text ≤ 30`, `start: number`, `aspect: "original" | "1:1" | "4:5" | "2:3" | "3:2" | "16:9" | "21:9"`, `caption?: text ≤ 200`
+
+### `booking` — Booking
+
+Lets visitors book an appointment through the owner's Cal.com or Calendly page. Use: Services, coaching, consultations and classes booked by time slot. The scheduler loads only after a click, so the page stays fast and private. `button` just links out. Avoid: Scheduling links the owner hasn't set up; more than one booking block per page.
+
+- Variants: `inline`, `split`, `button`
+- Fields: `url: text ≤ 300`, `provider: "auto" | "cal" | "calendly"`, `heading?: text ≤ 80`, `headingLevel: "h2" | "h3" | "h4"`, `description?: text ≤ 300`, `buttonLabel: text ≤ 30`, `height: "640" | "760" | "900"`
+
+### `button` — Button
+
+A clear call to action linking to a page, booking tool, email or file. Use: Once per screenful for the main action. Add a second (secondary-style) action only when it's a genuine alternative. Avoid: Several primary buttons side by side; vague labels like 'Click here' or 'Learn more' without context.
+
+- Variants: `default`, `large`, `full-width`
+- Fields: `label: text ≤ 40`, `link: link`, `role: "primary" | "secondary" | "tertiary"`, `secondaryLabel?: text ≤ 40`, `secondaryLink?: link`, `note?: text ≤ 120`
+
+### `card` — Card
+
+One self-contained item — a service, offer, event or article teaser — with an optional link. Use: Place 2–4 cards side by side in stack columns for services or offers. `overlay` sets text on the photo; `horizontal` suits wide columns. Avoid: Long body text (keep under ~40 words); different aspect ratios across cards in a row.
+
+- Variants: `stacked`, `horizontal`, `overlay`, `minimal`
+- Fields: `image?: image { src, alt }`, `aspect: "original" | "1:1" | "4:5" | "2:3" | "3:2" | "16:9" | "21:9"`, `icon?: "check" | "star" | "heart" | "leaf" | "sprout" | "flower" | "sun" | "moon" | "sparkles" | "mountain" | "waves" | "map-pin" | "phone" | "mail" | "message-circle" | "clock" | "calendar" | "coffee" | "utensils" | "music" | "camera" | "palette" | "brush" | "book-open" | "graduation-cap" | "user" | "users" | "heart-handshake" | "home" | "shield-check" | "lock" | "award" | "target" | "lightbulb" | "zap" | "rocket" | "gift" | "shopping-bag" | "package" | "truck" | "recycle" | "globe" | "wifi" | "car" | "bike" | "dumbbell" | "accessibility" | "baby" | "dog" | "paw-print" | "scissors" | "wrench" | "arrow-right"`, `eyebrow?: text ≤ 40`, `heading: text ≤ 90`, `body: richText`, `link?: link`, `linkLabel?: text ≤ 30`
+
+### `chart` — Chart
+
+Shows a small set of numbers as a bar, column, line or pie chart. Use: Up to ~12 values that tell one story: results, survey answers, growth over time. `line` for change over time, `pie` for shares of a whole (2–6 slices). Avoid: Invented or unsourced figures; pies with many slices; charts that need more than one series.
+
+- Variants: `bar`, `column`, `line`, `pie`
+- Fields: `title: text ≤ 120`, `description?: text ≤ 240`, `rows: list of { label: text ≤ 40, value: number }`, `prefix?: text ≤ 4`, `suffix?: text ≤ 12`, `showValues: boolean`, `showTable: boolean`
+
+### `columns` — Columns
+
+Parallel content in columns: a feature trio, numbered steps, or short offers. Use: When 2–4 items share the same shape. `steps` numbers them for a process; `cards` puts each on a surface. Avoid: Uneven text lengths across columns; more than four columns; long paragraphs.
+
+- Variants: `plain`, `cards`, `steps`
+- Fields: `items: list of { image?: image { src, alt }, heading: text ≤ 80, body: richText, link?: link, linkLabel?: text ≤ 30 }`, `columns: "2" | "3" | "4"`, `aspect: "original" | "1:1" | "4:5" | "2:3" | "3:2" | "16:9" | "21:9"`
+
+### `contact-info` — Contact details
+
+How to reach or visit the business: address, phone, email. Use: Contact pages, footers and beside a map or form. `columns` lays the details side by side on wide screens. Avoid: Personal phone numbers or addresses the owner hasn't chosen to publish.
+
+- Variants: `card`, `list`, `columns`
+- Fields: `heading?: text ≤ 60`, `headingLevel: "h2" | "h3" | "h4"`, `name?: text ≤ 80`, `address?: text ≤ 240`, `phone?: text ≤ 30`, `email?: text ≤ 120`, `directions: boolean`, `note?: text ≤ 200`
+
+### `countdown` — Countdown
+
+A live countdown to a moment: a launch, a sale ending, an event starting. Use: Time-bound announcements near a call to action. The exact date is always printed too, so it still works without JavaScript. Avoid: Fake urgency (timers that reset); countdowns to dates that have long passed.
+
+- Variants: `boxes`, `inline`, `large`
+- Fields: `heading?: text ≤ 80`, `headingLevel: "h2" | "h3" | "h4"`, `target: text ≤ 32`, `showSeconds: boolean`, `doneMessage: text ≤ 160`, `buttonLabel?: text ≤ 30`, `link?: link`
+
+### `divider` — Divider with ornament
+
+A decorative separator: a small ornament or label between thin lines. Use: Between passages of long-form text, menus or story pages where a plain line feels too stark. One or two per page. Avoid: Separating every block; ornaments that clash with a minimal site style.
+
+- Variants: `lines`, `ornament`, `label`
+- Fields: `ornament: "flourish" | "star" | "diamond" | "dots" | "leaf" | "wave" | "asterism"`, `label?: text ≤ 40`, `length: "short" | "half" | "full"`, `color: color`
+
+### `donation` — Donation
+
+Collects donations: preset or custom amounts, one-time or monthly. Use: Non-profits, community projects and creators. Say concretely what a gift pays for. `link` mode points to an existing donation page (Open Collective, Stripe Payment Link…). Avoid: Amounts or causes the owner hasn't approved; promising tax deductibility without confirming it.
+
+- Variants: `card`, `inline`, `split`
+- Fields: `heading?: text ≤ 80`, `headingLevel: "h2" | "h3" | "h4"`, `description?: text ≤ 400`, `mode: "checkout" | "link"`, `currency: "USD" | "EUR" | "GBP" | "CAD" | "AUD" | "NZD" | "CHF" | "SEK" | "NOK" | "DKK" | "JPY"`, `amounts: list of { amount: number }`, `allowCustom: boolean`, `frequency: "both" | "once" | "monthly"`, `buttonLabel: text ≤ 30`, `link?: link`, `note?: text ≤ 200`
+
+### `embed` — Embed / Code
+
+Embeds third-party widgets (booking, surveys, tickets, playlists) by URL or HTML snippet. Use: Only when no dedicated block exists for the service. Avoid: Tracking scripts; snippets with secrets or API keys; embedding YouTube/Vimeo (use the video block) or maps (use the map block).
+
+- Variants: `plain`, `framed`
+- Fields: `embed: embed`, `title: text ≤ 120`, `aspect: "auto" | "16:9" | "4:3" | "1:1"`, `height: number`
+
+### `events` — Events
+
+Shows events from the events collection: dates, times, places and a way to register. Use: Home, schedule and community pages. `calendar` shows month grids with an agenda below; `list` is the most scannable. Avoid: Typing events into text blocks (add them to the events collection so they stay in sync).
+
+- Variants: `list`, `cards`, `calendar`
+- Fields: `heading?: text ≤ 80`, `headingLevel: "h2" | "h3" | "h4"`, `source: reference`, `showImage: boolean`, `showLocation: boolean`, `showExcerpt: boolean`, `registerLabel: text ≤ 30`, `emptyMessage: text ≤ 160`, `structuredData: boolean`
+
+### `form` — Form
+
+Collects enquiries, bookings requests, RSVPs or applications into the owner's Inbox. Use: Contact pages and anywhere visitors need to send structured details. Pair with a short text block explaining what happens next. Avoid: Long forms (keep under ~8 fields); asking for sensitive data; password or payment fields (not allowed — payments go through checkout).
+
+- Variants: `default`, `card`, `underline`
+- Fields: `form: form`
+
+### `gallery` — Gallery
+
+Several related photographs shown together. Use: Portfolios, spaces, events and products. `grid` for tidy sets, `masonry` and `strips` for mixed orientations, `carousel` for many images in little space, `slideshow` for one large image at a time. Avoid: Mixing unrelated photos; fewer than three images (use the image block); captions that repeat alt text.
+
+- Variants: `grid`, `carousel`, `masonry`, `slideshow`, `strips`
+- Fields: `images: list of { image: image { src, alt }, caption?: text ≤ 160, link?: link }`, `aspect: "auto" | "original" | "1:1" | "4:5" | "2:3" | "3:2" | "16:9" | "21:9"`, `columns: "2" | "3" | "4" | "5"`, `lightbox: boolean`, `showCaptions: boolean`
+
+### `heading` — Heading
+
+A section heading with optional eyebrow and supporting line. Use: To open a section or introduce a group of blocks. `rule` adds a short accent line above, `underline` a line below, `split` puts the subheading beside the heading on wide screens. Avoid: Using headings for emphasis inside body copy (use text); skipping levels (h2 → h4); more than one Heading 1 per page.
+
+- Variants: `plain`, `rule`, `underline`, `split`
+- Fields: `eyebrow?: text ≤ 60`, `text: text ≤ 160`, `level: "h1" | "h2" | "h3" | "h4"`, `size: "auto" | "display" | "h1" | "h2" | "h3" | "h4"`, `subheading?: text ≤ 280`
+
+### `hours` — Opening hours
+
+When a place is open, day by day. Use: Contact, visit and footer areas of shops, studios, cafés and offices. Pair with the contact card or map. Avoid: Hours the owner hasn't confirmed; using it for event times (use events).
+
+- Variants: `table`, `compact`, `card`
+- Fields: `heading?: text ≤ 60`, `headingLevel: "h2" | "h3" | "h4"`, `rows: list of { day: "mon" | "tue" | "wed" | "thu" | "fri" | "sat" | "sun", opens?: text ≤ 5, closes?: text ≤ 5, closed: boolean }`, `note?: text ≤ 200`
+
+### `icon-list` — Icon list
+
+A scannable list of features, amenities, benefits or what's included. Use: Services and pricing pages, 'what to expect' sections. 3–8 items. Avoid: Using icons that don't match the meaning; paragraphs instead of one-line points.
+
+- Variants: `list`, `tiles`, `checklist`
+- Fields: `items: list of { icon: "check" | "star" | "heart" | "leaf" | "sprout" | "flower" | "sun" | "moon" | "sparkles" | "mountain" | "waves" | "map-pin" | "phone" | "mail" | "message-circle" | "clock" | "calendar" | "coffee" | "utensils" | "music" | "camera" | "palette" | "brush" | "book-open" | "graduation-cap" | "user" | "users" | "heart-handshake" | "home" | "shield-check" | "lock" | "award" | "target" | "lightbulb" | "zap" | "rocket" | "gift" | "shopping-bag" | "package" | "truck" | "recycle" | "globe" | "wifi" | "car" | "bike" | "dumbbell" | "accessibility" | "baby" | "dog" | "paw-print" | "scissors" | "wrench" | "arrow-right", title: text ≤ 60, text?: text ≤ 200 }`, `columns: "1" | "2" | "3" | "4"`
+
+### `image` — Image
+
+A single photograph or illustration. Use: To show the place, the people, the work or the product. Keep aspect ratios consistent within a section. `caption-overlay` suits atmospheric shots; `inset` frames an image on a soft surface. Avoid: Stock photos that don't depict the business; text baked into images; missing alt text.
+
+- Variants: `default`, `caption-overlay`, `inset`
+- Fields: `image: image { src, alt }`, `aspect: "original" | "1:1" | "4:5" | "2:3" | "3:2" | "16:9" | "21:9"`, `caption?: text ≤ 200`, `link?: link`, `lightbox: boolean`
+
+### `line` — Line
+
+A visual divider between pieces of content. Use: To separate groups inside a section, or as a short accent rule above a heading (`length: short`, color `accent`). Avoid: Lines between every block; using lines where whitespace or a section change would do.
+
+- Variants: `solid`, `dashed`, `dotted`, `fade`
+- Fields: `thickness: "hairline" | "regular" | "bold"`, `length: "full" | "half" | "short"`, `color: color`
+
+### `link-list` — Link list
+
+A link-in-bio list: a few large, tappable links under a photo and one-line bio. Use: On a dedicated links page shared from social profiles, or a compact 'start here' list. Put the most important link first and highlight at most one. Avoid: More than ~8 links; vague labels like 'Click here'; duplicating the main navigation.
+
+- Variants: `stacked`, `outline`, `cards`
+- Fields: `photo?: image { src, alt }`, `name?: text ≤ 60`, `bio?: text ≤ 200`, `links: list of { label: text ≤ 60, link: link, icon?: "check" | "star" | "heart" | "leaf" | "sprout" | "flower" | "sun" | "moon" | "sparkles" | "mountain" | "waves" | "map-pin" | "phone" | "mail" | "message-circle" | "clock" | "calendar" | "coffee" | "utensils" | "music" | "camera" | "palette" | "brush" | "book-open" | "graduation-cap" | "user" | "users" | "heart-handshake" | "home" | "shield-check" | "lock" | "award" | "target" | "lightbulb" | "zap" | "rocket" | "gift" | "shopping-bag" | "package" | "truck" | "recycle" | "globe" | "wifi" | "car" | "bike" | "dumbbell" | "accessibility" | "baby" | "dog" | "paw-print" | "scissors" | "wrench" | "arrow-right", highlight: boolean }`, `showSocial: boolean`
+
+### `logo-strip` — Logo strip
+
+Logos of publications, clients, partners or certifications. Use: Below a hero or near a call to action as social proof. 4–8 logos reads best. Avoid: Logos without permission or for relationships that don't exist; mixing press and clients in one strip.
+
+- Variants: `row`, `grid`, `marquee`
+- Fields: `label?: text ≤ 60`, `logos: list of { name: text ≤ 60, logo?: image { src, alt }, link?: link }`, `monochrome: boolean`
+
+### `map` — Map
+
+Shows where a place is, with the address and a link to full maps. Use: Contact and visit pages for any business with a physical location. Set latitude/longitude precisely; add parking or access notes in details. Avoid: Guessing coordinates — ask the owner or geocode the exact address; maps for online-only businesses.
+
+- Variants: `card`, `plain`, `split`
+- Fields: `name?: text ≤ 80`, `address: text ≤ 200`, `latitude: number`, `longitude: number`, `zoom: number`, `details?: text ≤ 240`, `linkLabel: text ≤ 40`, `tileServer?: text ≤ 300`, `aspect: "16:9" | "3:2" | "4:3" | "1:1"`
+
+### `marquee` — Scrolling text
+
+A continuously scrolling line of short phrases, like a ticker or a shop-window band. Use: For energy between sections: offerings, places, a short slogan. 3–8 phrases of 1–3 words. `band` sets it on an accent strip. Avoid: Essential information (it moves and can be paused); long sentences; more than one per page. It never moves for visitors who prefer reduced motion.
+
+- Variants: `text`, `outline`, `band`
+- Fields: `items: list of { text: text ≤ 60 }`, `separator: "star" | "dot" | "slash" | "dash" | "none"`, `size: "lead" | "h3" | "h2" | "display"`, `speed: "slow" | "medium" | "fast"`
+
+### `member-login` — Member sign-in
+
+Lets members sign in with an emailed link, or tells visitors that content is members-only. Use: On the members' sign-in page (`form`), at the top of a members-only page's public teaser (`gated`), or as a slim prompt (`banner`). Members need the Cloudflare hosting option. Avoid: Putting the members-only content itself on a public page; asking for passwords.
+
+- Variants: `form`, `gated`, `banner`
+- Fields: `heading?: text ≤ 80`, `headingLevel: "h2" | "h3" | "h4"`, `description?: text ≤ 300`, `buttonLabel: text ≤ 30`, `successMessage: text ≤ 200`, `signInLink?: link`, `joinLabel?: text ≤ 40`, `joinLink?: link`
+
+### `newsletter` — Newsletter signup
+
+Collects email subscribers (double opt-in) for the owner's newsletter. Use: Footers, the end of blog posts, and dedicated 'stay in touch' sections. Say what subscribers get and how often. Avoid: Promising content or frequency the owner hasn't agreed to; more than one signup per page.
+
+- Variants: `inline`, `stacked`, `card`, `banner`
+- Fields: `heading?: text ≤ 80`, `description?: text ≤ 240`, `askName: boolean`, `placeholder: text ≤ 60`, `buttonLabel: text ≤ 30`, `successMessage: text ≤ 200`, `note?: text ≤ 160`
+
+### `pricing` — Pricing table
+
+Compares plans, packages or tiers with prices and what each includes. Use: Pricing, membership and service-package pages. 2–4 plans; mark at most one as featured. Keep inclusions parallel across plans. Avoid: Prices the owner hasn't confirmed; hidden fees; more than ~6 inclusions per plan; using it for a single product (use the product block).
+
+- Variants: `cards`, `columns`, `compact`
+- Fields: `plans: list of { name: text ≤ 60, price: text ≤ 24, period?: text ≤ 30, description?: text ≤ 200, features: list of { text: text ≤ 120 }, buttonLabel?: text ≤ 30, link?: link, featured: boolean, badge?: text ≤ 24 }`, `note?: text ≤ 200`
+
+### `product` — Product
+
+Sells one product from the shop: image, price, options and an Add to cart button. Use: Featuring a single product on a landing page or inside a story. The price shown comes from the catalog; checkout always re-reads prices on the server. Avoid: Products that don't exist in the shop collection; writing prices by hand in text blocks.
+
+- Variants: `card`, `split`, `minimal`
+- Fields: `product: reference`, `showDescription: boolean`, `quantity: boolean`, `buttonLabel: text ≤ 30`, `detailsLabel: text ≤ 30`
+
+### `quote` — Quote
+
+A short, memorable quotation set apart from body text. Use: To pause the reader between sections, or to open a page with an epigraph. `large` is a centred statement, `bar` sits inside reading text. Avoid: Customer reviews (use testimonial); misattributed or invented quotes; quotes longer than three sentences.
+
+- Variants: `classic`, `large`, `bar`
+- Fields: `quote: richText`, `attribution?: text ≤ 80`, `source?: text ≤ 120`
+
+### `quote-carousel` — Quote carousel
+
+Several short quotes from clients or reviews in a swipeable carousel. Use: Social proof when there are four or more good testimonials and little space. `slides` shows one large quote at a time, `cards` several side by side. Avoid: Invented or edited quotes; fewer than three quotes (use testimonial); quotes over three sentences.
+
+- Variants: `slides`, `cards`, `minimal`
+- Fields: `label: text ≤ 80`, `quotes: list of { quote: text ≤ 400, name: text ≤ 80, role?: text ≤ 100, photo?: image { src, alt } }`
+
+### `restaurant-menu` — Menu
+
+A restaurant, café or bar menu: sections of dishes with descriptions and prices. Use: Menu pages and hospitality sites. Keep descriptions to one line; mark dietary information accurately. `columns` sets sections side by side on wide screens. Avoid: Out-of-date prices; dietary claims the kitchen can't guarantee; using it for services (use the pricing table).
+
+- Variants: `classic`, `columns`, `minimal`
+- Fields: `sections: list of { title: text ≤ 60, note?: text ≤ 160, items: list of { name: text ≤ 80, description?: text ≤ 240, price?: text ≤ 24, dietary: list of { tag: "v" | "vg" | "gf" | "df" | "n" | "spicy" } } }`, `currency?: text ≤ 4`, `legend: boolean`, `footnote?: text ≤ 240`
+
+### `search` — Search
+
+Opens the site's built-in search (Pagefind), which indexes every published page. Use: Sites with a blog, events or many pages — on a resources page, a 404 page or at the top of the journal. `icon` fits tight spaces. Avoid: Small sites of a few pages, where navigation is enough.
+
+- Variants: `field`, `button`, `icon`
+- Fields: `placeholder: text ≤ 60`, `shortcutHint: boolean`
+
+### `shape` — Shape
+
+Decorative shapes (blob, arch, sparkle, squiggle…) in palette colors. Use: In grid sections, layered behind or beside images and text to add warmth and brand character. Keep to one or two per section. Avoid: Using shapes to carry meaning or text; bright shapes behind body text that hurt contrast.
+
+- Variants: `solid`, `outline`, `soft`
+- Fields: `shape: "circle" | "ring" | "blob" | "arch" | "half-circle" | "pill" | "squircle" | "triangle" | "sparkle" | "star" | "flower" | "wave"`, `color: color`, `size: "sm" | "md" | "lg" | "fill"`, `rotate: number`, `stretch: boolean`
+
+### `share-buttons` — Share buttons
+
+Share links for the page being viewed (blog posts, events, announcements). Use: At the end of articles and event pages. Avoid: Putting share buttons on every page; more than four or five networks.
+
+- Variants: `icons`, `labels`, `pills`
+- Fields: `label?: text ≤ 40`, `networks: list of { network: "x" | "facebook" | "linkedin" | "bluesky" | "threads" | "pinterest" | "email" }`
+
+### `social-feed` — Social feed
+
+A grid of recent posts from the owner's social profile, linking to each post. Use: Near the footer or on about pages to show everyday life. Posts are fetched at publish time with the owner's permission, so no third-party scripts load. Avoid: Embedding other people's posts; feeds as the main content of a page.
+
+- Variants: `grid`, `row`, `mosaic`
+- Fields: `heading?: text ≤ 80`, `headingLevel: "h2" | "h3" | "h4"`, `network: "instagram" | "bluesky" | "mastodon" | "pinterest" | "tiktok" | "youtube"`, `handle: text ≤ 80`, `count: "3" | "4" | "6" | "8"`, `followLabel: text ≤ 40`, `posts: list of { image: image { src, alt }, url: link, caption?: text ≤ 200 }`
+
+### `social-links` — Social links
+
+Links to the owner's social media and email. Use: Footers, contact and about pages. Prefer `source: site` so profiles stay in sync across the site. Avoid: Linking to inactive accounts; more than ~6 networks.
+
+- Variants: `icons`, `labels`, `pills`
+- Fields: `source: "site" | "custom"`, `profiles: list of { network: "instagram" | "facebook" | "x" | "threads" | "bluesky" | "mastodon" | "linkedin" | "youtube" | "tiktok" | "pinterest" | "github" | "spotify" | "soundcloud" | "bandcamp" | "vimeo" | "behance" | "dribbble" | "substack" | "patreon" | "yelp" | "tripadvisor" | "email" | "website", url: text ≤ 300 }`, `label?: text ≤ 60`
+
+### `spacer` — Spacer
+
+Extra vertical space between blocks, sized from the site's spacing scale. Use: Sparingly, to give a heading or image more air than the default block gap. Avoid: Stacking spacers; using spacers to fake section padding (adjust the section instead).
+
+- Variants: —
+- Fields: `height: "xs" | "sm" | "md" | "lg" | "xl" | "2xl" | "3xl"`, `mobileHeight?: "xs" | "sm" | "md" | "lg" | "xl" | "2xl" | "3xl"`
+
+### `stats` — Stats
+
+Key figures that make a claim concrete (members, years, ratings, outcomes). Use: On about, services and fundraising pages; 3–4 numbers read best. `large` gives each number its own row. Avoid: Invented, rounded-up or unverifiable figures; more than six stats; vanity numbers.
+
+- Variants: `row`, `cards`, `large`
+- Fields: `items: list of { value: text ≤ 16, label: text ≤ 80, detail?: text ≤ 140 }`
+
+### `summary` — Summary
+
+Lists items from a collection (blog posts, events, projects, episodes, products) as cards. Use: On the home page and landing pages to surface fresh content: the latest 3 posts, featured projects, upcoming events. `wall` is a masonry of images for portfolios; `carousel` saves space. Avoid: Using it as the main collection page (the collection's own list page does that); mixing unrelated filters; more than ~12 items.
+
+- Variants: `grid`, `list`, `carousel`, `wall`
+- Fields: `heading?: text ≤ 80`, `headingLevel: "h2" | "h3" | "h4"`, `source: reference`, `columns: "2" | "3" | "4"`, `showImage: boolean`, `showDate: boolean`, `showExcerpt: boolean`, `showMeta: boolean`, `linkLabel?: text ≤ 30`, `link?: link`, `emptyMessage: text ≤ 160`
+
+### `tabs` — Tabs
+
+Parallel pieces of content shown one at a time, switched by tabs. Use: Comparable options (class styles, service tiers, menus by meal) where visitors want one at a time. 2–5 tabs with short labels. Avoid: Content everyone needs to read (tabs hide it); long labels; sequences (use a timeline) or FAQs (use an accordion).
+
+- Variants: `underline`, `pills`, `vertical`
+- Fields: `label: text ≤ 80`, `items: list of { label: text ≤ 40, content: richText }`
+
+### `team` — Team
+
+Introduces the people behind the business: staff, teachers, partners, a board. Use: About and team pages, and near services where visitors choose a person. `circles` suits large teams; `list` gives each bio more room. Avoid: People who haven't agreed to appear; stock photos presented as staff; bios over ~60 words.
+
+- Variants: `grid`, `list`, `circles`
+- Fields: `people: list of { name: text ≤ 80, role?: text ≤ 80, photo?: image { src, alt }, bio?: text ≤ 320, link?: link }`, `columns: "2" | "3" | "4"`
+
+### `testimonial` — Testimonial
+
+A short quote from a client or customer, attributed to a named person. Use: Social proof near a call to action or on a services page. Use three side by side (`card`) or one `large` testimonial as a section's centrepiece. Avoid: Inventing testimonials or ratings. Ask the owner for real quotes and permission to use names and photos.
+
+- Variants: `card`, `large`, `minimal`
+- Fields: `quote: richText`, `name: text ≤ 80`, `role?: text ≤ 100`, `photo?: image { src, alt }`, `rating?: number`
+
+### `text` — Text
+
+Running text: headings, paragraphs, lists and pull quotes. Use: Any time words carry the section — introductions, stories, policies. Use `columns` for long reading text, `drop-cap` for editorial openings, `callout` for a note that must stand out. Avoid: Walls of text; more than one H1 per page; using bold paragraphs as fake headings. Use the button block for calls to action.
+
+- Variants: `default`, `columns`, `drop-cap`, `callout`
+- Fields: `content: richText`
+
+### `timeline` — Timeline
+
+A sequence of dated or numbered milestones. Use: Company or project history, a programme's weeks, a process from enquiry to delivery. `horizontal` suits 3–5 short steps. Avoid: Undated lists (use a list or columns); invented history; more than ~10 milestones.
+
+- Variants: `vertical`, `alternating`, `horizontal`
+- Fields: `items: list of { date: text ≤ 40, title: text ≤ 100, text?: text ≤ 400 }`
+
+### `video` — Video
+
+A video from YouTube, Vimeo or PeerTube, or an uploaded video file. Use: Walkthroughs, talks, trailers and atmosphere. The player loads only when a visitor presses play, so pages stay fast. Avoid: Autoplaying sound; background loops longer than ~20 seconds; using a video where a photo says the same thing.
+
+- Variants: `default`, `framed`, `cinematic`
+- Fields: `source: "embed" | "file"`, `url?: text ≤ 500`, `file?: media`, `title: text ≤ 120`, `poster?: image { src, alt }`, `caption?: text ≤ 200`, `aspect: "16:9" | "21:9" | "4:3" | "1:1" | "9:16"`, `background: boolean`

package/dist/starter/site/astro.config.mjs

@@ -0,0 +1,8 @@
+// OpenSpace site shell. Site, base path, routes, images, feeds and publishing all come from
+// openspace.json and content/ via the site-kit integration — there is nothing to configure here.
+import openspace from "@omniharmonic/openspace-site-kit";
+import { defineConfig } from "astro/config";
+
+export default defineConfig({
+  integrations: [openspace()],
+});

package/dist/starter/site/package.json

@@ -0,0 +1,21 @@
+{
+  "name": "openspace-site",
+  "private": true,
+  "type": "module",
+  "scripts": {
+    "dev": "astro dev",
+    "build": "astro build",
+    "preview": "astro preview",
+    "check": "openspace check"
+  },
+  "dependencies": {
+    "@omniharmonic/openspace-site-kit": "^0.1.0",
+    "astro": "^7.4.2"
+  },
+  "devDependencies": {
+    "@omniharmonic/openspace-cli": "^0.1.0"
+  },
+  "engines": {
+    "node": ">=22.23.4"
+  }
+}

package/dist/starter/site/src/pages/[...slug].astro

@@ -0,0 +1,10 @@
+---
+// Every page, collection item, list page and the 404 page of the site, rendered by
+// @omniharmonic/openspace-site-kit from content/. Custom code belongs in src/overrides/ (Advanced).
+import { renderPage, staticPaths } from "@omniharmonic/openspace-site-kit/route";
+
+export const getStaticPaths = staticPaths;
+// biome-ignore lint/correctness/noUnusedVariables: used by the template below
+const html = await renderPage(Astro.props);
+---
+<Fragment set:html={html} />

package/dist/starter/site/tsconfig.json

@@ -0,0 +1,5 @@
+{
+  "extends": "astro/tsconfigs/strict",
+  "include": [".astro/types.d.ts", "**/*"],
+  "exclude": ["dist"]
+}