Forms: a "placed on" built-in — which pages place a form, as the item row's digest and the picker's meta #350

New issue

Open

opened 2026-10-24 10:37:09 +02:00 by dominik.polakovics · 0 comments

dominik.polakovics commented

2026-10-24 10:37:09 +02:00

Owner

The fact most worth seeing before disabling or deleting a form: the pages whose Form element places it. Drawn as the item row's digest ("2 pages · /contact/ · /about/ · +1"; "Not placed on any page yet"), and as the meta line of the picker's list view.

Rule: "which pages place this page" is evaluated once, on the server, from the Form elements' form params across the site's content (the page field stores the permalink), and served per entry in GET /api/module/entries (e.g. placedOn: [{path, title, permalink}] or a count plus the first n). The client never scans content. Generalisation to decide in triage: any page-typed param pointing at an entry (news teasers), or forms only.

Documents: docs/api.md GET /api/module/entries; scaffold/site/AGENTS.md "Editor modules" (a built-in usable as a column/digest); docs/features.md "The forms bundle"; docs/architecture.md if a content index is introduced. Skills: create-feature. Also enables "View on " in the row menu (#352).

Mockup: https://claude.ai/artifact/VKDHiP5SA6Nxdx5Ery762Q — "Proposal" pin 6, "Decisions" B; https://claude.ai/artifact/XC9KeADJfRrjD428fZFMdj §5 and https://claude.ai/artifact/BN7XprNTpmx1ZjigEcVCET (list view meta). Follow-up to #347 and #348 (agreed 2026-10-24). The fact most worth seeing before disabling or deleting a form: the pages whose Form element places it. Drawn as the item row's digest ("2 pages · /contact/ · /about/ · +1"; "Not placed on any page yet"), and as the meta line of the picker's list view. Rule: "which pages place this page" is evaluated once, on the server, from the Form elements' `form` params across the site's content (the `page` field stores the permalink), and served per entry in GET /api/module/entries (e.g. `placedOn: [{path, title, permalink}]` or a count plus the first n). The client never scans content. Generalisation to decide in triage: any `page`-typed param pointing at an entry (news teasers), or forms only. Documents: `docs/api.md` GET /api/module/entries; `scaffold/site/AGENTS.md` "Editor modules" (a built-in usable as a column/digest); `docs/features.md` "The forms bundle"; `docs/architecture.md` if a content index is introduced. Skills: `create-feature`. Also enables "View on <page>" in the row menu (#352).

dominik.polakovics added the

needs-triage

enhancement

labels

2026-10-24 10:37:09 +02:00