Developers and API
Can I define the content model in code?
The schema builder is visual, and its output is a JSON schema you can read, diff and copy from a live panel next to the model. Fields, groups, relationships and validation rules all live there. Changing a model does not require a migration step, so a field added on Tuesday is queryable on Tuesday.
Visual, with the JSON next to it
The builder is a visual editor and its output is a JSON schema shown in a live panel beside the model. Fields, groups, relationships and validation rules are all in it, and it can be read, copied and diffed.
So the model is designed by whoever should be designing it, and reviewed the way code is reviewed.
No migration step
Changing a model does not require one. That is the difference between a content model and a database schema, and it is why a field can be added the moment somebody realises it is missing rather than in the next release.
The discipline that replaces the migration is the review. Nothing stops a bad field; the JSON just makes it visible before it spreads.
Reviewing a model change
Copy the JSON before and after and diff the two. A model change reads as a handful of lines, which is short enough that somebody will actually read it, which is the only property that makes a review real.
Also in developers and api
Still have a question left
Thirty minutes with the product team, and a straight answer.