Make the fields
fit the work.
A workshop listing, a client project, a community directory. Describe what people need to edit, then give it structure. Your agent implements the application around that model.
Start with work you recognise.
Choose a structure, try its fictional example, then edit it to fit. These are field patterns for your agent to build from.
An event people can join, with a format, an optional online link and a repeating materials list.
Change Format to Online to reveal the joining link.
Opening a pattern changes this page. Your saved draft stays intact until you explicitly save over it. Sample entries are never stored or sent.
Start by describing what you want
Give the request to your agent. It returns the supported model JSON; import that file below. No AI account or paid API is connected by this page. Use fictional examples rather than private client records.
Content structure
Useful constraints beat broken forms.
This first editor supports short and long text, HTTPS links, whole numbers, Yes / no, choices and repeating groups. Repeaters contain up to six scalar fields and cannot nest, matching the current EmDash implementation. Groups and optional conditions belong to the generated app form; required conditional fields need a reviewed server implementation.
How this fits Init · Official EmDash field types · Reusable model implementation