Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
File renamed without changes.
File renamed without changes.
10 changes: 5 additions & 5 deletions PLAN.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,9 +39,9 @@ The short list, in order. Tick or remove an item as it lands; the history stays
- [x] Jeremy confirmed the other nine calls as recommended (2026-11-15).
- [x] Build this repository's half on `claude/forms-6a` (2026-11-15), then the cloud's (2026-11-15, in `vesper-cloud`). See "Phase 6a: progress".
- [x] Jeremy's OK (2026-11-15) for the cloud's new bindings, pushing both branches, and the staging deploy: done that day. Staging is migrated and deployed; `SECRETS_KEY` isn't set there yet.
- [ ] Open the PRs, so CI runs (it runs only on pull requests in both repositories).
- [ ] The end-to-end check on staging: `SECRETS_KEY` on both staging Workers (Jeremy's), and a site with forms that the staging cloud can read.
- [ ] Release `0.1.0-next.3`. wcpl.net launches on it.
- [x] The PRs: #14 here, merged 2026-11-15 after #13, and VesperCMS/vespercms-cloud#3.
- [x] Staging's check dropped (Jeremy, 2026-11-15: "just go live", as no site runs on the cloud yet). He saw the form, the API, routing, a confirmation and the inbox work by hand against the real API and app locally first. The cloud went to production that day, at `3ad9a2d`.
- [ ] Release `0.1.0-next.3`: versioned here; the Release workflow publishes it from `main`. wcpl.net launches on it.

**Next phase**
- [ ] Phase 5, Billing and ops. Before it starts, Jeremy decides spec §13.4: the final prices, from the cloud's measured cost (the addendum's numbers are placeholders). Bring him options; never pick.
Expand Down Expand Up @@ -80,7 +80,7 @@ Blocks (proposed, decided and built 2026-10-26): "Blocks: lists of different kin

## Phase 6a: progress

Started 2026-11-15, the day its calls were confirmed. The steps are the design's order of work, below. Built on `claude/forms-6a` (branched from #13's head, which should merge first), not yet pushed.
Started 2026-11-15, the day its calls were confirmed. The steps are the design's order of work, below. Built on `claude/forms-6a` (branched from #13's head) and merged in #14 on 2026-11-15, after #13.

| Step | What | Status |
|---|---|---|
Expand All @@ -89,7 +89,7 @@ Started 2026-11-15, the day its calls were confirmed. The steps are the design's
| 3 | `vespercms/forms`, `virtual:vesper/forms`, `<Form>` and its script, the dev capture | Built. The script is 5 KB gzipped (the test holds it to 8). A build with forms and no cloud project warns |
| 4 | The contract's `forms` section, the fake's endpoints, the playground's form, e2e, docs | Built: eight contract cases, passing against the fake and the real cloud; `e2e/cloud/forms.spec.ts` (eight tests, JavaScript on and off); `site/forms.mdoc`, the README and the reference; `vesper agents` says how a site's forms work |
| 5–8 | The cloud's half | In `vesper-cloud`: see its PLAN.md |
| 9 | The changeset and `0.1.0-next.3` | Waits for the cloud's staging check |
| 9 | The changeset and `0.1.0-next.3` | Versioned 2026-11-15, after the cloud went to production (`3ad9a2d`); the Release workflow publishes it |

**Found while building:**
- **A redraw on blur moved Send under a click.** Clearing an error or the summary as a field was left shifted the page between the button's mousedown and mouseup, so the click missed and nothing was sent. The script now adds errors and changes the summary only on submit; an error goes as its answer is fixed (DECISIONS.md, "<Form>'s script redraws nothing as a field is left").
Expand Down
2 changes: 1 addition & 1 deletion apps/playground/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@
"dependencies": {
"@astrojs/markdoc": "^2.1.0",
"@astrojs/mdx": "^8.1.0",
"vespercms": "0.1.0-next.2",
"vespercms": "0.1.0-next.3",
"astro": "^7.4.0",
"lucide": "^1.59.0"
},
Expand Down
2 changes: 1 addition & 1 deletion apps/site/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
"dependencies": {
"@astrojs/markdoc": "^2.1.0",
"@fontsource/figtree": "^5.3.0",
"vespercms": "0.1.0-next.2",
"vespercms": "0.1.0-next.3",
"astro": "^7.4.0",
"lucide": "^1.59.0",
"micromark": "^4.0.3"
Expand Down
16 changes: 8 additions & 8 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

10 changes: 10 additions & 0 deletions packages/admin/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,15 @@
# @vespercms/admin

## 0.1.0-next.3

### Patch Changes

- 2a1602b: Forms (Phase 6a): define a form in `src/forms.config.ts` with `defineForm` from `vespercms/forms`, and put it on a page with `<Form name="…" />` from `vespercms/components`. It works without JavaScript, posting to Vesper Cloud, which sends the browser back to the page's thanks message or shows the form again with the answers kept; with JavaScript, Vesper's own 5 KB script checks answers, posts without leaving the page and moves focus to the error summary or the thanks message. Fields can be text (`tel` is new), numbers, dates and times, choices, lists of choices (`checkboxes`), yes or no (`checkbox`) and groups. The build refuses what a form can't take and warns that a `.refine()` never runs on a submission; without a cloud project each form says it isn't connected yet. In `astro dev` posts are kept in `.vesper/forms/` and nothing is sent. `@vespercms/core/forms` has the reading, routing, confirmation and drawing the cloud shares, and `runCloudContract` a forms section. File uploads come in Phase 6b.
- 448d685: Each package includes its `CHANGELOG.md`, so `node_modules/vespercms/CHANGELOG.md` says what changed before you update.
- Updated dependencies [2a1602b]
- Updated dependencies [448d685]
- @vespercms/core@0.1.0-next.3

## 0.1.0-next.2

### Patch Changes
Expand Down
4 changes: 2 additions & 2 deletions packages/admin/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@vespercms/admin",
"version": "0.1.0-next.2",
"version": "0.1.0-next.3",
"description": "The Vesper studio: the editor UI served at /admin, one bundle for every storage mode.",
"license": "MIT",
"homepage": "https://vespercms.com",
Expand Down Expand Up @@ -47,7 +47,7 @@
"@tiptap/pm": "^3.32.0",
"@tiptap/react": "^3.32.0",
"@tiptap/starter-kit": "^3.32.0",
"@vespercms/core": "0.1.0-next.2",
"@vespercms/core": "0.1.0-next.3",
"dompurify": "^3.4.17",
"maplibre-gl": "^6.14.0",
"react-aria-components": "^1.22.1"
Expand Down
11 changes: 11 additions & 0 deletions packages/astro/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,16 @@
# vespercms

## 0.1.0-next.3

### Patch Changes

- 2a1602b: Forms (Phase 6a): define a form in `src/forms.config.ts` with `defineForm` from `vespercms/forms`, and put it on a page with `<Form name="…" />` from `vespercms/components`. It works without JavaScript, posting to Vesper Cloud, which sends the browser back to the page's thanks message or shows the form again with the answers kept; with JavaScript, Vesper's own 5 KB script checks answers, posts without leaving the page and moves focus to the error summary or the thanks message. Fields can be text (`tel` is new), numbers, dates and times, choices, lists of choices (`checkboxes`), yes or no (`checkbox`) and groups. The build refuses what a form can't take and warns that a `.refine()` never runs on a submission; without a cloud project each form says it isn't connected yet. In `astro dev` posts are kept in `.vesper/forms/` and nothing is sent. `@vespercms/core/forms` has the reading, routing, confirmation and drawing the cloud shares, and `runCloudContract` a forms section. File uploads come in Phase 6b.
- 448d685: Each package includes its `CHANGELOG.md`, so `node_modules/vespercms/CHANGELOG.md` says what changed before you update.
- Updated dependencies [2a1602b]
- Updated dependencies [448d685]
- @vespercms/core@0.1.0-next.3
- @vespercms/admin@0.1.0-next.3

## 0.1.0-next.2

### Patch Changes
Expand Down
6 changes: 3 additions & 3 deletions packages/astro/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "vespercms",
"version": "0.1.0-next.2",
"version": "0.1.0-next.3",
"description": "The Vesper integration for Astro: the studio at /admin, schema helpers and config.",
"license": "MIT",
"homepage": "https://vespercms.com",
Expand Down Expand Up @@ -84,8 +84,8 @@
"//dependencies": "axe-core runs the build's accessibility checks (spec §6.18, layer 2), the same engine as the e2e suite; jsdom is the DOM it runs in without a browser, matched against Chromium (DECISIONS.md). pagefind indexes the site for search (spec §6.19, D23): a regular dependency because search is on by default, with a 58 MB binary for the build machine's platform, as Starlight ships it. All three load only in astro:build:done.",
"dependencies": {
"@markdoc/markdoc": "^0.5.10",
"@vespercms/admin": "0.1.0-next.2",
"@vespercms/core": "0.1.0-next.2",
"@vespercms/admin": "0.1.0-next.3",
"@vespercms/core": "0.1.0-next.3",
"axe-core": "^4.14.0",
"jsdom": "^30.1.3",
"pagefind": "^1.5.2"
Expand Down
7 changes: 7 additions & 0 deletions packages/core/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,12 @@
# @vespercms/core

## 0.1.0-next.3

### Patch Changes

- 2a1602b: Forms (Phase 6a): define a form in `src/forms.config.ts` with `defineForm` from `vespercms/forms`, and put it on a page with `<Form name="…" />` from `vespercms/components`. It works without JavaScript, posting to Vesper Cloud, which sends the browser back to the page's thanks message or shows the form again with the answers kept; with JavaScript, Vesper's own 5 KB script checks answers, posts without leaving the page and moves focus to the error summary or the thanks message. Fields can be text (`tel` is new), numbers, dates and times, choices, lists of choices (`checkboxes`), yes or no (`checkbox`) and groups. The build refuses what a form can't take and warns that a `.refine()` never runs on a submission; without a cloud project each form says it isn't connected yet. In `astro dev` posts are kept in `.vesper/forms/` and nothing is sent. `@vespercms/core/forms` has the reading, routing, confirmation and drawing the cloud shares, and `runCloudContract` a forms section. File uploads come in Phase 6b.
- 448d685: Each package includes its `CHANGELOG.md`, so `node_modules/vespercms/CHANGELOG.md` says what changed before you update.

## 0.1.0-next.2

### Patch Changes
Expand Down
2 changes: 1 addition & 1 deletion packages/core/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@vespercms/core",
"version": "0.1.0-next.2",
"version": "0.1.0-next.3",
"description": "Vesper's framework-free core: schema introspection, manifest, serializers and the storage adapter interface.",
"license": "MIT",
"homepage": "https://vespercms.com",
Expand Down
Loading