Difference between Field Default Values and Field Defaults?

Hello @ressa → ,

The module Field Defaults → can be used when:
> When creating a new field or updating an existing field.
> What it does is, when we add / update any fields configuration [for that particular entity type bundle, eg: Article]. It allows us to update or preserve all the existing content for that field for that particular bundle.
> We can consider this module as an assistant to Bulk Operations on field values per bundle.

What the Field Default Values → module provides is:
> It gives us the configuration form (/admin/config/field-defaults), which allows us to set the default values for some majorly used field types. such as Text fields, Number fields, Email etc.
> Whenever we create a new field on any entity type, on any entity bundle.. It automatically checks the "Set default value" checkbox and pulls the default value from our saved configs for that field type.
> Means, just the one time process saves our time to fill default values.., whenever we plan to create the field of particular field type at any place over the entire site.
> Note: It works only when we create a new field.

Thanks, I get it now -- also after re-reading the project page a bit more attentively :)

Maybe you could consider showing two images of how it works, of setting the defining the default value for a field, and then showing the result, when you are creating a field of that type? I think then I would have understood it faster how it works.

Maybe include something like this on the project page?

Set default value for "Text (plain)" field types

Default value already set, when creating a new field of type "Text (plain)"

PS. Maybe add Drupal 11 support in *.info.yml? It seems to work fine ...

Thanks for the suggestions.

I've added the illustrative screenshots and added a new release → with Drupal-11 support.

Check here: https://www.drupal.org/project/set_field_defaults →

Thanks @keshav patel, it's very clear now, how the module works. And great that there's also Drupal 11 support.

Perhaps, as a final touch, you could consider setting 1.0.x as the default branch in the GitLab repo, since that's where development takes place?

Done, thanks!
Closing this issue.

Beautiful, thanks!