Yes, there is another way to do this in configuration. You can change

  translatable: true

in core.base_field_override.node.[content-type].title.yml.

If you don't find this configuration file, then there are no changes made so far for the title field. You can do this for example by modifying "Title field label" in the content type, which is also stored in this configuration and if it doesn't exist it will be created, so that you'll find the yaml in the exported config.

Yes, there is another way to do this in configuration. You can change

  translatable: true

in core.base_field_override.node.[content-type].title.yml.

If you don't find this configuration file, then there are no changes made so far for the title field. You can do this for example by modifying "Title field label" in the content type, which is also stored in this configuration and if it doesn't exist it will be created, so that you'll find the yaml in the exported config.

After you've changed the field label, export the configuration, open for each content type the mentioned yaml file, change translatable to false and reimport the configuration again.

See https://www.drupal.org/docs/8/configuration-management/workflow-using-the-drupal-ui or if you have installed drush use these two commands:

drush config-export
drush config-import

see https://www.drupal.org/docs/8/configuration-management/workflow-using-drush.

Yes, there is another way in configuration. You can change

translatable: true

to false in core.base_field_override.node.[content-type].title.yml.

If you don't find this configuration file, then there are no changes made so far to the title field. You can do this for example by modifying "Title field label" in the content type. This is stored then in this configuration and if it doesn't exist it will be created.

Yes, there is another way to do this in configuration. You can change

  translatable: true

in core.base_field_override.node.[content-type].title.yml.

If you don't find this configuration file, then there are no changes made so far for the title field. You can do this for example by modifying "Title field label" in the content type, which is also stored in this configuration and if it doesn't exist it will be created, so that you'll find the yaml in the exported config.