Forms generated from JSON Schema
When your AI builds something on Tessryx, it also describes the data, such as a menu whose items each have a name, a price and maybe a photo. That description is a JSON Schema, and Tessryx reads it to lay out the form your team edits in, with dropdowns, date pickers and lists you can drag into order.
Change the schema and the form changes with it. The layout comes from the schema too, its field order, groups and labels, since there's no drag-and-drop designer. The editor below is the real one from the product, so try changing the schema.
Try it
A schema and the editor made from it
Schema
{ "type": "object", "required": [ "name", "email", "pickup", "items" ], "properties": { "name": { "type": "string", "title": "Your name", "minLength": 1 }, "email": { "type": "string", "format": "email", "title": "Email", "examples": [ "sam@example.com" ] }, "pickup": { "title": "Pick up", "oneOf": [ { "const": "friday", "title": "Friday after school" }, { "const": "saturday", "title": "Saturday morning" } ] }, "items": { "type": "array", "title": "Order", "minItems": 1, "items": { "type": "object", "required": [ "item", "dozens" ], "properties": { "item": { "type": "string", "title": "Item", "enum": [ "Chocolate chip cookies", "Lemon bars", "Banana bread" ] }, "dozens": { "type": "integer", "title": "How many dozen", "minimum": 1, "maximum": 6, "default": 1 } } } }, "notes": { "type": "string", "title": "Anything we should know?", "x-tessryx-ui": { "input": "textarea", "options": { "rows": 2 } } }, "paid": { "type": "boolean", "title": "Paid", "default": false } } }
Edit the schema and the editor changes with it.
Editor
Your name
Pick up
Order
Anything we should know?
Paid
How it works
- 01
The schema picks each control
A number with a range gets a slider and a short list of choices gets radio buttons. A field marked as an email or a date gets an input built for it.
- 02
A few hints cover the rest
Plain JSON Schema has no way to ask for a cron field, a timezone or an image upload. A short list of optional hints does, and other tools simply ignore them.
Under the hood
The technical details
- from the schema
- title is the label, description the help text, examples[0] the placeholder, declaration order the field order. No form builder, no config file.
- everywhere
- The same renderer draws the editors for records and for the platform's own definitions: endpoints, workflows, schedules, integrations and apps.
- depth
- Nested objects, arrays and unions to any depth the data has; past 10 levels you edit in the JSON tab.
Related features
Inputs that fit the value
Fields marked as an email, a web address, a date or a duration get inputs made for them. A number with a range gets a slider and a yes-or-no gets a switch. Short lists of choices become radio buttons, long ones a searchable list.
Live validation and a raw JSON view
Problems show up as you type, written out in words on the field that has them. A JSON tab sits beside the form for pasting in a big block or fixing something by hand.
Content Studio
Content Studio is where your team edits records, in the form or as JSON, and publishes them. Folders and search help on a big site.
Rich text, Markdown and code fields
Long text can be Markdown with a live preview or rich text with a toolbar. Code fields get a proper code editor, with highlighting for 22 languages.