Content and editors
The control surface: editing your content in auto-generated forms, and the studios behind them.
This is the surface you'll live in. Your agent builds the machinery; you run the site by editing content in forms: no code, no rebuilds.
#Where your forms come from
Every editor in Tessryx is generated from a schema. Because the schema describes your data's shape, Tessryx knows exactly what form to draw:
- A text field → a text box (or a rich editor for long-form).
- A number → a number input, or a slider when it has a range.
- A date → a date picker. A yes/no → a toggle. A fixed set of choices → a dropdown or radio buttons.
- An image → an uploader. A list → an add/remove list. A color → a color picker.
- A link to another record → a searchable picker that browses your other content.
- A choice between shapes (say "either a link or an embed") → a variant dropdown that swaps the fields beneath it.
- A set of key/value pairs → a small map editor. Pick several from a set → a multi-select. A time or timezone → a time picker and a timezone chooser.
You never configure this. Design the data and the editor appears, correctly typed, with labels and help text your agent wrote into the schema.
Every editor also has a JSON tab showing the raw data behind the form. You rarely need it (the form is the point), but it's there to paste a large blob at once, or for the rare case a hand-broken schema won't render as a form. Both views edit the same underlying record.
For the full catalog of controls (sliders, rich text and code editors, cross-record pickers, maps, variant choosers, cron and timezone fields, and more), see Form fields.
#Editing content: Content Studio
Content Studio is your CMS. It holds your content records, each a form-driven entry following its schema. Open a record, change the fields, save. Records are organized into folders, so a large site (hundreds of blog posts, a full catalog) stays browsable.
A saved edit is a draft until it's published. What "published" means, and how a change reaches your live site, is covered in Publishing.
The rule of thumb: anything you'll change regularly (copy, prices, images, listings) lives in content records you can edit here. The logic that renders it stays in the workflow, which is your agent's to own. That split is deliberate: you get to change the what freely without risking the how.
#The studios
Content Studio is the one most people use. The others mirror the rest of the building blocks, for when you want to look under the hood or make a change by hand. Everything here, your agent can also do for you.
| Studio | For | You'll use it to… |
|---|---|---|
| Content | Content records | Edit your site's words, images, and data |
| Schema | Data shapes | See or tweak the structure behind a form |
| Delivery | Endpoints | Review the public URLs and their caching |
| Workflow | Rendering logic | Inspect how a page is built |
| API | Integrations | Review a connection to an outside system |
| Scheduler | Schedules | Turn automations on/off, see run history |
You reach all of them from the dashboard, and from an app you can open just the pieces belonging to that project.
#Previewing before it's live
You (or your agent) can preview a page exactly as it will serve, with real data and the right formatting, before publishing. Nothing a visitor sees changes until you publish, so you can iterate freely.