Alternatives

Direct alternatives for Schema Form

• Automatic Configuration Form – implements the same idea, but is targeted only at configuration forms. It does not use plugins, so support is limited to only built-in field types.
• Schema Based Config Forms – targeted only at configuration forms, extendable by plugins, and provides more field types out of the box.

Migration from alternatives

If you use those modules, you can simply replace them with this module Schema Form without any changes to your created schemas, because it supports form declaration formats from these modules too.

When you fully remove the previous modules, we recommend extracting the form-related data from the schema into Schema Form Design entities, to keep the schema YAML file clean and compact, holding only the schema-related data.

Alternatives based on content storage

There are also some modules that provide site configuration forms as content entities:

• Config Pages
• Site Settings and Labels
• ECK Site Settings
• Content Entity Builder

However, they store the configuration as content entities, which is conceptually wrong. Therefore, we do not recommend storing your configuration as content entities.

Why content is not good to store settings?

Because configurations is the configuration. It is not content! Let’s store it in the right place!

If you need to make the configuration editable by end users, there are many recommended ways to implement this using configuration, not content: Config Split, Config Ignore, etc.