From 8d7a8ff6b281e01025e98d501483a59992ab8419 Mon Sep 17 00:00:00 2001 From: Daniel Lopez Date: Sat, 15 Aug 2026 19:14:11 +0200 Subject: [PATCH 1/3] Edit the field where it sits, and draw it as it will look MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The canvas was a list of *descriptions* of fields — an icon, the label as static text, the type name underneath — and everything you could change lived in a pane on the right. So the two things you do most, writing the question and writing what goes in the box, happened at arm's length from the thing they belong to, and the canvas never answered the question you open a form builder to ask: what will this form look like? Now the card draws the control and its text is editable in place. Click the question to rewrite it, click the box to set its placeholder, click an option to rename it, and use + Add option where the options actually are. Required is a switch on the card instead of a badge that told you the state and made you go elsewhere to change it. Logic, validation and prefill stay in the inspector, because those are properties *of* a field rather than parts of it. This is not a second renderer, and two things keep it from becoming one. `builder.css` is registered with `form.css` as a dependency, so every front-end class is already in the document; emitting `.atf-input` and `.atf-choice__input` inside an `.atf-form` means the theme's own radius, borders, spacing and label position apply because it is the same stylesheet. The token values come from the server's own render — one request per theme change, its `