Better Content Language Settings

Core's Content language and translation page shows every setting for every bundle at once: a collapsible section per entity type, a table of bundles inside each, and the full list of field checkboxes nested inside every row. When you enable an entity type for customization, nothing is customised yet, only a fieldset pops up possibly outside of the screen you are viewing. It's a spaceship cockpit: everything visible, nothing prioritised. While good to get all the information if you need it, its very complicated to operate especially for new users.

This module rebuilds the page and introduces 3 layers of configuration complexity instead of the one spaceship cockpit:

1. Start with recommended settings When nothing is configured yet, there is a best effort estimation as to what the site will probably need to get started. This is based on our experience in Drupal CMS.
2. Bundle level simple translation checkbox One flat, filterable table with a row per bundle across all entity types, and a checkbox per row. Rows summarize field layer translatability settings but don't display all the settings immediately.
3. Advanced mode A Customize dialog per row holds the bundle's default language and whether editors may choose a different one — settings that apply whether or not the bundle is translatable. It also lists the bundle's fields, with select-all and none, so per-field detail only appears for the bundle you are working on.

The module alters core's form rather than replacing it, so modules that integrate with that form — Drupal Canvas, for instance — keep working unchanged. Requires the Language module; the translation layers appear when Content Translation is installed. (But this module only really gives a boost to site configuration when you have Content Translation module installed).

LLM disclosure

LLM was involved in the UI design and development of this module.