The schema support assumes I want to ask for variable input, can I force a value and make a field read only?

[fredvd]

The schema describes the form that is presented to the user creating the site.

But what If I want to 'fixate' some variables, like the default language, portal timezone, site title/id, etc? I assume I could fix this in a pre or post-handler, but it would be nice to also support a 'read only' version in the schema.json where the value is already set.

use case: I want to create a 'fixture' in a project where the testing-pages for a project are included in code during development and a frontender just has to create the backend site from a distribution for local dev setup. One identical configuration for all devs.

[fredvd]

Also, according to the readme these fields are required, which is strange are thereis also a required key and a pre_handler can override the answers to provide fixed values. IMHO only site_id should still be required as it needs to be calculated and shown to the end user for id collissions:

these are listen in the readme as required, but shouldn't, as I could set them in a pre_handler:

site_id
title
description
default_language
portal_timezone
setup_content

portal_timzeone seems not to be required, and is not even missed when not setting it in the pre_handler.